Reference no: EM133148739

Software/System Deconstruction using UML Models

This is a report you are making for the company that is using of the System, or for owner of the System. Here, you are showing that: (i) you have analysed the System comprehensively, from the perspective of an IS[1] Business Analyst, and (ii) identified some issues that could be fixed and/or some opportunities/functionalities/services that could be incorporated with the current System. You not only identify and mention these opportunities/functionalities/services but show in the UML diagrams how those will change the existing models (i.e., UML diagrams).
Format for the report and mark distribution
• Executive Summary (max 1 page[2])
• Business case (5 marks): (minimum 2, maximum 3 page)
o The background of the industry the system is operated
o The background of company the system belongs to or operated by
o What are the services/problems the company addressing by this system
o What are the opportunities of such a system/solution?
• Using UML models, discuss how the System is now operating (page limits not relevant here):
o Present an important process using Activity Diagram and briefly explain it.
o What services are offered to various users? Explain it with an overall use case diagram.
o In order to make more sense of the use cases, expend a use case and present a detailed use case diagram.
o Present a Class diagram and briefly explain the relationships.
o Present and briefly explain a State Machine Diagram.
• Each diagram should be narrated briefly so that any person who not necessarily a Business Analyst can understand your diagrams and the report. The marks are allocated for both the diagrams as well as the discussion.
• Narratives about the User Interface (UI) Design. Discuss the good, the bad, and the ugly side of the UI designs of the System - what are the best designs of the System, and how some interfaces could be improved? (1.5 to 3 page, do not occupy space with large pictures)
• What improvement or additional features you would add if you were appointed, as the business analyst, to upgrade it the System. How do you think this/these will add value (e.g., revenue, user satisfaction, business growth) to the System; tell in detail? Support your claim with references from published materials (e.g., journal article, newspaper article, magazine, business report, and web sites)
• Incorporate the new features/improvements in any two diagrams e.g., overall use case diagram, Class diagram, Activity diagram, or State diagram.
o Please note: If you use overall use case diagram where you add new use case(s) (with new <<include>>, <<extend>> and/or generalisation relationship), one (new) use case needs to be expanded i.e., present a detailed use case diagram; and this will be considered as the second diagram.
o Also note: just having them in the diagram is not sufficient; you need to explain so that a nonprofessional can understand how the new feature(s) will be integrated with the legacy system, and add value.
• References - both in-text referencing as well as reference list (presented at the end of the report, before appendix) will be marked. Quality of referencing - consistent application of a referencing style and the quality of the sources[3].
• Professional look of the report
• Appendix (no mark, but presentation of the appendix may affect the mark for ‘professional look':
o links and screen-shots of the system (however, you can report them in the report also but logically)
o the proposal submitted earlier (which was eventually been approved by your tutor).
o Any other things you want to share.