Embed Size (px)
Citation preview
CASE STUDY-I : COURSE ENROLLMENT
SRS for Course Enrollment
1. Introduction
Problem Definition A student accesses the system to get information about the various courses offered by the college and
can download forms for admission into various courses. One can get information about examination schedule and can check marks on the college’s website. The student however cannot make any changes in the data.
A lecturer can access the system to check the schedule and update marks of students. A lecturer needs to be logged on to the system to perform his tasks. Every lecturer is allotted a user name and appropriate views by the DBA.
The DBA is mainly responsible for the maintenance of the system. His hob includes allocations of rights to different actors. The DBA also updates the database whenever a function like admission takes place. The DBA needs to ensure that there are no contradictions. He defines the post-conditions and pre-conditions for different operations.
The database is maintained on a server with a unique IP address list. The data has to be protected from unauthorized accesses by providing security mechanisms like firewalls.
Objectives To reduce the expenses of the college by reducing the number of employees for entry and maintenance
of records. To manage data more efficiently. To attract talented students and lecturers to choose the appropriate course according to their interest
and talent. To reduce data redundancy and inconsistency. To display results on the internet. To make the software interface as user-friendly as possible.
Definitions Lecturer – Person teaching a particular subject in the college Student – Person intending to either join some course in the college or already admitted Management – The body managing the overall working of the college Database – The total data stored through which the various actors interact and get required
information. It is continually updated for each procedure completed. DBA – Person in-charge of managing the database
2. General Description
Product PerspectiveThis system is dependent on the database system of the college for providing details to students and other users. It interfaces the users with a special user screen that has different features from the normal user screens. It requires the users to login using a password.
Product FunctionThe various functions performed by the software are: Login – Qualifies users according their class and provides security and also improves the effectiveness
of the software.
Admission – Allows students to get admitted to the college or check their marks if they are already admitted.
Updating of marks – Helps the lecturers to update marks of students. Results – Which displays the marks in the website. Management of database – Assists the DBA in maintaining the database.
User CharacteristicsThe users are required of possessing the following qualities: highly motivated and conscientious, computer literate not necessarily professionals, related to the concerned college.
General ConstraintsThe system shall follow the following constraints in its design phase. Not more than 30 students are allowed to be admitted in a course. Atomicity of actions must be ensured.
3. Specific requirements
Functional Requirements
3.1.1 LoginAccessing the database to read and manipulate data. Any user who logs in does so under his user name and password.
3.1.2 AdmissionSteps involved
Receive the student details through electronic form Check the eligibility of the student and genuineness of the related documents Check the availability of the seats by referring the database Submit the student information to the database if the student is admitted and include the
information in the records Receiving the application fee from the admitted student
Inputs Student information through electronic form
Processing The student checks the database for required course and applies. The system receives the application and checks for the eligibility of the student for the
required course. If the eligibility criterion is satisfied, the system checks the database for the availability
of the seats in the desired course. If there is a vacancy, the student is admitted to the course and allotted a unique roll
number. The database is updated and the number of students in that course is incremented. The appropriate bill is dispatched to the student.
Outputs Particulars if the admitted students are submitted to the database. Issue fee receipt and identify the student.
Constraints Not more than thirty students should be admitted into any course.
3.1.3 Updating marksSteps involved
Checking the validity of the lecturer and verifying the password. Accepting the marks of the individual student of a particular course, if entered by an
authorized lecturer.
Updating the changes according to the marks allotted.Inputs
User name and password of the lecturer. Course and semester of the student, whose marks are to be entered. Roll number and marks of the individual students.
Processing The lecturer logins in order to enter the marks of their respective students. The system checks for the validity of the user name and password and allows access to
the required view (example – the lecturer can not access the salary database) The database is updated according to the marks allotted by the lecturer. The changes are saved and displayed on the college results website.
Outputs A message should be displayed after updating the marks in the database.
Constraints The user must be included in the list of lecturers and have a valid user name and
password The view must be created such that the lecturer must have access to the marks field of his
own students A lecturer cannot have privileges to manipulate other areas of database.
3.1.4 ResultsSteps involved
Accepting the roll number Display the results for a given roll number
Inputs Course and semester Roll number
Processing The student accesses the college website for the results. The system checks for the availability of marks for the semester and if available displays
the results The student can only check the marks but can’t update.
Outputs For valid input, display the result If roll number is not valid, display error message
Constraints The course and roll number must be related to the concerned college.
3.1.5 Management of DatabaseSteps involved
Adding, updating or deleting student information in the student database. Adding, updating or deleting lecturer information in the lecturer database. Adding, updating or deleting course information in the course database. Allocation and de-allocation of roles and privileges. Modifying the information, constraints governing the college.
Inputs User name and password to authorize the DBA. Selection of task. Unique identification key incase the DBA selects to update database so that concerned
data item can be accessed.Processing
The DBA uses this function to manage the changes in database, which occur due to other user cases, and to perform other tasks specified for a DBA.
The DBA logs into the system and then performs the required task.Outputs
Confirmation to the changes made. In case any failure, DBA is informed and the changes are cancelled.
Constraints Atomicity should be ensured, that a particular task should perform totally or should be
completely aborted. The changes made in the database should not be in conflict with the constraints specified.
External interface requirements External interfaces must be maintained by the central database as interpreted by the operator. Students require a different interface as there is no need for them to login. Hard and soft copy reports shall be the only output maintained. These outputs shall be controlled by authorized management personnel.
Performance RequirementsAll user requests shall be responded to within 3 to 5 seconds.Response shall be measured from the last entry keystroke to the appearance of an on screen reply.
Design ConstraintsDesign and development of the system shall confirm to college standards.The system is a java application which runs with the help of a reliable database management system.
Attributes
3.5.1 Security Security of all files shall be a major design requirement. Only authorized users shall be
permitted to access the database. Passwords shall be assigned only by the authorized management personnel. Three unsuccessful access attempts shall be recorded in transaction log, access shall be denied
after the third unsuccessful attempt.
3.5.2 Maintainability Software product documentation shall include design specification, a commented listing (a
comment for every three executable lines of code), a set of executable test cases and appropriate results.
A user manual shall be provided in a reproducible form.
3.5.3 Reliability The college largely relies upon the database and so the system needs to be reliable.
Other requirements
3.6.1 Database An efficient database management system shall be used as a back end, which facilitates
reliable and affective transactions.
3.6.2 Operations A backup of the database is created after each particular interval of time, which can be used
for recovery if needed.
Testing All modules of the systems need to be tested separately and also the system as a whole to assure that
the system works properly as per the requirement specification. Alpha and beta testing can be used for this purpose.
4. UML DIAGRAMS
Use case Diagrams
<<include>>
mode of payementbill generation
user
lecturer
student
fees payment
<<extend>>
login
offer courses
results
updation of marks
take admission
allocation of privilages
DBA
maintainanace of database
Data base
Fig 1: Use case diagram for System
Class Diagrams
DBAdminname : Stringid : Integer
login()admission()offerCourse()displayResults()maintainDB()allocationOfPrivilages()
DataBase
admissionDetails()courseDetails()MarksDetails()
*
11
updates
*Studentname : Stringroll_no : Integercourse_id : Integer
takeAdmission()checkResults()payFee()
enrolls
Coursecourse_id : Integerlecturer_id : Integer
offerCourse()
1..*
1..*
1..*
1..*
attends
Lecturername : Stringlecturer_id : Integercourse_id : Integer
login()offerCourse()updateMarks()
assign Courses
1..*
1..*
1..*
1..*teaches
Universityname : Stringaffiliation : Stringaddress : Stringcode : integer
admission()offerCourses()
1..* 11..* 1
maintains
1..*
1..*
1..*
1..*
1
1..*1..*
1
Fig 2: Class Diagram for System
Sequence Diagrams+
user system database
1: access the net()
2: give options()
3: select functions to be performed()4: look for required information()
5: perform the function()
Fig 3: Sequence Diagram for the System
user System database
1: access the net()
2: ask for the username and password()
3: enter username and password()
4: check for validity()
5: authorize()
Fig 4: Sequence Diagram for the Login
lecturer system dba database
1: acess net and select login option
2: enquire for username and password
3: enter username and password
4: check for validity
5: validate
6: give options
7: select offer courses option
8: get course details
9: give course details
10: display course details
11: select course to offer
12: send details
13: save changes
14: logout
Fig 5: Sequence Diagram for the offer course
Lecturer System DBA DataBase
1: acess net and select update option
2: enquire for username and password
3: enter username and password
4: check for validity
5: Validate
6: enquire for course and semester details
8: check for validity of course and semester
9: validate course and semester
10: accept student marks
11: enter marks for all students
12: send details to dba
13: save changes
14: logout of system
7: enter course and semester details
Fig 6: Sequence Diagram for the Updating of Marks
student system database
1: access net & select result option()
2: provide result form()
3: give course & semister()
6: enquire for roll number if validated()
4: check for validity of course & semister()
5: validate()
7: enter roll number()
8: check for validity of roll number()
9: validate and give result()
10: display result()
Fig 7: Sequence Diagram for the Result Function
systemstudent database
1: access net & select admission option()
2: provide relevant form for the selected course()
3: give necessary details and documents()
5: admit if selection criteria are met()
7: al lot roll number and dispatch necessary bi ll ing()
4: check for avai labili ty of seats and el igibi lity()
6: make necessary modifications()
Fig 8: Sequence Diagram for the Admission Function
DBA system database
1: access net & select namagement option()
2: enquire for username & password()
3: enter user name & password()4: check for validity()
5: validate()
6: select task to be performed()
7: enter data()
8: save changes()
9: logoff()
Fig 9: Sequence Diagram for the Management of Database
Collaboration Diagrams
user system
database
1: access the net()3: select functions to be performed()
2: give options()5: perform the function()
4: look for required information()
Fig 10: Collaboration Diagram for the System
user System
database
1: access the net()3: enter username and password()
2: ask for the username and password()
4: check for validity()5: authorize()
Fig 11: Collaboration Diagram for the Login
lecturer system
dba database
1: acess net and select login option
2: enquire for username and password
3: enter username and password
4: check for validity
5: validate
6: give options
7: select offer courses option
8: get course details
9: give course details
10: display course details
11: select course to offer
12: send details
13: save changes
14: logout
Fig 12: Collaboration Diagram for the offer courses
Lecturer System
DBA DataBase
1: acess net and select update option
2: enquire for username and password
3: enter username and password
4: check for validity
5: Validate
6: enquire for course and semester details
7: enter course and semester details
8: check for validity of course and semester
9: validate course and semester
10: accept student marks
11: enter marks for all students
12: send details to dba
13: save changes
14: logout of system
Fig 13: Collaboration Diagram for the updating of Marks
student system
database
1: access net & select admission option()3: give necessary details and documents()
2: provide relevant form for the selected course()5: admit if selection criteria are met()
7: allot roll number and dispatch necessary billing()
4: check for availability of seats and eligibility()6: make necessary modifications()
Fig 14: Collaboration Diagram for the admission
student system
database
1: access net & select result option()3: give course & semister()
7: enter roll number()
2: provide result form()6: enquire for roll number if validated()
10: display result()
4: check for validity of course & semister()8: check for validity of roll number()
5: validate()9: validate and give result()
Fig 13: Collaboration Diagram for the Result
DBA system
database
1: access net & select namagement option()3: enter user name & password()6: select task to be performed()
7: enter data()9: logoff()
2: enquire for username & password()
4: check for validity()8: save changes()
5: validate()
Fig 14: Collaboration Diagram for the Management of Database
Activity Diagrams
check result
Access the net
Options:1) Admission2) check results
student loginlecturer / DBA
Options:1) offer courses2) updation of marks
Lecturer
Options:1) Allocation of privilages2)maintainance of db
DBA
Admission
offer course
updation of marks
maintaince of database
Allocation of privilages
log off
Fig 15: Activity Diagram for System
Access the net
enter the user name and pass word
verify password
retry
Allow access to database
on success
on failure
[ 3 times ]
Fig 16: Activity Diagram for Login
Acess the net
Options: 1)Admission,2)Check Results
Perform Results Function
Check For Available Courses
Check for availability of courses
Continue the process
Available
Abort the process
Not Available
Check For Eligibility
Not Eligible
Accept details through online form
Eligible
Admit the Student into course
Allot Rollnumber and Dispatch Billing to the student
Make necessary changes in the Database
Fig 17: Activity Diagram for Admission
Acess the net
Options: 1)Admission,2)Check Results
Perform Admission Function
Accept Course and Semester
Check For Validity Of Course And Semester
Abort the Process
Invalid
Accept Roll number
Valid
Check Validity Of Roll number
Invalid
Display Results
Valid
Fig 18: Activity Diagram for Result Function
Acess the net
Verification Of Password
Abort the process
Not Valid
Options:1:Update Student Database. 2)Update Lecturer Database 3)Update Course Database 4)Allot Roles And Privilages,5)Other Modifications
Valid
Access the desired function to be performed by the DBA
Make Necessary Changes in the Database
Log-off
Fig 19: Activity Diagram for DBA Functionality
Acess the net
Login By Lecturer
Verification Of Password
Abort the Process
Invalid
Accept Course and Semester from Lecturer
Check Validity Of Course and Semester
Retry
AcceptMarks each Student
Save Changes to Database
Log-off
Invalid
Valid
Fig 20: Activity Diagram for Updating of Marks
access the system
select function to be performed
process and send changes
provide option
look for required function
give details to user
update database
save changes
provide details
data basedbasystemuser
Fig 21: Activity Diagram for System Using Swim Lanes
State chart Diagrams
IDLE
Active
connected
Processing
Display
connected
Processing
Display
on Select
on Access
error / print report
on Completion
end of transition
hang up
Entry / LoginExit / log off
Fig 22: State Chart Diagram for System
Component Diagrams
course enrollment.exe
database.exe
student lecturer dba
student.exe lecturer.exe dba.exe
Fig 23: Component Diagram for System
Deployment Diagrams
PC with Browser
PC With Browser
NewDevice3
Web ServerPrinter
Data Base Server
internet internet internet
intranet
cable
Fig 24: Deployment Diagram for System
Write the following contents of Each Diagram:
1. Aim Of Experiment2. Requirement Specification3. Theory4. Procedure to Draw the Diagram5. Observations and Analysis of Observations6. Conclusions
Use Case Specification: In order to better understand the various scenarios of a use case, it is to be detailed. This is possible by writing use case specification. It helps in making requirements complete, consistent and unambiguous. The typical format of use case specification (Detailing a use case) is as follows:
Use Case ID:Use Case Name:Created By: Last Updated By:
Date Created: Date Last Updated:
Actors:Description:Preconditions:Post conditions:Normal Flow:Alternative Flows:Frequency of Use:Business Rules:Assumptions:
