Skip to main content

General Idea for Creating a Software Architecture Using Reference Models

The architecture developed in this blog will follow the steps given in the diagram below:

 According to the diagram:
  • The first step is to form a list of functional requirements for the software.
  • The second step is to form a module structure representing the functional requirements.
  • The third step is to identify the style(s) suitable for the architecture. The style should be the one that incorporated all the quality attributes associated with the functional modules.
  • The fourth step is to combine the module structure with the appropriate style into a single diagram. The resultant diagram is known as the Reference Architecture Diagram. NOTE: THE ARCHITECTURE IS NOT YET FINALIZED!
  • The fifth step is to give a brief description on the functional module. NOTE: NOW THE ARCHITECTURE IS COMPLETE
  • The final step is to develop the system represented by the designed software system's architecture.
Formation of a Software Architecture for Student Portal System
  • Step 1: Identification of Functional Requirement:
    1. The student has to register himself/herself with the system.
    2. The student can view their attendance record.
    3. The student can give course feedback.
    4. The student can attempt an exam.
  • Step 2: Formulation of a Module Structure: The models can be connected depending upon their relationships.

  • Step 3: Identification of Suitable Software Architectural Style: Multiple styles can be selected for the system.Two architectural styles have selected for it:
    • Layered Architecture:
Layered Architecture
    • Client-Server (Peer-to-Peer) Architecture:
  • Step 4: Formulation of Reference Architecture: The best suitable software architectural style is combined with the designed module structure.
    • Using Layered Architecture:

Reference Architecture for Student Portal System using Layered Architectural Style


    • Using Client-Server (Peer-to-Peer) Architecture:
Reference Architecture for Student Portal System using Client-Server (Peer-to-Peer) Architectural Style
  • Step 5: Description of Functional Modules: 
This sections describes the following aspects of all the identified functional modules:
  1. Types of acceptable inputs.
  2. Types of outputs given by the module.
  3. Functionalities performed by the module.

Comments