Home > Software Quality Topics > Software Requirements > Software requirements techniques (Prototyping, Storyboards, Modeling, State transitions)
Software Quality Topics:
EMAIL THIS
 TOPICS HOME   BROWSE ALL SOFTWARE QUALITY TOPICS   SOFTWARE QUALITY INFO CENTERS   RESOURCE CENTERS     RSS FEEDS 

Software requirements techniques (Prototyping, Storyboards, Modeling, State transitions)


Tips and advice about software requirements techniques, such as prototyping, storyboards, modeling and state transitions, to help software development teams create secure, quality software.
IN THIS TOPIC:  EXPERT TECHNICAL ADVICE (60) , REFERENCE & LEARNING (7) , NEWS (16) , DEFINITIONS (1)

MUST READ
Top 10 software requirements tips
FAST GUIDE - Developing quality software starts with the requirements process. These software requirements tips can prevent the process from failing, thus preventing failed projects.
How to avoid requirements creep
TIP - A different approach to defining requirements can help curtail the creep that still plagues software projects.
Making requirements walkthroughs more effective (and fun)
TIP - Do you have to twist arms to get people to attend your requirements review sessions? Learn how a simulation model can get everyone engaged in the walkthrough.
Using proactive test design methods to catch requirements issues early
TIP - Proactive test design allows QA testers to identify requirements problems at an earlier stage than with traditional test cases.
Pros and cons of requirements-based software testing
TIP - Learn about the strengths and benefits of requirements-based testing as well as what the detractors say -- mostly based on incorrect assumptions about requirements.

  EXPERT TECHNICAL ADVICE: 1 - 3 of 60
SOFTWARE REQUIREMENTS TECHNIQUES (PROTOTYPING, STORYBOARDS, MODELING, STATE TRANSITIONS) EXPERTS
Betty Luedke
requirements practice manager
ASK A QUESTION
Robin F. Goldsmith
president
ASK A QUESTION
Quality assurance (QA) and testing's role in requirements
14 Apr 2009
TIP - Common wisdom is to include QA/testing early in the life cycle, but this actually has hidden pitfalls that can reduce the effectiveness of the requirements process.
Pros and cons of requirements-based software testing
Submitted By: SearchSoftwareQuality.com | 17 Feb 2009
TIP - Learn about the strengths and benefits of requirements-based testing as well as what the detractors say -- mostly based on incorrect assumptions about requirements.
How to avoid requirements creep
Submitted By: SearchSoftwareQuality.com | 22 Jan 2009
TIP - A different approach to defining requirements can help curtail the creep that still plagues software projects.
VIEW ALL EXPERT TECHNICAL ADVICE ON SOFTWARE REQUIREMENTS TECHNIQUES (PROTOTYPING, STORYBOARDS, MODELING, STATE TRANSITIONS)

  REFERENCE & LEARNING: 1 - 3 of 7
Mastering key requirements phases
08 Jul 2009
PODCAST - Consultant Robin F. Goldsmith describes the key phases in a successful software requirements process in this audiocast interview.
Software requirements: Moving beyond use cases
08 Jul 2009
PODCAST - In this podcast, expert Ellen Gottesdiener describes when use cases are a good fit for software projects, when they are not, and what alternative approaches should be used.
Agile software development tutorial: Agile requirements gathering
SearchSoftwareQuality.com |
TUTORIAL - In this section of our agile development tutorial, learn tips and techniques for defining and gathering requirements in an agile environment.
VIEW ALL REFERENCE & LEARNING ON SOFTWARE REQUIREMENTS TECHNIQUES (PROTOTYPING, STORYBOARDS, MODELING, STATE TRANSITIONS)

  NEWS: 1 - 3 of 16
Software development lifecycle (SDLC) trends 2009: Requirements, agile
SearchSoftwareQuality.com | 05 Jan 2009
ARTICLE - Read expert predictions on what's in store this year for software development lifecycle practices and who will best weather the economic storm.
Business analysis skills you need for successful software requirements
SearchSoftwareQuality.com | 12 Nov 2008
INTERVIEW - Business analysts must have certain skills and must understand the many software requirements techniques out there, says the author of "Seven Steps to Mastering Business Analysis."
Agile aims to bridge software requirements communications gap
SearchSoftwareQuality.com | 22 Oct 2008
ARTICLE - Agile practitioners say agile software development bridges the software requirements communications gap by embracing flexibility and face-to-face communication.
VIEW ALL NEWS ON SOFTWARE REQUIREMENTS TECHNIQUES (PROTOTYPING, STORYBOARDS, MODELING, STATE TRANSITIONS)

  DEFINITIONS: 1 - 1 of 1
requirements analysis
23 Mar 2007
WORD - Requirements analysis, also called requirements engineering, is the process of determining user expectations for a new or modified product. These features, called requirements, must be quantifiable, relevant and detailed. In ...
VIEW ALL DEFINITIONS ON SOFTWARE REQUIREMENTS TECHNIQUES (PROTOTYPING, STORYBOARDS, MODELING, STATE TRANSITIONS)

SEE ALSO - Topics Related to Software requirements techniques (Prototyping, Storyboards, Modeling, State transitions): 
Threat modeling, Use cases and misuse cases, Software requirements tools, Building security into the SDLC (Software development life cycle), Software Requirements Documentation



Software Quality Solutions - Software requirements techniques (Prototyping, Storyboards, Modeling, State transitions) White Papers

About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




All Rights Reserved, Copyright 2006 - 2009, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts