DESIGN PROBLEM-1 ON Software engineering

Submitted To: MR. Sartaj singh

Submitted By: HARLEEN KAUR Roll_no:B36 Prog: MCA(Hons.) 10800343

UMS IN LPU 1. Introduction:

Purpose The purpose of this document is to describe the external requirements for UMS scheduling system for an academic department in a University. It also describes the interfaces for the system. This SRS describes the performance requirements allocated to the UMS (University Management System) in the LPU for Teachers and Students. It describes how student fetch the information related to the various courses.

1 .2 Abstract: This is the requirements document for the case study that will be used throughout the book.The system to be developed is for scheduling the courses in a computer science department,based on the input about classrooms, lecture times, and time preferences of the different instructors

Scope: University Management System is developing for Lovely Professional University of Phagwara, Punjab and used to replace old paper work system and FMS. UMS is to build upon the existing File

Management system in order to provide facilities like upload/download marks/Assignments/Notes, view marks, mark/view attendance, and online fee payments and other kind of announcements and allocating supervisor/ideas to students.

1.1.1. Role of the student Every student can access its UMS accounts with its Registration no and same password by default and after that he/she have to change the password for security and than he/she can view their marks on it, Submit online fees and see its attendance. On the teacher side, they should enter all the detail such as marks of students and their attendance or information about other daily activities. The system will generate activation code and send email to student and confirm the registration. After, the system allow student to change information and provide the function forget password for student to retrieve back the password.

2. General Description:

3.1 Product Functions Overview: In the computer science department there are a set of classrooms. Every semester the department offers courses, which are chosen from the set of department courses. A course has expected enrollment and could be for graduate students or undergraduate students. For each course, the instructor gives some time preferences for lectures. The system is to produce a schedule for the department that specifies the time and room assignments for the different courses. Preference shouldbe given to graduate courses, and no two graduate coursesshould be scheduled at the same time. If some courses cannot be scheduled, the system should produce a conflict report that lists the courses that cannot be scheduled and the reasons for the inability to schedule them. . Including further student details

We want to record lots of information about students apart from just their enrolment in a particular unit (eg address, e-mail, phone, date of birth, etc), so we would not want to have to record all that in every unit enrolment. Therefore we want a separate entity to record details about each student. And of course most students are enrolled in a course, so we would like a separate entity to define the details of each course. Most units are also associated with particular courses, so we could add that link to if required. Sample attributes for these entities might be: Student = Student name + Student ID+ E-mail + Postal address + Phone, etc Course = Course name + Course code + Course type (bachelors, Masters by Research, masters by Coursework, etc) + Course coordinator, etc Student Result is given Unit enrolment has Student is enrolled in Course contains enrolls Unit offering has i) Product Perspective:i) Product functions:Marks of MTE (mid term examination) and ETE(end term examination) Will upload by the university on the UMS. Grade of every student will also display O Assignment:Every faculty member of LPU will upload the assignment of every Course . Announcement:The announcements for students will also display on the UMS by the faculty members. Unit

iii) User characteristics: Students and faculty members are the users of the UMS. People of the maintenance are also interacting with this software so that UMS are working without any interrupt. Top authority of the university is also the user of this software for knowledge about the students information. 4 Specific Requirements: 4.1 Inputs and Outputs: The system has two file inputs and produces three types of outputs. Input file 1: Contains the list of room numbers and their capacity; a list of all the courses in the department catalog; time1 , time2 , time3 ; 2 where room1 and room2 are room numbers with three digits, with a maximum of 20 rooms in the building; cap1 and cap2 are room capacities within the range [10, 300]; course1, course2 are course numbers, which are of the form csddd, where d is a digit.

4 Specific Requirements: 4.1 Inputs and Outputs: The system has two file inputs and produces three types of outputs. Input file 1: Contains the list of room numbers and their capacity; a list of all the courses in the department catalog; time1 , time2 , time3 ; 2 where room1 and room2 are room numbers with three digits, with a maximum of 20 rooms in the building; cap1 and cap2 are room capacities within the range [10, 300]; course1, course2 are course numbers, which are of the form csddd, where d is a digit.