TSI6223 System Integration and Architecture Project 2 2026/27 | Multimedia University

TSI6223 Project 2 (40%)

This project is to be done by the students as a group.

• Each group (“the development team”) will consist of a maximum of FOUR (4) students.
• The report should be single spaced and using Calibri font sized 11.
• The report must have the front cover as per the appendix.
• The report must fulfill all the required sections as per the table of content.
• The report should be neatly formatted.
• Interface prototype designs can be drawn using proto.io.
• UML diagrams can be drawn using draw.io.
• The report must be submitted before the presentation to the lecturer (“project sponsor”) on week 14.

Due to the successful implementation of the information system to track students’ progress for each trimester, College ABQ is planning to further expand their student experience by implementing a new application to handle library matters for students and staffs. The application should have basic features such as

1. Search books in the college library to display information about the book.
2. Check out a book from the library.
3. Return a book to the library.
4. Check student’s information (eg fees owed).

The development team may propose other beneficial features that will enhance the student’s experience with the college library. Since the college library is currently not using any computerized system to handle library matters, the development team needs to put in more effort to come up with the requirements for the application.

Part 1: Interface Prototype

The development team must come up with a simplified version of an interface prototype as a factfinding method to get a more accurate version of the library application requirements. The development team may use the interface prototype to query the project sponsor about the requirements.

Part 2: Requirements / Specifications

After the interview with the project sponsor, the development team needs to write the requirements gathered using the characteristics of good requirements. If possible, elevate the requirements to the standard of specifications.

Part 3: UML Diagrams

Draw the appropriate UML diagrams to model the requirements written in in part (2). The type and number of UML diagrams will be decided by the development team, as long as the UML diagrams sufficiently describe the library application.

Part 4: Cost Benefit Analysis

Perform cost-benefit analysis to demonstrate the profitability/viability of the library application to the college. All assumed cost / benefit must be sufficiently justified and reasonable.

Appendix 1: Table of content.

TSI6223 Marking Rubric