Chapter 3 Design

Chapter 3

Design

Hiring process of Poulvet Trading’s Page | 1

Chapter 3 Design

3.1 Data Flow Diagram

Data-flow diagrams (DFDs) model a perspective of the system that is most readily understood
by users – the flow of information through the system and the activities that process this
information.

Data-flow diagrams provide a graphical representation of the system that aims to be accessible
to computer specialist and non-specialist users alike. The models enable software engineers,
customers and users to work together effectively during the analysis and specification of
requirements. Although this means that our customers are required to understand the modeling
techniques and constructs, in data-flow modeling only a limited set of constructs are used, and
the rules applied are designed to be simple and easy to follow. These same rules and constructs
apply to all data-flow diagrams (i.e., for each of the different software process activities in
which DFDs can be used)

3.1.1 Data Flow Diagram Level 0

A Context Flow Diagram is 0th level DFD. It only contains one process node that
generalizes the functions of the entire system in relationship to external entities. In
Context Flow Diagram the entire system is treated as a single process and all its input,
output sinks and source are identified and shown.

Figure 1 – DFD Level 0

Hiring process of Poulvet Trading’s Page | 2

Chapter 3 Design

3.1.2 Data Flow Diagram Level 1

The Level 1 DFD shows how the system is divided into sub-systems (processes), each
of which deals with one or more of the data flows to or from an external agent, and which
together provide all of the functionality of the system as a whole.

Figure 2 – DFD Level 1

3.1.3 Data Flow Diagram Level 2

A level 2 data flow diagram (DFD) offers a more detailed look at the processes that make
up an information system than a level 1 DFD does. It can be used to plan or record the
specific makeup of a system.

Hiring process of Poulvet Trading’s Page | 3

Chapter 3 Design

Figure 3 – DFD Level 2

3.2 Use Case Diagrams

The main ingredients for this type of diagram are use cases and actors, respectively the roles
that users can take towards a system. It is often used in early stages of design process to collect
the intentional requirements of a project. This diagram shows the overall functionality of the
system.

Use Case diagrams show the interaction between use cases, which represent system
functionality, and actors, which represent the people or systems that provide or receive
information from the system. Use cases represent the requirements of the system from the
user’s perspective. Therefore, use cases are the functionality that the system provides. Actors
are the administrator and the user of the system.

Hiring process of Poulvet Trading’s Page | 4

Chapter 3 Design

3.2.1 Use Case diagram for Admin:

Figure 4 – Use Case Diagram (Admin)

Hiring process of Poulvet Trading’s Page | 5

Chapter 3 Design

3.2.2 Use case diagram for HM:

Figure 5 – Use Case Diagram (HM)

Hiring process of Poulvet Trading’s Page | 6

Chapter 3 Design

3.2.3 Use case diagram for Applicant:

Figure 6 – Use Case Diagram (Applicant);

3.3 Sequence Diagrams

A sequence diagram is an interaction diagram. From the name, it is clear that the diagram deals
with some sequences, which are the sequence of messages flowing from one object to another.
Interaction among the components of a system is very important from implementation and
execution perspective. So Sequence diagram is used to visualize the sequence of calls in a
system to perform a specific functionality.

Hiring process of Poulvet Trading’s Page | 7

Chapter 3 Design

3.3.1 Sequence Diagram for Admin:

Figure 7 – UML Diagram (Admin Panel);

3.3.2 Sequence Diagram for HM:

Figure 8 – UML Diagram (HM Panel);

Hiring process of Poulvet Trading’s Page | 8

Chapter 3 Design

3.3.3 Sequence Diagram for Applicant:

Figure 9 – UML Diagram (Applicant Panel);

1.4 Class diagram

A class diagram in the Unified Modeling Language(UML) is a type of static structure
diagram that describes the structure of a system by showing the system's classes, their
attributes, operations (or methods), and the relationships among objects.

There are three classifications of UML diagrams:

3.4.1 Behavior diagrams

A type of diagram that depicts behavioral features of a system or business process. This
includes activity, state machine, and use case diagrams as well as the four interaction diagrams.

3.4.2 Interaction diagrams

A subset of behavior diagrams which emphasize object interactions. This includes

communication, interaction overview, sequence, and timing diagrams.

3.4.3 Structure diagrams

A type of diagram that depicts the elements of a specification that are irrespective of time. This
includes class, composite structure, component, deployment, object, and package diagrams.

Hiring process of Poulvet Trading’s Page | 9

Chapter 3 Design

Figure 10 – Class Diagram

1.5 ERD (Entity Relationship Diagram)

Simply stated the ER model is a conceptual data model that views the real world as entities and
relationships. A basic component of the model is the Entity-Relationship diagram, which is
used to visually represent data objects. The utility of the ER model is:

 It is simple and easy to understand. Therefore, the database designer to communicate

the design to the end user can use the model.
 In addition, the model can be used as a design plan by the database developer to
implement a data model in a specific database management software.

Database

Hiring process of Poulvet Trading’s Page | 10

Chapter 3 Design

Hiring process of Poulvet Trading’s Page | 11