Convincing Features
Assignment Type
Subject
Uploaded by Malaysia Assignment Help
Date
This project is to be done by the students as a group.
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
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.
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.
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.
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.
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.
| i | Integrity pledge |
| ii | Task breakdown |
| 1 | Interface Prototype
Interface prototype designs can be simple but must capture the proposed functionality of the library application. Designs must be sufficient for requirements fact-finding. |
| 2 | Requirements / Specifications
All requirements must follow the characteristics of good requirements (found in Module 1). Requirements must be sufficiently complete and detailed. |
| 3 | UML Diagrams
The UML Diagrams must be detailed enough to remove significant uncertainties when developing the library application. |
| 4 | Cost Benefit Analysis (CBA)
Provide your best and most realistic estimations for CBA. Make sure to justify your estimations. Break down the estimations to provide better accuracy. Try to avoid using a lump sum. |
| 4.1 Estimate the project size | |
| 4.2 List Costs with justification | |
| 4.3 List Benefits with justification | |
| 4.4 State the CBA table with NPV, ROI and payback analysis |
| Excellent | Good | Adequate | |
| Interface Prototype (5m) |
5 – 4 | 3 – 2 | 1 – 0 |
| Captures most of the application functionality, and well-illustrated designs. | Captures most of the application functionality or decently designed. | Captures poorly the application functionality or poorly designed. | |
| Requirements / Specifications (5m) |
5 – 4 | 3 – 2 | 1 – 0 |
| Requirements are complete, detailed and exhibit other good characteristics. | Requirements are mostly complete, detailed and exhibit other good characteristics with minor issues. | Requirements are incomplete, lack detail or have significant issues. | |
| UML Diagrams (10m) |
10 – 7 | 6 – 4 | 3 – 0 |
| Clear, detailed, and accurate representation of the requirements. | Clear, detailed and accurate representation of the requirements with minor issues. | Unclear, lacking details or inaccurate representation of the requirements, or has significant issues. | |
| Cost Benefit Analysis (15m) | |||
| Project Size (3m) | 3 | 2 | 1 – 0 |
| Project size is reasonably estimated and justifiable. | Project size is estimated without justification. | Project size is not well estimated. | |
| List of Costs (4m) | 4 – 3 | 2 | 1 – 0 |
| Costs are estimated well with justification. | Costs are reasonably estimated with no proper justification. | Costs are not well estimated. | |
| List of Benefits (4m) | 4 – 3 | 2 | 1 – 0 |
| Benefits are estimated well with justification. | Benefits are reasonably estimated with no proper justification. | Benefits are not well estimated. | |
| CBA Table (4m) | 4 – 3 | 2 | 1 – 0 |
| All analyses were done properly with good explanations. | All analyses were done decently but lacking good explanations. | Analyses were not well done or without any explanations. | |
| Presentation (5m) | 5 – 4 | 3 – 2 | 1 – 0 |
| Students worked well in a group dynamic and questions were answered well and clearly. | Group work was a little uncoordinated, or questions were not answered well or clearly. | Group work was almost non-existent, or questions were poorly answered. | |
If you are struggling to complete your TSI6223 System Integration and Architecture Project 2 (MMU), especially with interface prototypes, UML diagrams, or cost-benefit analysis, you can choose Malaysia Assignment Help like many other students. Our experts provide project assignment help services tailored to your university requirements with well-structured solutions. You can also review our mmu assignment example to check the quality of our work. Order our online assignment helper service today and receive a 100% custom, human-written, and plagiarism-free solution.
