Final Project Report

"Web-Based Exam Management System"

By
Faizan Ahmed 70076777

A Project Report Submitted to the

DEPARTMENT OF COMPUTER SCIENCE & INFORMATION
TECHNOLOGY
in partial fulfillment of the requirements for the degree of
BACHELOR OF SCIENCE IN SOFTWARE ENGINEERING

Faculty of Computer Science & Information Technology

University of Lahore
Islamabad

1
DEDICATION
I dedicate my dissertation to all the faculty members of the Department of Computer
Science & Information Technology at the University of Lahore, whose guidance has
made this achievement possible. I express my gratitude to them for their efforts in
nurturing my skills and shaping us into contributing members of society. Lastly, we
dedicate our work to our parents, who have consistently supported us through thick and
thin. Their unwavering prayers have brought us to this momentous day.

1
DECLARATION
I declare that this dissertation is my original work, except where otherwise
acknowledged in the text and references. This work has not been submitted in any form
for another degree or diploma at any university or other tertiary education institution,
nor will it be submitted by me in the future for obtaining any degree from this or any
other university or institution.

Faizan Ahmed

70076777

1
CERTIFICATE OF APPROVAL
It is certified that the project titled “Web-Based Exam Management System” was
carried out by Faizan Ahmed, Reg. No. 70076777, under the supervision of Sir
Mehmood ul Hassan, University of Lahore is fully adequate, in scope and quality, as
a final year project for the degree of BS of Software Engineering.

Supervisor: Sir Mehmood ul Hassan

Lecturer
Dept. of CS & IT
University of Lahore

Internal Examiner : Sir Muhammad Iqbal

Lecturer
Dept. of CS & IT
University of Lahore

Project Coordinator: Sir Mehmood ul Hassan

Lecturer
Dept. of CS & IT
University of Lahore

Head of Department: Dr Maryam Zafar

HOD
Dept. of CS & IT
University of Lahore

2
ACKNOWLEDGMENT

We sincerely appreciate the invaluable cooperation and assistance provided by Mr.

Mehmood ul Hassan. His consistent guidance has been instrumental throughout this
project. Additionally, we extend our gratitude to our Project Coordinator, Mr.
Mehmood ul Hassan, for his unwavering support and guidance. We are also thankful to
our friends and families whose silent encouragement played a significant role in
enabling us to complete our project.

1
 ABSTRACT

The Web-Based Exam Management System (WBEMS) is a comprehensive platform

designed to streamline and enhance the process of managing examinations in
educational institutions. By leveraging web technologies, WBEMS offers a user-
friendly interface for administrators, instructors, and students to efficiently handle
various aspects of the examination process.

Key features of WBEMS include exam scheduling, question bank management, student
registration, automated grading, and result generation. Administrators can easily create
and manage exam schedules, allocate resources, and monitor exam progress in real-
time. Instructors have access to a centralized question bank, allowing them to create,
edit, and organize questions for exams with ease. Students can register for exams,
access study materials, and receive timely notifications about exam dates and results.

WBEMS aims to revolutionize the examination management process by eliminating

manual tasks, reducing paperwork, and minimizing errors. The system promotes
transparency, accountability, and fairness in assessments, ultimately enhancing the
overall academic experience for both students and faculty members.

Overall, WBEMS serves as a transformative tool for educational institutions,

revolutionizing the way examinations are managed and conducted. By automating
routine tasks, minimizing errors, and promoting transparency and fairness, WBEMS
enhances the efficiency and integrity of the examination process. As educational
institutions continue to adapt to the digital age, WBEMS stands as a testament to the
potential of technology to revolutionize academic assessment and improve the overall
learning experience for students and faculty members alike.

1
EXORDIUM
In the name of Allah, the Compassionate, the Merciful.

Praise be to Allah, Lord of Creation,

The Compassionate, the Merciful,
King of Judgment-day!

You alone we worship, and to You alone we pray for help,

Guide us to the straight path

The path of those who You have favored,

Not of those who have incurred Your wrath,

Nor of those who have gone astray.

1
PREFACE
It is great opportunity for me to have the BACHELORE OF SOFTWARE
ENGINEERING (BSSE) in University of Lahore. In the accomplishment of this
degree, I am submitting a project report on “Web Based Exam Management
System”.

The whole project report has been divided into 3 chapters.

 Gathering & Analyzing Info

 Designing the Project
 Development

2
 TABLE OF CONTENTS

CHAPTER NO. 1
GATHERING & ANALYZING INFO............................................................................9

1.1 INTRODUCTION……………………………………………………….10

1.2 PURPOSE…………………………………………………………… …10

1.3 SCOPE………………………………………………………………….10

1.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS……………………...11

1.5 PROJECT REQUIREMENTS

1.5.1 Functional Requirements…………………………………………11

1.5.2 Non-Functional Requirements …………………………………...12

1.6 USE CASES AND USAGE SCENARIOS

1.6.1 Use Case Diagrams……………………………………………….15

1.6.2 Usage Scenarios………………………………………………….16

1.7 DEVELOPMENT METHODOLOGY

1.7.1 Chosen Methodology…………………………………………….34

1.7.2 Reasons for Chosen Methodology……………………………….35

1.7.3 Work Plan (Gantt Chart) ………………………………………….36

1.7.3 Project Schedule (Submission Calendar) …………………………36

CHAPTER NO. 2
DESIGNING THE PROJECT.......................................................................................37

2.1 INTRODUCTION…………………………………………………………38

3
 2.2 PURPOSE…………………………………………………………38

2.3 SCOPE ……………………………………………………………38

2.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS………………...38

2.5 ARCHITECTURAL REPRESENTATION (ARCHITECTURE DIAGRAM) ….38

2.6 DYNAMIC MODEL: SEQUENCE DIAGRAMS…………………….39

2.7 OBJECT MODEL/LOGICAL MODEL: CLASS DIAGRAM…………42

2.8 DATABASE MODEL (DATABASE DIAGRAM) ………………………43

2.9 GRAPHICAL USER INTERFACES…………………………………...44

CHAPTER NO.3
DEVELOPMENT............................................................................................................48
3.1 DEVELOPMENT PLAN (ARCHITECTURE DIAGRAM)

4
 CHAPTER 1
Gathering & Analyzing Info

5
 CHAPTER NO. 1
1.1 Introduction

Web based exam system will encourage its clients to lead the online exam in campuses
or at home utilizing web. Administrator will deal with the entire framework. Teacher
will add question and generate exam. Students will able to participate in exam and
teacher will check the exam and announce the result.

1.2 Scope

In the age of modern learning people prefer the distance learning. in this
scenario teacher can teach and student can learn. but how to confirm that student
learned all that teach by the teacher? There was a need of exam.

The introduction of Web based exam management system replaced the conventional
system of assessment. The purpose of the system is to completely automate the old
manual procedure of conducting exam to a computerized System. That will reduce an
organization’s administrative burden but also saves cost and time.
Following are some reason for the introduction of the web-based exam management
system:

1. Backbone of the E-Learning: Exam is the only way to access that what student
have learned, but it was problem in e learning to get the answer of the above
question. solution of this problem generates the idea of exam management
system.
2. Conduct exams effortless: Computer based tests as a way of conducting
associate assessment modify users to manage associate test simply. The
functionalities of associate test package like easy dashboard, support for
multiple question sorts and formats, elaborate coverage, automatic instant
results help in smooth conduction.
3. Reduce exam anxiety Amongst test takers: The flexibility associated with
computer-based tests reduces exam anxiety among test takers as they can take
the exam at any time of the day that coincides with their preferred sleep/ wake
cycle.

6
 4. Prevents cheatings: Cheating amongst the test-takers in the examination hall is
one of the major drawbacks of pen paper-based assessment. Online examination
managed avoids the possibilities of secretly using unfair means to get the right
answers. The presence of various functionalities in exam system prevents
cheating irrespective of the test taker’s location.
5. Safe and secure data: Various tools will offer by exam system that will enable
the assessment conducting agencies to manage the crucial data related to
examination questions and test-takers safely.
6. Reduce administrative burden: Organizing and running exams online not only
reduces an organization’s administrative burden but also saves cost and time.
7. Online examination with its objective to make evaluation massive but simple,
cost-effective and faster has replaced the pen paper-based assessment.

1.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS

SRS Software Require Specification

PC Personal Computer
HTML Hyper Text Markup Language
CSS Cascade Styling Sheet
JAVA Just Another Vague Acronym
JS Java Script
JQ J Query

1.5 PROJECT REQUIREMENTS

1.5.1 Functional Requirements

Admin Functional Requirements:

1. Admin can login to the Exam system using his/her ID and password.
2. Admin can add new teachers.
3. Admin can search teachers.

7
 4. Admin can permanently delete teacher’s data from the database.
5. Admin can update teacher’s data.
6. Admin can add new subjects.
7. Admin can search subjects.
8. Admin can permanently delete subjects from the database.
9. Admin can update subjects.
10. Admin can allocate subjects to teacher.
11. Admin can change his/her password.
12. Admin can view figure of existing subjects, teachers and students.
13. Admin can view announcement made by teachers.
14. Admin can view his/her profile.
15. Admin can logout from the exam system.

Teacher Functional Requirements:

16. Teacher can login through ID and password.

17. Teacher can add new question.
18. Teacher can edit existing questions.
19. Teacher can delete existing questions.
20. Teacher can search question into question bank.
21. Teacher can view all the created questions.
22. Teacher can view all the enrolled students.
23. Teacher can make exam schedule (date and time of exam).
24. Teacher can make paper (total marks, MCQ’s, 3 marks and 5 marks
questions strength).
25. Teacher can make announcement (result declaration and other news).
26. Teacher can view exams of the students by clicking on his/her student id.
27. Teacher can check paper.
28. Teacher can change his/her password.
29. Teacher can view his/her profile.
30. Teacher can logout

Student Functional Requirements:

8
 31. Student can sign up.
32. Student can login for the Exam Portal.
33. Student can enroll in different courses.
34. Student can take paper.
35. Student can view profile
36. Student can view announcement.
37. Student can reset password.
38. Student can logout.

1.5.2 Non-Functional Requirements

There are a lot of software requirements specifications include in the Non-

Functional requirements of the Web based Exam system which contains various
process namely security, performance, maintainability and reliability.

 Security:
1) User identification:
The system should be able to recognize is it student, teacher or
Admin?
2) Login ID:
Any user who makes use of the system need to hold a login ID and
password.

 Modification:
Any modification like insert, delete, update, etc., for the database can be
synchronized quickly and also will perform only by the authorized actor for
that particular modification.
1) Teachers Rights:
Teacher can add new questions but he/she can’t change the subject
information. And only will responsible for the assigned subjects.
Similarly, they can view their profile but can’t modify it except password.
2) Administrator Rights:

9
 The administrator can view as well as alter any information in the Exam
system.
3) Students Rights:
Student can only take exam and view non editable profile except password.

 Performance:
1) Response Time:
The system provides paper in just one second once the student clicks
to get paper.
2) Capacity:
The system needs to support at least 1000 people at once.
3) User Interface:
The user interface acknowledges within five seconds.
 Maintainability:

1) Backup:
The system offers the efficiency for data backup.
2) Errors:
The system will track every mistake as well as keep a log of it.
 Reliability:
The system can update its content in real time. Therefore, changes such as
addition, deletion or modification can be done immediately. This ensures that
the content of the system is up-to-date, reliable and can be trusted. The system
will also be able to produce all related output to queries.
 Availability:
The system can operate 24 hours per week and 365 days a year. As long as the
user not shut down the desktop. All the information will be keep in the
database. Even though, the browser is shut off information still exist in the
database.
 Portability:
The system is being developed as web base using the PHP language and
MySQL. Before the system release to system needs to compile without any
error before the system run. Therefore, the exam portal will be able to run at any
kind of browser.
10
  Flexibility:

Flexibility System is working easily on the Internet with the username and
password of the user. The system has given the rights to the admin, teachers and
the students to use the system with their username. The system can also work on
other kind of technology with the little modification. System should be quite
flexible to use and maintain.

 Efficiency:
System should be efficient enough to meet all kinds of requirements as required
by the admin, teachers and students. The system should not hang or lose its
efficiency in any kind of worse conditions. It should provide the correct output
in all manners.
 User friendliness:
 System should be user friendly, so that any user can use and access the system
with easiness.

1.6 USE CASES AND USAGE SCENARIOS

1.6.1 Use Case Diagrams

A use case diagram at its simplest is a representation of a user's interaction with
the system that shows the relationship between the user and the different use
cases in which the user is involved.

11
1.6.2 Usage Scenarios

A usage scenario, or scenario for short, describes a real-world example of how one or
more people or organizations interact with a system. They describe the steps, events,
and/or actions which occur during the interaction.

Use case title Login

Use case Id 1
Actions Enter user name, password and press login button.
Description Admin will enter name and password to make login in

12
 the system.
Alternative Paths Forget Password
Pre-Conditions Admin have already record in DB.
Post-Conditions Admin successfully logged in.
exceptions Problem with network connection. Admin not
available into DB
Author (BC170401126)
Scenarios no. 1:

Scenarios no. 2:
Use case title Add teacher
Use case Id 2
Actions Enter teacher information and click add button.
System should provide confirmation message.
Description Admin can add and manage teachers.

Alternative Paths N /A
Pre-Conditions Admin have already logged in.
Post-Conditions Update system
exceptions Unable to login an admin
Author (BC170401126)

Scenarios no. 3:
Use case title Search teacher

13
Use case Id 3
Actions Enter teacher id and click search button.
System should provide teacher information.
Description Admin can view and manage teachers.

Alternative Paths N /A
Pre-Conditions Admin have already logged in.
Teacher have already record in DB
Post-Conditions Teacher information displayed successfully.
exceptions Unable to login an admin. Teacher not available in DB
Author (BC170401126)

Scenarios no. 4:
Use case title Delete teacher
Use case Id 4
Actions Hit delete teacher button.
System should provide confirmation message.
Description Admin can update and manage teachers.

Alternative Paths Search Teacher

Pre-Conditions Admin have already logged in.
Post-Conditions Teacher information delete successfully.
exceptions Unable to login an admin. Server not available
Author (BC170401126)

Scenarios no. 5:

14
Use case title Update teacher
Use case Id 5
Actions Enter teacher information and click update button.
System should provide confirmation message.
Description Admin can update and manage teachers.

Alternative Paths Search Teacher

Pre-Conditions Admin have already logged in.
Post-Conditions Teacher information update successfully.
exceptions Unable to login an admin. Server not available
Author (BC170401126)

Scenarios no. 6:
Use case title Add Subject
Use case Id 6
Actions Enter subject information and click add button.
System should provide confirmation message.
Description Admin can add and manage subjects.

Alternative Paths N /A
Pre-Conditions Admin have already logged in.
Post-Conditions Update system
exceptions Unable to login an admin
Author (BC170401126)

Scenarios no. 7:

15
Use case title Search subject
Use case Id 7
Actions Enter subject code and click search button.
System should provide subject information.
Description Admin can view and manage subject.

Alternative Paths N /A
Pre-Conditions Admin have already logged in.
Subject have already record in DB
Post-Conditions Subject information displayed successfully.
exceptions Unable to login an admin. Subject not available in DB
Author (BC170401126)

Scenarios no. 8:
Use case title Delete Subject
Use case Id 8
Actions Hit delete subject button.
System should provide confirmation message.
Description Admin can update and manage subject.

Alternative Paths Search Subject

Pre-Conditions Admin have already logged in.
Post-Conditions Subject information deletes successfully.
exceptions Unable to login an admin. Server not available
Author (BC170401126)

Scenarios no. 9:

16
Use case title Update Subject
Use case Id 9
Actions Enter Subject information and click update button.
System should provide confirmation message.
Description Admin can update and manage subject.

Alternative Paths Search Subject

Pre-Conditions Admin have already logged in.
Post-Conditions Subject information update successfully.
exceptions Admin not fulfill all the required fields. Server not
available
Author (BC170401126)

Scenarios no. 10:

Use case title Allocate Subject to Teacher
Use case Id 10
Actions Select subject and teacher and hit assign.
System should provide confirmation message.
Description Admin can update and manage subject and teacher.

Alternative Paths Add subject or add teacher

Pre-Conditions Admin have already logged in.
Post-Conditions Subject assign to teacher successfully.
exceptions Teacher or free subject not available, Server not
available
Author (BC170401126)

Scenarios no. 11:

17
Use case title Change password
Use case Id 11
Actions Enter old password and new password and click
confirm button.
System should provide confirmation message.
Description Admin can change his/her password.

Alternative Paths N/A

Pre-Conditions Admin have already logged in.
Post-Conditions Admin password update successfully.
exceptions Unable to login an admin, old password incorrect,
Server not available
Author (BC170401126)

Scenarios no. 12:

Use case title Home
Use case Id 12
Actions Click on the home button to view the current DB status

Description Admin can view total teachers, subjects and students in

DB and other.
Alternative Paths Login
Pre-Conditions Admin have already logged in.
Post-Conditions Admin can successfully see DB status.
18
exceptions Unable to login an admin. Server not available
Author (BC170401126)

Scenarios no. 13:

Use case title View Profile
Use case Id 13
Actions Click on the admin name to view the profile.
Description Admin can view his/her recorded information in DB
Alternative Paths N/A
Pre-Conditions Admin have already logged in.
Post-Conditions Admin can successfully see his/her profile.
exceptions Server error occurs to viewing the user’s profile.
Author (BC170401126)

Scenarios no. 14:

Use case title View Announcement
Use case Id 14
Actions Click on the bell icon to view the announcement.

Description Admin can view the announcement that made by the

teachers.
Alternative Paths N/A
Pre-Conditions Admin have already logged in.

19
Post-Conditions Admin see announcement successfully.

exceptions Announcement not recorded by any of the teacher.

Server not available.
Author (BC170401126)

Scenarios no. 15:

Use case title Logout
Use case Id 15
Actions Click on the logout button.

Description Admin can logout from system.

Alternative Paths Session time out

Pre-Conditions Admin have already logged in or session time out.
Post-Conditions Admin sign out successfully.

exceptions Server not available.

Author (BC170401126)

Scenarios no. 16:

Use case title Login
Use case Id 16
Actions Enter user name, password and press login button.
Description Teacher will enter name and password to make login
in the system.
Alternative Paths Forget Password

20
Pre-Conditions Teacher have already record in DB.
Post-Conditions Teacher successfully logged in.
exceptions Problem with network connection. Teacher not
available into DB
Author (BC170401126)

Scenarios no. 17:

Use case title Add Question
Use case Id 17
Actions Select subject and fill question filed and hit add.

Description Teacher can add question into assigned subject.

Alternative Paths Wait for subject allocation from the admin.

Pre-Conditions Teacher have already logged in and assigned selected
subject.
Post-Conditions Teacher add question successfully.

exceptions Problem with network connection .

Author (BC170401126)

Scenarios no. 18:

Use case title Edit Question
Use case Id 18
Actions Select subject and select question and click edit
button.
Description Teacher can edit existing question of the assigned
subject.
21
Alternative Paths Search question.
Pre-Conditions Teacher have already record in DB.
Post-Conditions Teacher successfully edit the question.
exceptions Problem with network connection .
Author (BC170401126)

Scenarios no. 19:

Use case title Delete Question

Use case Id 19
Actions Select question and hit delete button.

Description Teacher can delete question.

Alternative Paths Search question

Pre-Conditions Teacher have already logged in.
Post-Conditions Teacher delete question successfully.

exceptions Problem with network connection .

Author (BC170401126)

Scenarios no. 20:

Use case title Search question
Use case Id 20
Actions Enter question id or statement and hit search button.
Description Teacher can search question from the question bank.

22
Alternative Paths Add question
Pre-Conditions Teacher and question should be already record in DB.
Post-Conditions Teacher successfully search question.
exceptions Problem with network connection.
Author (BC170401126)

Scenarios no. 21:

Use case title View Existing question
Use case Id 21
Actions Select subject and hit to view questions button.
Description Teacher can view existing question from the question
bank.
Alternative Paths Add question
Pre-Conditions Teacher and question should be already record in DB.
Post-Conditions Teacher successfully view questions.
exceptions Problem with network connection.
Author (BC170401126)

Scenarios no. 22:

Use case title View Enrolled student

23
Use case Id 22
Actions Select subject and hit to view enrolled student button.
Description Teacher can view enrolled students for specific
subject.
Alternative Paths N/A
Pre-Conditions Teacher should be logged in.
Post-Conditions Teacher successfully view enrolled students.
exceptions Problem with network connection.
Author (BC170401126)

Scenarios no. 23
Use case title View Enrolled student
Use case Id 22
Actions Select subject and hit to view enrolled student button.
Description Teacher can view enrolled students for specific
subject.
Alternative Paths N/A
Pre-Conditions Teacher should be logged in.
Post-Conditions Teacher successfully view enrolled students.
exceptions Problem with network connection.
Author (BC170401126)

Scenarios no. 24:

Use case title Make Exam schedule
Use case Id 24
Actions Mention exam time and date and hit save.

24
Description Teacher can make exam schedule.

Alternative Paths N/A

Pre-Conditions Teacher should be logged in.
Post-Conditions Teacher successfully make exam schedule.
exceptions Problem with network connection.
Author (BC170401126)

Scenarios no. 25:

Use case title Make Paper
Use case Id 25
Actions Mention total marks and strength of the MCQ’s, 3
marks questions and 5 marks questions.
Description Teacher can make paper.

Alternative Paths N/A

Pre-Conditions Teacher should be logged in.
Post-Conditions Teacher successfully make paper.
exceptions Problem with network connection, not enough
questions in bank to fulfill total marks of the exam.
Author (BC170401126)

Scenarios no. 26:

Use case title Make Announcement
Use case Id 26
Actions Mention date and subject of the announcement.

25
Description Teacher can make announcement.

Alternative Paths N/A

Pre-Conditions Teacher should be logged in.
Post-Conditions Teacher successfully make announcement.
exceptions Problem with network connection.
Author (BC170401126)

Scenarios no. 27:

Use case title View student’s exam
Use case Id 27
Actions Select student to and hit view exam button.
Description Teacher can view student’s exam.

Alternative Paths N/A

Pre-Conditions Teacher should be logged in.
Post-Conditions Teacher successfully view student’s exam.
exceptions Problem with network connection.
Author (BC170401126)

Scenarios no. 28:

Use case title Check Paper
Use case Id 28
Actions Select the student exam and assign marks according to
given answers.
Description Teacher can check paper.

Alternative Paths N/A

Pre-Conditions Teacher should be logged in.
Post-Conditions Teacher successfully check student’s paper.

26
exceptions Problem with network connection.
Author (BC170401126)

Scenarios no. 29:

Use case title Change password
Use case Id 29
Actions Enter old password and new password and click
confirm button.
System should provide confirmation message.
Description Teacher can change his/her password.

Alternative Paths N/A

Pre-Conditions Teacher have already logged in.
Post-Conditions Teacher password update successfully.
exceptions old password incorrect, Server not available
Author (BC170401126)

Scenarios no. 30:

Use case title View Profile
Use case Id 30
Actions Click on the teacher name to view the profile.
Description teacher can view his/her recorded information in DB
Alternative Paths N/A
Pre-Conditions teacher have already logged in.
Post-Conditions teacher can successfully see his/her profile.
exceptions Server error occurs to viewing the user’s profile.
Author (BC170401126)

27
Scenarios no. 31:
Use case title Logout
Use case Id 31
Actions Click on the logout button.

Description Teacher can logout from system.

Alternative Paths Session time out

Pre-Conditions Teacher have already logged in or session time out.
Post-Conditions Teacher sign out successfully.

exceptions Server not available.

Author (BC170401126)

Scenarios no. 32:

Use case title Sign Up
Use case Id 32
Actions Go to login page and click sign up and fill all the
field’s data and hit sign up button.
Description Student can record his/her self into DB
Alternative Paths N/A
Pre-Conditions Student must visit login page.
Post-Conditions student can successfully submit his/her information.
And wait for approval.
exceptions Server error occurs to submitting student information.
Author (BC170401126)

Scenarios no. 33:

Use case title Login

28
Use case Id 33
Actions Enter user name, password and press login button.
Description Student will enter name and password to make login
in the system.

Alternative Paths Forget Password

Pre-Conditions Student have already record in DB.
Post-Conditions Student successfully logged in.
exceptions Problem with network connection. Student not
available into DB
Author (BC170401126)

Scenarios no. 34:

Use case title Take paper
Use case Id 34
Actions Select subject and hit start exam button.
Description Student can take paper. Write his/her answer and
submit.

Alternative Paths N/A

Pre-Conditions Student have already record in DB.
Post-Conditions Student successfully take his/her paper.
exceptions Problem with network connection. No exam session
available.
Author (BC170401126)

Scenarios no. 35:

Use case title View Profile
Use case Id 35
Actions Click on the student name to view the profile.
Description student can view his/her recorded information in DB
Alternative Paths N/A

29
Pre-Conditions student have already logged in.
Post-Conditions student can successfully see his/her profile.
exceptions Server error occurs to viewing the user’s profile.
Author (BC170401126)

Scenarios no. 36:

Use case title View Announcement
Use case Id 36
Actions Click on the bell icon to view the announcement.

Description student can view the announcement that made by the

teachers.

Alternative Paths N/A

Pre-Conditions student have already logged in.
Post-Conditions student see announcement successfully.

exceptions Announcement not recorded by any of the teacher.

Server not available.
Author (BC170401126)

Scenarios no. 37:

Use case title Change password

Use case Id 29
Actions Enter old password and new password and click
confirm button.
System should provide confirmation message.
Description Student can change his/her password.

Alternative Paths N/A

Pre-Conditions Student have already logged in.

30
 Post-Conditions Student password update successfully.
exceptions old password incorrect, Server not available
Author (BC170401126)

Scenarios no. 38:

Use case title Logout
Use case Id 38
Actions Click on the logout button.

Description Student can logout from system.

Alternative Paths Session time out

Pre-Conditions Student have already logged in or session time out.
Post-Conditions Student sign out successfully.

exceptions Server not available.

Author (BC170401126)

1.7 DEVELOPMENT METHODOLOGY

1.7.1 Chosen Methodology

Many methodologies exist a now days and a variety of model used various people to
their need and nature of their work.

Water Fall Methodology: -

31
The water fall methodology goes to the cycle of analysis, design, coding, testing, and
maintenance. The simplest version of this is called the "waterfall" methodology. The
systems services, constraints and goals are defined by consulting the system with users.
The requirement is classified into hardware and software systems. It gives overall
architecture of the system.The system is installed and gives to practical use. The
system checks errors are corrected them and improve it.

32
 Waterfall model:

In this approach, we see that processes flows in a downward fashion from

requirement phase to accepting phase which meets to client satisfaction. Requirements
phase collects software specifications, functional and non-functional requirements in
SRS (software requirement specification) document of VU final project. Analysis phase
analyzes cases and work plan on the basis of software requirement phase that covers
use case scenarios up to methodology and work plan. Design phase goes through with
flow charts, algorithms and GUI on the basis of analysis phase. Coding phase generates
the actual logic of the application and provide functionality to the system. The system
logic is tested if it is working as it is as in designing phase. Finally, client acceptance
phase verifies if application meets to the client's requirement.

1
Spiral Methodology: -
To avoid the risk that might be faced in development of software the spiral
methodology is used. For example, the risk might be a resignation from the key person
There are two dimensions in a Spiral Model; A Radial dimension which represents the
cumulative cost to date, and an angular dimension which represents the progress
through the spiral.The spiral model is very sensitive to risks. Due to its spiral nature the
development and maintenance run in parallel. This method is used for development of
large-scale and in-house software.

1
Planning phase covers scope, requirements and functionality of the system. Second
phase Risk analysis is most important phase of spiral model which defines cost-
effective strategies in project development. Risk at any stage indicates that
requirements must be reviewed to find out solution for the problem by given data in the
previous phase before proceed to the next. Development phase covers the designing,
coding and testing and finally application is delivered to client for further evaluation.
In case of any change it is required to iterate the application from all four phases again.
That's why it is called spiral model. Our developers use the spiral iterative methodology
to build software applications in the shortest possible time and with zero risk. In this
process, an application will go through different stages, such as:

2
1
VU Process Model: -
It is the combination of waterfall methodology and spiral methodology. It is also called
hybrid approach of system development. It has five phases, and which are Gathering
and analyzing requirement, planning, analysis and design, development and final
report. In the requirement phase the system goals, services and constrains are
established after discussion with user. The planning phase is synchronized effort to find
all the potential roadblocks and draft a robust plan to tackle each. This phase usually
involves a lot of brainstorming within software development team as well as with
respective client. It maximizes the quality of system and minimizes any risks and
errors.

1.7.2 Reasons for Chosen Methodology

I have chosen the methodology of VU Process model

1
For making our software we adopted VU Process Model which is a combination of
both waterfall and spiral models. The idea behind this model is that to get the benefits
of both these models.

Reasons for choosing the VU Process Model

 The VU Process Model, as described above, offers numerous advantages for
software developers and because of its beneficial flow we use this methodology.
 The staged development cycle enforces discipline: every phase has a defined
start and end point.
 Progress can be conclusively identified by both vendor and client.
 The emphasis on requirements and design before writing a single line of code
ensures minimal wastage of time and effort and reduces the risk of schedule
slippage, or of customer expectations not being met.
 Getting the requirements and design out of the way first also improves quality;
it’s much easier to catch and correct possible flaws at the design stage than at
the testing stage, after all the components have been integrated and tracking
down specific errors is more complex.
 Finally, because the first two phases end in the production of a formal
specification, the waterfall model can aid efficient knowledge transfer when
team members are dispersed in different location.

1
1.7.3 Work Plan (Gantt Chart)

581
 CHAPTER 2
Designing the Project

582
 2.1 INTRODUCTION
The analysis phase defines the requirements of the system, independent of how these
requirements will be accomplished. This phase defines the problem that the customer is
trying to solve. The deliverable result at the end of this phase is a requirement
document. Ideally, this document states in a clear and precise fashion what is to be
built. This analysis represents the “what” phase. The requirement document tries to
capture the requirements from the customer's perspective by defining goals and
interactions at a level removed from the implementation details.

2.2 PURPOSE
The main purpose of this is to formally document the design of software. Well
documented code is easier to reuse. It captures important design decision such as
responsibilities that drive the performance. It supports software integrating and unit
testing of the associated modules by describing their interface.

2.3 SCOPE
In this document, we have included ERD, Sequence and Class Diagram
Database and Interface Design, and Test Cases. Design document describe the system
requirements, system and subsystem architecture, processing logic and external
interface.

2.5 ARCHITECTURAL REPRESENTATION (ARCHITECTURE

DIAGRAM)
Once the features implemented and architecture drafted, system design is also needed
to implement the application. Following are the diagrams that are used to implement
the application.

583
Architectural layered Diagram:

2.6 DYNAMIC MODEL: SEQUENCE DIAGRAMS

Admin Area

584
Teacher Area

585
Student Area

586
2.7 OBJECT MODEL/LOGICAL MODEL: CLASS DIAGRAM

587
2.8 DATABASE MODEL (DATABASE DIAGRAM)

588
2.9 GRAPHICAL USER INTERFACES

589
58
10
55 1
 CHAPTER 3
Development

3.1 DEVELOPMENT PLAN (ARCHITECTURE DIAGRAM)

The deployment diagram is the UML that models the physical deployment of nodes
and artifacts. Following is the deployment diagram of our system.

REFERENCES
[1] Xampp server www.apachefriends.org
[2] Software Engineering CS504 Handouts Virtual University of Pakistan
[3] Database Management System CS403 Handouts VU
[4] Wekipedia.com
[5] Tutorials www.youtube.com
[6] Sublime Text Editor https://www.sublimetext.com/
[7] UML Diagrams draw.io

573
574
 APPENDIX

List of Figures

Work Plan ……………………………………………………….36

ARCHITECTURAL LAYERED DIAGRAM………………………… 38
USE CASE DIAGRAM……………………………………………...15
CLASS DIAGRAM ………………………………………………. 42
Database Design…………………………………………………,43
DEVLOPMENT DIAGRAM…………………………………………49

585