Software requirements analysis is the activity of eliciting, analyzing, and recording requirements for software systems. It overlaps with requirements-related issues for more general kinds of systems, but has its own specific approaches. It has been suggested that Software development life cycle be merged into this article or section. ... Software architecture or software systems architecture can best be thought of as a representation of an engineered (or To Be Engineered) software system, and the process and discipline for effectively implementing the design(s) for such a system. ... Software Testing is a process used to help identify the correctness, completeness, security and quality of developed computer software. ... This article needs to be wikified. ... Agile software development is a conceptual framework for undertaking software engineering projects. ... Iterative and Incremental development is a software development process, as opposed to more traditional waterfall model. ... Rapid application development (RAD), is a software development process developed initially by James Martin in the 1980s. ... The Rational Unified Process (RUP) is an iterative software development process created by the Rational Software Corporation, now a division of IBM. The RUP is not a single concrete prescriptive process, but rather an adaptable process framework. ... The spiral model is a software development process combining elements of both design and prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts. ... The waterfall model is a software development model (a process for the creation of software) in which development is seen as flowing steadily downwards (like a waterfall) through the phases of requirements analysis, design, implementation, testing (validation), integration, and maintenance. ... To meet Wikipedias quality standards, this article or section may require cleanup. ... Software Configuration Management (SCM) is part of configuration management (CM). ... To meet Wikipedias quality standards, this article or section may require cleanup. ... Project Management is the discipline of defining and achieving targets while optimizing the use of resources (time, money, people, materials, energy, space, etc) over the course of a project (a set of activities of finite duration). ... A requirement is a singular documented need of what a particular product should be or do. ...

Eliciting Requirements

Requirements elicitation is the task of communicating with customers and users to determine what their requirements are.

Analyzing Requirements

The true analysis part of requirements analysis locates places where requirements are unclear, incomplete, ambigious, or contradictory. Requirements analysts work with customer representatives to resolve these issues, sometimes preparing tradeoff studies to compare alternatives. Look up Analysis in Wiktionary, the free dictionary An analysis is a critical evaluation, usually made by breaking a subject (either material or intellectual) down into its constituent parts, then describing the parts and their relationship to the whole. ... A Tradeoff usually refers to losing one quality or aspect of something in return for gaining another quality or aspect. ...

Recording Requirements

The classic Waterfall process recorded requirements in large natural language documents. The waterfall model is a software development model (a process for the creation of software) in which development is seen as flowing steadily downwards (like a waterfall) through the phases of requirements analysis, design, implementation, testing (validation), integration, and maintenance. ...

Processes based on the Unified Modeling Language record requirements as use cases. The Unified Modeling Language (UML) is a non-proprietary, object modeling and specification language used in software engineering. ... In software engineering, a use case is a technique for capturing the potential requirements of a new system or software change. ...

Extreme programming records requirements as user stories. To meet Wikipedias quality standards, this article or section may require cleanup. ... User Story In the eXtreme Programming (XP) methodology, a User Story is a way for customers to communicate, to the programmers, functionality that they would like to see in a product. ...

External links

searching for currently-used textbooks