Numerous stakeholders collaborate to develop system requirements for a complex system. They conceive needs, evaluate risk, cost and benefits, identify tradeoffs, and negotiate priorities over a long period of time. Government and industry need a structured approach to requirements elicitation that supports this collaborative effort. Automated support is a long term goal of the author's research. The initial goal is to develop a firm foundation for capturing requirements, analyzing them, and supporting different views, including capture views (e.g. capabilities, constraints, operational environment), domain views (e.g. tracking, manufacturing, reliability), and stakeholder views (e.g. user, customer, designer, tester). These views help the analyst review specifications for errors and omissions. The paper identifies capture views and provides details concerning the system capabilities view, which includes functions, behavior, information entities, and non-functional requirements.
Index Terms:
formal specification; requirements capture; requirements analysis; modeling; system requirement; complex system; stakeholders; risk evaluation; cost analysis; benefits analysis; tradeoffs; requirements elicitation; collaborative effort; automated support; capture views; domain views; stakeholder views; errors; omissions; functions; behavior; information entities
Citation:
S. White, "Requirements capture and analysis prior to modeling," ecbs, pp.10, 1997 Workshop on Engineering of Computer-Based Systems (ECBS '97), 1997