No full-text available
To read the full-text of this research,
you can request a copy directly from the authors.
Applying software engineering practices to produce reliable, high-quality and accurate automated test systems
Abstract
Test engineers developing test systems for mission-critical applications have to prove that the test system is reliable and accurate. As a result, software engineering practices are becoming increasingly important in order to mitigate any risk of failure that could result in costly downtime, incorrect behavior, or safety failures. Quality standards such as CMMI and ISO mandate regiment practices for tightly controlled development environments. Similarly, software for in flight software is required to demonstrate compliance with DO-178B and similar certification standards. While these standards improve quality and reliability, they increase the development time. As a result, engineers often spend a significant amount of time documenting, testing, and validating their work. The appropriate use of software engineering tools can automate and improve much of this process to increase efficiency and the effectiveness of testing and decrease the amount of time required. This article will provide an overview of practices for using these tools when developing large, complex test systems.
... Un gran número organizaciones reconocen que las iniciativas de mejora de los procesos pueden resolver estos problemas (Camargo, Ferrari & Fabbri, 2014, Muñoz, Gasca & Valtierra, 2014. Aunque el uso de buenas prácticas permite reducir el coste de pruebas fallidas o poco fiables, ya que el personal de prueba garantiza que las pruebas funcionen de forma correcta (Kerry & Delgado, 2009). ...
In this article an approach to process improvement is established through the validation process area of CMMI, by focusing on making a metamodel. Validation process area was considered specifically, SG1 prepare for validation. By the metamodel, a taxonomy of projects, the testing characterization, the testing templates for the product to validate, for the validation environment, for the testing procedures and criteria, and a test plan are defined. The focus was subjected to evaluation by a case study. The case study was conducted in the IT Department of a public higher education institution. The approach proved its validity, since testers feel that it gives them specific tests for the development of the validation process and allows them to prepare validation for a particular project.
It is well-known that success or failure of any software is dependent upon requirement analysis. The most significant problem hidden in natural language software requirements may be ambiguity. This can lead to poor design and performance of the final software product and can be time-consuming at the system analysis stage. Previous studies applied natural language processing (NLP) techniques to identify these ambiguities and reduce them to improve the requirement quality. However, this problem has not yet been fully resolved. This study applies NLP to automatically extract the software system requirement specification and visualize an overview of the software that is being developed. The proposed method clusters relevant software requirement sentences of each system user by text mining technique, and then extracts ‘actors’ and their ‘actions’ from sentences using NLP techniques. The recall technique is used to evaluate the efficacy of the proposed method. Response time and relevancy of the results are significant factors for software product satisfaction.
Software engineering practices are becoming increasingly important in order to mitigate any risk of failure that could result in costly downtime, incorrect behavior, or safety failures. Requirement elicitation is the process to systematically extract and identify the requirement of the system from a combination of human stakeholder, the system's environment, feasibility studies, market analyses, business plans, analyses of competing products and domain knowledge. Communication gaps exist between customers, engineers and project managers, and requirements information loss might occur across different software development periods. This paper researches on the variety of approaches used during user requirement analysis in the software development process. A review of user requirement analysis technique from the literature is studied by listing their advantages and limitation. A tabulated summary based on the discussion are produced to form a picture of user requirement technique. Directions for future work are then proposed, based on the review.
ResearchGate has not been able to resolve any references for this publication.