ITECH 2002-System Requirements, Use Cases and Domain and Use Case Modelling

Overview
The purpose of the assignment is to provide students with the opportunity to apply knowledge and skills developed during the semester with particular reference to:
1. How to model a system using familiar tools;
2. How to document functional requirements using techniques widely used in the IT industry including use case texts/descriptions, user stories, use case diagrams and class diagrams; and
3. How different stakeholders contribute to the definition of requirements.

Students complete the assignment in groups of three.
As suggested in your text, Systems Analysis and Design in a Changing World (Satzinger, Jackson & Burd, 2016), you live in an age of ubiquitous computing. As IT students you should understand how to implement best practices for the analysis and design of information systems. This Course and this assignment in particular, concentrates on systems analysis, the activities of systems development that enable a person to understand and specify what a system is supposed to accomplish (Satzinger, Jackson & Burd 2016).

In this assignment you will work in a group to analyze and specify some of the requirements of a work management system for [email protected]@g3rs Pty. Ltd. Your analysis and specification will use components of the Unified Modelling Language (UML) and these need to be presented according to the notation specified in your text. You are expected to read the case study provided and determine and describe a sufficient number of user stories and use cases and provide a sufficient number of use case and class diagrams to describe the system. You are also expected to provide some overarching documentation such as pictorial mockup of the system, stakeholder chart, organization chart and vision and mission statements for the company and system. The case study is deliberately complex and detailed so that you can understand and experience some of the complexities and difficulties actually encountered in analysis.

Learning Outcomes Assessed
The following course learning outcomes are assessed by completing this assessment:

K1 Explain how models are used to assist in analysing and modifying existing business systems;
K2 Define various roles involved in the processes of system analysis;
K3 Describe techniques used to gather required information for system analysis;
K4 Explain the various stages of the system development life cycle;
S1 Identify appropriate models for given scenarios;
S2 Perform Object Oriented Analysis to construct various object models used to communicate the scope and requirements of the project.
A1 Write integrated reports, using appropriate models, providing detailed analysis of given textual scenarios

Assessable Tasks/Requirements
This assignment has a group work and individual work components. We require only one report for the group and separate report submissions for individual work. As a group you are required to understand the ITGWMS requirements by analyzing the information provided, identify factors about the organization that are useful, model them and also break the ITGWMS into sub-systems. Each student in the group needs to select one identified sub-system (no two students in the same group may choose the same sub-system) and then model the requirements through the use of user stories, use case descriptions, use case diagrams and domain model diagrams. Students are to consolidate this information as a group and provide a group report and also submit their individual findings on their selected sub-system in a separate report. The following information is required in the group report:

• Pictorial Model of the Organization (see Fig 2-1 of text for example)
• High Level Organizational Chart (see Fig 2-5 of text for example)
• Stakeholder Chart (see Fig 2-4 of text for example)
• Organization (not system) Vision Statement
• Organization Mission Statement
• System Vision Statement
• Consolidated Domain Model Class Diagram (see chapter 4 of text for Domain Modelling) The following work is to be completed by each student and submitted in an individual report:
• Two User Stories complete with statement and acceptance criteria
• A User Goal Table (see Fig 3-2 of text) for the two User Stories identified
• Eight Use Case Descriptions (see Fig 3-9 of text for examples) (Only two report types Use cases are permitted and you cannot have all your Use Cases triggered by only one event type)
• A Use Case Diagram of the ten use cases identified (see Fig 3-11 to 3-15 of your text for examples)
• A Domain Model Class Diagram for the selected sub-system to support the identified use cases

You may use drawing or modelling packages such as DrawIO, LucidChart or Enterprise Architect to create your model diagram but you must conform to the standards of the text.

Order Now