Architectural Design and Models of Software Architecture (Group 3)

DFP5043 – Software Requirement and Design

Group 3 – MOHAMMAD HUZAIFAH BIN MOHAMED YUSOFF (01DDT17F1007)
LUKMAN HAKIM BIN MAMAT (01DDT17F1001)
MOHAMMAD AMIRUL SHAH BIN MOHAMAD NASIR (01DDT17F1021)
MUHAMMAD ALIF BIN ZAKARIA (01DDT17F1014)
AHMAD FITRI BIN AHMAD (01DDT17F1006)
AHMAD LUQMAN BIN ADAM (01DDT17F1009)
MUHAMAD AFIQ FAHMI BIN JINS (01DDT17F1027)

Architectural Design is a creative process so the process differs depending on the type of system being developed.

The logical view is concerned with the functionality that the system provides to end-users. UML diagrams are used to represent the logical view include, class diagrams, and state diagrams or which shows the key abstractions in the system as objects or object classes.

The process view deals with the dynamic aspects of the system, explains the system processes and how they communicate, and focuses on the runtime behaviour of the system. The process view addresses concurrency, distribution, integrators, performance, and scalability. UML diagrams to represent process view include the activity diagram.

The development view illustrates a system from a programmer's perspective and is concerned with software management. This view is also known as the implementation view. It uses the UML Component diagram to describe system components. UML Diagrams used to represent the development view include the Package diagram.

The physical view depicts the system from a system engineer's point of view. It is concerned with the topology of software components on the physical layer as well as the physical connections between these components. This view is also known as the deployment view. UML diagrams used to represent the physical view include the deployment diagram.

The scenarios describe sequences of interactions between objects and between processes. They are used to identify architectural elements and to illustrate and validate the architecture design. They also serve as a starting point for tests of an architecture prototype. This view is also known as the use case view.