Software Requirements Documentation

NEWS: 1 - 3 of 6

	Software requirements sign-off essential for solid QA SearchSoftwareQuality.com | 04.11.2008 OPINION - Not properly signing off on a software project's requirements limits the quality assurance (QA) team's ability to ensure that the software does as it's intended.

	Poor business requirements process leads to high project costs, study finds SearchSoftwareQuality.com | 21 Feb 2008 ARTICLE - A recent IAG Consulting study finds that companies that have poor business requirements processes can expect to spend 49% more money and 39% more time on a project.

	From use case diagrams to context diagrams SearchSoftwareQuality.com | 01 Nov 2007 ARTICLE - It's tempting to consider use case diagrams as context diagrams because they do show context. But having one diagram for both will result in an unreadable cloud of bubbles.

	VIEW ALL NEWS ON SOFTWARE REQUIREMENTS DOCUMENTATION

EXPERT TECHNICAL ADVICE: 1 - 3 of 15

SOFTWARE REQUIREMENTS DOCUMENTATION EXPERTS
			Roxanne Miller principal and lead instructor ASK A QUESTION

	Requirements discipline throughout the SDLC 31 Mar 2008 EXPERT ANSWER - Requirements documentation varies throughout the software development life cycle. Expert Roxanne Miller explains how requirements activities and artifacts fit into the SDLC.

	Testability requirements and verification work 25 Mar 2008 EXPERT ANSWER - Testability and verifiability are a category of nonfunctional requirements. Expert Roxanne Miller explains how these concepts fit into software requirements engineering.

	Software requirements elicitation and documentation 05 Feb 2008 EXPERT ANSWER - Eliciting software requirements from clients is more important than complete documentation. Expert Rob Apmann explains how to effectively gather requirements.

	VIEW ALL EXPERT TECHNICAL ADVICE ON SOFTWARE REQUIREMENTS DOCUMENTATION

BEST WEB LINKS: 1 - 2 of 2

	Writing software requirements specifications TECHWR-L | 12 Feb 2007 BEST WEB LINK - For the uninitiated, this is a through introduction to software requirements specifications. Learn what SRSs are, why they are important and how to write them. There are tables and examples throughout.

	Requirements based development IT-Director.com | 18 Dec 2006 BEST WEB LINK - Translating business requirements into functional requirements is often a tricky process, the author points out. This short article suggests a means for improvement: Compuware's Optimal Trace. More than a simple product ...

	VIEW ALL BEST WEB LINKS ON SOFTWARE REQUIREMENTS DOCUMENTATION

DEFINITIONS: 1 - 3 of 5

	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 ...

	Wirth's Law 20 Mar 2007 WORD - Wirth's Law states that computer software increases in complexity faster than does the ability of available hardware to run it. Another way of stating this is "Software slows down faster than hardware speeds up." ...

	software requirements specification 14 Feb 2007 WORD - A software requirements specification (SRS) is a comprehensive description of the intended purpose and environment for software under development. The SRS fully describes what the software will do and how it will be expected ...

	VIEW ALL DEFINITIONS ON SOFTWARE REQUIREMENTS DOCUMENTATION

	SEE ALSO - Topics Related to Software Requirements Documentation:  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)