A Comparative Study of Software Inspection Techniques for Quality Perspective

Qazi, Asad Masood; Shahzadi, Sidra; Humayun, Mamoona

doi:10.5815/ijmecs.2016.10.02

Cited by 8 publications

(4 citation statements)

References 36 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Inspection is a method used to identify defects with lower cost during the development process [17]. According to Qazi et al [18], the main purpose of an inspection is to identify defects to reduce costs and improve software quality.…”

Section: Redundantmentioning

confidence: 99%

ComD2: Family of Techniques for Inspecting Defects in Models that Affect Team Communication

Lopes

Campos

Conte

et al. 2018

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Communication failures in software development teams can compromise the software quality. Therefore, identifying and mitigating risks for effective team communication are important activities in software development. Software models are one of the means of communication in development teams, because it communicates other members of the development team about the software. Thus, our research focuses on inspection techniques for identifying defects that affect the team communication through the software models. This paper presents a family of techniques for inspecting defects that affect team communication, called ComD2 (Communication between Designers and Developers). The ComD2 family was developed based on theories that investigate different ways of communication. For the time being, the ComD2 family has three specific inspection techniques for UML models, such as class diagrams, activity diagrams, and state machine diagrams. We performed a feasibility study and the results showed that the ComD2 family was considered useful for the identification of defects that affect the team communication through the software models.

show abstract

Section: Redundantmentioning

confidence: 99%

ComD2: Family of Techniques for Inspecting Defects in Models that Affect Team Communication

Lopes

Campos

Conte

et al. 2018

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

show abstract

“…In the pressure of getting the products to the market ahead of the competitors, the start-ups consider quality assurance a less essential component of software development, which leads to frequent mishaps because of software failure or errors [18,19].…”

Section: Introductionmentioning

confidence: 99%

Start-up failures due to Quality Failures

Aleem¹,

Santosh²,

Mahmood³

2021

IJEM

View full text Add to dashboard Cite

Software start-ups are fundamentally different from traditional software development firms and boutique software services enterprises of all sizes. They develop software products with strict time and resource constraints and are focused on beating competitors to the market. They fail fast and often pivot their business models several times in their lifetimes. Their approach to designing, developing, testing, and shipping software products differs vastly from the established software engineering principles that emerged during the field"s earlier decades. One such principle is Software Quality Assurance. Start-ups tend to do away with procedures that ensure that their products are of the utmost quality. Instead, they focus on shipping their products to market as fast as possible, testing these products vis-a-vis reallife customers and use-cases, and eventually improving these products, repeating the process several times over. We hypothesize that this reluctance to adhere to software quality assurance principles can have adverse effects on the health of start-ups or their products. This paper investigates this hypothesis through over 20 questions presented to CEOs, CTOs, Technical Leads, and Product Managers of several start-ups. These questions focus on start-ups" motivations, their levels of understanding and appreciation of software quality assurance principles, and the limitations they face due to time and resource constraints. Our research"s results indicate the surveyed start-ups" problems are partially due to the absence of robust software quality assurance practices within their processes.

show abstract

“…The checklist consists of three major methodologies, internal governance, project management knowledge areas [2] and ERP (i.e. processes, products and services [5]) implementation methodology since ERP implementation faces many difficulties that cause its failure [26], [27].…”

Section: Related Workmentioning

confidence: 99%

Use of Project Management Information System to Initiate the Quality Gate Process for ERP Implementation

Taniguchi¹,

Onosato²

2017

IJITCS

View full text Add to dashboard Cite

Abstract-Non-conformance to quality in a project often can lead to a major reason for project failure resulted in not meeting the triple constraints of project management, scope, time and cost. To prevent it from happening, a quality check against the standard for quality needs to be conducted at the critical stages of ERP implementation project. Proactive quality management by the quality gate process is embedded in the implementation methodology to help secure quality outcomes for the customers. However, getting the schedule of each quality gate timely fixed by the independent quality reviewer with the project manager of a newly started project can often be problematic without having a systematic approach implemented. Recent research has provided an application with the use of project management information systems (PMIS) for such implementations in improvement of quality management systems requirements [1]. This article describes how PMIS was used to implement the project quality gate process for ERP implementation projects conducted by the solution provider for their customers in the various industries in Japan. PMIS was found to be effective in identifying, notifying and influencing the project managers to timely initiate the quality gate process based on the schedule fixed for each quality gate review.

show abstract

A Comparative Study of Software Inspection Techniques for Quality Perspective

Cited by 8 publications

References 36 publications

ComD2: Family of Techniques for Inspecting Defects in Models that Affect Team Communication

ComD2: Family of Techniques for Inspecting Defects in Models that Affect Team Communication

Start-up failures due to Quality Failures

Use of Project Management Information System to Initiate the Quality Gate Process for ERP Implementation

Contact Info

Product

Resources

About