A client oriented requirements baseline

Leite, J.C.S.P.; Oliveira, Alberto

doi:10.1109/isre.1995.512551

Cited by 34 publications

(31 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Efforts to specify requirements in a natural language, such as Language Extended Lexicon (LEL) [18], have been studied since the 90's. The authors propose a lexical analysis of requirements descriptions in order to integrate scenarios into a requirements baseline, making possible their evolution as well as the traceability of the different views of the requirements baseline.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Testing Prototypes and Final User Interfaces Through an Ontological Perspective for Behavior-Driven Development

Silva

Hak

Winckler

2016

Lecture Notes in Computer Science

View full text Add to dashboard Cite

OATAO is an open access repository that collects the work of Toulouse researchers and makes it freely available over the web where possible. This is an author-deposited version published in : http://oatao.univ-toulouse.fr/ Eprints ID : 18842The contribution was presented at HCSE 2016:http://www.hcse-hessd.org/ Abstract. In a user-centered development process, prototypes evolve in iterative cycles until they meet users' requirements and then become the final product. Every cycle gives the opportunity to revise the design and to introduce new requirements which might affect the specification of artifacts that have been set in former development phases. Testing the consistency of multiple artifacts used to develop interactive systems every time that a new requirement is introduced is a cumbersome activity, especially if it is done manually. This paper proposes an approach based on Behavior-Driven Development (BDD) to support the automated assessment of artifacts along the development process of interactive systems. The paper uses an ontology for specifying tests that can run over multiple artifacts sharing similar concepts. A case study testing Prototypes and Final UserInterfaces is presented to demonstrate the feasibility of this approach in early phases of the design process, providing a continuous quality assurance of requirements, and helping clients and development teams to identify potential problems and inconsistencies before commitments with software implementation.

show abstract

Section: Related Workmentioning

confidence: 99%

“…The template proposed by the computer can be revised which leads to a training of the computer program and a better understanding of following sentences. Some works [1,18] use different approaches to process natural language; nonetheless none follow a User-Centered Design process.…”

Section: Related Workmentioning

confidence: 99%

Testing Prototypes and Final User Interfaces Through an Ontological Perspective for Behavior-Driven Development

Silva

Hak

Winckler

2016

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…Efforts to specify requirements in a natural language, such as Language Extended Lexicon (LEL) [22], have been studied since the 90's. The authors propose a lexical analysis of requirements descriptions in order to integrate Scenarios into a requirements baseline, making possible their evolution as well as the traceability of the different views of the requirements baseline.…”

Section: Related Workmentioning

confidence: 99%

“…The template proposed by the computer can be revised; which leads to a training of the computer program and a better understanding of following sentences. Some works [22], [23] use different approaches to process natural language; nonetheless, none follow a User-Centered Design process. Wolff et al [24] proposes linking GUI specifications to abstract dialogue models.…”

Section: Related Workmentioning

confidence: 99%

An Approach for Multi-Artifact Testing Through an Ontological Perspective for Behavior-Driven Development

Silva¹,

Hak²,

Winckler³

2016

J. Complex Syst. Inform. Model. Q.

View full text Add to dashboard Cite

Abstract. In a user-centered development process, artifacts evolve in iterative cycles until they meet users' requirements and then become the final product. Every cycle gives the opportunity to revise the design and to introduce new requirements which might affect the specification of artifacts that have been set in former development phases. Testing the consistency of multiple artifacts used to develop interactive systems every time that new requirements are introduced is a cumbersome activity, especially if it is done manually. This paper proposes an approach based on Behavior-Driven Development (BDD) to support the automated assessment of artifacts along the development process of interactive systems. The paper uses an ontology for specifying tests that can run over multiple artifacts sharing similar concepts. A case study testing Task Models, Prototypes, and Final User Interfaces is presented to demonstrate the feasibility of this approach from the early phases of the design process, providing a continuous quality assurance of requirements, and helping clients and development teams to identify potential problems and inconsistencies before commitments with software implementation are made.

show abstract

“…This paper reports on a proposal for extending the requirements baseline model [3] with a scenario view, in which evolution is the major driving factor. The scenario view should evolve, as part of the requirements baseline, during the software construction process.…”

Section: Introductionmentioning

confidence: 99%