Chapter VIII: System Design

Chapter VIII
System Design
 Chapter VIII: System Design

8.1 System Model

The system model as a result of the system modelling that describes and will represent
the system. A system comprises multiple views such as planning, analysis, design,
implementation, deployment, structure, behaviour of input and output data views.
The system model describes and represents the multiple views that possibly will use
different approaches. The first one is in the non-architectural approach and the second one is
architectural approach.

 The non-architectural approach picks a model for each view.

For example:
- SSADM (Structural Systems Analysis and Design Method)
- SC (Structure Chart)
- DFD (Data Flow Diagram)
 The architectural approach, instead of picking heterogeneous and unrelated
models, we will use one single coalescence model.
For example:
- System Architecture
- ADL (Architecture Description Language)
 Chapter VIII: System Design

8.2 Hierarchical Input Output Process (HIPO)

 Chapter VIII: System Design

8.3 Context Diagram

 Chapter VIII: System Design

8.4 Data Flow Diagram

 Chapter VIII: System Design

8.5 Entity Relationship Diagram

 Chapter VIII: System Design

8.6 Use Case Specification

8.6.1 Use Case
In Software Engineering, use case is a list of actions or event steps typically in
regarding to define the interactions between a role to be known in the Unified Modelling
Language as an actor and a system that need to achieve a goal. The actor can be a human or
another external system. In System Engineering, use cases are used at a higher level than within
Software Engineering often representing missions or stakeholder goals. The detailed
requirements may then be captured in the Systems Modelling Language (SysML).
 Chapter VIII: System Design
8.6.2 Actors
ACTORS ROLES
Admin/Manager The one who will manage all
the transactions of each
modules or forms and the
main function of the
system. Also the one who
can access the system
commonly like add, delete,
edit, update and view all the
records and reports.
Clerk Also the one who can
manage and monitor the
system. The one who will
check of the customers if he
pay or not.
8.6.3 Administrator/Manager Use Case Diagram
Fig. 8.6.3.1 Administrator/Manager Use Case Diagram
SYSTEM RESPONSE
 Allow to access
different modules of
the system.
 The server as the
security authorized
personnel that can
login the system.
 The one who can
perform all of the
necessary
functionalities or the
transaction of the
system.
 The one who describes
the process in which
the user’s login into
the system. It may also
sets up access of
permissions for various
categories of user.
 Allow to access module
of the system such as
the view and monitor
of the system.
 Chapter VIII: System Design

Fig. 8.6.3.2 Clerk Use Case Diagram

8.6.4 Use Case Model

8.7 Sequence Diagram

8.8 Activity Diagram

8.9 Class Diagram

 Chapter VIII: System Design

8.10 System Interface

 Chapter VIII: System Design

PAYMENT FORM
8.11 Program Design Approach
When the designs are done, it’s time to insert or input the codes. The programmer and
the System Analyst will work together to achieve the company’s goal in satisfying the clients.
The codes are written in Visual Studio using Vb.net and My Sql is used in database.

8.12 Structure Chart

8.13 Input Output Process Chart

8.14 Flow Chart

Fig. 8.14.1 Data flow for user login
 Chapter VIII: System Design

8.15 List of Algorithm

Login Form
1. Start
2. Input username
3. Input password
4. Forgot password
5. End