Professional Documents
Culture Documents
Assurance
Teacher: Elia Ornelas
What is QA?
Software quality assurance (QA) ensures that customers receive a product of the highest
caliber and up to their standards. Finding any design or development flaws, errors, or
failures that may have gone unnoticed during the design or development of a software
application is the process's main goal.
Software application
In software engineering, we can apply this QA to assure that the product is well developed,
without mistakes or bad practices that can affect the software.
This test aren’t made by everyone on the develop team, this are just made by the QA
engineer whose tasks are creating bug reports, writing test cases, testing applications. But
this is not his main objective, there are other task even more important that the mentioned
before.
The first one is:
Validation
• He has the last word on the project, he decides if the project is good to go or if it
needs more work, he basically has the las decision when making an app
Study
• He need to do a lot of research about technology topics, this means that he is
normally looking and searching for new ways to make a test, how the software
should be developed, and new tools to make his work in an effective way
Why is QA important?
Once the application is developed, its’s a common thing that it has a lot of bugs, issues
or bad functionality. Software testers are involved as the testing phase begins to reduce
the likelihood of such faults happening in the production environment. Early detection
of flaws and problems ensures that the provided software is high-performing and
customer-satisfying.
Security
Another main task of QA is to ensure the security of the application, this means that
every single part of the app is well protected by making the protocols on the different
modules. For example, is an “easy” thing to make injections to the DB, so QA must make
sure that the DB team prevented this.
Metrics
1. Accuracy Metrics: They aim to provide information about the validity and accuracy
of the software and its structure, including the deployment stage, but also the
testing and maintenance phase.
2. Performance Metrics: Through these, the performance of the software is
measured, both for each of its modules and for the system as a whole.
Conclusion
It is true that must of the software developers does not take on consideration these types
of tools or metric when creating a new application or software. Now I have learned that
this has been created to accomplish a task and make our lives and develop easier.
I think it is really interesting the usability metric, that is the one that I would use more,
because the one that has the last word is the final user, if everything is well developed,
that wouldn’t be a problem so I would make a lot of usability test to ensure everything is
well developed.