Introduction to Requirements Engineering and Management - Requirements Engineering and Management for Software Development Projects - page 4

c. The marketing team, if the resultant product is a COTS product so that they
can find customers and sell it
d. The managements of both the supplier and the customer as both derive ROI
(Return on Investment) from the endeavor
6. That must be fulfilled—The need must be fulfilled. If it cannot be fulfilled
either due to limitations of technology or finance, it becomes a future
requirement. If the need cannot be fulfilled by the present endeavor, then the
endeavor itself becomes unnecessary
7. The proposed software product—It is the place where the need is expected to
be fulfilled. It is the end result of the present endeavor
8. During its development—This specifies the timeline when the need shall be
fulfilled. If it is not being fulfilled during present development, then the need
remains unfulfilled or a future need.
When we come to the software development arena, we have two types of
requirements namely the user requirements and the software requirements.
User requirements are the needs specified by the end user for the proposed
software product. They consist mainly of functionalities to be achieved by the
software and any conveniences that are needed in improving the personal per-
formance. Users may also require additional analyses that may be not possible in
the present system but are necessary in improving the performance of the system
or to serve the customers in a better manner.
Software requirements are additions to the user requirements that are unique to
software systems like usability, security, user friendliness, audit trails and so on.
Software Requirements is a term used by IEEE. Even then, IEEE did not define
this phrase in its glossary of software engineering terminology standard in spite of
defining a standard for ''Software Requirements Specifications''. Even the CMMI
for development version 1.3 also does not mention this phrase.
1.2 Requirements Management
Having put the term ''requirement'' in its proper perspective, let us now look at the
phrase ''Requirements Management'', the topic that is covered by this topic. As
can be readily seen the two words in this phrase are ''Requirements'' and
''Management''. We have already defined and put the term ''Requirements'' in its
proper perspective.
Now let us look at the term ''Management''. This term has three connotations.
1. The first connotation is as a ''group of individuals'' who are running the affairs
of the company. They normally comprise of the Board of Directors and other
senior executives designated by the Board as Managers.