Premium
Requirements Engineering for Large and Very Large Scale Systems Part Two ‐Contract Based Systems
Author(s) -
Berenbach Brian,
ClelandHuang Jane
Publication year - 2010
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2010.tb01164.x
Subject(s) - session (web analytics) , deliverable , requirements elicitation , requirements engineering , computer science , requirements management , requirements analysis , product (mathematics) , work (physics) , requirements traceability , software engineering , tracing , engineering management , set (abstract data type) , scale (ratio) , requirement , systems engineering , engineering , software , world wide web , mechanical engineering , physics , geometry , mathematics , quantum mechanics , programming language , operating system
Requirements elicitation and management for contract based projects is significantly more complex than for product or product line development. For example, many practitioners are unaware of the fact that the traditional “V” model for requirements tracing does not work where there is a legal contract describing project deliverables; nearly every aspect of requirements engineering is more challenging, from elicitation to risk analysis and compliance management. This half‐day tutorial will describe in some detail contract issues that are typically not discussed in requirements texts and courses. This is part two of a two part tutorial. The morning session described how to set up processes and tooling for very large industrial projects. This session describes the unique nature of requirements engineering processes for contract based projects. Either session may be taken independently, but the attendee will get the most out of the tutorials by attending both sessions.