Reference no: EM132553845 , Length: 20 Pages

SAM 11486 Systems Analysis and Modelling Assignment - University of Canberra, Australia

The chosen case study is Case - EasyTicket.

Assignment requirements - All of the requirements below relate to your chosen case study. It is expected that you perform additional research and investigation, in addition to the information provided in the case study, to inform your reasoning and analysis. Explanation, justification, and evidence is expected to support report contents wherever relevant.

1. Dataflow diagram

Create a top-level DFD that describes the core processes of the system. Depending on your decomposition and the complexity of the case study, one or more lower level DFDs may also be required to further explain key processes of the system.

2. Data dictionary

Create a partial data dictionary that describes all key data flows present in the dataflow diagram. Note that a complete data dictionary is not expected, however it is expected that the data dictionary includes all important information data flows and explains any that need additional clarification or decomposition.

3. Process specifications

Create one or more process specifications that describe the most important and complex processes of the system. Note that process specifications are not expected for every single process, however it is expected that process specifications are included for all processes that are important and complex from the business perspective and clearly explain how these business processes work.

4. Use case diagram

Create a use case diagram for the system. This diagram may be broken down into sub-diagrams in order to aid presentation and readability.

5. Use case description, activity diagram, and sequence diagram

Create at least one use case description, at least one activity diagram, and at least one sequence diagram to describe important and complex use cases in the system. Each use case description, activity diagram, and sequence diagram will cover a different use case from the system. Note that further description or diagrams are not expected for every single use case, however it is expected that a use case description, activity diagram, or sequence diagram is included for all use cases that are important and complex from the business perspective, and at least one of each of the different ways of describing a use case are used.

Make sure that the choice between use case description, activity diagram, and sequence diagram is appropriate for each use case and briefly explained and justified.

6. Class Diagram

Create a class diagram for the system.

7. State Machine Diagrams

Create a state machine diagram that describes the behaviour of an important class in the system.

8. Assumptions

List and briefly explain all assumptions that you have made regarding the case study for your assignment.

9. References

List all references used in your report. Do not list any references that are not directly referred to in your report.

The references should be presented in Harvard Style. See the UC Referencing Guide for more information.

Attachment:- Systems Analysis and Modelling Assignment Files.rar