{"id":7708,"date":"2023-06-05T12:40:02","date_gmt":"2023-06-05T10:40:02","guid":{"rendered":"https:\/\/spiritinprojects.com\/usability-engineering-a-useful-addon-for-requirements-engineers\/"},"modified":"2023-06-24T13:13:46","modified_gmt":"2023-06-24T11:13:46","slug":"usability-engineering-a-useful-addon-for-requirements-engineers","status":"publish","type":"post","link":"https:\/\/spiritinprojects.com\/en\/usability-engineering-a-useful-addon-for-requirements-engineers\/","title":{"rendered":"Usability Engineering – a useful addon for requirements engineers"},"content":{"rendered":"\n

Requirements analysts will find it worth their while to make a quick detour in the direction of UX\/UI, since user interfaces are what essentially determine a solution’s acceptance.<\/strong><\/p>\n\n

No, usability engineering is not concerned with making graphical interfaces pretty. Yes, requirements engineers, especially those involved with applications for end customers or applications with a large number of internal users, should always be concerned with usability engineering.<\/p>\n\n

UX Challenges in Requirements Management<\/h2>\n\n

An increasingly growing challenge for requirements engineers is to functionally describe applications<\/strong> which not only claim to be correct and efficient, but also easy to learn<\/strong> (ideally no initial training at all is required), clear and understandable to users, fault-tolerant, not just for bad input but also for incorrect use, and finally attractive and helpful<\/strong> to users as a whole.<\/p>\n\n

A pretty user interface is just one aspect involved in the understandability, operability, clarity, learnability and attractiveness of a system. Although the design of this aspect is the responsibility of the user interface designer, the process is actually carried out using traceable methods, and also requires taste and a touch of artistic design<\/strong> throughout.<\/p>\n\n

The Solution: Usability Engineering<\/h2>\n\n

However, usability engineering is concerned with deriving and optimizing a system\u2019s functional and non-functional characteristics by examining the user\u2019s overall environment<\/strong>. Another aspect is to model the entire user journey<\/strong> and include it in system design. For example, a web shop user\u2019s experience with that system doesn\u2019t end when he places an order, but continues until he receives the package or support for his complaints.<\/p>\n\n

In requirements engineering, we set ourselves apart (completely intentionally) from the environment not directly associated with the system, which we already learned already over the course of creating context diagrams. This allows us, but sometimes only with difficulty, to understand the user’s motives behind individual activities<\/strong>. In addition, requirements engineering does not examine user satisfaction over the entire use life cycle (nor beyond system limits).<\/p>\n\n

Methods of requirements engineering and usability engineering complement each other perfectly in this area, and create real added value for many tasks. Spirit in Projects’ training portfolio offers basic and advanced courses for both directions, so you can selectively expand your own skill set.<\/strong><\/p>\n\n

\n\n

Learn more about our trainings on UX\/UI:<\/h2>\n
\"Trainings<\/a>

Usability Testing and Evaluation<\/a><\/h3><\/span><\/header><\/div>