AP scope  |  AP module  |  AP contents  |  AP index
Application module: Requirement management ISO/TS 10303-1348:2004(E)
© ISO

Cover page
Table of contents
Copyright
Foreword
Introduction
1 Scope
2 Normative references
3 Terms, definitions and abbreviations

4 Information requirements
   4.1 Required AM ARMs
   4.2 ARM type definitions
5 Module interpreted model
   5.1 Mapping specification
   5.2 MIM EXPRESS short listing
     5.2.1 MIM type definitions

A MIM short names
B Information object registration
C ARM EXPRESS-G   EXPRESS-G
D MIM EXPRESS-G   EXPRESS-G
E Computer interpretable listings
Bibliography
Index

ISO TC184/SC4/WG12 N3129

Date: 2006-06-02

Supersedes ISO TC184/SC4/WG12 N2350

ISO/TS 10303-1348:2004(E)
Product data representation and exchange: Application module: Requirement management

COPYRIGHT NOTICE:

This document is a Technical Specification and is copyright-protected by ISO. Except as permitted under the applicable laws of the user's country, neither this ISO document nor any extract from it may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, photocopying, recording, or otherwise, without prior written permission being secured.

Requests for permission to reproduce should be addressed to ISO at the address below or ISO's member body in the country of the requester:

ISO copyright office
Case postale 56, CH-1211 Geneva 20
Tel. +41 22 749 01 11
Fax +41-22-734-10 79
E-mail copyright@iso.ch

Reproduction for sales purposes may be subject to royalty payments or a licensing agreement.

Violators may be prosecuted.

ABSTRACT:

ISO/TS 10303-1348:2004 specifies the application module for Requirement management.

The following are within the scope of ISO/TS 10303-1348:2004:

  • representation of the data that identify a requirement and its versions;
  • the assignment of a requirement to a product or other item;
  • the identification of the source of a requirement;
  • relationships between requirements;
  • characterization of a version of a requirement, suitable for one or more application domains and one or more life-cycle stages;
  • identification of a universe of discourse suitable for the description of requirements;
  • relationships between requirements that are expressed at the view definition level;
  • assignment of date and time properties to requirements, requirement definitions, requirement versions, relationships between requirement versions, sources, relationships between requirement collections, requirement tracing relationships, and requirement assignments;
  • assignment of approval data to requirements, requirement definitions, requirement versions, relationships between requirement versions, sources, relationships between requirement collections, requirement tracing relationships, and requirement assignments;
  • assignment of identification and alias identification data to requirements, requirement definitions, requirement versions, relationships between requirement versions, sources, relationships between requirement collections, requirement tracing relationships, and requirement assignments;
  • assignment of person and organization data to requirements, requirement definitions, requirement versions, relationships between requirement versions, sources, relationships between requirement collections, requirement tracing relationships, and requirement assignments;
  • assignment of contract data to requirements, requirement definitions, requirement versions, relationships between requirement versions, sources, relationships between requirement collections, requirement tracing relationships, and requirement assignments;
  • assignment of security classification data to requirements, requirement definitions, requirement versions, relationships between requirement versions, sources, relationships between requirement collections, requirement tracing relationships, and requirement assignments;
  • assignment of language data to requirements, requirement definitions, requirement versions, relationships between requirement versions, sources, relationships between requirement collections, requirement tracing relationships, and requirement assignments.

KEYWORDS:

module, information management, requirement

COMMENTS TO READER:

This document has been reviewed using the internal review checklist (see WG12 N3203), the project leader checklist (see WG12 N3204), and the convener checklist (see WG12 N3205), and is ready for publication.

The project issues raised against the individual modules are stored on http://sourceforge.net/ under the stepmod project. Ballot comments will be maintained using ISO form 13b.

Project leader: Jim   U'Ren
Address: Eurostep America Inc.
1158 26th Street #158
Santa Monica
California
90401
USA

Telephone: +1 310 395 4252
Telefacsimile:
Electronic mail: Jim.URen@eurostep.com
Project editor: Allison   Barnard Feeney
Address: National Institute of Standards and Technology
100 Bureau Drive, Stop 8260
Gaithersburg
MD
20899-8260
USA

Telephone: +1 301 975 3181
Telefacsimile: +1 301 258 9749
Electronic mail: abf@nist.gov