Structured Analysis and Structured Design (SA/SD)

Structured Analysis and Structured Design (SA/SD) is a diagrammatic notation that is

SA/SD is combined known as SAD and it mainly focuses on the following 3 points: 
 
1. System 
2. Process 
3. Technology 
 
SA/SD involves 2 phases:  
1. Analysis Phase: It uses Data Flow Diagram, Data Dictionary, State Transition
diagram and ER diagram. 
2. Design Phase: It uses Structure Chart and Pseudo Code. 
 
1. Analysis Phase: 
Analysis Phase involves data flow diagram, data dictionary, state transition diagram, and
entity-relationship diagram. 
1. Data Flow Diagram: 
In the data flow diagram, the model describes how the data flows through the
system. We can incorporate the Boolean operators and & or link data flow when
more than one data flow may be input or output from a process. 
For example, if we have to choose between two paths of a process we can add an
operator or and if two data flows are necessary for a process we can add an
operator. The input of the process “check-order” needs the credit information and
order information whereas the output of the process would be a cash-order or a
good-credit-order. 
 
2. Data Dictionary: 
The content that is not described in the DFD is described in the data dictionary. It
defines the data store and relevant meaning. A physical data dictionary for data
elements that flow between processes, between entities, and between processes
and entities may be included. This would also include descriptions of data
elements that flow external to the data stores. 
A logical data dictionary may also be included for each such data element. All
system names, whether they are names of entities, types, relations, attributes, or
services, should be entered in the dictionary. 
 
3. State Transition Diagram: 
State transition diagram is similar to the dynamic model. It specifies how much
time the function will take to execute and data access triggered by events. It also
 describes all of the states that an object can have, the events under which an object
changes state, the conditions that must be fulfilled before the transition will occur
and the activities were undertaken during the life of an object. 
 
4. ER Diagram: 
ER diagram specifies the relationship between data store. It is basically used in
database design. It basically describes the relationship between different entities. 
 
2. Design Phase: 
Design Phase involves structure chart and pseudocode.  
1. Structure Chart: 
It is created by the data flow diagram. Structure Chart specifies how DFS’s
processes are grouped into tasks and allocate to the CPU. The structured chart
does not show the working and internal structure of the processes or modules and
does not show the relationship between data or data-flows. Similar to other SASD
tools, it is time and cost-independent and there is no error-checking technique
associated with this tool. 
The modules of a structured chart are arranged arbitrarily and any process from a
DFD can be chosen as the central transform depending on the analysts’ own
perception. The structured chart is difficult to amend, verify, maintain, and check
for completeness and consistency. 
 
2. Pseudo Code: 
It is the actual implementation of the system. It is an informal way of
programming that doesn’t require any specific programming language or
technology.

Behavioral Modeling
Overall behavior of a system can be fully understood by Behavioral model.
Behavioral Model is specially designed to make us understand behavior and factors that
influence behavior of a System. Behavior of a system is explained and represented with the
help of a diagram. This diagram is known as State Transition Diagram. It is a collection of
states and events. It usually describes overall states that a system can have and events which
are responsible for a change in state of a system.
So, on some occurrence of a particular event, an action is taken and what action needs to be
taken is represented by State Transition Diagram.
The Control Specifications (CSPEC) is used to indicate (1) how the software behaves when
an event or control signal is sensed and (2) which processes are invoked as a consequence of
the occurrence of the event. The control specification (CSPEC) contains a number of
important modeling tools.

The control specification represents the behavior of the system in two ways. The CSPEC
contains a state transition diagram that is sequential specification of behavior. It also contains
a process activation table (PAT) -a combinatorial specification of behavior.
Example :
Consider an Elevator. This elevator is for n number of floors and has n number of buttons one
for each floor.
Elevator’s working can be explained as follows :
1. Elevator buttons are type of set of buttons which is there on elevator. For
reaching a particular floor you want to visit, “elevator buttons” for that particular
floor is pressed. Pressing, will cause illumination and elevator will start moving
towards that particular floor for which you pressed “elevator buttons”. As soon as
elevator reaches that particular floor,
illumination gets canceled.
2. Floor buttons are another type of set of buttons on elevator. If a person is on a
particular floor and he wants to go on another floor, then elevator button for that
floor is pressed. Then, process will be same as given above. Pressing, will cause
illumination and elevator to start moving, and when it reaches on desired floor,
illumination gets canceled.
3. When there is no request for elevator, it remains closed on current floor.
State Transition Diagram for an elevator system is shown below –
Advantages :
● Behavior and working of a system can easily be understood without any effort.
● Results are more accurate by using this model.
● This model requires less cost for development as cost of resources can be
minimal.
● It focuses on behavior of a system rather than theories.
Disadvantages :
● This model does not have any theory, so trainee is not able to fully understand
basic principle and major concept of modeling.
● This modeling cannot be fully automated.
● Sometimes, it’s not easy to understand overall result.
● Does not achieve maximum productivity due to some technical issues or any
errors.