DEV Community: SIPSA_IT

Quality, Innovation, and Sustainability as Strategic Decisions for the New Year 2025.

SIPSA_IT — Wed, 15 Jan 2025 09:38:42 +0000

The Beginning of a New Year: Strategic Decisions for Quality, Innovation, and Sustainability in 2025

The start of a new year is the perfect moment to renew strategic commitments and focus efforts on what truly drives business success: quality, innovation, and sustainability. In 2025, these strategic decisions should be the central focus of IT projects, driving not only outstanding results but also a positive impact on the environment and society. At SIPSA, we have identified four essential pillars that will help you reach a new level of performance, competitiveness, and responsibility.

1. Holistic Quality: The Foundation of Success

Quality cannot be an isolated aspect; it must permeate every stage of development and operation in an IT project. Our holistic quality approach ensures that all components, from planning to implementation, work in harmony to deliver a significant impact.

Key points for implementation:

Full coverage: Includes technical, functional, and user experience testing.
Customization: We adjust methodologies to meet the unique needs of each client, adapting to specific industries and challenges.
Clear metrics: We measure success with tangible indicators that reflect both technical performance and business impact.

2. Sustainability: Commitment to the Future

In 2025, sustainability will not be optional; it will be a key factor in IT projects. It involves not only reducing environmental impact but also ensuring responsible and lasting technological practices that benefit both the company and the environment.

How to integrate sustainability into IT:

Energy efficiency: Implement solutions that optimize resource usage and reduce energy consumption in systems. Tools like TAST (Test Automation System Tool) not only automate functional, integration, and performance tests but also maximize operational efficiency, reducing the need for physical and energy resources in testing environments.
Process optimization: Use frameworks like TAST, whose cloud-based design allows tests to be executed without geographical barriers, eliminating the need for physical infrastructure and promoting a sustainable work model.
Software lifecycle: Design applications with a focus on durability, optimization, and adaptability to new technologies.
Social responsibility: Ensure technological processes are aligned with objectives of positive social impact, fostering a balanced development between business growth and community well-being.

3. Continuous Integration and Agility

To stay competitive, systems must be flexible and continuously evolving. Continuous integration, coupled with DevOps strategies, ensures changes are fast, efficient, and always aligned with objectives. Agile methodologies allow for quick adaptation to a dynamic environment while prioritizing the value delivered to the customer.

Key advantages:

Risk reduction: Automated tests detect errors before they become major problems.
Shorter delivery cycles: Increase delivery frequency without compromising quality.
Total flexibility: Methods like Scrum facilitate quick adjustments based on new needs or priorities.
Smooth collaboration: Connect all teams, from developers to testers, on a common platform, ensuring decisions always revolve around the positive impact on end customers.

4. Responsible Artificial Intelligence

The use of Artificial Intelligence (AI) will be essential in 2025, but it’s not enough to just use it; it must be implemented strategically and responsibly. AI should be a tool that enhances organizational capabilities, always aligned with the company’s objectives and values.

How to implement AI correctly:

Selecting the right use cases: Focus on areas where AI can generate the highest added value.
Ethics and transparency: Apply ethical principles in AI implementation, ensuring fair and understandable decisions.
Optimization and learning: Train teams to understand and use AI effectively, maximizing its impact on results.

Conclusion

2025 is an opportunity to transform the way companies approach quality, innovation, and sustainability. By integrating advanced tools like TAST, fostering collaboration, prioritizing continuous training, using AI responsibly, and adopting sustainable practices, your organization will be positioned to lead in an increasingly competitive market.

At SIPSA, we are committed to guiding you toward a more responsible and innovative future. Let’s talk and turn your strategic decisions for the new year into reality!

Maximize the efficiency of your tests with TAST

SIPSA_IT — Wed, 15 Jan 2025 09:36:27 +0000

In the realm of software development and testing, efficiency and collaboration are essential for success. At SIPSA, we believe in adopting practices that optimize the testing process. That's why TAST is the test automation tool designed to simplify automation, with features that help maximize testing efficiency and coverage.

Below, we explain two of the many features of TAST that maximize the efficiency of software testing: the gates and repositories of TAST. These features offer flexible and powerful solutions that save you time while improving the quality and consistency of your tests.

What is a gate?

In TAST, test cases are defined with UML sequence diagrams that detail the step-by-step process. A gate is a diagram nested inside another diagram.

How to create a gate?

Publish the diagram: First, publish the diagram you want to use as a Gate at the project or domain level.
Select the gate: In TAST, select the option to create a new Gate.
Draw the gate: Insert the Gate into the main diagram.
Configure properties: Define the properties of the Gate, including the corresponding domain and project.

Example: Gate URL

To illustrate how a gate works, let's consider a test case that involves automatically opening 100 different websites and capturing a screenshot of each to verify that they load correctly.

Gate GUI: We use a diagram that captures the screenshot of a webpage and convert it into a gate.
URL Loop: We insert this Gate into a loop that accesses an Excel file where the 100 URLs are listed, opening them sequentially and capturing the screenshot of each.

This gate can be reused in any other diagram that needs to capture a webpage screenshot, ensuring that any changes made to the Gate are reflected in all diagrams that contain it.

Benefits of using gates

Efficiency: Gates allow for the reuse of existing test cases, saving time and effort by avoiding duplicated work.
Simplicity: They simplify tests, making them more visual and easier to follow.
Modularity: Gates promote modularity in test case creation, adapting easily to iterative development deliveries.

What is a repository in TAST?

A repository in TAST is a feature that allows centralized storage of variables and XPaths. TAST repositories are YML or TXT files that facilitate the management and reuse of data in automated tests.

How to create a repository in TAST?

Manage repositories: In the Model menu, select "Manage Repositories". Click + to create a new repository, defining its name and the corresponding domain/project/folder.
Write content: Write the content of the repository, such as XPath, CSS Selectors, IDs, etc.
Link to the diagram: Open the test case (diagram) and link the steps that use the data from the repository.

In TAST, repositories can also be cloned to make the initial setup process easier.

Example: SAP Repository

To illustrate the use of a repository, let's consider an automated test case for the SAP web application. This test case involves: logging in, creating a project for a new client, creating work packages, assigning resources, issuing an invoice, and changing the project status to "in progress."

This repository stores the XPaths and IDs needed to identify and interact with elements on the webpage. If these elements change, you only need to modify the data in the repository, and the changes will be reflected in all test cases that use this repository.

Benefits of repositories

Centralization of resources: All information is stored in one place, making it easier to access and manage.
Simplified maintenance: Updating a resource in the repository will automatically reflect in all linked test cases.
Agile testing: The reuse of resources and centralization allow for faster and more efficient testing.

Maximize the efficiency of your tests with TAST

Using gates and repositories in TAST maximizes efficiency and improves the structure of automated tests.

Request your TAST demo with no commitment and discover more features that will make your testing team's work more efficient.

Quality software = Secure software

SIPSA_IT — Wed, 15 Jan 2025 09:33:07 +0000

In an increasingly connected world, where businesses heavily rely on digital aspects such as e-commerce, remote work, cloud services, and distributed asset control, software quality and security have become critical factors for business survival and success. A lack of quality and/or a security breach can lead to severe consequences, ranging from the loss of confidential data to reputational damage and even operational disruptions.

Cybercrime represents a significant economic challenge, with an estimated annual cost of $10.5 billion. Additionally, nearly 90 million attacks are reported every year. In Spain, over 375,000 internet-related crimes were committed in 2022, meaning 1 in every 5 crimes in the country occurred online. This highlights the urgent need to strengthen cybersecurity measures and digital protection.

At SIPSA, we understand that absolute security against cyberattacks is unattainable. However, our goal is to help you achieve the highest level of security and trust in your software. We are a consulting firm specializing in digital transformation, software quality, and automated testing. We have defined the SPHERICAL QUALITY methodology, a model that will enable you to develop secure, reliable, and high-quality software.

Where Do We Act to Achieve Quality and Secure Software?

At every stage of the software development lifecycle, quality and security practices are integrated. From planning to implementation, criteria are established to ensure the software meets high standards and prevents vulnerabilities.

PLAN: Awareness and Training

Team awareness and training are crucial to creating a culture of quality and security within the organization. Employees must understand common cyber threats, secure coding practices, sensitive data management, and the importance of security testing.

DESIGN: Secure Architecture Design

A robust and well-designed architecture forms the foundation of a secure system. At this stage, secure design principles are defined, threat analysis is conducted, security layers are implemented, and more.

CODING: Static Code Analysis

Static code analysis is a fundamental technique for identifying vulnerabilities and errors in the source code during the early stages of development. Addressing issues at their source ensures a solid and secure foundation for the software.

BUILD: Container Image Validation

Container images are essential components for deploying and running applications. At this stage, the origin of the images is verified, their digital signature is validated, the file used to build the image is examined, images are kept up-to-date, and their usage is logged and audited.

DEPLOYMENT: Vulnerability Scanning

Vulnerability scanning identifies and prioritizes security risks in the software before production deployment. This process detects issues such as access control failures, cryptographic flaws, code injection, insecure design, identification and authentication failures, software and data integrity issues, and server-side request forgery. The scanning process should be automated and generate regular reports for decision-making.

TESTING: Ethical Hacking and Security Testing

Ethical hacking and security testing are advanced techniques to evaluate systems’ resilience against real-world cyberattacks. These tests are conducted by experts simulating real attacks to identify vulnerabilities.

IMPLEMENTATION: Compliance Validation and Code Signing

Compliance validation ensures the software adheres to applicable regulations and standards. Code signing verifies software integrity and prevents the execution of unsigned or untrustworthy code. Additionally, internal security policies should be established, and regular compliance audits should be conducted.

MAINTENANCE: MDRR (Monitor, Detect, Respond, and Recover)

MDRR is a continuous process for managing security incidents. It includes constant monitoring of systems, networks, and applications to detect suspicious activity or indicators of compromise. If an incident is detected, quick and effective response is essential to contain damage and prevent further exposure. The final phase involves restoring affected systems to a normal operational state.

The SPHERICAL QUALITY Methodology

The SPHERICAL QUALITY methodology is an integral and revolutionary strategy that enables companies to protect their software and digital assets in an increasingly complex and threatening world. By addressing security from the earliest stages of development to continuous maintenance, organizations can mitigate risks and ensure the quality, reliability, and stability of their applications. This approach not only safeguards data and customer privacy but also fosters a culture of security within teams. Such a security culture promotes customer trust and enhances brand reputation, providing businesses with a competitive edge in the market.

As a pioneer in implementing SPHERICAL QUALITY, SIPSA becomes a valuable ally for companies seeking to thrive in the digital era. With a focus on prevention, early detection, and rapid response to threats, SIPSA offers its clients confidence that their software is secure, reliable, and prepared to face future challenges.

The challenge for CIOs

SIPSA_IT — Mon, 13 May 2024 09:40:59 +0000

In the current landscape, CIOs face a growing challenge: stagnant budgets versus rising expectations. The pressure to optimize resources and improve efficiency is evident, and in this context, process automation presents itself as an indispensable tool.

SIPSA offers a comprehensive solution that effectively addresses these challenges through TAST, a complete test automation tool, and its specialized testing services.
Therefore, the key to success is how to reconcile Quality with a scenario of deviations in Time and Cost? The answer is clear: Doing more with less effort. How? By automating the Testing Process.

Automation: The key to testing efficiency

Software testing is a crucial component of ensuring the quality and smooth operation of any application. However, manual testing processes can be slow, costly and error-prone. Test automation emerges as an effective solution to optimize this process, bringing numerous benefits:

Cost reduction: by speeding up testing and minimizing repetitive manual efforts. Although it requires technical skills, it improves software quality and speeds up development, enabling more cost-effective and efficient delivery of high-quality products.
Increased speed: Automated processes can execute tests much faster than humans, allowing more tests to be run in less time.
Increased accuracy: Automated processes are less prone to human error, ensuring more accurate test results.
Improved coverage: Automation allows for more comprehensive testing, covering a wider range of scenarios and use cases.
Freeing up resources: By automating repetitive testing tasks, human testers can spend their time on more strategic tasks, such as analyzing results and identifying complex issues.

TAST is an advanced framework that maximizes automation throughout the testing process from the end-user perspective. This codeless solution enables testing teams to design, implement and execute tests efficiently and accurately. TAST features a layered architecture that uses process diagrams with standard UML notation, facilitating communication between test teams and users. This intuitive interface reinforces user involvement in the testing and acceptance processes.

SIPSA offers a holistic approach by providing TAST along with specialized testing services, tailored to the unique needs of each organization. Test cases are defined independently of the system under test (SUT), which facilitates their reusability and adaptability to different projects.

In addition, TAST introduces the adapter concept, which allows mapping test cases to the SUT and generating test data. This provides testers with a wide selection of predefined functions to successfully interact with the system under test. With specific adapters for technologies such as GUIs, desktop applications, APIs, databases, files, legacy systems, MQ queues and more, TAST can automate a variety of test types, such as integration, functional, system, acceptance and accessibility testing.

SIPSA's testing services complement the TAST tool, offering a comprehensive methodology that encompasses test design, implementation, execution, and analysis. This approach ensures that organizations achieve optimal results and a significant return on investment.

By choosing SIPSA as a strategic partner, CIOs can be confident that they are investing in a comprehensive solution that optimizes operational efficiency, improves the quality of products and services, and accelerates development cycles. SIPSA and the TAST tool enables organizations to stay competitive in a constantly evolving market, meeting the quality and speed expectations that customers demand.

Sustainable Software

SIPSA_IT — Thu, 14 Mar 2024 14:51:45 +0000

Imagine a world where every click, every line of code leaves a tangible footprint on our planet. In a landscape full of software, how much are we willing to sacrifice for digital benefit? Discover how SIPSA is leading a quiet revolution towards more conscious and sustainable software development. The age of innovation cannot ignore environmental responsibility – are you ready to join the transformation?

Sustainable software refers to a development approach that considers environmental as well as social and economic aspects throughout its entire life cycle. This implies not only considering the efficiency and quality of the software, but also assessing and moderating its impact on the environment and society.

Sustainable software development practices may include:

Resource optimization: Efficient use of computational resources, such as energy efficiency and performance optimization to reduce resource consumption.
Carbon footprint reduction: Minimize carbon emissions associated with software development, deployment and use by optimizing code, selecting energy efficient infrastructures, and reducing hardware demand.
User-centered design and accessibility: Develop software that meets the real needs of end-users, thus reducing the waste of resources in the creation of unnecessary or little-used solutions.
Full software lifecycle: Consider environmental and social impacts during all stages of the software lifecycle, from design and development to decommissioning and disposal.
Transparency and accountability: Maintain transparency about software development practices and environmental impacts and take responsibility for any negative impacts.
Quantum Computing Implementation: technologies and practices that minimize the environmental impact associated with the research, development, and operation of computing systems. Quantum computing systems are designed to be more energy efficient compared to classical systems. This involves the development of hardware and software optimized to minimize energy consumption. Organizations that develop and operate quantum computing systems implement responsible practices that reduce their environmental footprint.
Sustainable team management and teleworking: key to business sustainability. They improve employees’ quality of life, reduce carbon footprint and operating costs, while strengthening the company’s reputation by aligning its actions with sustainability.

In this context, SIPSA stands out as an innovative alternative. The focus on sustainable development is not a utopian idea, but a core practice. From development time estimation to rigorous testing and agile deployment, each phase is executed with the goal of minimizing waste and maximizing efficiency.

One of the key areas where SIPSA makes a difference is in reducing the carbon footprint of software. Revealing data shows that seemingly simple actions, such as sending an email, can generate a surprising amount of carbon emissions. For example, it is estimated that sending an average-sized email emits approximately 4 grams of CO2, which is equivalent to driving a car for approximately 14 meters. With SIPSA, each line of code is optimized to minimize this impact, contributing to a cleaner and more sustainable digital environment.

Software quality is not compromised in the pursuit of sustainability. In fact, at SIPSA, quality and efficiency go hand in hand. Every solution developed is rigorously tested to ensure functionality and reliability, reducing the need for future revisions and rework.

The management of our development teams is sustainable, first and foremost, through teleworking. By allowing employees to work from home, it promotes their happiness and well-being by providing flexibility and work-life balance, resulting in greater job satisfaction and increased efficiency and productivity. It also helps to reduce pollution by reducing employees’ daily commuting, and reduces resource consumption in the office, contributing to a more sustainable management of business resources.

Sustainability is now a global priority, and the software industry cannot be left behind. SIPSA demonstrates that it is possible to create innovative and efficient technological solutions without compromising our environment. Adopting sustainable development practices is not only an ethical choice, but also a smart strategy for the future of technology.

At SIPSA, software is not just a tool, it is a commitment to a better and more sustainable world. Join us on this exciting journey towards environmentally conscious software development. Together, we can make a difference.

Migrating to the cloud | Top 6 challenges

SIPSA_IT — Thu, 04 Jan 2024 11:30:47 +0000

Cloud migration, in general terms, refers to the process of moving applications, data and services from local infrastructures or physical servers to cloud computing environments. Instead of relying on local physical hardware and resources, organizations use cloud services to store, process and access their data and applications over the Internet.

In today’s digital era, migrating to the cloud has become a crucial step for companies looking to optimize their operations and remain competitive in an ever-evolving marketplace. However, this process is not without significant challenges that can affect the efficiency and success of the transition.

1. DATA SECURITY.

Some of the associated risks include data loss, system disruption, unnecessary expenses and data security risk. To ensure security during the migration process, requirements such as selecting reliable cloud providers, assessing security risks, and protecting sensitive data must be considered.
It is paramount to perform data migration in a secure manner to avoid exposing data to unauthorized third parties. In addition, it is recommended to verify the integrity and consistency of the data once migrated, establish backup and recovery mechanisms, and implement early-stage testing to introduce security into the development pipeline.

2. TECHNICAL COMPLEXITY.

Cloud migration involves the transfer of systems, data, and applications to a different technological environment, which can generate significant technical complexities. This challenge encompasses aspects such as integrating existing systems with cloud services, optimizing performance in the new environment, and managing the cloud architecture to ensure scalability and operational efficiency.
Migrating to the cloud requires a thorough systems analysis to determine what resources to upload and what not to upload, as well as the adoption of a multi-layered approach that combines technology, processes, and people to ensure security in the deployment of these online resources.
Having an expert cloud migration service provider and trusted cloud partner is critical to effectively address these challenges.

3. EFFICIENT COST MANAGEMENT.

Some of the key aspects of achieving this efficient management include comparing the costs of maintaining on-premises infrastructure with cloud costs, calculating the total cost of ownership (TCO) for cloud migration, and using cloud automation to save costs.
Cloud service providers offer various cost management tools and services that enterprises can leverage to monitor, analyze, and optimize their costs. In addition, it is essential to define migration metrics, improve visibility and predictability of migration costs, and document cost variations during the migration process.

4. CULTURAL RESILIENCE AND STAFF TRAINING.

Cultural resistance manifests itself when teams do not understand why they should migrate to the cloud and perceive the migration as more difficult than expected.
On the other hand, migration to the cloud affects culture and working practices, so change management and staff training are critical aspects to consider.

5. SOFTWARE COMPATIBILITY MANAGEMENT.

This challenge involves addressing differences in cloud platform requirements and features, as well as differences in software versions and changes in data storage and processing methods. Before starting the migration process, it is essential to assess the compatibility of existing software with the selected cloud platform to avoid integration issues and ensure a smooth transition.

6. ASSURE THE SOFTWARE QUALITY OF THE NEW SYSTEM.

Cloud migration projects are often seen as highly technical projects, where functional teams are not involved and the BIG CHALLENGE of software quality assurance of the new system arises.
From the planning phase (where requirements are established and critical data is identified), to the execution of the migration (where extensive testing is carried out), the functional teams, such as business analysts, developers, UX/UI designers, testers, QA, implementation specialists, end users, etc., play crucial roles. Change management, data validation and acceptance testing with end users are key to ensuring the integrity and consistency of the migrated information. Together, the effective collaboration of these teams ensures a successful migration and SIPSA has the tools and expertise to tackle these projects implementing Quality.

Conclusion

In this journey, as organisations that address these challenges holistically, the smartest thing to do is to go with a partner who brings the expertise to successfully arrive at the destination, key to not only surviving, but thriving in the era of continuous innovation and taking advantage of the transformative opportunities that the cloud offers.

Shall we accompany you? For more information contact us by clicking here.

Exploratory Testing | Streamlining Exploratory Testing with TAST

SIPSA_IT — Fri, 21 Jul 2023 09:03:12 +0000

Exploratory testing is a method used to find bugs and problems in software without adhering to a predetermined test plan. It makes use of the tester’s knowledge, skills, and experience. The tester is free to explore the software in a flexible manner, test various features and scenarios and identify potential problems, rather than having to comply with a predetermined set of instructions. Exploratory testing is especially useful when new or complex applications need to be tested, where it can be a challenge to foresee all possible test cases.

When performing exploratory testing, testers often take an “ad hoc” approach, meaning that they decide what to test and how to test it on the spot without first creating a detailed plan. They have the ability to perform tasks such as clicking on various user interface elements, entering information into input fields, interacting with various functionalities, and viewing the results.

Exploratory testing also allows testers to test non-functional aspects such as usability, performance, and security. By exploring the software more freely, they can identify usability issues, such as confusing workflows or unintuitive interfaces. By subjecting the software to multiple workloads or performing repetitive tasks, they can also find performance issues.

Some of the main characteristics of this type of tests are:

Flexible approach: Exploratory testing is based on the tester’s experience and knowledge, allowing them to modify as they go along. They are not constrained by a predetermined testing strategy and are free to delve into the software as they see fit.
Creativity and intuition: testers can use their creativity and intuition to discover possible defects. To find problems, they can experiment with various combinations of actions, look for strange scenarios or even simulate end-user behavior.
Learning during testing: As testers explore the software, they gain a deeper understanding of its operation and behavior. This allows them to identify risk areas and concentrate their testing efforts there.
Exploration of non-functional components: Exploratory testing can test non-functional components such as security, performance, and usability, in addition to software functionality. When attempting to access restricted areas or manipulate data, testers may encounter security issues, while performance issues may arise when testing software under various workloads.
Logging and documentation: Although exploratory testing does not adhere to a predetermined test plan, it is crucial that testers record and document their findings as they are made. This helps to track problems encountered, communicate them to the development team, and facilitate defect reproduction.
Complementing other testing techniques: While exploratory testing is valuable, it should not be the only approach used. To ensure more complete coverage, they can be used in conjunction with other testing methods, such as scenario-based testing or regression testing.
Iterative and continuous: Exploratory testing can be performed in iterations during the software development cycle. Testers can perform additional exploratory testing to ensure that the software remains stable and bug-free as changes and new features are added.

Due to the characteristics of exploratory tests, their automation involves many challenges. But can we make these exploratory tests more agile? The answer is yes.

In TAST Test Automation System Tool there is the “Manual TAST” functionality that allows:

Manual intervention of the tester.
Record manual test sets.
Generate evidence along with the results of the steps.
Load results into project management applications such as ALM Octane or Jira/Xray.

In short, with TAST it is possible to make testing and test equipment efficient, automating or allowing manual intervention using “Manual TAST” in those cases where automation is not an option.

Click here to learn more about TAST.

QA | Quality Assurance Methodologies

SIPSA_IT — Tue, 28 Feb 2023 15:41:44 +0000

Quality Management (QM) is a global concept, within which other nested concepts are included: Quality Assurance (QA), Quality Control (QC) and Testing.

The purpose of this post is to have in the same document the most well-known continuous improvement models and quality assurance (QA) standards. Methodologies that are not only present in software engineering companies specialised in the production of software, but that apply to any business or company, as they require, to a certain extent, software for their operation and development.

CONTINUOUS IMPROVEMENT MODELS

Kaizen
The word Kaizen comes from two Japanese terms: kai, which means “improvement”, and zen, which means “good” or “well-being”, but is more loosely translated in the West as “continuous improvement“. The Kaizen process was popularised in the 1950s after World War II by Japanese manufacturers.

What sets it apart from other process improvement methods is that it aims to involve the entire organisation, from top management to assembly line workers, in its implementation. Having a Kaizen Culture in your organisation means that every individual, regardless of rank, is empowered to look for improvement opportunities every day, no matter how small.

To apply the Kaizen methodology, the following steps will be followed:

Plan: for this first step you should be aware of the current situation of your business, analyse the problems and define an action plan. Look at your bottlenecks, the most common incidents, the points you would like to improve.
Do: the next step is to develop the action plan and put it into action. This action plan should include measures for each of the aspects you have identified during the planning.
Check: In this third step, the most important thing is to analyse whether your action plan is having results and to compare these with the results obtained before establishing the Kaizen methodology. If you have achieved the results you set out to achieve at the beginning, it means that you are on the right track. If not, you will have to start all over again.
Act: if you have achieved the objectives you set at the beginning, then it is time to standardise the methodology, but without forgetting that it is a process in which improvement must be continuous.

LEAN
At the end of the 19th century, the first Lean thinking emerged in Japan from Sakichi Toyoda, the founder of Toyota. But it was not until the early 1990s that this work philosophy reached the West, thanks to a publication by James Womack, Daniel Jones and Roos entitled “The machine that changed the world”. In it, the characteristics of a new production system that combined efficiency, flexibility and quality were explained, where the concept of Lean Manufacturing appears for the first time.

This is based on the elimination within the production process of everything that does not add value, allowing to work more efficiently and with a lower consumption of resources. The Lean Methodology has evolved to new specific applications such as Lean Health, Lean Construction and Lean Office. The common point among all of them is the joint action of managers, middle management and operators, establishing quality principles to optimise work, improve results and apply Continuous Improvement in all business areas.

The five basic principles of this philosophy are:

Specify the value of the product as perceived by the customer.
Identify the value chain.
Let production and value flow.
Enable the customer to get what he/she wants.
Pursue perfection.

Lean Management encourages teamwork, everyone who works is an important part of the process and their work is critical to the rest of the employees and ultimately to the company.

In Lean thinking, any capacity in operations that is greater than the amount needed to satisfy customer demand will be considered waste that will not produce value, so all improvement initiatives will focus on eliminating this waste and balancing capacity with demand.

Six Sigma

The Six Sigma methodology was a concept created by engineer Bill Smith at Motorola in 1988, as a business and quality improvement strategy. But it was later improved and popularised by General Electric.

It is an improvement methodology that provides a path to follow to continuously improve the quality of the product or service, seeking cost savings, to increase customer satisfaction, to achieve 99.9999% efficiency (ability to achieve the desired or expected effect) and to eliminate variability and waste.

To this end, it focuses on reducing (to almost zero) defects and variations in processes, quality costs, cycle times and increasing productivity and customer satisfaction through the reduction of variations in products and processes, providing organisations with a sustainable competitive advantage over time.

The Six Sigma methodology bases continuous improvement on two main indicators: the speed with which a process is performed (cycle time) and the number of errors that reach the customer (internal/external). It consists of a robust design as well as establishing tolerances to define a standard and to know which products are or are not of sufficient quality to go to market.

The Six Sigma methodology is usually used to improve processes or products that already exist in the company and is based on the DMAIC method: define, measure, analyse, improve and control.

When Six Sigma is applied to processes or products that do not yet exist, it is based on the DMADV method: define, measure, analyse, design and verify.

TRADITIONAL METHODOLOGIES

WATERFALL
In software engineering, the waterfall methodology was named after the position of the development phases that seem to cascade “by gravity” towards the next phases, in a staggered manner.

It is the methodological approach that rigorously orders the stages of the software development process in such a way that the start of each stage must await the completion of the previous stage. At the end of each stage, the model is designed to conduct a final review, which is responsible for determining whether the project is ready to move on to the next phase. This model was the first to originate and is the basis for all other life cycle models.

This model began to be designed in 1966 and was completed around 1970. The main problem with this approach is when changes or modifications arise, as one has to go backwards in the life cycle. In addition, the results cannot be seen until very late in the project, so any change due to an error can mean a long delay as well as a high development cost.

V- Model
The V-Model first appeared at Hughes Aircraft, circa 1982, as part of the pre-proposal effort for the FAA Advanced Automation System (AAS) programme to replace air traffic control system hardware and software, providing new automated capabilities to cope with the increase in air traffic control.

The V-model is an SDLC (Software Development Life-Cycle) model in which the execution of processes occurs sequentially in a V-shape.

It is an extension of the waterfall model and is based on the association of a test phase for each corresponding development stage.

Prototyping
A prototype is a preliminary version of an information system for demonstration or evaluation purposes. Requirements prototyping is the creation of a partial implementation of a system, for the explicit purpose of learning about system requirements. A prototype is built as quickly as possible.

Spiral
Takes the advantages of the waterfall development model and the prototyping model and adds the concept of risk analysis.

Four activities are defined:

Planning: where initial requirements or new requirements to be added in this iteration are collected.
Risk analysis: based on the requirements, we decide whether or not we are capable of developing the software and the decision is made to continue or not to continue.
Engineering: in which a prototype is developed based on the requirements obtained in the planning phase.
Customer evaluation: the customer comments on the prototype. If the customer is satisfied with it, the process is finished, if not, new requirements are added in the next iteration.

Incremental
Allows the project to be built in incremental stages, where each stage adds functionality. These stages consist of: requirements, design, coding, testing and delivery.

Allows to deliver a faster product to the customer compared to the waterfall model.
Reduces risk by providing visibility into the progress of new releases.
Provides feedback through the functionality shown.
Allows major risks to be addressed from the outset.
Partial implementations can be done if sufficient functionality is available.
Testing and integration is ongoing.
Progress can be measured over short periods of time.
It is easier to accommodate changes by shortening the size of increments.
Can be planned based on the functionality to be delivered first.
Versatility requires careful planning at both administrative and technical levels.

Frameworks (working environments) have been created to support the development of projects using this model, the two most famous being the Rational Unified Process (RUP) and the Dynamic Systems Development Method (DSDM), which we explain below when we discuss agile methodologies.

Incremental and iterative development is also an essential part of a type of programming known as Extreme Programming and the other rapid software development frameworks.

RAD
The development methodology known as Rapid Application Development (RAD), officially introduced by James Martin in 1991, consists of developing applications rapidly through frequent iterations, prototyping and approvals with continuous customer feedback. Because of its speed and agility, RAD is growing in popularity.

The key benefits are:

Reduced development time and accelerated delivery.
Improved flexibility and adaptability.
Better risk management.
Less manual programming and shorter testing times.
Constant, relevant and real-time user feedback.

AGILE METHODOLOGIES

In February 2001, following a meeting held in Utah-USA, the term agile applied to software development was born. This meeting was attended by a group of 17 experts from the software industry, including some of the creators or promoters of software methodologies. Their objective was to outline the values and principles that should enable teams to develop software quickly and in response to changes that may arise during the course of the project.

It was intended to offer an alternative to traditional software development processes, characterised by being rigid and driven by the documentation generated by each of the activities carried out. Following this meeting, The Agile Alliance, was created, a non-profit organisation dedicated to promoting the concepts related to agile software development and helping organisations to adopt these concepts.

XP (Extreme Programming)
The main particularity of this methodology is the user stories, which corresponds to a requirements specification technique; these are formats in which the client describes the characteristics and functionalities that the system must possess.

It restricts team members to working only on immediate needs, rather than considering future needs. The aim is to create a simple system that can be easily implemented and then improved as needs arise. The aim is to solve as many small problems as possible before they become bigger problems and affect the delivery date.

In this methodology, the process called Planning game is carried out, which defines the compliance date and the scope of a functional delivery, the client defines the user stories and the developer, based on them, establishes the characteristics of the delivery, implementation costs and number of interactions to complete it.

Small deliveries are made using short development cycles, called iterations, which show the customer a functionality of the finished software and get feedback from him.

In this methodology, there is a very important part: acceptance testing, once a functionality has been developed, it goes into testing by the customer, giving his approval.

Scrum
Its main objective is for a team to react quickly, simply and appropriately instead of wasting time in creating/updating outdated work plans. It describes a set of practices for project management:

Sprint units of work, typically 30 days.
Short daily meetings (daily), 15 minutes, by the Scrum Team.
Demos with deliverables that can be delivered on time.
And roles are defined to generate a well-functioning structure:

Scrum Master: person who leads the team and ensures that the rules and processes of the methodology are followed.
Product Owner: representative of the clients who use the software.

The development team: group of professionals in charge of converting the list of requirements or Product Backlog into software functionalities.

DoR y DoD
Agile Scrum methods use DoR (Definition of Ready) and DoD (Definition of Done) to ensure quality by enforcing transparency and setting the right expectations.

In agile methodologies, Quality Gates are the quality gates that ensure quality throughout the different stages of the project.

DoR is the input criteria to the user stories for the sprint.

DoD is the output criteria to the user stories for the sprint.

Crystal Clear
Crystal was created by the anthropologist Alistair Cockburn, based on the analysis of different software development projects and his own experience. It is considered a family of methodologies, because it is subdivided into several types, depending on the number of people involved in the project.

The Crystal family has a colour code to mark the complexity of a methodology, the darker the colour, the heavier the method, the more critical a system is and the more rigour is required.

Kanban
Kanban is based on the idea that work in progress should be limited, and we should only start on something new when a previous block of work has been delivered or has moved on to another function further down the chain. The Kanban methodology uses a visual control mechanism to track work as it travels through the value stream.

Typically, a board with sticky notes or an electronic cardboard is used to manage workflow and assignments.

Mobile-D (agile and extreme mobile)
The goal of this methodology is to achieve very fast development cycles in very small teams. It is based on well-known but strictly applied mobile application development methodologies such as: extreme programming, Crystal Methodologies and Rational Unified Process.

It has different phases and each one has a planning day and a delivery day.

Exploration phase: focuses on planning and the basic concepts of the project. This is where the scope of the project and the functionalities are defined.

Initiation phase: we set up the project by identifying and preparing all the necessary resources, dedicating one day to planning and the rest to work and delivery.

Product phase: the sub-phases are repeated iteratively. Test-driven development (TDD) is used, before starting the development of a functionality there must be a test that verifies its operation. In this phase we can say that the entire implementation is carried out.

Stabilisation phase: the integration actions are carried out in order to hook the possible separate modules into a single application.

Testing phase: once the development has been completely stopped, a testing phase is carried out until a stable version is reached as established in the first phases by the client. If necessary, bugs are fixed, but nothing new is developed.

Adaptive Project Framework (AFP)
The adaptive project framework (AFP), also known as adaptive project management (APM), arose from the idea that at any stage of a project, unknown factors may arise and affect the project. This technique is mainly applied for IT projects where other traditional project management techniques do not work.

Feature Driven Development (FDD)
Feature Driven Development (FDD) methodology is aligned with agile development methodology. It is a design-oriented process, developed and refined by Jeff De Luca, Peter Coad and other contributors. It is customer-centric and is known for having short iterations and frequent releases.

Like Scrum, FDD requires the customer, also known as the business owner of the project, to attend the initial design meeting and iteration retrospectives.

By releasing new features incrementally, developers can prioritise customer requests, respond to requests in a timely manner, and keep customers satisfied.

Dynamic Systems Development Method (DSDM)
The Dynamic Systems Development Method is an agile method that focuses on the entire lifecycle of a project. This is the reason why this method has a more rigid structure and basis, unlike the other agile methods.

The 4 main phases are:

Feasibility study of the project and the company.
Iteration of the functional model or prototypes.
Design and iteration of the structure.
Implementation.

Adaptive Software Development (ASD)
Adaptive Software Development (ASD) is a methodology created by Jim Highsmith and Sam Bayer in the early 1990s. Its basis states that the normal state is the continuous adaptation of the development process to the actual work.

It has 3 stages:

Speculate: time estimates are made in the knowledge that they are subject to deviations.
Collaborate: This is the phase where most of the development is focused.
Learn: The last stage ends with a series of collaborative cycles, your job is to capture what has been learned, both positive and negative. It is a critical element of effective teams.

Unified Process (UP)
The Unified Process (UP) methodology is still being debated as an agile methodology, as it is characterised by being use-case driven, architecture-centric, iterative and incremental.

Conclusion

There are many quality assurance methodologies and models for managing software development projects, but theory differs from reality.

One of the first challenges facing companies today is to implement the agile models demanded by the market in order to be on time, with the highest quality for the end user and without increasing costs. In this post about The implementation of Quality in the Digital Transformation you have the key, for more information contact here.

Usability and UX

SIPSA_IT — Mon, 30 Jan 2023 10:26:02 +0000

At SIPSA we strive to assure the quality of software products and in order to do this we placethe end user at the heart of this quality, which is why we attach great importance to usability and user experience. In this article we are going to explain these two concepts, so closely related, but so different.

Usability and user experience are often confused because they have a similar objective: to respond as quickly and efficiently as possible to the needs posed by the user.

Definition of USABILITY

According to the International Organisation for Standardisation ISO 25010, the term "Usability" refers to the ability of the software product to be understood, learned, used, and appealing to the user, when used under certain conditions. This characteristic is further subdivided into the following sub-characteristics:

Ability to recognise its suitability: ability of the product to enable the user to understand whether the software is suitable for his needs.
Ease of learning: the ability to see how practical an application is.
Capability to be used: capability of the product that allows the user to operate and control it with ease.
User error protection: the ability of the system to protect users from making errors.
Aesthetics of the user interface: ability of the interface to be pleasing and satisfying to the user interaction.
Accessibility: the ability of the product to be used by users with certain characteristics or with certain limitations in their abilities.

The following three attributes are considered to assess usability:

Effectiveness.
Efficiency.
Degree of satisfaction.

These attributes are validated through surveys, tests, visual tracking, heat maps, etc. so as to eliminate failures that affect the achievement of the objective in a simple manner.

Usability, when interpreted from the perspective of users' personal goals, can include the kind of perceptual and emotional aspects associated with the user experience. Usability criteria can be used to evaluate aspects of the user experience.

The usability of a website, application or program is measured by how easy and intuitive it is to operate.

Definition of USER EXPERIENCE (UX)

On the other hand, according to the International Organisation for Standardisation ISO9241-21 the "User Experience (UX)" is the result of a person's perceptions and responses to the use or anticipation of the use of a product, system, or service. It is the complete experience of a person using a product, system, or service.

User experience encompasses more factors and goes one step further, referring to user satisfaction, and includes all the user's emotions, beliefs, preferences, perceptions, physical and psychological responses, behaviour and achievements that occur before, during and after use of that product, system or service. From the outcome of the user's interaction with that product, a positive or negative experience may be generated. This is the key:

The different experts of each knowledge area, not only the designers, anticipate the wishes of the users or customers and in this process are able to cover all or almost all the customer's needs.

The user experience is a consequence of the brand image, presentation, functionality, system performance, interactive behaviour and assistance capabilities of the system, the user's internal and physical state resulting from previous experiences, attitudes, skills and personality, and the context of use.

For example, if users can navigate the web easily, it has a good usability rating, as it fulfils its functional purpose. If, in addition, the experience is pleasant, comfortable, and positive, we can speak of a favourable user experience, supported by the design of the website and the navigation menu, capturing the user's attention, and making it possible for them to want to return at another time to visit that page and even recommend it to other users.

In conclusion, both concepts go hand in hand, as good usability is essential to ensure a positive user experience.

Factors that help to generate a good user experience:

Usability: refers to the user-friendliness of the user interface. If we offer a pleasant browsing experience, the user's perception will be greater. We must use colours that do not tire the eyes; avoid processes that involve long waiting times; ensure that the user achieves optimum handling of the software in the shortest possible time, etc.
Utility: all the elements of the software must have a specific purpose, aimed at meeting a user need. Revision must be constant so as to In this way, users can fulfil the objective they intended when using the product.
Trust: it is important to establish explanations in the form of a FAQ so that the user has all the necessary information at each step.
Credibility: in the case of access to websites, the content of these websites must generate credibility in the user, especially if they are an e-commerce website. This credibility will give confidence to the user and its UX will be good.
Desirability: design, aesthetics and quality multimedia content can make a product much more desirable, directly affecting a positive user experience. We will have an excellent UX if we manage, through an attractive design, to evoke emotion in the user, making it desirable for them to use the product again. This will reinforce our brand and image and will position us within the user's preferences. This is why it is essential to take this concept into account.
Ease of search: in the case of Internet users, if the content of the website is correctly structured and organised and the user finds what he/she is looking for in a few seconds, it will positively increase the UX.
Security: is fundamental regarding personal data or confidential information.
Value creation: the software product must offer value to the user, beyond the economics, meeting their expectations and highlighting what differentiates you from the competition.
Knowing the users: for us this is one of the most important concepts of UX. Before developing a software product or designing an application or website, we must know who our target users are for this product, application or website and what they are looking for... If we know what they want or what they are looking for, it will be much easier to guarantee an excellent UX. The difficulty always lies in getting right what we believe our target audience expects and for this it is advisable to study the competition to learn from their successes and mistakes.

As we said at the beginning of this post, at SIPSA we ensure the quality of software products, and we place the end user at the heart of this quality. Within our Spherical Quality methodology, we work on 3 fundamental axes:

X - axis: selection and application of quality assurance (QA) standards.

Y - axis: understanding the business environment in which the software is used and/or developed.

Z - axis: involve end-users whenever possible. When it is not, we must ensure that we know and understand their priorities and needs.

It is on this last axis, the Z-axis, that we focus on getting to know the users. To this end, we conducted a series of design thinking workshops.

Design thinking is presented as a methodology for developing people-centric innovation, offering a lens through which to observe challenges, detect needs and, finally, solve them.

It is carried out in three phases: inspiration, creation, and implementation, which take place in moderated work sessions or workshops in which the whole team participates.

These are very dynamic and graphic sessions in which we use visual tools.

We divide these workshops into 3 blocks:

Segmentation workshop: Segmentation studies the segmentation of user behaviour, dividing
them into unique groups, to analyse their needs and the main functionalities they require from the services.
Segmentation is used to group the users of the application and to identify their priorities for services and functionalities. Segmentation variables, the criteria used to segment. These are conventional variables such as demographic, geographic, behavioural or psychographic and others that determine the user's relationship with the application or service as a benefit, problem and/or added value.

User Persona workshop: The user persona allows us to move from segments to identifying/creating a series of fictitious or real people that are representative of the most common users of these segments for the application's services.
This identification provides two benefits:
It forces us to think in terms of persons, which after all are the users.
It is much easier to understand them when you identify persons rather than segments. Since segments can be measured, but people can be described.

The mechanisms for identifying the user personas of an application are:

Cross-referencing segmentation variables, cross-referencing only the most important variables.
From some of the real users. Flesh and blood people.

Once the user persona of an application has been identified, graphic cards like this one are generated:

Empathy map workshop: The empathy map is a visual tool used to get to know the perspective of a user. It allows us to access the mind of a user and get their unique perspective, so as to understand what priorities to give to the requirement, the tests, as well as the defects detected.

It allows us to visualize the impact of the application on the users identified, to understand their priorities, their needs and their likes and dislikes. It allows us to access the mind of the user and get to know their unique perspective.

For more information contact us here and we will be happy to help you without any obligation.

SIPSA | Software Quality in the Digital Era

SIPSA_IT — Wed, 25 Jan 2023 13:45:29 +0000

https://www.sipsa.net/en/

What is DevTestOps?

SIPSA_IT — Fri, 04 Nov 2022 09:00:04 +0000

Software development has had to adapt and evolve to keep up with the digital era in which we are immersed.
Companies have moved from a waterfall development model to an agile model (DevOps) to respond to the need to accelerate the software development process without neglecting the quality of the products they offer to their customers and end users.

DevOps combines development (Dev) and operations (Ops) to facilitate the integration and deployment of software updates.

In the waterfall software development lifecycle (SDLC), testing is not performed until all development is complete. If bugs are found at the end, this can delay the rollout and release, and when all the code is merged, it is more difficult to isolate and find bugs.

On the other hand, TestOps (Test Operations) is a new working methodology that offers an automated and improved version of traditional software testing. TestOps implies a greater involvement of the testing team in the process, giving them the authority to manage the entire testing process, adjusting it to their roles and needs.

What is DevTestOps and how did it come about?

DevTestOps emerged as an enhanced version of DevOps with TestOps included; it is a methodology whose main objective is to include continuous testing in the DevOps process, emphasising the importance of the testing process. In this way testers have become core members in software development and their testing activities are essential in the whole development process as well as developers and operations engineers.

Just as in DevOps the goal was to increase collaboration between developers and the operations team, with DevTestOps, this collaboration will be increased with testers. By testing at all stages of software development, quality becomes everyone’s responsibility. The product is owned by each of the team members and each of them will be involved in improving the product.

In this way, developers, testers and operations engineers will work together to improve quality, accelerate delivery and add value to the product, reducing the risk of finding bugs at later stages.

DevTestOps also requires software development companies to go beyond automation testing and embrace all types of testing during development.

DevTestOps requires greater collaboration, transparency and trust between teams. There should be no barriers to communication and teams should be self-organising and cross-functional.

Continuous testing and automation.

When we talk about continuous testing, we mean testing repeatedly throughout the process. Without automation, continuous testing would not be possible in agile methodologies. Automation allows the workflow to be agile and facilitates quick detection of errors, saves human resources, reduces execution time and ultimately helps to reduce the costs associated with error correction.

The scope of continuous testing is very broad and involves many types. Such as: unit testing, API testing, system testing, etc. all executed in a pre-production environment with automated testing.

How does DevTestOps work?

DevTestOps is a continuous improvement process, which involves several stages to achieve the expected quality of the product. These stages are:

Product management: defining and detailing requirements and their feasibility.
Software development: Analyse, design, develop and test the software.
Test management: Analysing the software specifications and designing and executing the test cases.
Continuous integration: Merging code changes into a central repository (by developers).
Continuous Deployment: Software development in sprints to ensure that the software in each sprint can be reliably released.
Continuous monitoring: the product is constantly reviewed, providing feedback and issues when the application is in production, and the team will resolve them as soon as possible.

Steps to follow:

To add continuous testing, the testers must be part of the DevOps team and test the software as soon as an update is made.
Include all the necessary tools to work effectively with them and be able to implement DevTestOps, such as: Jira, Kubernetes, Selenium, GitHub, Jenkins and others.
Teach the teams how to implement these tools.
Apply automation in each of the processes.
Update tools and processes to adapt them to technological trends.

DevTestOps Manifesto

The five main guidelines set out in it are:

Continuous testing rather than testing at the end of development.
Adopt all testing activities instead of only automated functional tests.
Test what gives value rather than testing everything.
Testing across the whole team rather than testing in isolated test departments.
Product coverage rather than code coverage.

Conclusion

DevTestOps is based on continuous integration, delivery, testing and feedback. It allows all team members to have the same understanding of the product being built. This coordinated effort is essential to develop a user-centric, high-quality product with a fast time to market.

We live in constant technological evolution and innovation and companies must continuously improve to adapt to the market and grow with it.

The DevTestOps methodology allows this continuous improvement and adaptation.

In SIPSA we have development and operations teams, in which the work done by the testers is vital so that together we can continue to offer a product in constant evolution, innovation and high quality as is TAST | Test Automation System Tool.

TAST is in continuous improvement, implementing new functionalities, adapting to the needs of our customers. To whom we offer:

our test automation tool.
our teams of expert testers in automation (TAF Test Automation Factory).
our Spherical Quality services.

SIPSA is the ally that accompanies you in the implementation of agile methodologies and the use of new tools that represent a competitive advantage to provide the quality that customers expect.

What are requirements?

SIPSA_IT — Mon, 10 Oct 2022 10:58:52 +0000

Communication is key to success in software development. Clear and well-communicated requirements help development teams to create the product requested.

When faced with requirements defined at a high level, agile methodologies can clarify and verify them sprint by sprint in an iterative way.

According to the IEEE (Institute of Electrical and Electronics Engineers) standard glossary of software engineering terminology, requirement is:

A condition or capability that a user needs to solve a problem or achieve a goal.
A condition or capability that must be achieved or possessed by a system or component of a system to satisfy a contract, standard, or other formally imposed document.
A document representation of a condition or capability as expressed in 1 or 2.

The main advantages of having good requirements specification are:

It helps to ensure that all stakeholders have a common understanding of the system to be developed. This avoids any misunderstandings during the later stages of development.
It serves as a reference point for all stakeholders during the development process.
It helps to identify any gaps in requirements at an early stage.
Reduces overall cost and development time by avoiding rework due to changes in requirements.

From the quality and testing area, the first step in understanding what we need to test is to read the documents detailing the product requirements, which set out the System Under Test (SUT). These include:

The Business Requirement Specification or Business Requirements Specification (BRS).

It contains information about the business and details about the processes to be implemented in the software and whether new functionality is required. It is a formal document, created by a business analyst, that details the requirements provided by the customer. It defines their needs. This document is used from the beginning to the end of the project.
In general, BRS contains the maximum number of concurrent users that will use the system, the types of users, the computer skills, the problems the users are currently facing. It also provides a description of the current system and possible future expansions.
The BRS also describes the deliverables or what the customer expects and describes the level of reliability expected for the software.
The BRS should not be written using overly technical terms.

The Software Requirements Specification (SRS).

An SRS is a document that provides a complete description of the behaviour of the future software or product to be developed. It is created by a systems analyst, systems architect or business analyst. It describes how the business works when the software or application is used. In this document the specifications are described in a more technical or formal way.

The Functional Requirements Specification (FRS).

The functional requirements of a system are those that describe any activity that the system must perform, i.e. the particular behaviour or function of a system or software when certain conditions are met.
Functional requirements begin by describing the required functionality as essential to the application. Functional requirements focus on end-user functionality, not on internal logic.

All these documents mentioned above help to identify what we have to test, how we have to test it and what we need to test it.

SIPSA's quality and testing teams work to achieve the highest levels of software quality, focusing on the definition of test cases from the earliest stages of the product lifecycle.

Contact us here to request more information on how we can help you in the definition and execution of the quality plan of your IT projects.