Timeline for Functional or non-functional requirement?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2013 at 7:24 | comment | added | Arseni Mourzenko | @AramKocharyan: that's why I said that we don't know whether this statement is a requirement at all. | |
| Jun 16, 2013 at 5:35 | comment | added | Aram Kocharyan | I'd argue "The application is written in C#." is a constraint, not a functional requirement, since it doesn't describe the behaviour of the system but ascribes a limitation to the solution space. | |
| Nov 8, 2011 at 15:38 | history | edited | Arseni Mourzenko | CC BY-SA 3.0 |
deleted 1 characters in body
|
| Nov 8, 2011 at 6:23 | comment | added | Arseni Mourzenko | @Emmad Kareem: you're right. I limit myself to purely technical requirements, i.e. the requirements that would be used by developers and QA. For business analysts, things are slightly different, and some elements that I qualified as not being requirements would in fact be perfectly valid ones. | |
| Nov 8, 2011 at 6:20 | history | edited | Arseni Mourzenko | CC BY-SA 3.0 |
added 1406 characters in body
|
| Nov 8, 2011 at 6:19 | comment | added | NoChance | +1 for details. I kind of disagree with your opinion in (1), you say "this is not a requirement". I think it is a requirement but the business analyst has to make it a "measurable" requirement before the team is committed to it. I also liked your usage of the word "wish" and your distinction between "wishes" and "requirements" | |
| Nov 8, 2011 at 6:02 | history | answered | Arseni Mourzenko | CC BY-SA 3.0 |