In this paper the enslavements between requirements and architectural

In 11 the authors from Laboratoire de génie logiciel
École Polytechnique de Montréal Montréal, Canada has presented quality
evaluation methodologies for specific domains or specific techniques. Normally
the software product developers  select a
pre-defined model, customize the features, define the metrics and estimate the
quality of the software product. But in this paper the authors presents a
bottom-up methodology for the quality estimate process. Also a methodology
designed and proposed for expected quality profile. Primarily, the first step
is listening to the users, and then retrieving the most important quality
factors and creating a model to evaluate the expected quality of the project.
The profile is formed by producing the expected users’ quality expectations,
and then quantifying the elicited factors by applying them to our quality
evaluation model and the ISO/IEC 25000 standard.

 

In 12 the authors have presented the mechanism of how
software engineering capabilities relate to the business performance. They have
proposed a structural model including the Software Engineering Excellence
indicator which consisted of deliverables, project management, quality
assurance, process improvement, research and development, human resource development
and customer contact.

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

 

In 13 the component based software development approach
is discussed and demonstrated. Authors have proposed quality assurance model
for component based software development which includes requirement
elicitation, design development, certification, customization, integration,
testing and maintenance.

 

In 14 the author has shared how NASA’s Johnson Space
Center developed a ‘statistical method’ to determine sample size for the number
of process tasks to be audited by SQA. The goal of this work is to produce a
high quality product which is cost effective.

 

In 15 this paper the enslavements between requirements
and architectural components are discussed so that software defects can be
mitigated.

 

In 16 authors have said that technological choices are
fundamental for project planning, resource allocation, and quality of the final
software product. For analysis they have taken open source web applications
available in SourceForge. Authors aim to provide tools to support project
managers. They have said that there is need to set thumb rule to guide
technological choices to increase the quality of software artifacts.

 

In 17, the authors have introduced the
evolution of software quality model standards and the facts of SQuaRE series
standards. The deficiencies of ISO/IEC 2502n software quality measurement
series standards were analyzed and a road map of new reference model is
proposed.

 

This paper 18
is related to software product quality modelling and measurement. The outcome
of the research is grouped as system-level software quality models, source code
element-level software quality models and applications of the proposed quality
models.