Premium
What Is A Requirement?
Author(s) -
Harwell Richard,
Aslaksen Erik,
Mengot Roy,
Hooks Ivy,
Ptack Ken
Publication year - 1993
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.1993.tb01553.x
Subject(s) - requirements management , schedule , quality (philosophy) , product (mathematics) , key (lock) , process (computing) , computer science , process management , risk analysis (engineering) , requirements analysis , requirement , engineering management , engineering , business , computer security , philosophy , geometry , mathematics , software , epistemology , programming language , operating system
Each contract specialist, lawyer, engineer, systems engineer, manager, or anyone else involved in the transition of vision into product , has his or her own definition of a requirement. With the rare exception, all are applicable and meaningful – but most are forgotten or ignored in the crunch to produce an effective requirements document under constrained schedule and funding environments. Yet, the need for effective requirements generation is probably the number one priority today in product development needs. Rather than approaching this problem from the theoretical or apriori standpoint, this paper examines the nature of a requirement through a process of identifying key characteristics and relationships from the viewpoint of the requirements manager/analyst and the requirements user (design team). It also discusses the importance of determining that requirements convey a need (as opposed to a directed solution), and ascertaining quality in terms of contextual adequacy.