2007 · 30 citations · 4 references
EngineeringComputer ScienceSystems EngineeringRequirements EngineeringSoftware EngineeringSystems ModelingRequirements AnalysisRequirements ElicitationRequirements ModelingRequirements SpecificationSoftware ModelingSystem RequirementsModel-based Requirements EngineeringScenario ModelingScenariosSystem Requirements SpecificationSystem Use CasesUse Cases
Use Case diagrams are well-known for their use to specify and describe system requirements. From initial system requirements documents, use cases can be derived representing several scenarios. These scenarios can later be detailed in different ways, as for example, through informal descriptions. In this paper, system requirements are first specified using the SysML requirements diagram and later by use cases. The main goal is to fill the gap between documents written in natural language and use cases by modeling requirements in a graphical and tabular way, which can improve the requirements representation. Also, the relationship between requirements is enhanced. An example of a real time distributed system is given to illustrate the approach.
4
An analysis of the requirements traceability problem
O. Gotel, Clive Finkelstein · 2002 · 1.2K citations
Deriving safety requirements using scenarios
K. Allenby, Tim Kelly · 2002 · 130 citations
Engineering, Systems Engineering, Requirements Engineering +10