A Framework for Aspectual Requirements Validation: an Experimental Study

Requirements engineering is a discipline of software engineering that is concerned with the identification and handling of user and system requirements. Aspect-Oriented Requirements Engineering (AORE) extends the existing requirements engineering approaches to cope with the issue of tangling and scattering resulted from crosscutting concerns. Crosscutting concerns are considered as potential aspects and can lead to the phenomena “tyranny of the dominant decomposition”. Requirements-level aspects are responsible for producing scattered and tangled descriptions of requirements in the requirements document. Validation of requirements artefacts is an essential task in software development. This task ensures that requirements are correct and valid in terms of completeness and consistency, hence, reducing the development cost, maintenance and establish an approximately correct estimate of effort and completion time of the project. In this paper, we present a validation framework to validate the aspectual requirements and the crosscutting relationship of concerns that are resulted from the requirements engineering phase. The proposed framework comprises a high-level and low-level validation to implement on software requirements specification (SRS). The high-level validation validates the concerns with stakeholders, whereas the low-level validation validates the aspectual requirement by requirements engineers and analysts using a checklist. The approach has been evaluated using an experimental study on two AORE approaches. The approaches are viewpoint-based called AORE with ArCaDe and lexical analysis based on Theme/Doc approach. The results obtained from the study demonstrate that the proposed framework is an effective validation model for AORE artefacts.

Analisis Dampak Perubahan Artefak Kebutuhan Berdasarkan Kedekatan Semantik Pada Pengembangan XP

The Extreme Programming (XP) development method is popular because of the flexibility of the development process, it can accommodate changes quickly. But this method has a weakness in terms of documentation. It is expected that the speed of discovering which parts of the source code need to be changed will be greatly improved by analyzing the impact of changes on the requirements document. In this study, a method of analyzing the impact of changes is proposed by tracing changes in the artifact of the need to find out the source code that occurs. Early language methods and semantic approaches are used. Based on the proximity of the semantics, it will be analyzed to find out the elements in the source code that use the Spearman Correlation Coefficient. The test dataset in this study consisted of the source code in the PHP programming language as well as the functional requirements of the software. Requirements change list is generated by analysis of the latest 2 (two) expert versions of the source code. The changing needs are described in a user story document. Based on the test results in this study, the average precision was 0.1725 and the average recall value was 0.6041.

Influence of Different Representation of Requirements on Idea Generation: An Experimental Study

The objective of this research is to understand how different representations of requirements influence idea generation in terms of quantity, addressment, sketch detail, novelty, and variety of conceptual sketches. Requirements are statements of need, desires, and wishes of the stakeholders that are used by engineers to frame the problem. Essentially, requirements are the raison d’etre for any engineering project. As the requirements document provides constraints and criteria for a design, it defines and determines the success of a project. While there is research studying the effect of requirements on the conceptual sketch, little study has focused one the impact of different requirement representations on solution development. An experimental study was conducted with 52 fourth year mechanical engineering undergraduate students. Two design problems were formulated with three different representations: a problem statement with embedded requirements, a problem statement and a traditional requirement list, and a problem statement with contextualized scrum stories. Each student was provided each design problems with two different representations of requirements. It was found that the use of contextualized scrum story representations significantly affected the conceptual sketch in the novelty of solution fragments and addressment of requirements, while no significant change in variety, sketch detail, and quantity was seen. Also, the contextualized representation positively affected all metrics but the sketch quantity. Finally, it was found that quantity is not directly related to the number of requirements addressed in the sketches.

ANALISIS KEBUTUHAN PERANCANGAN ULANG APLIKASI MOBILE TEMAN BUMIL MENGGUNAKAN FRAMEWORK SCRUM

Seeing the potential for healthtech startups that continue to emerge in Indonesia, of course companies must continue to create innovations to be able to compete with existing and future competitors, one of which is by doing a revamp or a process to change the appearance and user journey. As was done by one of the healthtech startup companies, namely PT. Global Urban Essentials in one of its products, namely the Teman Bumil application. This research was conducted to redesign the display and user journey in the Teman pregnant woman application. The design method used was the Scrum framework. The Scrum stages carried out are the first meeting, sprint planning meeting, sprint, sprint review meeting and sprint retrospective meeting. Data collection was carried out by studying documentation, observation, and interviews. Then the data were analyzed using the Miles and Huberman model with the stages of data reduction, data presentation, and conclusions. Through this research, it is known that the redesign was carried out to change the appearance and improve the experience by shortening the flow of application use, as well as the application design documentation process using the product requirements document guide which consists of three main parts, namely user requirements, interface pages, and flowcharts.

Self-generating quality control

This paper demonstrates how quality control infrastructure can be generated from a single requirements document. Taken from a recent project that is now being used in production at a large journal publisher, it discusses some of the challenges faced and techniques used when generating Schematron, XSpec tests, XML grammar checks, and documentation. The project set out to implement quality control requirements for journal articles using Schematron. In pursuing this objective, the project also created quality control infrastructure for Schematron itself that streamlines the process for incorporating iterative changes to requirements. The techniques used in this project and described in this paper may be generally applicable in other projects.

Torso body armour coverage defined according to feasibility of haemorrhage control within the prehospital environment: a new paradigm for combat trauma protection

Developments in military personal armour have aimed to achieve a balance between anatomical coverage, protection and mobility. When death is likely to occur within 60 min of injury to anatomical structures without damage control surgery, then these anatomical structures are defined as ‘essential’. However, the medical terminology used to describe coverage is challenging to convey in a Systems Requirements Document (SRD) for acquisition of new armour and to ultimately translate to the correct sizing and fitting of personal armour. Many of those with Ministry of Defence responsible for the procurement of personal armour and thereby using SRDs will likely have limited medical knowledge; therefore, the potentially complex medical terminology used to describe the anatomical boundaries must be translated into easily recognisable and measurable external landmarks. We now propose a complementary classification for ballistic protection coverage, termed threshold and objective, based on the feasibility of haemorrhage control within the prehospital environment.