MIS604 – REQUIREMENT ENGINEERING

Student Gigz Pty Ltd is a recently formed student start-up company in a university accelerator program in Adelaide. Their business focuses on ensuring that organisations can call on students, in short notice, to fulfil their short-term vacancies/ needs for specialised skills. Student Gigz Pty Ltd is building a web and mobile application combination. This application should allow organisations that require short term assistance to register for the service online to source students with the appropriate skills. The company will be funded by a pro rata commission charged per hours worked by each student.

The organisations will also be able to review student profiles and send targeted messages to students with the experiences in a specific area.
The mobile application is designed as the primary student interface. Students will be able to create a profile where they will be able to select their skills from a pre-existing list as well as the locations where they are able to work. Typical jobs might include project support, accounting support, wireframing, high fidelity html prototyping and marketing.

Contact can be made post-matching for students to find out more about the job or the organisation to find out more about the student’s availability. Once the job is completed, payment can be made securely through the app. The organisation will also be able to rate and review the student. Your company has been engaged by Student Gigz (Pty Ltd) to help them with the requirements analysis for this project.

This Assessment requires you to respond to a case study. For this assessment, you are required to produce an individual report of 1500 words detailing requirements elicitation plans for the case organisation.

Business Analysts work with organisations to improve organisational processes and systems. One of the most important parts of a Business Analysts job is to elicit requirements from stakeholders so that there is a clear understanding of what will be required from the new system.

This requires a Business Analyst to understand who their stakeholders are, how to engage with them and which elicitation methods to use. This assessment aims to develop your knowledge and skills in this area and to lay down the foundation of knowledge for your future professional practice.

Write a 1500 words requirements elicitation plan for the case organisation. Write a 1500 words (+/-10%) requirements elicitation plan for the case organisation.
Review your subject notes to establish the relevant area of investigation that applies to the case. Re- read any relevant readings for module 1 and 2 for this subject. Perform additional research and investigation and select five additional sources in the area of elicitation methods to add depth to your explanation of method selection.

Plan how you will structure your ideas for your report and write a report plan before you start writing.

Check Out: MGT501 – BUSINESS ENVIRONMENT

Title Page: A professional custom title page with the subject code and subject name, assignment title, student’s name, student number and lecturer’s name.

Introduction: An introduction (100-150 words) which will also serve as your statement of purpose for the report.

This means that you will tell the reader what you are going to cover in your report. You will need to inform the reader of:

• The key concepts you will be addressing,
• What the reader can expect to find in the body of the report

Body: The body of the report (1200-1300 words) will need to cover two specific areas:

• A Stakeholder Engagement Plan including:
   - Stakeholder list
   - A Power/Interest Grid
   - Definitions of each stakeholder’s power and interest
• An Elicitation Activity Plan:
   - Four elicitation methods
   - An explanation of each method and why it has been selected
   - A tailored and customised example of the information gathering tool you will use for each method
   - Which stakeholders will be engaged for the elicitation activity and why?

Conclusion: The conclusion (100-150 words) will summarise any findings or recommendations that the report puts forward regarding the concepts covered in the report.

This Assessment requires you as a group to write a requirements document and lifecycle management report in response to a case study. Write a report of 2500 words and focus on two topics:

a) Requirements Documentation
b) Requirements Lifecycle Management

You are required to form teams of 4-5 members and write a report of not more than 2500 words.

• The report does not require an executive summary or abstract.

• A professional custom title page with the subject code and subject name, assignment title, student’s name, student number and lecturer’s name

• An introduction (100-150 words) which will also serve as your statement of purpose for the report. This means that you will tell the reader what you are going to cover in your report. You will need to inform the reader of:

  -The key concepts you will be addressing,
  -What the reader can expect to find in the body of the report

• The body of the report (2200-2300 words) will need to cover two specific areas:
   • Requirements Documentation
      -Requirements/project scope
      -Two business goals (SMART) & objectives to be achieved
      -Map out a swim lane diagram of one key process which will be supported by the system
      -Two business requirements
      -Two actors within the system
      -Five functional requirements
      -Five non-functional requirements
   • Requirements Life Cycle Management
      - Explain the importance of managing the requirements lifecycle and implications of not managing this lifecycle.
      - Discus each stage of the Requirements Lifecycle: trace, maintain, prioritise, assess, and approve:
         • A description of each stage
         • The objectives of the process in each stage
         • The main activities of the process in each stage
         • Outputs of each stage
      - A Requirements Traceability Matrix to manage the requirements through each stage of the requirements lifecycle populated with the requirements identified in the first part of this assessment. You may use Excel for your Requirement Traceability Matrix.
  • The conclusion (100-150 words) will summarise any findings or recommendations that the report puts forward regarding the concepts covered in the report.

Agile has become a recognised software development approach which is both adaptive and iterative in nature. This has necessitated the development of new and differentiated requirements analysis and management skills, techniques, and capabilities. This assessment aims to assist you in developing well-rounded skills as a Business Analyst who uses a spectrum of tools and techniques. In doing so, you can draw irrespective of the approach your future employer may take to software development.

Write a 2000 words Agile Requirements Analysis & Management Report as a response to the case study provided. Perform additional research and investigation and select five additional sources in the area of elicitation methods to add depth to your explanation of method selection. Plan how you will structure your ideas for your report and write a report plan before you start writing.

A professional custom title page with the subject code and subject name, assignment title, student’s name, student number and lecturer’s name. An introduction (100-150 words) which will also serve as your statement of purpose for the report.

This means that you will tell the reader what you are going to cover in your report. You will need to inform the reader of:

    • Overview of the problem you’ve been asked to research.
    • The key concepts you will be addressing,
    • What the reader can expect to find in the body of the report

The body of the report (1700-1800 words) will need to cover the following areas:

    • A Product Roadmap and a Product Backlog of coarse granularity including Epics and user stories
    • A Persona who typifies the future system end user
    • Decomposition of an Epic in user stories for first release
    • Story Mapping – ordering user stories according priority and sophistication
    • Minimum Viable Product definition for first release
    • Story elaboration of the stories for MVP to ensure that the User Story is clear
    • Well considered acceptance criteria for the stories to ensure that ‘definition of done’ is clear to all stakeholders.
    • A paragraph detailing the similarities and differences between traditional predictive requirements analysis and management and Agile requirements analysis and management.

The conclusion (100-150 words) will summarise any findings or recommendations that the report puts forward regarding the concepts covered in the report.