Reference no: EM13333646

Submit all required artefacts necessary to achieve the ‘Life Cycle Objectives Milestone' (LCOM). These are:

1. A Vision document setting out the business objective and business case for the system, and the scope of the proposed system (use the Vision template from the OpenUP) (10% overall assessment).
2. A prioritised Risk List, together with intended risk mitigation strategies (5% overall assessment).
3. A Glossary defining important, or ambiguous terms, and any acronyms used (1% overall assessment).
4. An initial Architectural Model consisting of initial versions of all 6 relevant UML models (Use case, analysis, design, implementation, test, and deployment models) (2% overall assessment).
5. An initial Project Plan outlining at a high level the functional increments planned to achieve project completion. Use the project skeleton in Appendix A of the Study Guide or contained in the Resources section of the subject Interact site. The project plan should include a more detailed breakdown for the Elaboration phase, detailing high level objectives for each iteration (2% overall assessment).
6. Sponsor signoff indicating agreement to proceed with the proposed system.

The aim of the LCOM is to convince a sceptical audience that the project is both worth doing, and doable. If you cannot achieve the LCOM by the due date you must apply for an extension and complete it before proceeding with the project. The LCOM is a ‘pull the plug' milestone, and it is possible to both fail this unit, and be barred from enrolling in the second project unit at this point.

Identify the most difficult, risky, critical, core use case, and then identify 2 or 3 architecturally significant increments in system functionality required to support that use case. Prioritise these increments in terms of risk to the project and make these increments the high level objectives for the Elaboration iterations.

Plan to flesh out the design to support the selected use case in the first Elaboration iteration. Also plan to establish the development environment if you have not already done so. As part of establishing the development environment, consider what in-line documentation tool, what unit test framework, and what version control software you will use.