Verification Techniques

-

Different Verification Techniques 

Verification: Verification is the process of evaluating work-products of a development phase to determine whether they meet the specified requirements. verification ensures that the product is built according to the requirements and design specifications.

 There are three types of Techniques 

1.Walkthrough
2.Inspection 
3.Review




1.Walkthrough: walkthrough is an informal process, and is initiated and led by the author of the software work product. The colleague observes the document and gives their required feedback of assistance in location defects or suggestion for improvements. 

2.Inspection: inspection is a semi-formal process. It is usually done by domain experts. Inspection is more formal than a walkthrough.

There are five major roles: 
1.Moderator
2.Inspector
3.Author
4.Reader
5.Recorder

Moderator: moderator is the activity leader and the person responsible to ensure the discussions proceed on the production lines.

Inspector: inspector is the domain expert and all of the inspection team members who analyze and detect the defects within the work product.

Author: the author who originally created the work product and whose product is under inspection.

Reader: the reader is the read the whole work product for the entire inspection team.

Recorder: recorder who records all the defect that arises from the inspection team and notes down the minutes of the meeting.

3.Review: A process or meeting during which a work product, or set of work products, is presented to project personnel, managers, users, customers, or other interested parties for comment or approval. The main goal of reviews is to find defects. Reviews are a good complement to testing to help assure quality.
Assure the quality of deliverable before the project moves to the next stage. Once a deliverable has been reviewed, revised as required, and approved, it can be used as a basis for the next stage in the life cycle.


Comments

Post a Comment

Popular posts from this blog

Implicit and Explicit requirements

-
Implicit and Explicit requirements Explicit Requirements​ :    ● The Things business analyst Wrote Down.  ● These are the requirements explicitly stated or mentioned by the customer.  ● Explicit requirements are most commonly found in documents communicated by stakeholders to the development team.   ● This is the simplest type and the easiest to test.  ● The development team might take the form of an elaborate design specification, a set of acceptance criteria.  ● Explicit requirements in the form of claims that is, communications to end-users about things the software can do.   Implicit Requirements​ :  ● The Things client Will Expect  ● These are the requirements that are not explicitly stated by the customer, but implied or derived from the requirement stated by the customer.  ● These are all the things that users are going to expect that were not captured explicitly.  ● Examples include performance...
Read more

Software Configuration Management (SCM)

-
Software configuration management (SC) is a software engineering discipline consisting of standard processes and techniques often used by organizations to manage the changes introduced to its software products. SC helps in identifying individual elements and configurations tracing changes and version selection control and baselining.   SC is also known as software control management. SC aims to control changes introduced to large complex software systems through reliable version selection and version control.   Software Configuration Management does​ ​   ● Introduction to Software Configuration management and Configuration management for software Testers.  ● Software configuration management (SC) is the discipline for systematically controlling the changes that tae place during Software evelopment.  ● Software development software consists of a collection of items (such as program documents etc..) that can easily be changed. uring software...
Read more

Identified for Configuration Management

-
The term configuration item (CI) refers to the fundamental structural unit of a configuration management system. Examples of CIs include individual requirements documents software models and plans. The configuration-management system oversees the life of the CIs through a combination of processes and tools by implementing and enabling the fundamental elements of identification change management status accounting and audits. This system aims to avoid the introduction of errors related to lack of testing as well as incompatibilities with other CIs.     Configuration Management Activities ​:     1. ​Configuration Item Identification ​:  ​In this phase, the item will be identified for making changes.  Example: ​Requirement document design document source code etc    2. ​Change Control ​: ​ Controlling the release and changes of the product throw out the software life cycle here CCB team will approve or disapprove changes prioritize the change...
Read more