DOMINICAN AMERICAN UNIVERSITY

ENGINEERING AREA
SYSTEMS ENGINEERING

THEME:

Programming Test Standards.

José Luis Henríquez.

SUBJECT:

Software Project Management.

SUSTAINERS:

Margarita Lissette Moreno 2007-30-3-0058

DATE:

Santo Domingo, D.N.

Programming test standards are a way to 'normalize' programming.

in such a way that when working on any project, any of the people involved in it

have access to and understand the code. In other words, define the writing and organization of

source code of a program. Also, following a programming standard makes it easier for you as

programmer the modification of your own source code even if you are not working on a

team.

Generally, programming standards define how they should be declared.

the variables, the classes, the comments, in some standards specify what data must be

include information about the programmer and the changes made to the source code, etc.

For example, using a certain nomenclature for variable declaration, or of

Classes depending on their type are very helpful because when reading the name of the variable ...

Do you know what type of data you are working with and are you not afraid to look for the statement of the

variable, all this always depending on the environment and programming language you use.

Programming testing standards are a set of policies and rules that you apply.

when programming, they help unify the way of working, the results and the

productivity of programmers. It serves to ensure the quality and clarity of the

programs.

Programming testing standards include: rules for naming the

procedures, variables, fields, etc., rules and ways to make the windows, rules and

ways to create reports, comments in the code, and system documentation, even

The keys and controls that will be provided to the user to work on the screens.

2
Standards are chosen before starting to program, documented, and explained to the

programmers so that everyone works and their results look so similar internally in

programs like visually for the user.

They deal with the responsible practice of software engineering.

They regularly deal with the process instead of the product, although sometimes

they deal with the generic characteristics of the product or with support resources.

They deal with topics such as Configuration Management, Assurance

of Quality, Verification and Validation.

Importance of Programmer Testing Standards

They consolidate the existing technology on a firm foundation to introduce new ones.

technologies.

They enhance professional discipline.

They protect businesses.

They protect the Buyer.

They improve the product.

Tests must be presented throughout the entire development life cycle.

software, going through requirements, analysis and design, programming, implementation

march and maintenance.

3
 Quality Assurance and Standards

The quality assurance is the process that defines how to achieve software quality and

How does the development organization know the required quality level in the software.

We can define two types of standards as part of the assurance process.

quality

Product Standards: these are standards that apply to the product

software that is beginning to be developed. They include documentation standards, such as

standard comments header for class definition.

Process Standards: these are standards that define the processes that must

to be followed during the software development. They may include definitions of processes of

specification, design, and validation.

Software standards are very important for several reasons:

It is based on the knowledge of the best or most appropriate practice of the

company.

They provide a framework around which the process is implemented

quality assurance.

The development of standards for software engineering projects is a

difficult and long process. National and international organizations such as the

United States Department of Defense; ANSI, BSI; NATO and IEEE have been

active in the production of the standards.

4
 Software Quality Models and Standards

ISO 9000

CMM

ISO/SPICE

BS 7925–2

IEEE 829

ISO 9000

The International Organization for Standardization is a consortium that brings together

practically all industrialized nations. Its mission is to develop standards

international standards that facilitate international trade. ISO 9000 standards are

they guide the standardization of quality systems and are not related to

any particular product, but with the processes from which the products derive and

services. It is assumed that a quality system that meets ISO standards

9000 is reliable enough to safely produce products and

services that meet the needs and expectations of customers.

In general, ISO 9000 standards require that an organization be accredited,

that all its processes, both productive and administrative, directly affecting

the quality of the product and service. In many countries, there are standards

compatible with ISO 9000, so in essence they are very similar and

They pursue the same goals.

The ISO 9000 standard is, on one hand, a guide to implement certain purposes.

contractual agreements with clients by certifying that the company in question has a

system that allows the production of quality products.

5
A set of international standards that you can use in the development of a

quality management system. The ISO 9000 standards can be applied to a wide range

a range of organizations from manufacturing to services. ISO 9001

it is not a specific standard for software development, but it defines principles

generals that can be applied to software.

Its implementation, although it requires hard work, offers numerous advantages for the

companies, including:

Standardize the activities of the staff working within the organization.

through the documentation

Increase customer satisfaction

Measure and monitor the performance of processes

Reduce reprocessing

Increase the effectiveness and/or efficiency of the organization in achieving its

objectives

Continuously improve in processes, products, effectiveness, etc.

ISO 9000:2000 Quality management systems. Fundamentals and vocabulary (ISO

9000:2000

ISO 9001:2000 Quality management systems. Requirements (ISO 9001:2000)

ISO 9004:2000 Quality management systems. Guidelines for improvement

performance (ISO 9004:2000)

6
ISO Standard 1901 1, which provides guidance on system audits

of quality management and environmental management.

ISO 9001

Establish the elements of a quality management system.

Develop, implement, and improve the system.

Document the process.

Produce an operational manual.

ISO 9126

Software quality assessment model; provides simple characteristics of

evaluation and measurement.

Quality model

External metrics (Quality assurance)

Internal metrics (Development)

Quality metrics in use (Final product)

International Standards

BS 7925–2

British Standard for software component testing

Software Component Testing.

7
Describe techniques for designing and measuring test cases, involving execution.

and analysis of the results, characteristics to select to determine,

compare and improve the quality of the test.

IEEE 829

Standard for documenting software tests. Specifies 8 stages of the process.

of documentation.

Planning of tests

Test Design Specification

Specification of test cases

Procedure specification

Progress report of the tested cycles

Test registration

Incident report

Summary of the test

International Standards

TPI (Test Process Improvement)

Methodology to evaluate the maturity level of testing in an organization, thus

in order to improve the process.

Test: Activity in which a system or one of its

components to an evaluation of the results based on the execution

of this under specified conditions.

8
Test Case: Set of inputs and conditions that yield

expected results developed with a particular objective.

ISO 9000

Customer focus

Leadership

Staff participation

Process-based approach

System approach to management

Continuous improvement

Fact-based approach to decision making

Mutually beneficial relationships with the supplier

Role of senior management ISO 9000

Each organization should determine which processes need to be documented in

function of your client's requirements and the applicable legal or regulatory ones,

from the nature of its activities and its global corporate strategy. To

determine which processes should be documented the organization could consider

factors such as:

The effect on quality

The risk of customer dissatisfaction

The legal and regulatory requirements

Economic risk

9
Effectiveness and efficiency

The competence of the staff

The complexity of the processes

10
Bibliography

Delgado, H. C. (3rd). Development of a Quality Culture. McGraw Hill.

Sommeville, I. (2007). Software Engineering. Addison Wesley.

Urbira, G. B. ( 2006). Formulario y evaluación de proyectos. Mcgraw Hill.

11