重庆理工大学毕业设计（论文）
文 献 翻 译
学 院 两江人工智能学院
班 级
学生姓名 学 号
译 文 要 求
1、译文内容必须与课题（或专业）内容相关，并需注明详细出处。
2、外文翻译译文不少于 2000 字；外文参考资料阅读量至少 3 篇（相当
于 10 万外文字符以上）。
3、译文原文（或复印件）应附在译文后备查。
译 文 评 阅
导师评语（应根据学校“译文要求”，对学生外文翻译的准确性、翻译
数量以及译文的文字表述情况等作具体的评价）
指导教师：
年 月 日
原文：
Effective Requirement Engineering Process Model in
Software Engineering
1. Introduction
Developing a software product requires different processes and stages. Requirement engineering is one of the
major phases that involves every stakeholder in the software product development [4]. Requirements in the literal
sense can be referred to as anything that is discovered in order to develop products or services. A system’s
requirement includes services and constraints of the operation [1]. In order to meet customers’ needs, a well
defined requirement must include statements of system functionality that satisfies user requirement and system
requirements [5]. Software system requirements are divided into functional and non-functional requirement.
Functional requirements refer to statements of services that product or system is required to provide. These include
reaction of the system to different inputs, it also involves what the system is not required to do [25].
Non-functional requirements on the other hand refers to the constraints on the services offered by the system, these
constraints could include time, process and/or standards [3]. Requirements engineering is a very complex and
difficult phase in software development because it has the most impact on the results that will be gotten from the
product and it involves every stakeholder including the users [9]. Requirement engineering is an approach or
process through which a software engineer collects, analyzes and implement requirements from all stakeholder
from all stakeholders into the software development processes. Requirements lifecycle of the software
development [14].
In a typical software development environment, requirement engineering is only performed at the beginning
phase of the project but in large and complex system development, requirement engineering is a continuous and
iterative process as changes occur during the development so as to meet customer needs and quality [27].
Requirement engineering contains sets of activities for analysing, documenting, reviewing, maintaining and
validating requirements for a system. Requirement engineering can be further broken down into four groups which
are requirement elicitation and development, documentation of requirement, requirement verification and
validation and requirement management/planning [28].
This paper reviews an effective model of requirement engineering process for software development. This
paper is organized as follows, section 2 describes various requirement engineering models being reviewed based
on software development and also highlight the number of journals and their sources being used for this paper.
Section 3 introduces and highlights a typical effective model for requirement engineering and its processes. Finally
section 4 describes the concluding remarks and future research work.
2. Related Works
In the past years, researchers have focused more on the requirements engineering part of software
engineering being an integral part of the discipline.
Requirements traceability is an important part of requirements management which is an integral part of
requirements engineering [7]. Requirements traceability enables the developers to be able to trace the software
requirements from the beginning to the end of the development. This includes definitions, techniques, challenges
and tools using a systematic analysis [29].
Torkar, Gorschek, Feldt, Raja & Kamran in 2009 proposed a model for effective requirements engineering
process thereby producing quality requirements for software development. They went on to discuss the
requirement engineering as being the most essential stage of software development life cycle. It is important to
apply requirements engineering practices to every stage of the life cycle for software development [12]. Some
stages in requirements engineering is iterative and therefore must be repeated at every stage. The model showed
that requirement engineering and management has a good impact on quality software production.
A proposed model for requirements elicitation, specification, analysis and management of requirements is
being linked with software change management process [31]. This is used to help the development team without an
adopted process methodology.
Mogk N. W. in 2014 defines engineering design process as measureable objective functions modelled as an
improvement issue where goals, results and first choice of users are being incorporated, this is described in their
article; Requirement management system based on optimization model of the design process. The main goal of this
design process is to present a method of viewing the requirements that enhance communication with the user and
what the user wants which combines decision making techniques with the requirements engineering.
Hofman and Lehner in 2001 studied 15 requirements engineering process in various industries and came up
with the fact that some participants saw requirements engineering process as an ad hoc process with a few
