SRS UMS: Online University Management System

The Generic Automation for university will be a web based computerization for university ABC. The system should be generically developed, taking name, pictures of any university, it should display accordingly. The different users involved in the system and the functions which they can perform are given below:

Scope of Project UMS: Online University Management System:

Project scope is the part of project planning that involves determining and documenting a list of specific project  goals, deliverables, tasks, costs and deadlines. Defining the project scope involves adopting a clear vision and an agreement on the outcomes of the project. This allows each milestone of the project to stay on target

Functional and Non Functional Requirements of UMS: Online University Management System:

Functional Requirements :

A functional requirement shows that what the system must do what services the system present to users. It describes a software system or its component. A function is nothing but inputs to the software system, its behavior, and outputs

Functional Requirements of UMS: Online University Management System:

 Registration Manager
 Fee Manager
 Course Instructor
 Exam Manager
Responsibilities and functions of each user are given below:
Registration Manager:
There is only one registration manager in the system which is responsible to add/update
the student information such as name, Student Id, Degree Program, Date of birth, Age,
Address, Courses enrolled.
Fee Manager:
Fee manager is responsible to manage the fee record of every student such as fee
deposited, fee remaining, installments etc.
Course Instructor:
3. There are many course instructors in the system.
4. The system which an instructor can access include following attributes.
 Student ID
 Student Name
 Student Degree Program
 Student Course (which he teaches)
 Assignment marks
 Midterm marks
 Final Marks
 Sessional Marks
Exam Manager:
2. Exam Manager is responsible to maintain the records of complete course results and
print the final transcripts.

NON-FUNCTIONAL REQUIREMENTS UMS: Online University Management System:

• Application is user friendly.
• Application Perform fast manipulation and calculations.
• Application is adaptable.
• Application will be able to work on all types of operating systems.
• Application will be capable to handle multi user activities simultaneously.
• There will be back up system to face any problem in system
• All the options should be learning friendly I.e. member could easily understand what that option will do if he clicked on it.
• Response Time is very awesome.

Some others are:

• Accessibility
• Maintainability
•  Fault Tolerance.
• Security
• Robustnes

Use Case Diagram of Diagnosis of UMS: Online University Management System

a use case diagram can summarize the details of your system’s users   and their interactions with the system. Scenarios in which your system or application interacts with organizations, people, or external systems. Goals that your system or application helps those entities achieve

Usage Scenarios Diagnosis of UMS: Online University Management System:

A brief user story explaining who is using the system and what they are trying to accomplish. A Scenario is made up of a number of simple, discrete steps that are designated as being performed by either the System or a  User.

ADOPTED METHODOLOGY for UMS: Online University Management System:

The adopted methodology for this project is vu process model. Vu process model is a combination of water-fall model and spiral model. This combination has many advantages. This model has high risk analysis so avoidance of risk would be achieved. This model is easy to understand and use. Now first we will discuss the Water-fall model.

Work Plan of Diagnosis of UMS: Online University Management System:

Work plan

for complete srs contact us

watsapp: 03469806607