Requirements Development Process Research Articles

FROM LOCAL TO GLOBAL: DEVELOPING AN E-COMMERCE PLATFORM TO EMPOWER LOCAL VENDORS

This research work outlines the creation and implementation of an e-commerce website designed to support local vendors by providing a platform where they can list their products for free. The website allows users to buy products directly from these vendors, with an after-sale service ensuring customer satisfaction before funds are transferred to the sellers. Key features of the website include strong security measures, an intuitive user interface, and a unique focus on helping local vendors while providing a safe and satisfying shopping experience for customers. This initiative aims to boost local businesses and provide customers with a reliable online shopping platform. The following sections cover the requirement analysis, system architecture, development process, testing methodologies, implementation strategies, marketing efforts, and ongoing improvement measures to ensure the project's success.

Developing ambient assisted living technologies exploiting potential of user-centred co-creation and agile methodology: the CAPTAIN project experience

Information and Communication Technology can turn older adults’ homes into smart living environments, decreasing the need for support and improving life quality. However, new technology has high uncertainty in terms of acceptance. Co-creation approaches are proposed to reach high acceptability, usability and satisfaction, but performance evaluations are sparse. This paper aimed at presenting the evaluation of a hybrid approach of Agile co-creation framework, specially designed for large, distributed consortia and cross-national collaborations.The new framework, leveraging the concepts of Design Thinking, Lean start-up, and SCRUM Agile, was tested in the H2020 CAPTAIN project. A network of stakeholders, built across five Living Labs, allowed the participatory design of the CATAIN technology through multiple iterations. A pre-post assessment questionnaire was administered to team components and used to compare partners’ perspective and satisfaction about CAPTAIN‘s and other projects methodologies. A longitudinal assessment throughout the iterations, using actionable metrics, monitored team morale and stakeholders’ engagement and satisfaction.The CAPTAIN development process resulted in a stronger involvement of the partners and a in better perception of requirements elicitation, design and development process than previous projects. Team morale was good and steady along the development iterations. Stakeholders increased from 91 to 132 along the iterations and more than 90% were satisfied.The tested framework went beyond usual participatory designs. It required stronger technical coordination, activity planning and communication among technical and pilot partners, but resulted in high satisfaction and engagement of both team members and stakeholders, showing its validity as a development approach for H2020 projects.

Requirements Management Tools for Software Systems: A Systematic Tools Review

This article contains a systematic review of Requirements Management tools (RM tools) for Software Systems. A research question was defined as the following: requirements development process of large-scale software system (with thousands of requirements) and an interaction problem during this process (communication, coordination and control). The problem is caused by the fact that the requirements development process is a cross-disciplinary task and it involves multiple parties — stakeholders, domain experts, and suppliers with own goals and constraints, and thus, the interaction between them seriously slows down the overall requirements development process more than writing the requirements specification itself. The tools were classified into the following classes: Requirements Management Tools, ALM/PLM/SDLC Tools, Model-based System Engineering tools with Requirements support, Natural Language based tools for Requirements Engineering, WYSIWYG-prototyping and Requirements platform, Open Source tools, and tools developed by Russian vendors. Each tool class was described and represented with list of relevant tools — including feature-rich solutions, and a description of key features. A contribution of functionality from each tool into the research question was analyzed and summarized including potential further improvement steps. Advantages and disadvantages of the existing RM tools were represented in this work. To approach the research question, further potential directions were described.

Requirements Engineering for Software Systems: A Systematic Literature Review

This article contains a systematic literature review of requirements engineering for software systems. The literature published within last 5 years was included into the review. A research question was defined as requirements development process of large scale software system (with thousands of requirements) and an interaction problem during this process (communication, coordination and control). The problem is caused by the fact that large-scale software system requirements process is a cross-disciplinary task and it involves multiple parties — stakeholders, domain experts, and suppliers with own goals and constrains, and thus, the interaction between them seriously slows down the overall requirements development process than writing the requirements specification itself. The research papers were classified by several research directions: Natural Language Processing for Requirements Engineering (NLP4RE), Requirement Prioritization, Requirements Traceability, Quality of Software Requirements, Non-functional Requirements and Requirements Elicitation. Motivation and intensity of each direction was described. Each direction was structured and represented with the key references. A contribution of each research direction into the research question was analyzed and summarized including potential further steps. It was identified that some researchers had met a part of the described problem in different forms during their researches. At the end, other researches were described additionally in a short overview. To approach the research question further potential direction was described.

Initiatives and challenges of using gamification in software engineering: A Systematic Mapping

Context:Gamification is an emerging subject that has been applied in different areas, bringing contributions to different types of activities. Objective:This paper aims to characterize how gamification has been adopted in non-educational contexts of software engineering (SE) activities. Methods:We performed a Systematic Mapping of the literature obtained from relevant databases of the area. The searches retrieved 2640 studies (published up to January 2020), of which 548 were duplicates, 82 were selected after applying the inclusion and exclusion criteria, and 21 were included via the backward snowballing technique, thus reaching a total of 103 studies to be analyzed. Results:Gamification provided benefits to activities like requirements specification, development, testing, project management, and support process. There is evidence of gamified support to some CMMI 2.0 Practice Areas. The most commonly used gamification elements are points and leaderboards. The main benefit achieved is the increased engagement and motivation to perform tasks. Conclusion:The number of publications and new research initiatives have increased over the years and, from the original authors’ reports, many positive results were achieved in SE activities. Despite this, gamification can still be explored for many SE tasks; for the addressed ones, empirical evidence is very limited.

Requirements development process for manufacturing information systems based on quality function deployment

ABSTRACTThe requirements development process (RDP) is an important stage in deploying functional requirements from user requirements in the design of a manufacturing information system. As the RDP may contain subjective views or misunderstanding of user requirements, developers of a manufacturing information system should verify the effectiveness, consistency and completeness of the requirements in an RDP. Quality function deployment (QFD), a systematic process of deploy product functions the voice of customer, provides developers with a solid mechanism to check the effectiveness of the voice of customers and to ensure the consistency and completeness of product functions in the product development process. In order to utilise these advantages of QFD, this study proposes a QFD-based RDP that introduces the concept of QFD to the existing RDP. The QFD-based RDP in the design of a manufacturing information system defines the critical-to-system functions as product critical-to-quality (CTQ) of the QFD-1 process and derives the functional requirements from critical-to-system functions in the CTQ of the QFD-2 process. Thus, it is able to easily check the effectiveness of the user requirements and to guarantee the consistency and completeness of functional requirements. This study describes all the activities and tasks of each step of the RDP in detail for developers to execute the RDP by themselves. In order to check the usefulness of the proposed RDP, this study also applies it to the design stage of a quality management system and conducts comparison test with general RDP.

Public sustainable-energy requirements and innovation in UK PFI school projects

In a bid to understand the relationship between public sector clients’ sustainable energy requirements and innovation, this paper describes a study examining the requirement development process in four private finance initiative (PFI) school projects. A case study approach was adopted to enable a greater understanding of the public sector clients’ activities at the front end of the design process, particularly focusing on requirement identification and the effect of the requirement on private sector actors’ pursuit of an innovative sustainable design. The findings have shown that incentive effects of the requirements are often weak in PFI projects, particularly in relation to the requirement’s specificity and achievability, the inability of requirements such as BREEAM to promote energy efficiency and the low weighting of environmental sustainability on PFI bid evaluation criteria. Taken together, these results offer insight into public authorities in relation to the necessary conditions for the use of requirements as an effective contractual mechanism to encourage innovation for sustainable energy.

Capability Maturity Model Integration (CMMI) for Optimizing Object-Oriented Analysis and Design (OOAD)

The current popular method in analysis and design phase is object-oriented analysis design (OOAD). The OOAD method aims to identify the objects which are responsible for their own. Mostly, the measurements of OOAD results are using verification and validation technique. A more demanding approach is expected from the OOAD method to improve software development process. To address this issue, this paper use Capability Maturity Model Integration (CMMI) as integrated software process improvement standard and approach. The purpose of CMMI is to improve process in creating product or services within organization. Therefore, the idea of improving process using CMMI will be applied for optimizing OOAD. The proposed method in this study is by constructing checklist criteria which already comply with requirement development process area in CMMI. Each criterion will be given certain score, then the score will summarize into total number from the assessment towards the Unified Modeling Languange (UML) Diagrams. The result obtained score of 185 for all criteria in the checklist and achieved 77,08% of CMMI level implementation, which categorized into Large Implementation (LI). The score also means that the UML diagrams are quite good and could be delivered through the next steps of software development life cycle.

차량용 반도체의 품질 확보를 위한 사양 및 설계 개발 프로세스 수립

With the trend of increasing needs for high-technology from customer and tightening regulation on automotive fuel efficiency and safety, application of E/E system has been expanding consistently in automotive industry. Thus, demand for core elements of E/E system has been growing: micro controller, analog IC and ASIC. But, development process of automotive semiconductor hasn't been clearly established in domestic area. This research aims to present a guide and an example for construction of requirement and design development process on semiconductor based on ISO/TS 16949 that is requirement for quality management system, CMMI that has been proven in various area and ISO 26262 widely used methodology for functional safety. It is expected that the result of this research is used as guidance for construction of semiconductor development process.

Editorial

Editorial

Avoiding Conflicting Requirements: Development of Home Healthcare Devices Through an Interdisciplinary Approach

<i>Avoiding Conflicting Requirements:</i> Development of Home Healthcare Devices Through an Interdisciplinary Approach

시스템 요구사항 최적화를 위한 프레임워크

A well organized system requirements provide a solid basis of achiving a successful project and are effective methods of communication among stakeholders. We illustrate and propose a 'System Requirement Development Framework' to develop correct requirements as a methodical approach. We first organize a 'Requirement Development Process' and then establish a 'Non-Functional Requirements Principle'. On these basis, we next propose a 'Requirement Development Guideline' from a perspective of 'Functional Requirement', 'Non-Functional Requirement' and 'Triage' in advanced stages. We also verify and evaluate the suitability of our proposed 'System Requirement Development Framework' by applying it to several projects.

The emergence of shared understanding: applying functional pragmatics to study the requirements development process

AbstractWhile the importance of social interactions and especially communication is generally acknowledged in information systems development and requirements development, there are few studies that investigate communication. Departing from the conceptualisation of information systems development as a language development and formalisation process, we focus on linguistic communication and the development of language‐based shared understanding of requirements. We investigate and analyse the semantic alignment process by which stakeholders achieve shared understanding in requirements development. We adopt Functional Pragmatics and examine how linguistic communication is shaped and regulated during requirements development in an actual project. By developing a pattern for semantic alignment and its use as an analytical lens, we enable a systematic and insightful understanding of communication in information systems development.

Human Factors Considerations in Global Positioning System (GPS) Receiver Technology: Contrasting Military Technical Requirements with User Expectations

This paper presents only the opinions of the authors for a forum of other Human Factors professionals. No representation of The Aerospace Corporation, GPS Wing, US Air Force, US Army, or US Department of Defense (DoD) policy is implied or intended. The need for human factors considerations in the development of handheld GPS receiver technology becomes increasingly apparent as society becomes increasingly dependant on precision navigation and timing information. GPS receivers provide ubiquitous situational awareness, during the daily mundane commute or in theater amidst the fog of war. Both military and commercial receivers are only as useful as their ability to convey navigation information to the user in a timely and reliable manner. Warfighters have become familiar with the ease and convenience of commercial receivers, mapping functionality, and integrated technology. However, there is great variance between the requirement set for military operations and civilian applications. The US Army and Air Force GPS Wing face future expectation management issues with military GPS user equipment. Potential areas for risk mitigation include careful human factors considerations early in the requirements development process, platform and application tailoring, incorporating “best practices” from industry and commercial end-user experience, and education and training.

Structuring complex requirements

Sets of requirements that analysts are dealing with are often big and complex. That makes requirements structuring one of the most important activities in requirements engineering, because of how requirements are structured and presented directly impacts the requirements development process and the quality of requirements. In this methodological paper we argue that a requirements analyst has to build a requirements architecture that fits the properties of the problem. In particular, the requirements analyst should create a clear vision of the principles governing how requirements are being defined, built and presented. We review some of the instruments that an analyst can use to structure requirements: requirements sets, views, levels and links. Among static views we emphasize concepts view , and also consider functions view, application architecture view, and other views; among dynamic views we consider use cases view, operational scenarios view, events view, and others. We specifically notice the importance of individual requirements sets , the purpose of which is to reveal the requirements for a particular element (concept, function, action, etc.). We argue in favor of differentiating between requirements model and requirements representation. We demonstrate on examples how requirements architecture is needed in complex contexts.

6.6.3 Meeting the Needs of Hydrographic Surveying: A Case Study of the Requirements Development Process

AbstractA long‐standing challenge in oceanography and hydrographic surveying is accurate real‐time measurement of offshore water levels. The advent of recent techniques and technologies has afforded an opportunity to address this challenge. This paper will discuss the requirement development process as it related to specifying requirements for GPS‐tracked buoy for hydrographic survey applications at the National Oceanic and Atmospheric Administration (NOAA). How stakeholders from a variety of technical disciplines collaborated to develop requirements to meet and solve an important operational need via a Small Business Innovation Research (SBIR) grant will be explored.

6.2.2 Application of Computer Aided Systems Engineering Processes for Korea Next‐Generation High Speed Railway Train

AbstractA high‐speed rail system represents a typical example of large‐scale multi‐disciplinary systems, consisting of subsystems such as train, electrical hardware, electronics, control, information, communication, civil technology etc. The system design and acquisition data of the large‐scale system must be the subject under strict configuration control and management. Not only the requirements dictate the contracts with the suppliers but also become the basis for the development process, project execution, system integration, and testing. The requirements database provide the system design specification of all development activities. Using the RDD‐100, a systems engineering tool, the korea next‐generation high‐speed rail program can establish requirements traceability and development process management in performing the enabling train technology development projects. This paper presents results from a computer‐aided systems engineering application to the Korea next‐generation high‐ speed railway project. Especially, the focus of the study was on requirement management, PBS management, verfication management and project management.

Understanding the requirements for developing open source software systems

This study presents an initial set of findings from an empirical study of social processes, technical system configurations, organisational contexts and interrelationships that give rise to open software. The focus is directed at understanding the requirements for open software development efforts, and how the development of these requirements differs from those traditional to software engineering and requirements engineering. Four open software development communities are described, examined and compared to help discover what these differences may be. Eight kinds of software informalisms are found to play a critical role in the elicitation, analysis, specification, validation and management of requirements for developing open software systems. Subsequently, understanding the roles these software informalisms take in a new formulation of the requirements development process for open source software is the focus of this study. This focus enables the consideration of a reformulation of the requirements engineering process and its associated artefacts, or (in)formalisms, to better account for the requirements for developing open source software systems.

Organizational and social simulation of a software requirements development process

This paper provides one example of how simulation can address real-world software processes. It focuses on requirements development since this early activity is crucial to the success of any software project. The model not only explores the organizational issues of requirements development but also the social issues, namely, how does the effectiveness of ‘people interactions’ affect the resulting quality and timeliness of the output. Copyright © 2000 John Wiley & Sons Ltd

Organizational and social simulation of a software requirements development process

This paper provides one example of how simulation can address real-world software processes. It focuses on requirements development since this early activity is crucial to the success of any software project. The model not only explores the organizational issues of requirements development but also the social issues, namely, how does the effectiveness of ‘people interactions’ affect the resulting quality and timeliness of the output. Copyright © 2000 John Wiley & Sons Ltd