Requirement Engineering Report - Software Engineering, Module 2

This report examines the critical role of requirement engineering in software development, focusing on the ABC Pty Ltd case study. It explores the importance of requirement engineering, outlining the processes involved, such as requirement elicitation, analysis, and validation. The report discusses how effective requirement engineering can lead to successful software outcomes, while also addressing the potential pitfalls of poor requirement engineering. The analysis includes how requirement engineering impacts software maintenance, control, and automation, and how it affects the overall development cost. The case study is utilized to explain how the requirement engineering techniques and strategies can be applied to the company, providing a comprehensive understanding of the subject matter. The report aims to provide a comprehensive understanding of the subject matter, highlighting the benefits of well-managed requirements and the negative consequences of inadequate planning.

Requirement Engineering
The Engineering process, which defines, maintains and documents the
requirements of engineering, is known as requirement engineering.
Requirement engineering has a role in systems and software engineering.
Requirement engineering will aid ABC to understand the requirement of their
users more effectively. Poor requirement engineering can be problematic for
the management therefore they should hire proper engineer based on their
qualification and certificates.

Requirement Engineering
Requirement engineering involves four process that includes
requirement elicitation, requirement analysis, requirement specification
and requirement validation.
Most of the project fails because of poor requirement management. By
using proper engineering methods, the software can work efficiently and
providing proper user experiences to all of its users

Requirement Engineering
 Requirement elicitation is the most important part of requirement
engineering where different data are collected to fulfil the
requirement of the software.
 Brainstorming and Facilitated Application Specification Technique
(FAST) are the primary requirement elicitation techniques that should
be followed by ABC in this software.

Requirement Engineering
 Requirement analysis and validation should be done after elicitation
which identifies the risks associated with each requirement.
Requirement validation certifies the SRS document in acceptable
format assisting the requirement process to identify the errors of the
software and fixes it.

Requirement Engineering
 Requirement engineering will aid ABC to understand and identify the
problems of the software. This process aid the software to work
effectively and correctly. Requirement engineering also lowers the
development cost of the software aiding in the software development.

Requirement Engineering
 Poor requirement engineering will negatively affect the software.
Without proper requirement engineering, the maintenance, control
and automation of the software get difficult. Poor requirement
engineering can lead to inadequate tool support for the software.