Reflective Report on Requirement Engineering Practices (MIS604)

This reflective report examines requirement engineering practices in the context of academic, personal, and professional experiences. The author reflects on their understanding and application of requirement management, highlighting the importance of clear documentation, verification, and planning. The report details a personal experience of writing a research paper, illustrating how structured requirement management, including defining subparts and prioritizing tasks, improved the outcome. The author also discusses the challenges of interviewing a CEO and how effective requirement planning led to a successful outcome. The report concludes by drawing parallels between organizational management, software development, and personal life, emphasizing the need for effective requirement management to achieve desired results. The author emphasizes the importance of planning, integrating, and tracing requirements, as well as reporting fulfillments to stakeholders to ensure the vision and mission are met.

Requirement Engineering
Reflective Report

Requirement Engineering is a big category and out of it the area that is chosen for the analysis is
requirement management. It is important that a clear understanding of requirement management
is made before its application is traced in the professional or personal life.
When we are talking about requirement engineering we are talking about the process of
documentation, verification the needs that are going to arise or are there when a particular
expectation is fulfilled. This may relate to an event in personal life or it may also be applied
when trying to meet the demands of a customer. Its application is not specific to the situation.
This management concept can be applied in many situations as each event or an expectation is
brought to closure with the requirements getting fulfilled step by step.
Although what people do in their daily personal life is to meet the demand by trying to narrow
down to the necessary. But, when we are talking about an organizational situation or the
development of a product, for example, software, there are definite steps involved. When these
steps are followed, the whole process of requirement management is done with the system and
the result is as per the vision and mission of the organization or the institution that we are
associated with.
Some of the important steps that are involved here are planning for the requirement, integrating
the requirements, tracing the progress, change in the requirement. It also involves reporting the
fulfillments that is received by the stakeholder.
I had once tried to write a research paper for a platform that welcomes authors from different
areas of expertise to write about what they excel in. I am a software engineer and I decided to
write about a topic that roughly revolved around that topic.
The topic was easy when I decided to write but as more research was carried out there was a lot
area I discovered. Halfway, I thought this was a wrong decision but it was not easy to back out as
a lot of effort had already been put done.
Then I decided to have a clear list of the requirements and manage the whole project
accordingly. The requirements had been there in my mind by noting it down professionally
helped me come up with several subparts that would not have come had I kept it just in mind.
Documentation also helps in trying to understand if those portions were really necessary or there

can be an alternative to it. When I am talking about alterative, I am mainly talking about
developing the argument in order to support my claim in the research paper. It became quite
easy as each part was taken up one at a time and the whole process was simplified. The whole
process was as good as working on software when just like the first step is taken with a pen and
paper to jotting down what is required.
The main requirement in the research was that interviewing a CEO of an organization and
receive feedback on a particular topic of software development. This part of the research looked
easy but the CEO is usually busy and getting to interview for a research paper that was not
supported by a business school but an independent scholar was quite a deal.
What I did was made a list of all the small scale business that was there in the city and tried to
contact at least ten of them and the result was that one agreed for a full one-hour session. It was
quite fruitful and the researched paper gained a good angle that was very much appreciated by
the editors’ board that, in this case, we're like the stakeholders, having expectation from me. It
was on me how I had planned the requirement process and managed it so as to get the desired
result.
The way an organization is managed and software are developed is exactly the same way that
personal lives function. It is us who has to perform effective requirement management in order to
get the job done with utmost precision, fulfilling all the expectations.