Automated integrated support for requirements-area and validation processes related to system development

Alarcón, Pedro Pablo; Garbajosa, Juan; Crespo, Arturo Furones; Magro, B.

doi:10.1109/indin.2004.1417346

Cited by 12 publications

(12 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A Software Engineering Environment will manage the XML schemes and documents and will trigger the execution of the defined tools for performing the tasks assigned to different documents or subdocuments. A prototype was already developed few years ago as presented in (Alarcón et al, 2004).…”

Section: Discussionmentioning

confidence: 99%

See 1 more Smart Citation

Defining and Using a Metamodel for Document-Centric Development Methodologies

Bollaín¹,

Garbajosa²

2007

Proceedings of the Second International Conference on Evaluation of Novel Approaches to Software Engineering

View full text Add to dashboard Cite

The concept of software product is often associated to software code; process documents are, therefore, considered as by-products. Also very frequently, customers primarily demand "results" and, in a second place, documentation. Development efforts are then focused on code production at the expense of documents quality and corresponding verification activities. As discussed within this paper, one of the root problems for this is that documentation in the context of methodologies is often described with not enough level of detail. This paper presents a metamodel that faces this problem. It is an extension of ISO/IEC 24744, the metamodel for methodologies development. Under this extension, documents can become the drivers of the methodology activities. Documents will be the artifact in which method engineers should focus for methodology development, by defining its structure and constraints. Developers will put their effort in filling sections of the documents as the way to progress in the process execution. This process execution will be guided by those documents defined by the method engineers. This approach can be, as well, the basis for a new approach to a Document-Centric Software Engineering Environment.

show abstract

Section: Discussionmentioning

confidence: 99%

“…The use of documents to drive the software process is presented in (Bollain et al, 2003) and (Alarcón et al, 2004); it can be considered as a precedent research work to this one, but the theoretical background is not provided within here; these references also introduce which are the requirements for documents to support models.…”

Section: Related Workmentioning

confidence: 99%

Defining and Using a Metamodel for Document-Centric Development Methodologies

Bollaín¹,

Garbajosa²

2007

Proceedings of the Second International Conference on Evaluation of Novel Approaches to Software Engineering

View full text Add to dashboard Cite

show abstract

“…The interaction between test tools and SUTs has been solved from technical and engineering point of view but current solutions lack of the required generality and scalability to test any SUT. For example, the TTCN-3 [4] standard, and tools such as FIT [5], FitNesse [6], Easyaccept [7], and TOPEN [8], [9] test any kind of software using façade components to support the interaction with the SUT; however these façade components are specific for each SUT. In fact, the problem was discovered when a test tool built inhouse, TOPEN [8], had to be connected over and over again with different SUTs, and the cost of this connection was higher than the adaptation of TOPEN to a new domain itself.…”

Section: Introductionmentioning

confidence: 99%

A Systematic Process for Implementing Gateways for Test Tools

Díaz

Yagüe

Garbajosa

2009

2009 16th Annual IEEE International Conference and Workshop on the Engineering of Computer Based Systems

View full text Add to dashboard Cite

Test automation is facing a new challenge because tools, as well as having to provide conventional test functionalities, must be capable to interact with ever more heterogeneous complex systems under test (SUT). The number of existing software interfaces to access these systems is also a growing number. The problem cannot be analyzed only from a technical or engineering perspective; the economic perspective is as important. This paper presents a process to systematically implement gateways which support the communication between test tools and SUTs with a reduced cost. The proposed solution does not preclude any interface protocol at the SUT side. This process is supported using a generic architecture of a gateway defined on top of OSGi. Any test tool can communicate with the gateway through a unique defined interface. To communicate the gateway and the SUT, basically, the driver corresponding to the SUT software interface has to be loaded.

show abstract

“…Therefore the testing tools in [31] and [32]. Since then, it has evolved and has been and environment will be formed, in part, from knowledge integrated with a software/systems engineering environment related to the application domain, and the application itself; [33] in a project sponsored by the European space Agency this will alleviate the test engineer's work. In the model ESA/ESTEC.…”

mentioning

confidence: 99%

“…testing and software engineering environment can become In order to build a validation environment for acceptance integrated are available [43] and [33]. A general study on testing, the following sources of knowledge have been identi-validation-tools architecture can be found in [44] and on tools fied: and environments in [45].…”

mentioning

confidence: 99%

Applying the Knowledge Stored in Systems Models to Derve Validation Tools and Environments

Yagüe

Garbajosa

2007

6th IEEE International Conference on Cognitive Informatics

View full text Add to dashboard Cite

It is frequent that test tools are basically indepen-the models. The amount of knowledge related to scenarios dent from the application domain. This is usually the case for modeling is huge. Reference [2] reports that a lot of effort has languages as well. This reflection becomes particularly relevant been invested in techniques and approaches related to modelfor validation tools, since the validation process is closely related to requirements. Therefore, test engineers must work at a much based testing and validation, with limited success. Some other lower level of abstraction than that of the system domain. interesting references are [31, [4] and [5]. Therefore the apThe problem is especially relevant when dealing with complex proach taken by this paper is to model the system in line with systems, in which hardware and software are closely related, acceptance tests requirements. That is, the effort is focussed such as ambient intelligence systems, automotive, power plants, on the system interface required to support acceptance testing telecommunication and autonomic systems in general.The authors of this paper claim that validation tools can and avoids describig system behavior and will be domain specific in the future. For this reason, According to reference [6] acceptance testing is focused they will have to include knowledge defined in the system on different types of requirements such as functional, perrequirements. As explained within this paper, this knowledge can be incorporated into the validation tools with limited involvement formance, man-machie interacton. Followig [6] the main from the test engineer. These domain specific-tools will make the goals of acceptance testing are: to verify the man-machine task easier for test engineers. This paper analyzes the different interactions, validate the required functionality of the system, kinds of knowledge involved in domain-specific validation tools, verify that the system operates within the specified constraints specifically acceptance testing tools. The knowledge is expressed and check the systems external interfaces. Our work is aligned in terms of requirements and models. This paper also presents a model driven engineering approach with ISO/JEC 12207, Software hfecycle processes [7] and to derive validation tools and environments from system models. ISO/JEC 15288:2002, System lifecycle processes [8]. To clarify This approach uses model transformations. Derivation can be issues of terminology, the term 'testing' will be used in performed in either a semiautomatic or fully automatic way de-this paper to indicate some activities required to support pending on the system characteristics. Through these approaches, validations, i.e. testing is not a different process to validation. software and systems engineers can access to domain-specific Tests are structured into test procedures and test procedures validation tools during the early stages of the system life cycle. Te ade stru mber o t est procedures a redurs are made of a number of steps. Test procedures...

show abstract

Automated integrated support for requirements-area and validation processes related to system development

Cited by 12 publications

References 2 publications

Defining and Using a Metamodel for Document-Centric Development Methodologies

Defining and Using a Metamodel for Document-Centric Development Methodologies

A Systematic Process for Implementing Gateways for Test Tools

Applying the Knowledge Stored in Systems Models to Derve Validation Tools and Environments

Contact Info

Product

Resources

About