|
| 1 - 10 of 18 in Expert Technical Advice |
|
<< Previous page 1 2 Next >> |
|
|
|
Approaches to defining requirements within Agile teams
Submitted By: SearchSoftwareQuality.com | 24 Apr 2008
TIP - Agile development methods focus on defining "just enough" requirements detail for the next sprint. Martin Crisp explains three things to consider when eliciting those requirements.
|
|
|
Defining good performance requirements a joint effort
Submitted By: SearchSoftwareQuality.com | 28 Mar 2008
TIP - When dealing with performance requirements you need to look at a bigger picture -- one that includes business, operations and development organizations.
|
|
|
Quality software performance doesn't happen accidentally
Submitted By: SearchSoftwareQuality.com | 14 Feb 2008
TIP - If you want quality software performance, you must specify it. With performance requirements you can address concerns for efficiency, interoperability, robustness and testability.
|
|
|
Software requirements: Wish vs. need
Submitted By: SearchSoftwareQuality.com | 06 Feb 2008
TIP - Analysts have to clearly define the distinction between the wishes and needs of the system when gathering requirements.
|
|
|
Mind maps show project relationships
Submitted By: SearchSoftwareQuality.com | 30 Aug 2007
TIP - While not a substitute for formal software requirements processes, mind maps can provide a visual representation to make a project come alive to developers.
|
|
|
Software requirements: A picture is worth a thousand words
Submitted By: SearchSoftwareQuality.com | 30 Aug 2007
TIP - By creating a diagram based on the end user's description of what the completed system would look like, you can better identify specific requirements for the software or system.
|
|
|
How a business analyst can help on a software project
Submitted By: SearchSoftwareQuality.com | 20 Aug 2007
TIP - Business analysts not assigned a primary role in software requirements development are still valuable. Using their skills and experience they can smooth the requirements dialogue.
|
|
|
Using card sorting to decide software requirements
Submitted By: SearchSoftwareQuality.com | 17 Jul 2007
TIP - Indecision can arise in the software requirements phase when a team is deciding what field type and process should surround the field information. Card sorting can mitigate that.
|
|
|
Tuning up your software requirements reviews
Submitted By: SearchSoftwareQuality.com | 13 Jul 2007
TIP - The most powerful software quality practice today is inspection of software requirements documentation. The problem is most organizations don't do them or do them badly.
|
|
| 1 - 10 of 18 in Expert Technical Advice |
|
<< Previous page 1 2 Next >> |
|
|
|
|
|
