Project Progress
Task 1: Project planning
1.1 Draw a Gantt chart showing the project planning across the whole assignment process.1.2 Create a Trello board for managing your assignment, and maintain the Trello board across the whole assignment process. Submit a set of snapshots for the Trello board showing the updating process.
Task 2: Requirements Documentation Write a requirement, in plain English, for the scenario “Pay Fine”. You may need to make creative assumptions for assignment purposes, and pretend you have conducted requirements elicitation with the client.
Your requirements will be assessed based on whether they:
• are verifiable, non-ambiguous, modifiable, traceable, consistent, and complete
• form a set of conditions, not only a series of operations / process descriptions
• relate to system requirements, not only business process
Hint: This is a potentially large task if you let your imagination run away with you. Try to keep your requirements to the minimum – you are not being assessed on creativity or system knowledge, just your ability to write a requirement!
Task 3: Use case diagram
You should provide one use case diagram that includes all actors and use cases within scope. Your diagram must include a use case named ‘Pay Fine’, as documented in Task 2. Your diagram will be assessed based on:
• Consistency with the scope including the specific functionality requested
• Appropriate use of actors, includes/extends, and generalization
• Appropriate use of UML notation
Task 4: Use case textual description
Borrowing a book is the key function of this system. This functionally includes searching, borrowing and returning book to the library. Develop a description of the use case using “Template – Use Case textual description” as per
Hint: This is a potentially large task if copious low-level data is included, so ensure you provide the appropriate level of information. For example, in the flow of events a step may be “Log in” or “System validation” instead of “insert student card with bar code facing up for scanning”.
Task 5: Sequence diagram
You should create a sequence diagram for the scenario below: Lee is a current student with active borrowing privileges. At a desk physically located in the library, Lee searches for the book named “UML Distilled”. Viewing the results, Lee notes it is currently on loan and places a hold on the item. Your diagram should highlight how objects interact to achieve the aims of the user and any objects that are created or destroyed. Your diagram will be assessed based on:
• Completeness and consistency with the scenario
• Appropriate identification and use of objects, messages, etc.
• Appropriate use of UML notation
Task 6: Class diagram of the library system
You should create one class diagram that reflects the data and behaviours of the library system.Your diagram will be assessed based on:
• Consistency with the scope including the specific functionality requested
• Consistency with use case model in Task 3
• Inclusion of key classes, data members, operations and well-specified relationships
• Appropriate use of UML notation
Task 7: Activity diagram
Create an activity diagram to show the activities that are involved in a student searching for a book, and placing it on hold. Your diagram will be assessed based on:
• Completeness and consistency with both the scenario and the sequence diagram in Task 5.
• Appropriate identification and use of activities, transitions, decisions, branches, swim-lanes, etc.
• Appropriate use of UML notation
Task 8: User interface design
Create mock-up interface for administrators of the library. Your interface should have separate pages to perform following tasks (each task may need several pages to accomplish a task):
• Login, logout, forgotten password and registration pages for library admin.
• Library loans’ interface: This interface at least should able to show loans, overdue loans, history of past loans and search loans with different criteria.
• Library member’s interface: This interface should include different pages for adding removing, suspending members of the library. It should also have the page for searching member’s information (registered information and loan history).
• Library borrowable items interface: Library borrowable items fall into different categories including books, audio/videos material, and facility booking (e.g. room, computer). Each borrowable type item should have pages for adding, removing, and searching borrowable items.
Task 9: Test case generation
Design a set of test cases based on the activity diagram that you design in Task 7. Your test cases are aimed at checking validity of user input and common vulnerabilities of your system. Your test casts should follow the format of the below table.
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
|
