Scribd
Upload
63 views20 pages

CSC 214 Week4

This course covers structured analysis, tools for structured analysis such as data flow diagrams, data dictionaries, decision trees, decision tables, structured English, and pseudocode. At the end of the course, students will be expected to understand structured analysis, how to use tools for structured analysis, and system design.

Uploaded by

Ayomide
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
63 views20 pages

CSC 214 Week4

This course covers structured analysis, tools for structured analysis such as data flow diagrams, data dictionaries, decision trees, decision tables, structured English, and pseudocode. At the end of the course, students will be expected to understand structured analysis, how to use tools for structured analysis, and system design.

Uploaded by

Ayomide
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/ 20

CSC 214: SYSTEM ANALYSIS AND

DESIGN
Intended Learning Outcome:

At the end of this course, students are expected to


 Structured Analysis
 Tools for Structured Analysis
 System Design.
THIS LECTURE
What is Structured Analysis
• Development method that allows the analyst to understand the system and its
activities in a logical way.
• It is a systematic approach, which uses graphical tools that analyze and refine the
objectives of an existing system and develop a new system specification which can
be easily understandable by user.
It has following attributes:
It is graphic which specifies the presentation of application.
It divides the processes so that it gives a clear picture of system flow.
It is logical rather than physical i.e., the elements of system do not depend
on vendor or hardware.
It is an approach that works from high-level overviews to lower-level details.
Structured Analysis Tools

THIS LECTURE
• Data Flow Diagrams
• Data Dictionary
• Decision Trees
• Decision Tables
• Structured English
• Pseudocode
Structured Analysis
THIS LECTURE
Data Flow Diagrams (DFD) or Bubble
Chart

THIS LECTURE
• It is a technique developed by Larry Constantine to express the requirements of system in a graphical
form.
• It shows the flow of data between various functions of system and specifies how the current system is
implemented.

• It is an initial stage of design phase that functionally divides the requirement specifications down to the
lowest level of detail.

• Its graphical nature makes it a good communication tool between user and analyst or analyst and system
designer.

• It gives an overview of what data a system processes, what transformations are performed, what data are
stored, what results are produced and where they flow.
Basic Elements of DFD
Types of DFD
Context Diagram
• A context diagram helps in understanding the entire system by one DFD
which gives the overview of a system
Data Dictionary
• is a structured repository of data elements in the system

• A data dictionary improves the communication between the analyst


and the user
Decision Trees
• Decision trees are a method for defining complex relationships by describing decisions and
avoiding the problems in communication.
• A decision tree is a diagram that shows alternative actions and conditions within horizontal
tree framework.
• It depicts which conditions to consider first, second, and so on
• Decision trees depict the relationship of each condition and their permissible actions.
• A square node indicates an action and a circle indicates a condition.
• The major limitation of a decision tree is that it lacks information in its format to describe
what other combinations of conditions you can take for testing

THIS LECTURE
Decision Tables
Decision tables are a method of describing the complex logical relationship in a
precise manner which is easily understandable.

• It is useful in situations where the resulting actions depend on the


occurrence of one or several combinations of independent conditions.
• It is a matrix containing row or columns for defining a problem and the
actions.

THIS LECTURE
Components of a Decision Table
• Condition Stub: It is in the upper left quadrant which lists all the condition to
be checked.
• Action stub: It is in the lower left quadrant which outlines all the action to be
carried out to meet such condition.
• Condition Entry: It is in upper right quadrant which provides answers to
questions asked in condition stub quadrant.
• Action Entry: It is in lower right quadrant which indicates the appropriate
action resulting from the answers to the conditions in the condition entry
quadrant.
Decision Rules
• Y shows the existence of a condition.
• N represents the condition, which is not satisfied.
• A blank - against action states it is to be ignored.
• X (or a check mark will do) against action states it is to be carried out.
Structured English
Structure English is derived from structured programming language which gives
THIS LECTURE
more understandable and precise description of process.

It is based on procedural logic that uses construction and imperative sentences


designed to perform operation for action.

• It is best used when sequences and loops in a program must be considered


and the problem needs sequences of actions with decisions.
• It does not have strict syntax rule. It expresses all logic in terms of
sequential decision structures and iterations
Pseudocode
• A pseudocode 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.

THIS LECTURE
Guidelines for Selecting Appropriate Tools

• Use DFD at high or low level analysis for providing good system documentations.

• Use data dictionary to simplify the structure for meeting the data requirement of the system.

• Use structured English if there are many loops and actions are complex.

• Use decision tables when there are a large number of conditions to check and logic is complex.

• Use decision trees when sequencing of conditions is important and if there are few conditions to
be tested.
System Design
how to implement?
System design is the phase that bridges the gap between problem domain and the existing system
in a manageable way.
It is the phase where the SRS document is converted into a format that can be implemented and
decides how the system will operate.
 Inputs to System Design
 Outputs for System Design
Types of System Design
• Logical Design = abstract representation of the data flow.
• Physical Design = actual input and output processes of the system.
• Architectural Design = design of system architecture.
• Detailed Design = Architectural design and focuses on development of each module

THIS LECTURE

You might also like