Requirements Specification Phase Research Articles

Functional suitability assessment of smart contracts: A survey and first proposal

AbstractBlockchain is a cross‐cutting technology allowing interactions among untrusted entities in a distributed manner without the need for involving a trusted third party. Smart contracts (i.e., programs running on the blockchain) enabled organizations to envision and implement solutions to real‐world problems in less cost and time. Given the immutability of blockchain and the lack of best practices for properly designing and developing smart contracts, it is crucial to assure smart contract quality before deployment. With the help of an exploratory survey involving developers and researchers, this paper identifies the practices and tools used to develop, implement, and evaluate smart contracts. The survey received 55 valid responses. Such responses indicate that (i) inefficiencies may occur during the development cycle of a smart contract, especially regarding requirements specification, design, and testing phases, and (ii) the lack of a shared standard to evaluate the functional quality of implemented smart contracts. To start coping with these issues, the adoption of functional suitability assessment measures recommended by the ISO/IEC 25000 standard, widely used in software engineering, is proposed by adapting them to the context of smart contracts. Through some examples, the manuscript also illustrates how to measure the functional completeness and correctness of smart contracts. The proposed procedure to measure smart contract functional suitability brings advantages to both developers and users of decentralized finance or non‐fungible tokens platforms, data marketplaces, or shipping and real estate services, just to mention a few. In particular, it helps (i) better outline the responsibilities of smart contracts, (ii) uncover errors and deficiencies of smart contracts in the early stages, and (iii) ensure that the established requirements are met.

Modeling of Security Fault-Tolerant Requirements for Secure Systems

Security services can keep a system from security breaches for a while, but they are ultimately compromised as the system is deployed and used. This paper describes the modeling of security fault-tolerant (SFT) requirements, which can tolerate the failures of security services for systems. SFT requirements are specified together with the security services requirements so that they tolerate breaches of the security services. This paper addresses an approach for specifying and analyzing SFT requirements using a meta-model. Threats to systems are identified in the requirements specification and analysis phases, and SFT measures against the threats are described with security services. An electronic commerce system is selected to illustrate the approach.

Designing the architecture of electrochemical energy storage systems. A model-based system synthesis approach

Designing complex systems that address a wide range of heterogeneous requirements is a difficult task. The skills and know-how of the designers are no longer sufficient and it becomes essential to provide them with efficient methodologies and computational tools to achieve this task. The objective of this paper is to present a model-based system synthesis (MBSS) approach to perform this task. This approach is notably based on the DEPS language and constraint programming. Design examples involving electrochemical energy storage systems are used to illustrate the approach. The design of a starting battery for an internal combustion engine is first presented. It demonstrates the ability to make rational and quantified design choices between several available cell technologies and models (lead–acid, Li-ion NCA, NMC or LFP) while taking into account many design constraints. An example of battery design for a hybrid or electric vehicle is then discussed. The requirements of this second example include in particular a mission profile to be satisfied. Based on these two case studies, the article shows the strength and usefulness of using the DEPS-based design methodology. This approach is particularly suitable for the preliminary design and requirements specification phases, which often require trade-offs between the different stakeholders.

Embedding Quality into Software Product Line Variability Artifacts

The success of any software product line development project is closely tied to its domain variability management. Whereas a lot of effort has been put into functional variability management by the SPL community, non-functional variability is considered implicit. The result has been dissatisfaction among clients due to resultant poor quality systems. This work presents an integrated requirement specification template for quality and functional requirements at software product line variation points. The implementation of this approach at the analytical description phase increases the visibility of quality requirements obliging developers to implement them. The approach proposes the use of decision tree classification techniques to support the weaving of functional quality attributes at respective variation points. This work, therefore, promotes software product line variability management objectives by proposing new functional quality artifacts during requirements specification phase. The approach is illustrated with an exemplar mobile phone family data storage requirements case study.

Embedding Quality into Software Product Line Variability Artifacts

The success of any software product line development project is closely tied to its domain variability management. Whereas a lot of effort has been put into functional variability management by the SPL community, non-functional variability is considered implicit. The result has been dissatisfaction among clients due to resultant poor quality systems. This work presents an integrated requirement specification template for quality and functional requirements at software product line variation points. The implementation of this approach at the analytical description phase increases the visibility of quality requirements obliging developers to implement them. The approach proposes the use of decision tree classification techniques to support the weaving of functional quality attributes at respective variation points. This work, therefore, promotes software product line variability management objectives by proposing new functional quality artifacts during requirements specification phase. The approach is illustrated with an exemplar mobile phone family data storage requirements case study.

Towards “Design for Interoperability” in the context of Systems Engineering

In product development, early decisions made within the requirements specification and design phase have significant impact on overall functionality, quality and lifecycle cost of the product. In Systems Engineering, these oftentimes iterative design phases are steered by underlying development models, providing processes, guidelines and best practices. One family of guidelines are the “Design for X” (DfX) tools or principles. In the development of mechatronic systems e.g. production systems, traditionally the mechanical, electric and software domain are to be distinguished. Over time, driven by trends of digitalization, communication and interconnection of systems, the product innovation and thus the required development effort has been shifting from the mechanical domain towards the software domain. The question of system interoperability thereby is of a fundamental nature. This is especially relevant within the current paradigms of Industry 4.0 and the Digital Twin.To reflect the growing importance of interoperability (i.e. the ability of systems to purposefully interchange interpretable information) as a requirement for the product within the design phase of technical systems, this paper introduces “Design for Interoperability” (DfIOp) as a new DfX principle. First, this is motivated by the ever-growing importance of information technology for current and future products. Then, the main contribution of the paper is the combination of the state of the art in the research domains of DfX, interoperability, Systems Engineering and Industry 4.0. Consequently, DfIOp will be presented, including a systematization model as well as a first method for its implementation. Further contemplation on DfIOp shows, that it enables derivative principles such as “Design for Data Analytics” and “Design for Digital Twin”. In future research, the underlying models as well as methods of DfIOp are to be further detailed and integrated into the research context.

A Fuzzy Case-Based Reasoning Model for Software Requirements Specifications Quality Assessment

Different software Quality Assurance (SQA) audit techniques are applied in the literature to determine whether the required standards and procedures within the Software Requirements Specification (SRS) phase are adhered to. The inspection of the Software Requirements Specification (iSRS) system is an analytical assurance tool which is proposed to strengthen the ability to scrutinize how to optimally create high-quality SRSs. The iSRS utilizes a Case-Based Reasoning (CBR) model in carrying out the SRS quality analysis based on the experience of the previously analyzed cases. This paper presents the contribution of integrating fuzzy Logic technique in the CBR steps to form a Fuzzy Case-Based Reasoning (FCBR) model for improving the reasoning and accuracy of the iSRS system. Additionally, for efficient cases retrieval in the CBR, relevant cases selection and nearest cases selection heuristic search algorithms are used in the system. Basically, the input to the relevant cases algorithm is the available cases in the system case base and the output is the relevant cases. The input to the nearest cases algorithm is the relevant cases and the output is the nearest cases. The fuzzy Logic technique works on the selected nearest cases and it utilizes similarity measurement methods to classify the cases into no-match, partial-match and complete-match cases. The features matching results assist the revised step of the CBR to generate a new solution. The implementation of the new FCBR model shows that converting numerical representation to qualitative terms simplifies the matching process and improves the decision-making of the system.

An effective approach to develop location-based augmented reality information support

Using location-based augmented reality (AR) for pedestrian navigation can greatly improve user action to reduce the travel time. Pedestrian navigation differs in many ways from the conventional navigation system used in a car or other vehicles. A major issue with using location-based AR for navigation to a specific landmark is their quality of usability, especially if the active screen is overcrowded with the augmented POI markers which were overlap each other at the same time. This paper describes the user journey map approach that led to new insights about how users were using location-based AR for navigation. These insights led to a deep understanding of challenges that user must face when using location-based AR application for pedestrian navigation purpose, and more generally, they helped the development team to appreciate the variety of user experience in software requirement specification phase. To prove our concept, a prototype of intuitive location-based AR was built to be compared with existing standard-location based AR. The user evaluation results reveal that the overall functional requirements which are gathered from user journey have same level of success rate criteria when compared with standard location-based AR. Nevertheless, the field study participants highlighted the extended features in our prototype could significantly enhance the user action on locating the right object in particular place when compared with standard location-based AR application (proved with the required time).

Rapid Formal Verification as Requirements Stage Verification and Validation Technique

Early formal verification of a system during initial stages of development has the potential to improve the confidence in the system specifications, in addition to improving the formal verifiability throughout the software development cycle. A formal verification methodology is derived to achieve system modelling and verification during the requirements specification and system design phase. This is achieved by using Focus Stream theory for developing a formal system model derived from requirements analysis leading to a preliminary software design. This results into component architecture and it incorporates the development of component behaviour using Finite Sate Machines. The models developed for real time system encompass modelling of infinite state domains. After model development, formal property enumeration under various categories is done. An enhanced safety property verification is proposed and implemented using Linear Temporal Logic propositions, pattern based properties and system safety based property patterns. Properties verification on the model is done in order to validate and refine the specifications. Derived properties are verified using NuXMV Satisfiability Modulo Theories based algorithms. Tool verification as mandated in RTCA DO-330 is incorporated in the proposed methodology. The proposed approach is practical, implementable by system designers and scalable to handle industrial systems.

An Analysis of the Impact of Transient Faults on the Performance of the CAN-FD Protocol

The increasing complexity of distributed real-time control systems in the vehicular area has led to the development of new protocols, such as controller area network with a flexible data rate (CAN-FD), that provides high-bandwidth communication with FD rate. Different topologies are used to interconnect electronic control units in safety-critical applications in the automotive area and the applied communication protocols, such as CAN-FD, must comply with reliability requirements. Moreover, the functional operations must be tested to their limits, since they require appropriate assessment techniques for different application scenarios. Recent research has highlighted that power switching systems cause transient faults that affect the communication network. In light of this concern, this paper explores the IEC/TS 62228:2007 and ISO 26262-3/4/9:2018 standards that can act as guidelines for the development of a test method and testing board for evaluating the impact of electrical fast transients on the performance of a distributed automotive control system. Metrics such as difference jitter, average jitter, and packet loss, are used to determine the fault impact on the control law of a critical vehicular control system. The experiments that were conducted show that during the four test scenarios in which the testing board was used, the average jitter increased from 10.41 to 29.05% in the worst case scenario. These results highlight the importance of carrying out consistent tests to prevent critical situations and that these data can be used in software requirements specification phases to improve reliability in vehicular control systems.

A Mobile Internet Service for Self-Management of Physical Activity in People With Rheumatoid Arthritis: Challenges in Advancing the Co-Design Process During the Requirements Specification Phase.

BackgroundUser involvement in the development of health care services is important for the viability, usability, and effectiveness of services. This study reports on the second step of the co-design process.ObjectiveThe aim was to explore the significant challenges in advancing the co-design process during the requirements specification phase of a mobile Internet service for the self-management of physical activity (PA) in rheumatoid arthritis (RA).MethodsA participatory action research design was used to involve lead users and stakeholders as co-designers. Lead users (n=5), a clinical physiotherapist (n=1), researchers (n=2) with knowledge in PA in RA and behavioral learning theories, an eHealth strategist (n=1), and an officer from the patient organization (n=1) collaborated in 4 workshops. Data-collection methods included video recordings and naturalistic observations.ResultsThe inductive qualitative video-based analysis resulted in 1 overarching theme, merging perspectives, and 2 subthemes reflecting different aspects of merging: (1) finding a common starting point and (2) deciding on design solutions. Seven categories illustrated the specific challenges: reaching shared understanding of goals, clarifying and handling the complexity of participants’ roles, clarifying terminology related to system development, establishing the rationale for features, negotiating features, transforming ideas into concrete features, and participants’ alignment with the agreed goal and task.ConclusionsCo-designing the system requirements of a mobile Internet service including multiple stakeholders was a complex and extensive collaborative decision-making process. Considering, valuing, counterbalancing, and integrating different perspectives into agreements and solutions (ie, the merging of participants’ perspectives) were crucial for moving the process forward and were considered the core challenges of co-design. Further research is needed to replicate the results and to increase knowledge on key factors for a successful co-design of health care services.

Conceptual Software Testing: a New Approach

Software testing is an important aspect of the software development life cycle that plays an important role in ensuring quality, applicability, and usefulness of products. UML has been applied in this development from the requirements specification and code generation phases through to testing. New approaches advocate addressing test cases from the initial work on requirements since this would facilitate applying them in the later stages. Hence, several approaches have been investigated for generating test cases from UML diagrams. Nevertheless, using UML diagrams as a conceptual basis for testing may embed ambiguity in semantics and discontinuity in structure, thus negating the advantages of introducing testing aspects at the initial stage of software development. This paper proposes a new diagrammatic approach as a foundation for identifying test cases. The viability of the method is demonstrated by examples that identify test cases utilizing UML use cases.

Une extension SysML pour l’ingénierie des exigences non fonctionnelles orientée but

This paper describes a work-in-progress in the framework of a research project aiming at defining traceability links between requirements phase and specification phase. The main idea is to extend the SysML language with the most relevant concepts of commonly used requirements engineering approaches. In this paper, we first define a set of SysML extensions to represent basic concepts of KAOS goal model. Then, we present a software tool to support the proposed extensions.

Naked Objects Framework

more and more business systems designed using object oriented approach, written using object oriented languages like Java and interfaces created through various tools, there is need for such systems to show the quintessence of object orientation, which is behavioural completeness. This paper discusses Naked Objects Framework (NOF), which is an open source prototyping tool based on Java that auto generates an entire system that is behaviourally complete by plainly defining behaviourally rich objects that can be easily accessed by the user. The resulting object oriented interface is very user friendly and allows both the developer and the client to equally contribute in the requirements specification phase.

PEPIA: a Norwegian collaborative effort for institutional repositories

PurposeThe purpose of this paper is to report on Project for Electronic Publications and Institutional Archives (PEPIA), which is a government‐sponsored Norwegian effort, to provide institutional repositories to multiple Norwegian universities, university colleges and other research institutions through a consortium managed by BIBSYS.Design/methodology/approachSome aspects of the project are headlined to give a brief introduction to the PEPIA project and the problems associated with creating a consortium with multiple institutions on one software platform.FindingsThe ongoing project PEPIA has shown that it is possible for multiple organizations to join forces and create a consortium to develop an institutional repository on one software platform. After an initial requirements specification phase it was found that most institutions have the same basic requirements, even though they may seem different. The requirements, besides basic registration and searching, are mostly centered on integration with library systems, research documentation systems, national OAI harvesters and preferably learning management systems. The experience with the freely available DSpace software is mostly good, but the work of integrating the software into an already existing software development platform and production environment was more complex than estimated. The user management mechanisms in DSpace is too simplistic but the development of a more advanced rule‐based access mechanisms for collections has resulted in a lot easier management by users, and can further lower the operating costs for the members of the consortium.Originality/valueThe paper provides an overview of the PEPIA project, which enables more and more institutions to see the benefits of working together towards better solutions.

Exploring defect causes in products developed by virtual teams

This paper explores the effects of virtual development on product quality, from the viewpoint of ‘conformance to specifications’. Virtual Development refers to the development of products by teams distributed across space, time, and organization boundaries (hence virtual teams). Specifically, causes of defect injection and non- or late-detection are explored. Because of the practical difficulties of obtaining hard project-specific defect data, an approach was taken that relied upon accumulated expert knowledge. The accumulated expert knowledge based approach was found to be a practical alternative to an in-depth defect causal analysis on a per-project basis. Defect injection causes are concentrated in the Requirements Specification phases. Thus defect dispersion is likely to increase, as requirements specifications are input for derived requirements specifications in multiple, related sub-projects. Similarly, a concentration of causes for the non- or late-detection of defects was found in the Integration Test phases. Virtual development increases the likelihood of defects in the end product because of the increased likelihood of defect dispersion, because of new virtual development related defect causes, and because causes already existing in co-located development are more likely to occur. The findings are important for virtual development environments and (1) allow further research focusing on a framework for lowering residual defects, and (2) give insights that can be used immediately by practitioners to devise strategies for lowering residual defects.

Pflegeinformatik: Bestandsaufnahme und Perspektiven einer Spezialisierung innerhalb der Pflege

Nursing Informatics is defined as a specialty that combines nursing science, computer science and informatics to capture, process, store and communicate data, information and knowledge from the nursing domain. Therefore, Nursing Informatics is understood as a subspecialty within nursing. In Germany, Switzerland and Austria, Nursing Informatics looks back to more than 10 years of experience in the field. A Nursing Informatics Framework is proposed to represent the scientific and practical work. It goes beyond a mere definition and forms an action space for showing present achievements and the need for future activities. An analysis of the state of the science reveals that applications in patient care, management and education and training are nearly equally covered by Nursing Informatics. However, a deficit in basic research is apparent mainly in formalising and representing nursing knowledge. There is also a lack of system descriptions following the phases of the software-engineering process. In the requirements specification phase for nursing information systems meaningful reporting applications for use in quality assurance, evidence based nursing and management will have to be identified. Systematic software-engineering including scientific evaluations is needed in particular of systems in emerging areas such as case management. However, the activities proposed require a thorough education and training in Nursing Informatics on all levels.

Specification of management views in information warehouse projects

An approach for specifying management views in the requirement specification phase of information warehouse projects is presented. Based on a framework relating development phases and abstraction layers, the roles of documents are outlined. Management views are used as metadata and parameters in subsequent development phases. Algorithms formally show the transformation of management views into logical data mart schemes and report queries. Development phases are integrated using meta-level relationships.

Requirements Reuse for Improving Information Systems Security: A Practitioner’s Approach

Information systems security issues have usually been considered only after the system has been developed completely, and rarely during its design, coding, testing or deployment. However, the advisability of considering security from the very beginning of the system development has recently begun to be appreciated, and in particular in the system requirements specification phase. We present a practical method to elicit and specify the system and software requirements, including a repository containing reusable requirements, a spiral process model, and a set of requirements documents templates. In this paper, this method is focused on the security of information systems and, thus, the reusable requirements repository contains all the requirements taken from MAGERIT, the Spanish public administration risk analysis and management method, which conforms to ISO 15408, Common Criteria Framework. Any information system including these security requirements must therefore pass a risk analysis and management study performed with MAGERIT. The requirements specification templates are hierarchically structured and are based on IEEE standards. Finally, we show a case study in a system of our regional administration aimed at managing state subsidies.

ViSta: a tool suite for the visualization of behavioral requirements

ViSta is a tool suite designed to support the requirements specification phase of reactive systems. It enables the user to prepare and analyze a diagrammatic description of requirements using the statechart notation. ViSta includes a template wizard, a graphical editor and a statechart visualization tool. The template wizard guides the user through the steps necessary for the extraction of relevant information from a textual description of requirements. This information is stored in a database that is used by the statechart visualization tool to automatically generate statechart layouts. The statechart visualization tool offers a framework that combines hierarchical drawing, labeling, and floorplanning techniques. Hence, the automatically produced drawings enjoy several important aesthetic properties: they emphasize the natural hierarchical decomposition of states into substates; they have a low number of edge crossings; they have a good aspect ratio, and require a small area. These aesthetic features are invaluable since they allow the user to shift focus from organizing the mental or physical structure of the requirements document to its analysis.