|
Task Name |
Duration |
Start |
Finish |
Predecessors |
Resource Names |
|
Software Development Plan |
70 days |
Thu 7/19/18 |
Wed 10/24/18 |
||
|
Scope |
1.75 days |
Thu 7/19/18 |
Fri 7/20/18 |
||
|
Determine project scope |
6 hrs |
Thu 7/19/18 |
Thu 7/19/18 |
Management |
|
|
Secure project sponsorship |
1 day |
Thu 7/19/18 |
Fri 7/20/18 |
2 |
Management |
|
Analysis/Software Requirements |
8.75 days |
Fri 7/20/18 |
Thu 8/2/18 |
||
|
Conduct needs analysis |
5 days |
Fri 7/20/18 |
Fri 7/27/18 |
3 |
Analyst |
|
Draft preliminary software specifications |
3 days |
Fri 7/27/18 |
Wed 8/1/18 |
5 |
Analyst |
|
Obtain approvals to proceed (concept, timeline, budget) |
6 hrs |
Wed 8/1/18 |
Thu 8/2/18 |
6 |
Management,Project Manager |
|
Analysis complete |
0 days |
Thu 8/2/18 |
Thu 8/2/18 |
7 |
|
|
Design |
8.5 days |
Thu 8/2/18 |
Tue 8/14/18 |
||
|
Review preliminary software specifications |
2 days |
Thu 8/2/18 |
Mon 8/6/18 |
8 |
Analyst |
|
Develop functional specifications |
5 days |
Mon 8/6/18 |
Mon 8/13/18 |
10 |
Analyst |
|
Obtain approval to proceed |
12 hrs |
Mon 8/13/18 |
Tue 8/14/18 |
11 |
Management, Project Manager |
|
Design complete |
0 days |
Tue 8/14/18 |
Tue 8/14/18 |
12 |
|
|
Development |
17 days |
Wed 8/15/18 |
Thu 9/6/18 |
||
|
Review functional specifications |
1 day |
Wed 8/15/18 |
Wed 8/15/18 |
13 |
Developer |
|
Identify modular/tiered design parameters |
1 day |
Thu 8/16/18 |
Thu 8/16/18 |
15 |
Developer |
|
Develop code |
15 days |
Fri 8/17/18 |
Thu 9/6/18 |
16 |
Developer |
|
Development complete |
0 days |
Thu 9/6/18 |
Thu 9/6/18 |
17 |
|
|
Testing |
28 days |
Fri 9/7/18 |
Tue 10/16/18 |
||
|
Develop unit test plans using product specifications |
4 days |
Fri 9/7/18 |
Wed 9/12/18 |
18 |
Testers |
|
Develop integration test plans using product specifications |
4 days |
Thu 9/13/18 |
Tue 9/18/18 |
20 |
Testers |
|
Unit Testing |
10 days |
Wed 9/19/18 |
Tue 10/2/18 |
||
|
Review modular code |
5 days |
Wed 9/19/18 |
Tue 9/25/18 |
21 |
Testers |
|
Modify code |
3 days |
Wed 9/26/18 |
Fri 9/28/18 |
23 |
Testers |
|
Re-test modified code |
2 days |
Mon 10/1/18 |
Tue 10/2/18 |
24 |
Testers |
|
Unit testing complete |
0 days |
Tue 10/2/18 |
Tue 10/2/18 |
25 |
|
|
Integration Testing |
10 days |
Wed 10/3/18 |
Tue 10/16/18 |
||
|
Test module integration |
5 days |
Wed 10/3/18 |
Tue 10/9/18 |
26 |
Testers |
|
Identify anomalies to specifications |
2 days |
Wed 10/10/18 |
Thu 10/11/18 |
28 |
Testers |
|
Modify code |
3 days |
Fri 10/12/18 |
Tue 10/16/18 |
29 |
Testers |
|
Integration testing complete |
0 days |
Tue 10/16/18 |
Tue 10/16/18 |
30 |
|
|
Documentation |
1 day |
Wed 10/17/18 |
Wed 10/17/18 |
||
|
Develop Help specification |
1 day |
Wed 10/17/18 |
Wed 10/17/18 |
31 |
Technical Communicators |
|
Documentation complete |
0 days |
Wed 10/17/18 |
Wed 10/17/18 |
33 |
|
|
Pilot |
4 days |
Thu 10/18/18 |
Tue 10/23/18 |
||
|
Identify test group |
1 day |
Thu 10/18/18 |
Thu 10/18/18 |
34 |
Project Manager |
|
Develop software delivery mechanism |
1 day |
Fri 10/19/18 |
Fri 10/19/18 |
36 |
|
|
Install/deploy software |
1 day |
Mon 10/22/18 |
Mon 10/22/18 |
37 |
Deployment Team |
|
Evaluate testing information |
1 day |
Tue 10/23/18 |
Tue 10/23/18 |
38 |
Deployment Team |
|
Pilot complete |
0 days |
Tue 10/23/18 |
Tue 10/23/18 |
39 |
|
|
Post Implementation Review |
1 day |
Wed 10/24/18 |
Wed 10/24/18 |
||
|
Document lessons learned |
1 day |
Wed 10/24/18 |
Wed 10/24/18 |
40 |
Project Manager |
|
Post implementation review complete |
0 days |
Wed 10/24/18 |
Wed 10/24/18 |
42 |
|
|
Software development template complete |
0 days |
Wed 10/24/18 |
Wed 10/24/18 |
43 |
Figure 1: Gantt chart
Figure 2: Trello board
Functional Requirements:
Register: The user have to sign up in the portal with proper specification provided in the page.
Login: The user has to put their login credentials to log into their profile.
Book Issued: List of books will be displaced along with data of return.
Search: Enter the name of author’s name of the books to be issued.
Return: The retuned book will be updated in the database of the portal.
Fine: The fine will be calculated, if it crossed the date of return and the user did not renewed if then fine will be applied by $1 per day. When a borrower has a fine exceeding $25, they can no longer renew or borrow any items until the fine is paid.
Add books: Details of books including book name, author name and quantity will be updated.
Remove books: Enter the name of the book in the search box and remove the book by clicking on delete. The database will be updated.
Usability requirement: The system will help users to access the system from their android devices.
Availability Requirement: The system has been available for the users and can be used for 24 hours a day and 365 days a year.
Efficiency requirement: Even the system fails, the system is able to recover back all the data within an hour.
Figure 3: Use case diagram of Library system management
|
Name |
Online Library Management system |
|
Version |
1.0 |
|
Goal |
Borrow a book from library |
|
Summary |
Borrowing a book is the main function of the use case. |
|
Actors |
Borrow books |
|
Pre-conditions |
The borrower should be a registered user |
|
Triggers |
User registers himself in the portal |
|
Basic course of Events |
Registering-searching a book-Borrowing a book- approval |
|
Alternative Paths |
Login-borrowing a book-approval |
|
Post-Conditions |
Book is borrowed |
|
Business Rules |
Book is borrowed only if it is in the database |
|
Notes |
Book needs to be return on time |
Figure 4: Sequence Diagram of library management system
Figure 5: Class Diagram of the library system
Figure 6: Activity diagram
|
Number |
Test name |
Description |
Scenario |
Precondition |
Input |
Expected output |
|
1 |
Register |
User registers into the portal. |
Unregistered user needs to register themselves on the portal |
The user is unregistered |
User puts their details on the registration page |
If user put wrong information, user is not registered. |
|
2 |
Login |
Registered needs to login into their account. |
Registered users put their login credentials into the login page |
The user is already a registered user. |
The user puts their login credentials on the login page. |
If the user put wrong credentials, user can login into their account. |
|
3 |
Borrowing a book |
User needs to borrow a book form the portal. |
User wants to borrow a book from the library. |
The user has log in into their account. |
The user needs to search for the book in the search box. |
After searching, if book is found, it gets borrowed. |
|
4 |
Removing a book |
Admin needs to remove a book from portal. |
Admin wants to delete a book from the database |
Book is added in the database. |
Admin needs to search the book. |
If book is not found after searching, book cannot be deleted. |
References
Bryson, J. (2017). Effective library and information centre management. Routledge.
Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.
Moran, B. B., & Morner, C. J. (2017). Library and information center management. ABC-CLIO.
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
