Scribd
Upload
13 views2 pages

2.12 Analysis Modeling

Uploaded by

benita.a
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
13 views2 pages

2.12 Analysis Modeling

Uploaded by

benita.a
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

DEPARTMENT NAME:MASTER OF COMPUTER APPLICATIONS

Class: I MCA Batch: 2023-2025


Course code:23CAR206 Course Title: OBJECT ORIENTED SOFT-
WARE ENGINEERING

UNIT II PLANNING AND SCHEDULING 9


Planning & Scheduling: Software prototyping – Software project planning – Scope – Resources
– Software Estimation – Empirical Estimation Models – Planning – Risk Management –
Software Project Scheduling – Object Oriented Estimation & Scheduling. Analysis and Design:
Analysis Modeling – Data Modeling – Functional Modeling & Information Flow – Behavioral
Modeling – Structured Analysis – Object Oriented Analysis – Domain Analysis.

2.12 Analysis Modeling

Analysis Model is a technical representation of the system. It acts as a link between the system
description and the design model. In Analysis Modelling, information, behavior, and functions of the
system are defined and translated into the architecture, component, and interface level design in the
design modeling.

Objectives of Analysis Modeling:

 It must establish a way of creating software design.

 It must describe the requirements of the customer.

 It must define a set of requirements that can be validated, once the software is built.

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 modeling data objects
defined during software requirements.

2. Entity Relationship Diagram (ERD):


It depicts the relationship between data objects and is used in conducting data modeling
activities. The attributes of each object in the Entity-Relationship Diagram can be described

Prepared By: A.BENITA Page 1


DEPARTMENT NAME:MASTER OF COMPUTER APPLICATIONS
Class: I MCA Batch: 2023-2025
Course code:23CAR206 Course Title: OBJECT ORIENTED SOFT-
WARE ENGINEERING

using 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 the additional information which 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 the 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 attributes of the data object present in the Entity
Relationship Diagram. Hence, it incorporates all the data objects and their attributes.

Prepared By: A.BENITA Page 2

You might also like