All question Just true or false question.

MVP is the final version of the product for which the users should be trained. 3 ISO 25010: 2011 is a standard that defines quality attributes for a software process, such as document formatting, roles, tasks, and diagrams. 4 In use case diagrams, > relationships stand for mandatory execution flows between use cases. 5 Portability is an example of functional requirement. 6 "Generate a report for the most sold product" is an example of a non-functional requirement. 7 Kanban is a graphical representation of work left to do versus time. 8 Traceability of software requirements is important for understanding which requirements motivated the development of a specific component. 9 An > relationship between use cases indicates that every time that a use case is executed, the other use case will also be executed. 10 Scalability is an example of a non-functional requirement. 11 Reliability is a key non-functional requirement for mission-critical systems. 12 Functional requirements answer the following : what is the system supposed to do? 13 Interviews, focal groups, naires, forms, existing material, and observations can be sources for software requirements. 14 Use cases are short descriptions of how users will use a system, which will be further expanded when the use cases will be implemented, while user stories focus on specifying in detail the user interaction with the system. 15 The description of a user story is usually more detailed than the description of a use case. 16 The minimum viable product (MVP) is used to validate a product proposal. 17 Actors in the Use Case diagram represent the execution threads of the system. 18 Performance is a key non-functional requirement for real-time systems. 19 A verifiable non-functional requirement is a statement about the product using a measurement that can be objectively tested