Software Requirements Process Research Articles

A Novel Automated Requirements Prioritization and Selection Model Based on Requirements Weights and Stakeholder Importance

This paper proposes a novel approach to select and prioritize the requirement items in the requirement document. We use an automated requirement method that collects requirements from different stakeholders groups and categories. The new approach is based on assigning an importance factor to each stakeholder group and an acceptance weight for each requirement item. The importance factor and the acceptance weight for each requirement are used to decide whether to include or exclude this requirement item based on a proposed formula. This method is validated by using a case study based on a set of examples, and shows a significant improvement in software requirements process.

The software requirements process for designing a microcontroller-based voice-controlled system

Smartphones of today are capable of controlling motors, music systems, and lighting. This project's objective is to construct a robot car for the elderly and disabled that is based on the Arduino platform. Voice instructions can be used to wirelessly control the robotic car that the user is riding. The robot is able to move to the left and right, as well as forward and backward, and it can also stop. The voice-controlled robot vehicle built using Arduino and operated by an HC-05 module is connected to Bluetooth. The exact spoken commands are sent to the robot through the phone via an application that runs on android. The Arduino, which is in charge of controlling the robotic automobile, gets commands through a Bluetooth transceiver module, which then relays them to the Arduino. The hardware consists of an android phone, an android-powered motor drive, an Arduino, and Bluetooth. This system was developed with the help of Arduino C and the android-meets-robot framework. The primary goals of this piece of writing are to gain an understanding of how to create the criteria for a voice-controlled system that is based on Arduino.

Online Application of Hotel Point of Sales: System Development Life Cycle of the Wing Ed Hotel of the Bali State Polytechnic

Purpose: This research aims to design and develop a web-based application, which will make it easier, faster and accurate for the hotel management both in operations and hotel supervision. The application also has the advantage of being able to be accessed all the time from all points in the world with various media. Method: The development of this application is carried out using the Waterfall method, which is a sequential and systematic software development method consisting of analysis, design, coding, and testing. The analysis is the process of gathering software requirements. Design is a software design process. Encoding is the process of translating designs into a form that can be read and done by a computer. Testing is the process of testing the results of coding to ensure results are free from error and according to what is needed. Result: Online Point of Sales Application at The Wing Ed Hotel Bali State Polytechnic provides facilities in accordance with business fields and user authority as follows: Manager, Front Office Officers, Restaurant Officer, and Laundry Officer. All transactions carried out on each business field have been integrated and processed automatically to produce fast, easy and accurate information at the hotel point of sales. This has fulfilled the needs of the hotel revenue information system as planned previously. Novelty: Produce online applications that simplify and speed up hotel operations because the entire process has been done automatically.

Optimization of software requirement process: An integrated conceptual model of lean six sigma and requirement planning

Providing quality requirements in Software Engineering is vital to ensure the product developed is able to deploy and function to meet the operational objectives. Software Requirement Engineering is the most complex process because it involves the integration of human, logics and process. Extracting or capturing what customers need and want is called Requirement Elicitation (RE) and it is the most crucial process in requirement engineering. If handled poorly, the cost of the failures would be very expensive. Most of the software projects that failed were due to poor requirements which occurred at RE phase. Thus, enhancing and optimizing the RE methods have been subject to a long research debate to ensure quality requirements are captured. Recently, Lean Six Sigma (LSS) had emerged as part of a continuous improvement in Software Development Life Cycles (SDLC). LSS is known for a systematic and structure business improvement successfully deployed in many fields of industry that contributes a significant gain not only in quality of products and services but also in operational costs and delivery. The objective of the research is to develop an integrated conceptual framework of LSS principles with Software Requirement Engineering methodology to optimize RE process. The article will produce conceptual framework as the comprehensive guidelines to capture quality software requirements.

Improved Software Requirement process for Software Industries

In the software system development, requirement engineering plays a great role because system successfulness depends on it. If the requirements are clear and unambiguous in every aspect then the system will be developed error free. A number of clients that are not educated and illiterate, then in this scenario, the given requirements are not clear and full of ambiguous. In this paper, we proposed a method to resolve this problem in the shape of break the requirements, filter it (separate the necessary and un-necessary requirements), break into little bits, numbering them and prioritize them, after it is documented, the requirement that is very helpful for current and future changing in software system and finally shift to the development team for develop the project. We will apply this proposed method on case study as experimental to find out the definite and relevant results.

Особливості управління процесом розроблення вимог до програмного забезпечення

Наведено технологічні особливості управління процесами розроблення вимог до ПЗ та внесення змін до них, методи і засоби яких дають змогу проконтролювати стан їхнього виконання та встановити статус кожної з вимог протягом усіх етапів реалізації програмного проекту. Проаналізовано основні поняття про план виконання завдань програмного проекту та управління процесом його реалізації, що допомогло зрозуміти суть пропонованих методів і засобів здійснення контролю за станом виконання кожного із завдань та відстеження їхнього статусу на усіх етапах реалізації програмного проекту. Виявлено проблеми, які виникають під час управління процесом розроблення вимог до ПЗ, що дає змогу запобігти непередбачені втрати і неприємні інциденти, які можуть виникнути на деяких етапах реалізації програмного проекту. З'ясовано, що більшість виявлених проблем пов'язані насамперед з: плануванням послідовності виконання робіт; контролем за станом виконання робіт; управлінням змінами вимог до ПЗ; відстеженням статусу кожної вимоги. Характер проблем, з якими стикаються IT-компанії при управлінні вимогами до ПЗ, залежить також і від специфіки їхньої діяльності. Досліджено деякі особливості управління вимогами до ПЗ в процесі діяльності компанії його замовника, виконавця та виробника, що дає змогу своєчасно підготувати відповідні плани виконання завдань програмного проекту та ефективно управляти процесом їх реалізації. Встановлено, що на початкових етапах розроблення користувацьких вимог до ПЗ процедура внесення змін має мати незначний ступінь формалізації, яка повинна постійно збільшуватися в міру просування етапів реалізації програмного проекту. Зроблено відповідні висновки та надано рекомендації щодо практичного використання запропонованих методів і засобів управління процесом розроблення вимог до ПЗ.

Propuesta de Modelo de Proceso de Ingeniería Distribuida de Requisitos de Software

Los escenarios de Desarrollo Global de Software, donde los actores del proceso están dispersos geográficamente, crecen a diario en muchas partes del mundo, incluso en Latinoamérica. Este nuevo entorno impacta sobre el desempeño de los métodos y las herramientas usadas en los procesos tradicionales de desarrollo de software. Debido al alto flujo de comunicación humana que requiere, el proceso de ingeniería de requisitos es fuertemente afectado por las características particulares de estos nuevos escenarios globales. Basado en estudios experimentales, este artículo presenta un modelo de proceso de ingeniería de requisitos para desarrollo de software distribuido que contempla tanto técnicas de elicitación como así también herramientas de comunicación.

Requirements Association Extraction based on Use Cases Diagram

Requirements are the initial step in the software development process. It is very important to ensure the association (relationship) of requirements and high quality of specification as more than three-quarters failure of software derives from the software requirement process. Therefore, the analysis process is required to ensure the association between requirements and the requirements of other users. As a result, interdependency requirements association is essential. This research proposes an approach of software requirements association. These are based on the reference of interdependency in the user case, namely the result of collaboration of the association of the dependency of requirements based on Unified Modeling Language (UML) design in the Use cases diagram. In this research, the mapping between requirements and use cases and interdependencies between use cases are used to determine the interdependency between requirements. The analysis presented is the association of similar requirements, requires, or, temporal, elaborates dan generalises. The purpose of this research is to generate a requirements dependency graph that models the type of dependency between requirements within a software project.

A proposed Framework for Software Process Improvement: Extending CMMI-DEV model Using Six Sigma and Quality Function Deployment Techniques

Software Process Improvement (SPI) has become the key to the survival of many software development organizations. Many international SPI models/standards, such as; ISO, Capability Maturity Model Integrated (CMMI), SPICE, Trillium…etc, are developed for SPI. Numerous software development companies have chosen to utilize CMMI to access and improve their current software development process, because CMMI is one of the most widespread and acknowledged SPI models. Unfortunately, CMMI does not provide a systematic way of determining to improve the process. That is, CMMI defines what to but leaving how to do to organizations. Thus, it is desirable to have a means to guide the companies in the development of action plans and appropriate tools for SPI. These actions should be based on the software process requirements from relevant sources. Therefore, this research proposes a SPI-CMMI framework that provides an overall process improvement strategy to be implemented in any software development organization more effectively and comprehensively. The proposed model based on applying assessment and improvement procedures through adopting the CMMI-DEV 1.3 model using six sigma approach and Quality Function Deployment (QFD) technique.

Exploring the Educational Needs of Learners in the View of Software Engineering

Software requirements in software engineering link software and hardware, and link users and developers. It is the key process of software engineering. In this paper, the view of software engineering to analyze education, through in-depth analysis of each process of software requirements, the content of education needs and the process of obtain for a deep thinking and consummation.

Manufacturing Execution Systems And A Sectoral Application

<p class="KeywordsText"> Information systems have widespread usage on Manufacturing Systems. Most companies need tracking production processes with information systems to become prominent in highly competitive environment. There are some specific metrics need to be followed and important to access these datas on time and also should be reliable. These metrics include all manufacturing and quality processes. In this context; efficiency, line stoppages, malfunction and interruptions, body and supplied part trace ability informations are needed. This study MES (Manufacturing Execution Systems) is the system developed for tracking production processes. MES is working from receipt of order to delivery of the product that are the essentials for the production activities to achieve real time status of all manufacturing data. In this way, all information which not manually recorded or takes long process time to record or can be tracked instantaneously and these records can be reached and analyzed in the future. The system also provides accurate data for us. In this study all phases from design to implementation of an automotive subindustry firm’s MES application designed based on integrated software process requirements are depicted. Relevant system’s integrated software will be implemented to Module Line. This study will allow tracking related product’s all process, decision making and traceability data with serial numbers.</p>

Dealing with software process requirements complexity: an information access proposal based on semantic technologies

Organizations developing software for critical sectors like aerospace, automotive, and medical systems need to apply process requirements coming from different sources: industrial standards, customer-provided requirements, and procedures from internal quality management systems. In these situations, software teams need to deal with complex sets of process requirements that govern different aspects of their work. This paper describes the development of a collaborative, web-based solution to improve access to process requirements. The solution makes use of semantic technologies to handle the context of process requirement. Requirements are contextualized by linking them to activities, tasks, and work products. With this tool, software engineers have a single point of access to all the applicable process requirements, avoiding the risk of missing relevant information.

A control model of the software requirements process

PurposeMany project failures can be attributed to changes in requirements as the project progresses. The purpose of this paper is to review several system dynamics models of the requirements process from the literature, especially the model of Andersson and Karlsson. This model addresses the deficiencies in the system dynamics model devised hitherto to create a model than can be used to predict requirements acquisition and staff resources for different levels of project complexity and size.Design/methodology/approachA new control‐theoretic model of requirements gathering is devised using the Software Test Model of Cangussu as a framework. Conventional control system techniques are then used to compute typical responses.FindingsThe results agree with the limited published data. This model can be used to predict an estimate of the possible number of requirements that could be devised for the project. It allows the incorporation of workforce, quality and complexity information to predict the time to complete the requirements process. This model is then used to predict how the requirements process responds to requirements creep and to changes in workforce used.Research limitations/implicationsThis model is theoretical and is proposed so that it can be simple tested. It makes a number of assumptions not yet recorded by industry that would have to be obtained.Practical implicationsIf it is supported by experimental data then a better project development model can be created with the prospect of greater control of project development.Originality/valueThis work, although based on the work of Cangussu et al., is devised by the author.

Quality evaluation modeling of requirements analysis based on chaos

Based on the research of chaos and software requirements complexity theory,a theory model was proposed. The model was a trajectory graph consisting of three segments obtained under the described nonlinear equation,and it could guide the evolution process of software requirements,evaluate the quality of requirements process as well. The primary research shows that the evolution process of requirements can be regarded as normal when the requirements evolutionary process changing chart is consistent with the model trajectory. In the end,the efficiency and feasibility of this model on estimating requirements evolutionary process are testified by a specific example.

Multimodal Modeling, Analysis, and Validation of Open Source Software Development Processes

Understanding the context, structure, activities, and content of software development processes found in practice has been and remains a challenging problem. In the world of free/open source software development (F/OSSD), discovering and understanding what processes are used in particular projects is important in determining how they are similar to or different from those advocated by the software engineering community. Prior studies have revealed that development processes in F/OSSD projects are different in a number of ways. In this article, we describe how a variety of modeling perspectives and techniques are used to elicit, analyze, and validate software development processes found in F/OSSD projects, with examples drawn from studies of the software requirements process found in the NetBeans.org project.

A requirements engineering environment for embedded real-time software—SREE

The paper presents the embedded real-time soft-ware-oriented requirements engineering environment SREE. It involves the whole process of software requirements engineering, including the definition, analysis and checking of requirements specifications. We first explain the principles of the executable specification language RTRSM. Subsequently, we introduce the main functions of SREE, illustrate the methods and techniques of checking requirements specifications, especially how to perform simulation execution, combining prototyping method with RTRSM and animated representations. At last, we compare the SREE with other requirements specifications methods and make a summary for SREE's advantages.

Priority assessment of software process requirements from multiple perspectives

The improvement of software processes involves the collection of software process requirements from various groups of stakeholders – each having their own perception of the process. Often stakeholders specify similar requirements in different ways. This results in the fact that different perceptions are related to each other. An effective technique is needed to incorporate the relationships between various stakeholders’ process requirements. This paper presents a Correlation-Based Priority Assessment framework (CBPA), which prioritizes software process requirements gathered from multiple stakeholders by incorporating inter-perspective relationships of requirements. This research uses a relationship matrix to analyze the impacts between requirements and to facilitate the integration. Higher stakeholder satisfaction is achieved by increasing the priorities of the software process requirements whose satisfaction can increase the satisfaction of other requirements from multiple perspectives.

Achieving high integrity at low cost: a constructive approach

The paper presents a development process, delivering high-quality software at exceptionally low cost, and its application to the mission computer software for the new Lockheed C-130J (Hercules) aircraft. For this safety-critical application, the software process requirements were: • a rigorously verified, error-free end product, right first time, • modularity, portability, ease of functional modification and extension of software components, essential for an aircraft with a long life, • rapid, low-cost development. These aims were met by investing in “correctness by construction”: • integration of the US Software Productivity Consortium's CoRE requirements expression method, the graphical Domain-Specific Design Language (DSDL), and multi-level design in Ada to strict rules, enforced by templates and mechanical checks, • use of SPARK Ada, allowing mechanical code verification against CoRE specifications. Large savings in V & V were achieved, through: • reduced cost of testing to DO-178B Level A requirements, and • mechanisation of semantic analysis (as required by MoD).