Académique Documents
Professionnel Documents
Culture Documents
Specification
for
Courseware Management
System
Version 1.0 approved
Cdac, Noida
17-09-2012
Copyright 2012 by Lokender Tiwari. Permission is granted to use, modify, and distribute this document.
Page ii
Table of Contents
1. Introduction................................................................................................................................4
1.1 Purpose ...............................................................................................................................................
1.2 Document Conventions.......................................................................................................................
1.3 Intended Audience and Reading Suggestions.....................................................................................
1.4 Product Scope......................................................................................................................................
1.5 References...........................................................................................................................................
4
4
4
4
4
2. Overall Description....................................................................................................................4
2.1 Product Perspective............................................................................................................................. 4
2.2 Product Functions................................................................................................................................ 5
7
7
7
7
8
8
8
3. System Features......................................................................................................................... 8
3.1 New User Creation/Login...................................................................................................................
3.2 Viewing...............................................................................................................................................
3.2.1 Description and priority..................................................................................................................
3.3 Preparing course schedule...................................................................................................................
8
9
9
9
Page iii
Revision History
Name
Date
Version
1.
Introduction
1.1
Purpose
ThepurposeofthisdocumentistopresentadetaileddescriptionoftheCourseware
ManagementSystem.Itwillexplainthepurposeandfeaturesofthesystem,theinterfaces
ofthesystem,whatthesystemwill,andhowthesystemwillreacttoexternalstimuli.
1.2
Document Conventions
Document and Specification team have prepared this SRS document to the best of their
ability. Each section is important to the overall SRS and significant to the project.
1.3
This document is intended for developers, users, testers and document writers
1.4
Product Scope
It is a standalone system for an institution which automates the student, faculty and
management interactions. This system designed to allow institute management to manage
various courses and their schedule and to communicate with student and faculties. The
software facilitates the communication with program coordinator, students and faculty
via publishing course information and its schedule on the website. This system also
include a relational database containing list of faculties, courses, students and schedule.
1.5
References
IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements
Specifications. IEEE Computer Society, 1998.Institute Manuals
2.
Overall Description
2.1
Product Perspective
This product is for automate the manual institute management system. With this
product institute management would be able to manage various courses and their
schedule and to communicate with student and faculties at a single centralize place.
2.2
Product Functions
2.2.1
Administrative Function
2.2.2.1 Access tutor , and student details and can modify also.
2.2.2.2 Manage course.
2.2.2.3 Prepare course schedule.
2.3
2.3.1
Administrator
Diagram:
administrator
Manage
Account
2.3.2
Course Coordinator
Manage
Course
<include>
Prepare
Schedule
course coordinator
Brief Description: Manages the course content, syllabus etc.
2.3.2.2 Use case: Prepare Schedule
Brief Description: Prepare schedule according to availability of tutors.
2.3.3
User
User can be anyone who is authorized for viewing and accessing the course and
college data these can be students, HODs, Director of institute etc. Administrator
manages the user accounts.
Diagram:
user
<include>
Manage
Account
<include>
<extends>
View
schedule
Brief Description: Allow registered user to login .
2.3.4
Tutor
Tutors have their unique account which includes educational qualification along with
specialization.
Diagram:
tutor
<include>
Manage
Account
<extends>
View
schedule
Brief Description: Allow tutor to login .
<include>
2.4
Operating Environment
2.4.1
Operating System
2.4.2
2.5
Security and integrity of the data and information regarding institute must be maintained.
User interface must be interactive n friendly in nature.
2.6
User Documentation
There must be a installation guide which is to be supplied along with product and also
user manuals for each administrator, course coordinator, tutors and general users that
must be supplied along with the product.
2.7
Following assumptions ,rights and dependencies must be satisfied with the product.
Only administrator has the right to allow or deny the creation of any new user
account.
Administrator manages the viewing permissions to a particular details related to
course and accounts.
Course coordinator capable of accessing course details, tutor details, student
details and schedule for a course and can manipulate them. External Interface
Requirements
2.8
User Interfaces
User interface must be GUI and user friendly. There must be a special column for
Important news, latest course schedule.
2.9
Hardware Interfaces
Product is not very hardware specific so it can be easily runnable on a normal hardware.
3.
System Features
3.1
3.1.1
Description and priority
This will handles the new account creation for either student, tutor.
3.1.2
Stimuli/Response sequences
User request for a new account creation and system response after successful creation of
account. Allow registered user to login.
3.1.3
Functional Requirements
REQ: User Role (Student, Tutor, Course coordinator, Admin).
3.1.3.1 If Student
REQ: Student name
REQ: Program Name
REQ: Department
REQ: Courses.
REQ: Student ID
REQ: Password.
3.1.3.2 If Tutor
REQ: Tutor Name
REQ: Designation
REQ: Department
REQ: Specialization.
REQ: Tutor ID
REQ: Password
3.1.3.3 Other/Login
REQ: ID
REQ: Password
3.2
Viewing
3.3
4.
4.1
Security Requirements
There must be a security mechanism such that the access to the account details is
allowed only for authorized persons.
4.2
10
4.3
Business Rules
In case of any kind of data discrepancies only administrator can be able to correct data
discrepancies.
Appendix A: Glossary
SRS: Software Requirement Specification
ID: Identity
IEEE: Institute of Electrical and Electronics Engineers
REQ: Requirement
DFD: Data Flow Diagram
ER Diagram:
11