FIT2001 Assignment 2- Requirements Modelling & Documentation Solution

Title: Requirements Modelling & Documentation

Assignment outline:
You have been given the task of gathering and documenting the requirements for a new information system for Secondo Store.

Assignment 2 – Requirements Modelling &
Documentation
• Story Mapping Workshop & Draft User Story Map & User Stories


• Final User Story Map & User Stories • Final Report




Value:
Assignment 2 is worth 25% of the final mark.

Aims:
This assignment will give you the opportunity to practice your data gathering, analytical, modelling, documentation and communication skills. Specifically, it will help you:
● Identify and confirm user requirements for a system accurately using data gathering techniques
● Develop your modelling/documentation skills to describe user requirements using user story maps, user stories, use case diagrams and activity diagrams
● Identify and describe data requirements for a system accurately and completely using domain modelling


Assessment criteria:
A detailed marking scheme is available in the Assignments section on Moodle. We highly recommend reviewing the marking scheme before commencing the assignment.


Assignment help:
NOTE: Staff will make every attempt to answer questions promptly – NOT necessarily immediately.

Assignment planning and management:
Assignment planning and management must be done using the Trello Kanban project management tool. Failure to actively use Trello will result in a reduction in your Team Assignment Project Management mark.

Extensions:

Submission process:
● The file name of the submission should follow this format:
• FIT2001_Assignment2_ Team[yourTeamID].pdf
• e.g. FIT2001_Assignment2_Team99.pdf
● All team members are responsible for the final submission, and therefore every team member should review the final version, prior to its submission.
● Each team member must accept the digital coversheet on Moodle. Failure to do so will result in your assignment not being submitted correctly, and thus not being marked.
● Ideally, a single file (PDF) should contain the entire submission, if there is a need for multiple files, all files must be in pdf format.
To submit the assignment ONLY DONE BY ONE TEAM MEMBER
• Click on 'Assignment 2 - Requirements Modelling & Documentation Information'
• To submit a pdf copy of the assignment - click on 'Add submission'
• Click on 'Submit Assignment'
• When at the digital coversheet 'Confirm Submission' statement
• Tick the 'I accept student statement' box, Click on 'Continue'
To confirm submission - MUST BE DONE BY ALL OTHER TEAM MEMBERS, otherwise
the assignment submission will not be finalised
• Click on 'Assignment 2 - Requirements Modelling & Documentation Information’
• Click on 'Submit Assignment'
• When at the digital coversheet 'Confirm Submission' statement
• Tick the 'I accept student statement' box, Click on 'Continue'
Once all team members have been through this process the assignment is deemed to have been submitted.
DETAILED ASSIGNMENT REQUIREMENTS

This assignment will help you understand, model and document the business requirements of the system desired by Secondo Store.
Use the ‘System Detailed Description’, the associated sample files/forms (See Assignment 2 section of FIT2001 Moodle site), and the feedback you receive during the User Story Mapping Workshop to complete the following tasks.


USER STORY MAPPING (40%)
Software requirements: Please ensure that you have signed up for MIRO using your Monash email address. You will be invited to a Team and a MIRO Board for your story mapping activity labelled 2021OCT_TTeamNumber_A2_StoryMap (e.g. 2021OCT_T99_A2_StoryMap).

Story mapping help: Please review the Story Mapping Example Video in Week 5 – Workshop 5.

The User Story Mapping section of the assignment is as follows:

• Story Mapping Workshop (24%) o Develop a DRAFT User Story Map and detailed User Stories using the detailed description of the system and sample files/forms. This User Story Map should include:
 ALL Journeys for the Secondo system
 ALL Epics for all the User Journeys you have identified
 For the following 2 Journeys – ALL the high level User Stories (or features) and complete User Stories (including Acceptance Criteria):
- Process new stock
- Return unsold stock
o Your DRAFT User Story Map and detailed User Stories should be as complete as you can possibly make it, given the information you have BEFORE you attend your Story Mapping Workshop with your client.
Use the MIRO Board labelled 2021OCT_TTeamNumber_A2_StoryMap to document your story map and user stories
o Conduct a Story Mapping Workshop (approx. 30 minutes) with your client to review and confirm your DRAFT User Story Map and User Stories
Story Mapping Workshop o NOTE: The Story Mapping Workshop must be conducted by Week 7, to give you enough time to complete all the assignment tasks using the information gathered during the workshop

• Finalise User Story Map (16%) o Finalise your User Story Map and include all your detailed User Stories for the specified 2 User Journeys (Process new stock and Return unsold stock), using the system detailed description, sample files/forms, and feedback from the workshop.

Continue working on the same MIRO Board labelled
2021OCT_TTeamNumber_A2_StoryMap to finalise your story map and user stories.
SYSTEM OVERVIEW (4%)
Write a System Overview to provide a brief overview of the business, the background and rationale for the project and the system capabilities and benefits. It is made up of the following sections:
• Project description
This section will provide some background about the client and a brief history of the circumstances leading up to the project. It should state the reasons why the client wants the system built or modified. This should be stated in a way that makes clear the nature of the information needs and/or problems that the system is to address.
• System capabilities
This section briefly describes the main functional and non-functional requirements of the future NEW system that you expect to provide to the client.
• Business benefits
This section lists the primary benefits or outcomes that the project is intended to achieve. These include the direct and indirect benefits.


ACTIVITY DIAGRAM (15%)
Using all the information gathered from Secondo Store, create an Activity diagram for the following function for the NEW system functionality:
• Markdown stock
This activity diagram should include all functionality for the markdown of stock items. It should include the markdown process for the 8 weeks that items do not sell.
NOTE: We recommend the use of Lucidchart or Diagrams.net (free) to draw your Activity Diagram.


USE CASE DIAGRAM (15%)
Create the User Case diagram for the NEW ‘Secondo’ system functionality. The model should include all relevant actors, show the relationships between actors and use cases, and any relationships between use cases.
NOTE 1: You are not required to complete the Use Case descriptions.
NOTE 2: We recommend the use of Lucidchart or Diagrams.net (free) to draw your Use Case Diagram.



DOMAIN MODEL CLASS DIAGRAM (22%)
Create the Domain model class diagram for the NEW ‘Secondo’ system. The model should include all relevant domain classes, show their attributes, relationships and relationship multiplicities.

NOTE: We recommend the use of Lucidchart or Diagrams.net (free) to draw your Class Diagram.


REPORT PRESENTATION AND TEAM ASSIGNMENT PROJECT MANAGEMENT (4%)
Please refer to the Faculty Style Guide for assistance with Report Writing:
https://www.monash.edu/it/current-students/resources-and-support/style-guide/writing-a-report

For the Team Assignment Project Management, please refer to the section “Assignment planning and management:” on page 2 of this document.

ASSIGNMENT DELIVERABLES
Assignment 2 will be submitted as 3 separate deliverables:
1. DRAFT User Story Map including all detailed user stories (user stories + acceptance criteria) via MIRO at the Story Mapping Workshop.


Please refer to Monash Research Learning Online for resources to help with planning
presenting your Assignment - https://www.monash.edu/rlo/home
It should include the following assignment sections, including any assumptions made for each section:
• System Overview
• Activity Diagram
• Use Case Diagram (not Use Case Descriptions)
• Domain Model Class Diagram

4. Team Assignment Project Management Board via Trello
ASSIGNMENT 2 SELF & PEER ASSESSMENT
IMPORTANT – If you have given a team member a lower rating than your team, YOU MUST provide the reasons for the lower score.