Requirement Engineering MIS604

Subject Code – MIS604
Subject Name – Requirement Engineering
University Name – Torrens University, Australia

What is Requirement Engineering MIS604? 

This Requirement Engineering MIS604 is a course that focuses on the concept of defining, documenting, and maintaining the requirements for changing large, and complex software systems.

It will help you to understand that the process in Requirement Engineering is not sequential, it is an iterative process in which activities are iterative.

It is a four-step process including elicitation, specification, verification, and management. The purpose of requirement engineering is to introduce the systems engineering standards which include the RE process from a standard perspective, show the relationship between system and software requirement engineering, and development, and for the different views of the RE process.

Requirements Engineering MIS604 is a course which is taught in two degrees of Torrens University one is Master of Business Information Systems another one is Master of Engineering Management

A Master of Business Information Systems degree will connect you with the concept of Requirements Engineering MIS604 course. This helps developers to understand requirement management and how it supports system engineering and software engineering life cycles. On the other hand, the Master of Engineering Management course equips students with specialized knowledge and practical management. 

Learning Outcomes

• Understand the methods for eliciting, analyzing, and documenting.
• Learn to maintain the requirements in an organizational context.
• Demonstrate the key principles of requirements management
• Be able to communicate to stakeholders in order to solve problems.
• Evaluate Organizational requirements to maximize  effectiveness
• Understand how to promote sustainable business practices.

What are the Types of Software Requirements?

A software requirement can be categorized into three parts: functional requirements,  non-functional requirements, and domain requirements respectively.

Functional Requirements

The fictional requirements are the statements that are used to define the system’s behavior. They Are used to describe what a software system must do or not do. (For instance, a doctor is able to retrieve the information of his patients in a hospital management system.)

Non-Functional Requirement 

The requirements that are related to software security, maintainability, reliability, scalability, performance, re usability, and flexibility

Domain Requirement  

The characteristics of a particular domain project. For example, maintaining the records related to school, college, and office. Like maintaining the record of an employee in the office. 

Why is Requirement Engineering Important? 

• They deliver value to your product development process.
• They establish the scope of It helps in defining the scope of a software project
• They help to schedule which software will deliver to the customer 
• They show what elements and functions are essential for the project

Why Choose Our Website’s Services? 

The services our professionals are providing you are excellent. Whenever you need a top-writing assignment we are always there for you. Our customer is our first priority, and that is why we are determined to make a trustworthy bond with our clients. We believe in creating useful, knowledgeable, and concise assignments for our clients.

If you want to enhance your grade, reduce the burden of assignments and save your time and focus on your studies by assigning the assignments to our experts. It is a platform where you can hire an expert to complete your assignment so don’t hesitate to get our best writing services to help.

Task-1 

You are required to produce an individual report of 1500 words detailing a requirements elicitation plan for the case organization.

The report should contain the following:

1. A Stakeholder Engagement Plan detailing should include a stakeholder list, area of influence and power mapped on a power grid, and a definition of the stakeholder’s power and interest.
2. An Elicitation Activity Plan detailing includes four elicitation methods, an explanation of each method, a tailor and customer example of information gathering tool, and Which stakeholders will be engaged for the elicitation activity and why?

Task Instruction 

1. Read the attached MIS604 Assessment Case Study.

2 Write 1500 words requirements elicitation plan for the case organization

Task 2  

This Assessment requires you to write a group report of 2500 words. Write a requirements document and lifecycle management report in response to a case study. Focus on the following two areas:

1. a) Requirements Documentation
2. b) Requirements Lifecycle Management

Task Instructions

1. Team Formation 

• You are required to form teams of 4-5 members and the deadline for team registration is 11:45 pm AEST Friday
• To register your team, you are required to send your Learning Facilitator an email with “[MIS604] Team Registration” in the subject line.

2. Please read MIS604_Assessment_Case Study.
3. Write a 2500 words requirements document and lifecycle management group report.

4. Structure of the Group Report

• 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)
• The body of the report (2200-2300 words) 

5. Report Format and Layout

The report should use font Arial or Calibri 11 point, and should be line spaced at 1.5 for ease of reading and page numbers on the bottom of each page.

6. Peer evaluation

• Each student in the team will evaluate the other members’ contributions using a participation score matrix (see Group Participation Score Matrix attached) Individually, each team member will assign a “Group participation score” for each member of the group using the score matrix.

7. You are strongly advised to read the rubric which is an evaluation guide with criteria for grading the assignment. This will give them a clear picture of what a successful report looks like.

Task 3

Analysis. In this assessment you are required to produce an individual report of 2000 words (+/-10%) detailing the following:

1. A Product Roadmap and a Product Backlog of coarse granularity including Epics and user stories
2. A Persona who typifies the future system end-user
3. Decomposition of an Epic in user stories for the first release
4. Story Mapping – ordering user stories according to priority and sophistication
5. Minimum Viable Product definition for the first release
6. Story elaboration of the stories for MVP to ensure that the User Story is clear
7. Well-considered acceptance criteria for the stories to ensure that the ‘definition of done’ is clear to all stakeholders.

8. A paragraph detailing the similarities and differences between traditional predictive requirements analysis and management and Agile requirements analysis and management.

Task Instruction 

1. Please read the attached MIS604_Assessment_Case Study.
2. Write a 2000 words Agile Requirements Analysis & Management Report as a response to the case study provided.

3. Review your subject notes to establish the relevant area of investigation that applies to the case. Re-read any relevant readings for Modules 1 and 2 for this subject.

4. 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.
5. Please structure the report as follows:

• 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, the body of the report, and the conclusion

6. The report should use font Arial or Calibri 11 point, should be line spaced at 1.5 for ease of reading and page numbers on the bottom of each page. If diagrams or tables are used, due attention should be given to pagination to avoid loss of meaning and continuity by unnecessarily splitting information over two pages. Diagrams must carry the appropriate captioning.

7. You are strongly advised to read the rubric which is an evaluation guide with criteria for grading the assignment. This will give you a clear picture of what a successful report looks like.