13-04-2012, 04:17 PM
SRS(Software Requirements Specification)
srs.pdf (Size: 2.34 MB / Downloads: 58)
Introduction
1.1. Purpose
The m a i n objective of this document is to illustrate the requirements of
the project University Management system. This document
describes the design decisions, architectural design and the detailed
design needed to implement the system. It provides the visibility in
the design and provides information needed for software support. The
document gives the detailed description of t h e both functional and
non functional requirements proposed by th e client. The d o c u m e n t is
developed a f t e r a n umb e r of consultations with the c l i e n t
and considering the comp l e te requirement spe c if i ca tions of the
given Project. The final product of the team will be meeting the
requirements of this document.
1.2. Document Conventions
The following are the list of c o n v e n t i o n s and acronyms used in t h i s
document and the project as well:
Administrator: A login id representing a user with user administration
privileges to the software
User: A general login id assigned to users
Client: Intended users for the software
SQL: Structured Q u e r y Language; used to retrieve information
From a database
SQL Server: A server used to store data in an organized format
A S P: Active Server Pages: A Web Page formatted on the server
and delivered to the browser.
Layer: Represents a section of the project
User Interface Layer: The s e c t i o n of the assignment referring to
what the user interacts with directly.
Application Logic Layer: The s e c t i o n of the assignment referring
to the Web Server. This is where all computations are completed.
D a t a Storage Layer: The s e c t i o n of the assignment referring to
where all data is recorded
Data flow diagram: It shows the dataflow between the entities.
U s e Case: A broad level diagram of the project showing a basic
overview
B o o l e a n: A true/false
notation
I n t e r f a c e: Something used to
communicate across different
mediums
Unique Key: Used to differentiate entries in a database
1.3 Scope
Online Project Marking System is developing for School of Computing,
University of Portsmouth and used to replace old p a p e r work system
and PUMS. OPMS i s t o build upon the existing web-based project
marking system PUMS i n o r d e r to implement the project marking
process and allocating supervisor/ideas to students. This increase in
efficiency of project marking, audit trails of marking process, give
feedback to student, finally, publication and email student result. It
provides a mechanism to edit the online marking form which makes
the system is flexible.
2. Overall Description
2.1 Product Perspective
The proposed University Management System is an on-line
University Management S y s t e m. This System wi l l provide a
v i e w, submit, online payment, uploading various documents and
other mislenious resources. This view will b e based on the categories
like
Attendance view and daily activities. Further the University
management staff personnel (faculty) can add/update/remove the
resources or an automatic removal of a c c e s s i n g features when the
time limit completes.
The System will also have an ADMIN who has full-fledged rights with
regards to managing resources across branches – such as transferring
books across these b r a n c h e s. The users c a n v iew, submit, online
payment, uploading various documents and information about their
account etc. there are basic two types of u se rs one are the students
and other are faculty members. Each user facilitates with a different
account number having a profile along with a password for private use.
The two types of u s e r s differ from each other due to the accessing
limits to online University management system.
2.2 Product Features
There are three different users who will be using this product:
University chancellor who will be acting as the administrator.
Faculty members who are second level users accessing UMS.
Student of the University who will be accessing the UMS online.
The features that are available to the Administrator are:
the a dmi n i s t r a t o r has the full fledged rights over the UMS.
can create/delete an account.
can view the accounts.
can change the password.
can hide any kind of features from the both of users.
Insert/delete/edit the information of available on UMS.
can access all the accounts of the faculty members/students.
The fe a t u r e s available to the Faculty members are:
can mark the attendance of students online.
can view the attendance online.
c a n upload marks, assignments, reading materials for
students.
The fe a t u r e s available to the Students are:
can view the d i f f e r e n t categories of assignments available
in their account.
can view their marks.
can view the various reading material.
can view attendance.
can view and modify its profile but can modify it to some
limited range.
can pay their fee online.
2.3 User Classes and Characteristics
There are v a r i o u s kinds of users for the p r o d u c t. Usually
web products are visited by various users for different reasons.
The u s e r s include:
Chancellor who will be acting as the controller and he will
have all the privileges of administrator.
Faculty members who will be using the above features by
accessing the UMS online.
Students who will be using the above features by accessing
the UMS online.
2.4 Operating Environment
The product will be operating in wind ows environment. Also i t will be
compatible with the IE 6.0. Most of t h e features will b e compatible
with the M o z i l l a Firefox & O p e r a 7.0 o r higher v e r s i o n. The
only requirement to use this online product would be the
internet connection.
2.5 Design and Implementation Constraints
The P r o d u c t is developed using ASP. The b a c ke n d database for this SQL
Server. The p r o d u c t is accomplished with login facility so that specific
function is available to specific student.