2008IEEE SoftwareRequires access

User Requirements and System Requirements

Neil Maiden

Open publisher page 45 citations

Abstract

In software, we often talk about user requirements and system requirements. Most people know the terms: users give you user requirements, designers work from system requirements. The terms have entered our lingua franca. However, in my experience, people - stakeholders, analysts, and designers - often fail to differentiate the roles of these two kinds of requirements. Unfortunately, treating user and system requirements as the same thing can create problems for projects. In this column I unpack some problems I've observed with user requirements and system requirements and explore what we can do about them.

About this research paper

What this paper is about

In software, we often talk about user requirements and system requirements. Most people know the terms: users give you user requirements, designers work from system requirements. The terms have entered our lingua franca. However, in my experience, people - stakeholders, analysts, and designers - often fail to differentiate the roles of these two kinds of requirements. Unfortunately, treating user and system requirements as the same thing can create problems for projects. In this column I unpack some problems I've observed with user requirements and system requirements and explore what we can do about them.

Why it matters

OpenAlex reports 45 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

In software, we often talk about user requirements and system requirements. Most people know the terms: users give you user requirements, designers work from system requirements. The terms have entered our lingua franca. However, in my experience, people - stakeholders, analysts, and designers - often fail to differentiate the roles of these two kinds of requirements. Unfortunately, treating user and system requirements as the same thing can create problems for projects. In this column I unpack some problems I've observed with user requirements and system requirements and explore what we can do about them.

Key concepts: User requirements document, Requirements analysis, Requirements engineering, Requirements elicitation, Software requirements specification, Requirements management, Business requirements, Requirement

Related papers

Back to paper searchBrowse research topicsOriginal source
User Requirements and System Requirements — Research Paper | ScholarLens