The last time we talked bout the Validation and Verification process, the diference between these two and how to select and do a V&V planning, this time is going to be a little different it is going to be about software review.

• Definitions and characteristics of software review
• Activities and roles in each review
• How to retrieve the key work products, plans, requirements, design and code

Defining software review

In software there are some features that must be analized as a part of the software review, software review is a process that ensures that all the measurements of the system are on top, which means that reviewing our code.

• Software quality: We have talked about software quality before, and in this definition we explained that software quality goes with the client, the more satisfied the client the higher the quality, but even the proceddures and funtionalities implementes play an important role in software quality.
• Software quality assurance, this is a methodology to ensure that a software at the end of its life cycle it is now considered software of quality

Types of review

• Internal review: the old classic review method, in which the software is distributed to many people and tell them to try the system and review the proyect to get feedback.
• Walkthrough: In this process all of the involved participate in each of the phases to make sure that most of the posibilities are considered
• Inspection: isnpection is kinda similar to walkthrough but a little more rigorous
• Testing: Testing is the most basic type of review, because everyona can do it, it helps to know what the system is capable of, where does the system break and get information about how does the system works.
• Peer: Focuses on the tecnical content and quality of the system, this review is worked with other developers
• Management: Evaluates the level of work status, where all the future descisions of the systems are taken
• Audit: In which people not related to the system try the system and evaluate possible scenarios about the system, with purpose of getting new ideas of the system

• Objectives and Scope: In order to ensure tha idea becomes sucessful
• Project Planning: To ensure that the selected objectives follow the plan selected to do a good review
• Executing the plan: In this phase all procedures of the plan are executed, all the reviews and analisis needed for the system.
• Measuring and Monitoring: Now wih the evaluation of the plan is time to meassure the level of quality and V&Vness of the system, to make sure it has reached the desired level
• Post Project Review: At the end of the cycle it is documented the results of the review to check wheter another review is needed or if we have finally reached our goal.

During the inspection phase there are some aspects:

• The average preparation effort per unit of material
• The average examination effort per unit of material
• The average defect number found per unit of material
• The average hours spent to find a defect
• The average number of serious defects found per unit of material
• The average number of hours required finding a serious defect

During inspection process there are six main steps:

• Planning
• Presentation
• Preparation
• Meeting
• Rework
• Follow-up
• Objectives
• Inspection Staff
• Rules

With these considerations now you must be able to do a fully review of the system, to check wheter it fulfills the quality, V&V levels desired, with their proper standars. Software review is important because it helps to make sure that the system not only it is considered as quality system but you make sure that every posible case of the system is now checked and the system can be runnable with no issues, distributed and ready to life its life.

Most addictive game in this quarantine

Genshin Impact: This is probably one of the few games that traps the user as soon as they enter the game, genshin is an open world game in which you can play with many characters as you explore the two different regions that are available in the game, defeating bosses, exploring dungeons, using elemental powers such as: electro, geo, hydro, cryo, pyro, and anemo, there are so many things and combos than can be perfomed withing the game, the only problem is that is a gacha game, this means that if you want yo can pay to the game, because most of the characters are obtainable through loot boxes, which are not easy to obtain inside the game, adicitive, fun and really good.

Hi everyone and wellcome back, I know that it has been a while since the last time we talked but now we have another topic to discuss and know about, and this time is going to be about how to properly do a V&V in every proyect, about the methodology and step by step on how to niceli finish a V&V process.

---

V&V in the life cycle of software development

At this point if you were reading my blog you’ll probably know about the life cycle, which is the flow of life in every system, it determines the objective of a system, when it was born, when it develops and when it is expected to end its life, in other words when the system has already completed its purpose of existing.

Of couse if we talk about Verification and Validation first we need to describe what are these:

• Verification: when the product is being built right
• Validation: when people are building the right project

In other words Verification checks if that they are building the system the right way, and Validation checks that the product that they are building is the one who si going to complete the main objective

To describe its aplications to this topic fist we are going to use a life cycle model as an example:

In this model the life cycle of the system is descibred in 4 phases

• Initiacion
• Planning
• Execution
• Closing

Initiation: In this phase the idea of the product that is going to be built is being processed, Verification in this phase is going to be in charge of making sure that the model the idea of making the product is right. Validation makes sure that the product must fullfill the main objective

Planning:In this phase how the model is going to be built is being processed. Verification the going to check that the procedure that is goign to be followed is the correct one. Validation: is going to check that the procedure taken keeps following the main objective.

Execution: In this phase the system is now being built, following the procedure previously established. Verification checks that the procedure is following the objective of the system. Validation checks that the procedure is going to finish a project that fulfulls the main requirements.

Closing: in this phase the end of the system finally is reached. Verification checks that the product was built right. Validation checks that the final project fulfills the objective established in the first phase.

With this example you now probablly know a little bit more about how to implement V&V during a lyfe cycle of a system.

Black mirror recomendation

White bear: In this episode a woman awakes in an abandoned house with no memories at all, aparently she is in her house but she remembers nothing at all, while the episode develops the memories of the woman star to comeback but there a some people who are trying to kill her, and everyone in the world just records how she is being chased with no help at all.

---

International standars for V&V of software

Because V&V are models to evaluate the levels of goodness there are some standars that describes a level of quality for some saying, and these standars rely on rules that need to be followed and level of achieveness acomplished.

Some of the standars implemented in V&V are:

• ISO/TS 17033
• ISO 14021
• IEC 17029
• IEEE
• ISO 9000
• ISO/IEC 15408
• IEC27001

These standars describe the level of achieveness of a system, every one of these standars descibre a diferente level of achieveness, if you want to knoe a little more about the standars pleas check out this link.

Black mirror recomendation

Shut up and dance: In this episode our main character gets blackmailed because some hacker caught him doing some bad things, our main character needs to follow some orders if he wants to keep his secret, secret, as the story goes our main character meets an adult man in the same situation as him, little did they know that hackers have some different plans for them.

---

---

How to plan V&V

In order to do a correct planning about V&V some phases needs to be analyzed and described to finally do a V&V process.

This process is kinda similar to a lyfe cycle, but with more in deph about what needs to be planned before or to be prepared to do the V&V planning.

• Requirements: Validate the requierements of the system and verify that are acomplisable
• Architecture and Design: Validate that the sistem is well designed and runs according the objective of the system. Verification to check non functional requirements
• Implementation: in each procedure implemented check that follows that the software must suceed and do some testing about in each implementation
• Testing: checks that all functionalities of the system meets the requiremens previously established and to make sure that everything works as expected
• Deployment: comfiguration and instalation must run as expected with no bugs and errors

Following these phases when building you ensure that your system is optimal to do a V&V implementation of the system, and now it is time to select one or more standars to meassure the level of V&Vness.

Black Mirror recomendation

Hang the dj: Imagine in a world in which there is an app that will show you who your perfect partner for life is, this is the story about two people who gets matched by the aplication, just for one night, and in that night they felt more for each other than for anyone in the world that they have met before or will met, is an app more powerfull than true love?

---

---

Administrating the V&V Plan

This is probably one of the easiest topics to discuss because in the previous entry we discussed about the diferenece, how to implement, and measure the level of V&Vness which results in a very easy way to administrate the V&V plan.

Procedure to administrate the V&V plan:

• Explain the objetives of the project
• Document all the implemented functions and sequences
• Make sure to test all cases to avoid bugs
• Make sure to aproeach the system in a way that nothing stays outside the evaluations
• If bugs found make sure to document which bugs occurs, under which circumstances and if corrected the way to corrected, to make sure that if some kind of similar bug occurs now there is a way to correct it
• Make sure that procedures can run under any enviroment, if not make sure to run on at least most of them, and to acknowlegde which requieremnts are needed.
• To ensure a bidirectional comunication with the customer, to keep updated all of the involved
• Run updates to the system and maintenance
• ALLWAYS document everything that happens in the system, bugs, errors, implementations, everything.
• Make sure that the end of the system is defined and to redo the planing until a level of V&Vness is adquired.

With this procedure now we can make sure that you are now ready to do a good V&V implementation in your systems, I only recomend doing this if your project is big enough or if you want your project to be as clean as posible.

Black mirror recomendation

Bandersnatch: This is a movie in which we are the main character as the story progresses the main character will face some desicions and we are the ones who decide which opcion the character chooses, each decision takes the character to a different scenario in which good or bad things could happen, we are now the true puppet masters.