Reasons for Importance of Usability Testing in Real-Time Embedded Systems
What meaning of a Usability software testing?
The usability testing is using in mostly based on the experience of using the system.
I choose this subject as a result of the professional debate in my job with one of the project managers.
The reason for the professional debate was our different approach to usability testing in real-time systems.
The source to the debate was a standard professional interview with the tester.
One of job interview questions was: “Please, Describe all types of test cases to elevator” (it includes such test types as sanity, functional, regression, load, performance and etc.’
The candidate returned test cases from all types of tests and I thought it was enough for me.
Suddenly a project manager asked him: “What’s about the test to air condition?” After all, with no air condition what the value of the lift, the air condition is a classic example of user experience…
If are you asking yourself, why is aroused the professional debate?
Important to say that most of my career was in real-time systems.
The main emphasis in these tests is the testing of complex processes, algorithms, and less user experience because development approach is “the user should know what he is doing”.
Maybe is it correct approach …
Real-time systems, the user really should know what he is doing but is this unequivocal approach.
I think that these systems have a gradual change on this issue, as you can see the part of improvements that understanding that users should be involved early in requirements stage and even should be as part of testing process.
In addition, many projects share the software ergonomics and a professional designer in the early stages of development.
Why is it so important to “user experience”?
See development practice…
This is what the end user sees the development of a product and the user works with the system daily.
Just think about it! If you are working on a system of any kind and something is not intuitive, what happened as a result?
In the beginning, it bothers you, then begins to irritate and can finally be discouraged and eventually even stop using the system.
Have you ever seen the end of such software systems?
I got to know systems where end users were not involved in the characterization and design. A s a result after version release to production, I’d hear comments like: “The system is not Intuitive at all …” Etc…
I think such kind of tests is so important for each project because at the end user use the system daily.
What other reasons for not using the software system? Tell what you know from your professional experience😃
Is this article helpful for you? Tell everyone how it helped you