Requirements analysis

From Wikipedia, the free encyclopedia

In systems engineering and software engineering, requirements analysis encompasses all of the tasks that go into the instigation, scoping and definition of a new or altered system. Requirements analysis is an important part of the system design process, whereby requirements engineers and business analysts, along with systems engineers or software developers, identify the needs or requirements of a client. Once the client's requirements have been identified, the system designers are then in a position to design a solution.

Requirements analysis is also known under other names:

  • requirements engineering
  • requirements gathering
  • requirements capture
  • operational concept documenting
  • systems analysis
  • requirements specification

Contents

[edit] Main techniques

Conceptually, requirements analysis includes three types of activity:

  • Eliciting requirements: the task of communicating with customers and users to determine what their requirements are.
  • Analyzing requirements: determining whether the stated requirements are unclear, incomplete, ambiguous, or contradictory and resolving these issues.
  • Recording requirements: Requirements may be documented in various forms, such as natural-language documents, use cases, or user stories, process specifications.

Requirements analysis can be a long and arduous process and lots of delicate psychological skills are involved. New systems change the environment and relationships between people, so it is important to identify all the stakeholders, take into account all their needs and ensure they understand the implications of the new systems. Analysts can employ several techniques to elicit the requirements from the customer. Historically, this has included such things as holding interviews, or holding focus groups (more aptly named in this context as requirements workshops - see below) and creating requirements lists. More modern techniques include prototyping, and use cases. Where necessary, the analyst will employ a combination of these methods to establish the exact requirements of the stakeholders, so that a system that meets the business needs is produced.

[edit] Stakeholder interviews

Stakeholder interviews are a common method used in requirement analysis. Some selection is usually necessary, cost being one factor in deciding whom to interview. These interviews may reveal requirements not previously envisaged as being within the scope of the project, and requirements may be contradictory.

[edit] Requirement workshops

In some cases it may be useful to gather stakeholders together in "requirement workshops". These workshops are more properly termed Joint Requirements Development (JRD) sessions, where requirements are jointly identified and defined by stakeholders.

It may be useful to carry out such workshops in a controlled environment, so that the stakeholders are not distracted. A facilitator can be used to keep the process focused and these sessions will often benefit from a dedicated scribe to document the discussion. Facilitators may make use of a projector and diagramming software or may use props as simple as paper and markers. One role of the facilitator may be to ensure that the weight attached to proposed requirements is not overly dependent on the personalities of those involved in the process.

[edit] Contract-style requirement lists

One traditional way of documenting requirements has been contract style requirement lists. In a complex system such requirements lists can run to hundreds of pages.

[edit] Measurable goals

Best practices (see Competitive Engineering) take the composed list of requirements merely as clues and ask why, repeatedly, until the actual business purposes are discovered. Then stakeholders and developers can devise tests to measure what level of each goal has been achieved so far. These goals change more slowly than the long list of specific but unmeasured requirements. Once the small set of critical, measured goals has been established, rapid prototyping and short iterative development phases may proceed to deliver actual stakeholder value long before the project is half over.

[edit] Prototypes

Main article: Prototyping

In the mid-1980s, prototyping became seen as the solution to the requirements analysis problem. Prototypes are mock ups of the screens of an application which allow users to visualize the application that isn't yet constructed. Prototypes help users get an idea of what the system will look like, and make it easier for users to make design decisions without waiting for the system to be built. Major improvements in communication between users and developers were often seen with the introduction of prototypes. Early views of the screens led to fewer changes later and hence reduced overall costs considerably.

However, over the next decade, while proving a useful technique, it did not solve the requirements problem:

  • Managers once they see the prototype have a hard time understanding that the finished design will not be produced for some time.
  • Designers often feel compelled to use the patched together prototype code in the real system, because they are afraid to 'waste time' starting again.
  • Prototypes principally help with design decisions and user interface design. However, they can't tell you what the requirements were originally.
  • Designers and end users can focus too much on user interface design and too little on producing a system that serves the business process.

Prototypes can be flat diagrams (referred to as 'wireframes') or working applications using synthesized functionality. Wireframes are made in a variety of graphic design documents, and often remove all color from the software design (i.e. use a greyscale color palette) in instances where the final software is expected to have graphic design applied to it. This helps to prevent confusion over the final visual look and feel of the application.

[edit] Use cases

Main article: Use case

A use case is a technique for documenting the potential requirements of a new system or software change. Each use case provides one or more scenarios that convey how the system should interact with the end user or another system to achieve a specific business goal. Use cases typically avoid technical jargon, preferring instead the language of the end user or domain expert. Use cases are often co-authored by software developers and end users.

Use cases are deceptively simple tools for describing the behavior of the software. A use case contains a textual description of all of the ways which the intended users could work with the software through its interface. Use cases do not describe any internal workings of the software, nor do they explain how that software will be implemented. They simply show the steps that the user follows to use the software to do his work. All of the ways that the users interact with the software can be described in this manner.

During the 1990s, use cases have rapidly become the most common practice for capturing functional requirements. This is especially the case within the object-oriented community where they originated, but their applicability is not restricted to object-oriented systems, because use cases are not object-oriented in nature.

Each use case focuses on describing how to achieve a single business goal or task. From a traditional software engineering perspective, a use case describes just one feature of the system. For most software projects, this means that perhaps tens or sometimes hundreds of use cases are needed to fully specify the new system. The degree of formality of a particular software project and the stage of the project will influence the level of detail required in each use case.

A use case defines the interactions between external actors and the system under consideration to accomplish a business goal. Actors are parties outside the system that interact with the system; an actor can be a class of users, a role users can play, or another system.

Use cases treat the system as a "black box", and the interactions with the system, including system responses, are as perceived from outside the system. This is deliberate policy, because it simplifies the description of requirements and avoids the trap of making assumptions about how this functionality will be accomplished.

A use case should:

  • describe a business task to serve a business goal
  • be at an appropriate level of detail
  • be short enough to implement by one software developer in a single release

Use cases can be very good for establishing functional requirements, but they are not suited to capturing Non-Functional Requirements. However Performance Engineering specifies that each critical use case should have an associated performance oriented non-functional requirement.

[edit] Software requirements specification

A software requirements specification (SRS) is a complete description of the behavior of the system to be developed. It includes a set of use cases that describe all of the interactions that the users will have with the software. Use cases are also known as functional requirements. In addition to use cases, the SRS also contains nonfunctional (or supplementary) requirements. Nonfunctional requirements are requirements which impose constraints on the design or implementation (such as performance requirements, quality standards, or design constraints).

Recommended approaches for the specification of software requirements are described by IEEE 830-1998. This standard describes possible structures, desirable contents, and qualities of a software requirements specification.

[edit] Stakeholder identification

A major new emphasis in the 1990s was a focus on the identification of stakeholders. It is increasingly recognized that stakeholders are not limited to the organization employing the analyst. Other stakeholders will include:

  • those organizations that integrate (or should integrate) horizontally with the organization the analyst is designing the system for
  • any back office systems or organizations
  • higher management

[edit] Problems

[edit] Stakeholder issues

Steve McConnell, in his book Rapid Development, details a number of ways users can inhibit requirements gathering:

  • Users don't understand what they want
  • Users won't commit to a set of written requirements
  • Users insist on new requirements after the cost and schedule have been fixed.
  • Communication with users is slow
  • Users often do not participate in reviews or are incapable of doing so.
  • Users are technically unsophisticated
  • Users don't understand the development process.

This may lead to the situation where user requirements keep changing even when system or product development has been started.

[edit] Engineer/developer issues

Possible problems caused by engineers and developers during requirements analysis are:

  • Technical personnel and end users may have different vocabularies. Consequently, they can believe they are in perfect agreement until the finished product is supplied.
  • Engineers and developers may try to make the requirements fit an existing system or model, rather than develop a system specific to the needs of the client.
  • Analysis may be often carried out by engineers or programmers, rather than personnel with the people skills and the domain knowledge to understand a client's needs properly.

[edit] Attempted solutions

One attempted solution to communications problems has been to employ specialists in business or system analysis.

Techniques introduced in the 1990s like Prototyping, Unified Modeling Language (UML), Use cases, and Agile software development were also intended as solutions to problems encountered with previous methods:

Also, a new class of application simulation or application definition tools have entered the market. These tools are designed to bridge the communication gap between business users and the IT organization — and also to allow applications to be 'test marketed' before any code is produced. The best of these tools offer:

  • electronic whiteboards to sketch application flows and test alternatives
  • ability to capture business logic and data needs
  • ability to generate high fidelity prototypes that closely imitate the final application
  • interactivity
  • capability to add contextual requirements and other comments
  • ability for remote and distributed users to run and interact with the simulation

[edit] References

[edit] See also

[edit] External links

The external links in this article may require cleanup to comply with Wikipedia's content policies.
Please improve this article by removing excessive or inappropriate external links. Please remove this tag when this is done. (talk)
Retrieved from "http://en.wikipedia.org../../../r/e/q/Requirements_analysis.html"
In other languages