Verification and validation Q1) What is the difference between verification and

ID: 3588038 • Letter: V

Question

Verification and validation

Q1) What is the difference between verification and validation, and provide details about “the right disciplines”.

Effective methods for integration

Q2) Discuss this idea: “In order to have an impact on the integration and quality of software in addition to meeting scheduled delivery deadlines, hardware and software designers MUST work together to solve issues.”

Team development life cycle

Q3) Discuss the team development life cycle.

Senior management

Q4) Discuss the roles and responsibilities of senior management in program and project planning step of software development life cycle.

Explanation / Answer

Verification and validation

Q1) What is the difference between verification and validation, and provide details about “the right disciplines”.

Verification is the process executed during the "development phase" of software development life cycle and before the product being given the testing. This is the process of verification of specifications, design, documents, code, and other programs. Verification ensures that product should of high quality, up to mark and meets requirement. Verification is achieved by method called static testing

Validation is the process executed after the development phase means in the testing phase. In the phase the product is well tested against all the requirement specification and customer’s satisfaction.

This can be achieved by method called dynamic testing.

Difference between Verification & Validation.

Verification

Validation

This is manual process of verification of documents, design,

This can be achieved by either manual testing or automated testing

This should be done before Testing phase of SDLC

This needs to be done during testing phase of SDLC

The ensures code quality

The ensures customer’s satisfaction and requirement

Here bugs are treated as low/minor severity

Here bugs are treated as high/major severity

it uses static testing methods like analysis, walkthrough, hardware requirement etc.

Validation uses methods like black box (functional) testing, gray box testing, and white box (structural) testing etc.

This is ensured by Quality and assurance team

This is ensured by testing team

Code execution is not required

Code execution is must

It target is quality and high performance hardware/software

It targets to a end level product

Effective methods for integration

This is true that “In order to have an impact on the integration and quality of software in addition to meeting scheduled delivery deadlines, hardware and software designers MUST work together to solve issues”. Because the hardware to be chosen should be based upon the requirement as well as the software that is going to run on that. There should be perfect match between these two.

The unplanned combination of hardware and software can leads major faults, software crashes or hardware failure which leads to delay in scheduled delivery and deadlines. So there should be pre planned software and hardware architecture and to ensure the same the software and hardware designers needs to work together.

Team development life cycle

Q3) Discuss the team development life cycle.

There are five stages of team development life cycle as listed below

Out of these five, first four stages were developed by Bruce Wayne Tuckman and published in 1965 and is called "Tuckman's Stages". Later in 1977, the 5th stage was introduced jointly by Tuckman and Mary Ann Jense.

Forming: This stage is initial stage where team members meets each other and introduce their self and share background, experiences and interests. In this stage the team lead clears the team goals to the members and tells about roles and responsibilities of an individual. Team leads plays an important role here and helps/guide everyone

Storming: The next stage is storming stage where team members goes through developing stage and compete against each other for their point and ideas. Everyone can have different opinion on execution of something. Here again team leads needs to ensure that there should not be any conflicts and if conflicts are there then how to resolve those conflicts. This is very important stage and must not be avoidable. Then stage ends when the team learns to work together and making common decisions.

Norming: This is stage the individual members of teams are focused on team goals rather than individual goals. They resolve conflicts by their self without team leads intervention. Individual members take responsibility of their respective areas. In this stage, team leads helps the members where ever they get stuck and ensures that team works collaboratively.

Performing: In this stage the team members concentrate on team goals and company’s goals. The team at this stage will be at high performance. Here there is no role of team lead. The members resolves their conflicts there self and team leads intervention is very minimal. Whenever new members join then the team can again go to Forming or storming stage for maintain the flow and mange the change

Adjourning: This is the stage when the project ends and everyone will move in their directions.

Team leads ensures that there is time to celebrate the success and capture the best practices and learning from the same. This also gives the occasion for individual to meet up for one last time and say good bye to each other

Senior management

Q4) Discuss the roles and responsibilities of senior management in program and project planning step of software development life cycle.

The senior members have important roles in various fields:

In short, senior management plays an important role in SDLC, in terms of team's cordination and customer engagement.