Late Submission Policy & UML Analysis: Systems Design Essay

Late submission of coursework policy:

Late submissions will be processed in accordance with current University regulations which state: “the time period during which a student may submit a piece of work late without authorisation and have the work capped at 40% [50% at PG level] if passed is 14 calendar days. Work submitted unauthorised more than 14 calendar days after the original submission date will receive a mark of 0%. These regulations apply to a student’s first attempt at coursework. Work submitted late without authorisation which constitutes reassessment of a previously failed piece of coursework will always receive a mark of 0%.”

Summary of Assignment

Based on a Case Study, students are expected to draw and discuss: an Analysis Class Diagram, a Communication Diagram, and a Sequence Diagram. Students are also expected to discuss and evaluate the usefulness of UML diagrams and a CASE tool during analysis and design.

Diagrams should be created in Enterprise Architect and inserted into a Word or PDF file to accompany the discursive aspect of the assignment.

University policies on late submission of coursework and plagiarism will be strictly adhered to for this assignment.

This is an individual assignment. This part of the coursework represents 60% of the module mark.

The marking schemes indicate how marks are given for each aspect of the work.

Learning Outcomes (from module template)

1 Have a comprehensive understanding of the role of the systems analyst/ designer, the context in which the systems development activity takes place and the professional standards that are applied to the activity.

2 Apply up to date structured techniques to produce analysis and/or design models for a given case study problem

Part 1. Use Case Realisation for the ‘Record New Tour’ Use Case Analysis Class Diagram

a) In your own words, briefly describe what is meant by an Analysis Class Diagram, and how class diagrams can be useful in systems analysis and design (100 words approx.).

b) Draw an Analysis Class Diagram for the ‘Record New Tour’ Use Case, using the Use Case description given. This should include all required boundary, control and entity classes with their associations and attributes. Your diagram should be drawn using the Enterprise Architect software and copied and inserted as a picture into your document.

c) Write a brief summary of the decisions made whilst drawing the diagram, and your reasons for making those (150 words approx.).

Communication Diagram

a) In your own words, briefly describe what is modelled in a Communication Diagram, and how Communication Diagrams can be useful in systems analysis and design (100 words approx.).

b) Draw a Communication Diagram for the use case in your diagram that corresponds most closely to the use case ‘Record New Tour’, using the Use Case description given. This should include all control, boundary and entity objects involved in the scenario and sufficient detail of the messages to show that the interaction is feasible and would meet the system requirements. Your diagram should be drawn using the Enterprise Architect software and copied and inserted as a picture into your document.

c) Write a brief summary of the decisions made whilst drawing the diagram, and your reasons for making those (150 words approx.).

Part 2. Sequence Diagram

a) In your own words, briefly describe what is modelled in a Sequence Diagram, and how Sequence Diagrams can be useful in systems analysis and design (100 words approx.).

b) Draw a Sequence Diagram for the use case in your diagram that corresponds most closely to the use case ‘Record New Tour’. This should include all control, boundary and entity objects involved in the scenario and the sequence of interactions that take place in order to meet the system requirements. Your diagram should be drawn using the Enterprise Architect software, and copied and inserted as a picture into your document.

c) Write a brief summary of the decisions made whilst drawing the diagram, and your reasons for making those (150 words approx.).

Part 3. Evaluation

Enterprise Architect is a CASE tool. In your own words and using examples, briefly describe what a CASE tool offers during analysis of the World-Wide Tours scenario, and what tasks the CASE tool supports. Give your own evaluation of how the role of an analyst/designer is supported by a CASE tool. Discuss how UML modelling supports the analyst/designer (750 words approx.).