Assignment - Li
ary System
Suppose that you are required to document a li
ary system, particularly focusing on the functionality at
the back end. The scope the system’s back end is defined as follows:
• You should include all system functions and data, such as bo
owing items, accessing both physical
and electronic items, renewing loans, viewing a bo
ower’s account (including overdue items and
fines), searching catalogues for various items, renewing loans, login, and asking a li
arian. Note
that this list is not exhaustive.
• Some functionality (such as book rooms, access databases, bo
ow ebooks) is provided by
applications integrated with the UNI li
ary system. As such, you will need to show that the
functionality is captured, but that no structural data is retained in this system.
• Front-end content, such as ‘getting started in the li
ary’, information pages (with static HTML
content), the ‘About’ section, reference guides, and general information, is out of scope, and thus
is not required to be included in your work.
Some specific functionality is not necessarily apparent from public or student views, but should be
included:
• An ITS officer uploads a list of lists of active bo
owers each year. The list contains staff, student
and ‘others’. On this list:
a. staff have a staff ID, barcode, name, DOB, and department
. students have a student ID, barcode, name, DOB and department
c. others have a bo
ower ID, name, DOB, address & license number
• The uploaded list is compared to existing bo
owers by the system. If a person have left the
university, his/her account will be removed if they have no unpaid fines. Otherwise, their
o
ower status is changed to inactive, and their record is retained. A new bo
ower account is
created for a new person on the list
• Li
arians can also add bo
owers. They create a bo
ower account with a name, DOB, and an
expiry date.
• If bo
owers do not have a card with a barcode (such as those that are just created by the
li
arian), their bo
owing status is pending until they collect a li
ary bo
owing card from the
li
ary.
• If a bo
ower is late in returning items, a fine occurs. When a bo
ower has a fine exceeding $25,
they can no longer renew or bo
ow any items until the fine is paid. Li
ary fines must be paid in
person to a li
arian, who will then mark the fine as paid in the system and issue a receipt.
• Li
arians can view any record in the system – catalogue items, bo
ower records, etc. They can
search for a record or scan a barcode (of an item or bo
ower) to view the data.
• A bo
ower’s status can either active, inactive, pending, temporary, or suspended.
• Staff may request the li
ary to place items used by their course on ‘reserve’ or ‘restricted
o
owing’. Staff may also submit past exam papers to the li
ary.
• The head li
arian generates reports based on item usage, bo
owing rates, and li
ary usage by
department type (staff and student).
You are required to play the role as a technical business analyst, analyzing the li
ary system and creating
diagrams as requested in the questions that follow. Note you are not modelling a website using
storyboards, site-maps etc., but rather the back-end behavioural and structural needs of the system.
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
equirements 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
Bo
owing a book is the key function of this system. This functionally includes searching, bo
owing and
eturning book to the li
ary. Develop a description of the use case using “Template – Use Case textual
description” as per Appendix.
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 cu
ent student with active bo
owing privileges. At a desk physically located in the li
ary, Lee
searches for the book named “UML Distilled”. Viewing the results, Lee notes it is cu
ently 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 li
ary system
You should create one class diagram that reflects the data and behaviours of the li
ary 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,
anches, swim-lanes, etc.
• Appropriate use of UML notation
Task 8: User interface design
Create mock-up interface for administrators of the li
ary. 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 li
ary admin.
• Li
ary loans’ interface: This interface at least should able to show loans, overdue loans, history
of past loans and search loans with different criteria.
• Li
ary member’s interface: This interface should include different pages for adding removing,
suspending members of the li
ary. It should also have the page for searching member’s
information (registered information and loan history).
• Li
ary bo
owable items interface: Li
ary bo
owable items fall into different categories
including books, audio/videos material, and facility booking (e.g. room, computer). Each
o
owable type item should have pages for adding, removing, and searching bo
owable 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.
Number Test name Description Scenario Precondition Input Expected output
Submission timeline
There will be two stages for submitting the assignment:
• Stage 1 of the assignment will include Tasks 1 to 5. The weighting of stage 1 in the whole
assignment is 40%. You should put all the outcomes of Tasks 1 to 5 into one document in a single
.doc, .docx, or .pdf file. The deadline for stage 1 will be 5pm, Friday the 11th of May 2018 (Week
7).
• The second and final stage of the assignment will include all tasks. The weighting of stage 2 in the
whole assignment is 60%. Though you already submitted Tasks 1 to 5 in stage 1, they may be
updated based on the lecturer’s feedback as well as your work on Tasks 6 to 9. You should put all
the latest outcomes of Tasks 1 to 9 into one document in a single .doc, .docx, or .pdf file. The
deadline for the final stage will be 5pm, Friday the 15th of June 2018 (Week 12).
Note that this is an individual assignment. Every student should submit his/her own work by the due date.
Late submission will incur a penalty – 10% of the total possible mark will be deducted for each day past
the deadline (including public holidays and weekends). Students with special circumstances (acute illness,
loss or bereavement, hardship or trauma) may apply for an extension up to five days.
Appendix: Template for use case textual description
Name This must have an identical name as one of the use cases in the use case diagram.
(it is an expanded description of it)
Version Identifier to distinguish between versions of one use case.
Goal A one-sentence summary of the use cases existence.
Summary A short paragraph describing the process that is followed.
Actors List the primary actor (the person who initiate the use case) and the secondary
actors (anyone else who is involved in the use case). These should be a job title, not
individual’s name.
Be careful to distinguish between data and