RISDM: A requirements inspection systems design methodology: Perspective-based design of the pragmatic quality model and question set to SRS

Saito, Shinobu; Takeuchi, Mutsuki; Yamada, S.; Aoyama, Mikio

doi:10.1109/re.2014.6912264

Cited by 7 publications

(5 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Such common defect types existing in the literature occurs in the studies of Anda and Sjøberg (2002;Belgamo et al, 2005;Mello et al, 2010;Alshazly et al, 2014;Saito et al, 2014;Naveed and Ikram, 2015;Langenfeld et al, 2016). The Lopes et al (2015) is another study (non-evidenced) that also addresses the Engineering Requirements domain and such defect types.…”

Section: Research Question 1 (Rq1a and Rq1b)mentioning

confidence: 96%

“…Continue Felderer et al (2014) On the role of defect taxonomy types for testin 2014 IEEE Xplore requirements: Results of a controlled experiment Rodriguez et al (2014) Preliminary comparison of techniques for dealing with 2014 ACM Digital Library imbalance in software defect prediction Femmer et al (2014) Rapid requirements checks with requirements smells: 2014 ACM Digital Library Two case studies Yusop et al (2016) Reporting usability defects: Do reporters report what 2016 ACM Digital Library software developers need? Cavezza et al (2014) Reproducibility of environment-dependent software 2014 IEEE Xplore failures: An experience report Langenfeld et al (2016) Requirements defects over a project lifetime: An 2016 Compendex SpringerLink empirical analysis of defect data from a 5-year automotive project at bosch Saito et al (2014) RISDM: A requirements inspection systems design 2014 IEEE Xplore methodology -perspective-based design of the pragmatic quality model and question set to SRS Travassos (2014) Software defects: Stay away from them. Do inspections!…”

Section: Data Sources X Rqs X Research Typesmentioning

confidence: 99%

“…Anda and Sjøberg (2002) Saito et al (2014) proposed RISDM (Requirements Inspection System Design Methodology) a technique set based on the PQM (Pragmatic Quality Model) and PBR. In such paper, it was analyzed more than 140 projects of NTT DATA for five years.…”

Section: Research Question 1 (Rq1a and Rq1b)mentioning

confidence: 99%

See 2 more Smart Citations

Defect Types and Software Inspection Techniques: A Systematic Mapping Study

OliveiraJr¹,

Geraldi²

2017

Journal of Computer Science

View full text Add to dashboard Cite

Software inspection has been used to guarantee and control the quality of products by detecting defects, which can be spread out throughout the entire software life cycle. Therefore, the main premise is to identify and reduce the number of defect types in software artifacts during inspections. This work focuses on providing an up to dated overview of existing defects in the context of software inspection techniques. A systematic mapping was carried out, from which 2096 primary studies were retrieved and 32 were final selected. From the analysis, classification and aggregation of the retrieved studies, important different defect types were identified. Most studies encompass defect types by means of experiments and proposed techniques and approaches. Thus, as a main result, the identification of several different studies with distinct proposals concerned on defect types is evident. Although researchers have conducted studies over time, a general pattern on the detection of defects could not be established. Therefore, the scenario in which this study was carried out provides researchers with the capability of conducting further research in a motivating and challenging research topic, as well as practitioners with the adoption of empirically evaluated inspection techniques and respective defect types.

show abstract

Section: Research Question 1 (Rq1a and Rq1b)mentioning

confidence: 96%

Section: Data Sources X Rqs X Research Typesmentioning

confidence: 99%

See 1 more Smart Citation

Defect Types and Software Inspection Techniques: A Systematic Mapping Study

OliveiraJr¹,

Geraldi²

2017

Journal of Computer Science

View full text Add to dashboard Cite

show abstract

“…Saito et al stated the success of software development always depend on the quality of the SRS. They applied some statistics and discovered that the quality characteristics in SRS shows very strong correlation to the project cost and quality levels are used to evaluate the maturity of SRS [30]. Faisal et al described that during system development, volatile requirements are always considered as a main factor.…”

Section: Literature Reviewmentioning

confidence: 99%

Fagan Inspection: A Defects Finding Mechanism in Software Requirements Specification (SRS) Document

Yousaf,

Ali,

Nawaz

et al. 2022

VFAST trans. softw. eng.

View full text Add to dashboard Cite

The preparation of Software Requirement Specification (SRS) document is a critical task as the successful completion of software depends heavely upon the SRS. The requirements gathering phase in Software Development Life Cycle SDLC is equally important as it witnesses the creation of an SRS document. The quality of an SRS document is dubious as there is a scarcity of proficient inspection methods for detecting the defects in the software. There are various reading based inspection techniques such as Checklist Based Reading technique (CBR), Defect Based Reading technique (DBR) and Perspective Based Reading technique (PBR). There are certain problems with these techniques such as the CBR only covers potential types of defects, The DBR focused on various defects but the problem is that it is not structured in nature. Likewise, PBR is not suitable as it mainly focused on use-cases. As owing to the absence of a suitable inspection technique, the main focus of this study is to highlight the Fagan based inspection technique. This technique is not only formal and lightweight but it also overcome the limitations of reading base d techniques. The Fagan is a structured approach and finds defects in specification, programming code, design and also others during the SDLC. During analysis a questionnaire based survey is conducted in almost 300 national and international software industries. As a result, 150 responses are received. The likert scale is used for developing the questionnaire. SPSS tool is also utilized for data entry and analysis. The consequences are drawn by developing hypothesis and using the Chi-square test. More satisfactory results are gained at international level than at the national level. The satisfaction level of defect detection is 59.2%, time saved is 48.3% and cost reduction is 40.0%. Thus, the obtained outcome is positive and satisfies the requirements.

show abstract

“…More specifically, [12][13][14][15][16][17] proposed different design frameworks to integrate user experience design into the software development cycle. In [18] RISDM ("Requirements Inspection Systems Design Methodology") is proposed to design the RIS ("Requirements Inspection System") to be conducted by a third party inspection team. Furthermore, [19] proposed a methodology for improving agile processes based on CMMI, this achieves by defining improvement on the GQM approach, that allow precise and intentional selection of CMMI practices.…”

Section: Introductionmentioning

confidence: 99%

A sustainable procedural method of software design process improvements

Al-Sarayreh

Meridji

Alenezi

et al. 2021

IJEECS

View full text Add to dashboard Cite

In practice, the software process is an intermediate phase for enhancement and improvements the design for different types of software products and help developers to converts the specified requirements into prototypes that implement the design into reality. The objective of this paper is to provide software developers, designers and software engineers who work in small companies with a standards-based process improvement using a procedural method technique including detailed steps for designing the small software systems into their companies. The method used in this paper includes 1) analysis four different types of commonly design processes used by industry such as CMMI, conventional or software process in ISO 19759, generic and engineering design processes. 2) mapping between those four design processes. 3) collect the dispersed design concepts proposed by those four processes. 4) proposed a sustainable procedural method of software design process improvements 5) Illustration of the applicability of the proposed approach using A template-based implementation. The primary result of this study is a guideline procedure with detailed steps for software design process improvements to help and guide developers in small companies to analyze and design a small software scales with limited cost and duration. In conclusion, this paper proposed a method to improve the design process for different kinds of the software systems using a template-based implementation to reduce the cost, effort and time needed in the implementation phase in small companies. The scientific implication behind a template-based implementation helps the system and software engineering to use this template easily in their small companies; because most of the time those engineering developers are responsible for analyzing, designing, implementing and testing their software systems during the whole software life cycle.

show abstract

RISDM: A requirements inspection systems design methodology: Perspective-based design of the pragmatic quality model and question set to SRS

Cited by 7 publications

References 18 publications

Defect Types and Software Inspection Techniques: A Systematic Mapping Study

Defect Types and Software Inspection Techniques: A Systematic Mapping Study

Fagan Inspection: A Defects Finding Mechanism in Software Requirements Specification (SRS) Document

A sustainable procedural method of software design process improvements

Contact Info

Product

Resources

About