A Snow Card, identifies a number of attributes that together compose one atomic requirement. If you are using the snowcard method, it would be a better idea to expand the high-level requirements (e.g, the search feature example you gave), in order to get atomic requirements. If there are too many atomic requirements, you may want to group them but in that case a better way to represent them is a use case.

"Adrian Borthwick" [email protected] wrote:

Hi Mehwish

For part 2 of the assignment, I was wondering how we would count the number of requirements required.

From the lecture snowcards (slide 14 lect 3a) it gives an example of a requirement " the product shall have a search facility".

This requirement is quite broad, and there may be additional more specific sub requirements/specifications for this, such as:

• the product shall allow searching by fields including artists, song name, album, year,
• or the search function will include a history of searches,
• or the search function will allow the user to choose which music library to search.
• or the search function may sort by price of the song.

So just wondering - Does the search facility count as 1 requirement with multiple specifications? Or is each specification counted as 1 requirement with a snow card for each.
Adrian.