Sunday, 10 February 2019

Architectural Design and Models of Software Architecture (Group 1)


DFP5043 – Software Requirement and Design
Tutorial Lab4
Instruction:
Discuss and contribute together to answer  
the questions below and post the answer to the class's blog.
Don't forget to write your name in the blog.

Define and draw example of architectural design and models of software architecture below:
i.                    Architectural Design
ii.                  Logical View
iii.                Process View
iv.                 Development View
v.                   Physical View
vi.                 Scenario
  • Architectural Design
An architectural model is a rich and rigorous diagram, created using available standards, in which the primary concern is to illustrate a specific set of tradeoffs inherent in the structure and design of a system or ecosystem. Software architects use architectural models to communicate with others and seek peer feedback. An architectural model is an expression of a viewpoint in software architecture.
Image result for architecture diagram in software engineering
  • Logical View
The logical view is concerned with the functionality that the system provides to end-users. UML diagrams 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.
Image result for logical view
  • Process View
The process view deals with the dynamic aspects of the system, explains the system processes and how they communicate, and focuses on the runtime behavior of the system.
The process view addresses concurrency, distribution, integrators, performance, and scalability, etc. UML diagrams to represent process view include the activity diagram.
Activity diagrams are graphical representations of workflows of stepwise activities and actions with support for choice, iteration and concurrency.
In the Unified Modelling Language, activity diagrams are intended to model both computational and organizational processes (i.e., workflows), as well as the data flows intersecting with the related activities. Although activity diagrams primarily show the overall flow of control, they can also include elements showing the flow of data between activities through one or more data stores

    • Development View
    The Development Viewpoint is a considerable amount of planning and design of the development environment is often required to support the design and build of software for complex systems. It is the role of the Development view to address these aspects of the system development process.

    Definition
    Describes the architecture that supports the software development process.
    Concerns
    • module organization
    • common processing
    • standardization of design
    • standardization of testing
    • instrumentation
    • codeline organization
    Models
    • module structure models
    • common design models
    • codeline models
    Pitfalls
    • too much detail
    • overburdening the AD
    • uneven focus
    • lack of developer focus
    • lack of precision
    • problems with the specified environment
    Stakeholders
    Production engineers, software developers and testers.
    Applicability
    All systems with significant software development involved in their creation.

    Image result for development view/implementation view example
    • Physical View
    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 following diagram is the UML deployment diagram:
    Image result for deployment diagram in architectural design

    • Scenario
    The description of an architecture is illustrated using a small set of use cases, or scenarios, which become a fifth view. 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. The following diagram is the use case view.
    Image result for use case diagram


    Overall:
    Image result for what is physical view of architectural design


    GROUP 1:
    • ARIF ASNAWI BIN MOHD PAUZI (01DIS17F1047)
    • MUHAMMAD FARID BIN MOHD ARIFFIN (01DIS17F1041)
    • MUHAMMAD AKMAL BIN AHMAD FADZIL (01DIS17F1040)
    • ABDUL RAHMAN BIN MESRUN (01DIS17F1061)
    • MUHAMMAD HASNUDDIN BIN SALAHUDDIN (01DIS17F1062)
    • MUHAMMAD AMIRUDDIN BIN ABDUL KADIR (01DIS17F1034)
    • MUHAMMAD HAFIZ BIN ZUHARI (01DIS17F1037)
    • AHMAD THAQIF ILMAM BIN ABDUL AZIZ (01DIS17F1035)
    • NURUL IZZAH BINTI KAMAL FAISAL (01DIS17F1049)
    • MIMI AMIRAH BINTI CHE ABDUL (01DIS17F1045)
    • NUR AFIQAH BIN MOHAMAD RAMLEE (01DIS171057)
    • KU NURAL' IZZATI BINTI KU KAMARUDZAMAN (01DIS17F1064)
    • NURUL ELISYAH BINTI MUHAMMAD ARSHAD (01DIS17F1033)
    • YASHELA A/P CHANDRANSANGRAN (01DIS17F1101)

    No comments:

    Post a Comment

    UML Group 1

    DFP5043 – Software Requirement and Design Lab 7 Instructions: Discuss with your group. Answer all questions and post the question an...