Requirement Elicitation (REN) Plan for Application Design 

It is the process of finding and recognizing the needs of a system from users, customers, and
all stakeholders. This process is also known as requirement gathering. Inayat et al. (2018)
also stated that the need for the recognition of representatives is required in terms of
understanding customer’s perspectives.
Before necessities can be recognized, examined, or demonstrated they should be assembled
through the elicitation rehearses. elicitation processes commonly used are stakeholder
interviews or meetings. The requirements elicitation process is where one can never be sure
about every piece of requirements from the customers and users by just investigating them
what to do or not to do. Requirements elicitation processes include questionnaires,
interviews, user observation, brainstorming workshops. Darwish, Mohamed & Abdelghany
(2016) mentioned that the success of the RE depends on the implementation of the
techniques in terms of interviews, observation as well as brainstorming.

REN Process
The requirements elicitation process may appear simple however some issues can arise
which complicate this process.
In 1992, Christel and Kang have identified a few problems indicating the challenges for the
elicitation process. 
1. Problem of scope
2. Problem of understanding
3. The problem of volatility and some other
 
 
Minimum Viable Product (MVP)

The base practical product is a variation of another application that an anybody uses to
gather the approved figuring out to maximum, about the customers with minimum of effort.
A Minimum practical Product is an aspect of a key cycle made toward assembling and selling
items to clients. It is an iterative cycle of presentation, idea generation, analysis,
prototyping, and learning and information assortment.
Steve Blank (2010) typically defines a minimum viable product as a set of minimum
features.  

 
Purpose of MVP

· Its purpose is to test an application or product with minimal resources.

· It should ignite and expedite new learning
· Squandered engineering hours should be reduced
· Product delivery to customers must consume minimum time
· Create foundation for other useful product.
· Establishing creator's abilities in crafting and designing the required product.
· Brand creation and brand awareness to be done very quickly

Key elements of MVP 

An MVP must include these key components for quality production:

· Functionality – It is the arrangement of highlights which must convey an unmistakable

incentive to the client,
· Design – It is that the plan of the Minimum Viable Product must be, up to the most
noteworthy industrial standards.
- Reliability – in this creation quality standard are to be accomplished by proceeds and
thorough testing.
- Usability – It is that the MVP must be easy to understand, use and should be intuitive.

Complementary Approaches in the Requirement Elicitation (REN) Process

Alexander and Beus-Dukic (2009) introduced a few alternative approaches for

software/system requirement –

· Identify stakeholders 
· Modelling context
· Modelling goals
· Discover qualities and constraints
· Modelling assumptions
· Writing definitions of terms
· Analysing measurements 

Justification of Choice

● The company will implement a minimum viable product technique

● This will facilitate in taking new ideas and implement it a development of a unique
application.
● It will also apply the process of Requirement elicitation.
● Proper analysis will enhance the knowledge of the working engineers (Andersson et
al. 2016)
The respective company will implement two tools such as minimum viable product
and requirement analysis and elicitation for the development of the respective application.
With the aid of MVP, they can develop processes that can be accumulated from customers.
On the other hand, the elicitation process can facilitate the management in terms of
evaluating, documentation and implementing existing literary sources for the development
of the application.
Conclusion

To conclude, this report highlighted in detail the concept of Requirement Engineering, in

which the importance of RE and steps involved in the RE are discussed. The major aim of
this case study is to find out the importance of requirement engineering for any
organization before starting to build an application or any project planning and execution. It
is an essential tool for any company/organization to understand the requirements of the
system. In this report, a detailed discussion is done on the requirement elicitation process,
minimum viability requirement, and its validation. Followed by requirements like business
software requirements, functional software requirements, and non- functional software
requirements for XYZ Pty Ltd.  

References:

1. Lock, D. (2013). Project management (10th ed.). Gower. INSERT-MISSING-URL.

2. Lyee-W02 (2002: Paris, France), Fujita, H., & Johannesson, P. (2002). New trends in software
methodologies, tools, and techniques: proceedings of lyee-w02 (Ser. Frontiers in artificial
intelligence and applications, v. 84). IOS Press/Ohmsha. INSERT-MISSING-URL.
3. Kouzis-Loukas, D. (2016). Learning scrapy: learn the art of efficient web scraping and
crawling with python (Ser. Community experience distilled). Packt Publishing. INSERT-
MISSING-URL.
4. Ungerer, M., Jock, R. J., & Terblanche, N. H. D. (2019). Creating and maintaining a
commercially viable executive coaching practice in south Africa. The Southern African
Journal of Entrepreneurship and Small Business Management, 11(1), 1–10.
https://doi.org/10.4102/sajesbm.v11i1.192
5. Bäck, A., & Jaring, P. (2017). Social media in accelerating mobile apps. International Journal
of E-Business Research (Ijebr), 13(2), 1–13. https://doi.org/10.4018/IJEBR.2017040101
6. Gilb, T., & Brodie, L. (2005). Competitive engineering: a handbook for systems engineering,
requirements engineering, and software engineering using planguage. Butterworth-
Heinemann. INSERT-MISSING-URL.