System Analysis and Design with UML Modelling

The general intention is to design the required system through system analysis and design techniques using UML modelling.

Use the given case study to write a Business Requirements Statement for the new system.  Use the Unified Modelling Language (UML) to achieve the modelling.

Task1:  General report structure

a. Cover page and Table of Contents  

b. Report structure / neatness (introductions, professional presentation, report structure apply sections, referencing, font … etc.) 

Task 2: Business requirement identification   

 Document all the requirements for the system by studying the scenario and make required assumptions.

b. List all identified non-functional requirements ( including assumed ones) in a table /Matrix  (Templates available)

Task 3: Activity Diagram for whole assumed system (full system process modelling)

Produce an activity diagram for the whole required system including swim-lanes, objects and actors involved in the system operations. This activity diagram is being used as a process modelling to understand the whole operational processes within car parking system.

Task 4: Actor Glossary / UseCase Glossary

a.  Actor Glossary ( a List of actors[roles] related to the system )/Table ( templates to be used)

b. Use Case Glossary ( A list of all use cases for the system describing what this system is being used for ) /Table    ( templates to be used)  

Task 5: UseCase diagrams/ UseCase narratives

a. Use Case Model Diagram for the whole system including defined system boundaries.

AT least three boundaries are expected (sample of possible boundaries: Entry, payments, leaving, etc.)

b.  Use case narratives for major use cases within each chosen boundaries. ( at least two for each boundaries , minimum 6  narratives

Task 6: Produce state transition diagram for three selected objects within the designed system

  Select three most complicated objects within your system design. Explain the complexity of each object and draw three state transition diagram for selected objects. State transition diagram is to identify all state of an object (Class) by applying given events which will change the state of an object.

Task 7: Identifying software objects within Use Cases/ creating communication diagrams

a. Identify and sketch “Interface”, “controller “and “entity” objects for all major use cases you   identified in task 4 (this can be done in Ms World, as EA does not support this action directly, you draw the refined version of this as communication diagram).

You need to explain briefly how did you decide to draw each diagram and what was your logic behind decisions you made.   (Minimum 6 major use cases)

b.  Transfer all drawn use case objects /relations above to proper communication diagrams and identify /add all relevant messages between each objects (all messages must be named, numbered and include directions between each object).

Produce set of sequence diagram for all Uses cases that you produced narrative for in question 2, each diagram should have at least a paragraph explaining the sequence diagram you made   (  Chosen UseCases for drawing sequence diagram can be the same as the one were chosen for drawing communication diagram)                             12 marks

      Hint1: (you can get help from the narrative you produced in task 2)

Hint 2: (Sequence diagram is the transformation of communication diagram, having sequence timing in mind)

Task 9: Produce an analysis/design final class diagram

Produce full analysis/design class diagram for the part of systems that communication and sequence diagram was produced (Minimum 6 Diagrams).In these diagrams you should identify all the characteristics of an object class that will make it ready for a programmer to use this class diagram and enable them to code the system. They should include all correct connections based on prior analysis, class attributes and methods and to be indicated which one is public, private … and etc.