Analysis Model

  The analysis model connects the system description and design model. The system description provides information about the entire functionality of the system, which is achieved by implementing the software, hardware, and data. In addition, the analysis model specifies the software design in the form of a design model, which provides information about the software's architecture, user interface, and component-level structure.

In the above figure, the analysis model connects the system description and design model. 

The model should concentrate on requirements in the problem domain that are to be accomplished. However, it should not describe the procedure to accomplish the requirements in the system.

Every element of the analysis model should help in understanding the software requirements. This model should also describe the information domain, function, and behavior of the system.

The analysis model should be useful to all stakeholders because every stakeholder uses this model in his own manner. For example, business stakeholders use this model to validate requirements whereas software designers view this model as a basis for design.

The analysis model should be as simple as possible. For this, additional diagrams that depict no new or unnecessary information should be avoided.

Elements of Analysis Model:

1. Data Dictionary:

It is a repository that consists of a description of all data objects used or produced by the software. It stores the collection of data present in the software. It is a very crucial element of the analysis model. It acts as a centralized repository and also helps in the modeling data objects defined during software requirements.

2. Entity Relationship Diagram (ERD):

It depicts the relationship between data objects and used in conducting data modeling activity. The attributes of each object in the Entity-Relationship Diagram can be described using the Data object description. It provides the basis for activity related to data design.

3. Data Flow Diagram (DFD):

It depicts the functions that transform data flow and it also shows how data is transformed when moving from input to output. It provides additional information that is used during the analysis of the information domain and serves as a basis for the modeling of function. It also enables the engineer to develop models of functional and information domains at the same time.

4. State Transition Diagram:

It shows various modes of behavior (states) of the system and also shows the transitions from one state to another state in the system. It also provides details of how the system behaves due to the consequences of external events. It represents the behavior of a system by presenting its states and the events that cause the system to change state. It also describes what actions are taken due to the occurrence of a particular event.

5. Process Specification:

It stores the description of each function present in the data flow diagram. It describes the input to a function, the algorithm that is applied for the transformation of input, and the output that is produced. It also shows regulations and barriers imposed on the performance characteristics that are applicable to the process and layout constraints that could influence the way in which the process will be implemented.

6. Control Specification:

It stores additional information about the control aspects of the software. It is used to indicate how the software behaves when an event occurs and which processes are invoked due to the occurrence of the event. It also provides the details of the processes which are executed to manage events.

7. Data Object Description:

It stores and provides complete knowledge about a data object present and used in the software. It also gives us the details of the attributes of the data object present in the Entity Relationship Diagram. Hence, it incorporates all the data objects and their attributes.