Srs Use Case Documentation,
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Srs Use Case Documentation, as PDF for free.
More details
- Words: 565
- Pages: 8
SRS USE CASE DOCUMENTATION FOR
OBJECT ORIENTED SOFTWARE ENGINEERNING
(SEMESTER PROJECT) TITLE: UNIVERSITY MANAGEMENT SYSTEM (LIBRARY and FI)
Submitted by: SHAKIR BASHIR ALVI M.HANZALA ALI ABBASS Submitted to: ENGR. AMINA
USE CASE DIAGRAM and DOCUMENTATION for LMS: Library management system is being made for ease of the people who visits library for book reading or consulting their respected books without getting in for the old conservative process and try to gain maximum use of computing/software engineering world. As it’s this project is the part of our course Object oriented software engineering so we have to make its USE CASE DIAGRAM and document it. USE CASES: ACTORS:
The actors which are participating in the case are 6 namely LIBRARIAN:
The one who manages the library and its database and rapidly keeps on updating the students or people records for issuing books and etc. LIBRARIAN DATABASE:
You can say this as an assistant librarian. STUDENT:
As this project is being made for the UNIVERSITY LIBRARY so obviously the main user for this would be the student itself. GUEST:
A guest who don’t have the membership of the library comes to it and wants to have membership. VIP USER:
The one who can borrow DVD games etc other accessories in the library REGULAR USER:
A regular user is the one who is not the VIP or but a student who wants to get VIP membership.
the student
the librarian
guest
asst.librarian
VIpUSER
ENTRY CONDITIONS FOR ULMS:
The entry condition for accessing the ULMS is just to log in the system. SEPARATE FLOW OF EVENTS FOR EACH ACTOR: THE LIBRARIAN; 1- SEARCH BOOKS: For searching books . Extended case: Invalid search.
2-Add record: Adding the records of new arrivals or maintaining the old ones by renewing them. Included case: He has to maintain the database after doing this.
3-Delete books: For deleting the old books which have been eliminated from the library. Extended case: The ID of the books is invalid.
4-Update the books status: After the issuing of book to users maintains the status of book to issued. Extended case: Invalid id. Included case: Update id.
THE LIBRARY DATABSE OFFICER: He has to prepare the database for the library.
THE STUDENT: 1-Authentication: Authenticate his self by giving username and password of his library ID. Extended case: Invalid username or password.
2-Search books: he searches his required books. Extended case: Invalid id or name.
3-Reserve books. He reserves books which he see is issued earlier and he needs it too. Extended case: Report the status ID.
4-RE-issuing of books: He needs the issued book for more time then allowed by library so he has to re issue it. Extended case: Invalid id.
5-Check accounts: For checking his record of books.
VIP USER: 1-Borrows DVD,Games: 2-home delivery. 3-request new books.
EXIT CONDITION: After the books are issued,reissued, etc.
USE CASE INDEXES : Use case ID 1 2 3 4 5 6 7 8 9 10
Use case name
Primary actor
Scope
Complexity
Priority
Search books Add record Update record Delete book Prepare library database Register for membership
Librarian,student Librarian Librarian Librarian Asst.Librarian
In In In In In
High High High High High
1 2 2 2 1
Guest
In
Low
1
Authentication Reissue Check accounts Borrow dvd’s
Student Student Student
In In In
High High Low
1 2 2
VIP USER
In
Low
1
THE USE CASE DIAGRAM MAIN VIEW:
OBJECT ORIENTED SOFTWARE ENGINEERNING
(SEMESTER PROJECT) TITLE: UNIVERSITY MANAGEMENT SYSTEM (LIBRARY and FI)
Submitted by: SHAKIR BASHIR ALVI M.HANZALA ALI ABBASS Submitted to: ENGR. AMINA
USE CASE DIAGRAM and DOCUMENTATION for LMS: Library management system is being made for ease of the people who visits library for book reading or consulting their respected books without getting in for the old conservative process and try to gain maximum use of computing/software engineering world. As it’s this project is the part of our course Object oriented software engineering so we have to make its USE CASE DIAGRAM and document it. USE CASES: ACTORS:
The actors which are participating in the case are 6 namely LIBRARIAN:
The one who manages the library and its database and rapidly keeps on updating the students or people records for issuing books and etc. LIBRARIAN DATABASE:
You can say this as an assistant librarian. STUDENT:
As this project is being made for the UNIVERSITY LIBRARY so obviously the main user for this would be the student itself. GUEST:
A guest who don’t have the membership of the library comes to it and wants to have membership. VIP USER:
The one who can borrow DVD games etc other accessories in the library REGULAR USER:
A regular user is the one who is not the VIP or but a student who wants to get VIP membership.
the student
the librarian
guest
asst.librarian
VIpUSER
ENTRY CONDITIONS FOR ULMS:
The entry condition for accessing the ULMS is just to log in the system. SEPARATE FLOW OF EVENTS FOR EACH ACTOR: THE LIBRARIAN; 1- SEARCH BOOKS: For searching books . Extended case: Invalid search.
2-Add record: Adding the records of new arrivals or maintaining the old ones by renewing them. Included case: He has to maintain the database after doing this.
3-Delete books: For deleting the old books which have been eliminated from the library. Extended case: The ID of the books is invalid.
4-Update the books status: After the issuing of book to users maintains the status of book to issued. Extended case: Invalid id. Included case: Update id.
THE LIBRARY DATABSE OFFICER: He has to prepare the database for the library.
THE STUDENT: 1-Authentication: Authenticate his self by giving username and password of his library ID. Extended case: Invalid username or password.
2-Search books: he searches his required books. Extended case: Invalid id or name.
3-Reserve books. He reserves books which he see is issued earlier and he needs it too. Extended case: Report the status ID.
4-RE-issuing of books: He needs the issued book for more time then allowed by library so he has to re issue it. Extended case: Invalid id.
5-Check accounts: For checking his record of books.
VIP USER: 1-Borrows DVD,Games: 2-home delivery. 3-request new books.
EXIT CONDITION: After the books are issued,reissued, etc.
USE CASE INDEXES : Use case ID 1 2 3 4 5 6 7 8 9 10
Use case name
Primary actor
Scope
Complexity
Priority
Search books Add record Update record Delete book Prepare library database Register for membership
Librarian,student Librarian Librarian Librarian Asst.Librarian
In In In In In
High High High High High
1 2 2 2 1
Guest
In
Low
1
Authentication Reissue Check accounts Borrow dvd’s
Student Student Student
In In In
High High Low
1 2 2
VIP USER
In
Low
1
THE USE CASE DIAGRAM MAIN VIEW:
Related Documents
Srs Use Case Documentation,
June 2020 2
Srs
July 2020 36
Srs
October 2019 34
Srs
October 2019 36
Srs
November 2019 36
Srs
June 2020 20More Documents from ""
Srs Use Case Documentation,
June 2020 2
Creating Linked Lists In C
May 2020 8
Mobile Ad Hoc Networks (manet)
May 2020 8
Object Oreinted Software Engineering/uml
June 2020 8
In Fix To Post Fix Conversion
May 2020 6