Here i am putting one SRS for College Management System. That created by me It might Help to you for How to write SRS
System can be used to manage the
data of all type of educational institutes. It will support both stand alone
and also networking environment. The system uses VB. Net Technology. This is a web oriented application allows us to access the
whole information about the college, staffs, students, facilities etc. This
application provides a virtual tour of Campus. Here we will get the latest
information about the students and staffs. This generic application designed
for assisting the students of an institute regarding information on the
courses, subjects, classes, assignments, grades and timetable. It also provides support that a faculty can also check about
his daily schedule, can upload assignments, and notices to the students. Here
administrator will manage the accounts of the student and faculties, makes the
timetable, and upload the latest information about the campus.
Main purpose for developing this system is to provide and
easy way not only to automate all functionality of a college, but also to
provide full functional reports to top management of college with the finest of
detail about any aspect of college
College management system is software as perspective of
attaining attraction of those colleges which don’t have good performing
software for keeping their information secure and make their management easier.
CMS provide one attractive environment where you can multiple data and
information about student and staff easily. So we can say the core purpose of
designing CMS is to manage task related to the college students/employees and
reduce time to searching of appropriate candidate in college view
This system provides the details structure of the college
campus and its departments.CMS synchronizes the working of all the
departments. It looks on all aspects of a college, its students, faculties,
Departments, marks and other co–curricular activities.CMS is the easiest way to
manage all functionalities of a college, which facilitates colleges to maintain
the functionality related to college employees and their students.
The scope of the project includes the following
1. Any college can use this system
as it is not client centric.
2. Deliver
Electronic Workplace
3. Provide
Bi-lingual support
4.
Application Support & Maintenance after deployment to production
5. The
Admin Module can be reused for projects as well which have many users with
different rights. Hence it is reusable.
| 1.4 TECHNOLOGY AND LITERATURE
REVIEW |
Ø
Technology to be used in this
system:
·
OS:
Windows XP or higher
·
Environment:
Visual Studio.Net
·
Language:
VB.NET
·
Database:
SQL
Ø
Literature Review
Until
recently the place of the College Management System, Now-a-days, education is
playing very significant role in the society. Day-by-day, the percentage of
illiterates are decreasing and the percentage of literates is increasing.
Education will change the society in all the aspects and everyone wants to
study higher professional degrees. Admissions are increasing day by day so
there by. Ratio of establishment new colleges and schools are also increasing.
But the actual challenge is starting from now. Most of the schools and colleges
are maintain student information in records. When the number of records
increased, it is difficult to maintain the information of each student in the
old manual system. Maintaining the records manually
leads to error prone and required more man power and it consumes more time for
processing the records. Information Management Software System (IMS) is a set
of modules of software system to help manage the information of the educational
management activities in a college.
Existing System:
In existing system of the project we had just results that is
usage through manually, here student. And factulties members are work with
fully transparent and effectively
2.1 PROJECT PLANNING AND
SCHEDULING
|
2.1.1 Project Development Approach and Justification
For this Project development we are
using Waterfall model because waterfall model which states that the phases are
organizing in linear order the waterfall model suggests a systematic
,sequential approach to software development that begin at system level and progresses
through analysis, design, coding and testing. For a successful project
resulting in a successful product all phases listed in waterfall model must be
performed any different ordering of phases will result in less successful
software product.
There are number of project output
in waterfall model that is produced to produce a successful product.
- Requirement
document and project plan
- System
and detail design
- Coding
- Testing
- Deployment
2.1.2 Project Plan
This section describe roles and responsibilities and
assumption and dependencies
·
Roles and Responsibilities:
- Contributing to overall project objectives
- Completing individual deliverables
- Providing expertise
- Working with users to establish and meet business needs
- Documenting the process
- Establish a project schedule and determine each phase
- Determine the methodology used on the project
- Assumptions
and Dependencies:
Assumptions:
o
Data that should be given is right
and entry in correct way
o
All data entry must be in time to
time
Dependencies:
o
Some modules may depended on Each
other.
o
It may be dependent on connectivity
also
Ø Risks mainly include the
difficulties or obstacles we would face while developing the system.
Identifying risk and drawing up plans to minimize their effect on the project
is called risk management.
2.2.1 Risk Identification: -
Ø The followings are the possible
risks, which is associated with project. We have identified mainly technical
and project risks.
Ø Technical Risks: -
Data
manipulation
As
lower version of operating system like XP our project may not run efficiently.
Ø Technological Risks:-
The
database used in system cannot process as many transactions per second as
expected.
Ø Project Risks: -
Loss
of a team member.
Difficulties
in integrating work
Planning
taking up too much time, not enough time to work on product.
Continuing stream of requirements changes
Ø Financial Risk:
Organizational
financial problems force reductions in project budget. This might degrade
better software development.
2.2.2 Risk Analysis:-
·
To
handle the risks, they should be prioritized. The damaging risks can be handled
first and then most likely risks. Since the risk related to the schedule
slippage arise primarily due to the intangible nature of the software, so we
had to do the visibility of software requirements documentation and reviewing
the relevant documents during the developments. Every phase can be broken into
the reasonably sized tasks and milestones can be scheduled for these tasks.
·
In
this process each identified risk is considered in turn and a judgment made
about the probability and the seriousness of the risk.
1. The probability of the risk might be
assessed as very low (less than 10%), low (10-25%), moderate (25-50%), high
(50-75%) or very high (greater than 75%).
2. The effects of the risk might be
assessed as catastrophic, serious, tolerable or insignificant.
Risks
|
Probability
|
Effects
|
Organizational financial problems force reductions in
project budget
|
Very
low
|
Catastrophic
|
Loss of a team member
|
Low
|
Critical
|
Difficulties in integrating work
|
Moderate
|
Serious
|
Continuing stream of
requirements changes
|
Low
|
Critical
|
Operating System
Compatibility
|
Low
|
Serious
|
Database Manipulation
|
Moderate
|
Critical
|
2.2.3 Risk Planning:-
The following section describes the
strategies to manage the above risks:
Ø Technical Risks: -
Nowadays
most of peoples are using windows 7 or greater version so it is not a big
issue.
Ø Technological Risks:-
The
database used in system almost works in an accurate way. Hence chances of
crashes or any other problems are very low.
Ø Project Risks: -
The
time limits can be matched up in many ways by either giving more time later, or
giving more efforts in terms of labors.
For
difficulties in work integrity Integrate all work Sunday nights.
Probability of loss of a member is very low
if this happened then Assure files are uploaded and integrated consistently,
use knowledge management strategies such as pair programming to understand each
other’s work.
For requirement changes product
deliverables, bi-weekly.
Ø Financial Risk:
Organizational
financial problems would not cause a major issue of worrying as the project
requirements are not those high.
Software
Requirement Specification
College
Management System
Prepared By:
Aliasgar K. Hathiyari
Version: 1.0
1. Introduction
This section describes the purpose, scope and
an overview of the entire system.
1.1
Purpose:
Current scenario of system CMS used by college is lot of paperwork and keeping written work so CMS
will provide full management system like
records of students Academia ,Attendance and faculty records so no need to do
on paper. Its work with internet or intranet
CMS Software as perspective of
attain attraction of those college which don’t have good performing
software for keeping this information secure and make their management easier..
1.2
Scope:
In-Scope:
Scope of this system is limited authentic person of a college like
student, faculties, principal is a part of user of their system. It looks on
all aspects of a college its student faculties, department, marks and other
co-curricular activites.
Out-of-Scope:
Attendance can be done by biometric system and registration
of faculties by himself is out of scope for this system
1.3
Overview:
The rest of this SRS is organized as follows: Section 2 gives an
overall description of the software. It gives what level of proficiency is
expected of the user, who will be using the system, some assumptions and
dependencies of the system. Section 3 gives specific functional requirements
which the software is expected to deliver. Section 4 describes the interface
requirements whereas Non-functional requirements are listed in Section 5. The
costing of the software is given in Section 6. The definitions, acronyms, and
abbreviations and the user screens are given in section 7.
2. General Description
This section describes the product
perspective, user characteristics, principal actors and the assumptions and
dependencies of the system.
2.1
Product Perspective:
Main Aim of this system by use of this system college’s all records
maintain in one place like details of all students attendance details of all
department and faculties details etc. product should be user-friendly and ease
of access and easy to learn.
2.2
Principal Actors:
The system has 3 principal actors
1.
Admin
2.
Faculties
3.
Students
2.3
User Characteristics:
The admin must be having hands-on knowledge of the computer as he
has to manage the entire system the person using this system is must be have
computer knowledge and members of
college also student and faculties must be enrolled in college to using this system.
2.4
Assumptions and Dependencies:
CMS is dependent on internet
connection or intranet connectivity the details of student and faculties only
entered by admin and entered correct details it is also assume that details of
attendance is entered time to time.
3. Functional Requirements
This section describes
different functional requirements of the system in terms of the
functions/features the system should provide.
1.
Login
for Admin (by Admin)
2.
Registration
of Student (by Admin)
3.
Registration
of Faculties (by Admin)
4.
Update
details of Faculties (by Admin)
5.
Update
details of Students (by Faculties)
6.
Add/Delete
Student (by Admin)
7.
Delete
faculties (by Admin)
8.
Update attendance
of student (by Faculties)
9.
Update
Marks details (by Faculties)
10. Login for Student(By student)
11. Login for faculties (By faculties)
12. Generate attendance report (By faculties)
13. View student cummulative attandance and their acedemia performance (By student)
After being logged in, as an admin whole system would be managed by
this it can be add/delete/modify students, faculties records it can be generate
all reports of students faculties etc. it can generate student id and
password as well as faculties id and
password which uses for login throughout time.
After being logged in, as a faculties it should see its particular
subjects students list of particular class it enrolled and it take attendance
of student for particular subject it can generate report of attendance as well
as students marks faculties can see students whole academic performance
After being logged in as a student it can see their cumulative
attendance subject wise and it also see its academic performance.
4. Interface Requirements
This section describes different interface requirements of the
system:
4.1 Hardware
Interface Requirements:
Wireless Ethernet Card for internet
connectivity. Or LAN
4.2 Software
Interface Requirements:
OS .Windows 7 or later
SQL Server
4.3 External
Interface Requirement (GUI Requirements):
One way to select students enroll no or name to take their
attendance other way is by clicking on photographs of student to mark their
attendance
5. Non-Functional Requirements
The non- functional requirements of the system are as follow:
1.1
Performance Requirements: 90% of the responses should
be within 2 sec, except for downloading the entire case history for which more
time is acceptable.
1.2
Security: Data containing information
regarding client’s case should be secured against malicious deformations.
1.3
Reliability/Fault Tolerance: Data should not become
corrupted in case of system crash or power failure.
1.4
Maintainability: The system should be having
high maintainability in terms of correctness, adding new functionalities and
should be highly adaptive.
The whole system with all other supporting components can be
packaged and easily deployed to server. The system uses Microsoft SQL Server
Express edition, which comes for FREE from Microsoft. Application using .net
framework and visual .net it comes with
license so that cost should include and effort costing and developing cost as
per agreement.
7. Appendices
7.1 Acronyms
and Abbreviations:
CMS: College Management System
SRS:Software Requirements
Specification.
GUI: Graphical User Interface.
LAN: Local Area Network
7.2 Definitions:
Intranet: It is based on LAN it means it
provide local network support it doesn’t use internet
System Design: Data Dictionary.
Admin
table
Attribute
|
Datatype
|
Constraint
|
UserName
|
varchar(15)
|
|
Password
|
varchar(15)
|
|
Student
table
Column
|
Type
|
Null
|
Default
|
S_id
|
Int(11)
|
No
|
|
Name
|
Varchar(100)
|
No
|
|
Enrol
|
Varchar(50)
|
No
|
|
Addr
|
LONGTEXT
|
No
|
|
Course
|
Varchar(50)
|
No
|
|
Department
|
Int(11)
|
No
|
|
Faculty
table
Column
|
Type
|
Null
|
Default
|
Fid
|
Int(11)
|
No
|
|
Name
|
Varchar(50)
|
No
|
|
Department
|
Int(11)
|
No
|
|
Subject
|
Varchar(50)
|
No
|
|
Salary
|
bigInt(20)
|
No
|
|
Department table
Column
|
Type
|
Null
|
Default
|
dpt_id
|
Int(11)
|
No
|
|
d_name
|
varchar(50)
|
No
|
|
Course table
Column
|
Type
|
Null
|
Default
|
Course_id
|
Int(11)
|
No
|
|
course_name
|
varchar(50)
|
No
|
|
Course_credit
|
Int(11)
|
No
|
|
·
Black box testing.
Black box testing uncover following:
§ Incorrect or missing functions
§ Interface error
§ Error in data structure
§ Performance error
§ Termination error
·
White Box Testing
·
White-box
testing (a.k.a. clear box testing, glass box testing, transparent box
testing or structural testing) is a method of testing software that tests
internal structures or workings of an application, as opposed to its
functionality.
·
In white-box testing an internal perspective of
the system, as well as programming skills, are required and used to design test
cases. The tester chooses inputs to exercise paths through the code and
determine the appropriate outputs. This is analogous to testing nodes in a
circuit.
·
While white-box testing can be applied at the
unit, integration and system levels of the software testing process, it is
usually done at the unit level. It can test paths within a unit, paths between
units during integration, and between subsystems during a system level test.
Though this method of test design can uncover many errors or problems, it might
not detect unimplemented parts of the specification or missing requirements.
·
White-box test design techniques include:
§ Control
flow testing
§ Data
flow testing
§ Branch
testing
§ Path
testing
TEST CASES
·
In this section we have
included various tests performed on our developed system and their results are
given below.
·
Test Case 1:
·
Sign-up (registration) Process
Description:
This test will perform check whether system allowuser’s to do their
registration or not.
Test
Data Used: All the valid Admin information format.
Excepted
Output: System allows Admin to do Registration
Actual
Output: System allows Admin to do Registration
Pass/Fail:
Pass
·
Test Case 2:
·
Login Process
Description:
This test will perform check whether system allows valid user to login.
Test
Data Used: Valid user id and valid password
Excepted
Output: System allows user to login.
Actual
Output: System allows user to login.
Pass/Fail:
Pass
Ø LIMITATION
Though we
tried our best but due to some reasons like time available the system has some
limitations as compared to the other content providers. Since these limitations
can be easily removed. Here we will discuss these things.
·
All the page and database are stored at
server side so if server goes down then system cannot respond.
·
Customer can change only their personal
information themselves.
·
The system requires browser to run.
·
Application requires internet connection
for entire operation. There is no offline mode
Ø FUTURE
ENHANCEMENT
Each and every system contains scope
for better developments. It means that each and every system has enhancement
possibilities. In our project enhancement can be made like:
·
It can be targeted to run on non-windows
platform like Tablets.
·
Application is also dealing with some
financial services so there few scopes to user Transaction Coordinator.
·
As
we have given the various technological details to the users, In future we can
think about managing them better & providing the all the related news &
other functionality such as downloading the books etc.
·
In
our application there is a discussion board on which the user can ask the
question only and get answered. On that module we can add the functionalities
like uploading the related books,
sharing other related topics & links etc.
·
At
last, In Future we will try to provide better & better services to our
users
Ø CONCLUSION
We conclude that
by developing this system. We are learn how to developed actual software and
how analyzed system and implements system. We also get knowledge about system
analysis and designing and how to developed web based application in JAVA.
It was a really good
experience for us to do a project in this semester. Working on this project has
given us a valuable experience. It has
been like stepping on the first step of the staircase that leads us towards
building our career. It was our first
experience of working in the atmosphere of a software firm.
At the time of
practically executing our knowledge, we fortunate to have very cooperative and
supportive project leaders and colleagues, their attitude towards us was very
palliative and was always there in our needs.We also learnt how to co-operate
with other employees while working in the same project. This precious experience would definitely be
helpful to us for future.We make one website for our public information. During
the development of website we learnt different other things like to create web
application and get other knowledge.
In future if we get
opportunity to develop other website then we can easily do it better. The
advantage of this website in that we can easily get the information about
unmarried person with user. In this project we also use different kind of
database connectivity with greater feature.
We
have completed this project work in less time period but it is effective and
efficient during this project work we also get other knowledge which is useful
for us make project and also in practical.
Thanks for Reading
If you have any queries related to this please email me at aliasgar.hathiyari52@gmail.com
