By Topic

2014 IEEE 1st International Workshop on Requirements Engineering and Testing (RET)

26-26 Aug. 2014

Filter Results

Displaying Results 1 - 13 of 13
  • [Front matter]

    Publication Year: 2014, Page(s):i - ii
    Request permission for commercial reuse | PDF file iconPDF (40 KB)
    Freely Available from IEEE
  • Contents

    Publication Year: 2014, Page(s): 1
    Request permission for commercial reuse | PDF file iconPDF (51 KB)
    Freely Available from IEEE
  • Message from the chairs

    Publication Year: 2014, Page(s):iii - iv
    Request permission for commercial reuse | PDF file iconPDF (99 KB) | HTML iconHTML
    Freely Available from IEEE
  • On the delicate balance between RE and Testing: Experiences from a large company

    Publication Year: 2014, Page(s):1 - 3
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (130 KB) | HTML iconHTML

    Requirements Engineering and Testing are considered inseparable and together enable successful projects. One could make a statement that serious negligence of any of the two will bring catastrophic consequences for the project, delays, failures and unhappy customers. Thus, alignment and cooperation between the two are not only recommended but highly required for contemporary complex software and s... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Revisiting the challenges in aligning RE and V&V: Experiences from the public sector

    Publication Year: 2014, Page(s):4 - 11
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1746 KB) | HTML iconHTML

    Successful coordination of Requirements Engineering and Testing (RET) is crucial in large-scale software engineering. If the activities involved in RET are not aligned, effort is inevitably wasted, and the probability of delivering high quality software products in time decreases. Previous work has identified sixteen challenges in aligning RET in a case study of six companies. However, all six cas... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Testers learning requirements

    Publication Year: 2014, Page(s):12 - 15
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (465 KB) | HTML iconHTML

    When software testers talk about their job, they generally state that their task is to find defects as well as to ensure that no (major) defects exist in the main paths of business processes. They often add the comment they are doing this by checking the software (application under test) against existing requirements. Its common sense that testers should be familiar with understanding and interpre... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A/B testing: A promising tool for customer value evaluation

    Publication Year: 2014, Page(s):16 - 17
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (160 KB) | HTML iconHTML

    This paper aims to describe the use of A/B testing, a method used in web-development and position it in the context of the requirements engineering process and customer value evaluation. We propose that A/B testing can complement qualitative user research and offer a potential way to validate the value which system improvements bring to customers. Finally, we discuss our research plan for investig... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Verifying security requirements using model checking technique for UML-based requirements specification

    Publication Year: 2014, Page(s):18 - 25
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1277 KB) | HTML iconHTML

    Use case analysis is known to be an effective method to clarify functional requirements. Security requirements such as access or information control tend to increase the complexity of functional requirements, and therefore, need to be correctly implemented to minimize risks. However, general developers find it difficult to correctly specify adequate security requirements during the initial phases ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Using automated tests for communicating and verifying non-functional requirements

    Publication Year: 2014, Page(s):26 - 28
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (424 KB) | HTML iconHTML

    In software development the code often must comply to a number of non-functional requirements, like architectural requirements. These requirements are often communicated and verified by writing guidelines and creating reports of the non-compliance. This way of communicating and verifying non-functional requirements is very costly since all developers needs to understand all requirements. It is als... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Position on metrics for security in requirements engineering

    Publication Year: 2014, Page(s):29 - 31
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (90 KB) | HTML iconHTML

    A number of well-established software quality metrics are in use in code testing. It is our position that for many code-testing metrics for security equivalent requirements level metrics should be defined. Such requirements-level security metrics should be used in evaluating the quality of software security early on, in order to ensure that the resultant software system possesses the required secu... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • C&L: Generating model based test cases from natural language requirements descriptions

    Publication Year: 2014, Page(s):32 - 38
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (991 KB) | HTML iconHTML

    Software testing tasks are usually time-consuming, especially if one considers complex projects. Requirements engineering artifacts are a valuable starting point for the development of software products, and most of software requirements specifications are written in natural language. This paper presents a tool that implements an approach for generating test cases based on Natural Language (NL) re... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Towards the automated generation of abstract test cases from requirements models

    Publication Year: 2014, Page(s):39 - 46
    Cited by:  Papers (4)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (991 KB) | HTML iconHTML

    In a testing process, the design, selection, creation and execution of test cases is a very time-consuming and error-prone task when done manually, since suitable and effective test cases must be obtained from the requirements. This paper presents a model-driven testing approach for conceptual schemas that automatically generates a set of abstract test cases, from requirements models. In this way,... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The observer-based technique for requirements validation in embedded real-time systems

    Publication Year: 2014, Page(s):47 - 54
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (760 KB) | HTML iconHTML

    Model-based requirements validation is an increasingly attractive approach to discovering hidden flaws in requirements in the early phases of systems development life cycle. The application of using traditional methods such as model checking for the validation purpose is limited by the growing complexity of embedded real-time systems (ERTS). The observer-based technique is a lightweight validation... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.