Chapter 3

System Analysis and Design

3.0 System Design:

System design is the process of defining the architecture, interfaces, and data for a system that
satisfies specific requirements. System design meets the needs of your business or organization
through coherent and efficient systems.

3.1 Data Flow Diagram (DFD)

A data-flow diagram is a way of representing a flow of data through a process or a system

(usually an information system). The DFD also provides information about the outputs and
inputs of each entity and the process itself. A data-flow diagram has no control flow, there are
no decision rules and no loops. Specific operations based on the data can be represented by a
flowchart.

Data-flow diagrams (DFD) quickly became a popular way to visualize the major steps and data
involved in software-system processes. DFDs were usually used to show data flow in a
computer system, although they could in theory be applied to business process modeling. DFDs
were useful to document the major data flows or to explore a new high-level design in terms
of data flow.

DFD components:

DFD consists of processes, flows, warehouses, and terminators. There are several ways to view
these DFD components.

Process:

The process (function, transformation) is part of a system that

transforms inputs to outputs. The symbol of a process is a
circle, an oval, a rectangle, or a rectangle with rounded corners
(according to the type of notation).

The process is named in one word, a short sentence, or a

phrase that is clearly to express its essence.
Data flow:

Data flow (flow, dataflow) shows the transfer of information (sometimes also material) from
one part of the system to another. The symbol of the flow is the arrow. The flow should have
a name that determines what information (or what material) is being moved. Exceptions are
flows where it is clear what information is transferred through the entities that are linked to
these flows. Material shifts are modeled in systems that are not merely informative. Flow
should only transmit one type of information (material). The arrow shows the flow direction
(it can also be bi-directional if the information to/from the entity is logically dependent on
question and answer). Flows link processes, warehouses, and terminators.

Warehouse:

The warehouse (datastore, data store, file, database) is used to store data for later use. The
symbol of the store is two horizontal lines, the other way of view is shown in the DFD Notation.
The name of the warehouse is a plural noun (orders)—it derives from the input and output
streams of the warehouse. The warehouse does not have to be just a data file but can also be,
for example, a folder with documents, a filing cabinet, or a set of optical discs. Therefore,
viewing the warehouse in a DFD is independent of implementation. The flow from the
warehouse usually represents reading of the data stored in the warehouse, and the flow to the
warehouse usually expresses data entry or updating (sometimes also deleting data). The
warehouse is represented by two parallel lines between which the memory name is located (it
can be modeled as a UML buffer node).

Terminator (Entity):

The terminator is an external entity that communicates with the system and stands outside of
the system. It can be, for example, various organizations (a bank), groups of people
(customers), authorities (a tax office) or a department (a human-resources department) of the
same organization, which does not belong to the model system. The terminator may be another
system with which the modeled system communicates.

3
System Overview
View user list.

Admin

Users Registration
Process

Users

Search, insert and

upload autism
information and
details.

Healthcare
provider Send help request.

Search for healthcare

provider.

Add, update and

delete autism
information and
details.
(User) login DFD

This DFD shows the process of logging in to the system by the users such as parents as a user
of the system and use the system services.

5
Admin Data Flow Diagram

In the following Administrator Data Flow diagram, the pathways of Data are demonstrated will
information related to the process. Here, basic activities of admin have been shown in our
system. And we can see this in the following DFD:
3.2 Data Dictionary:

The data dictionary contains the logical structure for the information in a database. It includes
a description of each relation (table or file) and each piece of information in each relation. A
data dictionary is a collection of descriptions of the data objects or items in a data model for
the benefit of programmers and others who need to refer to them. The dictionary gives a brief
description of the objects that will be needed to form the online problem tracking management
system.

A database is an organized collection of data. A relational database, more restrictively, is a

collection of schemas, tables, queries, reports, views, and other elements. Database designers
typically organize the data to model aspects of reality in a way that supports processes requiring
information, such as (for example) modelling the availability of rooms in hotels in a way that
supports finding a hotel with vacancies.

A database-management system (DBMS) is a computer-software application that interacts with

end-users, other applications, and the database itself to capture and analyze data. A general-
purpose DBMS allows the definition, creation, querying, update, and administration of
databases.

Admin Table:

Field Type Key

Admin _ ID Varchar (50) PRI

Admin_username Varchar (50)

Admin _Password Varchar (20)

7
Autism Information Table:

Field Type Key

Id Varchar (50) PRI

Autism Details Varchar

Healthcare Varchar (100)

provider

Login Table:

Field Type Key

Login _ID int(100) PRI

Login_Username Varchar (100)

Password Varchar (20)

Users Table:

Field Type Key

User _No Int (50) PRI

User _Name Varchar (100)

Username Varchar (50)

User password Varchar (10)

User _ phone Char (11)

User _Email Varchar (50)

Healthcare Providers Table:

Field Type Key

Healthcare _No Int (50) PRI

Healthcare _Name Varchar (100)

Username Varchar (50)

User password Varchar (10)

Healthcare _ phone Char (11)

Healthcare _Email Varchar (50)

Help Request Table:

Field name type (Size ) Key

Request _id Int (50) PRI

Request _Title varchar (100)

Request _Start date Date

Request _End date Date

Feedback Table:

Field name type (Size ) Key

Feedback _id Int(50) PRI

Feedback _Title Varchar (100)

Feedback _ date Date

9
3.3 Input Design and output Design:

In practice, most design inputs are requirements, and thus the terms are used interchangeably.
Technically, we’d say a design input is any information, including requirements, that the design
team uses as an input when performing their system design process. The results of the design
process are design outputs.

The major inputs and outputs of the system are as follows:

Design input:

If a product that is in the market has issues, odds are the issue can be traced back to the design
inputs defined during product development .Design inputs are the foundation of system
development, and your system is only as effective as the inputs used to create it. Well
established design inputs can make the rest of system development easier as a result. Once
you’ve defined design inputs, you are ready to engage in core development. In my opinion, this
is one of the most enjoyable aspects of system development.

Design input is the starting point for system design. The requirements which form the design
input establish a basis for performing subsequent design tasks and validating the design.
Therefore, development of a solid foundation of requirements is the single most important
design control activity.
The objectives of input design are:

Your goals when defining design inputs include:

• Capturing all functional, performance, safety, and regulatory requirements.

• Build upon user needs and intended use.

• Make sure design inputs are clear and objective.

• State design inputs in a way that allow you to prove / disprove them.

Design outputs:

A design output is a drawing or specification or manufacturing instruction. Design outputs

describe all the components, parts, and pieces that go into your system. Design outputs describe
all assemblies and subassemblies of your system.

Design outputs established during system development become the basis of the device master
record (DMR) when in production. Design outputs describe all the ingredients that go into your
system. These could include drawings, components, materials, parts, pieces, specifications,
manufacturing instructions, and inspection procedures.

The design of output is the most important task of any system. During output design, developers
identify the type of outputs needed, and consider the necessary output controls and prototype
report layouts.

The objectives of input design are:

▪ To develop output design that serves the intended purpose and eliminates the
production of unwanted output.

▪ To develop the output design that meets the end users' requirements.

▪ To deliver the appropriate quantity of output.

▪ To form the output in appropriate format and direct it to the right person.

▪ To make the output available on time for making good decisions.

11