Are Use Cases Beneficial for Developers Using Agile Requirements?

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.

Download Full-text

A Tale of Two Agile Requirements Engineering Practices

Advances in Computer and Electrical Engineering - Advanced Methodologies and Technologies in Network Architecture, Mobile Computing, and Data Analytics ◽

10.4018/978-1-5225-7598-6.ch115 ◽

2019 ◽

pp. 1562-1574

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 chapter is to situate use cases and user stories in the 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.

Download Full-text

A Deep Dive into NoSQL Databases: The Use Cases and Applications

10.1016/s0065-2458(18)x0003-5 ◽

2018 ◽

Keyword(s):

Use Cases ◽

Deep Dive ◽

Nosql Databases

Download Full-text

Real-time Voltage Stability Assessment and Enhancement: Implementation and Use Cases

2020 AEIT International Annual Conference (AEIT) ◽

10.23919/aeit50178.2020.9241133 ◽

2020 ◽

Author(s):

Gilburt Chiang ◽

Simon Wyatt ◽

Pat Causgrove ◽

Hua Li

Keyword(s):

Real Time ◽

Voltage Stability ◽

Use Cases ◽

Stability Assessment

Download Full-text

Use of Business Models within Model Driven Architecture

Scientific Journal of Riga Technical University Computer Sciences ◽

10.2478/v10143-009-0010-1 ◽

2009 ◽

Vol 38 (38) ◽

pp. 119-130

Author(s):

Erika Asnina

Keyword(s):

Business Models ◽

Business Processes ◽

Use Cases ◽

Separation Of Concerns ◽

Model Driven Architecture ◽

Model Driven ◽

Development Processes ◽

Business Requirements ◽

Complex Computer ◽

Independent Model

Use of Business Models within Model Driven Architecture Model Driven Architecture is a framework dedicated for development of large and complex computer systems. It states and implements the principle of architectural separation of concerns. This means that a system can be modeled from three different but related to each other viewpoints. The viewpoint discussed in this paper is a Computation Independent one. MDA specification states that a model that shows a system from this viewpoint is a business model. Taking into account transformations foreseen by MDA, it should be useful for automation of software development processes. This paper discusses an essence of the Computation Independent Model (CIM) and the place of business models in the computation independent modeling. This paper considers four types of business models, namely, SBVR, BPMN, use cases and Topological Functioning Model (TFM). Business persons use SBVR to define business vocabularies and business rules of the existing and planned domains, BPMN to define business processes of both existing and planned domains, and use cases to define business requirements to the planned domain. The TFM is used to define functionality of both existing and planned domains. This paper discusses their capabilities to be used as complete CIMs with formally defined conformity between planned and existing domains.

Download Full-text