SRS On OSMS

SRS ON ONLINE
SCHOOL
MANAGEMENT
SYSTEM
Software
Project
Lab-2
Title: Online School Management

System
Group Member:
Nowrose Ashraf
Supervisor:
Emon Kumar Dey
Lecturer
Institute of Information Technology
University of Dhaka
Submission Date:
th
29 Mar, 2014
Contents
Chapter 1....................................................................................................................................... 1
1.1 Introduction........................................................................................................................ 1
1.2 Purpose................................................................................................................................2
1.3 Goals.................................................................................................................................... 2
Chapter 2....................................................................................................................................... 3
2.1 Introduction........................................................................................................................ 3
2.2 Identifying Stakeholders..................................................................................................3
2.3 Recognizing multiple viewpoints................................................................................... 5
2.4 Working towards collaboration.......................................................................................6
2.5 Common requirements.................................................................................................... 6
2.6 Conflicting Requirements................................................................................................ 6
2.7 Final requirements............................................................................................................ 7
2.8 Conclusion...........................................................................................................................7
3.1 Introduction........................................................................................................................ 8
3.2 Eliciting Requirements..................................................................................................... 8
3.3 Collaborative Requirements Gathering........................................................................9
3.3.1 Requirement elicitation through interview...........................................................9
3.3.2 Requirement elicitation through questioning
................................................................................................................................................
10
3.3.3 Record view
................................................................................................................................................
10
3.3.4 Observation
................................................................................................................................................
10
3.4 Quality Function Development
....................................................................................................................................................
10
3.4.1 Normal Requirements
................................................................................................................................................
11
3.4.2 Expected Requirements
................................................................................................................................................
11
3.5. Case Scenario
....................................................................................................................................................
12
3.5.1. Registering Online
................................................................................................................................................
12
3.5.2. Admission
................................................................................................................................................
12
3.5.3 Student database generation
................................................................................................................................................
13
3.5.4 Attendance sheet generation
................................................................................................................................................
13
3.5.5 Result sheet generation
................................................................................................................................................
13
3.5.6 Annual report generation
................................................................................................................................................
13
Chapter 4
.......................................................................................................................................................
14
4.1 What is usecase diagram?
....................................................................................................................................................
14
4.2 Usecase Diagram
....................................................................................................................................................
15
4.3 Activity Diagram and Swimlane Diagram
....................................................................................................................................................
31
4.3.1 Activity Diagram
................................................................................................................................................
31
4.3.2 Swimlane Diagram
................................................................................................................................................
39
Chapter 5
.......................................................................................................................................................
47
5.1 Data Modeling Concept
....................................................................................................................................................
47
5.3 Data Relationship Diagram
....................................................................................................................................................
51
5.4Entity Relationship(ER) Diagram
....................................................................................................................................................
52
5.4 Table Schema Diagram
....................................................................................................................................................
54
Chapter 6
.......................................................................................................................................................
56
6.1 Class Based Modeling Concept
....................................................................................................................................................
56
6.2 Identifying Analysis Classes
....................................................................................................................................................
56
6.3
Class Schema Diagram
....................................................................................................................................................
58
6.4 Class Responsibility Collaboration (CRC)
....................................................................................................................................................
59
6.5
Class Card
....................................................................................................................................................
60
Chapter 7
.......................................................................................................................................................
62
7.1 Introduction
....................................................................................................................................................
62
7.2 Data Flow Design (DFD)
....................................................................................................................................................
62
Chapter 8
.......................................................................................................................................................
70
8.1 State diagram
....................................................................................................................................................
71
8.2 Sequential model
....................................................................................................................................................
76
Chapter 9
.......................................................................................................................................................
80
3.3.2 Requirement elicitation through questioning
A questionnaire is a convenient way for the analyst to contact a large number of persons to get
views about various aspects of the system. Wide distribution ensures that the respondent has
great anonymity.
3.3.3 Record view
A good volume of records and reports are often available, which provide useful information
about the existing system. The term record refers to the written policy manuals, regulations
and standard operating procedures.
3.3.4 Observation
Observation as a fact-finding technique is widely accepted by scientist, sociologists,

psychologists and industrial engineers. Observation provides first-hand information about
how activities are carried out.
3.4 Quality Function Development

Quality function deployment (QFD) is a quality management technique that translates the needs of
the customer into technical requirements for software. QFD concentrates on maximizing customer
satisfaction from the software engineering process. QFD consists of two components which are
traced into the design process: quality and function. The quality deployment component brings the
customers voice into the design process. The "function deployment" component links different
organizational functions and units into to the design-to-manufacturing transition via the formation of
design teams. QFD identifies three types of requirements
10 | P a g
e
3.4.1 Normal Requirements
Accessible via the Internet.
Time and Money consuming system.
Keep attendance record.
Generate automatic result sheet.
Generate automatic annual report.
3.4.2 Expected Requirements
Mobile transaction
Mobile notification
The system shall enable the Administrator to change any database.(password, PIN)
The system shall automatically send e-mail and SMS to the user when a task is forwarded
The user interface of the system shall be easy to use and shall make use
11 | P a g
3.5. Case Scenario

This project will contain the Online School Management system. The process will be done online
as much as possible.
3.5.1. Registering Online
The whole process starts with the applicant registering online. An applicant will go to the School
web interface and he/she will click 'Admission Form' to open up the form. There will be a
manual instruction. He has to read it carefully then follow the instruction.
At first he has to pay registration fee to a particular mobile. Then he will get a pin number.
He has to fill the online registration form with the pin. If he does not give pin number he cannot
registration. The form contains the following fields:
Name, mobile numbers, address, email Id.
After successful registration student data will keep in a temporary database.
3.5.2. Admission
After successful registration student will ask for admission via mobile message.
He can get admission information in school website also. He will ask for viva exam. From the
exam school authority will select student .selected student will have unique id and selection
information will send to individual student via their mobile. Student can also get selection result
in school website.
Selected student will call for admission. Student will pay tuition fee and sure their admission.
After successful admission student data will store in permanent database.
12 | P a g
e
3.5.3 Student database generation
From permanent database DBA will make class wise student database. This database will
contain:
Student name, id, roll, class, section, email id etc.
DBA will add attendance table, result table, payment table in the database.
3.5.4 Attendance sheet generation
In every day in first class teacher will login in the system. There will be a attendance sheet in
the software. Teacher will take attendance in that attendance sheet. After complete attendance he
will press ok button on attendance sheet. When DBA will see that attendance sheet DBA press
ok button then attendance data will store in student attendance sheet database. Finally at the end
of class period we will generate digital attendance sheet from attendance data.
3.5.5 Result sheet generation
After every exam teacher or Office Stuff will entry student result in Online Result sheet. When
the work will complete DBA will store result data in database.
From the database DBA will generate Result sheet.
3.5.6 Annual report generation
At the end of year DBA will generation Annual report from student database.
13 | P a g
e
Chapter 4
Scenario-based modeling of Online School Management System
This chapter describes the scenario-based modeling of Online School Management System.
4.1 What is usecase diagram?

A use case diagram is a graphic depiction of the interactions among the elements of a system. 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 diagrams are employed in
UML (Unified Modeling Language), a standard notation for the modeling of real-world objects
and systems. A usecase diagram looks something like a flowchart. A use case diagram contains
some components.
The actors, usually individuals involved with the system defined according to their roles.
The use cases, which the specific roles are played by the actors within and around
the system.
The relationships between and among the actors and the use cases.
In Online School Management System the usecase diagram represents the whole process and
activities done before admission test.
For scenario-based modeling a complete scenario is needed to describe the Online School
Management System in words. Then actors are to be identified from the scenario.
These actors are of two types.
Primary actor.
Secondary actor.
Primary actor: The actors those both produce and consume information of a system.
Secondary actor: The actors those either produce or consume information of a system.
14 | P a g
4.2 Usecase Diagram
Registration
Admission
Teacher
Student
Authentication
Generating student Database
DBA
Attendance and result store
Result publication
Mobile
operator
Clark
Annual report generation
Figure 4.1: Level 0 (School management system)
15 | P a g e
Level 0:
Use case: Online school management system
Primary actors: DBA, student
Secondary actors: Teacher, mobile operator, office clerk
16 | P a g e
Goto website
DBA
Follow the instruction
Pay registration fee

Student
Download registration form

Mobile
operator
Submit registration form with

PIN
Store data in temporary DB
Figure 4.2: Level 1.1 (Registration)
17 | P a g e
Level 1.1:
Use case: Registration
Primary actors: DBA, student
Secondary actors: Teacher, mobile operator, office clerk
Action and Reply:
Student :
Action: Enter roll, pin
Reply: Entered/not entered
Mobile operator:
Action: receive message
Reply: sent/not sent
Action: sent PIN Reply:
sent/not sent
Teacher:
Action: Receives result

Reply: Received/not received
Action: verifies result with obtained marks
Reply: correct/not correct
Action:
sends
approval
message Reply: sent/not sent
Exceptions:
1. Messages are not sent. Sends confirmation message.
2. Violation of information security. Each user can access system through
authentication.
18 | P a g
e
Call for interview
Select student
Office clark
Student
Pay admission fee
Admit into school

DBA
Student info store in DB
Teacher
Figure 4.3: Level 1.2 (Admission)
19 | P a g e
Level 1.2:
Use case: Admission
Primary actor: DBA, student, Teacher
Secondary actor: office clerk, mobile operator
Action and Reply:
DBA:
Action: receives data from admission
office. Reply: received/not received
Action: accumulates result
Reply: done/not done
Action: stores result in TDB
Reply: stored/not stored
Exceptions:
1. Collected results are not appropriate. Send feedback for correction.
2. Results are not stored in database.
20 | P a g e
Enter ID,Password
Teacher
Login
DBA
Log out
Office clark
Figure 4.4: Level 1.3 (Authentication)
21 | P a g e
Level 1.3:
Use case: Authentication
Primary actor: DBA
Secondary actor: Teacher, office clerk, mobile operator
Action and Reply:
Action: Enter password

Reply: Entered / not entered
Action: Verify password
Reply: Correct / incorrect
Action: Log in
Reply:
Successful
/
password
mismatch Action: Log out
Reply: done /not done
Exceptions:
1. Password incorrect. Show retry message.
2. Unauthorized user.
3. Error in password verification system. Stops access in the system.
22 | P a g e
Get data from temporary

database
Classify them class wise

DBA
Generate class wise student

permanent DB
Figure 4.5: Level 1.4 (Geneate student DB)
23 | P a g e
Level 1.4:
Use case: Generate student DB
Primary actor: DBA
Secondary actor: Student, Teacher, office clerk, mobile operator
Action and Reply:
DBA:
Action: Receive roll from mobile operator
Reply: Received / not received
Action: Verify roll
Reply: Verified / not verified
Action: Send result to Mobile operator
Reply: Sent / not sent
Mobile operator :
Action: Receive request message

student Reply: Received/ not received
Action: Send roll to dean of unit
office Reply: Sent/ not sent
Action: Send request back message
from
Exceptions:
1. Error while sending message. Sends feedback about message sent.
2. Roll number mismatch can occur. Shows mismatch message.
24 | P a g e
Get daily attendance
Teacher
Store in permanent DB
DBA
Generate attendance sheet
Figure 4.6: Level 1.5(Geneate attendance sheet)
25 | P a g e
Level 1.5:
Use case: Attendance sheet generation
Primary actor: office clerk, DBA
Action and Reply:
DBA:
Action: Receive attendance from Database
Reply: Received / not received
Action: Verify ID
Reply: Verified / not verified
Action: Send to office clerk
Reply: Sent / not sent
Teacher :
Action: Receive data from

student Reply: Received/ not
received Action: Send to database
Reply: Sent/ not sent
Exceptions:
1. Error while sending message. Sends feedback about message sent.
2. Roll number mismatch can occur. Shows mismatch message.
26 | P a g e
Get result form teacher
Teacher
DBA
Generate class wise result
DBA
Publish result
Figure 4.7: Level 1.6(Result publication)
27 | P a g e
Level 1.6:
Usecase: Result publication
Primary actor: DBA, Teacher
Secondary actor: Student, Office clerk
Action and Reply:
All actor:
Action: Receive result
Reply: store result
Exceptions:
1. All submit result are not collect properly.
2. Violation of information security. Each user can access system through
authentication.
3. Result is not verified properly. DBA again verifies it.
28 | P a g
e
Get attendance sheet
Get result sheet
Teacher
Get student class performance

DBA
data combine and analysis
Generate annual report

Clark
Publish annual report
Figure 4.8: Level 1.7(Generating annual report)
29 | P a g e
Level 1.7:
Use case: Generating annual report
Primary actor: DBA, office clerk
Secondary actor: Student, teacher
Action and Reply:
DBA
Action: generate result
Reply: generated / not generated
Action: Verify roll, pin
Reply: Verified/ not verified
Action: Receive all data
Reply: Received/ not received
Exceptions:
1. Error in generating page. Regenerates page and verifies information.
2. All data are not found.
3. Error occurs while publishing result through web page.
30 | P a g e
4.3 Activity Diagram and Swimlane Diagram

4.3.1 Activity Diagram
Activity Diagram for Usecase level: 0
retransmission
Registration
Complete
registration
No
Prompt for re entry
Yes
Ask for admission test
Select and admitted
Retransmission
invalid
valid
Store student info into
permanent DB
Generate class wise student

database
Add attendance and result sheet
Generate attendance and result

report
31 | P a g e
Go to website
Pay registration feee

Pay
unsuccessful Show error message
Pay successful
Generate PIN
Get PIN
Download registration form
Fill eg. Form
Submit Reg. Form with

PIN
invalid
Promote for re entry
valid
Send confirmation
message
Store in temporary
database
32 | P a g e
Ask for interview
Select qualify student
Sent selection message
send failed
Show error message
send successful
Get selection message
Pay admission fee

Pay
unsuccessful
Show error message
Pay successful
Get admission fee
Admitted on the school
Store updated data on

permanent database
33 | P a g e
retransmission
Enter ID,password
invalid
valid
prompt for re entry
Log in into system
action:change
password
Change password
no entry remain
action:don't
change
password
Type current password
Type new password
Do other action
Password change
34 | P a g e
retransmission
Enter ID,password
invalid
Prompt for re entry
valid
Read info from permanent
database
Analysis information
generate class wise

database
Update database
Add attendance and result

table in database
35 | P a g e
retransmission
Enter ID,password
invalid
Prompt for re entry
valid
Collect daily attendance
Update database
retransmission
Send to DBA
send failed
Prompt for re send
successfully
send
Receive data
Generate attendance
sheet
36 | P a g e
retransmission
Enter ID,password
invalid
Prompt for re entry
valid
Collect subject wise
marks
retransmission
Send to DBA
send failed
Prompt for re send
send successfull
Result analysis
Generate class wise

result
Publish result
37 | P a g e
retransmission
Enter ID,password
invalid
Prompt for re entry
valid
from DB
Get result sheet DB

failed
Get student class
performance DB
successful
Analysis report and
combine
Store in permanent
database
publish annual report
38 | P a g e
4.3.2 Swimlane Diagram
Swimlane Diagram for Usecase level: 0
Student
Admission office
DBA
Teacher
retransmission
Registration
Prompt for re entry
No
Complete
registration
Yes
Ask for admission

test
Select and
admitted
valid
Retrans
mission
Store student info

into permanent DB
invalid
Add attendance
and result sheet
Generate class
wise student
database
Generate
attendance and
result report
Generate annual
report
39 | P a g
e
Applicant
Admission Office
Go to website
Pay registration fee

Pay
unsuccessful
Show error
message
Pay successful
Generate PIN
Send PIN
Get PIN
Generate Reg. Form
Download Reg. Form
Fill Reg. Form
Submit Reg. Form with

PIN
invalid
Promote for re entry
valid
Send confirmation
message
Store in temporary
database
40 | P a
ge
Applicant
Admission Office
Ask for interview
Select qualify student
Send selection message
send failed
suc
Get
selection
message
Pay
admission
fee
Show error message
c
e
s
s
f
u
l
l
y
s
e
n
d
pay unsucessfull
S
h
o
w
er
ro
r
m
e
ss
a
g
e
pay sucessfull
Get admission fee
A
d
m
i
t
t
e
d
o
n
t
h
e
s
c
h
o
o
l
a
t
a
o
n
p
e
r
m
a
n
e
n
t
d
a
t
a
b
a
s
e
S
t
o
r
e
u
p
d
a
t
e
d
d
41 | P a g e
DBA, Teacher,Clark
retransmission
Enter ID,password
invalid
valid
prompt for re entry
Log in into system
action:change
password
Change password
no entry remain
action:don't
change
password
Type current password
Type new password
Do other action
Password change
42 | P a g e
DBA
retransmission
Enter ID,password
invalid
Prompt for re entry
valid
Read info from permanent
database
Analysis information
generate class wise database
Update database
Add attendance and result table in

database
43 | P a g e
Teacher
DBA
retransmission
Enter ID,password
invalid
Prompt for re entry
valid
Collect daily attendance
Update database
retransmission
Send to DBA
send failed
Prompt for re send
Receive data
successfully
send
Generate attendance
sheet
44 | P a g e
Teacher
DBA
retransmission
Enter ID,password
invalid
Prompt for re entry
valid
Collect subject wise
marks
Send to DBA
retransmission
send failed
Prompt for re send
send successfull
Receive marks
Analysis result
Generate result
Publish result
45 | P a
ge
DBA,Teacher
retransmission
Enter ID,password
invalid
Prompt for re entry
valid
from DB
Get result sheet DB

failed
Get student class
performance DB
successful
Analysis report and
combine
Store in permanent
database
publish annual report
46 | P a g e
Chapter 5
Data Model of Online School Management System

5.1 Data Modeling Concept
Data modeling is the formalization and documentation of existing processes and events that
occur during application software design and development. Data modeling techniques and tools
capture and translate complex system designs into easily understood representations of the data
flows and processes, creating a blueprint for construction and/or re-engineering. In fact, the data
model simply describes the structure of data entities and their relationships.
In our Online School Management System, we have done the following activities as our
Data Model.
Data object identification and Define Attributes for each Data object.
Data Relationship Diagram.
ER Diagram
Table or Schema Generation
5.2 Data object and Attributes identification

A data object is a representation of information which has different properties or attributes that
must be understood by software. We have identified following data objects in our Online
Admission System.
Potential Data Object
General Classification
Student
School
Interface
Information
Results
Pin_number
Money
External entities, Roles

Organizational unit
Things
External entities, attributes of applicant
External entities
Things, events
None
47 | P a g
e
Text message
Attributes of mobile operator
Confirmation SMS
Transaction
Cell phone balance
Verification
Authentication
Instruction
temp_data_table
permanent_data_ta
ble
subject_wise_mark
attendance
payment
attendance
Attributes of mobile operator

Method of mobile operator
None
External entities, Events
External entities, Events
Methods of mobile operator
External Entities
External Entities
Things
External entities,Things
External entities,Things
Things , Events
Fig : 5.1 :Data Object Identification Table
Data Object: pin_number

Attributes:
pin
mobile_number
amount
Data Object: temp_data_table

Attributes:
Id
pin
name
mobile number
address
48 | P a g
e
Data Object: permanent_data_table

Attributes:
Id
Name
Class
Roll
mobile number
email id
Data Object: subject_wise_mark

Attributes:
Id
Roll
Class
Subject 1 mark
Subject 2 mark
Subject n mark
Total mark
Data Object: result

Attributes:
Id
Roll
Class
Total mark
GPA
49 | P a g e
Data Object: payment

Attributes:
Id
Roll
Class
amount
Data Object: attendance

Attributes:
Id
Roll
Class
Attendance
Data Object: Authentication

Attributes:
Id
Roll
Class
Attendance
50 | P a g e
5.3 Data Relationship Diagram
keep in
pin_number
keep in
temp_data_table
permanent_data
_table
has
permanent_data
_table
has
permanent_data
_table
has
temp_data_table
permanent_data
_table
result
attendance
payment
get from
result
51 | P a g e
subject_wise_mark
5.4Entity Relationship(ER) Diagram

ER Diagram shows the total picture of the interaction of data and it facilitates to construct
schema and database designing for the Online School Management System.
52 | P a g e
mobile_num
ber
pin
mobile_num
ber
pin
name
id
amount
address
pin_number
roll
id
temp_data_table
keep in
class
keep in
id
attendance
email
attendance
permanent_data_
table
has
name
class
result
id
mobile_num
ber
class
roll
subject_wise_mark
has
total_marks
id
roll
sub_n
sub_1
sub_2
payment
class
pament
id
roll
Fig 5: ER diagram
53 | P a g e
5.4 Table Schema Diagram
pin
int(20)
mobile_number
Int (20)
amount
Int (20)
Fig 5.4.1: pin_number
i
d
int(20)
mobile_numb
er
name
Int(20)
Varchar(30)
address
varchar(30)
pin
Int(20)
Fig 5.4.2: temp_data_table
pin
Int(20)
mobile_numb
er
Name
roll
Varchar(3
Int(20)
0)
Int(10)
id
Int(20)
address
email
Varchar(3 Varchar(3
0)
0)
Fig 5.4.3: permanent_data_table
id
Int (20)
Roll
Int(10)
class
Int(10)
Fig 5.4.4: Attendance
attendance
Varchar(10)
54 | P a g e
id
Int(20)
Roll
Int(10)
class
Int(10)
total_mark
Int(10)
Fig 5.4.5: Result
id
Int(20)
Class
Int(10)
roll
Int(10)
payment
Int(10)
Fig 5.4.6: Payment
id
Int(20)
sub_1
Int(10)
Sub_2
Int(10)
Fig 5.4.7: subject_wise_mark
Sub_n
Int(10)
55 | P a g
e
Chapter 6
Class Based Model of Online School Management System
This Chapter is intended to describe class based modeling of Online School Management
System
6.1 Class Based Modeling Concept

Class-based modeling represents the objects that the system will manipulate, the operations that
will applied to the objects, relationships between the objects and the collaborations that occur
between the classes that are defined.
6.2 Identifying Analysis Classes

Step 1: Identifying and categorize all nouns
External Entities: mobile operator, attendance, payment
Occurrence or events: registration, selection
Roles: office staff, DBA, teacher, student.
Places: school.
Structures: web interface, form, pin number
Step 2: Selection of potential class
Selection characteristics:
1. Retained information
2. Needed services
3. Multiple attributes
4. Common attributes
5. Common operations
6. Essential requirements
56 | P a g e
Potential Class
Accepted/Rejected
Student
All accepted
Web Interface
accept 1,3,4,5
Form
accept 1,3,4,5
Pin _number
accept 1,2,6
Registration
All accepted
Selection
All accepted
DBA
accept 1,5,6
Teacher
accept 1,5,6
Student
All accepted
Office Staff
Result
accept 1,5,6
All accepted
Attendance
accept 1,2,4,5,6
Payment
accept 1,2,4,5,6
Money
Mobile Operator
accept 2
accept 1,2
57 | P a g
e
6.3 Class Schema Diagram

Attribute Identification:
1. Registration= Id+mobile
2. Selection = Id+ Roll+name,+mobile
3. Payment = Id+ Roll+name
4. Attendance= Id+ Roll+name+roll
5. Result = Id+ Roll+name+roll
6. Student = Id+ Roll+name+roll
Method Identification:
Registration= get from() ,check from() ,confirm(),store()
Selection = Massaging(),Check payment(),Admit()
Payment = Check Payment(),Store database(),Confirmation()
Attendance= get Attendance(),store Attendance(),generate Attendance Sheet()
Result = Get Result(),Store Result(),Generate Result sheet()
Student = Annual report(),Upgrade()
58 | P a g e
6.4 Class Responsibility
Collabor
ation (CRC)
Registration
Selection
Id, mobile
Id, Roll, name, mobile
Payment
Id, Roll, name
get from()
check from()
Massaging()
confirm()
Check payment()
store()
Admit()
Check Payment()
Store database()
Confirmation()
Result
Attendance
student
Roll, class, name
Id, Roll, class
get Attendance()
Annual report()
store Attendance()
Upgrade()
generate
Attendance
Sheet()
Id, Roll, class, name

Get Result()
Store Result()
Generate Result
sheet()
59 | P a g e
6.5 Class Card
Class name: Registration

Responsibility
Collaboration
1.Form submission
Selection
2.Store data temp_database
Class name: Selection

Responsibility
Collaboration
1
. Select student
Registration
2
. Admit student
Class name: Payment

Responsibility
Collaboration
1. check payment
Student
2. store database
60 | P a g e
Class name: Attendance

Responsibility
Collaboration
1. Get attendance
Student
2.Generate attendance sheet
Class name: Result

Responsibility
Collaboration
1. Get result
Student
2.Generate result sheet
Class name: Student

Responsibility
Collaboration
1
. Keep all information
payment, attendance
,result
2
. Generate annual report
61 | P a g e
Chapter 7
Flow Oriented Model of Online School Management System
7.1 Introduction
We have almost described the Online School Management System up to last chapter. But Data
Flow Diagram (DFD) can play a vital role to visualize the system input and output. It is a
significant modeling technique for analyzing and constructing information processes. That is
why; we use DFD for the system in this chapter.
7.2 Data Flow Design (DFD)

The DFD takes an input-process-output view of a system. DFD literally means an illustration
that explains the course or movement of information in a process. DFD illustrates this flow of
information in a process based on the inputs and outputs.
In the figures, data objects are represented by arrows, external entities are boxes, transformations
are circle and storages are represented by double lines.
62 | P a g
e
Student
DBA
Online School
Management
Teacher
Databa se
System
OS
Fig 7.1: level 0 (Online School

Management System)
Student
DBA
input and accept
Database
Fig 7.2: level 1.1 ( Registration ) OSMS
Student
DBA
input and accept
OS
Fig 7.3: level 1.2 ( Admission ) OSMS
63 | P a g e
Database
Teacher
input and accept
Database
DBA
Fig 7.4: level 1.3 ( Authentication ) OSMS
DBA
input and accept
Database
Fig 7.5: level 1.4 ( Generate

student database ) OSMS
Teacher
input and accept
Database
DBA
Fig 7.6: level 1.5 ( Generate attendance

sheet ) OSMS
64 | P a g e
Teacher
input and accept
Database
DBA
Fig 7.7: level 1.6 ( Result publication )

OSMS
Teacher
input and accept
Database
DBA
Fig 7.8: level 1.7 (Generate annual report)

OSMS
Student
pay money
Database
DBA
send pin
Fig 7.9: level 2.1 ( Registration ) OSMS
65 | P a g e
Student
pay fee
OS
receive fee
DBA
store data
Database
Fig 7.10: level 2.2 ( Admission ) OSMS
Teacher
sign up
DBA
log in
log out
Database
Fig 7.11: level 2.3 ( Authentication )

OSMS
66 | P a g e
DBA
get student
info
Database
generate
database
analysis
data
Fig 7.12: level 2.4 ( generate student

database ) OSMS
67 | P a g e
Teacher
get student
attendance Database data
DBA
generate
attendance
sheet
store data
Fig 7.13: level 2.5 ( generate attendance

sheet ) OSMS
68 | P a g e
Teacher
get student
result data
DBA
Database
generate
result sheet
store data
Fig 7.14: level 2.6 (generate result sheet)

OSMS
get student
result data
database
Teacher
get student
class
performance
data
Teacher
generate
annual
report
store data
Fig 7.15: level 2.7 (generate annual report)
69 | P a g e
Chapter 8
Behavioral Model of Online School Management System

Behavioral model describes the control structure of a dynamic system. This can be things like:
Sequence of operations
Object states
and Object interactions
The behavioral model indicates how software will respond to external events or stimuli. We
represent behavioral model through two diagrams:
State Diagram
Sequence Diagram
Events
Generate application form
Initiator
Collaborator
DBA
Student
Form fill up
Student
DBA
Pay tuition fee
Student
OS,DBA
Get attendance
Teacher
DBA
Generate result
Teacher
DBA
Teacher, OS
DBA
Annual report generation

DBA: Database Administrator.
OS: Office Stuff
70 | P a g
8.1 State diagram

State diagram represents active states for each class and events that cause changes between the
active states. We illustrate our state diagram. We consider two different characterization of state:
a) The state of each class as the system perform its function
b) The state of the system as observed from the outside as the system performs its
function. The state of the class takes on both active and passive state.
71 | P a g e
Invalid
start
Forms fill up
Idle
Valid
Response via mobile
Authentication
Payment
Authentication
Result
Authentication
Attendance
End
Fig 8.1.1: State diagram(Online School

Management System)
72 | P a g e
Invalid
start
Idle
Forms fill up with PIN
Store in temp.
database
Valid
Store in parmanent
database
Pay admission fee
Response via
mobile
End
Fig 8.1.2: State diagram( Registration )
start
Idle
Idle
Authentication
Entry payment
Check payment
End
Fig 8.1.3: State diagram( Payment )
73 | P a g e
start
Idle
Authentication
Entry result
Store in database
End
Generate result sheet
Fig 8.1.4: State diagram(Result

generation)
start
Idle
Authentication
Generate attendance sheet
Entry attendance
Store in database
End
Fig 8.1.5: State diagram(Attendance sheet generation)
74 | P a g e
start
Idle
Authentication
Entry result
Entry attendance
Store in database
End
Fig 8.1.6: State diagram(Annual report generation)
75 | P a g e
8.2 Sequential model

Sequential model indicates how events cause transition from object to object.
We have identified every event by examining use case. Being modeler, we have created the
sequence diagram. It represents how events cause flow from one object to another as a function
of time.
76 | P a g e
Student
payment
DBA
Database
pay reg istr ation fee
give PIN
IN
dP
e
store in database
form fill up
Fig 8.2.1: Sequence diagram (Registration)
77 | P a g e
Student
OS
Database
payment
pay registr ati on fee

store in database
s t o r e i n
database
Fig 8.2.2: Sequence diagram(Admission)
78 | P a g e
Teacher
get attendance
Database
store
attendance
store in database
Fig 8.2.3: Sequence diagram(Attendance)
Teacher
Database
get result
store result
store in dat abase
Fig 8.2.4: Sequence diagram(Result)
79 | P a g e
Chapter 9
Conclusion
We are pleased to submit the final SRS report on Online School Management System. The
SRS helps the developer to automate the School Management System. This report contains use
cases which are the most important part of the scenario based modeling as well as the system for
development. The students as well as the teachers will be flexible if the System is automated. In
addition, the SRS has been done sequentially so that the readers can easily understand the SRS
report and can visualize the system as well. We have tried our best to the SRS of the Online
School Management System and hopeful that the readers will get benefit from the document.
80 | P a g
e
Appendix
Reference
1. Roger S. Pressman, Software Engineering: A Practitioner's Approach (7th ed.)
2. Abraham Silberschatz, Henry F. Korth, S. Sudarshan, Database System Concept (5th ed)
3. http://www.google.com
81 | P a g e

SRS On OSMS

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

SRS On OSMS

Uploaded by

Copyright:

Available Formats

SRS ON ONLINE

Title: Online School Management

3.5. Case Scenario

3.5.1. Registering Online

3.5.3 Student database generation

3.5.4 Attendance sheet generation

4.1 What is usecase diagram?

4.2 Usecase Diagram

4.3 Activity Diagram and Swimlane Diagram

4.3.1 Activity Diagram

4.3.2 Swimlane Diagram

5.1 Data Modeling Concept

5.3 Data Relationship Diagram

5.4Entity Relationship(ER) Diagram

5.4 Table Schema Diagram

Class Schema Diagram

3.3.2 Requirement elicitation through questioning

3.3.3 Record view

Observation as a fact-finding technique is widely accepted by scientist, sociologists,

3.4 Quality Function Development

3.4.1 Normal Requirements

Accessible via the Internet.

Time and Money consuming system.

Keep attendance record.

Generate automatic result sheet.

Generate automatic annual report.

3.4.2 Expected Requirements

3.5. Case Scenario

3.5.1. Registering Online

3.5.3 Student database generation

3.5.4 Attendance sheet generation

3.5.5 Result sheet generation

3.5.6 Annual report generation

4.1 What is usecase diagram?

4.2 Usecase Diagram

Attendance and result store

Annual report generation

Figure 4.1: Level 0 (School management system)

Follow the instruction

Pay registration fee

Download registration form

Submit registration form with

Store data in temporary DB

Figure 4.2: Level 1.1 (Registration)

Action: Receives result

Call for interview

Pay admission fee

Admit into school

Student info store in DB

Figure 4.3: Level 1.2 (Admission)

Figure 4.4: Level 1.3 (Authentication)

Action: Enter password

Get data from temporary

Classify them class wise

Generate class wise student

Figure 4.5: Level 1.4 (Geneate student DB)

Action: Receive request message

Get daily attendance

Generate attendance sheet

Figure 4.6: Level 1.5(Geneate attendance sheet)

Action: Receive data from

Get result form teacher