0% found this document useful (0 votes)
42 views16 pages

Structures Analysis and Design SAD

The document discusses Structures Analysis and Design (SAD), focusing on software modeling techniques including Structured Analysis and Object Oriented Analysis. It outlines the importance of creating models to represent system requirements, processes, and data, and describes various modeling techniques such as Data Flow Diagrams (DFDs) and Unified Modeling Language (UML). Additionally, it covers behavioral models like data-driven and event-driven modeling to illustrate system behavior in response to stimuli.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
42 views16 pages

Structures Analysis and Design SAD

The document discusses Structures Analysis and Design (SAD), focusing on software modeling techniques including Structured Analysis and Object Oriented Analysis. It outlines the importance of creating models to represent system requirements, processes, and data, and describes various modeling techniques such as Data Flow Diagrams (DFDs) and Unified Modeling Language (UML). Additionally, it covers behavioral models like data-driven and event-driven modeling to illustrate system behavior in response to stimuli.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 16

Structures Analysis and Design

SAD

1
Software process model

Requirements Design and


Validation Evolution
Specification Implementation

2
Modeling

A model is an abstract view of a system


We create a model to gain better understanding
of an entity, for example a model of a plane is a
small plane.
When the entity is software, the model takes a
different form.

3
A software Model

A software model must be capable of


representing :
▪ the information that the software transforms,
▪ the functions that enable the transformation to occur,
and
▪ the behavior of the system as the transformation
takes place.
Two types of software modeling (requirements):
▪ Structured model
▪ Object oriented model
4
Structured Analysis Vs. Object Oriented
Modeling

 Structured Analysis and Object Oriented Analysis are different techniques


of developing a computer system.
 Structured analysis: the focus is only on process and procedures.
Modeling techniques used in it are DFD(Data Flow Diagram), Flowcharts
etc.
 Object oriented analysis: the focus is more on capturing the real world
objects in the current scenario that are of importance to the system. It
stresses more on data structure and less on procedural structure.
Modeling techniques used in it are UML(Unified modeling Language),
that can present both structural and behavioral/procedural aspect of the
system. UML includes Class Diagram, State Diagram, Use case diagram,
Sequence Diagram, etc.

Chapter 5 System modeling 5


Structured analysis and design

 Analysis
▪ Determine system requirements
▪ Structuring system process requirements
▪ Logical requirements (logical modeling)
▪ Structuring system data requirements
 Design
▪ Database design (DB normalization)
▪ Forms and report design (GUI design)

Chapter 5 System modeling 6


Analysis: Structured analysis and design

 Determine system requirements:


▪ Interviewing individuals and/or group
 Structuring system process requirements
▪ Data flow diagrams (DFD) - process modeling
▪ Context diagram
▪ Process decomposition (DFD levels): 4 types of DFD:
• Current physical: adequate detail only
• Current logical: enables analysts to understand current system
• New logical: technology independent, show data flows, structure,
and functional requirements of new system.
• New physical: technology dependent.
▪ Logical modeling: using structured English, decision table/tree
▪ Structuring system data requirements: using ER diagram
Chapter 5 System modeling 7
DFD symbols

Chapter 5 System modeling 8


Context diagram

Chapter 5 System modeling 9


Level-0 diagram

Chapter 5 System modeling 10


Behavioral models
A- Data-driven modeling – Activity diagram

 Behavioral models are models of the dynamic behavior of a system


as it is executing. They show what happens or what is supposed to
happen when a system responds to a stimulus from its environment.
 Many business systems are data-processing systems that are
primarily driven by data. They are controlled by the data input to the
system, with relatively little external event processing.
 Data-driven models show the sequence of actions involved in
processing input data and generating an associated output.
 They are particularly useful during the analysis of requirements as
they can be used to show end-to-end processing in a system.

11
Data-driven modeling

 Data flow diagrams (DFDs) may be used to model the


system’s data processing.
 These show the processing steps as data flows through
a system.
 UML does not support DFDs . UML use activity diagram
instead.

12
Ex: An activity model of the insulin pump’s
operation

13
Behavioral models
B- Event-driven modeling - State diagram

 Event-driven modeling shows how a system responds to


external and internal events.

14
Ex: State diagram of a microwave oven

15
16

You might also like