Capture Software Design Rationale Based on an Integrated Analysis of Both Software Process and Product Quality Requirements from Multiple Perspectives

Abstract

The capture of design rationale in terms of the process and product quality requirements for a software system from different perspectives in concurrent engineering poses two challenges (1) process and product quality requirements arising from different perspectives usually conflict with each other, and (2) both process and product quality requirements are often vague and imprecise Recent research into methods for handling software quality requirements has taken one of two approaches—quantitative and qualitative Quantitative approaches are based upon software metrics and specify requirements using predicate logic Qualitative approaches represent requirements qualitatively and decompose the requirements into a hierarchy of subrequirements A unified approach for specifying and analyzing requirements quantitatively and qualitatively is also developed based on fuzzy logic However, none of these methods addresses design rationale capture based on integrated analysis of both product and process quality requirements from multiple perspectives in concurrent software development In this paper a formal framework is developed for an integrated analysis of software process and product quality requirements to support design rationale capture from

Prioritizing solution-oriented software requirements using the multiple perspective prioritization technique algorithm: An empirical investigation

“…According to the main goal of the RP, it is usually necessary to involve various stakeholders in the prioritization process. The stakeholders to be involved, for example, are project managers, developers and customers, who can hold their own viewpoints on the system (Liu and Sigman, 1997).…”

WWW-Based Collaborative System for Integrated Design and Manufacturing

“…Effective collaboration between various groups is important for reducing cost and product development time. For example, a designer could benefit greatly by discussing his design with others (including other designers, customers, and manufacturers) [3][4][5][6] during the design stage. Once errors are found by others, the designer could immediately make corrections.…”