Reflections on Choosing a New Requirements Management Tool

IEEE Software ◽  
2022 ◽  
Vol 39 (1) ◽  
pp. 7-10
Author(s):  
Michael Panis ◽  
Sarah Gregory
Author(s):  
Sara Allabar ◽  
Christian Bettinger ◽  
Michael Müllen ◽  
Georg Rock

Nowadays, industrial products as well as software applications are expected to be tailored to the user’s needs in an increasingly distinct manner. This often makes it necessary to design a vast number of customized variants, which leads to complex and error prone analysis and development processes. Generally, requirements engineering is considered to be one of the most significant activities in software and system development. Variant management has proven to play an important role in handling the complexity arising from mass-customization of products. However, there are only a few, often rather complex-to-use, applications which allow adding variance information directly to requirements. Especially in case of small and medium sized enterprises, approaches to meet this challenge often result in isolated solutions that are not driven by state-of-the-art analysis methods and do not cope with future requirements. This paper introduces a lightweight requirements management tool called scone, which will be embedded into an overall variability management methodology. scone enables the user to create and manage requirement specifications and augment them with variability information. Based on this specification, the requirements can be analyzed in a formal way with respect to their variability using the variability management tool Glencoe. scone was created as a single-page web application to eliminate the need for installation and allow it to run on many devices, while offering the experience of working with a native application, rather than a website. Both tools are designed to provide a proof of concept for the seamless integration of variability information within a system development process as well as to show how variability can be handled in an easy-to-use way from the very beginning within this process.


Author(s):  
Daniyal M Alghazzawi ◽  
Shams Tabrez Siddiqui ◽  
Mohammad Ubaidullah Bokhari ◽  
Hatem S Abu Hamatta

2021 ◽  
Author(s):  
Abe Hudson ◽  
Jim Marsh

Abstract This paper discusses the lessons learned from transforming upstream operational requirements from a document environment into a requirements management tool (database). Operations requirements from upstream practices, procedures, specifications, and guides were migrated from a document centric environment into a requirements management system (data centric). Here, requirements were assigned attributes denoting the organization and accountable operational role that requirement. Many organizations, operating complex offshore procedures, especially where operations are highly regulated, are looking to move their operational requirements from a document centric environment to a data centric environment. This paper highlights some potential pitfalls and mitigation strategies for ensuring a successful migration.


2021 ◽  
Author(s):  
Reynaldo Celestial Climacosa ◽  
Sierra Foster Matlock ◽  
Joveline Anne Ollero ◽  
David Miller

Abstract Currently oil and gas companies are spending billions of dollars on digitalization efforts. One important aspect of a project that needs to be digitized are requirements. Most oil and gas companies receive project documentation and requirements as PDF files. Receiving PDF documents make it very difficult for companies to manipulate the content to identify which parts of the document are requirements and which parts are just background information. In addition, documents that contain requirements have poorly written requirements that are ambiguous, and can have many interpretations, making it difficult to show compliance. To solve the issues caused by poorly written requirements and receiving PDF files instead of receiving requirements in a more usable format, the solution is to rewrite the requirements and use a requirements management (RM) tool to put the requirements in a database. The American Petroleum Institute (API) 17O 2nd Edition document and a representative list of High Integrity Pressure Protection System (HIPPS) product requirements are used to show the benefits of using a requirements management tool. This paper will describe the prerequisites prior to selecting an RM tool, show how using a requirements quality analyzer tool can aid in preparing requirements to be imported into an RM tool, demonstrate the main benefits of using an RM tool in a project context, and discuss lessons learned from adding an RM tool to a document-based project.


Sign in / Sign up

Export Citation Format

Share Document