Assignment 2: Advanced Requirements Modeling and Specification

Due Date

22nd of October, Friday (Teaching week 12 – 12.00 noon Perth local time online though Blackboard)

This assignment counts for 30% of the final marks.

Important note

1. This assignment is to be carried out individually (basically, you need to work alone not in

groups!) Each student will submit one report through blackboard.

2. Each student is required to continue to work on the selected problem statement from Assignment

Objective

Assignments’ 1 and 2 are closely related to each other. The two assignments together form a complete software requirements specification. In these two assignments, you will analyse the requirements and write a requirements specification for a software development project of your own choice from the problem statements provided. Assignment 1 expected you to model the problem using a mixture of modeling techniques.

Assignment 2 expects you to further use advanced modeling techniques like UML class diagram, goal modeling and i* models (both SD and SR Diagrams) and then produce a software requirements specification (SRS) document. The objective of this assignment is to give you practice in organizing the results of a requirements analysis and modeling process into a formal specification document.

Doing the Assignment

This assignment has following steps. They are listed as below:

• Further, develop models of key aspects of the Your models must include:
  1. The structure of application domain information to be represented by the proposed system (using UML Class Diagram). Include details on generalizations, associations, cardinality and role names where they
  2. Model stakeholder goals using “goal modeling” and capture the organisational context, dependencies between various actors and internal intentional rationale using the i* models (both SD and SR Diagrams).

Note: Drawings must be clear and legible. You can use open source modeling tools of your choice like ArgoUML, Star UML, PlantUML, OpenOME etc to draw your models – Strictly, do not draw models/diagrams by hand.

• Further extend and refine identified requirements (you have already identified subset in Assignment 1), including all functional and non-functional requirements for the new system, the data that the system will need to manage, interfaces to other systems, and interfaces for different classes of
• Trace these requirements to the models you produced in Assignments’ 1 and Requirements must be traceable to the models. Note: Just reference them.
• Write a formal requirements specification that documents these requirements (using the IEEE standard or Karl E. Wiegers SRS document). IEEE & Karl E. Wiegers templates are provided on the unit webpage as ready reference).
• Create wireframe/mockup diagrams that illustrate what the requirement or functionality may look like when fulfilled. These must be done using appropriate diagram modeling tools such as draw.io, com or any other suitable tool you have come across.
• Clearly list any assumptions you might make in completing this assignment at appropriate

Written requirements of the assignment:

You should hand in a report (in .pdf format and contain all relevant graphics) of your work, not exceeding two (2) pages (not counting references, appendices, figures or tables etc). The report itself is intended just to give an overview of what you did, and the rationale for any choices you made (e.g. about what to model and how to model it; how to organize the specification; the requirements elicitation techniques used to further refine the requirements, discuss any interesting lessons learned during the elicitation and modeling process etc). Your appendices (see below) are likely to be considerably longer than this report.

The report should include the following:

• A methodology section that describes your analysis process, including steps you took for further requirements identification, elicitation and documentation as
• A discussion session that briefly describes any difficulties you encountered, limitations on your analysis, and interesting lessons learned during the analysis and specification process,
• A conclusion that summarizes the key points in the report, including a brief assessment of what you have achieved
• An appendix containing all of your models (UML Class Diagram, Goal Models and the i* Models). Make sure you provide enough commentary with the models for the reader to understand what each model is of, and how to understand
• Second appendix containing a detailed requirements specification (SRS). Use the IEEE standard or Karl Wiegers SRS document to give you a structure for this document.
• Third appendix containing wireframe/mockup
• Any further appendices you feel are relevant

Assignments will be judged on the basis of visual appearance, grammatical correctness and quality of writing, as well as their contents. Please make sure that the text of your report is well-

structured, using paragraphs, full sentences, and other features of a well-written presentation. The report must not consist of itemized lists of points. Text font size should be either 10 or 12 points.