17-07-2012, 03:55 PM
ANALYSIS AND DESIGN x OF INFORMATION SYSTEMS
Development of UMS System.pdf (Size: 610.4 KB / Downloads: 25)
INTRODUCTION
University Management System, is an online system, for the management of all the activities of an University.
It includes management of all the records and all related activities.
It includes Management of record of different entities such as Students, Teachers, Staff Members, etc.
EASE OF ACCESS:
The Life of every man is a diary in which he means to write one story, and writes another; and his humblest hour is when he compares the volume as it is with what he vowed to make it.
To make accessing the record, such as searching, updating and make task easier, it was very necessary to build and system, so was the UMS build.
Searching an record of a student, in an university, where more than 26,000 students exists, it’s nearly impossible to find record of some specific students.
But with the help of UMS, we have an online system through which we just at a instance check any record we want within a matter of seconds.
ONLINE/LIVE ACCESS:
Making everything live, such that things become easy and available instant at a second flip.
Now we can access any record at any moment of time, anywhere we want.
We can check our attendance or marks, or our CA components anywhere or anytime we want.
SOLVING OF PROBLEMS :
The university management had been facing a lot of problems and criticisms in the management and the development of the records of the university teachers, students and staff’s. To solve this problem the UMS was build upon.
Here are some steps in which requirements are determined: 1. Identify a set of key end users who collectively have the credibility to define the software the team is building. 2. Interview the end users to create a set of preliminary requirements. 3. Build a simple, interactive user interface prototype. 4. Show the simple user interface prototype to the key end users and solicit their feedback. Continue revising the simple prototype, keeping it simple, showing it the end users, and revising it again until the end users are excited about the software concept. 5. Develop a style guide that codifies the prototype’s look and feel, review it, and put it under change control.