scholarly journals JGOOSE: A REQUIREMENTS ENGINEERING TOOL TO INTEGRATE I* ORGANIZATIONAL MODELING WITH USE CASES IN UML

2009 ◽  
Vol 17 (1) ◽  
Author(s):  
André Abe Vicente ◽  
Victor F. A Santander ◽  
Jaelson B Castro ◽  
Ivonei Freitas da Silva ◽  
Francisco G Reyes Matus
Keyword(s):  
Requirements Engineering ◽  
Use Cases

scholarly journals An Ontology for Specifying and Tracing Requirements Engineering Artifacts and Test Artifacts

2019 ◽  
Vol 22 (1) ◽  
Author(s):  
María Luciana Roldán ◽  
Marcela Vegetti ◽  
Silvio Gonnet ◽  
Marcelo Marciszack ◽  
Horacio Leone
Keyword(s):  
Requirements Engineering ◽  
Use Cases ◽  
Test Cases ◽  
Semantic Consistency ◽  
Ontology Language ◽  
Testing Management

This paper proposes an ontology that defines and integrates the concepts adopted for use cases and test cases specification. These concepts belong to the metamodels of different Requirements Engineering and testing management supporting tools, and their formalization in an ontology language prevents using concepts ambiguously and enables interoperability among the involved tools, in order to achieve semantic consistency and artifacts tracing.

A Tale of Two Agile Requirements Engineering Practices

2018 ◽  
pp. 7577-7587
Author(s):  
Pankaj Kamthan ◽  
Terrill Fancott
Keyword(s):  
Requirements Engineering ◽  
Agile Software Development ◽  
Use Cases ◽  
User Stories ◽  
Similarities And Differences ◽  
Agile Software ◽  
Engineering Practices ◽  
Different Origins ◽  
Agile Requirements ◽  
Practical Implications

There are a number of concerns in agile software development, including requirements engineering. There are different types of agile requirement, of which currently the most common forms are use cases and user stories. The use cases and user stories have different origins, both in space and in time, but, by being among the practices of scenario-oriented requirements engineering (SORE), they are not entirely unrelated. The purpose of this article is to situate use cases and user stories in context of each other. This is done by means of a conceptual framework for systematically comparing use cases and user stories. The understanding of similarities and differences between use cases and user stories have pedagogical as well as practical implications.

Business Indicators for Data Warehouse Requirement Engineering

2020 ◽  
pp. 71-100
Author(s):  
Hanu Bhardwaj
Keyword(s):  
Data Warehouse ◽  
Requirements Engineering ◽  
Requirement Engineering ◽  
Decision Makers ◽  
Use Cases ◽  
Use Case ◽  
Data Warehouses ◽  
Functional Perspective ◽  
Information Contents

Traditionally, data warehouse requirements engineering is oriented towards determining the information contents of the warehouse to be. This has resulted in a de-emphasis of the functional perspective of data warehouses. Consequently, it is difficult to specify functions needed for computing business indicators. The authors' approach aims to elicit needed business indicators from organizational decision makers. Thereafter, indicator hierarchies are built. Then they associate functions with business indicators of the hierarchy. These functions are visualized as use case diagrams. To do this, they extend these diagrams to allow for actor aggregation in addition to actor specialization. Further, they introduce the ‘estimated from' relationship between use cases, in addition to the ‘extend' and ‘include' relationships of UML. They illustrate their proposals with an example.

An Experimental Comparison of System Diagrams and Textual Use Cases for the Identification of Safety Hazards

2014 ◽  
Vol 5 (1) ◽  
pp. 1-24 ◽  
Author(s):  
Tor Stålhane ◽  
Guttorm Sindre
Keyword(s):  
Control System ◽  
Requirements Engineering ◽  
Development Process ◽  
Early Stage ◽  
Use Cases ◽  
Experimental Comparison ◽  
Safety Hazards ◽  
Safety Requirements ◽  
Peripheral Equipment ◽  
Life Threatening

Requirement defects are more costly to correct the later in the development process they are discovered. The same applies to safety requirements, and defects that remain in the fielded system are then not only costly, but potentially life-threatening. It is important to discover safety hazards as early in the process as possible, and it is thus interesting to integrate safety analysis with techniques used in the early stage of requirements engineering. This paper describes an experiment comparing how well two system diagrams and textual use cases support non-experts in identifying hazards in a simple control system. Results show that system diagrams were better for finding hazards related to peripheral equipment, while for all other kinds of hazards textual use cases were as good or better. Not only the type of representation matters, but also how the information is brought into focus for the analyst, as this might steer the analyst towards noting some hazards but ignoring others.

Integration and analysis of use cases using modular Petri nets in requirements engineering

1998 ◽  
Vol 24 (12) ◽  
pp. 1115-1130 ◽  
Author(s):  
Woo Jin Lee ◽  
Sung Deok Cha ◽  
Yong Rae Kwon
Keyword(s):  
Petri Nets ◽  
Requirements Engineering ◽  
Use Cases

scholarly journals Requirements Engineering Contributions on the Development of Educational Software for the Blind or People with Impaired Vision

2006 ◽  
Vol 9 (1) ◽  
Author(s):  
Victor Francisco Araya Santander ◽  
Dorisvaldo Rodrigues da Silva
Keyword(s):  
Requirements Engineering ◽  
Educational Software ◽  
Use Cases ◽  
Functional Requirements ◽  
Impaired Vision

This paper presents an account of the experience observed when obtaining a set of requirements for the development of educational software for people with impaired vision. Numerous techniques of requirements engineering, specifically review and prototyping techniques, were applied to elicit, analyze, and validate 51 requirements for educational software for the vision impaired. Requirements were documented and subdivided in functional requirements (FR) and non-functional requirements (NFR). To improve the understanding of these requirements, they were represented via Use Cases at UML. The results were the elicitation, analysis and negotiation, modeling, and validation of 40 functional requirements, and 11 non-functional requirements, as well as the diagram of the resultant of use cases.

Sign in / Sign up

Export Citation Format

Share Document