54204_PP09_Chap09PPT_Modified

54204_PP09_Chap09PPT - Chapter 9 INTERACTION ORIENTED SOFTWARE ARCHITECTURES Objectives • Introduce concepts of interaction-oriented software

Info iconThis preview shows pages 1–10. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Chapter 9 INTERACTION ORIENTED SOFTWARE ARCHITECTURES Objectives • Introduce concepts of interaction-oriented software architectures. • Describe the MVC and PAC architectural styles. • Discuss the applicable domains of interaction- oriented software architectures. • Discuss the benefits and limitations of the interaction-oriented software architecture style. • Discuss other related architectures. Overview • The interaction oriented software architecture decomposes the system into three major partitions: Data module Control module View presentation module • Each module has its own responsibilities. • The data module provides the data abstraction and all core business logic on data processing. • The view presentation module is responsible for visual or audio data output presentation and it may also provide user input interface as well when necessary. • The control module determines the flow of control involving view selections, communications between modules, job dispatching, and certain data initialization and system configuration actions. • The key point of this architecture is in the separation of user interactions from data abstraction and business data processing. • Since there may be many view presentations in different formats multiple views may be supported for the same data set. • Even for a specific view presentation, the interfaces or views may need to change often, so loose coupling between data abstractions and its presentations is helpful, and this is supported by this style. • The loose coupling connections can be implemented in many different ways such as explicit method invocation or implicit registration/ notification method invocation. • The control module plays a central role that mediates the data module and view presentation modules. • All three modules may be fully connected. • This chapter presents two major styles categories of interaction-oriented architectures; these are the Presentation-Abstraction-Control (PAC) and the Model-View-Controller (MVC) architectures. • These two models are very similar in the sense that they propose three component decompositions. • The Presentation module of PAC is like the View module of MVC; • the Abstraction module of PAC looks like the data (or Model) module of MVC; • the Control module of PAC is like the Controller module of MVC. • Both of MVC and PAC are used for interactive applications such as Web online applications, and distributed applications with multiple talks and user interactions. • They are different in their flow of control and organization. • The PAC is an agent based hierarchical architecture, whereas the MVC does not have a clear hierarchical structure and all three modules are connected together. Model-View-Controller (MVC) • “Model-View-Controller programming is the application of this three-way factoring whereby objects of different classes take over the operations related to the application domain (the model), the display of the application's state (the view), and the user interaction with the model and the view (The controller).” •...
View Full Document

This note was uploaded on 09/14/2010 for the course SAD 333 taught by Professor Luis during the Summer '10 term at St. Louis CC.

Page1 / 51

54204_PP09_Chap09PPT - Chapter 9 INTERACTION ORIENTED SOFTWARE ARCHITECTURES Objectives • Introduce concepts of interaction-oriented software

This preview shows document pages 1 - 10. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online