z-logo
Premium
Requirements management as a matter of communication
Author(s) -
Ogren Ingmar
Publication year - 1999
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.1999.tb00340.x
Subject(s) - vendor , computer science , requirements management , requirements analysis , formalism (music) , requirements elicitation , process (computing) , process management , work (physics) , system requirements specification , engineering management , knowledge management , systems engineering , software engineering , engineering , business , programming language , mechanical engineering , art , musical , software , marketing , visual arts
Requirements work all started as a dialogue between a vendor and an end user. Nowadays this dialogue has been complicated through introduction of marketing and acquisition personnel. This has led to introduction of requirements specifications, but the need for a basic dialogue is still there since a specification cannot capture the increase of knowledge that will always take place during development. An efficient dialogue must not only include requirements, but also stated missions, problem management and understandable formalism for the system's structure and behavior. Further study of the dialogue shows that requirements management must be managed as a process in parallel with processes for development and verification.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here