Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...

What is the purpose of process assessment? Why has spice
been developed as a standard for process assessment?

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


Please Help Members By Posting Answers For Below Questions

What are the negative test cases for water bottle?

2326


How would you know if the same build you tested is deployed in production? There are chances that developer might deploy some other working build?

1545


is all the test cases to be automized !!! if yes / no let explain the reason

2013


Why should an organisation be concerned about software risk factors and software quality?

848


How would you finalize on testcases in estimation? Say you have 200 requirements. How would you come up how many testcases you are going to write for each requirements?

1515


I am looking for interview question / technical questions for veritas netbackup.

1970


what is the difference between testing and quality analysis

1971


hi can anyone provoide SRS for order processing system and intranet plz

2559


is QA expects any level of interaction from development engineer !!!

2012


Explain waterfall model? what will the testing team do in Requirement phase in this model and what happens in design phase?

1518


how to test the application/software without any requirements(like BRD,FRD etc.,) for a new project?

2580


Explain the architecture diagram of your current project?

1623


what are the expectations of QA from unit level testing

1993


How would you do an Estimation?

1630


explain the basic QA plan to co-op with development plan for effective delivery of the product

1895