Enhancing a requirements baseline with scenarios

Leite, J.C.S.P.; Rossi, Gustavo; Balaguer, F.; Maiorana, Vanesa; Kaplan, Gladys; Hadad, Graciela Dora Susana; Oliveros, Alejandro

doi:10.1007/bf02745371

Cited by 94 publications

(51 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…We agree with Leite [12] in the importance of understanding the language of the problem and in the importance of building a glossary at the beginning of the elicitation process. Following Leite, two principles should be followed: the principle of circularity, (the glossary must be as self-contained as possible) and the principle of minimal vocabulary (requirements descriptions must use as many glossary items as possible).…”

Section: Unambiguitysupporting

confidence: 75%

Supporting requirements verification using XSLT

Durán

Ruiz–Cortés

Corchuelo

et al.

Proceedings IEEE Joint International Conference on Requirements Engineering

View full text Add to dashboard Cite

show abstract

Section: Unambiguitysupporting

confidence: 75%

Supporting requirements verification using XSLT

Durán

Ruiz–Cortés

Corchuelo

et al.

Proceedings IEEE Joint International Conference on Requirements Engineering

View full text Add to dashboard Cite

show abstract

“…9 depicts an environment we have been investigating as to support software transparency. It inherits the baseline idea from a previous work (Leite et al 1997), and uses a mix of intentional modeling (i * ; Yu 1994) with a scenario and light ontology (Language Extended Lexicon; Breitman and Leite 2003). Other investigators also have pursued the combination of intentional models with a scenario-oriented model in requirements engineering (Rolland and Salinesi 2009;Castro et al 2009).…”

Section: Fig 9 the Transparency Environmentmentioning

confidence: 99%

Software Transparency

2010

Self Cite

View full text Add to dashboard Cite

Software transparency is a new and important concern that software developers must deal with. This paper reports on initial findings on exploring the obstacles for enabling software transparency. For providing a definition of transparency and understanding the semantics of software transparency, a SIG (Softgoal Interdependence Graph) is used, which has been refined in three versions. Based on three example situations we demonstrate the application of the transparency SIG.

show abstract

“…Operations scenarios are widely accepted as a tool to help write good and complete requirements [1,2,3]. In the software development realm, scenarios are put to a wide variety of usages during design, implementation, and testing phases of the project lifecycle [4].…”

Section: Introductionmentioning

confidence: 99%

Web Based Tool for Mission Operations Scenarios

Boyles¹,

Bindschadler²

2008

SpaceOps 2008 Conference

View full text Add to dashboard Cite

A conventional practice for spaceflight projects is to document scenarios in a monolithic Operations Concept document. Such documents can be hundreds of pages long and may require laborious updates. Software development practice utilizes scenarios in the form of smaller, individual use cases, which are often structured and managed using UML. We have developed a process and a web-based scenario tool that utilizes a similar philosophy of smaller, more compact scenarios (but avoids the formality of UML). The need for a scenario process and tool became apparent during the authors' work on a large astrophysics mission. It was noted that every phase of the Mission (e.g., formulation, design, verification and validation, and operations) looked back to scenarios to assess completeness of requirements and design. It was also noted that terminology needed to be clarified and structured to assure communication across all levels of the project. Attempts to manage, communicate, and evolve scenarios at all levels of a project using conventional tools (e.g., Excel) and methods (Scenario Working Group meetings) were not effective given limitations on budget and staffing. The objective of this paper is to document the scenario process and tool created to offer projects a low-cost capability to create, communicate, manage, and evolve scenarios throughout project development. The process and tool have the further benefit of allowing the association of requirements with particular scenarios, establishing and viewing relationships between higher-and lower-level scenarios, and the ability to place all scenarios in a shared context. The resulting structured set of scenarios is widely visible (using a web browser), easily updated, and can be searched according to various criteria including the level (e.g., Project, System, and Team) and Mission Phase. Scenarios are maintained in a web-accessible environment that provides a structured set of scenario fields and allows for maximum visibility across the project. One key aspect is that the tool was built for a scenario process that accounts for stakeholder input, review, comment, and concurrence. By creating well-designed opportunities for stakeholder input and concurrence and by making the scenario content easily accessible to all project personnel, we maximize the opportunities for stakeholders to both understand and agree on the concepts for how their mission is to be carried out. I. BackgroundOperations scenarios are widely accepted as a tool to help write good and complete requirements [1,2,3]. In the software development realm, scenarios are put to a wide variety of usages during design, implementation, and testing phases of the project lifecycle [4]. Scenarios are often treated as relatively informal tools; widely divergent methods have been applied to developing and managing them. In particular, Achour [5] advocates developing guidelines for scenario authors, in order to maintain clarity and uniformity of approach to scenarios. A broad survey of scenario development and management ...

show abstract

Enhancing a requirements baseline with scenarios

Cited by 94 publications

References 19 publications

Supporting requirements verification using XSLT

Supporting requirements verification using XSLT

Software Transparency

Web Based Tool for Mission Operations Scenarios

Contact Info

Product

Resources

About