Requirements and Quality Management Flashcards
What is quality in a product?
Software quality is defined from different points of view, that all have different interests Each of these quality factors should be clearly defined(by requirements), prioritized(by the customer) and made measurable(by the customer and developers):
The 3 stakeholders in software quality are Sponsors, Users and Developers.
User are interested in functional quality - that the software performs the tasks it is meant to
Developers and sponsors are interested in not only functional quality, but also structural quality and process quality.
What are functional and non-functional requirements and what do we use them for?
Functional requirements define the features necessary for the actors to be able to fulfill their goals/tasks, while non-functional requirements define how these features should work to provide the most satisfactory experience for the actor.
Combined, we use them to develop a system that works to fulfill the tasks that the customer needs in a way that works for the users.
How do we test whether they are fulfilled?
Functional requirements can be measured by establishing acceptance criteria for each step in the fully dressed use case for example:
- user should be able to input an email, phone number, address and name
- at least name and phone number has to be entered
- (min and max requirements for length of input)
Non-functional requirements acceptance criteria needs to individually defined based on priority and context. These are then tested accordingly. Non-functional requirements like performance and security are measured without involving users, while all usability criteria, needs to be tested using usability tests involving users of the system. Therefore, it is important that individual acceptance criteria are defined for each non-functional requirement that are prioritized within the development process.
