Student Registration System-Final Report

STUDENT REGISTRATION SYSTEM
FINAL REPORT
COURSE: SOFTWARE ENGINEERING
Fall 2019
CLASS: MONDAY MORNING (LABORATORY)
SATURDAY MORNING (THEORY)
INSTRUCTOR: Ms. N.T.T.LOAN
Member:
Trịnh Minh Đăng ITITIU16022
Nguyễn Đức Phi Hồng ITITIU17022
Võ Huy Thành ITITIU17026
OUTLINE
A. PROJECT PLAN
I. OVERVIEW
II. GOALS & SCOPE
III. ORGANIZATION
IV. RESOURCE REQUIREMENTS
V. SCHEDULE
VI. RISK MANAGEMENT
VII. DELIVERY PLAN
VIII. SECURITY ASPECTS
IX. ABBREVIATIONS AND DEFINITIONS
X. REFERENCES
B. REQUIREMENT
I. INTRODUCTION
II. GLOSSARY
III. USECASE AND USERSTORY
IV. FUNCTIONAL REQUIREMENTS
V. NON-FUNCTIONAL REQUIREMENTS
C. DESIGN
I. SYSTEM ARCHITECTURE
II. ERD
III. CLASS DIAGRAM
IV. SEQUENCE DIAGRAM
V. ACTIVITY DIAGRAM
D. USER MANUAL
I. INSTALL MANUAL
II. USER MANUAL
III. TEST CASE
A. PROJECT PLAN
I. OVERVIEW
1.1 About Us
Tech World is a company specializing in developing software and web application.
We focus on creating the products with high quality in design, functionality, and
performance. Our customers range from small to medium enterprises, development
partners.
Company Name: SE Team

Team Name: SE Team
Business: - Develop software
- Develop and design web application
Customer: Ms. N.T.T.LOAN
Office: International University, Quarter 6, Linh Trung Ward,
Thu Duc District, HCM City
Email: shiuxing123@gmail.com
Phone: (+083) 7300 909 (Mr Hong)
1.2. Product’s Information

Student Registration System is a vital part of any university’s running because
students are what keep a university alive. A poor system can mean fewer students
being admitted into a university because of mistakes or an overly slow response
time.
Student Registration System is the software which is helpful for students as
well as the department. In this project, we are facilitated by the system for
registration students, add subjects and fee structure. Our Student Registration
System helps deal with the various activities related to the students
Aside from the costs for hardware resources and domain server used to
develop and run the system, which our team decides to take care of by ourselves,
we intend to distribute the final product absolute free for everyone. Any donations
from the community are strongly appreciated but are not required. “We believe in
what people make possible. Our mission is to empower every person and every
organization on the planet to achieve more” is our slogan.
Our early approximation:
The First Day of the Construction: 26th September 2019.
The Last Day of the Construction: 28th December 2019.
Time
Duration: approximately 3 months.
Delivery
Demonstration Date: 4nd January 2019
To implement this project, our team is going to need an amount

of budget. This amount is separated into three kinds: hardware
budget, software budget and human budget.
- Hardware budget: $3325
- Software budget: $440
Budget
- Human budget: $2000
- Additional budget: $1000
- Total cost estimated: $5765
The detail cost will be present in section Resource Requirement
II. GOALS AND SCOPES

Priority: 1 – Highest 5 – Lowest
2.1. Project Goals
PROJECT GOALS PRIORITY DESCRIPTION
FUNCTIONAL GOALS
All documents should be clear, easy to
1. Requirement
1 understand and collected from all stakeholder
Specification
The User Interface of final system should be
2. UI Design
1 simple, well-organized and convenience.
3. Implementation All functions must be clear, maintainable and

2
flexible.
Testing phase should be included testing plan and
4. Testing
3 testing the whole system with test cases, make
sure paying attention into the result of process.
STRATEGIC GOALS
System shall be able to achieve and maintain
1. Customer services
1 outstanding services for users
System shall attract many users and make a well-

2. Popularity
1 known status in the Internet community
BUSINESS GOALS
The final product shall be delivered within 3
1. Released time
2 months from first day of the development process.
The final system (Online Retail Application) shall

be delivered to users with the appropriate price.
2. Cost Additionally, we also charge for advertisements
2
from other organizations and use that profit to
cover the cost of running the system.
3. Market growth The final product shall produce significant growth

3
in the market.
TECHNOLOGICAL GOALS
System shall deliver standard functions for Online
1. Basic functions
1 Retail Application.
2. Future System shall leave rooms for future improvement

enhancement 2 (can implement new functions)
QUALITY GOALS
System shall be able to execute all the
1. Functions
implemented functions smoothly, free of
execution 1
errors.
2. Response time System shall be able to respond to user within an

2
acceptable amount of time.
System shall display its components in an
3. System interface organized and well-formatted way; clearly and
1
easy to use.
ORGANIZATIONAL GOALS
1.Competence System shall be designed and implemented so that
development 2 it is able to compete with the top product in the
market.
System shall be developed such that it is easy to
2. Maintenance
3 be maintained.
3. New technologies System shall be able to adapt to new technologies.

4
4. Modern tools Up-to-date tools and technologies shall be used to
exploitation 4 develop the whole system.
CONSTRAINTS
1. Environment System shall be able to access by multi-platform
constraints 2 devices.
2. Application System shall satisfy most common standard rules

standards 1 of a web application.
3. National and System shall not be illegal

3
cultural standards
2.2. Project Scope

Customer classifications:
1. Unprivileged user: Student
2. Privileged users: Admin
2.2.1. Included
Due to time and human constrains, our final project can only provide some
standard functions that is typical for the Student Registration System:
- Register function (Register account).
- Authentication function (Login/Logout function).
- Allow student to enroll for course.
- Allow student to view enrolled course
- Allow student to delete course from list.
- Allow student to view their profile
- Allow student to edit their profile
- Allow admin/student to edit their password
- Allow admin to add/edit course.
- Allow admin to view student profile.
- Allow admin to add/edit student profile.
- Allow admin to view enroll history.
2.2.2. Excluded
There are some functions our group decided to exclude from the project but may
intrigue customers will be left for future improvements, including:
- Allow student to make payment.
- Allow student to contact admins.
- Allow student to receive their password when they forget it.
- Allow student to search for specific course
- Allow student to create their account that does not depend on the
acceptation of admins
III. ORGANIZATION
3.1. Organizational Boundaries and Interfaces

The project is built on a web-based platform and can be accessed by every device
that has internet connection. And since this is only a project developed for the
university’s course, the stakeholders are the members that work on this project.
All the resources used in this project belong to the team member. The final product
will be received by the internet users. This project is free to use by anyone that has
interest in it. Nevertheless, any commercial intention on this product is not
allowed.
List of suppliers for the project:
Company Product
Microsoft Corporation Microsoft Office 365
Xampp Database and web server
JetBrains Pycharm
3.2. Project Organization
Each member of the group has their own role in this project, nonetheless, we share
our work to one another. Some possess skills that’s required for specific tasks,
which will improve the product quality.
List of the team member:
Name Role Contact Email
Trịnh Minh Đăng Tester, Business
analyst
Nguyễn Đức Phi Hồng Designer, Developer +0837300909 shiuxing123@gmail
.com
Võ Huy Thành Scrum Master
IV. RESOURCE REQUIREMENTS

4.1. Hardware Resource
Name Purpose Quantity Price Total
Estimation
Asus A510 Designing/Testing 1 $725 $725
Asus GL552 Designing/Testing 1 $900 $900
Acer Aspire Designing/Testing 1 $600 $600
E5
Asus FX504 Designing/Testing 1 $1100 $1100
Total estimation of Hardware resource: $3325
4.2. Software Resource

Name Purpose Total
Quantity Price Estimation
Microsoft Documenting 4 $110 $440
Office 365
Umlet Diagram/Designing 1 Free $0
Draw.io Diagram 1 Free $0
Xampp Designing 1 Free $0
Pychram Designing Free $0
Total estimation for Software resource: $440
4.3. Human Resource

Name Skillset Time Salary per
month
Tester, Business
Trịnh Minh Đăng Full-time $500
analyst
Nguyễn Đức Phi Designer,
Full-time $1000
Hồng Developer
Võ Huy Thành Scrum Master Full-time $500
Total estimation for Human resources: $2000
V. SCHEDULE
5.1. Work Breakdown Structure
Student Registration
System
System
Course Student
Resgistration
Interaction Management
Management
Student
management
Requirement
Design IU Implement Testing
Specification
Design
Sketch relating UML Add Student Test the interface
announcement
Analyze use case

Design confirm box Search Student Test all functions
and requirement
Design main
Test the whole
funtion,algorithm View Student
website
and database used
Course Interaction
Requirement
Specification
Sketch relating Design Database

Course function management Control Function Test the interface
UML management page
Update course Test all functions

Analyze use case Design creation
Update of Course Add course and database
and requirement page
connection
Design main
Design discussion Test the whole
funtion,algorithm View of Course Delete course
page website
and database used
System registration
management
Requirement
Specification
Resgistration Modification Test respomsiveness

Sketch relating UML Design Login page Authentication
of the interface
Acount Account Resgistration

Analyze use case and function Validation testing of
Design resgister page Autheritication Edit profile
requirement login
Function
Design main Course registration Pricacy testing in

funtion,algorithm and Design home page Log in function personal information
database used and database
Log out
5.2. Schedule and Milestones

Here is the product backlog that our team comes up with after applying Scrum
Framework to the project development process:
Priority: 1- Highest
5- Lowest
Estimate
ID Sprint Date Backlog Items Priority
(week)
As an admin, I want to
Sprint 1
21/10/2019- register a student so that I
1 Register 2 1
27/10/2019 can have all student’s
account
accessibilities.
As a student and admin, I
Sprint 2
2 want to login/logout my 1
Login/Logout
account.
Sprint 3 28/10/2019- As an admin, I want to add
3 student. 1 4
Add student 3/11/2019
Sprint 4 As an admin, I want to
4/11/2019-
4 Add/edit Add/edit courses to course 3 1
10/11/2019
course list
Sprint 5 Add As a student, I want to add
11/11/2019-
5 course courses and edit/update in 2 2
17/11/2019
(Student) my registration list.
Sprint 6 18/11/2019- As a admin, I want to see
6 2 2
View student 24/11/2019 details of student.
Sprint 7 As a student, I want to see
25/11/2019-
7 View enrolled my enrolled course 2 4
1/12/2019
course
Sprint 8 As an admin, I want to see
View enrolled 2/12/2019- student’s enrolled course.
8 2 1
course 8/12/2019
(Admin)
Sprint 9 As a student, I want to
9/12/2019-
9 Change change my password. 2 2
15/12/2019
Password
Schedule and Milestones

Whole team
Designer
Tester
Sprint 1 + 2
Register account + Login/Logout (21/10/2019-27/10/2019)
Tasks Mon Tue Wed Thu Fri Sat Sun
Analyze the
requirements
and define
the concept
of the
functions
Design
interface for
registration
page
Design
interface for
Login/
Logout page
Design +
insert data
into database
Test
functions
with database
Sprint 3
Add menu (28/10/2019-3/11/2019)
Analyze the
requirements
and define the
concept of the
functions
Design
interface for
Add course
Design +
insert data
into database
Test functions
with database
Sprint 4
Add/edit course (4/11/2019-10/11/2019)
Analyze the
requirements
and define the
concept of the
functions
Design
interface for
Course
Design +
insert data
into database
Test functions
with database
Sprint 5
Update Course (Student) (11/11/2019-17/11/2019)
Analyze the
requirements
and define the
concept of the
functions
Design
interface for
enrolled
course
(Student)
Design +
insert data
into database
Test functions
with database
Sprint 6
View Student (18/11/2019-24/11/2019)
Analyze the
requirements
and define the
concept of the
functions
Design
interface for
view student
page
Design +
insert data
into database
Test functions
with database
Sprint 7
View enrolled course (25/11/2019- 1/12/2019)
Analyze the
requirements
and define the
concept of the
functions
Design
interface for
enrolled
course
(admin)
Design +
insert data
into database
Test functions
with database
Sprint 8
View enrolled course (Admin) (2/12/2019- 8/12/2019)
Analyze the
requirements
and define the
concept of the
functions
Design
interface for
view enrolled
course
Design +
insert data
into database
Test functions
with database
Sprint 9
Change Password (3/12/2019 - 9/12/2019)
Analyze the
requirements
and define the
concept of the
functions
Design
interface for
Change
password
Design +
insert data
into database
Test functions
with database
VI. RISK MANAGEMENT

When an entity makes an investment decision, it exposes itself to several financial
risks. Therefore, in order to minimize and control the exposure of investment to
such risks, we listed a list of risks that our project would likely to come across as
well as some strategy to solve those problems.
PROJECT RISKS
Risk Probability Description Strategy

When stakeholders Perform weekly meeting
Stakeholders have a negative with customer to have
fail to support Low attitude towards the their ideas about the
project project and wish to project and keep track of
see it fail. their demands.
Have a specific project’s
Inability to secure resource checklist and
Resource
Moderate sufficient resources plan some backup plan in
shortfalls
for the project. case of insufficient
resource
Have teammate prepare
Training is often a
for necessary skills as
poor substitute for
well as techniques and
professional
tools before the project
Training is experience. Projects
Moderate start executing to create a
inadequate shouldn't assume that
good product.
resources will be fully
Choosing right member
productive in a new
with suitable skills for the
skill.
project.
Have daily meeting with
team member to discuss
about the difficulty and
Low team Team members lack
High trouble that they are
motivation motivation
having and find a good
way to solve each
problem.
COMMERCIAL RISKS
Have a strategy of
advertising the product
via media and online ads
Demand risk for the to get the interest of as
Product doesn't
Moderate new product in many people as possible.
sell
market. Add some unique features
to increase the project
competitiveness among
the market.
Technology Make sure that the project
Components that fail
components Moderate is implemented with
after a short time.
aren't reliable latest technology
PRODUCT RISKS
Have some surveys about
customers’ opinions of
The user interface is
User interface is the interface and
High buggy, slow or
low quality summarize those ideas to
difficult to use.
create an optimal
interface.
Project Technical problems The project manager must
management with the project know and get use to using
Moderate
tool problems & management tools a suitable tool to develop
issues themselves. the project.
When requirements
are misinterpreted by
Revise the requirement
Project team the project team a gap
analysis phase carefully
misunderstand High develops between
before adjusting the role
requirements expectations,
of each team members.
requirements and
work packages.
VII. DELIVERY PLAN
Day Day Day Day Day Day Day Estimate

Sprint 1 & 2 Main Tanks
1 2 3 4 5 6 7 (Total hours)
User Story: As an admin, I want to register a student so that I can have all student’s
accessibilities.
User Story: As a student and admin, I want to login/logout my account.
Design UI for Register
4 2
page
Register
Design UI for Login /
account + Logout page 4 2
Login/Logout
(21/10/2019- Design use cases and class
diagrams 4 4
27/10/2019) 27
Create database to manage
data of users 3
Testing Register page 2
Testing Login /Logout
page 2

Sprint 3 Main Tanks
1 2 3 4 5 6 7 (Total hours)
User Story: As an admin, I want to add student.
Design UI for add page 5
Add menu Test functions with
database 3
(28/10/2019-
18
3/11/2019) Design use cases and class
diagrams 2 4
Testing page 2 2
Sprint 4 Main Tanks
1 2 3 4 5 6 7 (Total hours)
User Story: As an admin, I want to Add/edit courses to course list
Design UI for course 2 2 5
Add/edit Test functions with
database 2 4
course
(4/11/2019- Design use cases and class 30
diagrams 3 3 4
10/11/2019)
Create database of Course
1 1 3
Sprint 5 Day Day Day Day Day Day Day Estimate

Main Tanks
1 2 3 4 5 6 7 (Total hours)
User Story: As a student, I want to add courses and edit/update in my registration list.
Design UI for enrolled
course 2 2 4
Update
Course Test functions with
2 3
(Student) database
26
(11/11/2019- Design use cases and class
3
17/11/2019) diagrams
Create database of
3 3 4
Shopping cart

Sprint 6 Main Tanks
1 2 3 4 5 6 7 (Total hours)
User Story: As a admin, I want to see details of student..
Design UI for paying page 3 4
Create database of paying
2
View Student
(18/11/2019- Test functions with
2 2 24
24/11/2019) database
Test Order with system 1 2
Design use cases and class
diagrams 3 2 3

Sprint 7 Main Tanks
1 2 3 4 5 6 7 (Total hours)
User Story: As a student, I want to see my enrolled course.
Design UI for view
View enrolled enrolled course 4
course Create database contact
(25/11/2019- Admin 2 13
1/12/2019)
Test functions with
database 2
diagrams 2 3

Sprint 8 Main Tanks
1 2 3 4 5 6 7 (Total hours)
User Story: As an admin, I want to see students enrolled course.
Design UI for view
View enrolled enrolled course for admin 2 4
course Test functions with
(Admin) database 2 3
(2/12/2019- 18
Test product of database 1 1 1
8/12/2019)
diagrams 4

Sprint 9 Main Tanks
1 2 3 4 5 6 7 (Total hours)
User Story: As a student, I want to change my password.
Design UI for change
password 1 3
Change
Test functions with
Password 1
database
(3/12/2019 - 15
Test product of database
9/12/2019) 1

4 2 3
diagrams
VIII. SECURITY ASPECT (OPTIONAL)

Data security refers to protective digital privacy measures that are applied to
prevent unauthorized access to computers, databases and websites. Data security
also protects data from corruption. Data security is an essential aspect of IT for
organizations of every size and type.
Here are some vulnerabilities that are likely to happen to a web-based project
system:
Vulnerability Description Solution
Memory safety is the state of Uses static program analysis
Memory being protected from various and automated theorem proving
safety software bugs and security to ensure that the program is
vulnerabilities when dealing free of memory errors
with memory access, such as
buffer overflows and
dangling pointer.
An internet user can be Add static analysis (also called
tricked or forced into “white-box” testing) to your
downloading software onto a software development lifecycle
Malicious computer that is of malicious to review your code for the
software intent. Such software comes presence of malicious code
in many forms, such as Use some trusted security
viruses, Trojan horses, application to detect malicious
spyware, and worms. code.
Use runtime application self-
Applications used to access protection (RASP) technologies
Internet resources may deployed within or alongside
Application contain security the application runtime
vulnerabilities vulnerabilities such as environment that instruments an
memory safety bugs or application and enables
flawed authentication checks. detection and prevention of
attacks
Phishing is an attack which
Transaction verification and
targets online users for
signing through using mobile
extraction of their sensitive
Phishing phone as a second channel for
information such as
verification and authorization of
username, password and
banking transactions.
credit card information
IX. ABBREVIATIONS AND DEFINITIONS
WORD MEANING
UI Design User Interface Design

MySQL A freely available open source Relational Database
Management System (RDBMS) that uses Structured Query
Language (SQL)
Hardware Physical component of a computer system
Software The programs and other operating information used by a

computer.
Use case A use case is a methodology used in system analysis to

identify, clarify and organize system requirement
Product backlogs A list of all things that needs to be done within the project
Agile A group of software development methods
Scrum A lightweight process framework for agile development
Iteration The process of repeating computing process
HTML Hyper Text Markup Language - the standard markup

language for creating Web pages.
CSS The language for describing the presentation of Web pages,

including colors, layout, and fonts
Bug An error, flaw, failure or fault in a computer program or

system that causes it to produce an incorrect or unexpected
result
X. REFERENCES
1. https://continuingprofessionaldevelopment.org/risk-management-steps-in-risk-
management-process/
2. https://searchcompliance.techtarget.com/definition/risk-management
3. https://www.peterjoubert.com/resource-requirements/
4. https://www.projectinsight.net/project-management-basics/project-management-
schedule
5. https://www.liquidplanner.com/blog/back-school-special-project-management-
tips-successful-project-delivery/
6. https://www.wbdg.org/project-management
7. https://www.commonplaces.com/blog/6-common-website-security-
vulnerabilities/
8. https://www.creativebloq.com/web-design/website-security-tips-protect-your-
site-7122853
B. REQUIREMENT
I. INTRODUCTION
The Requirement Specification focuses on the introduction of the project including
the purpose, scope as well as the details of the system requirements.
Based on this requirements specification, implementation of each function
including all the conditions as well as functional and non-functional requirements,
supplied by the customers, will be made. This document helps the reader to
understand the Online Retail Web Application by providing details into the product
features.
II. GLOSSARY
Identify the actors involved in an interaction and names the

type of interaction. The additional information may be a
Use Case
textual description or one or more graphical models such as
UML sequence or state charts.
Functional Description of the system features to show how the software
Requirements operates and processes the data from the user’s input.
Non-
Standards and constraints on the functionalities of the system
functional
to meet customer’s expectation.
Requirements
III. USECASE AND USER STORIES
3.1 Use Case Diagram
3.2 Use Case Description (9 user stories)
Use case description for user story 1: As an admin, I want to register a student so
that I can have all student’s accessibilities.
- Name: Account Registration
- Identifier: UC1
- Input:
+Password
+StudentRegNo
-Output:
+If success: The successful message.
+If fail: The registration page with error message
-Pre-conditions:
+User must be in Home Page
-Basic Course:
User: Admin System
1.Open Home Page 1.1. Display Home Page
2.Click on “Registration” button in 2.1. Direct and display Registration
Home Page Page
3.Enter user’s information (include
StudentRegNo, password)
4. Click on “Sign Up” button 4.1 Check the user’s input
4.1.1. Check empty
4.1.2. Check user’s name availability
4.2. Display the successful message
-Alternative Path:
+Condition 1: StudentRegNo and password are invalid
*In step 4, if StudentRegNo and password of a customer are
invalid, the system will display an error message “Invalid
input” and prompt admin to choose a different StudentRegNo /
password or fill the empty section.
-Post-condition:
+New student’s account will be added into database.
Use case description for user story 2: As a student and admin, I want to
login/logout my account.
*Use case description 2.1: Login
-Name: Log in
-Identifier: UC2.1
-Input:
+StudentRegNo for Student or Username for Admin
+Password
-Output:
+Home page after successfully logged in.
-Pre-condition:
+User must have an account already.
-Basic course:
User: Admin and student System
2. Click on “Sign in” button 2.1 Direct and display Login Page
3. Enter StudentRegNo for Student or
Username for Admin and password
4. Click on “Login” button 4.1. Validate the input
4.2. Retrieve matching user from
database
4.3. Record the result user object to
session
4.4. Redirect user to the Home Page
-Alternative Path:
+Condition 1: Users enter invalid StudentRegNo for Student or
Username for Admin or password.
*In step 4, after validating user’s input, system displays a
warning message “Invalid Username or password” and ask
users to enter again.
-Post-condition:
+Users successfully log in.
*Use case description 2.2: Log out

-Name: Log out
-Identifier: UC2.2
-Input: None
-Output:
+Return home page after successfully logged out.
-Pre-condition:
+User has already logged in.
-Basic Course:
1.Click on “Log out” button in 1.1. Retrieve user object form session
“account” bar 1.2. Erase current user object from
session
1.3. Redirect user to the home page
-Alternative Path: None

-Post-condition:
+Users successfully log out.
Use case description for user story 3: As an admin, I want to add student.
-Name: Add student
-Identifier: UC3
-Input:
+Student‘s information
-Output:
+If success: The successful message.
+If fail: The error message
-Pre-condition:
+ User must log in as a admin
+ User must be in “Manage Student ” page
-Basic Course:
User: Admin System
1.Click on “Manage Student ” button
2.Input student‘s information
3.Press “Enter” key 3.1.Check valid input
3.2. Check empty input
3.4. Save the project info in database
-Alternative Path:
+Condition 1: User input invalid or empty input
*In step 3, display “Student Info” with error message
“Invalid Input” or “Empty input”.
-Post-condition:
+Save the project info in database
Use case description for user story 4: As an admin, I want to Add/edit courses to
course list.
-Name: Add/Edit course
-Identifier: UC4
-Input:
+Course’s name
+Course’s id
+Course’s number of seat
+Course’s fee
+Course’s time
-Output:
+ Return “Course” Page with “Save product succefful” message.
-Pre-condition:
+ User must be in “Course” page
-Basic Course:
User: Admin System
1.Click “Course” button 1.1.Display “Course” Page
2.Enter course’s information (name,
id, number of seat , fee, time)
3.Click “Save” button 3.1.Check valid input
3.2. Check empty input
3.3. Return “Course” Page with “Save
product successful” message.
3.4. Save the project info in database
-Alternative Path:
+Condition 1: User input invalid or empty input
*In step 3, display “Course Info” with error message
“Invalid Input” or “Empty input”.
-Post-condition:
+Save the project info in database
Use case description for user story 5: As a student, I want to add courses and
remove course in my registration list.
*Use case description 5.1: Add course (Student)

-Name: Add course (Student)
-Identifier: UC5
-Input: None
-Output:
+A pop-up that displays all course in the enrolled list with their
information.
-Pre-condition:
+User must be in the “Enroll for course” Page.
+User must log in already
-Basic Course:
User: Student System
1. Select course.
2. Press “Enroll” button. 2.1 Save the course in student’s enroll
history.
-Alternative Path:
+Condition 1: The course is out of seat
*In step 2, if the course is not available, display error
message”Out of Seat”.
-Post-condition:
+ Save the course in students enroll history
*Use case description 5.2: Remove course (Student)
-Name: Remove course (Student)
-Identifier: UC5.2
-Input: None
-Output:
+ Display new enroll history in “Enroll history” Page.
-Pre-condition:
+User must be in the “Enroll history” Page.
+ User must log in already
-Basic Course:
1.Press “Enroll history” button 1.1. Display “Enroll history” Page
2.Press “Delete” Button 2.1. Remove an item from “Enroll
history” Page
2.2. Update enrolled list

-Post-condition:
+ Update enrolled list.
Use case description for user story 6: As an admin, I want to see details of
student.
-Name: View student
-Identifier: UC6
-Input: None
-Output:
+All student information.
-Pre-condition:
+ User must be in “Manage Student” page
-Basic Course:
User: Admin System
1.Click on “Manage Student” button 1.1 Display all student
2.Click on “Edit” button next to a 2.1. Display all information of that
specific student student

-Post-condition:
+All student’s information are listed out.
Use case description for user story 7: As a student, I want to see my enrolled
course
-Name: View enrolled course (Student)
-Identifier: UC7
-Input: None
-Output:
+All enrolled course information.
-Pre-condition:
+ User must log in as a student
+ User must be in “Enroll history” page
-Basic Course:
1.Click on “Enroll history” button 1.1 Display enrolled course.

-Post-condition:
+All enrolled course of that student are listed out.
Use case description for user story 8: As an admin, I want to see student’s
enrolled course.
-Name: View enrolled course (Admin)
-Identifier: UC8
-Input: None
-Output:
+All enrolled course information of all student.
-Pre-condition:
+ User must be in “Enroll history” page
-Basic Course:
User: Admin System
1.Click on “Enroll history” button 1.1 Display enrolled course of all
student.

-Post-condition:
+All student’s enrolled course are listed out.
Use case description for user story 9: As a student and admin, I want to change
my password.
-Name: Change password
-Identifier: UC9
-Input:
+Old password
+New password
-Output:
+Home page after successfully logged in.
-Pre-condition:
+User must have an account already.
-Basic course:
2. Click on “Change password” 2.1 Direct and display “Change
button password” Page
3. Enter old password , new
password and confirm password
4. Click on “Submit” button 4.1 Check the user’s input
4.1.1. Check empty
-Alternative Path:
+Condition 1: Users enter invalid old password.
*In step 4, after validating user’s input, system displays a
warning message “Invalid password” and ask users to enter
again.
-Post-condition:
+ New user’s password will be added into database.
IV. FUNCTIONAL REQUIREMENTS

UC1: Account Registration
- Shall display a page that require the user to information such as name, year, and
department.
- Shall check the name, StudentRegNo and password.
- Shall save the user’s registration information in database if successfully sign
up.
- Shall check for the existed account in the database
UC2: Login/Logout
- Shall display Username and password bar for the user to sign in.
- Shall check the user’s input with the database.
- Shall notify the user if login successfully or failed.
- Shall redirect the user to the home page if login successfully.
- Shall display the logout icon in the user’s expansion menu if the user has
logged in.
- Shall close all the user’s accessibilities after the user has logged out.
- Shall redirect user back to the homepage after the user has logged out
successfully.
UC3: Add student
- Shall display the “Manage Student” button in the homepage.
- Shall allow the user to type in the information bars.
- Shall save the student information in database.
UC4: Add/Edit course
- Shall allow admin to modify course
- Shall save all changes made by admin to the database
UC5: Add course (Student)
- Shall display the “Course” button in the homepage.
- Shall check if the course is still have enough seat in the database, else it’s
unable to add.
- Shall save the course the user added to the enroll history and in the database.
- Shall display the “Delete” button for the user to remove undesired course.
UC6: View student
- Shall display the list of student.
- Shall display the student’s information in the list of students.
- Shall display the “Delete” button for the user to remove undesired student.
UC7: View enrolled course (Student)
- Shall display the list of enrolled course.
- Shall display the course’s information the list of enrolled course.
- Shall display the “Delete” button for the user to remove undesired course.
UC8: View enrolled course (Admin)
- Shall display the list of enrolled course of all student.
- Shall display the course’s information in the list of enrolled course.
UC9: Change password
- Shall display the “Change password” button.
- Shall allow customer to enter their new password.
- Shall check for the user old password to allow the “submit” button to be
clicked.
- Shall save the user’s new registration information in database if successfully
change password.
V. NON-FUNCTIONAL REQUIREMENTS
#1 Environment
Summary The system is built upon a reliable

environment which must both be
stable and upgradable.
Rationale Developing a website requires a
stable environment for securing both
the user and the developer. Lack of
stability may affect customer’s trust
thus reduce the profit from the
website. The environment also needs
to be frequently updated for future
improvement.
Requirements The system is developed based on
Xampp.
Database: using MySQL database.
#2 Security
Summary All external communications between
the system’s data server and clients
must be encrypted
Rationale Only registered user can use the
system. Any attack from the outsiders
will be prevented to ensure security.
Requirements Security provided by Xampp.
#3 Understandability
Summary Website UI needs to be simple, easy
to use.
Rationale As there are more customer register,
the system must be simple for
different types of user.
Requirements Minimalist design: The UI appears
easy to look at without tons of
information, while still being
understandable by the user.
#4 Usability
Summary An interface should be easy to learn
how to use and easy to remember how
to use
Rationale Information must be presented in a
clear way that users should not be
required to consult a manual for
items.
Requirements Efficiency of use: goals are easy to
accomplish quickly and with few or
no user errors.
Intuitiveness: the interface is easy to
learn and navigate.
Low perceived workload: the
interface appears easy to use, rather
than intimidating, demanding and
frustrating.
#5 Reliability
Summary The product’s data must be full and
must not return any inaccurate result.
Rationale To provide the user with reliable and
detail information about the product.
Inaccurate data might lead to
misunderstanding in product’s
quality.
Requirements Contact information visible on
website
Accuracy of the search query result
must be ensured.
#6 Stability
Summary The system must be stable in order to
deal with user’s growth.
Rationale When the website becomes popular,
there will be more people register.
Thus, the website must be stable and
maintain the loading speed to ensure
the user experience.
Requirements Database must be simple, sufficient
and upgradable.
#7 Supportability
Summary Developer must reply any questions
from the user as soon as possible.
Rationale When the user wants to contact the
administrator or the administrator
want to contact the development
team, the website must provide a
method that is quick and reliable for
better communication.
Requirements A contact page for the user to ask for
support.
C.DESIGN
I. SYSTEM ARCHITECTURE
II. ERD
III. CLASS DIAGRAM
IV. SEQUENCE DIAGRAM
UC2: LOGIN / LOGOUT
UC2.1: Log in
UC2.2: Log out
UC3: View student

UC5: Add /Remove course (Student)
UC5.1: Add course (Student)
UC5.2: Remove course (Student)
UC6: Edit student

V. ACTIVITY DIAGRAM
UC2: LOGIN / LOGOUT
UC2.1: Log in
UC2.2: Log out
UC3: View student

UC5: Add /Remove course (Student)
UC5.1: Add course (Student)
UC5.2: Remove course (Student)
UC6: Edit student

D.USER MANUAL
I. INSTALL MANUAL
Installation Steps (Configuration)
1. Download XAMPP
2. Put “onlinecourse” file inside root directory (htdocs folder in xampp folder)
3.Open XAMPP
4.Start XAMPP MySQL and Apache
5. Database Configuration
Database Configuration
Open phpmyadmin
Create Database onlinecourse
Import database onlinecourse.sql (available inside zip package)
Login Details
To Login as admin put inside browser “http://localhost/onlinecourse/admin”
To Login as Student put inside browser “http://localhost/onlinecourse/”
II. USER MANUAL

2.1 Register Account
Step 1: Login as an admin
Step 2: Admin can registry a student by click on ‘Registration’ button at the menu
bar. The Student Registration page will then appear.
Step 3: Student Registration page will appear and admin can enter information and
click on ‘Sign up’ button to finish registration.
2.2 Login/Logout Account

To Login as admin put inside browser “http://localhost/onlinecourse/admin”
To Login as Student put inside browser “http://localhost/onlinecourse/”
Student and admin have similar login/logout method so we will do the Student
Login/Logout
*Login
Step 1: Enter web browser
Step 2: Enter information and click ‘Log in’ button to log in.
*Logout
Step 1: Click ‘Log out’ button in the menu bar
2.3 View/Edit Student

Step 1: Login as admin
Step 2: Admin can view students list by click on ‘Manage Student’ button at the
menu bar. The Manage Student page will then appear.
Step 3: Manage Student page will appear and admin can click on “Edit” to edit a
student information
Step 3: Student Profile page will appear and admin can input new information of
student and click on ‘Update’ button to finish edit.
2.4 Add course
Step 2: Admin can add course by click on ‘Course’ button at the menu bar. The
Course page will then appear.
Step 3: Course page will appear and admin can input new information of student
and click on ‘Submit’ button to add course.
2.5 Add course (Student)

Step 1: Login as student
Step 2: Student can enroll for course by click on ‘Enroll for course’ button at the
menu bar. The enroll for course page will then appear.
Step 3: Enroll for course page will appear and Student can choose course to enroll
and click on ‘Enroll’ button to enroll for course.
2.6 View/Remove course (Student)
Step 2: Student can view enrolled course by click on ‘Enroll History’ button at the
menu bar. The Enroll History page will then appear
Step 3: Enroll History page will appear and Student can click on ‘Delete’ button to
remove course.
2.7 View student’s course

Step 2: Admin can view student’s enrolled course by click on ‘Enroll History’
button at the menu bar. The Enroll History page will then appear
2.8 Change password
Student and admin have similar password method so we will do the Student
Change password
Step 2: Student can change their account’s password by click on ‘Change

password’ button at the menu bar. The Change password page will then appear
Step 3: Enter current password, new password and confirm it. Then click Submit to
change password
III. TEST CASE
3.1 Register Account
3.1.1 Simple Test
Test case #: 01 Test case name: Register Account
System: Student Registration System Subsystem: Account
Designed by: SE Team Design Date:19/10/18
Executed by: SE Team Execution Date:19/12/18
Short Description: Test the Register
Account service
Pre-conditions:
The system displays the Register Account page
Expected
Step Action System Pass/Fail Comment
Response
1 Enter name “Phi Hong” Pass
2 Enter Student Reg No Pass
“17022”
3 Enter password “123456” Pass
4 Click “Submit” Succesfull Pass
message
“Student
Registered
Successfully !!”
appear
5 Check Post-condition 1 Pass
Post-conditions:
1. A new account with: Name: “Phi Hong”
Student Reg No: “17022”
Password: “123456” are saved in database
3.1.2 Complex Test

Test case #: 01 Test case name: Register Account
Short Description: Test the Register
Account service
Pre-conditions:
The user must be logging in as admin
The system displays the Register Account page
Expected
Response
1 Enter name “Phi Hong” Pass
2 Enter Student Reg No “17022” Pass
4 Click “Submit” Succesfull Pass
message
“Student
Registered
Successfully
!!” appear
6 Repeat step 1 with name “Huy Pass
Thanh”
7 Repeat step 2 with Student Reg The system Pass
No “17022” displays the
message
warning that
the Student
Reg No is
not valid
8 Repeat step 2 with Student Reg Pass
No “17026”
9 Click “Submit” The system Pass
displays the
message
warning that
the password
is empty.
10 Repeat step 3 with password Pass
“159753”
11 Click “Submit” Return to Pass
Homepage
with the
account is
automatically
logged in.
Post-conditions:
1. A new account with: Name: “Phi Hong”
2. A new account with: Name: “Huy Thanh”
3.2 Login/Logout Account

*The Logout function is too simple, so my team decide to skip this function
3.2.1 Simple Test
Test case #: 02 Test case name: Login Account
Short Description: Test the Login
Account service
Pre-conditions:
-The user has not logged in before.
-The user has an activate account: Student Reg No – “17022”,
Password – “123456”.
-The system displays the Login box.
Expected
Response
“17022”
3 Click “Login” button Return to Pass
Homepage with
the account is
logged in
Post-conditions:
1. User has successfully login
3.2.2 Complex Test

Test case #: 02 Test case name: Login Account
Short Description: Test the Login
Account service
Pre-conditions:
-The user has not logged in before.
-The user has an activate account: Student Reg No – “17022”,
Password – “123456”.
-The system displays the Login box.
Expected
Response
“17022”
3 Click “Login” button Return to Pass
Homepage with
the account is
logged in
5 Repeat step 1,2,3 using The system Pass
wrong Student Reg No displays an alert
“dsg48fgs”. about wrong
Student Reg No
or password.
6 Repeat step 1,2,3 using The system Pass
wrong password “itu212”. displays an alert
about wrong
email or
password.
7 Repeat step 1,2,3 without The system Pass
performing anything displays an alert
prompting input
email/password.
8 Repeat step 1,2,3 Return to Home Pass
page with the
account is
logged in.
9 Check Post-conditions 1 Pass
Post-conditions:
1. User has successfully login
3.3 View/Edit Student

3.3.1 Simple Test
Test case #: 03 Test case name: View/Edit student
Short Description: Test the
View/Edit Student function
Pre-conditions:
-The user has already logged in as an admin
-The system displays the menu bar with “Manage Student” Button
Expected
Response
1 Press “Manage Student” The system Pass
Button displays Manage
Student page
2 Press “Edit” button next to a The system Pass
student displays Student
profile page
3 Change the name of the Pass
student in the name bar
from “Phi Hong” to
“Doraemon”
4 Press “Update Button” Successful Pass
message
“Student Record
Update
Successfully !!”
appear
5 Check Post-conditions 2,3 Pass
Post-conditions:
1. All students are displayed
2. The page is displayed with new information
3. Changes are saved to the database
3.3.2 Complex Test

Test case #: 03 Test case name: View/Edit student
Short Description: Test the
View/Edit Student function
Pre-conditions:
-The system displays the menu bar with “Manage Student” Button
Expected
Response
1 Press “Manage Student” The system Pass
Button displays Manage
Student page
2 Press “Edit” button next to a The system Pass
student displays Student
profile page
3 Change the name of the Pass
student in the name bar
from “Phi Hong” to
“Doraemon”
message
“Student Record
Update
Successfully !!”
appear
6 Change the CGPA of the Pass
student in the CGPA bar
from “10” to “9”
message
“Student Record
Update
Successfully !!”
appear
Post-conditions:
1. All students are displayed
2. The page is displayed with new information
3.4 Add course

3.4.1 Simple Test
Test case #: 04 Test case name: Add course
System: Student Registration System Subsystem: Course
Short Description: Test the Add
course function
Pre-conditions:
-The system displays the menu bar with “Course” Button
Expected
Response
1 Press “Course” Button The system Pass
displays Manage
Student page
2 Enter course’s information Pass
(code,name,unit,seat limit)
3 Press “Submit” button next Successful Pass
to a student message
“Course Created
Successfully !!”
appear
Post-conditions:
1. The system displays a successful Courses box
2. The system add course in database
2.4.2 Complex Test
System: Student Registration System Subsystem: Course
Short Description: Test the Add
course function
Pre-conditions:
The system displays the Course page
Pre-conditions:
-The system displays the menu bar with “Course” Button
Expected
Response
1 Press “Course” Button The system Pass
displays Manage
Student page
2 Enter course’s information Pass
(code,name,unit,seat limit)
“Course Created
Successfully !!”
appear
5 Repeat step 1,2,3 without The system Pass
performing anything displays an alert
prompting input.
6 Repeat step 1,2,3 Successful Pass
message
“Course Created
Successfully !!”
appear
Post-conditions:
1. The system displays a successful Courses box
3.5 Add course (Student)

3.5.1 Simple Test
System: Student Registration System (student)
Designed by: SE Team Subsystem: Course
Executed by: SE Team Design Date:19/10/18
Short Description: Test the Add Execution Date:19/12/18
course (student) function
Pre-conditions:
-The user has already logged in as an Student
-The system displays the menu bar with “Enroll Course” Button
Expected
Response
1 Press “Enroll for Course” The system Pass
Button displays Enroll
Course page
2 Choose “Database” Course Pass
3 Press “Enroll” button Successful Pass
message
“Course
Enrolled
Successfully !!”
appear
Post-conditions:
3.5.2 Complex Test

System: Student Registration System (student)
Short Description: Test the Add Execution Date:19/12/18
course (student) function
Pre-conditions:
-The system displays the menu bar with “Enroll Course” Button
Expected
Response
1 Press “Enroll For Course” The system Pass
Course page
2 Choose “Database” Course Pass
“Course Created
Successfully !!”
appear
5 Choose “Learing about Pass
space stuff” Course (which
is full)
6 Press “Submit” button next Fail message Pass
to a student “Seat not
available for this
course. All Seats
Are full “appear
Post-conditions:
3.6 View/Remove course (Student)

3.6.1 Simple Test
Test case #: 06 Test case name: View/Remove
System: Student Registration System course (Student)
Short Description: Test the Execution Date:19/12/18
View/Remove course (Student)
function
Pre-conditions:
-The system displays the menu bar with “Enroll History” Button
Expected
Response
1 Press “Enroll History” The system Pass
History page
2 Press “Delete” button next Successful Pass
to a Course message
“Course Remove
Successfully !!”
appear
Post-conditions:
1. The system remove course from database
3.6.2 Complex Test

Test case #: 06 Test case name: View/Remove
System: Student Registration System course (Student)
Short Description: Test the Execution Date:19/12/18
View/Remove course (Student)
function
Pre-conditions:
Expected
Response
History page
to Database Course message
“Course Remove
Successfully !!”
appear
History page
to Physics 1 Course message
“Course Remove
Successfully !!”
appear
History page
to Calculus 1 Course message
“Course Remove
Successfully !!”
appear
Post-conditions:
1. The system remove course from database
3.7 View student’s course

This use case is simple so it don’t have complex test
3.7.1 Simple test
Test case #: 07 Test case name: View student’s
System: Student Registration System course
Short Description: Test the View Execution Date:19/12/18
student’s course function
Pre-conditions:
Expected
Response
History page
Post-conditions:
1. The system displays a successful Enrolled history box
3.8 Change password

3.8.1 Simple test
Test case #: 08 Test case name: Change password
Short Description: Test the Change
password function
Pre-conditions:
-The user has already logged in
-The system displays the menu bar with “Change password” Button
Expected
Response
1 Press “Change password” The system Pass
Button displays Change
password page
2 Enter current password, new Pass
password and confirm
password (same as new
password)
“Change
password
Successfully !!”
appear
Post-conditions:
3.8.2 Complex test

Test case #: 08 Test case name: Change password
Short Description: Test the Change
password function
Pre-conditions:
-The user has already logged in
-The system displays the menu bar with “Change password” Button
Expected
Response
1 Press “Change password” The system Pass
Button displays Change
password page
password)
“Change
password
Successfully !!”
appear
password (different from
new password)
“Password and
Confirm
Password Field
do not match
!!”appear
password)
“Change
password
Successfully !!”
appear
Post-conditions:

Student Registration System-Final Report

Uploaded by

Copyright:

Available Formats

You might also like

Student Registration System-Final Report

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

Student Registration System-Final Report

Uploaded by

Copyright:

Available Formats

STUDENT REGISTRATION SYSTEM

Company Name: SE Team

1.2. Product’s Information

To implement this project, our team is going to need an amount

II. GOALS AND SCOPES

3. Implementation All functions must be clear, maintainable and

System shall attract many users and make a well-

The final system (Online Retail Application) shall

3. Market growth The final product shall produce significant growth

2. Future System shall leave rooms for future improvement

2. Response time System shall be able to respond to user within an

3. New technologies System shall be able to adapt to new technologies.

2. Application System shall satisfy most common standard rules

3. National and System shall not be illegal

2.2. Project Scope

3.1. Organizational Boundaries and Interfaces

IV. RESOURCE REQUIREMENTS

4.2. Software Resource

4.3. Human Resource

Analyze use case

Sketch relating Design Database

Update course Test all functions

Resgistration Modification Test respomsiveness

Acount Account Resgistration

Design main Course registration Pricacy testing in

5.2. Schedule and Milestones

Schedule and Milestones

VI. RISK MANAGEMENT

Risk Probability Description Strategy

Day Day Day Day Day Day Day Estimate

Day Day Day Day Day Day Day Estimate

Sprint 5 Day Day Day Day Day Day Day Estimate

Day Day Day Day Day Day Day Estimate

Day Day Day Day Day Day Day Estimate

Day Day Day Day Day Day Day Estimate

Day Day Day Day Day Day Day Estimate

Design use cases and class

VIII. SECURITY ASPECT (OPTIONAL)

IX. ABBREVIATIONS AND DEFINITIONS

UI Design User Interface Design

Hardware Physical component of a computer system

Software The programs and other operating information used by a

Use case A use case is a methodology used in system analysis to

Agile A group of software development methods

Scrum A lightweight process framework for agile development

Iteration The process of repeating computing process

HTML Hyper Text Markup Language - the standard markup

CSS The language for describing the presentation of Web pages,

Bug An error, flaw, failure or fault in a computer program or

Identify the actors involved in an interaction and names the

*Use case description 2.2: Log out

-Alternative Path: None

*Use case description 5.1: Add course (Student)

-Alternative Path: None

-Alternative Path: None

-Alternative Path: None

-Alternative Path: None