![]() ![]() A quality attribute scenario is an unambiguous way to specify a testable quality attribute. To define a tangible quality attribute, a good starting point is to write a quality attribute scenario. This allows teams responsible to implement certain tasks to know when they did a good job, according to some stakeholders, to complete that requirement. ![]() First of all, all quality attributes must be measurable in some way. Everyone is going to say it must be secure - whatever that means.īut those situations can be avoided with some work and preparation. He would probably say, “the minimum time possible.” Most of the time they are implicit or said without much thought behind them.Ī real-world example is if you’re in charge of developing certain features and you ask your boss about the time that the system should take to complete a task. They're only verbally said alongside functional requirements. Quality attributes, most of the time, are not written. An example of a QA is how fast the function must be performed or how resilient it must be to an erroneous input, the time to deploy the product, or a limitation on operational costs. In other words, a quality attribute (aka as Non-Functional Requirements) is what makes a system good with respect to a specific stakeholder. A quality attribute ( QA) is a measurable or testable property of a system that is used to indicate how well the system satisfies the needs of its stakeholders. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |