Reference no: EM131483614 , Length: word count:2000

Task -

In this assessment item, you are required to provide the detailed architecture and design of the system presented in Assessment Item 1 in report form. The total number of words should be between 1800-2000. Please note the words included in the diagrams/figures will not be counted. Amongst the information sought are answers to the following questions:

Questions you need to address are:

1. Identify and briefly describe the main functional and non-functional requirements for the major systems areas of the case study.

2. Explain the role of use cases for the creation of a domain model of the problem domain and draw use case diagrams for all systems in the case study that show all actors and use cases.

3. Draw a UML domain model class diagram for all systems in your chosen case study. Be as specific and accurate as possible, given the information provided. If needed information is not given, make realistic assumptions.

4. Review the functional and non-functional requirements for the major systems areas of the case study you have developed in question 1. Then, for each of the five design activity of SDLC, list and briefly describe some specific tasks required for each design activities (i.e., describing the environment, designing application components, user interfaces, the database, and software methods.

5. Develop a System Vision Document to give the total vision of the system and develop a work breakdown structure (WBS) for the project's first iteration.

Rationale

This assessment tasks covers the fundamental concepts of object modeling, use cases, dynamic models and has been designed to ensure that you are engaging with the subject content on a regular basis. The purpose of the assessment task is to strengthen the student's skill in developing a detailed OO design using UML notation, based on a set of user requirements. More specifically it assess your ability to:

• Apply the concepts of object orientation methodology;
• Analyse system requirements to determine the use cases and domain model of the problem domain;
• Create class diagrams and dynamic models with UML notations;
• Perform modeling of various aspects of systems to construct quality diagrams from a case study.