What is the purpose of process assessment? Why has spice
been developed as a standard for process assessment?
- 1 Answers
- 8546 Views
- I also Faced
- E-Mail Answers
Answer Posted / sevak.yatrik777
SPICE provides a set of documents, which are used as a
framework for the assessment of software process.
Organizations can use these documents in various phases of
production, for example in planning, managing, monitoring,
controlling and improving acquisition, supply, development,
operation, evolution and support of software.
Basically software process assessment examines the selected
processes whether they are effective in achieving their
goals, which is done by determining the capability of the
selected processes. This structured approach for software
process assessment helps an organization to improve its
processes or to determine its capability for certain
requirement, or to determine suppliers capability for
certain requirement.
Process assessment provides information of the capability of
the selected processes. Analysis results, from business
point of view, identify strengths, weakness and risks
inherent in the processes. By this, analysers are able to
determine whether the processes are effective, and to
identify significant causes of poor quality, or over runs in
time or cost. After recognizing these kinds of issues,
managers can prioritise improvements to processes .
Process capability determination analyses the proposed
capability of selected processes against a target process
capability profile. By this, it tries to find out the risks
involved in a project, if the project is run with the
analysed processes .
The document suite of SPICE contains nine different
documents, which can be used in process assessment. These
documents will be shortly described in the following sub
chapters.
SPICE documents from 1 to 6 mainly concentrate in addressing
various aspects related to process assessment. Other
documents, 7 and 8, address the use of process assessment
for process improvement or for process capability
determination. Document 9 acts as a vocabulary .
| Is This Answer Correct ? | 4 Yes | 2 No |
Post New Answer View All Answers
Give a suitable definition of software quality and briefly describe the rationale for your definition.
Why is it that a single, all – encompassing metric cannot be developed for programme complexity or programme quality?
explain the basic QA plan to co-op with development plan for effective delivery of the product
What are ‘throwaway’ prototypes and ‘evolutionary’ prototypes? How can production of a prototype be controlled and why is this important?
How you test a Pen?
Explain the architecture diagram of your current project?
what are the usual metrics one have to apply for SW improvement projects
what are the expectations of QA from unit level testing
explain the model(s) of co-ordination you experienced for effective delivery of the product
what is regression testing, how effectively the QA lead / manager can implement this for product qualification
Explain the main differences between software review and software inspection or walkthrough
brief about the methodologies to evaluate weightage of test cases and what are the basic parameters to be considered
As soon as you get a build ,what would you ask your testing team to do?
Explain the deployment process?
Explain waterfall model? what will the testing team do in Requirement phase in this model and what happens in design phase?
