School Management System 2011
School Management System 2011
School Management System 2011
Table of Contents
Introduction:........................................................................................................................................................ 2
Companys Profile:............................................................................................................................................... 2
User Requirements: ............................................................................................................................................. 3
Reports: ....................................................................................................................................................... 3
Software Objective: ............................................................................................................................................. 3
Software Scope: ................................................................................................................................................... 3
Features: .............................................................................................................................................................. 4
Feasibility Report: ................................................................................................................................................ 5
Process................................................................................................................................................................. 6
Incremental model: ......................................................................................................................................... 6
Process Decomposition: ...................................................................................................................................... 7
Cost estimation:................................................................................................................................................... 8
Time Estimation ................................................................................................................................................... 8
THE W5HH PRINCIPLE.......................................................................................................................................... 8
Resources: ......................................................................................................................................................... 11
Human Resource: .......................................................................................................................................... 11
Reusable Software Resources ....................................................................................................................... 11
Environmental Resources: ............................................................................................................................. 11
Diagrams ............................................................................................................................................................ 12
Use Case Diagram .............................................................................................................................................. 12
Sequence Diagram............................................................................................................................................. 13
Activity Diagram ................................................................................................................................................ 16
Software quality plan ........................................................................................................................................ 19
Project testing technique .................................................................................................................................. 23
White Box Technique: ................................................................................................................................... 23
UNIT TESTING: ........................................................................................................................................... 23
Integration Testing: ................................................................................................................................... 23
Black Box Testing: .......................................................................................................................................... 23
VALIDATION TESTING: ................................................................................................................................... 24
Alpha and Beta Testing: ............................................................................................................................. 24
Page | 1
School Management System 2011
strong educational foundation to the young generation to ensure the development of open-
minded global citizens securing the future for everyone. Advanced technology available today
record keeping to control absentees, producing report cards, producing official transcript,
preparing timetable and producing different reports for teachers, officials from Dr.Mohiuddin
Automation is the utilization of technology to replace human with a machine that can perform
more quickly and more continuously. By automating SMS documents that took up many large
storage rooms can be stored on few disks. Transcript images can be annotate. It reduces the
Companys Profile:
Future heaven school is the renowned school. The school is enlightening the futures of
students in Federal B.Area Karachi. It is under the management of Dr.Mohiuddain Education
foundation. The school is educating the students of Montessori, prep to matric. Currently the
school is totally manual. They are not using any software. The want to automate their process
by using the new world technology. For this we are designing the application. This will cover
the key areas of the school. The details of the project are listed in remaining document.
Page | 2
School Management System 2011
User Requirements:
1. The system will deal with Student Information.
2. The system will manage the payroll and typical H.R process
3. The system will have the Attendance module which stores the teacher and student
attendance.
4. The system will manage the class time table.
5. The system will manage the fesses from student.
6. The system should Manage the exams results and save according to academic year
Reports:
Results
Salary Sheet.
Attendance Sheet.
Time Table.
Software Objective:
The objective of the system is to provide the user friendly application which mange the whole
school. The software helps the user to record the student and employees data. Give a path for
better reporting
Software Scope:
The scope of the system is to manage the
Page | 3
School Management System 2011
Features:
Get easy access to student particulars, their schedules, address, parents, disciplinary
Track your teacher's particulars, residential addresses and other important data
Report cards are fully customizable - you get to have your own grading criteria, grading
flow, report card format. You can print beautiful report cards and transcripts.
Teachers will be treated to the simplest interface around for them to enter grades.
Track daily attendance. Easy to use interface to check off students Attendance.
Fees management. Track the fees of the students. Automatic generation of the fee bills.
tracked automatically.
Manage the employees data. There information is stored with their types and branches.
Employee salaries are calculated in the system automatically. Theses salaries are
Page | 4
School Management System 2011
Feasibility Report:
PROPOSED SOLUTION
Owing to the captioned evaluation, the best solution is to design and develop the information
system on RDBMS coupled with front-end support on the latest visual tools and efficient
utilization of reporting tools.
FEASIBILITY AREAS
Keeping in view the earlier discussion pertaining to terms of reference that is Project Scope,
Problem and Opportunity Identification, and Option Evaluation; the key areas of feasibility can
be analyzed as follows:
Technical Feasibility
The proposed system is feasible on technical grounds because of its implementation via
available resource utilization of hardware and software. In addition, the proposed system will
be
Operational Feasibility
The proposed system is feasible on operational grounds sine it imposes no conflicts with the
way the academy undertake its operations. In addition there would be no training costs for the
new system in consideration.
Social Feasibility
In social ground there would be no conflicts among the system functionalities and personal
policies, job specification, skill requirements and motivational factors.
Economic Feasibility
On grounds the project deemed to be no or very little cost project to the academy owing to the
availability of very low priced software. Furthermore the existing hardware ca easily be
utilized for the system implementation.
Page | 5
School Management System 2011
Process
In the project school management system we are using the incremental model. The model is
based on the different increments and each increment has some tasks.
Incremental model:
When an incremental model is used, the first increment is often a core product. The core
product is used by the customer or undergoes a detailed review. As a result of use and/or
evaluation a plan is developed for the next increment. The plan addresses the modification to
the core product to better meet the needs of the customer and delivery of additional features
and functionality. Software is constructed in a step-by-step manner. While a software product
is being developed, each step adds to what has already been completed.
Steps
Incremental -1 core product Student information System
Incremental -2 School administration Module
Incremental -3 H.R module
Test
Code
Design
Analysis
Page | 6
School Management System 2011
Process Decomposition:
Processes Sub-Processes
Gathering User Requirements
Do Validation Testing
Page | 7
School Management System 2011
Cost estimation:
COST
Practitioner cost 5000 * 2 = 10,000
Utility Bills
5000
Computer Cost
10,000
Total 15,000
Time Estimation
The system is being developed to give the user to manage the school efficiently. Track the
income by the business. Give timely information to the higher management and staff so
necessary action will be taken.
Page | 8
School Management System 2011
Project Plan
NO. Phases Start End Date Dependencies
date
1 Gather 10 Oct 17th Oct
requirements 2011 2011
2 Analysis of the 18th Oct 30th Oct
1
system 2011 2011
3 Make diagrams 1st Nov 20 Nov
2
2011 2011
4 Make 21st Nov 27th Nov
3
prototypes 2011 2011
5 Approve the 28th Nov 29th Nov
prototypes 2011 2011
4
from the
customer
6 Coding of 30th Nov 10th Dec
5
Student module 2011 2011
7 Approve 11th Dec 11th Dec
6
Student module 2011 2011
8 Coding of 11th Dec 19th Dec
School 2011 2011
3,6
management
module
9 Approve of 20th Dec 20th Dec
School 2011 2011
7
management
module
10 Coding of HR 1st Jan 10th Jan
3,7,8
module 2012 2012
11 Approve of HR 11th Jan 11th Jan
10
module 2012 2012
12 Coding of Fee 12th Jan 30th Jan
3,7,8,11
module 2012 2012
13 Approve of Fee 1st Feb 1st Feb
12
module 2012 2012
14 Testing and 2nd Feb 20th Feb
13
Implementation 2012 2012
15 Support 21th 20th
Feb March 14
2012 2012
Page | 9
School Management System 2011
.
Q) Who is responsible for a function?
All the technical jobs will be done by Hassam Ahmed and all the managerial job is done by Hifza
Nisar
Role Responsibilities
Hifza Nisar Analysis phase
UML diagrams
Front End
ERD
Q.A
Resources
Hardware Resources Intel Core 2 Duo, 2.6 GHz Processors, 120gb
H.D.D, 2gb Ram.
Page | 10
School Management System 2011
Resources:
There are three types of resources that we will use in our project:
Human Resource:
Role Responsibilities
Hifza Nisar Analysis phase
UML diagrams
Front End
ERD
Q.A
Hassam Ahmed Technical job
Store procedures
Coding
Implementation
Testing
Support
Dev Express: this software will help in making the forms .the tools are up to date and make the
work more efficient.
Enterprise library 3.1: The Microsoft Enterprise Library is a collection of reusable software
components (application blocks) designed to assist software developers with common
enterprise development cross-cutting concerns (such as logging, validation, data access,
exception handling, and many others). Application blocks are a type of guidance; they are
provided as source code, test cases, and documentation that can be used "as is," extended, or
modified by developers to use on complex, enterprise-level line-of-business development
projects
Environmental Resources:
In our project we need different softwares and hardwares to make better and efficient
product.
Hardware Resources: Intel Core 2 Duo, 2.6 GHz Processors, 120gb H.D.D, 2gb Ram.
Software Resources: we need, Ms. Visio for mapping the analysis phase, Ms. SQL Server for
generating Database, Ms. Visual studio for Coding, , Ms. Word for writing the report.
Page | 11
School Management System 2011
Diagrams
Principle *
Add Classes
Generate Report *
Change Policies / Cards
* Grades
* Manage Students
*
Manage Records *
Update Records View Attendence
*
*
*
* *
Manage Salaries *
Manage All Students
*
View Salary Sheet *
* Teacher
Generate Salaray Submit Grade
Manage Marks
Sheet Reports
* *
**
Update or View
Accountant * Receive Fee Bill Grades
Generate Fee Bill
*
Monitor Accounts
Page | 12
School Management System 2011
Sequence Diagram
Registration Sequence Diagram
Class Teacher
EnterStudent ID Validate ID
Validated
Enter Marks
insert()
Page | 13
School Management System 2011
Administrator
Validated
Return List
Mark Attandance
Save
acknowledge ()
Page | 14
School Management System 2011
Class Teacher
EnterStudent ID Validate ID
Validated
Enter Marks
insert()
Page | 15
School Management System 2011
Activity Diagram
Registration Activity Diagram
Yes
No
Amissions Test are conducted
Page | 16
School Management System 2011
Yes
Student Employees
Press Show
Press Save
Page | 17
School Management System 2011
Enter Student ID
Enter Remarks
Press Save
Result Prepare
Eject
Page | 18
School Management System 2011
Page | 19
School Management System 2011
Page | 20
School Management System 2011
Class Diagram
Page | 21
School Management System 2011
1) In the first step, we will select the test factors and rank them. The selected test factors
such as reliability, maintainability, portability or etc, will be placed in the matrix
according to their ranks.
2) The second step is for identifying the phases of the development process. The phase
should be recorded in the matrix.
3) The third step is that identifying the business risks of the software deliverables. The
risks will be ranked into three ranks such as high, medium and low.
4) The last step is that deciding the test phase of addressing the risks. In this step, we will
decide that which risks will be placed each development phase.
Correctness
Performance
Availability
Continuity of
Processing
Compliance
Ease of use
Coupling
Ease of
Operations
Access
Control
File Integrity
Page | 22
School Management System 2011
Formal Reviews:
The SQA will ensure that the necessary revisions to the document have been made and that the
document would be released by the stated date. In case there are any shortcomings then the
same would be pointed to the software project management
UNIT TESTING:
The primary goal of unit testing is to take the smallest piece of testable software in the
application, isolate it from the remainder of the code, and determine whether it behaves
exactly as you expect. Each unit is tested separately before integrating them into modules to
test the interfaces between modules. Unit testing has proven its value in that a large percentage
of defects are identified during its use.
Advantages:
It allows for automation of the testing process, reduces difficulties of discovering errors
contained in more complex pieces of the application, and test coverage is often enhanced
because attention is given to each unit.
Integration Testing:
Integration testing will execute on several modules together and need for the untested
modules. However it should be avoided big bang integrations when we are going directly
from unit tests to whole program tests. It is likely to have many big issues. In this test, it is hard
to identify which component causes each. This test interaction between modules ultimately
leads to end-to-end system test.
Page | 23
School Management System 2011
In black box testing we will test the forms of the system. In this our scope is to test the
following Forms:
Modules Forms
Student Information Module Student Information Form-Registration &
admissions
Human Resource Module :
Employees Info- Registration
Reporting
Result card
VALIDATION TESTING:
Alpha and Beta Testing: In software development, your alpha test will be a test among
yourselves (the teams) to confirm that your product works. Originally, the term alpha test
meant the first phase of testing in a software development process. During this time you will
compress files, edit for misspelled words and unclear directions
In software development, a beta test is the second phase of software testing in which a
sampling of the intended audience tries the product out. Beta testing can be considered "pre-
release testing. The Beat version of software is given to users .they use the software and not
the errors and areas where changes and improvements are needed. We have given the
software to the employees of school and also to the teacher
Page | 24