Unit 3

Structured Analysis and Structured

Design (SA/SD)
Jackson Structured Development (JSD)
 Organization of this lecture
• Introduction to SA/SD
• Elements of Structured Analysis and Design
• Phases of SA/SD
• Jackson structured Development
 Introduction
• Object oriented design is a method where developers think in
terms of objects instead of procedures or functions.
• Structured Analysis and Structured Design (SA/SD) is
diagrammatic notation which is design to help people
understand the system. The basic goal of SA/SD is to improve
quality and reduce the risk of System failure. It establishes
concrete management specification and documentation.
• Basically the approach of SA/SD is based on the Data Flow
Diagram.
• SA/SD technique can be used to perform high level design.
• SA/SD methodology consists of two distinct activities:
 Structured Analysis (SA)
 Structured Design (SD)
 Structured analysis
• Transforms a textual problem description into a graphic
model.
• done using data flow diagrams (DFDs).
• DFDs graphically represent the results of structured analysis.
 Structured design
• All the functions represented in the DFD:
• mapped to a module structure.
• The module structure:
• also called as the software architecture:
 Structured Analysis vs.
Structured Design
• Purpose of structured analysis:
• capture the detailed structure of the system as the user
views it.
• Purpose of structured design:
• arrive at a form that is suitable for implementation in
some programming language.
Elements of Structured Analysis
and Design
 Essential Model
• Model of what the system must do
• Doesn’t define how the system is accomplish its purpose.
• It is a combination of environmental and behavioral model.
 Environmental Model
• Defines the scope of the proposed system
• Defines the boundary and interaction between the system and
outside world.
• Composed of : Statement of purpose, Context diagram etc.
 Behavioral Model
• Model of the internal behavior and data entities of the system
• Models the functional requirements
• Composed of Data dictionary, DFD, ER diagram etc.
 Implementation Model
• Maps the functional requirements to the hardware and
software .
• Tools: Structure chart
 SA/SD
• SA/SD is diagrammatic notation which is design to
help people understand the system.
• The basic goal of SA/SD is to improve quality and
reduce the risk of System failure.
• It establishes concrete management specification and
documentation. It focuses on reliability, flexibility
and maintainability of system.
• In this system it involves 2 phases.
– Analysis Phase: It uses DFD, Data Dictionary,
StateTransition diagram and ER diagram.
– Design Phase: Structure Chart, Pseudo Code
 SA/SD
• Analysis Phase:
– Data Flow Diagram: In a DFD model describe how the
data flows through the system.
– It is a technique developed by Larry Constantine to express
the requirements of system in a graphical form.
 SA/SD
– Data Dictionary: The content that is missing from DFD is
described in the data dictionary. Data Dictionary defines
the Data store and there relevant meaning.
– A data dictionary is a structured repository of data
elements in the system. It stores the descriptions of all
DFD data elements that is, details and definitions of data
flows, data stores, data stored in data stores, and the
processes.
Sr.No. Data Name Description No. of
Characters
1 ISBN ISBN Number 10
2 TITLE title 60
3 SUB Book Subjects 80
4 ANAME Author Name 15
 SA/SD
– State Transition Diagrams is similar to Dynamic model .It
specifies how much time function will take to execute and
data access triggered by events.
 SA/SD
• ER Diagram: It specifies the relationship between data store
 SA/SD
• Design Phase: Structure Chart, Pseudo Code
– Structure Chart: It is created by the DFD. Structure Chart
specifies how DFD‟s processes are grouped in to task and
allocate to CPU‟s.
– Pseudo Code: Actual implementation of the System.
– A pseudo code does not conform to any programming language and
expresses logic in plain English.
• It may specify the physical programming logic without actual coding
during and after the physical design.
• It is used in conjunction with structured programming.
• It replaces the flowcharts of a program.
Jackson Structured Development
(JSD)
• JSD was introduced by Michael Jackson in 1983.
• The fundamental principle of JSD is that it focuses on
describing the real world by the system i.e. its main focus is to
map the progress in the real world rather than specifying the
functions performed by the system i.e its main focus is to map
the progress in the real world.
• It is a methodology to specify and design systems in which
time factor is significant and system may be described using
sequence of events.
 Phases of JSD
• JSD consist of three stages or phases:
1. Modeling Phase
2. Specification Phase
3. Implementation phase
 Modeling Phase
• In the modeling phase of JSD the designer creates a collection
of entity structure diagrams and identifies the entities in the
system, the actions they perform, the attributes of the actions
and time ordering of the actions in the life of the entities.
 Specification Phase
• This phase focuses on actually what is to be done? Previous
phase provides the basic for this phase. An sufficient model of
a time-ordered world must itself be time-ordered. Major goal
is to map progress in the real world on progress in the system
that models it.
 Implementation phase
• In the implementation phase JSD determines how to obtain the
required functionality. Implementation way of the system is
based on transformation of specification into efficient set of
processes. The processes involved in it should be designed in
such a manner that it would be possible to run them on
available software and hardware.
 Principles of JSD's work
• JSD method lets describe and model the real world, not
specifies and not structures the function performed by the
system.
• The time-ordered world must be time-ordered itself, JSD
depicts the progress in the real world that models it.
• The implementation of the system is based on transformation
of specification into efficient set of processes.
 Steps for JSD Software
development
• Initially there were six steps when it was originally presented by Jackson,
they were as below:
• Entity action step: Developer list the entities and their actions
• Entity structure step: actions of each entity are partially ordered with
reference to time.
• Initial Model step: connection between entity and real world is shown.
• Function step: focuses on functions that system being developed will
provide to its end users.
• System timing step: focuses on performance constraints
• System implementation step: focuses on process scheduling and allocates
the number of processors required. The process may be different form the
processors
 Steps for JSD Software
development
Later, some steps are combined to create a method with only three
steps:
1. Modeling Stage(Analysis)
 Action step
 Structure step
2. Network stage(Design)
 initial model step
 function step
 System timing step
3. Implementation stage(Realisation)
 System implementation
 Advantages of JSD
• Specially design to handle real time problems
• JSD considers concurrent processing and timing
• JSD modeling focuses on time
• It provides functionality in real world
• Excellent functionality for micro code application
 Disadvantages of JSD
• JSD is a poor approach for high level analysis and database
design
• More complex due to pseudo code representation
• Complex and difficult to understand
• Less graphically oriented than SA/SD