You are here: Development Standards > OSAS Standards

# OSAS Standards

Product Definitions

The first step in creating a product is deciding what it will do and how it will look. Applications can be defined as standalone pieces or as products that integrate with existing OSAS products. This section explains the differences in the product types and the considerations involved in creating a new product.

OSAS products must be

- written in PRO/5, Visual PRO/5, or BBj
- well-designed
- fully debugged
- able to run in both character and GUI modes
- able to meet the industry-specific needs of particular users
- installable using the standard OSAS installation utilities
- consistent in appearance and design with existing OSAS products
- consistent with Open Systems coding, documentation, testing standards and procedures

Consider these questions when designing a new product and creating your initial product specification

What is the market for this product?

- What is the demand for this product?
- How was this demand determined?

What tasks will this product perform?

- What new functions does it provide?
- What features will it replace?
- What features will it duplicate?

How will this product appear to the user?

- What menus or menu items do we have to create?
- What existing menu items can be used?
- How should the new menus be arranged?

What existing items can be used in this product?

- What OSAS applications must change to work with this new product?
- What existing data files will this product access?
- Which OSAS applications must be installed before this product works?
- Which OSAS applications are enhanced by this product?

What new data storage requirements does this product have?

- How much new data needs to be stored?
- What reserved fields are available in the existing data files?
- What new files are required?
- Which applications can use these new files?

What new forms does this product require?

- Can the product be adapted to use existing preprinted forms?
- Which reports are enhanced or replaced by this product?

How will this product fit into the OSAS product line?

- Does it duplicate an existing product?
- Does it render an existing product unusable?
- Is it too large (or small) a task for one application?
- With what other application should it interface?