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 (65) , REFERENCE & LEARNING (8) , NEWS (19) , 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 65
SOFTWARE REQUIREMENTS TECHNIQUES (PROTOTYPING, STORYBOARDS, MODELING, STATE TRANSITIONS) EXPERTS
Betty Luedke
requirements practice manager
ASK A QUESTION
Robin F. Goldsmith
president
ASK A QUESTION
When it comes to requirements, what is 'just enough'?
10 Sep 2009
EXPERT ANSWER - Find out how to check requirements to find out if they fit users' needs without going overboard.
Defining report requirements with use cases
09 Sep 2009
TIP - This tip offers a new and interesting way to go about defining and reporting requirements for use cases.
How requirements use cases facilitate the SDLC
09 Sep 2009
TIP - Learn software use case processes and techniques that result in better application requirements in this tip. Takeaways are use case diagrams and user acceptance test case examples.
VIEW ALL EXPERT TECHNICAL ADVICE ON SOFTWARE REQUIREMENTS TECHNIQUES (PROTOTYPING, STORYBOARDS, MODELING, STATE TRANSITIONS)

  REFERENCE & LEARNING: 1 - 3 of 8
Excelling in the art and science of requirements elicitation
22 Jul 2009
PODCAST - Eliciting software requirements is a human-intensive activity. Learn techniques to make the right choices in eliciting and then analyzing requirements needs.
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 - Find out when use cases are a good fit for software projects, when they are not, and what alternative approaches should be used.
VIEW ALL REFERENCE & LEARNING ON SOFTWARE REQUIREMENTS TECHNIQUES (PROTOTYPING, STORYBOARDS, MODELING, STATE TRANSITIONS)

  NEWS: 1 - 3 of 19
Requirements practices evolving, but organizations still struggle
SearchSoftwareQuality | 16 Nov 2009
ARTICLE - Requirements elicitation causes software development teams' some of their toughest problem today, according to a Tech Target survey.
Why business analysts are application development key players today
SearchSoftwareQuality | 27 Oct 2009
INTERVIEW - Tight budgets, agile development and other economic factors have pushed business analysts into application requirements elicitation and testing.
GatherSpace beefs up cloud-based requirements management
SearchSoftwareQuality.com | 24 Aug 2009
ARTICLE - GatherSpace version 2 is now available and continues to offer low-cost software requirements gathering technology, that is easily learned and easily implemented.
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