SDD Student4u

Student4U
Table of Contents
1.0 Introduction 2
1.1 Intended Audiences and Intended Use 2
2.0 Data Flow Diagram (DFD) 3

2.1 Context Diagram 3
2.2 Diagram 0 4
2.3 Data Dictionary of DFD 5
3.0 Data Modeling 22

3.1 Entity Relationship Diagram (ERD) 22
3.2 Data Dictionary of ERD 23
4.0 Operating Overview 26
5.0 Interface Design 28

5.1Interface Flows 28
5.2 Interface Sketches 30
References 43
Appendixes 44
Confidential Page 1 of 46
Student4U
1. Introduction
This document contains a design description of the Student4U. This includes the system design,
database design and interface design. The followings are the section that will be covered in this
document:
i. Intended Audiences and Intended UseD

ii. Data Flow Diagram (DFD)
iii. Data Modeling
iv. Operating Overview
v. Interface Design
1.1 Intended Audiences and Intended Use
The intended audiences of this document are:

● System Developers
● UiTM Segamat Student Representatives Council (MPP)
They use this document for:

● To provide the description of the design of the system to the stakeholders and system
developers to follow includes the Data Flow Diagram, Entity Relational Diagram and
User Interface wireframe.
● To describe the basis of the system design will be built to meet the set of technical
requirements to the system developers.
● To provide the scope of the work required for the project to be completed to the
stakeholders and system developers.
Student4U
2. Data Flow Diagram (DFD)

2.1 Context Diagram
Student4U
2.2 Diagram 0
Student4U
2.3 Data Dictionary of DFD
i. Documenting the Processes
Process Number : 1
Process Name / Label : REGISTER INTO THE SYSTEM
Process Description : Process to register new MPP members or new
students by the MPP members or students to be
stored in MPP DATA and STUDENT DATA data
store
Process Number : 2
Process Name / Label : LOG INTO THE SYSTEM
Process Description : Process to log the user either MPP members or
students into the system
Process Number : 3
Process Name / Label : CREATE COMPLAINT
Process Description : Process for students to create any complaint that will
be stored in COMPLAINT data store
Process Number : 4
Process Name / Label : VIEW SELF-PROPOSED COMPLAINT
Process Description : Process for students to view their self-proposed
complaint that have been stored in the COMPLAINT
data store
Student4U
Process Number : 5
Process Name / Label : DELETE COMPLAINT
Process Description : Process for students to delete their submitted
complaint from the COMPLAINT data store
Process Number : 6
Process Name / Label : VIEW STUDENT’S COMPLAINT
Process Description : Process for MPP members to view all of the student’s
complaints that have been stored in the
COMPLAINT data store
Process Number : 7
Process Name / Label : RESPONSE TO STUDENT’S COMPLAINT
Process Description : Process for MPP members to response to the
students’ complaints that have been stored in the
COMPLAINT data store with any comments
Process Number : 8
Process Name / Label : SUBMIT PAPERWORK
Process Description : Process for club committee to submit their paperwork
that will be stored in the PAPERWORK data store
Student4U
Process Number : 9
Process Name / Label : VIEW SELF-PROPOSED PAPERWORK
Process Description : Process for club committee to view their
self-proposed paperwork that have been stored in the
PAPERWORK data store
Process Number : 10
Process Name / Label : DELETE PAPERWORK
Process Description : Process for club committee to delete their submitted
paperwork that have been stored in the
Process Number : 11
Process Name / Label : RESPONSE TO SUBMITTED PAPERWORK
Process Description : Process for MPP members to response to the
submitted paperworks that have been stored in the
PAPERWORK data store with any comments
Process Number : 12
Process Name / Label : REGISTER CLUB
Process Description : Process for MPP members to register new club into
the system that will be stored in the CLUB data store
Student4U
Process Number : 13
Process Name / Label : DELETE CLUB
Process Description : Process for MPP members to delete any selected club
that have been stored in the CLUB data store
Process Number : 14
Process Name / Label : VIEW CLUB LIST
Process Description : Process for MPP members to view the club list from
the CLUB data store
Student4U
ii. Documenting the Entities
Entity Name : MPP

Alternate Name : MPP members
Description : People who manage the system and all of the
information stored in the system data stores
Input Data Flows : ● Complaint details
● Club details
Output Data Flows : ● MPP details
● MPP log details
● Complaint response
● Paperwork response
● Club details
● Clu
Entity Name : STUDENT

Alternate Name : Normal Students
Description : People who want to propose any complaint
Input Data Flows : ● Complaint details
Output Data Flows : ● Student details
● Student log details
● Complaint details
Entity Name : STUDENT

Alternate Name : Club committee members
Description : People who want to submit paperwork for approval
Input Data Flows : ● Paperwork details
Output Data Flows : ● Student details
● Student log details
● Paperwork details
Student4U
iii. Documenting the Data Flows
Data Flow Name / Label : MPP details

Alternate Name : -
Description : MPP members will key in the new MPP members to
be registered into the system
Origin : MPP entity
Destination : REGISTER INTO THE SYSTEM process
Volume and Frequency : Approximately 20 members per year
Data Flow Name / Label : MPP details

Alternate Name : -
Description : The new MPP members details will be stored in the
MPP DATA data store
Origin : REGISTER INTO THE SYSTEM process
Destination : MPP DATA data store
Volume and Frequency : Approximately 20 members per year
Data Flow Name / Label : Student details

Alternate Name : -
Description : Students will key in the personal details to be
registered into the system
Origin : STUDENT entity
Destination : REGISTER INTO THE SYSTEM process
Volume and Frequency : Approximately 50 per week
Student4U
Data Flow Name / Label : Student details

Alternate Name : -
Description : The new students’ personal details will be stored in
the STUDENT DATA data store
Origin : REGISTER INTO THE SYSTEM process
Destination : STUDENT DATA data store
Data Flow Name / Label : MPP log details

Alternate Name : -
Description : MPP members will key in their log details to log into
the system
Origin : MPP entity
Destination : LOG INTO THE SYSTEM process
Volume and Frequency : Approximately 10 per day
Data Flow Name / Label : MPP log details

Alternate Name : -
Description : The log details of MPP members will be checked in
the MPP DATA data store to verified
Origin : LOG INTO THE SYSTEM process
Destination : MPP DATA data store
Student4U
Data Flow Name / Label : Student log details

Alternate Name : -
Description : Students will key in their log details to log into the
system
Destination : LOG INTO THE SYSTEM process
Data Flow Name / Label : Student log details

Alternate Name : -
Description : The log details of students will be checked in the
STUDENT DATA data store to verified
Origin : LOG INTO THE SYSTEM process
Destination : STUDENT DATA data store
Data Flow Name / Label : Complaint details

Alternate Name : -
Description : Student will create a complaint
Destination : CREATE COMPLAINT process
Student4U

Alternate Name : -
Description : Students’ complaint will be stored in the
Origin : CREATE COMPLAINT process
Destination : COMPLAINT data store

Alternate Name : -
Description : Student’s complaint details will be taken from the
COMPLAINT data store to be shown to the student
Origin : COMPLAINT data store
Destination : VIEW SELF-PROPOSED COMPLAINT process

Alternate Name : -
Description : Student’s complaint details will be shown to the
student
Origin : VIEW SELF-PROPOSED COMPLAINT process
Destination : STUDENT entity
Student4U

Alternate Name : -
Description : Student will key in their selected complaint to be
deleted
Destination : DELETE COMPLAINT process

Alternate Name : -
Description : Selected complaint will be deleted from the
Origin : DELETE COMPLAINT process

Alternate Name : -
Description : Students’ complaint details will be taken from the
COMPLAINT data store to be shown to the MPP
members
Origin : COMPLAINT data store
Destination : VIEW STUDENT’S COMPLAINT
Student4U

Alternate Name : -
Description : Student’s complaint details will be shown to the MPP
members
Origin : VIEW STUDENT’S COMPLAINT process
Destination : MPP entity
Data Flow Name / Label : Complaint response

Alternate Name : -
Description : MPP members will response the complaints with any
comments
Origin : MPP entity
Destination : RESPONSE TO STUDENT’S COMPLAINT
process
Data Flow Name / Label : Complaint response

Alternate Name : -
Description : The response and comments will be stored in the
Origin : MPP entity
Student4U
Data Flow Name / Label : Paperwork details

Alternate Name : -
Description : Club committee members will submit their
paperwork to the system
Destination : SUBMIT PAPERWORK process

Alternate Name : -
Description : The paperwork submitted will be stored in the
Origin : SUBMIT PAPERWORK process
Destination : PAPERWORK data store

Alternate Name : -
Description : The paperwork details will be taken from the
PAPERWORK data store to be shown to the student
Origin : PAPERWORK data store
Destination : VIEW SELF-PROPOSED PAPERWORK process
Student4U

Alternate Name : -
Description : The paperwork details will be shown to the student
Origin : VIEW SELF-PROPOSED PAPERWORK process
Destination : STUDENT entity

Alternate Name : -
Description : Student will key in their selected paperwork to be
deleted
Destination : DELETE COMPLAINT
Volume and Frequency : Approximately 5 per month

Alternate Name : -
Description : The selected paperwork will be deleted from the
Origin : DELETE PAPERWORK process
Volume and Frequency : Approximately 5 per month
Student4U
Data Flow Name / Label : Paperwork response

Alternate Name : -
Description : MPP members will response with any comments on
the submitted paperwork
Origin : MPP entity
Destination : RESPONSE TO SUBMITTED PAPERWORK
process
Data Flow Name / Label : Paperwork response

Alternate Name : -
Description : The response and comments will be stored in the
Origin : RESPONSE TO SUBMITTED PAPERWORK
process
Data Flow Name / Label : Club details

Alternate Name : -
Description : MPP members will key in new club details to be
registered into the system
Origin : MPP entity
Destination : REGISTER CLUB process
Volume and Frequency : If necessary
Student4U

Alternate Name : -
Description : The new club details will be store in the CLUB data
store
Origin : REGISTER CLUB process
Destination : CLUB data store

Alternate Name : -
Description : MPP members will key in the selected club to be
deleted
Origin : MPP entity
Destination : DELETE CLUB process

Alternate Name : -
Description : The selected club will be deleted from the CLUB
data store
Origin : DELETE CLUB process
Destination : CLUB data store
Student4U

Alternate Name : -
Description : The club list details will be taken from the CLUB
data store to be shown to the MPP members
Origin : CLUB data store
Destination : VIEW CLUB LIST process

Alternate Name : -
Description : The club list details will be shown to the MPP
members
Origin : VIEW CLUB LIST process
Destination : MPP entity
Student4U
iv. Documenting the Data Stores
Data Flow Number : D1

Data Store Name : MPP DATA
Description : Store all MPP members personal details

Data Store Name : STUDENT DATA
Description : Store all registered students’ personal details

Data Store Name : COMPLAINT
Description : Store complaints details

Data Store Name : PAPERWORK
Description : Store paperwork submissions details

Data Store Name : CLUB
Description : Store all club details
Student4U
3. Data Modeling
3.1 Entity Relationship Diagram (ERD)
Student4U
3.2 Data Dictionary of ERD
Student4U
Student4U
Student4U
4. Operating Overview
To develop this system, the equivalent specification that is required for software is http
server which uses Apache version 2.4.46, DBMS phpMyAdmin version 5.2.0 and Xampp
version 7.4.29. All the servers may run in OS Windows Servers 2022 operating system. For the
end-user, the minimum requirement for software is it may run on OS Windows 7 / 8.1 / 10 / 11.
As for the hardware, the minimum requirement for the server may run in Intel Xeon with 8GB
RAM, 120GB SSD storage for server storage. Lastly the minimum requirement of hardware for
end-users is free 100MB hard drive space, 4GB RAM and also need Android Marshmallow 6.0
or later for the mobile version.
Minimum System Requirements:
1) Software
● Server:
a) OS: Windows Server 2022
Resolution: 1024x768.
b) Http server: Apache
Version: 2.4.46 (latest)
c) DBMS: phpMyAdmin
Version: 5.2.0
d) Web Server Solution: Xampp
Version: 7.4.29
Student4U
● End-User:
a) OS: Windows 7 / 8.1 / 10 / 11
Resolution: 1024x768
2) Hardware
● Server:
a) CPU: Intel xeon
RAM: 8GB
Storage ssd: 120GB
GPU: Nvidia Quadro Q600
● End-User:
a) Minimum spec to run Chrome using PC:
Free hard drive space: 100MB
RAM: 4GB
b) Minimum specs to run Chrome using phone: Android Marshmallow 6.0 or later
Student4U
5. Interface Design
5.1 Interface Flows
This is the interface flow that we used to develop the Student4U system. The registration
is used by the existing MPP members to register for other MPP members. Students can also
register themselves into the system. Once the user logs into the system, it will redirect the user
based on its role. The user may log into the system either as an MPP member or as a student.
Under the MPP section, there will be another two sections which are the complaint section and
paperwork submission section. For the complaint section, the MPP member may view the
complaints proposed by the students and respond to them with any appropriate comments. As for
the paperwork submission section, the MPP member can view the paperwork submitted by the
club committee members, respond to the paperwork submitted, register a new club name, view
the club list, and delete any club from the list.
For the student’s section, there are also two sections which also include the complaint
section and paperwork submission section. For the complaint section, the student may create any
complaint to be proposed to the MPP members and view their self-proposed complaint. They are
also allowed to delete the complaint which has already been submitted but has not been approved
by the MPP members yet. Lastly, in the paperwork submission section, the student may submit
their paperwork for approval from the MPP members, view the paperwork that they already
submitted, and delete the paperwork from submission that has not been processed or responded
yet.
Student4U
Student4U
5.2 Interface Sketches
Firstly, users need to log in by entering their username and their respective password or if
they do not have an account yet they will be redirected to the Sign Up page which is the
registration section. After the registration and login process have been done by the users, there
will be two scenarios.
Student4U
Scenario 1
For the first scenario, the user is one of the MPP members, so their homepage will
display some information and there will be navigators to go to the Complaint, Paperwork and
Others page.
Student4U
If the MPP member goes to the Complaint page there will be several features that allow
them to view complaints that have been submitted by the students or respond to the complaints.
Date and Status of the complaint also will be displayed.
Student4U
When the MPP member chooses to edit the response, the page will turn to Edit Complaint
Response. So the user can take any necessary action whether to approve or reject a complaint,
they can also include comments in their response.
Student4U
While, if the MPP member goes to the Paperwork page, there will be options to view and
respond to the paperwork. Besides, there are also navigators for register club and view club list.
Date and Status of the paperwork also displayed.
Student4U
Next, if the MPP member chooses to Edit Paperwork Response, the page is almost the
same as Edit Complaint Response but in this page, MPP members can return a file if they want,
for example return file for correction.
Student4U
Scenario 2
For the second scenario, the user is an ordinary student or a club committee member, so
their homepage is about the same as the MPP’s Home page except it will display their course
instead of roles in MPP. There will be navigators to go to the Complaint, Paperwork and Others
page.
Student4U
If the student goes to the Complaint page, the interface is slightly different than MPP
members’ Complaint page where they have navigators for View and Delete complaints. Not to
forget, it also has a button to create a new complaint.
Student4U
After that, if the user wants to make a new complaint, they will have to click the button
and they will be directed to this page where they will be needed to fill in the form completely
and they can choose to be recorded anonymously or not using the check box. By clicking the
Confirm button means that they are submitting their complaint.
Student4U
While, if the user wishes to view the details of their status, the Complaint Response page
will display the details including comments from MPP members and they just need to use the
Back button if they want to go back to the Complaint page.
Student4U
In addition, the Paperwork page for students has Submit, View and Delete navigators.
Date and status also will be displayed in the table.
Student4U
Furthermore, when the user wants to submit Paperwork then they will need to fill in the
form same as in the complaint form previously. The only difference is they will have to upload
the paperwork files which will be reviewed by the MPP members.
Student4U
Later, if the user wants to view the response of their paperwork, the Paperwork Response
page will display all the details including the returned file and comments from the MPP member.
Student4U
References
Book:
● Scott Tilley, Harry J. Rosenblatt (2017). Systems Analysis and Design, Eleventh Edition.
United States of America: Cengage Learning.
Human:
● Putri Elisa binti Ishak, Yang Dipertua Majlis Perwakilan Pelajar UiTM Cawangan Johor.
Date interview: 22th of April 2022
● Muhammad Firdaus bin Mohamed, Setiausaha Agung Majlis Perwakilan Pelajar UiTM
Cawangan Johor.
● Nur Rasyidah binti Abu Mansor, Bendahari Kehormat Majlis Perwakilan Pelajar UiTM
Cawangan Johor.
Website:
● Interface
Bootstrap AdminLTE admin panel user interface.
Link: https://adminlte.io/
● User Interface Flow Sample

UiTM Student management system (UFuture)
Link: https://ufuture.uitm.edu.my
● User Interface Flow Sample

WireframePro - HR Management App
Link:
https://wireframepro.mockflow.com/view/MoDmh4k3Emb#/page/4c26125f1c784783958
5b293d949344a
Student4U
Appendixes
figure 1: Xampp Web Server Solution
figure 2: phpMyAdmin RDBMS
Student4U
figure 3: AdminLTE Bootstrap admin panel template

SDD Student4u

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SDD Student4u

Uploaded by

Copyright:

Available Formats

Student4U

2.0 Data Flow Diagram (DFD) 3

3.0 Data Modeling 22

4.0 Operating Overview 26

5.0 Interface Design 28

i. Intended Audiences and Intended UseD

1.1 Intended Audiences and Intended Use

The intended audiences of this document are:

They use this document for:

2. Data Flow Diagram (DFD)

2.3 Data Dictionary of DFD

i. Documenting the Processes

ii. Documenting the Entities

Entity Name : MPP

Entity Name : STUDENT

Entity Name : STUDENT

iii. Documenting the Data Flows

Data Flow Name / Label : MPP details

Data Flow Name / Label : MPP details

Data Flow Name / Label : Student details

Data Flow Name / Label : Student details

Data Flow Name / Label : MPP log details

Data Flow Name / Label : MPP log details

Data Flow Name / Label : Student log details

Data Flow Name / Label : Student log details

Data Flow Name / Label : Complaint details

Data Flow Name / Label : Complaint details

Data Flow Name / Label : Complaint details

Data Flow Name / Label : Complaint details

Data Flow Name / Label : Complaint details

Data Flow Name / Label : Complaint details

Data Flow Name / Label : Complaint details

Data Flow Name / Label : Complaint details

Data Flow Name / Label : Complaint response

Data Flow Name / Label : Complaint response

Data Flow Name / Label : Paperwork details

Data Flow Name / Label : Paperwork details

Data Flow Name / Label : Paperwork details

Data Flow Name / Label : Paperwork details

Data Flow Name / Label : Paperwork details

Data Flow Name / Label : Paperwork details

Data Flow Name / Label : Paperwork response

Data Flow Name / Label : Paperwork response

Data Flow Name / Label : Club details

Data Flow Name / Label : Club details

Data Flow Name / Label : Club details

Data Flow Name / Label : Club details

Data Flow Name / Label : Club details

Data Flow Name / Label : Club details

iv. Documenting the Data Stores

Data Flow Number : D1

Data Flow Number : D2

Data Flow Number : D3

Data Flow Number : D4

Data Flow Number : D5

3.2 Data Dictionary of ERD

Minimum System Requirements:

a) OS: Windows Server 2022

b) Http server: Apache

Version: 2.4.46 (latest)

d) Web Server Solution: Xampp

a) OS: Windows 7 / 8.1 / 10 / 11