There is detailed what was planned to be developed by the team during the project, look that is no task has been completed yet as we are on the first day of the first week.
At the end of the first week, the project is already in progress, some tasks have already been completed such as the creation of the scope. In that way the team is doing the design of the system and analysing the requirements to be able to start the next tasks.
At this point, the development is well advanced, but as it is an important part it has been highlighted as being of high priority. We can also see that other tasks are already being completed.
At the end of the project most of the tasks have been completed, leaving only deployment and post-implementation that are in progress and about to be completed.
There is the Gantt chart that will be used by the team to create the system. Showing start dates of each task as the time limit to be delivered.
The requirements of this project can be listed as follows:
- The library management system will be implemented
- The database warehouse of the library management system would be decided
- The timeline of implementation would be decided
- The Documentation of the implementation would be done
- The use case and the sequential diagrams for the system implementation would be done
- The UML Class for the system would be implemented
- The testing of the system would be done after implementation
There is a demonstrating of an external view of the system, showing the actors, they are external elements that interact with the system and use it. In the library system, the staffs add information to the system in addition to being able to remove borrower and impose fine. On the other hand, the student interacts with the system borrowing and returning books, and pay fine as well.
Case Use Diagram – Library System:
|
Use Case Name |
Add Account |
|
Description |
Add account of student as borrower |
|
Triggering Event |
Student is enrolled in the University |
|
Actors |
Student, Staff |
|
Preconditions |
Student Enrolled |
|
Post conditions |
Student account added |
|
Exception Conditions |
Student not enrolled |
|
Use Case Name |
Add books |
|
Description |
Add books in the library |
|
Triggering Event |
Book is bought |
|
Actors |
Staff |
|
Preconditions |
Book is bought |
|
Post conditions |
Book added in the library |
|
Exception Conditions |
Book not available |
|
Use Case Name |
Borrow Book |
|
Description |
Book is borrowed by student |
|
Triggering Event |
Student is added in the system |
|
Actors |
Student |
|
Preconditions |
Student enrolled |
|
Post conditions |
Book is borrowed |
|
Exception Conditions |
Book not available |
Test case generation
|
Number |
Test Name |
Description |
Scenario |
Precondtion |
Input |
Expected output |
|
1 |
Login |
A student or a staff logins to their account |
Login to access the system |
User must have an account |
Username, password |
Session is created and the user is granted access to the system |
|
2 |
Add account |
A staff adds a student account |
New student requires an account in the system |
Student should not already be existing in the system |
Username, Name, Email, password |
A student account is created |
|
3 |
Add book |
A staff adds a new book to the system |
A new book has to be added to the system |
The book should not be already added to the system |
Unique ISBN or ID, Name, Category, quantity |
A new record of a book is created |
|
4 |
Borrow book |
A student borrows a book |
Student needs to borrow a book using the system |
The student should have an account and the book should be in the system |
studentID, bookID |
A new borrowing record is created and the status of the book is updated |
|
5 |
Return book |
A student returns a book which was borrowed |
Student needs to return a previously borrowed book |
There should be a borrowing record in the system |
borrowingID |
The status of the book is updated to available and the borrowing status is changed |
|
6 |
Impose fine |
A staff imposes a fine for a borrowed book |
Student is late on returning a borrowed book |
A student should be late on returning a book |
borrowingID |
A new record of fine is created |
|
7 |
Pay fine |
A student pays for a fine |
A fine has been imposed for returning a book late |
A fine record related to the borrowing should exist in the system |
FineID |
The status of the fine is updated to paid |
|
8 |
Generate report |
A staff generates a report |
A staff needs to generate a report |
The staff must be logged in |
Type of report |
System generates a report |
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
