Model view controller design pattern model holds the

This preview shows page 41 - 50 out of 63 pages.

Model View Controller Design PatternModelholds the domain knowledge (Business Rules).Viewholds the User input and display model.Controllerholds the sequencing of the user inputs and acts as intermediate between Model and View.41Software Engineering -CSC4350/6350 - Rao Casturi
42Model View Controller Design PatternModelControllerViewSmart - Thin- DUMMY approachInitiator , Subscriber & NotifierObserver Design PatternUSERActionResultsRequestRefreshSoftware Engineering -CSC4350/6350 - Rao Casturi
43
,
Source: OOSE-Bernd Bruegge & Allen H. DutoitSoftware Engineering -CSC4350/6350 - Rao Casturi
Peer-to-Peer Architecture Style44
Software Engineering -CSC4350/6350 - Rao Casturi
Three-Tier & Four Tier Architecture45In this style the subsystems are organized into three layers The interface layer includes all boundary objects which deal with end users. Example windows, forms, web pages etc. The application logic layer includes all control and entity objects, realizing the processing, rule checking, and notification required by the application.The storage layerrealizes the storage, retrieval, and query of persistent objects.Source: OOSE-Bernd Bruegge & Allen H. DutoitSource: OOSE-Bernd Bruegge & Allen H. DutoitSoftware Engineering -CSC4350/6350 - Rao Casturi
Pipe and filter Architecture46Pipe and filter architectural style the subsystems process data received from a set of inputs and send results to other subsystems via a set of outputs. The subsystems are called “filters,” and the associations between the subsystems are called “pipes.” Each filter knows only the content and the format of the data received on the input pipes, not the filters thatSource: OOSE-Bernd Bruegge & Allen H. DutoitSoftware Engineering -CSC4350/6350 - Rao Casturi
System Design Activities: Addressing Design Goals47Software Engineering -CSC4350/6350 - Rao Casturi
Addressing Design Goals1.Mapping Subsystems to Processors and Components 2.Identifying and Storing Persistent Data 3.Providing Access Control 4.Designing the Global Control Flow 5.Identifying Services 6.Identifying Boundary Conditions 7.Reviewing the System Design Model 48Software Engineering -CSC4350/6350 - Rao Casturi
49Addressing Design GoalsSource: OOSE-Bernd Bruegge & Allen H. DutoitSoftware Engineering -CSC4350/6350 - Rao Casturi

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture