0% found this document useful (0 votes)
36 views

Online School Management System: The Punjab College of Commerce &computer Science Haroonabad

School Mangement System SDD

Uploaded by

Shahid Jamal
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
36 views

Online School Management System: The Punjab College of Commerce &computer Science Haroonabad

School Mangement System SDD

Uploaded by

Shahid Jamal
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 61

SCHOOL MANAGEMENT SYSTEM

Final Project Report

Online School Management System

The Punjab College of commerce &Computer Science


Haroonabad

1
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Project Supervisor
Mr Shahid Jamal

Submitted By

Students
Name Amna Ashraf & Mehreen Maryam

Roll No 172501 , 172508

Class MCS 3rd

Session 2017-2019

Department of computer Science

2
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

TABLE OF CONTENTS

CHAPTER NO. 1

GATHERING & ANALYZING INFO.............................................................................4

1.1 – SCOPE OF PROJECT 5


1.2 – SOFTWARE REQUIREMENTS 5
1.2.1 – FUNCTIONAL REQUIREMENTS 5
1.2.2 – NON FUNCTIONAL REQUIREMENTS 6
1.3 – USE CASES 7
1.3.1 – USE CASE DIAGRAM 8
1.3.2 – USE CASE SCENARIOS 8

CHAPTER NO. 2

PLANNING THE PROJECT.........................................................................................25

2.1 – INTRODUCTION OF THE PLANNING PHASE 25


2.2 – METHODOLOGIES 26
2.2.1 – EXISTING METHODOLOGIES 26
2.2.1.1 – BUILD AND FIX MODEL 27
2.2.1.2 – RAPID PROTOTYPING MODEL 27
2.2.1.3 – SYNCHRONIZE AND STABILITY MODEL 27
2.2.1.4 – SPIRAL MODEL 28
2.2.2 – ADOPTED METHODOLOGY 28
2.2.3 – REASONS FOR CHOOSING THE METHODOLOGY 29
2.3 – Gantt Chart 30
2.4– Team Structure 31

3
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

CHAPTER NO. 3

DESIGNING THE PROJECT.......................................................................................32

3.1 – INTRODUCTION 33
3.2 – OVERVIEW 33
3.3 – DATA FLOW DIAGRAMS (DFD) 34
3.4 – ENTITY RELATIONSHIP DIAGRAM (ERD) 35
3.5 – ACTIVITY DIAGRAMS 38
3.6 – SEQUENCE DIAGRAMS 42
3.7 – CLASS DIAGRAM
43
3.8 – DATABASE DESIGN 44
3.9 – INTERFACE DESIGN 45

CHAPTER NO.4

DEVELOPMENT............................................................................................................54

4.2 – TEST CASES 55

CHAPTER NO.5

DEPLOYMENT...............................................................................................................58

5.1 – DEPLOYMENT DIAGRAM


59
5.2– References 60

4
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

CHAPTER 1
Gathering & Analyzing Info

5
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

1.1 - Scope of Project


The project is a web Application that is to be hosted on a web server. Any
Student/Person will be able to access the web application by using internet. This web
application will facilitate the Student/Person can visit this web application and apply online
for school admission and Teacher mark attendance and upload result. Student and Parent
can view attendance and results online. After the admission and registrations give the user
name and password to the student . Students and their parents view student reports (results
And attendance). And Student can send leave application online.
The project will facilitate the student and parents to quickly view reports of the
student at any time. The interface of web application will be very user friendly. Even the
end users that are not so much computer literate or have not much experience in surfing the
Internet will feel very easy to navigate the web application home page like website. For the
purpose, the web application is to be very simple and straightforward. The website will not
have lot of text, links, graphics and advertisements on a single webpage to confuse the
user. Whatever the user will see will actually be valuable.
Admin can change system and insert, update, delete user accounts and manage
class routine, exam results, fee of students and he can manage classes, sections, manage
students, subjects, manage teachers after approved the addition of student. Admin can
seething, his on login details

There is a public notes board. Every user can view notes board appeared on the
front page of the web application

1.2 - Software Requirements

1.2.1 - Functional Requirements

FR01 Student Apply online


FR01-01 Get admission num

6
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

FR02 User Login


FR02-01 Get User name from admin
FR02-02 Get password from admin
Validate the User ID and password and enable the user to reenter the
FR02-03 User ID and Password if record is not found
FR02-04 Make the user know that he or she is logged in

FR04 Student Login


FR04-01 Get Attendance Status
FR04-02 View Exam Results
FR04-03 Request for Leave
FR04-04 View Class Routine

FR05 Teacher Login


FR05-01 Upload Exam Result
FR05-02 View Exam Result
FR05-03 Mark Attendance
FR05-04 View Attendance

FR06 Parent Login

FR06-01 Get Children Result


FR06-02 Get Children Class Routine

FR06-03 Get Children Attendance

FR07 Admin Login


FR07-01 Manage User Accounts/ Teacher , Parent , Student
FR07-02 Manage Class Routine
FR07-03 Manage Exam Results
FR07-04 Manage Student Attendance
FR07-05 Manage Fee Of Student
FR07-06 Generate Reports

1.2.2 - Non Functional Requirements


7
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Usability

 Speed of use
 Required Administrator Ability
 On-line Help
 Consistency

Reliability

 Maximum Failure Rate


 Maximum Down Time
 Easy to Recovery

Performance

 Throughput
 Degradation Under Overload Condition
 Resource Usage
 Response Time

Security

 Internal Security
 External Security

Supportability

 Ease of Installation
 Planned Maintenance
 Easy of Configuration
 Easy of Testing

The system is to be developed as web application with home page like website because
the system is open for the users by nature and every user will have access to the
system.
The web application will not have so much heavy graphics and interface that the user
will wait for a long time waiting the web application to be loaded

1.3 - Use Cases


A use case is a methodology used in system analysis to identify, clarify, and organize
system requirements. In this context, the term "system" refers to something being
developed or operated, such as a mail-order product sales and service Web site. Use case

8
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

diagrams are employed in UML (Unified Modeling Language), a standard notation for the
modeling of real-world ob 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. A use case diagram can
identify the different types of users of a system and the different use cases and will
often be accompanied by other types of diagrams as well jects and systems.

1.3.1 - Use Case Diagram

Use case

9
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

1.3.2 – Use Case Scenarios

Use Case Description

Use Case ID UC- 1


Use Case This use case describes how a users logs into
Descriptions the School Management System
Use Case Name Login
Primary Actor All Student , Parents , Teachers , Admin
Trigger When users click on the login button with user
name & password
Pre-Condition Users must be at the home page of the
software.
The users must be registered his/her login
name & password in the database.
Basic Flow This use case starts when the users wishes to
login to the School Management System.
 System request, that the users enter
his/her name & password.
 When the users enter his/her name &
password system validates the entered
name & password & logs the User into
the system.
Alternative Flow If the name or password is not validate system
return error message. The Users can choose to
either return to the beginning of the basic flow
or cancel the login at which the use case ends.
Post Condition If the use case was successful then the user is
now logged into the system.
Exception The software returns error message if invalid
entries are entered.
Login

Use Case Description

10
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Use Case ID UC- 2


Use Case This use case describes how a user logout from
Descriptions the School Management System
Use Case Name Logout
Primary Actor All Students , Parents , Teachers & Admin
Trigger When user click on the logout button.
Pre-Condition User must be logged into the system before he/she
signs out.
Basic Flow This use case starts when the user wishes to sign
out from the School Management System.
 user press the sign out button & the session
of user expires.
 After signing out system return to Home
page.
Post Condition If the use case was successful then the user is now
sign out from the system.
Logout

Use Case Description

Use Case ID UC- 3


Use Case This use case describes how the Student can
Descriptions register online in School Management System
Use Case Name Online Registration
Primary Actor All students
Trigger When Student clicks on online Registration
button.
Pre-Condition Student must be at the Home page.
Basic Flow This use case starts when the Student wishes
to register online into School Management
System.
 Student must be visit over web site must
be at over home page.
 When the Student clicks on online
11
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

registration button then there will be


open are registration form Students must
fill all form fields..
 Student must be press Submit Button

Post Condition If the Student was successful submit his


admission form then They will receive a
confirmation message and due date for fee
submission in account office.
Online Registration

Use Case Description

Use Case ID UC- 4


Use Case This use case describes how the Students can
Descriptions view the Notes board of the School
Management System
Use Case Name View Notes board
Primary Actor Students
Trigger When Students click on the Notes board
button.
Pre-Condition Students must be at the Home page.
And must be registered his/her login name &
password in the database.
Basic Flow This use case starts when the Student wishes
to view Notes board of the School
Management System. He should be must login
to his account.
 The Student should be click at Notes
board button at his own page after login.

Post Condition When the Student was successful clicks on


Notes board button then he can view his notes
board information.

12
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

View Notes board

Use Case Description

Use Case ID UC- 5


Use Case This use case describes how the Admin can
Description manage all user accounts (Teacher, Student,
Parents) in School Management System.
Use Case Name Manage User Accounts.
Primary Actor Admin
Trigger When Admin click on the Manage User
Accounts button.
Pre-Condition Admin must be at the Admin page by login.
Basic Flow This use case starts when the Admin wishes to
Insert, Update, Delete & View all User
Accounts of School Management System.
 System request that the Admin should be
at his Admin page.
 When the Admin clicks on manage users
accounts a dropdown list shows the
Name of users (Teacher , Students ,
Parents)
 Admin should be select any users from
dropdown list their will be open a new
page of that users then he can perform
insert, update, delete functions.
Post Condition When the Admin was successful to Insert,
Update or delete any users, then he cans
logged.
Manage User Accounts

Use Case Description

Use Case ID UC- 6


Use Case This use case describes how the Admin can
13
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Description manage class routine in School Management


System.
Use Case Name Manage Class Routines.
Primary Actor Admin
Trigger When Admin click on the Manage Class
Routine button.
Pre-Condition Admin must be at the Admin page by login.
Basic Flow This use case starts when the Admin wishes to
manage class routine of School Management
System.
 System request that the Admin should be
at his Admin page.
 When the Admin clicks on manage class
routine a dropdown list shows the Name
of All classes.
 Admin should be select any class from
dropdown list their will be open a new
page of that class then he can perform
insert, update, delete functions at class
routine time table.
Post Condition When the Admin was successful to Insert,
update or delete class routine then he can
logout.
Manage Class Routines

Use Case Description

Use Case ID UC- 7


Use Case This use case describes how the Admin can
Description manage all exam results of School
Management System.
Use Case Name Manage Exam Results
Primary Actor Admin
Trigger When Admin click on the Exam Results

14
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

button.
Pre-Condition Admin must be at the Admin page by login.
Basic Flow This use case starts when the Admin wishes to
Insert, Update, Delete & View the results of
all students of any class in School
Management System.
 System request that the Admin should be
at his Admin page.
 When the Admin clicks on Exam Results
a dropdown list shows the Name of
Classes
 Admin should be select any class from
dropdown list their will be open a new
page of that class result then he can
perform insert, update, delete functions.
Post Condition When the Admin was successful to Insert,
update or delete results then he can logout.
Manage Exam Results

Use Case Description

Use Case ID UC- 8


Use Case This use case describes how the Admin can
Descriptions View the Student Attendance of School
Management System.
Use Case Name View Student Attendance
Primary Actor Admin
Trigger When Admin click on the Student
Attendance button.
Pre-Condition Admin must be at the Admin page by login.
Basic Flow This use case starts when the Admin wishes to
View the student attendance of any class in
School Management System.
 System request that the Admin should be

15
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

at his Admin page.


 When the Admin clicks on student
attendance button.
 There will be open a new page at this
page there should be enter date , class
and section and click on View button.
Then the attendance of entered class will
show billow.
Post Condition When the Admin was successful view the
attendance of any class then he can logout.
View Students Attendance

Use Case Description

Use Case ID UC- 9


Use Case This use case describes how the Admin can
Descriptions manage (Insert , Update , Delete , View) the
Student fee
In School Management System.
Use Case Name Manage Student Fee
Primary Actor Admin
Trigger When Admin click on the Student Fee button.
Pre-Condition Admin must be at the Admin page by login.
Basic Flow This use case starts when the Admin wishes to
Insert, Update , Delete & View the Fee of any
class of any month in School Management
System.
 System request that the Admin should be
at his Admin page.
 When the Admin clicks on student fee
 there will be open a new page, at this
page there must be Select Month , class
and section from dropdown list and click
on Insert, Update , Delete & View

16
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

button. There will be show below fee of


all student of that class to perform.
Post Condition When the Admin was successful to Insert ,
update , delete or View Student fee then he
can logout.
Manage Student Fee

Use Case Description

Use Case ID UC- 10


Use Case This use case describes how the Admin can
Descriptions manage (Insert , Update , Delete , View) the
Student fee
In School Management System.
Use Case Name Manage Student Fee
Primary Actor Admin
Trigger When Admin click on the Student Fee button.
Pre-Condition Admin must be at the Admin page by login.
Basic Flow This use case starts when the Admin wishes to
Insert, Update, Delete & View the Fee of any
class of any month in School Management
System.
 System request that the Admin should be
at his Admin page.
 When the Admin clicks on student fee
 there will be open a new page, at this
page there must be Select Month , class
and section from dropdown list and click
on Insert, Update , Delete & View
button. There will be show below fee of
all student of that class to perform.
Post Condition When the Admin was successful to Insert,
update, delete or View Student fee then he can
logout.
17
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Manage Student Fee

Use Case Description

Use Case ID UC- 11


Use Case This use case describes how the Admin can
Descriptions manage (Insert , Update , Delete , View) the
Student fee
In School Management System.
Use Case Name Manage Student Fee
Primary Actor Admin
Trigger When Admin click on the Student Fee button.
Pre-Condition Admin must be at the Admin page by login.
Basic Flow This use case starts when the Admin wishes to
Insert, Update, Delete & View the Fee of any
class of any month in School Management
System.
 System request that the Admin should be
at his Admin page.
 When the Admin clicks on student fee
 there will be open a new page, at this
page there must be Select Month , class
and section from dropdown list and click
on Insert , Update , Delete & View
button. There will be show below fee of
all student of that class to perform.
Post Condition When the Admin was successful to Insert.
Update, delete or View Student fee, then he
cans logout.
Manage Student Fee

Use Case Description

Use Case ID UC- 12

18
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Use Case This use case describes how the Teacher can
Descriptions Upload student result In School Management
System.
Use Case Name Upload result
Primary Actor Teacher
Trigger When Teacher click on the Upload result
button.
Pre-Condition Teacher must be at the Teacher page by login.
Basic Flow This use case starts when the Teacher wishes
to insert the student result of any class in
School Management System.
 System request that the Teacher should
be at the teacher home page.
 When the teacher clicks on upload
result button
 There will be open a new page, at this
page there must be enter year, class and
section and click on Insert button. There
will be show bellow insert result form.
Post Condition When the Teacher was successful to Insert
result, then he cans logout.
Upload Result

Use Case Description

Use Case ID UC- 13


Use Case This use case describes how the Teacher can
Descriptions Mark attendance In School Management
System.
Use Case Name Mark attendance
Primary Actor Teacher
Trigger When Teacher click on the Mark Attendance
button.
Pre-Condition Teacher must be at the Teacher page by login.

19
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Basic Flow This use case starts when the Teacher wishes
to mark attendance of any class in School
Management System.
 System request that the Teacher should
be at the teacher home page.
 When the teacher clicks on mark
attendance button
 There will be open attendance page , at
this page there must be enter date , class
and section and click on Insert button.
There will be show bellow attendance
form with save button.
Post Condition When the Teacher was successful to save
result, then he cans logout.
Mark Attendance

Use Case Description

Use Case ID UC- 14


Use Case This use case describes how the Student can
Descriptions View his attendance status In School
Management System.
Use Case Name View Attendance
Primary Actor Student
Trigger When Student click on the View attendance
button.
Pre-Condition Student must be at the Student home page by
login.
Basic Flow This use case starts when the Student wishes
to view his/her attendance status in School
Management System.
 System request that the Students should
be at the Student home page.

20
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

 When the Student clicks on View


attendance button
 There will be open a new page, at this
page there must be select month and
click on Attendance button. There will
be show bellow present and absents of
this student
Post Condition When the Student was successful to View
Attendance then he can logout.

View Attendance

Use Case Description

Use Case ID UC- 15


Use Case This use case describes how the Student can
Descriptions View his exam results In School Management
System.
Use Case Name View exam results
Primary Actor Student
Trigger When Student click on the View exam result
button.
Pre-Condition Student must be at the Student home page by
login.
Basic Flow This use case starts when the Student wishes
to view his/her exam result status in School
Management System.
 System request that the Students should
be at the Student home page.
 When the Student clicks on View exam
result button
 there will be open a new page, at this
page there must be enter class & roll
number and click on result button. There
21
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

will be show bellow result of this student


Post Condition When the Student was successful to View
result, then he cans logout.
View Exam Results

Use Case Description

Use Case ID UC- 16


Use Case This use case describes how the Student can
Descriptions submit application for leave In School
Management System.
Use Case Name Request for leave
Primary Actor Student
Trigger When Student click on the request for leave
button.
Pre-Condition Student must be at the Student home page by
login.
Basic Flow This use case starts when the Student wishes
to send application for leave to admin in
School Management System.
 System request that the Students should
be at the Student home page.
 When the Student clicks on Application
button
 There will be show bellow text area for
write application with send button.
Post Condition When the Student was successful to send
application, then he cans logout.
Request for Fee

Use Case Description

Use Case ID UC- 17


Use Case This use case describes how the Student can

22
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Descriptions View class routine In School Management


System.
Use Case Name View class routine
Primary Actor Student
Trigger When Student click on the View class routine
button.
Pre-Condition Student must be at the Student home page by
login.
Basic Flow This use case starts when the Student wishes
to view class routine in School Management
System.
 System request that the Students should
be at the Student home page.
 When the Student clicks on View class
routine button
 There will be open a new page, at this
page there must be select class and click
on View button. There will be show
bellow class time table or routine
Post Condition When the Student was successful to View
class routine, then he cans logout.
View Class Routine

Use Case Description

Use Case ID UC- 18


Use Case This use case describes how the Parent can
Descriptions View there children exam results In School
Management System.
Use Case Name View exam results
Primary Actor Parents
Trigger When Parent click on the View exam result
button.
Pre-Condition Parent must be at the Parent home page by

23
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

login.
Basic Flow This use case starts when the Parent wishes to
view his/her children exam result status in
School Management System.
 System request that the Parent should be
at the Parent home page.
 When the Parent clicks on View exam
result button
 there will be open a new page, at this
page there must be enter class & roll
number and click on result button. There
will be show bellow result of this student
Post Condition When the Parent was successful to View
result, then he cans logout.
View Exam Results

Use Case Description

Use Case ID UC- 19


Use Case This use case describes how the Parents can
Descriptions View class routine of their children In School
Management System.
Use Case Name View class routine
Primary Actor Parents
Trigger When Parents click on the View class routine
button.
Pre-Condition Parents must be at the parent home page by
login.
Basic Flow This use case starts when the Parent wishes to
view class routine in School Management
System.
 System request that the Parents should
be at the Parent home page.

24
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

 When the Parent clicks on View class


routine button
 There will be open a new page, at this
page there must be select class and click
on View button. There will be show
bellow class time table or routine
Post Condition When the parents were successful to View
class routine, then he cans logout.
View Class Routine

Use Case Description

Use Case ID UC- 20


Use Case This use case describes how the Parents can
Descriptions View his/her children attendance status In
School Management System.
Use Case Name View Attendance
Primary Actor Parents
Trigger When Parents click on the View attendance
button.
Pre-Condition Parents must be at the Parent home page by
login.
Basic Flow This use case starts when the Parent wishes to
view his/her children attendance status in
School Management System.
 System request that the Parent should be
at the Parent home page.
 When the Parent clicks on View
attendance button
There will be open a new page, at this
page there must be select month and
click on Attendance button. There will
be show bellow present and absents of
their children.

25
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Post Condition When the Parents was successful to View


Attendance then he can logout.
View Attendance

CHAPTER 2
Planning the Project

26
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

2.1 - Introduction of the Planning Phase


The planning phase illustrates the methodology adopted for the project and how the
project is scheduled. It includes existing methodologies, adopted methodologies and
reasons to choose the methodology. It also includes a Gantt chart to show how the project
is scheduled.
The planning phase is the most critical step in completing development,
acquisition, and maintenance projects. Careful planning, particularly in the early stages of
a project, is necessary to coordinate activities and manage project risks effectively. The
depth and formality of project plans should be commensurate with the characteristics and
risks of a given project. Project plans refine the information gathered during the
initiation phase by further identifying the specific activities and resources required to
complete a project.
Software project planning is an activity carried out by the project manager to
estimate and address Software scope estimation, Resource requirement, Time requirement,
and Structural decomposition and Risk analysis and planning. Software scope describes the
data and control to be processed, function, performance, constraints, interfaces, and
reliability. Determination of the software scope is a prerequisite of all sorts of estimates,
including, resources, time, and budget.
As this is an educational project so planning phase does not cover financial aspects
and risk management. Other aspects like time requirement, structural decomposition and
software life cycle methodologies are covered in detail in this document.

2.2 - Methodologies

2.2.1 - Existing Methodologies

Many methodologies have been evolved for the development of the Software system. All
of them have certain advantages and disadvantages and are appropriate in certain
circumstances and nature of software systems. A few of them include Build and fix model,
Waterfall model, Rapid prototyping mode, Incremental model, Extreme programming,
Synchronize and stabilize model, spiral model. Here is some detail of them.

2.2.1.1 - Build and Fix Model

27
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

This is the simplest model of software development; the system is constructed with
minimal requirements and generally with no specification. This is the mostly used
approach. There is just a main loop of development and feedback, the system is continually
modified according to the feedback of the client.

2.2.1.2 - Rapid Prototyping Model

The Rapid Prototyping Model is used to overcome issues related to understanding


and capturing of user requirements. In this model a mock-up application is created
“rapidly” to solicit feedback from the user. Once the user requirements are captured in the
prototype to the satisfaction of the user, a proper requirement specification document is
developed and the product is developed from scratch.
An essential aspect of rapid prototype is embedded in the word “rapid”. The
developer should endeavor to construct the prototype as quickly as possible to speed up the
software development process. It must always be kept in mind that the sole purpose of the
rapid prototype is to capture the client’s needs; once this has been determined, the rapid
prototype is effectively discarded. For this reason, the internal structure of the rapid
prototype is not relevant.

2.2.1.3 - Synchronize and Stabilize Model:

This is yet another form of incremental model adopted by Microsoft. In this model,
during the requirements analysis interviews of potential customers are conducted and
requirements document is developed. Once these requirements have been captured,
specifications are drawn up. The project is then divided into 3 or 4 builds. Each build is
carried out by small teams working in parallel. At the end of each day the code is
synchronized (test and debug) and at the end of the build it is stabilized by freezing the
build and removing any remaining defects. Because of the synchronizations, components
always work together. The presence of an executable provides early insights into operation
of product.

28
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

2.2.1.4- Spiral Model:

This model was developed by Barry Boehm. The main idea of this model is to avert
risk as there is always an element of risk in development of software. For example, key
personnel may resign at a critical juncture, the manufacturer of the software development
may go bankrupt, etc.

In its simplified form, the Spiral Model is Waterfall model plus risk analysis. In this case
each stage is preceded by identification of alternatives and risk analysis and is then
followed by evaluation and planning for the next phase. If risks cannot be resolved,
project is immediately terminated.

2.2.2 - Adopted Methodology

The adapted methodology for the current project is the Hybrid Process model.
Hybrid Process model is a combination of the waterfall and spiral models.

29
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

The Waterfall Model is a documentation-driven model. It therefore generates


complete and comprehensive documentation and hence makes the maintenance task much
easier. It however suffers from the fact that the client feedback is received when the
product is finally delivered and hence any errors in the requirement specification are not
discovered until the product is sent to the client after completion. This therefore has major
time and cost related consequences.
In its simplified form, the Spiral Model is Waterfall model plus risk analysis. In this
case each stage is preceded by identification of alternatives and risk analysis and is then
followed by evaluation and planning for the next phase. If risks cannot be resolved,
Project is immediately terminated.
The LLU Process model uses both of these models the waterfall model and the
spiral model. In fact the spiral model already contains the waterfall model.

2.2.3 - Reasons for choosing the Methodology

The drawbacks with the waterfall model are due to the fact that the entire product is
developed and delivered to the client in one package. This results in delayed feedback from
the client. Because of the long elapsed time, a huge new investment of time and money
may be required to fix any errors of omission or commission or to accommodate any new
requirements cropping up during this period. The Hybrid Process model can be used to
overcome these issues.

30
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

s2.4 Gantt chart:

31
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

2.5 Project Structure:

Team and structure:

There are four members in the team and software development activities are distributed
according to the team structure shown below:

32
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

CHAPTER 3
Designing the Project

33
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

3.1 – Introduction to Design Phase


Design and analysis phase is the key stage in the development of the project. This provides
the real architecture, flow and database design of the project. It includes data flow diagram,
activity diagram, sequence diagram, ER Diagram, Architecture diagram etc. All of these
describe functionally and design of the proposed system.
The purpose of the design phase of a project is to plan out a system that meets the
requirements defined in the analysis phase. In the design phase, the project team defines
the means of implementing the project solution – how the product will be created.
Design phase provide the project team with a means for assessing the quality of the
solution before it has been implemented, when changes are still easy to make and are less
costly.

3.2 - Overview
The project is a web Application that is to be hosted on a web server.
Any Student/Person will be able to access the web application by using internet. This web
application will facilitate the Student/Person can visit this web application and apply online
for school admission and Teacher mark attendance and upload result. Student and Parent’s
can view attendance and results online .After the admission and registration give the user
name and password to the student. Students and there parents view student reports results
and attendance). And Student can send leave application online.

34
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

3.3 - Data Flow Diagrams (DFD)

Data Flow Diagram

35
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

3.4 - Entity Relationship Diagram (ERD)


Entity Relationship Diagram

36
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

37
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Entity Relationship Diagram

38
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

1.5 - Activity Diagrams

Activity diagrams are graphical representations of workflows of stepwise


activities and actions with support for choice, iteration and concurrency. In
the Unified Modeling Language, activity diagrams are intended to model both
computational and organizational processes (i.e. workflows). Activity diagrams
show the overall flow of control.

Admin

39
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Teacher

40
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Parent

41
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Student

42
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

3.6 Sequence Diagrams


A Sequence diagram is an interaction diagram that shows how objects operate
with one another and in what order. It is a construct of a Message Sequence
Chart. A sequence diagram shows object interactions arranged in time sequence.
It depicts the objects and classes involved in the scenario and the sequence of
messages exchanged between the objects needed to carry out the functionality of
the scenario. Sequence diagrams are typically associated with use case
realizations in the Logical View of the system under development. Sequence
diagrams are sometimes called event diagrams or event scenarios.

Sequence Diagram

3.7 - Class Diagram

43
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

The class diagram is a static diagram. It represents the static view of


an application. Class diagram is not only used for visualizing,
describing and documenting different aspects of a system but also for
constructing executable code of the software application.

The class diagram describes the attributes and operations of a class


and also the constraints imposed on the system. The class diagrams
are widely used in the modeling of object oriented systems because
they are the only UML diagrams which can be mapped directly with
object oriented languages.

Class Diagram

3.8 - Database Design

Database design is the process of producing a detailed data model of database.


This data model contains all the needed logical and physical design choices and

44
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

physical storage parameters needed to generate a design in a data definition


language, which can then be used to create a database.

Database Diagram

3.9 - Interface Design


Index page

45
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Home page 2

Parent home page

46
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Student home page

Teacher Panel

47
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

View exam result

View Attendance

48
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Manage exam result

Monthly fee

49
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Manage classes

Generate Report

50
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Exam Result

Class Routine

51
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Assign Section

Admin Home Page

52
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Monthly Fee

53
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

CHAPTER 4
Development

54
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

s4.2 - Test Cases


Test Case # 1:
Title Testing of new user registration in web application
Preconditions The web application is displayed
Actions 1. Click on the apply Button
2. Enter the data in all fields
3. Click Submit button
Expected Results Data is saved in database and confirmation screen is opened
Tested By Junaid Shafique
Result Pass

Test Case # 2:
Title Testing the login process of web application
Preconditions A user account already has been created
Actions 1. Click on the Login Button
2. Enter user id and password
3. Click OK button
Expected Results Session is started and welcome screen opens
Tested By Sadia Aslam
Result Pass

55
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Test Case # 3:
Title Testing of View Attendance
Preconditions The user is logged in
Actions 1. Click Attendance Button
2. Enter roll num , name , class
3. Press Submit Button
Expected Results Data is appears in the screen.
Tested By Neelam Mubarak
Result Pass

Test Case # 4:
Title Testing of update Teacher
Preconditions Admin is logged in
Actions 1. Click on manage teacher button
2. Enter the data in all fields
3. Click Update button
Expected Results Data should be saved and teacher update screen should appear
Tested By Sadia aslam
Result Pass
Test Case # 5:
Title Test of view result
Preconditions The user is logged in
Actions 1. Click on the result button
2. Enter roll num , name , class , section
3. Click on submit button
Data is appeared in the screen
Expected Results
Tested By Junaid Shafique
Result Pass

Test Case # 6:
Title Test of viewing class routine
Preconditions User logged in
Actions 1. Click on the class routine button
2. Enter roll num , name , class
3. Click on submit button
Expected Results Data is appeared on the screen
Tested By Sadia Aslam
Result Pass

Test Case # 7:
Title Test Viewing fee structure
Preconditions User logged in
Actions 1. Click on the fee button

56
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

2. Enter class id , section


3. Click on submit button
Expected Results Fee is appeared on the screen
Tested By Neelam Mubarak
Result Pass

Test Case # 8:
Title Test add student
Preconditions Admin is logged in
Actions 4. Click on the manage student button
5. Enter the data in all fields
6. Press submit button
Expected Results Student add in the specific class
Tested By Junaid shafique
Result Pass

Test Case # 9:
Title Test mark Attendance
Preconditions Teacher logged in
Actions 1. Click attendance button
2. Select date
3. Mark attendance of a class
4. Press submit button

Expected Results Appeared message the data is saved


Tested By Neelam Mubarak
Result Pass

57
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

CHAPTER 5
Deployment

58
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

5.1 Deployment Diagram


The deployment diagram specifies a set of constructs that can be used to define the
execution architecture of system that represent the assignment of software artifacts to
nodes. Nodes are connected through communication paths to create network systems of
arbitrary complexity.

59
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Deployment Diagram

References

Software Engineering: A Practitioner's Approach”, 5th/Ed , McGraw-Hill, 2001.


Craig Lawman (2001), “Applying UML and Patterns: An Introduction to Object-
Oriented Analysis and Design and the Unified Process”, 2nd /ed., Prentice Hall PTR,
2001.

60
Division of Science & Technology Township Campus Lahore
SCHOOL MANAGEMENT SYSTEM

Wendy Boggs, Michael Boggs (2002), “Mastering UML with Rational Rose 98, Sybil,
and ISBN: 0782140173.
Timothy Let bridge, Robert Lagan ere (2002), “Object-Oriented Software
Engineering: Practical Software Development using UML and Java”, McGraw-Hill,
2002.
Peter Rob, Database Systems (Paperback), Thomson Learning, International edition
2008.
Peter Rob, Carlos Coronel, Database Systems: Design, Implementation, and
Management, Course Technology; 8 edition, 2007.
C. J. Date “Database Systems”, Addison-Wesley 1994.
Joseph Phillips, “IT Project Management: On Track from Start to Finish”, McGraw-
Hill, 2004.
Carl Chatfield, Timothy Johnson, Microsoft® Office Project 2007 Step by Step (Step
By Step (Microsoft)) Microsoft Press, 2007.
http://www.w3school.com
American lyceum School management System

Beacon house school management system

61
Division of Science & Technology Township Campus Lahore

You might also like