About Quality of Service Requirements

It seems like the quality of service requirements are really important for the MSF Agile process. I'm reading the guidance, but I just don't get the idea of this work items. Can anybody give me examples of quality of service requirements and the way the would be handled in the MSF Agile process? How do you discover them? How do the have to be developed? What has to do the developer with them? How do they fit in the general project schedule?

Thanks.

[457 byte] By [JulioCasalT.] at [2008-2-15]
# 1

Our quality of service requirement format was inspired by Jeromy Carriere. It takes the form of <<context>> <<stimulus>> and <<response>> such as "During a catalog search, return the search results in under 3 seconds." There are other forms such as deployment platform that are simple lists.

Randy
MSF

RandyMiller at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Visual Studio Team System - Microsoft Solutions Framework (MSF)...
# 2
Check out my blog on LAAAM from a few weeks ago. I elaborate a bit on the scenario-driven approach to identify quality attributes (aka quality of service requirements) in the context of a utility tree, as inspired by the ATAM method from the SEI.

Generally the process of collecting an appropriate set of scenarios requires a large stakeholder group donig brainstorming. The utility tree provides the context, but each stakeholder should reflect their specific perspective as one or more scenarios - developers, testers, operations staff, users, project managers, etc. all provide their input via scenarios.

See the sidebar on pages 54-55 of "Evaluating Software Architectures" for an interesting treatment of scenarios. Also see Step 7 "Brainstorm and Prioritize Scenarios" of the ATAM method on page 59 of the book.

JeromyCarriere at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Visual Studio Team System - Microsoft Solutions Framework (MSF)...

Visual Studio Team System

Site Classified