ESTÁNDARES EN LA INGENIERÍA DEL SOFTWARE
José R. Hilera, José A. Gutierrez, J.Javier Martínez
Departamento de Ciencias de la Computación
Universidad de Alcalá de Henares
e-mail: jrhg, jagm, jjmh @ cc.alcala.es
Resumen.
Toda organización que
desarrolle software comercial o de uso propio, debe pretender que los productos
desarrollados alcancen una cotas de calidad dignas de satisfacer las
necesidades de los usuarios o para ser competitivos en el entorno donde tienen
que convivir.
La utilización de estándares
puede ayudar a conseguir dichos niveles de calidad. Como, por otra parte, suele
ser muy costoso el poder desarrollar completamente estandares propios, creemos
más util el partir de los ya desarrollados por grandes organizaciones que
cuentan con potencial para ello.
Ofrecemos en este artículo
una recapitulación de estándares y guias de Ingeniería del Software que puede
ser interesante para una consulta rápida a modo de indice.
1. Calidad del
software y estándares.
Una definición clásica, y ya
con cierta solera, sobre el aseguramiento de la calidad en el software fue la
enunciada en 1984 por E.H.Bersoff, que dice:
“El Aseguramiento de la
Calidad consiste en los procedimientos, técnicas y herramientas aplicadas por
los profesionales para asegurar que un producto alcanza o excede estandares
preespecificados durante el ciclo de vida de desarrollo de un producto”.[1]
Esta definición permite
comprender la vital importancia que han llegado a alcanzar los estándares en la
ingeniería del software como garantes de la consecución de niveles óptimos de
calidad. Hasta tal punto que, prácticamente se han establecido para casi
cualquier área relacionada con la producción de software:
· Estándares para
datos (desde asignar nombres a los datos y especificar su longitud y tipo hasta
los estándares más modernos vinculados con bases de datos orientadas a
objetos).
· Estándares de
codificación (abreviaturas y designaciones formales para describir actividades
y entidades dentro de la organización).
· Estándares
estructurales (políticas para dividir el software en módulos, para la
codificación estructurada y la relación existente entre los componentes del
sistema).
· Estándares de
documentación (descripciones de las características del diseño de sistemas, de
la relacción entre componentes y de las características de operación).
· Y un largo
etcetera de actividades implicadas en la consecución de una cierta “calidad del
software”.
Obviamente, a lo largo del
tiempo se han suscitado críticas a favor y en contra de la utilización de
estándares. A menudo han sido vistos como mecanismos para restringir y devaluar
las habilidades de los ingenieros de software para resolver problemas de manera
creativa. Este argumento es normalmente esgrimido por gente que no entiende el
espíritu o la intención de un buen estilo. La creatividad siempre ocurre dentro
de un marco básico de estándares. Los músicos utilizan progresiones de un
acorde fundamental, los poetas se apegan al ritmo y métrica del lenguaje,
etc...Sin un marco de trabajo de estándares que guíen y canalicen una
actividad, la creatividad se vuelve un caos sin sentido. [2][4]
Por el contrario entre las
razones que se pueden esgrimir para que una organización, en sus distintas
actividades, decida la utilización de estandares, se pueden asumir como más
importantes las señaladas por Ian Sommerville [3]:
· Los estándares
proporcionan un reagrupamiento de las mejores y más apropiadas prácticas y
usos. Engloban los “conocimientos” que son patrimonio de una organización.
· Proporcionan un
marco alrededor del cual pueden ser implementados procedimientos de
Aseguramiento de la Calidad del Software. Dichos procedimientos se simplifican
al tener que centrarse, principalmente, en controlar la consecución y el
seguimiento de los estándares.
· Proporcionan
una cierta continuidad en el trabajo realizado por una persona y retomado por
otra. Todo el mundo dentro de una organización adopta las mismas prácticas, por
eso el esfuerzo de aprendizaje cuando se inicia un nuevo trabajo es mínimo.
2. Síntesis de los
estándares existentes.
Estamos convencidos de la
necesidad de la utilización de estándares durante todas las etapas del ciclo de
vida del software y somos conscientes de la enorme dificultad que para ciertas
organizaciones supone el tener que definir sus propios estándares partiendo de
cero. Por eso, hemos creído útil el posibilitar el aprovechamiento del enorme
esfuerzo desarrollado por diferentes y potentes organismos (IEEE, ANSI,BSI,
etc..), en la creación de estándares de diferente naturaleza (ver tabla 1).
Las principales herramientas
con las que hemos contado para la confección de la síntesis que facilitamos a
continuación han sido el completo libro “Software Engineering Standards and
Specifications” (referencia completa al final) y los “site” en Internet de
distintas organizaciones: ISO, IEEE, etc...
2.1. Claves
para la interpretación de la síntesis.
Proporcionamos una tabla con
más de 200 estándares y especificaciones. Consta de catorce columnas cuyo
significado es el siguiente:
· La primera
columna indica su año de publicación. Donde aparecen dos años (1988/93) quieren
significar el de publicación y su última revisión.
· La segunda, el
acrónimo de la organización creadora (también hemos incluido otra tabla con los
nombres completos de todas las organizaciones que aparecen citadas).
· La siguiente
columna es el número asignado por la propia organización creadora.
· A continuación
tenemos el nombre completo del estándar o especificación.
· Sigue una
columna con la categoría, bien sea de estándar (E), guía (G) o documento
técnico (R). Lo que diferencia una categoría de otra, siguiendo los criterios
básicos de M.Dorfman y R.H.Thayer [7], es lo siguiente:
¨ Un estándar es
un conjunto de criterios aprobados, documentados y disponibles para determinar
la adecuación de una accion (estándar de proceso) o de un objeto (estándar de
producto).
¨ Una guía es un
conjunto de criterios bien definidos y documentados que encaminan una actividad
o tarea. Por lo tanto es algo más flexible que un estándar.
¨ Un documento
técnico no llega a la compleción y rigurosidad de los anteriores.
· Continuamos
especificando si se trata de un estandar de proceso, de producto o de recurso.
Los estándares de producto muestran una serie de atributos o características
que tienen que ser cumplidos por todos los componentes del sistema. Un estándar
de proceso nos ilustra sobre como fabricar un producto de ingeniería de
software. En cuanto a los estándares sobre recursos nos identifican las
características de los usados para llevar a cabo un determinado proceso.
· Para terminar
tenemos ocho columnas que nos indican el tipo de proceso que cubre
principalmente el estándar dentro del ciclo de vida del software:
Þ Definición de requisitos.
Þ Diseño.
Þ Codificación.
Þ Gestión de proyectos.
Þ Verificación y validación.
Þ Gestión de la configuración.
Þ Aseguramiento de la calidad.
Þ Otros.
· Las
organizaciones que han desarrollado los estandares que aparecen en la tablas
son:
AECL |
Atomic Energy of Canada Limited |
AIAA |
American Institute of Aeronautics and
Astronautics |
ANS |
American Nuclear Society |
ANSI |
American National Standards Institute |
APWA |
American Public Works Association |
AS |
Standards Association of Australia |
ASME |
American Society of Mechanical Engineers |
ASTM |
American Society for Testing and Materials |
ATA |
Air Transport Association of America |
BCS |
British Computer Society |
BSI |
British Standards Institution |
CCITT |
Comité Consultatif International
Telegraphique et Telephonique |
CEN |
Comité Européen de Normalisation |
CSA |
Canadian Standards Association |
DEF |
British Defence Standards |
DIN |
Deutches Institut für Normung |
DOD |
Defense Materiel Specifications and Standards
Office United States Department of Defense |
DTI |
Department of Trade and Industry |
ECMA |
European Computer Manufacturers Associations |
EIA |
Electronic Industries Association |
EPRI |
Electric Power Research Institute |
ESA |
European Space Agency |
FAA |
Federal Aviation Authority |
FDA |
Federal Food and Drug Administration |
GFMT |
German Federal Ministry of Transport |
GPA |
Gas Processors Association |
IAEA |
International Atomic Energy Agency |
IEC |
International Electrotechnical Commission |
IEE |
British Institution of Electrical Engineers |
IEEE |
Isntitute of Electrical and Electronics
Engineers |
ISA |
Instrument Society of America |
ISO |
International Organization for
Standardization |
KBSt |
Bundesministerium des Innern |
NASA |
National Aeronautics and Space Administration |
NATO |
North Atlantic Treaty Organization |
NISO |
National Information Standards Organization |
NIST |
National Institute of Standards and
Technology |
NMTBA |
National Machine Tool Builders Association |
NRC |
Nuclear Regulatory Commission |
RTCA |
Radio Technical Commission for Aeronautics,
Inc. |
SAE |
SAE International |
SEI |
Software Engineering Institute |
SIS |
Standardiseringskommissionen y Sverige |
STRI |
Icelandic Council for Standardization |
UL |
Underwriters Laboratories, Inc |
|
|
Tabla 1.Organizaciones que
han definido estándares
2.2. Elenco
de estándares.
AÑO |
ORG |
CODIGO |
NOMBRE |
CAT |
TIPO |
Req |
Dis |
Cod |
Pro |
VV |
Cnf |
Cal |
Otros |
1966 |
ECMA |
ECMA-4 |
FLOW CHARTS |
E |
prod |
|
* |
|
|
|
|
|
* |
1972 |
NMTBA |
NMTBA 14 |
COMMON WORDS AS THEY RELATE TO NC SOFTWARE |
G |
rec |
|
|
|
|
|
|
|
* |
1974 |
NIST |
FIPS PUB.30 |
SOFTWARE SUMMARY FOR DESCRIBING COMPUTER
PROGRAMS AND AUTOMATED DATA SYSTEMS |
E |
prod |
|
|
|
|
|
|
|
* |
1974 |
NIST |
FIPS PUB.31 |
GUIDELINES FOR AUTOMATIC DATA PROCESSING
PHYSICAL SECURITY AND RISK MANAGEMENT |
G |
proc |
|
|
|
|
|
|
|
* |
1974 |
NIST |
FIPS- PUB.30 |
SOFTWARE SUMMARY FOR DESCRIBING COMPUTER
PROGRAMS AND AUTOMATED DATA SYSTEMS |
E |
prod |
|
|
|
|
|
|
|
* |
1974 |
NIST |
FIPS-PUB.31 |
GUIDELINES FOR AUTOMATIC DATA PROCESSING
PHYSICAL SECURITY AND RISK MANAGEMENT |
G |
proc |
|
|
|
|
|
|
|
* |
1976 |
NIST |
FIPS PUB.38 |
GUIDELINES FOR DOCUMENTATION OF COMPUTER
PROGRAMS AND AUTOMATED DATA SYSTEMS |
G |
prod |
|
|
|
|
|
|
|
* |
1977 |
NIST |
FIPS PUB.49 |
GUIDELINE ON COMPUTER PERFORMANCE MANAGEMENT:
AN INTRODUCTION |
G |
proc |
|
|
|
* |
|
|
|
|
1978 |
NIST |
FIPS PUB.56 |
GUIDELINE FOR MANAGING MULTIVENDOR
PLUG_COMPATIBLE ADP SYSTEMS |
G |
proc |
|
|
|
* |
|
|
|
|
1978 |
NIST |
FIPS PUB.57 |
GUIDELINES FOR THE MEASUREMENT OF INTERACTIVE
COMPUTER SERVICE RESPONSE TIME AND TURNAROUND TIME |
G |
proc |
|
|
|
|
|
|
|
* |
1979 |
NIST |
FIPS PUB.64 |
GUIDELINES FOR DOCUMENTATION OF COMPUTER
PROGRAMS AND AUTOMATED DATA SYSTEMS FOR THE INITIATION PHASE |
G |
prod |
|
|
|
|
|
|
|
* |
1979 |
IEC |
643 |
APPLICATION OF DIGITAL COMPUTERS TO NUCLEAR
REACTOR INSTRUMENTATION AND CONTROL |
G |
prod |
* |
|
|
|
|
|
|
* |
1979 |
DOD |
MIL-STD-1574A |
SYSTEM SAFETY PROGRAM FOR SPACE AND MISSILE
SYSTEMS |
E |
proc |
|
* |
|
* |
|
|
* |
* |
1979 |
CSA |
CAN/CSA-Z243.15.1 |
BASIC GUIDELINES FOR THE STRUCTURE OF
DOCUMENTATION OF COMPUTER BASED SYSTEMS |
G |
proc prod |
|
|
|
|
|
|
|
* |
1979 |
CSA |
CAN/CSA-Z243.15.4 |
BASIC GUIDELINES FOR THE STRUCTURE OF
DOCUMENTATION OF SYSTEM DESIGN INFORMATION |
G |
proc |
|
* |
|
|
|
|
|
* |
1979 |
CSA |
CAN/CSA-Z243.15.5 |
BASIC GUIDELINES FOR THE STRUCTURE OF
DOCUMENTATION OF SYSTEM DATA |
G |
proc |
|
|
|
|
|
|
|
* |
1979 |
CSA |
CAN3-Z243.27.1 |
DATA PROCESSING VOCABULARY FUNDAMENTAL TERMS |
E |
rec |
|
|
|
|
|
|
|
* |
1980 |
BSI |
BS 5887 |
TESTING OF COMPUTER-BASED SYSTEMS |
E |
proc |
|
|
|
|
* |
|
|
|
1980 |
DOD |
NBSIR 79-1940 (R) |
INTEGRATED COMPUTER AIDED MANUFACTURING
(ICAM) SOFTWARE DOCUMENTATION STANDARDS |
E |
prod |
|
|
|
|
|
|
|
|
1980 |
NIST |
FIPS PUB.72 |
GUIDELINES FOR THE MEASUREMENT OF REMOTE
BATCH COMPUTER SERVICE |
G |
proc |
|
* |
|
|
|
|
|
* |
1980 |
NIST |
FIPS PUB.73 |
GUIDELINES FOR SECURITY OF COMPUTER
APPLICATIONS |
G |
proc |
* |
* |
|
|
|
|
|
* |
1981 |
EPRI |
NSCAC-39 |
VERIFICATION AND VALIDATION FOR SAFETY
PARAMETER DISPLAY SYSTEMS |
R |
prod |
|
|
|
|
* |
|
|
|
1981 |
EIA |
CMB4-3 |
COMPUTER SOFTWARE LIBRARIES |
G |
proc prod |
|
|
|
|
|
* |
|
|
1981 |
ANSI |
ANSI X3.88 |
AMERICAN NATIONAL STANDARD FOR COMPUTER
PROGRAM ABSTRACTS |
E |
prod |
|
|
|
|
|
|
|
|
1981 |
EIA |
CMB4-2 |
CONFIGURATION IDENTIFICATION FOR DIGITAL
COMPUTER PROGRAMS |
G |
proc |
|
|
|
|
|
* |
|
|
1981 |
BSI |
BS 6154 |
METHOD OF DEFINING SYNTACTIC METALENGUAGE |
E |
prod |
|
|
|
|
|
|
|
|
1981 |
DOD |
IDS 1501200001 |
INTEGRATED COMPUTER AIDED MANUFACTURING
(ICAM) DOCUMENTATION STANDARDS |
E |
prod |
|
|
|
|
|
|
|
|
1981 |
NATO |
NATO AQAP-13 |
SOFTWARE QUALITY CONTROL SYSTEM REQUIREMENTS |
E |
proc, prod |
|
|
|
* |
|
* |
* |
|
1982 |
BSI |
BS 6238 |
PERFORMANCE MONITORING OF COMPUTER-BASED
SYSTEMS |
G |
proc |
|
|
|
|
|
|
|
|
1982 |
EIA |
CMB4-4 |
CONFIGURATION CHANGE CONTROL FOR DIGITAL
COMPUTER PROGRAMS |
G |
proc |
|
|
|
|
|
* |
|
|
1982 |
ANSI |
ANSI/ANS/ IEEE 7 4.3.2 |
APPLICATION
CRITERIA FOR PROGRAMMABLE DIGITAL COMPUTER SYSTEMS IN SAFETY OF NUCLEAR POWER
GENERATING STATIONS |
E |
rec |
* |
* |
|
* |
* |
|
|
|
1982 |
NIST |
FIPS PUB.96 |
GUIDELINE FOR DEVELOPING AND IMPLEMENTING A
CHARGING SYSTEM FOR DATA PROCESSING SERVICES |
G |
proc |
|
|
|
|
|
|
|
* |
1983 |
ATA |
SPEC. 102 |
SPECIFICATION FOR COMPUTER SOFTWARE MANUAL |
G |
prod |
|
* |
* |
|
|
|
|
|
1983 |
EPRI |
EL 3089 |
SOFTWARE DEVELOPMENT AND MAINTENANCE
GUIDELINES |
G |
proc |
* |
* |
* |
* |
* |
* |
|
|
1983/91 |
IEEE |
829 |
SOFTWARE TEST DOCUMENTATION |
E |
prod |
|
|
|
|
* |
|
|
|
1983 |
ISA |
ISA S5.3 |
GRAPHIC SYMBOLS FOR DISTRIBUTED
CONTROL/SHARED DISPLAY INSTRUMENTATION, LOGIC AND COMPUTER SYSTEMS |
E |
prod |
|
|
|
|
|
|
|
* |
1983 |
NIST |
FIPS PUB.99 |
GUIDELINE: A FRAMEWORK FOR THE EVALUATION AND
COMPARISON OF SOFTWARE DEVELOPMENT TOOLS |
R |
proc prod |
|
|
|
|
|
|
|
* |
1983 |
NIST |
FIPS PUB.101 |
GUIDELINE FOR LIFE CYCLE VALIDATION,
VERIFICATION AND TESTING OF COMPUTER SOFTWARE |
G |
proc prod |
|
|
|
|
* |
|
|
* |
1983 |
NIST |
FIPS PUB.102 |
GUIDELINE FOR COMPUTER SECURITY CERTIFICATION
AND ACCREDITATION |
G |
proc |
|
|
|
|
|
|
|
* |
1984 |
BSI |
BS 6488 |
CONFIGURATION MANAGEMENT OF COMPUTER-BASED
SYSTEMS |
E |
proc |
|
|
|
|
|
* |
|
|
1984 |
ASTM |
E 622 |
GENERIC GUIDE FOR COMPUTERIZED SYSTEMS |
G |
proc |
|
|
|
|
|
|
|
|
1984 |
DEF |
00-16/ISS.1 |
GUIDE TO THE ACHIEVEMENT OF QUALITY IN
SOFTWARE |
G |
proc |
|
* |
* |
* |
|
* |
|
|
1984 |
ASTM |
E 1029 |
GUIDE FOR DOCUMENTATION OF CLINICAL
LABORATORY COMPUTER SYSTEMS |
G |
prod |
|
|
|
|
|
|
|
|
1984 |
DOD |
MIL-STD-882B |
SYSTEM SAFETY PROGRAM REQUIREMENTS |
E |
proc |
|
* |
|
* |
|
|
|
|
1984 |
EIA |
CMB4-1A |
CONFIGURATION MANAGEMENT DEFINITIONS FOR
DIGITAL COMPUTER PROGRAMS |
G |
rec |
|
|
|
|
|
* |
|
|
1984 |
BSI |
BS 5515 |
DOCUMENTATION OF COMPUTER-BASED SYSTEMS |
G |
proc prod |
|
|
|
|
|
|
|
|
1984/90 |
IEEE |
828 |
SOFTWARE CONFIGURATION MANAGEMENT PLANS |
E |
prod |
|
|
|
|
|
* |
|
|
1984 |
ISO |
ISO 2382 |
INFORMATION PROCESSING - VOCABULARY |
E |
rec |
|
|
|
|
|
|
|
* |
1984 |
ISO |
ISO 5806 |
INFORMATION PROCESSING - SPECIFICATION OF
SINGLE-HIT DECISION TABLES |
E |
prod |
|
* |
* |
|
|
|
|
|
1984 |
NATO |
NATO AQAP-14 |
GUIDE FOR THE EVALUATION OF A CONTRACTOR´S
SOFTWARE QUALITY CONTROL SYSTEM FOR COMPLIANCE WITH AQAP-13 |
G |
proc |
|
|
|
|
|
|
* |
|
1984 |
NIST |
FIPS PUB.105 |
GUIDELINE FOR SOFTWARE DOCUMENTATION
MANAGEMENT |
G |
proc |
|
|
|
|
|
|
|
* |
1984 |
NIST |
FIPS PUB.106 |
GUIDELINE ON SOFTWARE MAINTENANCE |
G |
proc |
|
|
|
|
|
|
|
* |
1985 |
DOD |
STD-1467 |
SOFTWARE SUPPORT ENVIRONMENT |
E |
rec |
|
|
|
|
|
|
|
|
1985 |
ASTM |
E 730 |
GUIDE FOR DEVELOPING FUNCTIONAL DESIGNS FOR
COMPUTERIZED SYSTEMS |
G |
proc |
|
* |
|
|
|
|
|
|
1985 |
DOD |
MIL-STD-490A |
SPECIFICATION PRACTICES |
E |
proc prod |
* |
|
|
|
|
|
|
|
1985 |
DOD |
MIL-STD-1521 B |
TECHNICAL REVIEWS AND AUDITS FOR SYSTEMS,
EQUIPMENTS AND COMPUTER SOFTWARE |
E |
proc |
|
|
|
* |
|
|
|
|
1985 |
DEF |
00-57 /ISS.2 |
CONFIGURATION MANAGEMENT POLICY AND
PROCEDURES FOR DEFENSE MATERIAL |
E |
proc |
|
|
|
|
|
* |
|
|
1985 |
DOD |
AFISC SSH 1-1 |
SOFTWARE SYSTEM SAFETY |
G |
proc |
* |
* |
|
|
|
|
|
|
1985 |
DEF |
00-17/ISS.1 |
MODULAR APPROACH TO SOFTWARE CONSTRUCTION,
OPERATION AND TEST-MASCOT |
E |
prod |
|
* |
* |
|
* |
|
|
|
1985 |
ISO |
ISO 5807 |
INFORMATION PROCESSING - DOCUMENTATION SYMBOLS AND CONVENTIONS FOR DATA, PROGRAM
AND SYSTEM FLOWCHARTS, PROGRAM NETWORK CHARTS AND SYSTEM RESOURCE CHARTS |
E |
prod |
|
* |
|
|
|
|
|
* |
1985 |
ISO |
ISO 6592 |
INFORMATION PROCESSING - GUIDELINES FOR THE
DOCUMENTATION OF COMPUTER-BASED APPLICATION SYSTEMS |
G |
prod |
|
|
|
|
|
|
|
* |
1985 |
ISO |
ISO 6593 |
INFORMATION PROCESSING - PROGRAM FLOW FOR
PROCESSING SEQUENTIAL FILES IN TERMS OF RECORDS GROUPS |
E |
prod |
|
* |
* |
|
|
|
|
|
1986 |
IEC |
880 |
SOFTWARE FOR COMPUTERS IN THE SAFETY SYSTEMS
OF NUCLEAR POWER STATIONS |
E |
proc prod |
* |
* |
* |
* |
* |
* |
|
|
1986 |
DOD |
AFSCP 800-43 |
AIR FORCE SYSTEM COMMAND SOFTWARE MANAGEMENT
INDICATORS |
G |
proc |
|
|
|
* |
|
|
|
|
1986 |
ANSI |
ANSI/ANS-10.3 |
GUIDELINES FOR THE DOCUMENTATION OF DIGITAL
COMPUTER PROGRAMS |
G |
prod |
|
|
|
|
|
|
|
|
1986 |
ASTM |
E 1113 |
GUIDE FOR PROJECT DEFINITION OF COMPUTERIZED
SYSTEMS |
G |
proc |
|
|
|
* |
|
|
|
|
1986/93 |
IEEE |
1008 |
SOFTWARE UNIT TESTING |
E |
proc |
|
|
|
|
* |
|
|
|
1986 |
ANSI |
ANSI/ANS-10.5 |
GUIDELINES FOR CONSIDERING USER NEEDS IN COMPUTER PROGRAM DEVELOPMENT |
G |
proc |
* |
|
|
|
|
|
|
|
1986 |
EIA |
CMB5-A |
CONFIGURATION MANAGEMENT REQUIREMENTS FOR SUBCONTRACTORS/VENDORS |
G |
proc |
|
|
|
|
|
* |
|
|
1986 |
BSI |
BS 6719 |
SPECIFYING USER REQUIREMENTS FOR A COMPUTER-BASED SYSTEM |
G |
proc prod |
* |
|
|
|
|
|
|
|
1986 |
NIST |
S.P. 500-136 |
AN OVERVIEW OF COMPUTER SOFTWARE ACCEPTANCE TESTING |
R |
proc |
|
|
|
|
|
|
|
* |
1986 |
NIST |
S.P. 500-142 |
A MANAGEMENT OVERVIEW OF SOFTWARE REUSE |
R |
proc |
|
|
|
|
|
|
|
* |
1986 |
SAE |
ARP 1570 |
FLIGHT MANAGEMENT COMPUTER SYSTEM |
G |
prod |
* |
|
|
|
|
|
|
|
1986 |
SAE |
ARP 1623A |
GUIDE FOR PREPARING AN ECS COMPUTER PROGRAM USER’S MANUAL |
G |
prod |
|
|
|
|
|
|
|
* |
1987 |
APWA |
S.R. 53 |
MICROCOMPUTERS IN PUBLIC WORKS |
R |
proc |
|
* |
|
* |
* |
|
|
|
1987 |
BSI |
BS 6224 |
DESIGN STRUCTURE DIAGRAMS FOR USE IN PROGRAM DESIGN AND OTHER LOGIC
APPLICATIONS |
G |
prod |
|
* |
|
|
|
|
|
|
1987 |
FDA |
|
TECHNICAL REFERENCE ON SOFTWARE DEVELOPMENT ACTIVITIES |
R |
proc |
* |
* |
* |
|
* |
* |
|
|
1987 |
DOD |
AFSCP 800-14 |
AIR FORCE SYSTEMS COMMAND SOFTWARE QUALITY INDICATORS |
G |
proc |
|
* |
|
* |
* |
|
|
|
1987/92 |
IEEE |
1012 |
SOFTWARE VERIFICATION AND VALIDATION PLANS |
E |
proc prod |
|
|
|
|
* |
|
|
|
1987 |
DOD |
STD-2168 |
DEFENSE SYSTEM SOFTWARE QUALITY PROGRAM |
E |
proc |
|
|
|
|
|
|
|
|
1987 |
ANSI |
ANSI/ANS-10.4 |
GUIDELINES FOR THE VERIFICATION AND VALIDATION OF SCIENTIFIC AND
ENGINEERING COMPUTER PROGRAMS FOR THE NUCLEAR INDUSTRY |
G |
proc |
|
|
|
|
* |
|
|
|
1987 |
ASTM |
E 792 |
GUIDE FOR COMPUTER AUTOMATION IN THE CLINICAL LABORATORY |
G |
proc |
* |
* |
* |
* |
* |
* |
|
|
1987/92 |
IEEE |
1002 |
TAXONOMY FOR SOFTWARE ENGINEERING STANDARDS |
G |
rec |
|
|
|
|
|
|
|
|
1987 |
FAA |
STD-021A |
CONFIGURATION MANAGEMENT |
E |
proc |
|
|
|
|
|
* |
|
|
1987 |
DOD |
ASDP 800-5 |
SOFTWARE DEVELOPMENT CAPABILITY/CAPACITY REVIEW |
G |
proc |
|
|
|
* |
|
|
|
|
1987 |
FAA |
STD-018A |
COMPUTER SOFTWARE QUALITY PROGRAM REQUIREMENTS |
E |
proc prod |
|
|
|
|
|
|
|
|
1987/93 |
IEEE |
1016 |
RECOMMENDED PRACTICE FOR SOFTWARE DESIGN DESCRIPTIONS |
G |
prod |
|
* |
|
|
|
|
|
|
1987 |
ASTM |
E 1013 |
TERMINOLOGY RELATING TO COMPUTERIZED SYSTEMS |
E |
rec |
|
|
|
|
|
|
|
|
1987 |
ASTM |
E 625 |
GUIDE FOR TRAINING USERS OF COMPUTERIZED SYSTEMS |
G |
proc |
|
|
|
|
|
|
|
|
1987 |
ASTM |
E 1206 |
GUIDE FOR COMPUTERIZATION OF EXISTING EQUIPMENT |
G |
proc |
* |
* |
* |
* |
* |
* |
|
|
1987 |
ISO |
ISO 8790 |
INFORMATION PROCESSING SYSTEMS - COMPUTER SYSTEM CONFIGURATION
DIAGRAM SYMBOLS AND CONVENTIONS |
E |
prod |
|
* |
|
|
|
|
|
* |
1987 |
ISO |
ISO 9001 |
QUALITY SYSTEMS - MODEL FOR QUALITY ASSURANCE IN DESIGN/DEVELOPMENT,
PRODUCTION, INSTALLATION AND SERVICING |
E |
proc |
|
|
|
|
|
|
* |
|
1987 |
NIST |
FIPS PUB.132 |
GUIDELINE FOR SOFTWARE VERIFICATION AND VALIDATION PLANS |
G |
prod |
|
|
|
|
* |
|
|
|
1987 |
NIST |
S.P. 500-148 |
APPLICATION SOFTWARE PROTOTYPING AND FOURTH GENERATION LANGUAGES |
R |
proc |
* |
* |
|
|
|
|
|
|
1987 |
U.S. NRC |
NUREG/CR-4640 |
HANDBOOK OF SOFTWARE QUALITY ASSURANCE TECHNIQUES APPLICABLE TO THE
NUCLEAR INDUSTRY |
R |
proc |
|
|
|
|
|
|
* |
|
1987 |
SEI |
CMU/SEI-87-TR-23 |
A METHOD FOR ASSESSING THE SOFTWARE ENGINEERING CAPABILITY OF
CONTRACTORS |
R |
proc |
|
|
|
|
|
|
* |
* |
1988 |
GPA |
9175 |
STANDARD FOR COMPUTER PROGRAM DOCUMENTATION AND DEVELOPMENT STANDARDS |
E |
prod |
|
|
|
|
|
|
|
|
1988 |
IEE |
|
GUIDELINES FOR ASSURING TESTABILITY |
G |
proc |
|
|
|
|
* |
|
|
|
1988 |
DOD |
STD-2167A |
DEFENSE SYSTEM SOFTWARE DEVELOPMENT |
E |
proc |
* |
* |
* |
* |
* |
|
|
|
1988 |
DOD |
MIL-HDBK-782 |
SOFTWARE SUPPORT ENVIRONMENT ACQUISITION |
G |
rec |
|
|
|
|
|
|
|
|
1988 |
GFMT |
BDLI 10 00 00-00 C |
TESTING, DOCUMENTATION AND CERTIFICATION OF SOFTWARE-BASED SYSTEMS IN
AIRCRAFT |
G |
proc |
|
|
|
|
* |
|
|
|
1988 |
EIA |
CMB6-5 |
TEXTBOOK FOR CONFIGURATION STATUS ACCOUNTING |
G |
proc |
|
|
|
|
|
* |
|
|
1988/93 |
IEEE |
1042 |
SOFTWARE CONFIGURATION MANAGEMENT |
G |
proc |
|
|
|
|
|
* |
|
|
1988 |
ANSI |
ANSI/ANS-10.2 |
RECOMMENDED PROGRAMMING PRACTICES TO FACILITATE THE PORTABILITY OF
SCIENTIFIC AND ENGINEERING COMPUTER PROGRAMS |
G |
proc |
|
* |
* |
|
|
|
|
|
1988 |
ASTM |
E 627 |
GUIDE FOR DOCUMENTING COMPUTERIZED SYSTEMS |
G |
proc |
|
|
|
|
|
|
|
|
1988 |
ASTM |
E 1246 |
PRACTICE FOR REPORTING RELIABILITY OF CLINICAL LABORATORY COMPUTER |
E |
proc |
|
|
|
|
|
|
|
|
1988 |
DOD |
MIL-STD-1803 |
SOFTWARE DEVELOPMENT INTEGRITY PROGRAM (SDIP) |
E |
proc |
* |
* |
* |
|
* |
|
|
|
1988 |
IEEE |
982.1 |
DICTIONARY OF MEASURES TO PRODUCE RELIABLE SOFTWARE |
E |
rec |
|
|
|
|
|
|
|
|
1988/93 |
IEEE |
1028 |
SOFTWARE REVIEWS AND AUDITS |
E |
proc |
|
|
|
* |
|
|
|
|
1988 |
FDA |
DS-9 |
REVIEWER GUIDANCE FOR COMPUTER-CONTROLLED MEDICAL DEVICES |
G |
proc |
* |
* |
* |
* |
* |
* |
|
|
1988 |
DOD |
AFSC/AFLCP 800-45 |
ADQUISITION MANAGEMENT SOFTWARE RISK ABATEMENT |
G |
proc |
|
|
|
* |
|
|
|
|
1988 |
IEEE |
982.2 |
GUIDE FOR THE USE OF IEEE STANDARD DICTIONARY OF MEASURES TO PRODUCE
RELIABLE SOFTWARE |
G |
proc |
|
|
|
|
|
|
|
|
1988 |
DOD |
STD-7935A |
DOD AUTOMATED INFORMATION SYSTEMS (AIS) DOCUMENTATION STANDARDS |
E |
prod |
|
|
|
|
|
|
|
|
1988/93 |
IEEE |
1058.1 |
SOFTWARE PROJECT MANAGEMENT PLANS |
E |
prod |
|
|
|
* |
|
|
|
|
1988 |
ISO |
ISO 9127 |
INFORMATION PROCESSING SYSTEMS - USER DOCUMENTATION AND COVER
INFORMATION FOR CONSUMER SOFTWARE PACKAGES |
E |
prod |
|
|
|
|
|
|
|
* |
1988 |
NIST |
S.P. 500-154 |
GUIDE TO DISTRIBUTED DATABASE MANAGEMENT |
R |
proc prod |
* |
* |
|
|
|
|
|
|
1988 |
NIST |
S.P. 500-155 |
MANAGEMENT GUIDE TO SOFTWARE REUSE |
R |
proc |
|
|
|
|
|
|
|
* |
1989 |
ASTM |
E 623 |
GUIDE FOR DEVELOPING FUNCTIONAL REQUIREMENTS FOR COMPUTERIZED SYSTEMS |
G |
proc prod |
* |
* |
|
|
|
|
|
|
1989 |
CSA |
CAN/CSA-Q396.1.1 |
SOFTWARE QUALITY ASSURANCE PROGRAM FOR THE DEVELOPMENT OF SOFTWARE
USED IN CRITICAL APPLICATIONS |
E |
proc |
|
|
|
|
|
|
|
|
1989 |
CSA |
CAN/CSA-Q396.1.2 |
SOFTWARE QUALITY ASSURANCE PROGRAM FOR PREVIOUSLY DEVELOPED SOFTWARE
USED IN CRITICAL APPLICATIONS |
E |
proc |
|
|
|
|
|
|
|
|
1989 |
CSA |
CAN/CSA-Q396.2.1 |
SOFTWARE QUALITY ASSURANCE PROGRAM FOR THE DEVELOPMENT OF SOFTWARE
USED IN NONCRITICAL APPLICATIONS |
E |
proc |
|
|
|
|
|
|
|
|
1989 |
CSA |
CAN/CSA-Q396.2.2 |
SOFTWARE QUALITY ASSURANCE PROGRAM FOR PREVIOUSLY DEVELOPED SOFTWARE
USED IN NONCRITICAL APPLICATIONS |
E |
proc |
|
|
|
|
|
|
|
|
1989 |
DOD |
TAD STAND E |
SOFTWARE DEVELOPMENT, DOCUMENTATION AND TESTING POLICY FOR NAVY
MISSION CRITICAL SYSTEMS |
E |
proc |
|
|
|
|
* |
|
|
|
1989/93 |
IEEE |
1063 |
SOFTWARE USERS DOCUMENTATION |
E |
prod |
|
|
|
|
|
|
|
|
1989 |
ASTM |
E 1283 |
GUIDE FOR PROCUREMENT OF COMPUTER-INTEGRATED MANUFACTURING SYSTEMS |
G |
proc |
* |
* |
|
|
|
|
|
|
1989 |
CCITT |
Z.100 |
FUNCTIONAL SPECIFICATION AND DESCRIPTION LANGUAGE (SDL) CRITERIA FOR
USING FORMULA DESCRIPTION TECHNIQUES (FDTs) |
E |
prod |
|
* |
* |
|
|
|
|
|
1989 |
DOD |
NSWC TR 89-33 |
SOFTWARE SYSTEM SAFETY DESIGN GUIDELINES AND RECOMMENDATIONS |
R |
proc |
* |
* |
* |
|
|
|
|
|
1989 |
FAA |
STD-026 |
NATIONAL AIRSPACE SYSTEM SOFTWARE DEVELOPMENT |
G |
proc |
* |
* |
* |
* |
|
|
|
|
1989 |
DEF |
00-41 (1)/ ISS.2 |
MOD PRACTICES AND PROCEDURES FOR RELIABILITY AND MAINTAINABILITY.
PART 1: RELIABILITY DESIGN PHILOSOPHY |
E |
proc prod |
|
|
|
|
|
|
|
|
1989 |
DEF |
00-41 (3)/ ISS.2 |
MOD PRACTICES AND PROCEDURES FOR RELIABILITY AND MAINTAINABILITY.
PART 3: RELIABILITY PREDICTION |
E |
proc |
|
|
|
|
|
|
|
|
1989 |
DEF |
00-41 (5)/ ISS.2 |
MOD PRACTICES AND PROCEDURES FOR RELIABILITY AND MAINTAINABILITY.
PART 5: RELIABILITY TESTING AND SCREENING |
E |
proc |
|
|
|
|
* |
|
|
|
1989 |
DEF |
DEFCON 143 |
SOFTWARE DEVELOPMENT QUESTIONNAIRE- FOR INCLUSION WITH INVITATIONS TO
TENDER |
R |
proc |
|
|
|
|
|
|
|
|
1989/93 |
IEEE |
730 |
SOFTWARE QUALITY ASSURANCE PLANS |
E |
prod |
|
|
|
|
|
|
|
|
1989 |
ASME |
NQA-1 |
QUALITY ASSURANCE PROGRAM REQUIREMENTS FOR NUCLEAR FACILITIES |
E |
proc |
|
|
|
|
* |
|
|
|
1989 |
DEF |
00-41 (4) /ISS.2 |
MOD PRACTICES AND PROCEDURES FOR RELIABILITY AND MAINTAINABILITY.
PART 4: RELIABILITY ENGINEERING |
E |
proc |
|
|
|
|
|
|
|
|
1989 |
FDA |
90-4236 |
PREPRODUCTION QUALITY ASSURANCE PLANNING: RECOMMENDATIONS FOR MEDICAL
DEVICE MANUFACTURER |
G |
proc |
|
|
|
|
|
|
|
|
1989 |
DEF |
00-41 (2)/ ISS.2 |
MOD PRACTICES AND PROCEDURES FOR RELIABILITY AND MAINTAINABILITY.
PART 2: RELIABILITY APPORTIONMENT, MODELLING AND CALCULATION |
E |
proc |
|
|
|
|
|
|
|
|
1989 |
DOD |
MIL-HDBK-287 |
A TAILORING GUIDE FOR DOD-STD-2167A, DEFENSE SYSTEM SOFTWARE
DEVELOPMENT |
G |
proc |
* |
* |
* |
* |
* |
|
|
|
1989 |
ISO |
ISO 8631 |
INFORMATION TECHNOLOGY - PROGRAM CONSTRUCTS AND COMVENTIONS FOR THEIR
REPRESENTATION |
E |
prod |
|
|
|
|
|
|
|
* |
1989 |
NIST |
S.P. 500-161 |
SOFTWARE CONFIGURATION MANAGEMENT: AN OVERVIEW |
R |
proc |
|
|
|
|
|
* |
|
|
1989 |
NIST |
S.P. 500-165 |
SOFTWARE VERIFICATION AND VALIDATION: ITS ROLE IN COMPUTER ASSURANCE
AND ITS RELATIONSHIP WITH SOFTWARE PROJECT MANAGEMENT STANDARDS |
R |
proc |
|
|
|
* |
* |
|
|
|
1989 |
SIS |
SIS TR 321 |
SYSTEMS DEVELOPMENT REFERENCE MODEL |
R |
proc |
* |
* |
* |
* |
* |
* |
* |
* |
1990 |
IEE |
|
GUIDELINES FOR THE DOCUMENTATION OF COMPUTER SOFTWARE FOR REAL TIME
AND INTERACTIVE SYSTEMS |
G |
proc prod |
|
|
|
|
|
|
|
* |
1990 |
IEE |
|
SOFTWARE INSPECTION HANDBOOK |
G |
proc |
|
|
|
|
|
|
* |
|
1990 |
IEE |
|
SOFTWARE QUALITY ASSURANCE MODEL PROCEDURES |
G |
proc |
|
|
|
|
|
|
* |
|
1990 |
DIN |
VDE 0801 |
PRINCIPLES FOR COMPUTERS IN SAFETY-RELATED SYSTEMS |
E |
proc |
* |
* |
* |
|
* |
|
|
* |
1990 |
ASME |
NQA-2 |
QUALITY ASSURANCE REQUIREMENT FOR NUCLEAR FACILITY APPLICATIONS |
E |
proc |
|
|
|
|
|
|
* |
|
1990 |
EIA |
SEB6-A |
SYSTEM SAFETY ENGINEERING IN SOFTWARE DEVELOPMENT |
G |
proc |
* |
* |
|
|
|
|
|
* |
1990 |
ASTM |
E 731 |
GUIDE FOR SELECTION AND ACQUISITION OF COMMERCIALLY AVAILABLE
COMPUTERIZED SYSTEMS |
G |
proc |
|
|
|
|
|
|
|
* |
1990 |
ASTM |
E 1340 |
GUIDE FOR PROTOTYPING OF COMPUTERIZED SYSTEMS |
G |
proc |
* |
* |
|
|
|
|
|
|
1990 |
DOD |
MIL-HDBK-347 |
MISSION-CRITICAL COMPUTER RESOURCES SOFTWARE
SUPPORT |
G |
proc |
* |
|
|
|
|
* |
|
* |
1990 |
DTI |
SafeIT |
A FRAMEWORK FOR SAFETY STANDARDS |
G |
proc prod |
|
|
|
|
|
|
|
* |
1990 |
CEN |
ENV 40 003 |
COMPUTER INTEGRATED MANUFACTURING (CIM): CIM
SYSTEMS ARCHITECTURE FRAMEWORK FOR MODELLING |
G |
prod |
|
|
|
|
|
|
|
* |
1990 |
DOD |
MIL-HDBK-59A |
COMPUTER-AIDED ACQUISITION AND LOGISTIC
SUPPORT (CALS) PROGRAM IMPLEMENTATION GUIDE |
G |
rec |
|
|
|
|
|
|
|
* |
1990 |
IEEE |
610.12 |
GLOSSARY OF SOFTWARE ENGINEERING TERMINOLOGY |
E |
rec |
|
|
|
|
|
|
|
* |
1990 |
BCS |
ISS. 1.2 |
A STANDARD FOR SOFTWARE COMPONENT TESTING |
E |
proc |
|
|
|
|
* |
|
|
|
1990 |
FDA |
CS-91-1.1 |
APPLICATION OF THE MEDICAL DEVICE GMPS TO COMPUTERIZED DEVICES AND MANUFACTURING
PROCESS |
G |
proc |
|
|
|
|
* |
* |
* |
|
1990 |
AECL |
STD-00-00902-001 |
SOFTWARE ENGINEERING OF SAFETY CRITICAL
SOFTWARE |
E |
proc |
* |
* |
* |
* |
* |
* |
* |
* |
1990 |
ASTM |
E 624 |
GUIDE FOR DEVELOPMING IMPLEMENTATION DESIGNS
FOR COMPUTERIZED SYSTEMS |
G |
proc |
|
* |
|
|
|
|
|
|
1990 |
ASTM |
E 626 |
GUIDE FOR EVALUATING COMPUTERIZED SYSTEMS |
G |
proc |
|
|
|
|
|
|
|
* |
1990 |
ASTM |
E 919 |
SPECIFICATION FOR SOFTWARE DOCUMENTATION FOR
A COMPUTERIZED SYSTEM |
E |
prod |
|
|
|
|
|
|
|
* |
1990 |
ASTM |
E 1239 |
GUIDE FOR DESCRIPTION OF
RESERVATION/REGISTRATION-ADMISSION, DISCHARGE TRANSFER (R-ADT) SYSTEMS FOR AUTOMATED PATIENT CARE INFORMATION
SYSTEMS |
G |
prod |
* |
|
|
|
|
|
|
|
1990 |
DOD |
MIL-HDBK-286 |
A GUIDE FOR DOD-STD-2168 DEFENSE SYSTEM
SOFTWARE QUALITY PROGRAM |
G |
proc |
|
|
|
|
|
|
* |
|
1990 |
ISO |
ISO 2382-20 |
INFORMATION TECHNOLOGY - VOCABULARY PART 20: SYSTEM DEVELOPMENT |
E |
rec |
|
|
|
|
|
|
|
* |
1990 |
ISO |
ISO TR 9294 |
INFORMATION PROCESSING - GUIDELINES FOR THE MANAGEMENT
SOFTWARE DOCUMENTATION |
R |
rec |
|
|
|
* |
|
|
|
* |
1990 |
NIST |
S.P. 500-180 |
GUIDE TO SOFTWARE ACCEPTANCE |
R |
proc |
|
|
|
|
* |
|
|
|
1991 |
AS |
AS 3563.1 |
SOFTWARE QUALITY MANAGEMENT SYSTEM:
REQUIREMENT |
E |
proc |
|
|
|
|
|
|
* |
|
1991 |
AS |
AS 3563.2 |
SOFTWARE QUALITY MANAGEMENT SYSTEM:
IMPLEMENTATION GUIDE |
G |
proc |
|
|
|
|
|
|
* |
|
1991 |
EIA |
CMB7-1 |
ELECTRONIC INTERCHANGE OF CONFIGURATION
MANAGEMENT DATA |
R |
proc |
|
|
|
|
|
* |
|
|
1991 |
ESA |
PSS-05-0 ISS.2 |
SOFTWARE ENGINEERING STANDARDS |
E |
proc prod |
* |
* |
* |
* |
* |
* |
* |
* |
1991 |
EIA |
CMB7-2 |
GUIDELINE FOR TRANSITIONING CONFIGURATION
MANAGEMENT TO AN AUTOMATED ENVIRONMENT |
R |
proc |
|
|
|
|
|
* |
|
|
1991 |
ASTM |
E 1384 |
GUIDE FOR DESCRIPTION FOR CONTENT AND
SCTRUCTURE OF ALL AUTOMATED PRIMARY RECORD OF CARE. |
G |
prod |
* |
* |
|
|
|
|
|
* |
1991 |
DEF |
00-55 (1)/1 |
THE PROCUREMENT OF SAFETY CRITICAL SOFTWARE
IN DEFENCE EQUIPMENT-REQUIREMENTS |
E |
proc |
* |
* |
* |
* |
* |
* |
* |
* |
1991 |
DEF |
00-55 (2)/1 |
THE PROCUREMENT OF SAFETY CRITICAL SOFTWARE
IN DEFENCE EQUIPMENT-GUIDANCE |
G |
proc |
* |
* |
* |
* |
* |
* |
* |
* |
1991 |
DEF |
00-56/1 |
HAZARD ANALYSIS AND SAFETY CLASSIFICATION OF
THE COMPÙTER AND PROGRAMMABLE ELECTRONICS SYSTEM ALEMENTS OF DEFENSE
EQUIPMENT |
E |
proc |
|
* |
|
* |
|
|
|
* |
1991 |
AIAA |
ANSI/AIAAG-009 |
GUIDE FOR IMPLEMENTING SOFTWARE DEVELOPMENT
FILES CONFORMING TO DOD-STD-2167A |
G |
proc |
|
|
|
|
|
|
|
* |
1991 |
DEF |
5169/TI |
ImproveIT (SOFTWARE ENGINEERING MATURITY
MODELS DIRECTORY) |
R |
proc |
|
|
|
|
|
|
|
* |
1991 |
BSI |
DD 198 |
ASSESSMENT OF RELIABILITY OF SYSTEMS
CONTAINING SOFTWARE |
G |
proc |
|
|
|
|
|
|
|
* |
1991 |
EIA |
IS-81 |
CDIF (CASE DATA INTERCHANGE FORMAT):
FRAMEWORK FOR MODELING AND EXTENSIBILITY |
E |
rec |
|
|
|
|
|
|
|
* |
1991 |
CSA |
CAN/CSA-396.0 |
GUIDE FOR SELECTING AND IMPLEMENTING THE
CAN/CSA-Q396-89 SOFTWARE QUALITY ASSURANCE PROGRAM STANDARDS |
G |
proc |
|
|
|
|
|
|
* |
|
1991 |
DEF |
05-95 / ISS.1 |
QUALITY SYSTEM REQUIREMENTS FOR THE
DEVELOPMENT, SUPPLY AND MAINTENANCE OF SOFTWARE |
E |
proc |
|
|
|
|
|
|
* |
|
1991 |
IEEE |
1074 |
STANDARD FOR DEVELOPING SOFTWARE LIFE CYCLE
PROCESS |
E |
proc |
* |
* |
* |
* |
* |
* |
* |
* |
1991 |
ECMA |
TR/55 |
REFERENCE MODEL FOR FRAMEWORKS OF SOFTWARE
ENGINEERING ENVIRONMENTS |
R |
prod |
|
|
|
|
|
|
|
* |
1991 |
ISO |
ISO 9000-3 |
QUALITY MANAGEMENT AND QUALITY ASSURANCE
STANDARDS - PART 3, GUIDELINES FOR THE APPLICATION OF ISO 9001 TO THE
DEVELOPMENT, SUPPLY, AND MAINTENANCE OF SOFTWARE |
G |
proc |
|
|
|
|
|
|
* |
|
1991 |
ISO |
ISO 9126 |
INFORMATION TECHNOLOGY - SOFTWARE PRODUCT
EVALUATION - QUALITY CHARACTERISTICS AND GUIDELINES FOR THEIR USE |
E |
proc |
|
|
|
|
|
|
* |
|
1991 |
NASA |
NASA STD-2100 |
SOFTWARE DOCUMENTATION STANDARD SOFTWARE
ENGINEERING PROGRAM |
E |
prod |
|
|
|
|
|
|
|
* |
1991 |
NATO |
STANAG 4159 |
MATERIAL CONFIGURATION MANAGEMENT POLICY AND
PROCEDURE FOR MULTINATIONAL JOINT PROJECTS |
E |
proc |
|
|
|
|
|
* |
|
|
1991 |
NISO |
ANSI/NISO Z39.67 |
COMPUTER SOFTWARE DESCRIPTION |
E |
prod |
|
|
|
|
|
|
|
* |
1991 |
NIST |
NIST FIPS PUB.11-3 |
GUIDELINE: AMERICAN NATIONAL DICTIONARY FOR
INFORMATION PROCESSING SYSTEMS |
G |
rec |
|
|
|
|
|
|
|
* |
1991 |
SEI |
CMU/SEI-91-TR-24 |
CAPABILITY MATURITY MODEL FOR SOFTWARE |
R |
proc |
* |
* |
* |
* |
* |
* |
* |
* |
1991 |
SEI |
CMU/SEI-91-TR-25 |
KEY PRACTICES OF CAPABILITY MATURITY MODEL |
R |
proc |
* |
* |
* |
* |
* |
* |
* |
* |
1991 |
STRI |
STRI TS2 |
MODELING A SOFTWARE QUALITY HANDBOOK MSQH |
G |
proc |
|
|
|
|
|
|
* |
|
1992 |
AIAA |
AIAA R-023 |
RECOMMENDED PRACTICE FOR HUMAN-COMPUTER
INTERFACES FOR SPACE SYSTEM OPERATIONS |
G |
prod |
* |
* |
|
|
|
|
|
* |
1992 |
DTI |
TickIT |
GUIDE TO SOFTWARE QUALITY MANAGEMENT SYSTEM
CONSTRUCTION AND CERTIFICATION |
G |
proc |
|
|
|
|
|
|
* |
|
1992 |
DOD |
MIL-STD-973 |
CONFIGURATION MANAGEMENT |
E |
proc |
|
|
|
|
|
* |
|
|
1992 |
AIAA |
ANSI/AIAA G-043 |
GUIDE FOR THE PREPARATION OF OPERATIONAL
CONCEPT DOCUMENTS |
G |
proc |
* |
|
|
|
|
|
|
* |
1992 |
CSA |
CAN/CSA-Z243.58 |
INFORMATION TECHNOLOGY VOCABULARY |
E |
rec |
|
|
|
|
|
|
|
* |
1992 |
DOD |
MIL-STD-1535B |
SUPPLIER QUALITY ASSURANCE PROGRAM
REQUIREMENTS |
E |
proc |
|
|
|
|
* |
* |
* |
|
1992 |
IEEE |
1045 |
SOFTWARE PRODUCTIVITY METRICS |
E |
proc |
|
|
|
* |
|
|
* |
|
1992 |
IEEE |
1061 |
A SOFTWARE QUALITY METRICS METHODOLOGY |
E |
proc |
* |
* |
* |
|
|
|
* |
* |
1992 |
IEEE |
1209 |
RECOMMENDED PRACTICE FOR THE EVALUATION AND
SELECTION OF CASE TOOLS |
G |
proc |
|
|
|
|
|
|
|
* |
1992 |
IEEE |
1219 |
SOFTWARE MAINTENANCE |
E |
proc |
|
|
|
|
|
|
|
* |
1992 |
ISO |
ISO TR 12382 |
PERMUTED INDEX OF THE VOCABULARY OF
INFORMATION TECHNOLOGY |
R |
rec |
|
|
|
|
|
|
|
* |
1992 |
KBSt |
KBSt V MODEL |
SOFTWARE LIFECYCLE PROCESS MODEL (V-MODEL) |
E |
proc |
* |
* |
* |
* |
* |
* |
* |
* |
1992 |
NIST |
FIPS PUB. 29-3 |
INTERPRETATION PROCEDURES FOR FEDERAL
INFORMATION PROCESSING STANDARDS FOR SOFTWARE |
E |
proc |
|
|
|
|
|
|
|
* |
1992 |
NIST |
S.P. 500-204 |
HIGH INTEGRITY SOFTWARE STANDARDS AND
GUIDELINES |
R |
proc |
|
|
|
|
* |
|
* |
|
1992 |
RTCA |
DO-178B/ED-12B |
SOFTWARE CONSIDERATIONS IN AIRBORNE SYSTEMS
AND EQUIPMENT CERTIFICATION |
G |
proc prod rec |
* |
* |
* |
* |
* |
* |
* |
* |
1992 |
UL |
UL 1998 |
STANDARD FOR SAFETY RELATED SOFTWARE |
E |
proc |
* |
* |
|
|
|
|
|
|
1993 |
AIAA |
ANSI/AIAA R-013 |
RECOMMENDED PRACTICE FOR SOFTWARE RELIABILITY |
G |
proc |
|
|
|
|
|
|
|
* |
1993 |
BSI |
BS 7649 |
THE DESIGN AND PREPARATION OF DOCUMENTATION
FOR USERS OF APPLICATION SOFTWARE |
G |
proc |
|
|
|
|
|
|
|
* |
1993 |
IEEE |
1016.1 |
GUIDE TO SOFTWARE DESIGN DESCRIPTIONS |
G |
proc |
|
* |
|
|
|
|
|
|
1993 |
AIAA |
ANSI/AIAA G-031 |
GUIDE FOR LIFE CYCLE DEVELOPMENT OF KNOWLEDGE
BASES SYSTEMS WITH DOD-STD-2167A |
G |
proc |
* |
* |
* |
* |
* |
|
|
* |
1993 |
AIAA |
ANSI/AIAA G-010 |
GUIDE FOR REUSABLE SOFTWARE: ASSESSMENT
CRITERIA FOR AEROSPACE APPLICATIONS |
G |
proc |
|
|
|
|
|
|
|
* |
1993 |
IAEA |
SE-1 |
STATE OF THE ART REPORT ON SOFTWARE IMPORTANT
TO SAFETY IN NUCLEAR POWER PLANTS |
R |
proc |
|
|
|
|
|
|
|
* |
1993 |
IEEE |
730.1 |
GUIDE FOR SOFTWARE ASSURANCE PLANNING |
G |
proc |
|
|
|
|
|
|
* |
|
1993 |
IEEE |
830 |
SOFTWARE REQUIREMENTS SPECIFICATIONS |
G |
prod |
* |
|
|
|
|
|
|
|
1993 |
IEEE |
1012.1 |
GUIDE FOR SOFTWARE VERIFICATION AND
VALIDATION PLANS |
G |
proc |
|
|
|
|
* |
|
|
|
1993 |
IEEE |
1044 |
CLASSIFICATION FOR SOFTWARE ANOMALIES |
E |
proc prod |
|
|
|
|
|
|
|
* |
1993 |
IEEE |
1062 |
RECOMMENDED PRACTICE FOR SOFTWARE ACQUISITION |
E |
proc |
|
|
|
|
|
|
|
* |
1993 |
IEEE |
1228 |
SOFTWARE SAFETY PLANS |
E |
proc prod |
* |
* |
|
|
* |
|
|
|
1993 |
NIST |
S.P. 500-209 |
SOFTWARE ERROR ANALYSIS |
R |
proc |
|
|
|
|
* |
|
* |
|
1993 |
U.S. NRC |
NUREG/BR-0167 |
SOFTWARE QUALITY ASSURANCE PROGRAM AND
GUIDELINES |
G |
proc |
* |
* |
* |
* |
* |
* |
* |
* |
1994 |
ISO |
ISO/IEC 12119 |
INFORMATION TECHNOLOGY-SOFTWARE
PACKAGES-QUALITY REQUIREMENTS AND TESTING |
E |
prod |
|
|
|
|
|
|
* |
|
1995 |
ISO |
ISO/IEC 12207 |
INFORMATION TECHNOLOGY-SOFTWARE LIFE CYCLE
PROCESSES |
E |
proc |
* |
* |
* |
* |
* |
* |
* |
* |
1995 |
ISO |
ISO/IEC 14102 |
INFORMATION TECHNOLOGY-GUIDELINE FOR THE EVALUATION AND SELECTION OF CASE
TOOLS |
G |
prod |
|
|
|
|
|
|
|
* |
3. Conclusiones.
Fijándose con detenimiento
en la tabla anterior y estudiando los estándares de las tres décadas que abarca
podemos concluir con las siguientes consideraciones generales:
· En la década de
los setenta no existe todavia una conciencia clara sobre la necesidad de
utilizar ciertas “reglas” a la hora de realizar sistemas informáticos. Existen
muy pocos estándares y la mayoría son guías, generalmente sobre temas
determinados (especialmente definición de requisitos, diseño y gestión de
proyectos).
· En los ochenta
se produce la explosión, sobre todo en su segunda mitad, en la aparición de
estándares y guías. De estas últimas ya tenemos algunos casos que intentan
abarcar todos los procesos del ciclo de vida del software aunque todavía no se
incorporan de manera generalizada los aspectos del aseguramiento de la calidad.
· La década en la
que nos encontramos ha supuesto el asentamiento de toda una filosofía que
entiende el desarrollo del software como un proceso de ingeniería y, por tanto,
su concepción como un “todo”. Tenemos ya gran variedad de estándares que
contemplan todos los aspectos del ciclo de vida. Vemos también en la tabla como
han aparecido numerosas guías y estándares centrados en aspectos que
tradicionalmente habían sido relegados: la gestion de la configuración y, sobre
todo, los temas relaccionados con el aseguramiento de la calidad. Incluso se ha
empezado a trabajar en la confección de guías para realizar estándares.
Al hilo de lo comentado para la última década queremos hacernos eco de
un trabajo que está siendo realizado por ISO/IEC y que tiene una gran relación
con el presente artículo:
ISO/IEC DTR 14399
Information Technology -- Mapping of Relevant Software Engineering Standards --
Standards Relevant to ISO/IEC JTC 1/SC 7 - Software engineering.
Como colofón decir que esta
guia puede estar, obviamente, incompleta y que animamos al lector a informarnos
de otras normas que no hayan sido incluidas.
4
Bibliografía y referencias.
La mayoria de los documentos
incluidos en la tabla pueden obtenerse de las organizaciones responsables de
cada uno.
[1] E.H.Bersoff “Elements of software configuration
management”, IEEE Trans.Software Eng.
[2] R. Fairley. “Software
Engineering Concepts”,
McGraw-Hill, Inc. USA.
[3] I. Sommerville “Software
Engineering”
Addison-Wesley Publisinhg
Company.
[4] J.A. Senn. “Analysis &
Design of Information Systems”,
McGraw-Hill, Inc. USA.
[5] Stan Magee, CDP and L.L.Trip
“Software Engineering Standards and Specifications”,
Global Professional
Publications. USA.
[6] “Software Engineering
Standards Collection”,1991. IEEE.
[7] M.Dorfman, R.H.Tayer
“Standards, Guidelines and Examples on System and Software Requirements
Engineering ”,
IEEE Computer Society Press
1990.
[8] S.L.Pfleeger, N.Fenton y
S.Page “Evaluating Software Engineering Standards”,
COMPUTER pp.71-79,
Sept.1994.