Systems design is simple the design of
systems. It implies a systematic and rigorous
approach to design -- an approach demanded
by the scale and complexity of many system
Is the third of the five stages of Systems
Development Life Cycle (SDLC).
To develop a logical model of the system and
considered various development strategies.
To create a blueprint that will satisfy all
documented requirements for the system. At
this stage, the user interface will be designed
and all the necessary outputs, inputs, and
processes will be identified.
A flow chart is a graphical or symbolic
representation -- This diagrammatic
representation can give a step-by-step
solution to a given problem -- of a process,
showing the steps as boxes of various kinds,
and their order by connecting these with
Flowcharts are used in analyzing, designing,
documenting or managing a process or
program in various fields.
Each step in the process is represented by a
different symbol and contains a short
description of the process step. All processes
should flow from top to bottom and left to
Start and End symbol
Represented as circles,
ovals or rounded
containing the word
"Start" or "End", or
signaling the start or
end of a process, such
as "submit enquiry" or
Showing "flow of
An arrow coming from
one symbol and ending
at another symbol
represents that control
passes to the symbol
the arrow points to.
Generic Processing Symbol
Denotes the process to
be carried out
Examples: "Add 1 to X";
part"; "save changes"
Add 1 to X
Represented as a
Denotes an input
operation or output
Examples: Get X from
the user; display X.
Conditional or Decision
Represented as a diamond
showing where a decision
is necessary, commonly a
Yes/No question or
The conditional symbol is
peculiar in that it has two
arrows coming out of it,
usually from the bottom
point and right point, one
corresponding to Yes or
True, No or False.
Is x =>
Represented by an
identifying label inside
Labeled connectors are
used in complex or
to substitute for
Showing controls over a document-flow through a
Showing controls over a data flows in a system
Showing controls at a physical or resource level
Showing the controls in a program within a
A high-level (also called first-level or top-down)
flowchart shows the major steps in a process.
It illustrates a "birds-eye view" of a process.
It can also include the intermediate outputs of
each step (the product or service produced), and
the sub-steps involved.
The detailed flowchart provides a detailed picture
of a process by mapping all of the steps and
activities that occur in the process.
This type of flowchart indicates the steps or
activities of a process and includes such things as
decision points, waiting periods, tasks that
frequently must be redone (rework), and feedback
Deployment or Matrix Flowchart
A deployment flowchart maps out the process in
terms of who is doing the steps.
It is in the form of a matrix, showing the various
participants and the flow of steps among these
It is chiefly useful in identifying who is providing
inputs or services to whom, as well as areas where
different people may be needlessly doing the
Data Flow Diagram (DFD) is a graphical
representation of the "flow" of data through
an information system, modeling
its process aspects.
DFDs can also be used for the visualization
of data processing (structured design).
Often they are a preliminary step used to
create an overview of the system which can
later be elaborated.
A DFD shows what kinds of data will be input
to and output from the system, where the
data will come from and go to, and where the
data will be stored.
It does not show information about the
timing of processes, or information about
whether processes will operate in sequence
or in parallel.
In software engineering and systems
engineering, a Context Diagram is a diagram
that represents the actors outside a system
that could interact with that system.
A context diagram is a data flow diagram,
with only one massive central process that
subsumes everything inside the scope of the
It shows how the system will receive and send
data flows to the external entities involved.
Context Diagram is the highest level view of a
Context Diagrams shows a system, often
software-based, as a whole and its inputs and
outputs from/to external factors.
It is similar to a Block diagram.
A Gantt chart is a graphical representation of the
duration of tasks against the progression of time.
A Gantt chart is a useful tool for planning and
Gantt charts illustrate the start and finish dates
of the terminal elements and summary elements
of a project.
Terminal elements and summary elements
comprise the work breakdown structure of the
Some Gantt charts also show the dependency
relationships between activities.
A Gantt chart is a horizontal bar chart developed
as a production control tool in 1917 by Henry L.
Gantt, an American engineer and social scientist.