Reference no: EM132551700 , Length: word count:2000

MIS604 Requirement Engineering - Torrens University

Task Instructions:

You, as a group, should first read and understand the following case before proceeding to answer the questions in Assessment Tasks section. Note that every piece of information provided in the following case serves a purpose.

The case:

XYZ Pty Ltd is an established company (the 'Company') that has been selling hardware tools and paints for the last 30 years using traditional "brick and mortar" business model, based on tradesmen coming to the store and selecting the goods they want to buy.

They are currently seeking to expand their business to include on-line catalogue with ability to be browsed, select items to be put in the shopping bag and to make an on-line payment with goods either being collected in the store, or shipped via a courier.

The objectives are to increase the sales, to make it more convenient (time saving) for the tradies and also to allow non-trade people to shop on-line.

The Company CEO provided the following very high-level and rough ideas for possible developers:

For customers, they can browse the catalogue, explore particular item's details, add an item to shopping bag, change the number of items, add and delete items to/from shopping bag, select pick-up in the store or delivery to the nominated address and make an online payment or to send an inquiry to the store. Store personnel can respond to the inquiries and contact the customer via email or phone based on the details provided by the customer.

Customers will also have the opportunity to rate and review goods purchased and service provided by the store. Store personnel will be able to respond to the customers' review.

The Company wants to implement the first Minimum Viable Product (MVP) in the next six months and have secured an investment for this. Further investment to finalize the full version in the following six months will be provided on the basis of satisfactory assessment of the MVP implementation.

XYZ has engaged you (i.e. a group of you) as the requirements analyst in this project.

Assessment tasks

Part A.

As a group write a report addressing the following tasks:

Part 1. Establish your credentials in giving requirements engineering advice to XYZ. Note that you are not a student in this case. You are required to undertake some research and identify qualifications, certificates or experiences related to requirements engineering that will add to your credentials.

Part 2. Advise XYZ Pty Ltd of the importance of requirements engineering, and the implications of not having in place proper requirement engineering practices in the project.

Part 3. Advise XYZ Pty Ltd of the key processes in requirements engineering in relation to the project. Provide (a) a description of each requirements engineering process; (b) the objectives, the main activities, key stakeholders and outputs of each process.

Part 4. Advise XYZ Pty Ltd of a plan for requirement elicitation for the proposed app. Given the nature of this app, what are the requirements elicitation activities you would perform? Justify your choices. Provide detailed descriptions of at least two requirements elicitation techniques. For example, if an interview is to be conducted, you will need to provide:
• who are the interviewees;
• who are the interviewers;
• the interview questions;

5. Based on the case description and use common sense, for the proposed app, list
a. At least two (2) business requirements;
b. At least five (5) functional requirements;
c. At least three (3) non-functional requirements;

The requirements must satisfy the criteria of a "good" requirement discussed in Module 2.1.
Your report should include the following

1. Title page: Subject code and name, assessment number, report title, assessment due date, word count (actual), student names, student IDs, Torrens email address, campus learning facilitator, and Subject coordinator. Not included in the word count.

2. Executive summary: should include the purpose of the report, the problem including key issues considered and how they were investigated, and your findings. This part should be approximately three quarters of an A4 page but must not be longer than one (1) A4 page. Not included in the word count.

3. Table of Contents (ToC): should list the report topics using decimal notation. Need to include the main headings and subheadings with corresponding page numbers, using a format that makes the hierarchy of topics clear. Because you are including a ToC the report pages should be numbered in the footer as follows: title page has no page number; and main text to have Arabic numerals commencing at 1. Create the ToC using MS Word's ToC auto-generator rather than manually typing out the ToC.

4. Introduction: provide a brief description of the company as given in the case scenario including any assumptions, a concise overview of the problem you have been asked to research, the main aims/purpose of the report, the objectives to be achieved by writing the report (include the tasks outlined in the case study) and how you investigated the problem. Provide an outline of the sections of the report. Should be approximately 200 words.

5. Body of the report (use appropriate headings in the body of the report.): Ensure that you address the tasks listed in the case study scenario. Do NOT use generic words such as ‘Body, Body of the Report, Tasks' as section headings. Create meaningful headings and subheadings that reflect the topic and content of your report. Should be approximately 1600 words.

6. Conclusion: restate the purpose of the report and key issues investigated and the related findings based on your research and analysis. Explain the significance of your findings for addressing the problem stated in the case scenario and any limitations. State how your report has achieved its objectives and any future work to be considered. Should be approximately 200 words.

7. Reference list. Not included in the word count.

8. Appendices if necessary. Not included in the word count.

Attachment:- Requirement Engineering.rar