For Prioritization we use Moscow Technique and Validation we use FURPS technique.
MoSCow is also termed as Moscow prioritization or Moscow analysis It plays a vital role in business analysis and software development in understanding stakeholders on the importance they give on each requirement.
MoSCow stands for:
M – MUST: a requirement that must satisfy in the final solution for the solution to be considered a success.
S – SHOULD: a high-priority item that should be included in the solution if it is possible.
C -COULD: a requirement which is considered desirable but not necessary. It is included if time and resources permit.
W – WON’T: a requirement that stakeholders have agreed will not be implemented in release, but may be considered for the future.
Priority of MoSCoW requirements:
Requirements are prioritized to deliver the greatest and immediate business benefits.
Developers deliver all M, S ,C requirements but the S and C requirements will be the first to move if the delivery timescale is hazardous.
MoSCoW helps the customers to understand what activities are done during prioritization also attaching priority, like high, medium and low.
Must requirements are critical for project success and have to be included in the current delivery time zone. If at least one MUST requirement is not included, the project delivery may be a failure.
Should requirements leads to project success, but are not necessary for delivery of the project.
Could requirements are less critical
Won’t requirements are least-critical and are not appropriate at that time.
Functionality deals with product features, attributes that bear on the existence of a set of functions and their specified properties.
Usability deals with attributes such as logic, uniformity in the user interface, on the capability of software to maintain its level of performance under stated conditions for a stated period of time.
Reliability deals with attributes such as availability, accuracy of system calculations, and recovery from failure, capability of software to maintain its level of performance under stated conditions for a stated period of time.
Performance deals with attributes such as throughput, response time, recovery time, start-up time, and shutdown time.
Supportability deals with attributes such as testability, adaptability, maintainability, compatibility, configurability, install ability, scalability, and localizability.Tags: Requirements