Download
1 / 8
80 likes | 191 Views
This article explores how to ensure quality in software development through effective requirement assessment in iterative processes. Quality in software is defined as achieving conformance to requirements, and it is essential to meet the expectations of users and stakeholders. By examining the outputs of each iteration and asking critical questions, teams can gauge if they are meeting agreed-upon standards. The article emphasizes that quality is multidimensional, impacting both the end product and the broader business context. Learn how to apply these principles to improve project outcomes.
E N D
How Does One Go about Achieving Quality? • The very nature of the thing we produce, source code, models, and other artifacts, is intangible. • We must assure that the thing produced has the requisite quality to meet the needs of the users and extended stakeholders. • REQUIREMENTS QUALITY DRIVES SYSTEM QUALITY.
Software Project Quality • “Quality is conformance to requirements” • “Quality is achieved when the software is ‘good enough’” • “Quality is ultimately situational and objective” • “Quality is the characteristic of having demonstrated the achievement of producing a product that meets or exceeds agreed-upon requirements – as measured by agreed-upon measures and criteria – and that is produced by an agreed-upon process” [Rational Software Corporation 2002]
Software Project Quality (Cont’d) • Quality is a multidimensional concept that address two primary dimensions: • The end result of the application itself • The business impact on the producer and consumer • What we have studied in this course is how to effectively manage requirements to help the development team assure that the product or system being developed meets or exceeds agreed-on requirements and to apply an agreed-on process to help assure that those results are achieved.
Assessing Quality in Iterative Development • When we complete the delivery of an iteration we can ask the following questions: • “Does it do what we said it would do?” • “Does is appear to meet the requirements as we know them at this time?” • “Did we do it about when we said we would?” • Now that you can see a bit of this thing, is this what you really wanted? Is this what you really meant?” • We can look at the artifacts of the process and inspect them for quality as well. These artifacts demonstrate that the process is being followed as well.
Performing the Assessment • We have already put in place an iterative process whereby the objective evidence of the iterations themselves are the primary quality measures. • We can apply secondary measures by assessing each of the requirements artifacts at each iteration, or at any iteration we choose, by looking at the various aspects of quality that each artifact should contain at that point in the development process.
