Gerência e Qualidade de Software - Aula 05 - Verificação e Validação

Verification and Validation Processes in Software Development

Introduction to Verification and Validation

• The lesson focuses on verification and validation (VV) processes, essential for software development, illustrated through a real software company example.

Understanding Testing in Software

• Testing is not the sole method for analyzing software products for defects; it is part of fundamental processes in software genesis.

• VV processes are disciplined methods to evaluate software products and control quality, applicable to various artifacts beyond just the software itself.

Types of Analysis: Static vs. Dynamic

• Two general types of analysis exist: static (no execution required) and dynamic (involves executing the product).

• Static analysis includes reviews, while dynamic analysis often involves testing; both are crucial for assessing product properties.

Differentiating Verification from Validation

• Verification ensures that selected products meet specified requirements; these can include feasibility, consistency, correctness, and adherence to defined standards.

• In contrast, validation demonstrates whether a product meets user needs when placed in its intended environment.

Techniques Used in Verification

• Various techniques like architectural evaluations or continuous integration help verify if requirements are feasible and correct during different project phases.

• Prototyping and simulations can be used during requirement definition to validate concepts with user involvement.

Importance of Continuous Feedback

• Continuous delivery allows users early access to the software, facilitating ongoing validation through acceptance testing by stakeholders.

Conclusion on VV Processes

• Both verification and validation serve distinct purposes: verification checks if the right product is built while validation checks if the right product meets stakeholder needs.

How Does Legal Verification Process Work?

Overview of Legal Verification and Code Review Practices

• The legal verification process involves various practices aimed at achieving high-quality code, including code reviews where team members assess each other's work rather than relying on a single reviewer.

• This collaborative approach fosters teamwork and ensures that all team members are familiar with the project’s codebase, which is believed to add significant value to the overall project.

• Automated testing is emphasized across different levels, from unit tests for individual functions to higher-level integration tests that simulate user interactions with the platform.

Tools and Techniques in Code Quality Assurance

• A practice similar to code review but automated is referred to as "code analysis," which utilizes tools specific to programming languages to ensure adherence to coding standards defined by the team.

• These tools help identify potential issues in the code (often termed "code smells") and alert developers about possible problems that need attention.

Agile Development Practices

• In agile development, it’s crucial for developers to spend time thinking through their functions before coding. This reflection can streamline the development process significantly.

• Each type of practice has associated tools; for instance, in Ruby on Rails, there are platforms like Beach Rugby that facilitate collaborative coding and feedback among team members.

Testing Frameworks and Validation Processes

• Various libraries exist for testing purposes; examples include RSpec for Ruby and Jasmine for JavaScript, which support both unit testing and integration validation processes.

• The validation process is critical in software development as it ensures that the final product meets client requirements. It begins early with specifications and visual designs before actual implementation starts.

Client Interaction and Feedback Loops

• Early-stage design allows clients to visualize outcomes before full functionality is developed, minimizing effort compared to direct implementation of features without prior approval.

• Throughout development cycles (which may last one or two weeks), functionalities are tested internally by all team members in a shared environment where they can verify if features meet expectations.

• After internal testing, completed functionalities move into a staging environment where clients can validate whether their needs have been met before final deployment occurs.

Conclusion on Best Practices

• Continuous practices such as code reviews not only enhance verification but also contribute positively towards software quality improvement over time.