CS504 Final Term Short Notes Lectures 23-45

CS504 Short Notes final term · Lec 23 to 45 · Website Link:

Important Note

You should never copy paste the same answer which we are providing. Please do make some changes in the solution file. If you appreciate our work, please share our website with your friends.

آپ کو کبھی بھی وہی جواب کاپی پیسٹ نہیں کرنا · چاہیے جو ہم فراہم کر رہے ہیں۔ براہ کرم حل · فائل میں کچھ تبدیلیاں کریں۔ اگر آپ ہمارے · کام کی تعریف کرتے ہیں تو براہ کرم ہماری ویب · کو اپنے دوستوں کے · ساتھ شیئر کریں۔

Architectural Views

Krutchen proposed that the software architecture model should be composed of multiple views as a software architecture deals with abstraction, with decomposition and composition, with style and esthetics as well as requirements from different stake holders. His architectural model is known as Krutchen’s 4+1 architectural view model. As evident, this model proposes the development of 5 main views namely.

Logical view: The logical view is the object model of the design.

Process view: The process view captures the concurrency and synchronization aspects of the design.

Physical view: The physical view documents the mapping(s) of the software onto the hardware and reflects its distributed aspect.

Development view: The development view describes the static organization of the software in its development environment.

Use case view: The use case view uses selected use cases or scenarios to validate that the architecture supports the required functionality.

Views

Views are an engineering tool to help achieve desired system qualities. Each view provides an engineering handle on certain quality attributes. In some systems, distinct views collapse into one. Views are also used as documentation vehicle for current development and future development. Users of views include both managers and customers. For these reasons views must be annotated to support analysis. This annotation can be achieved with the help of scenarios and design rationale.

They are also used to understand the dynamic behavior of the system and understand the limits of design. Hierarchical Views

Every view is potentially hierarchical, e.g. functional view could contain sub-functions. Similarly development view contains directories which contain files. Code view would have modules and systems that contain sub-modules and sub-systems respectively. Concurrency view contains processes that are further subdivided into threads. Finally, physical view clusters contain computers which contain processors.

The architectural model of a system may conform to a generic architectural model or style. An awareness of these styles can simplify the problem of defining system architectures. However, most large systems are heterogeneous and do not follow a single architectural style.

Each style describes a system category that encompasses:

(1) A set of components (e.g., a database, computational modules) that perform a function required by a system. (2) A set of connectors that enable “communication, coordination and cooperation” among components. (3) Constraints that define how components can be integrated to form the system and semantic models that enable a designer to understand the overall properties of a system by analyzing the known properties of its constituent parts.