Project Company Urd 0001

Mobilefish.
com document SDP-MF-URD-0001

Voyager Street 10 version 1.0
9999 XX Zaandam date 3 Jul 2006
The Netherlands page 1
Security class
Restricted
Title
Software Development Process
The User Requirement Document template

Summary
This report is a User Requirements Document template which can be used for small projects.
name department date signature
prepared
checked
agreed
approved
authorized
All rights reserved. Disclosure to third parties of this document or any part thereof, or the use of any 41700435.doc
information contained therein for purposes other than provided for by this document, is not permitted,
except with prior and express written permission of Mobilefish.com.
Mobilefish.com document SDP-MF-URD-0001
REVISION RECORD
version date pages affected brief description of change
1.0 3 Jul 2006 All First issue.
Table of Contents
TABLE OF CONTENTS...................................................................................................................................................3
1 INTRODUCTION...........................................................................................................................................................4
1.1 PURPOSE OF THE DOCUMENT .....................................................................................................................................4
1.3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS.............................................................................................................4
1.3.1 [Definitions]........................................................................................................................................................4
1.3.2 [Acronyms] ........................................................................................................................................................4
1.3.3 [Abbreviations]...................................................................................................................................................5
1.4 REFERENCES ........................................................................................................................................................5
1.5 OVERVIEW OF THE DOCUMENT .................................................................................................................................5
2 GENERAL DESCRIPTION..........................................................................................................................................6
2.1 GENERAL CAPABILITIES...........................................................................................................................................6
2.2 GENERAL CONSTRAINTS...........................................................................................................................................6
2.3 USER CHARACTERISTICS ..........................................................................................................................................6
2.4 OPERATIONAL ENVIRONMENT....................................................................................................................................6
3 SPECIFIC REQUIREMENTS......................................................................................................................................7
3.1 CAPABILITY REQUIREMENTS.....................................................................................................................................7
3.1.1 [subsection]........................................................................................................................................................7
3.1.2 [ ... ]....................................................................................................................................................................8
3.2 CONSTRAINT REQUIREMENTS....................................................................................................................................8
3.2.1 [subsection] .......................................................................................................................................................9
3.2.2 [subsection]........................................................................................................................................................9
A [APPENDIX HEADING]............................................................................................................................................10
1 Introduction
1.1 Purpose of the document
This document describes the user requirements for the Mobilefish.com website.
1.3 Definitions, acronyms and abbreviations
1.3.1 [Definitions]
1.3.2 [Acronyms]
UML Unified Modelling Language
URD User requirements Document
1.3.3 [Abbreviations]
1.4 References
[1] Guide to applying the ESA software engineering standaards to small software projects, ESA
BSSC(96)2 Issue 1, May 1996.
http://www.mobilefish.com/downloadswdevelopment/bssc962.pdf
From this Web page, access can be obtained to this document.
1.5 Overview of the document
2 General Description
The general requirement of this project is to change the existing static website into a CMS based website based. The
CMS used is the Drupal content management system.
2.1 General capabilities
[Describe the main capabilities required and why they are needed.]
2.2 General constraints
[Describe the main constraints that apply and why they exist.]
2.3 User characteristics
[Describe who will use the software and when.]
2.4 Operational environment
[Describe what external systems do and their interfaces with the product. Include a context diagram or
system block diagram.]
3 Specific Requirements
[List all specific requirements, with attributes.
User requirements fall into two categories: capabilities needed by users to solve a problem or achieve an
objective; constraints placed by users on how the problem is to be solved or the objective achieved.
Each user requirement must include the attributes listed below.
Identifier - each user requirement shall include an identifier, to facilitate tracing through subsequent phases.
Need - essential user requirements shall be marked as such. Essential user requirements are non-
negotiable; others may be less vitally important and subject to negotiation.
Priority - for incremental delivery, each user requirement shall include a measure of priority so that the
developer can decide the production schedule.
Stability - some user requirements may be known to be stable over the expected life of the software; others
may be more dependent on feedback from the SR, AD and DD phases, or may be subject to change during
the software life cycle. Such unstable requirements should be flagged.
Source - the source of each user requirement shall be stated. This may be a reference to an external
document (e.g. system requirement document) or the name of the user, or user group, that provided the
user requirement.
Clarity - a user requirement is clear if it has one, and only one, interpretation. Clarity implies lack of
ambiguity. If a term used in a particular context has multiple meanings, the term should be qualified or
replaced with a more specific term.
Verifiability - each user requirement shall be verifiable. This means that it must be possible to: check that
the requirement has been incorporated in the design; prove that the software will implement the
requirement; test that the software does implement the requirement. ]
3.1 Capability Requirements
[Capability requirements describe functions and operations needed by users. Quantitative statements that
specify performance and accuracy attributes should form part of the specification of a capability.
Space and time dimensions can be useful for organizing capability requirements. It is often convenient to
describe capability requirements in terms of a sequence of operations.]
3.1.1 [subsection]
UR [id1]
[UR Statement]
Need [How essential is this UR]
Priority [Priority for incremental delivery]
Stability [How subject to change is this UR]
Source [Name of person, group, document, ... from which the UR originates]
Clarity [If more than one interpretation possible, this must be qualified]
Verifiability [Check that UR is incorporated into the design, is implemented in the software,
and can be tested]
[Any Other Attribute] [Value of any other attribute]
UR [id2]
[UR Statement]
Verifiability [Check that UR is incorporated into the design, is implemented in the software,
and can be tested]
...
3.1.2 [ ... ]
3.2 Constraint requirements
[Constraint requirements place restrictions on how software can be built and operated. For example,
definitions of external communications, hardware and software interfaces may already exist, either because
the software is a part of a larger system, or because the user requires that certain protocols, standards,
computers, operating systems, library or kernel software be used.
Constraints that users may wish to place on the software include the quality attributes of adaptability,
availability, portability and security. The user shall describe the consequences of losses of availability, or
breaches of security, so that developers can fully appreciate the criticality of each function.
The user may choose to make additional standards applicable; such requirements are additional constraints
on the development. ]
3.2.1 [subsection]
...
UR [id3]
[UR Statement]
Verifiability [Check how UR: can be incorporated into the design; implemented in the
software; can be tested]
[Any Other Attribute] [Value of Any Other Attribute]
...
3.2.2 [subsection]
A [Appendix Heading]

Project Company Urd 0001

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Project Company Urd 0001

Diunggah oleh

Hak Cipta:

Format Tersedia

Mobilefish.

com document SDP-MF-URD-0001

Software Development Process

The User Requirement Document template

name department date signature

1.0 3 Jul 2006 All First issue.

1.1 Purpose of the document

1.3 Definitions, acronyms and abbreviations

UML Unified Modelling Language

URD User requirements Document

From this Web page, access can be obtained to this document.

1.5 Overview of the document

2.1 General capabilities

2.2 General constraints

2.3 User characteristics

[Describe who will use the software and when.]

2.4 Operational environment

[List all specific requirements, with attributes.

Each user requirement must include the attributes listed below.

3.1 Capability Requirements

3.2 Constraint requirements

Anda mungkin juga menyukai