app build information model

8/14/2019 App Build Information Model

1/184


2/184

BluePhoenix AppBuilder 2.1.0.Document TitleApril, 2003

Corporate Headquarters

BluePhoenix Solutions

Vlierwerf 7B4704 SB RoosendaalThe Netherlands+31 (0) 165 399 401+31 (0) 165 396 308 fax

USA HeadquartersBluePhoenix Solutions USA, Inc.8000 Regency ParkwayCary, NC 27511United States+1 919.380.5100+1 919.380.5111 fax

www.bluephoenixsolutions.com

1992-2003 BluePhoenix Solutions

All rights reserved.

BluePhoenix is a trademark of BluePhoenix Solutions. All other product and company namesmentioned herein are for identification purposes only and are the property of, and may be trademarksof, their respective owners.

Portions of this product may be covered by U.S. Patent Numbers 5,495,222 and 5,495,610 and various

other non-U.S. patents.

The software supplied with this document is the property of BluePhoenix Solutions, and is furnishedunder a license agreement. Neither the software nor this document may be copied or transferred by anymeans, electronic or mechanical, except as provided in the licensing agreement.

BluePhoenix Solutions has made every effort to ensure that the information contained in this documentis accurate; however, there are no representations or warranties regarding this information, includingwarranties of merchantability or fitness for a particular purpose. BluePhoenix Solutions assumes noresponsibi li ty for errors or omissions that may occur in this document. The information in thisdocument is subject to change without prior notice and does not represent a commitment byBluePhoenix Solutions or its representatives.
http://www.bluephoenixsolutions.com/http://www.bluephoenixsolutions.com/


3/184

AppBuilder 2.1.0 Information Model Reference Guide i

TABLE OF

CONTENTS

AppBuilder 2.1.0 Information Model Reference Guide

1 Information M odel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Understanding the Information Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Information Model Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Enti ty Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Relationship Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Repositories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Submodels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Internal Object Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Accessing Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Comparative Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Common Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Diagrammatic Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

2 Entit y Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Common Properties of Entity Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Common Entity Type Property Descript ions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Entity Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4Application Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Bitmap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7Bitmap Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Business Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13Component Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15

Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16Data Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Drawing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29Identifier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30

Table of Contents


4/184

ii AppBuilder 2.1.0 Information Model Reference Guide

Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31Logical Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33Machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38Physical Event. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41Relationship. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50State. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-53Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55Transition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57Value. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58

Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60

3 Relationship Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Common Properties of Relationship Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Common Relationship Properties Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Relationship Variants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Relationship Type Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Relationship Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Accesses (is-accessed-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6Affects (is-affected-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Can-Access (can-be-accessed-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Causes (is-caused-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Cites (is-cited-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Comprises (is-comprised-of). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Connects (is-connected-to) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Contains (is-contained-in) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10Converses (is-conversed-by). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14Depends-on (is-depended-on-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15Encapsulates (is-encapsulated-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16Has (is-had-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18Has STD (has-a-state-transition-diagram). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19Impacts (is-impacted-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19Includes (is-included-in) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20Influences (is-influenced-by). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21

Init iates (is-init iated-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22Intersects (intersects-with). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22Invokes (is-invoked-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23Is-carried-out-at (Carries Out).. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24Is-composed-of (Composes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24Is-constrained-by (Constrains) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25Is-defined-by (Defines) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25Is-described-by (Describes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26Is-distributed-at (Where-is-distributed) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26


5/184

Table of Contents iii

Is-forwarded-to (Is-forwarded-from) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27Is-implemented-by (Implements) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27Is-involved-in (Involves) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29Is-keyed-by (Keys) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29Is-modified-at (Where-is-modified) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30Is-modified-by (Modif ies). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30Is-preconditioned-by (Preconditions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31Is-profiled-by (Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32Is-referenced-by (References) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32Is-replaced-by (Replaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33Is-related-via (Relates) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33Is-responsible-for (is-the-responsibility-of) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34Is-site-of (Has-as-its-site) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35Is-typed-by (Types). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35Maps (is-mapped-to) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35Member (is-member-of) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36Owns (is-owned-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36Partit ioned (partit ioned-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38Refers-to (is-referred-to-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38

Refines-into (is-refined-from) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39Replaces System (System is-replaced-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40Results-in (is-the-result -of). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41Stores (provides-storage-for) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42Supports (Is-supported-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43Triggers (is-triggered-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44Uses (is-used-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45

4 Text Property Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

General Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Abbreviation Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

5 Enterprise Administrat ion Informat ion M odel . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Administration Information Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1User Enti ty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Group Enti ty. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5Project Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

6 Enterprise Repository Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Using the Enterprise Repository Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Listing of Enterprise Repository Objects, Methods, and Actions. . . . . . . . . . . . . . . . . . . . . . . . . . .6-1

A Backw ards Compat ibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1

New Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1Database Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2Help Text. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2


6/184

iv AppBuilder 2.1.0 Information Model Reference Guide

Logical Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3Rebuild Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3Relationship. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-3Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

New Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4Is-carried-out-at. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4Is-involved-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5Is-modified-by. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5Is-profiled-by. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5Is-responsible-for . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5Is-signatured-by . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5Is-site-of. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5Is-supported-by. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5

Refines-into. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-5Replaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-5

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i


7/184

AppBuilder 2.1.0 Information Model Reference Guide 1-1

CHAPTER

1

INFORM ATION M ODEL


The AppBuilder Information Model is the collection of object types available to business planners,analysts, system designers, and developers who work in the AppBuilder environment. This guideprovides information about the entity types and relationship types within the Information Model. Theseentity types and relationship types are listed alphabetically, and each listing includes a description aboutthe object and its properties.

Understanding the Informat ion Model

The Information Model is a collection of entity types and relationship types, collectively called objecttypes. This discussion includes:

Information Model Elements

Accessing Properties

Comparative Terminology

Common Properties

Diagrammatic Summary

You tailor object types when you build an application. When you assign a unique name to an objecttype, you create an object, which is an instanceof that object type. For example, a File entity typedesigned to hold business addresses might be called CUSTOMER_ADDRESSES. You bui ld models ofyour business and you design and develop applications by defining particular instances of these objecttypes, making them unique by defining their properties. Thus, you use object types to create objects.

You should use nouns to represent the names of instances of entity types. For example, an instance of theRule entity type that gets customer information from a file might be called CUSTOMER_FETCHER.You should also use a noun-verb-noun combination to represent instances of relationship types. Forexample, the relationship instance between the rule and the file just mentioned isCUSTOMER_FETCHER accesses CUSTOMER_ADDRESSES.


8/184

1-2 Information Model


Informat ion M odel Elements

The elements of the Information Model include:

Entity Types

Relationship Types

Properties

Repositories

Submodels

Internal Object Types

Entit y Types

An enti ty type is essentially anything about which you can store data (for example, a table, a person, or acorporation). In Information Model diagrams, entity types appear as boxes and their names appear as

nouns.

Relationship Types

A relationship type indicates how an entity type interacts with another entity type. In InformationModel diagrams, relationship types appear as lines and their names appear as verbs. Because arelationship type always connects two entity types, you can view the relationship from the perspective ofeither entity. For example, a Process is-defined-by a Rule or a Rule defines a Process are two differentways of looking at the same relationship.

Properties

Propert ies (or att ributes) define both entity types and relationship types. (In the ConstructionWorkbench interface, Properties refer to properties of entity types and Relationship Properties refer toproperties of relationship types. There may be several specific properties of an object type.

There are three possible statuses for a property. If it is a required property, you must provide a value forit to save the instance successfully. If it is an optional property, you can save the instance withoutproviding a value for it. If it is a generated property, the AppBuilder environment populates it and youcannot alter it.

Repositories

The models and applications that you build are stored in repositories. There are three implementationsof repositories in the AppBuilder Environment:

Personal ( local) repository

Workgroup (server) repository (also called Freeway)

Enterprise (mainframe) repository


9/184



The personal repository resides on a workstation along wi th a series of development tools you can use tobuild new or edit existing instances of repository object types. The personal repository stores the datathat is accessed by all the tools.

The workgroup repository is a server-based or departmental repository that resides on a network server.Developers can simultaneously view and access any objects in this repository.

The enterprise repository resides on the host (mainframe). Developers can upload and downloadobjects between this repository and a workstation Personal Repository.

Repositories store data about your business and the system you are building, and all basically use thesame Information Model, though there are a few differences between the workstation and host objects(seeAppendix A, Backwards Compatibil it y). For more details, refer to the Personal RepositoryAdmini strat ion Guideand theFreeway Repository Administration Guide.

Submodels

The Information Model can be broken down into functional subsets called submodels. For example, thepart of the Information Model that deals with security can be viewed as the Security submodel (seeDiagrammatic Summary on page1-6for more information).

All object types are part of the Information Model unless otherwise noted. Generally, this guide presentsa property of an object type as it appears on the workstation, which may differ slightly from the way itappears on the host. For instance, properties that appear as check boxes on the workstation usuallyrequire you to choose between two items and perform a numeric selection on the host.

Internal Object Types

There are a few entity and relationship types that the AppBuilder environment uses internally. Theseobjects are generally invisible to you while you are working within the environment. However, you mustseparately upload and download these objects to and from the host; these objects are consequentlyvisible within the Repository Maintenance tool and may be referred to during a workgroup or enterpriserepository migration. This manual lists these objects in the event that you need to identi fy them dur inghost communications, but they are not otherwise available for your use.


10/184




To access the properties (of entity type objects or relationship type objects), from the ConstructionWorkbench, right-click on objects in the Hierarchy window (in any of the tabs: Project, Configuration,Repository, Inverted).

Figure 1-1 Accessing Properties from the Construction Workbench

To access the propert ies from the Freeway Explorer, select Objects > Query. Select an object and double-click on the object in the main window. The Properties dialog opens (Figure 1-2). The dialog has severaltabs.

Figure 1-2 Proper ties Dialog

TheGeneraltab contains the editable properties of that entity.

TheAudittab contains the common propert ies of that entity.

TheRemote Audit tab contains information about migration of the entity to and from theenterpriserepository.

TheTexttab contains a space for you to enter descriptive text about that entity.

TheKeywordstab contains a space for you to enter a list of keywords to associate with that entity.

OR


11/184




The use of entity types in AppBuilder is significantly different from the use of their third-generationlanguage equivalents in a traditional development environment. If you have programmed using atraditional language, such as COBOL or PL/I, Table1-1describes the purpose of some of theInformation Model enti ty types. Table1-1lists several Information Model entity types commonly used

during system development, along wi th the closest corresponding term.

Keep in mind that the correspondences are not exact equivalents. For example, the View entity type isnot the same as a 3GL environment Record. In AppBuilder, a View constitutes a data definition, whichyou can attach to a file. In this case, a view would, in effect, define a record. You also can use the sameview to define the output of a rule used to populate the file, or associate it with a window used to displaythe data.

Common Properties

All entity types have common properties. All common properties except System ID are the entity types

Audit propert ies. The Audit propert ies (except for local date and local time) are not populated unti l theenti ty type has either been created on the host (either directly or by uploading) or committed to theworkgroup repository.

In the enterprise repository on the host, allproperties appear on the main screen for each object type,and may appear in a different order.

In the personal and workgroup repositor ies on the workstation, Name and System ID, as well as allproperties unique to each object type, appear on the General tab of the Properties dialog for that objecttype. Audit properties appear on the entity types Audit tab (see Figure1-3).

Table 1-1 Information Model Terms Compared with 3GL Terms

Traditional term AppBuilder term

Menu item Process

Paragraph or routine Rule

Screen Window

Subroutine Component

Record View

Field or variable Field

File or table File


12/184



Figure 1-3 Audi t and Remote Audi t Tabs

Property names may be slightly different among the workstation and host repositor ies, and someproperties may not appear in both (seeAppendix A, Backwards Compatibil ity). The following listindicates how each property appears in the host and workstation repositories. If not specified, the nameis the same in all repositor ies.


The following diagrams graphically illustrate many of the entity and relationship types described in thisbook.

The Information Model is divided into the following views:

Design and Construction: Data View

Design and Construction: Data Traceability View

Design and Construction: Process View

Security View


13/184



Figure 1-4 Design and Construction: Data View

Figure 1-5 Design and Construction: Data Traceability View

owns

is-based-on

has

relates-via

owns

composes

includes

is-typed-by

refines-into

has

has

is-described-by

is-composed-of

is-referenced-by

is-fowarded-to

is-composed-of

is-constrained-by

composes

is-described-byis-related-via

includes

SET

RELATIONSHIP

ATTRIBUTE FIELDCOLUMN

VIEW

FILE

KEYIDENTIFIER

ENTITYBUSINESS OBJECT

DATA TYPE

TABLE

connects-to

connects-to

is-implemented-by

is-implemented-by

is-implemented-by

connects-to

is-implemented-by

is-implemented-by

is-implemented-by

is-implemented-by

connects-to

is-implemented-by

is-implemented-by

is-implemented-by

FILE

ENTITY

ATTRIBUTE

KEY

IDENTIFIER

COLUMN

TABLE

RELATIONSHIP

COLLECTION


14/184



Figure 1-6 Design and Construction: Process View

Figur e 1-7 Secur it y View

owns

owns

contains

uses

intersects-with

includes

refers-to

refers-to

owns

refines-into

owns

owns

is-keyed-by

depends-on

is-defined-by

uses

is-composed-of

owns

converses

ownsis-accessed-by

is-fowarded-to is-accessed-by

refers-to

converses

depends-on

is-implemented-by

uses

includes

affects

refers-to

depends-on

triggers

impacts

is-modified-by

ownshas

is-implemented-by

refers-to

refines-into

contains

FIELD

SET

RULE

LOGICAL PROCESS

VIEW

PHYSICAL EVENT

COMPONENT

WINDOW

FILE

ENTITY

PROCESS

REPORT

SECTION

FUNCTION

VALUE

has-access-to

containsis-member-of

is-owned-by

is-owned-by

GROUP

PROJECTUSER

INSTANCEOF

OBJECTTYPE


15/184


CHAPTER

2

ENTITY TYPES


An object type is anything about which information can be stored in the AppBuilder repository. Objecttypes have properties that describe them. There are two categories of object types in the repository:entity types and relationship types. This section lists properties common to all entity types and thenprovides a detailed description of each entity type.

This chapter includes:

Common Properties of Entity Types

Enti ty Types

In the enti ty type descriptions, each entry starts with a description of the entity type and how it is used,a screenshot of the Properties dialog, specifically the General tab where properties can be edited, a tablelisting its specific properties, and the relationships associated with the entity type.

Name and System ID properties are described as common properties because their generalcharacteristics are discussed in Common Properties of Entity Types .The Relationship sectiondescribes how each Entity type is related to other Entity types. See Chapter 3, Relationship Typesfordetails of the relationship types and their properties.

Common Propert ies of Ent ity Types

The common properties of entity types in the AppBuilder Information Model include:

Name

System ID

Owner

Project

Explicit lock (Personal or Workgroup)

QA status (Personal and Workgroup)

Change number

Created/Remote date (Personal or Workgroup)

Datecreated (Enterprise)

Created/Remote time (Personal and Workgroup)


16/184

2-2 Entity Types

Common Properties of Entity Types

Timecreated (Enterprise)

Created/Remote user (Personal and Workgroup)

Created by (Enterprise)

Maintained/Remote date (Personal and Workgroup)

Datemaintained (Enterprise)

Maintained/Remote time (Personal and Workgroup)

Timemaintained (Enterprise)

Maintained/Remote user (Personal and Workgroup)

Maintained by(Enterprise)

Maintained/Local date (Personal and Workgroup)

Maintained/Local time (Personal and Workgroup)

Version (Enterprise only)

Common Entity Type Property Descriptions

Name

Status: Required

Unique name, up to thirty (30) characters in length, identifies each instance of an object type. Namesshould adhere to text standards (seeChapter 4, Text Property Conventions) in order to facili tate reuse.Since names provide information about the function and purpose of an object instance, failure to adhereto a standard naming convention makes it hard to quickly locate and use an existing instance.

Follow these general guidelines for creating names:

Abbreviate. Use abbreviations where necessary. (SeeAbbreviation Guidelines on page4-2.)

No Spaces. An instances name cannot contain spaces. To separate character strings in a name, usean underscore (_) between each word.

Object-Action. Names should describe the function or purpose of an instance by first describingwhat it is and then describing what it does.

Names are stored in uppercase. Take this into account when performing comparisons in the rulesource code.

System ID

Status: Generated

An alphanumeric string the AppBuilder environment uses internally to refer to the instance of the objecttype. Each instance has a unique System ID. During workstation installation, a workgroup repository(Freeway) System ID (a number between 400 and 1295) for your workstation was entered. An instancesSystem ID is generated from this number. For an instances System IDs to be unique across anapplication, the Freeway System ID chosen at installation must be unique from all other developers ofthat application.


17/184


18/184

2-4 Entity Types

Entity Types

Maintained/Remote date (Personal and Workgroup)

Date maintained (Enterprise)

Status: Generated

Format: YY/MM/DD

Date the instance was last changed in the enterprise repository, either directly or by uploading.

Maintained/Remote time (Personal and Workgroup)

Time maintained (Enterprise)

Status: Generated

Format: HH:MM

Time the instance was last changed in the enterprise repository, either directly or by uploading.

Maintained/Remote user (Personal and Workgroup)

M aintained by (Enterprise)

Status: Generated

ID of last user who changed the instance in the enterprise repository, either directly or by uploading.

Maintained/Local date (Personal and Workgroup)

Status: Generated

Format: YY/MM/DD

Date the instance was last changed on the workstation.

Maintained/Local time (Personal and Workgroup)

Status: Generated

Format: HH:MMTime the instance was last changed on the workstation.

Version (Enterprise only)

Status: Generated

Identifies the logical repository in which this instance resides.

Entity Types

The entity types in the AppBuilder Information Model (in alphabetical order) are shown in Table2-1.

Table 2-1 Information Model Entity Types

Application Configuration Event Relationship

Attribute Field Report

Bitmap File Rule

Bitmap Implementation Function Section

Business Object Identifier Server


19/184

Entity Types


Properties

Refer to Common Properties of Entity Typesfor propert ies common to all entity types. Propert iesspecific to each of the listed entity types are shown in the Properties Table under each entity heading. Ifthere is no Properties Table, that indicates there are no properties specific to that entity type.

Application Configuration

The Application Configuration enti ty type (Figure2-1) encapsulates the information needed to preparea client-server application, to migrate it to a production environment, and to administer it at run-time.

Figure 2-1 Application Configuration Properties Dialog

Relationships

Application Configuration has the Partition

Inverse Relationships

Application Folder contains an Application Configuration

Application Configuration parti tions a Function. This is the inverse relationship added for aFunction; the relationship already exists in the relationships list.

Attribute

The Attribute (Figure2-2) describes the characteristics or properties of an entity or a relationship.Typically, you define instances of Attributes during business object analysis to provide details for yourdata model. For example, i f you have an object called Customer, you might create attributes calledFirst_Name, Last_Name, Street_Address, and so on.

Collection Key Set

Column Logical Process Symbol

Component Machine Table

Component Folder Migration Transition

Database Partition Value

Data Type Physical Event View

Drawing Process Window

Entity State

Table 2-1 Information Model Entity Types (Continued)


20/184


21/184


22/184

2-8 Entity Types

Entity Types

Bitmap Implementation

The Bitmap Implementation is entity type that manages the physical files that can comprise a bitmap. Itexists to facilitate uploading objects to the host.


Bitmap is-had-by Bitmap Implementation

Business Object

The Business Object (Figure2-4) groups together a set of entities.

Table 2-4 Bitmap Implementation Properties

Property Description

CountryLanguage

Status: Optional

Default is English (US)mDomCountryLanguage

The following choices are available:

English (US) English (UK)

X_ResStatus: OptionalCan contain a maximum of 5 characters

Y_ResStatus: Optional

Can contain a maximum of 5 characters

FormatType

Status: OptionalDefault is BMPmDomBMPFormatType

The following choices are available: BMP

ICR

PTR JPEG

GIF

WAV AVI

MOV

MPEG QTW

DescriptionStatus: OptionalUp to 30 characters of additional information that describes the bitmap


23/184

Entity Types


Figure2-4 Business Object Proper t ies Dialog

Relationships

Business Object data-content-defined-by ER View

Business Object has State

Business Object has-STD Drawing

Business Object owns Enti ty

Business Object owns Event

Business Object owns Business Object

Business Object owns Logical Process

Business Object refines-into Business Object

Business Object has member Enti ty

Business Object has member Class Property

Business Object has member Class Domain

Business Object has member Class Object Business Object has member Class Relationship

Table 2-5 Business Object Properties

Field in Dialog Property Description

Description DescriptionStatus: OptionalUp to 30 characters of additional information that describes the Business

Object

Type BusObj_Type

Status: RequiredDefault is Referential

mDomBusinessObjectType

Designates the type of Business Object.The following choices are available:

Referential

Transactional


24/184

2-10 Entity Types

Entity Types


Event influences Business Object

Application contains Business Object

Scheme maps to Business Object

Value maps to Business Object

Business Concept maps to Business Object

Logical Business Function maps to Business Object

Model Scope includes Business Object


Collection

The Collection entity type (Figure2-5) stores internal traceabil ity information. You can view this entitytype, but you should not modify i t.

Figure 2-5 Col lect ion Proper t ies Dialog

Table 2-6 Customized_To Relationships

FROM TO

Logical Business Function

Customized

Logical Process

Logical Workflow Entity

Business Object Attribute

Attribute Critical Business Process

Logical Process Logical Workflow

Business Data Domain Logical Business Function

Event Business Object

Relationship Business Data Domain

Critical Business Process Relationship

Entity Event


25/184

Entity Types


Relationships

Collection connects-to Collection

Collection connects-to Column

Collection connects-to Key

Collection connects-to Table

Collection is-implemented by Collection

Collection is-implemented by Column

Collection is-implemented by File

Collection is-implemented by Key

Collection is-implemented by Table

Collection implements Collection


Attribute connects-to Collection

Attribute is-implemented-by Collection

Collection is-connected-to Collection

Collection is-implemented-by Collection

Data type connects-to Collection

Data type is-implemented-by Collection

Enti ty connects-to Collection

Enti ty is-implemented-by Collection

Identi fier connects-to Collection

Identi fier is-implemented-by Collection

Relationship connects-to Collection

Relationship is-implemented-by Collection

Table is-implemented-by Collection

Table 2-7 Collection Properties


TypeStatus: OptionalThe type of the Collection. Maximum of 3 characters.

Nature

Status: Required

The nature of the Collection. The following choices are available: Logical

Physical Relational

Number of elementsStatus: Optional

The number of elements in the Collection. This can be a numeric Value from 0 to 99.

Number of groupsStatus: OptionalThe number of groups in the Collection. This can be a numeric Value from 0 to 99.


26/184

2-12 Entity Types

Entity Types

Column

The Column entity type (Figure2-6) represents a column in a database.

Figure 2-6 Co lumn Proper ties Dialog

Table 2-8 Column Proper t ies


Implementation

nameCol_Imp_Name

Status: Optional


Maximum of 30 alphanumeric characters (18 for DB2 and DBMDatabases), the first of which must be alphabetic.

Column format Col_Type

Status: Required

Default is CharacterThe following choices are available:

Boolean Object Reference (not implemented)

Character Date

Decimal

Graphic Character (DBCS) Image

Mixed Character

Picture

Small Integer or Integer Text

Time

Timestamp VarChar

Column length Col-Length

Status: Generated if column format is Date, Time, or Timestamp.

Required for any other column format.Can contain a maximum of 5 characters

Default is Character

How large the column is. The value range for this property dependson the column format, as shown in Table 2-8.

Column fraction Col_Scale

Status: OptionalCan contain a maximum of 2 characters

Default is 0Number of decimal places. For decimal and picture ColumnFormats, the Column fraction can range from zero to the Column

length. For other Column Formats, this property is irrelevant.

Average length Col_Avg_Length

Status: Optional


The average length of the Column. This can be a numeric Valuefrom 0 to 99,999.


27/184

Entity Types



Attribute connects-to Column

Attribute is-implemented-by Column

Collection connects-to Column

Collection is-implemented-by Column

Data type connects-to Column

Data type is-implemented-by Column

Entity connects-to Column

Entity is-implemented-by Column

Identif ier connects-to Column

Identif ier is-implemented-by Column

Key has Column

Relationship connects-to Column

Relationship is-implemented-by Column

Table has Column

Table is-implemented-by Column

Component

The Component enti ty type (Figure2-7) contains code wri tten in a third-generation computerlanguage, such as C, COBOL, assembler, or PL/I, to do things that the Rules Language either cannot do,or cannot do efficiently. This might be a complicated arithmetic algorithm (such as a square root), non-SQL data access logic (such as an IMS Database interface), or hardware-specific functions.

Components also support the concept of reengineering, where existing applications can be defined tothe repository. Because components are written for a specific processing environment, they are notportable between environments.

Table 2-9 Minimum and Maximum Column Lengths (according to column format)

Column Format Minimum length Maximum length

Character 1 4,000

Date 4 4

Decimal 1 31

Graphic Character (DBCS) 1 2,000

Mixed Character 1 4,000

Picture 1 30

Small Integer or Integer Small: 15; Integer: 31 Small: 15; Integer: 31

Time 4 4

Timestamp 12 12

VarChar 1 4,000


28/184

2-14 Entity Types

Entity Types

Figure 2-7 Component Proper t ies Dialog

Table 2-10 Component Properties


Description Component Status: OptionalUp to 30 characters of additional information that describes the

Component.

DBMS usage DBMS_Usage

Status: Required

Can contain a maximum of 4 charactersDefault is N/A

mDomCompDBMSUsage

Defines if the Component accesses a Database. The following choicesare available:

DB2

DL/I N/A

Execution

environmentExec_Environ

Status: Required

Can contain a maximum of 6 charactersDefault is PC (PC Workstation)

mDomCompExecEnv

The following choices are available: IBM Mainframe Batch

PC User Component

PC Workstation IBM Mainframe (CICS)

IBM Mainframe (IMS)

IBM Mainframe (CICS & Batch)

PC System Component


29/184

Entity Types


Relationships

Component is-accessed-by File

Component owns View

Component refers-to Set

Component uses Component


Component is-used-by Component

Parti tion encapsulates Component

Rule uses Component

Component Folder

The Component Folder is a storage mechanism for objects (like files) that are not generated byAppBuilder. These are objects that do not fall into the usual object categories but the objects can bedescribed (embodied) by fi le representations. Such objects are now represented within the repositoryusing a Component Folder object. Each Component Folder represents one non-AppBuilder object.

Implementationname

Comp_Imp_Name

Status: Optional

Maximum of 8 alphanumeric characters, the first of which must bealphabetic.

Language Language

Status: Required

Can contain a maximum of 8 charactersDefault is C

mDomLanguageThe Language the Component is written in. The following choices are

available: Assembler , C, COBOL, PL/I, JAVA, PTAL

Subroutine (Y/N) Exec_Mode

Status: Required


Default is N

mDomExecutionModeDefines if the Component has a subroutine. The following choices are

available:

Has a subroutine No subroutine

Sys_Source Sys_Source Status: RequiredCan contain a maximum of 3 charactersDefault is N/A

Table 2-10 Component Properties (Continued)



30/184


31/184

Entity Types


Figure2-9 Database Proper t ies Dialog

Relationships

Database contains Table

Database is-accessed-by File

Database is-related-to Database


Parti tion encapsulates Database

Database relates-to Database

Data Type

The Data Type entity type (Figure2-10) records a physical description of data. Typically, you defineinstances of Data Type entity types during business object analysis when you build your data model.

Table 2-12 Database Properties


Machine name Machine_NameStatus: RequiredThe Machine associated with the Database in a Partition.

Maximum of 30 characters.

Type DBMS_Type

Status: Required

Default is DB2

mDomDBMStypeThe Database type. The following choices are available:

DB2 Oracle MS-SQLServer

DB2/UDB

Database directory path DB_Imp_DirectStatus: Required

The run time directory path. Maximum of 100 characters.

Implementation name DB_Imp_NameStatus: OptionalCan contain a maximum of 30 characters


32/184

2-18 Entity Types

Entity Types

Figure 2-10 Data Type Properties Dialog

Table 2-13 Data Type Properties


Data Format

Status: Required

Default is CharacterThe following choices are available:

Boolean Object Reference (not implemented)

Character Date Decimal

Graphic Character (DBCS)

Image Mixed Character

Picture

Small Integer or Integer Text

Time

Timestamp VarChar

Data Length

Status: Generated if column format is Date, Time, or Timestamp. Required for any other

column format.Can contain a maximum of 5 characters

Default is CharacterHow large the column is. The value range for this property depends on the column format, asshown in Table 2-14.

Data Fraction


Default is 0Number of decimal places. For decimal and picture Column Formats, the Column fraction can

range from zero to the Column length. For other Column Formats, this property is irrelevant.

Table 2-14 Minimum and Maximum Field Lengths (according to data format)

Data Format Minimum length Maximum length

Character 1 4,000

Date 4 4

Decimal 1 31

Graphic Character (DBCS) 1 2,000

Mixed Character 1 4,000

Picture 1 30


33/184

Entity Types


Relationships

Data Type composes Data Type

Data Type connects-to Collection

Data Type connects-to Column

Data Type connects-to Key

Data Type connects-to Table

Data Type is-constrained-by Set

Data Type is-implemented-by Collection Data Type is-implemented-by Column

Data Type is-implemented-by File

Data Type is-implemented-by Key

Data Type is-implemented-by Table


Attribute is-typed-by Data Type

Data Type is-composed-of Data Type

Drawing

The Drawing enti ty type (Figure2-11) is a graphic representation of a user-defined model built ofAppBuilder entity and relationship types. Drawing entity types are created on the workstation with thefollowing tools:

Enti ty-Relationship Diagrammer

Process Dependency Diagrammer

State Transition Diagrammer

Matrix Builder

Window Flow Diagrammer

Database Diagrammer

Each Drawing entity has a drawing file with references to the object types in the drawing, but not to theirdefinition. Drawing entity type relationships may not be viewed outside of these environments.

Small Integer or Integer Small: 15; Integer: 31 Small: 15; Integer: 31

Time 4 4

Timestamp 12 12

VarChar 1 4,000

Table 2-14 Minimum and Maximum Field Lengths (according to data format) (Continued)

Data Format Minimum length Maximum length


34/184

2-20 Entity Types

Entity Types

Figure 2-11 Drawing Properties Dialog

Table 2-15 Drawing Properties


Type Drawing_Type

Status: Generated

Can contain a maximum of 3 charactersDefault is State Transition

mDomDrawing

Drawings are diagrams that can be reused.

They are created with Construction Workbench tools.

The drawing type indicates the tool used to make the drawing.For example, the Entity Relationship Diagram tool creates entity-

relationship diagrams.The values for the types of drawings are summarized in Table 2-17.

Table 2-16 Drawing entity type


NameStatus: Required

Common Property

System IDStatus: GeneratedCommon Property

ShortNameStatus: Optional


Drawing_Type

Status: GeneratedCan contain a maximum of 3 characters

Default is State Transition

mDomDrawingDrawings are diagrams that can be reused. They are created with Construction Workbench

tools. The drawing type indicates the tool used to make the drawing. For example, the Entity-

Relationship Diagrammer creates entity-relationship diagrams.The following table shows the values for the types of drawings, as shown in Table 2-17.

Table 2-17 Drawing description and values

Description Values

State Transition 001

Entity Relationship 002

Process Dependency 003

Window Flow 010

Database Diagram 011

Physical Network 012

Data Store vs Entity 013

Function vs Entity 014


35/184

Entity Types



Business Object has-a-state-transition Drawing

Enti ty has-a-enti ty-relationship Drawing

Enti ty has-a-state-transit ion Drawing

Event has-a-process-dependency Drawing

Logical Process has-a-process-dependency Drawing

State has-a-state-transition Drawing

Entity

The Entity entity type (Figure2-12) describes the data an enterprise or organization uses. Typically, youdefine instances of entity object types during business object analysis when you build the data model.For example, an enterprise that rents automobiles might have a customer entity, a reservation enti ty, anda rental location enti ty.

Figure 2-12 Entity Properties Dialog

The following entity types are available:

Function vs Location 015

Entity vs Location 1 016

Entity vs Location 2 017

Organization vs Entity 018

Process vs Entity 019

Organizat ion vs Process 020

Matrix 021

System vs Process 022

Class Interaction 023

Table 2-17 Drawing description and values (Continued)

Description Values


36/184

2-22 Entity Types

Entity Types

Kernel A kernel entity is a basic entity that can exist independently from other enti ties in a logicalmodel. This does not imply that it cannot have a relationship with other objects; rather, it impl iesthe enti ty must be a unique object wi th its own Identifier. A kernel entity should not needrelationships with other entities to be identified.

AssociativeAn associative entity associates two or more kernel or characteristic entities.Associative entities contain non-key properties and can be used to resolve many-to-many

relationships. CharacteristicA characteristic entity is a weak or dependent entity because it requires the

existence of another entity in a logical model. Characteristic entities describe a kernel entity.

IntersectionAn intersection entity associates two or more kernel entities and contains noproperties. An intersection entity is the primary way to resolve many-to-many relationshipsbetween entities.

Table 2-18 Entity Properties


Type Ent_Type

Status: RequiredCan contain a maximum of 20 charactersDefault is Kernel

mDomEntityTypeThe following choices are available:

Kernel

Associative Characteristic Intersection

Expected minimum rows Exp_Min_Rows

Status: Optional


User-defined lower limit of the expected size of the instance(number of Fields). This can be a numeric Value from 0 to

99,999.

Expected maximum rows Exp_Max_Rows


User-defined upper limit of the expected size of the instance

(number of Fields). This can be a numeric Value from 0 to9,999,999,999.

Activity period Exp_Duration

Status: RequiredCan contain a maximum of 5 characters

Default is DaymDomDurarionTime period that describes the frequency of various

operations performed with instances of this entity type. Thechoices are:

Day

Week Month

Year

Quarter

Avg. inserts for period Ave_Wkly_Inserts

Status: Optional


Estimated number of times during implementation thatinstances of this entity type will be created. This can be a

numeric value from 0 to 9,999.

Avg. deletes for period Ave_Wkly_Deletes

Status: Optional

Can contain a maximum of 4 charactersEstimated number of times during implementation thatinstances of this entity type will be deleted. This can be a



37/184

Entity Types


Relationships

Enti ty connects-to Collection

Entity connects-to Column

Entity connects-to Key Enti ty connects-to Table

Enti ty has-a-enti ty-relationship Drawing

Enti ty has-a-state-transit ion Drawing

Entity has State

Entity has Identifier

Entity is-accessed-by Project

Entity is-described-by Attribute

Enti ty is-implemented-by Collection

Entity is-implemented-by Column Entity is-implemented-by File

Enti ty is-implemented-by Key

Enti ty is-implemented-by Table

Enti ty is-modified-by Development Project

Enti ty is-modif ied-by Logical Process

Enti ty is-related-via Relationship

Entity owns View


Assumption is-supported-by Enti ty

Business Object owns Enti ty

ER View involves Enti ty

Function intersects-with Entity

Goal is-supported-by Entity

Information Need is-supported by Enti ty

Avg. updates for period Ave_Wkly_Updates

Status: Optional

Can contain a maximum of 4 charactersEstimated number of times during implementation that

instances of this entity type will be updated. This can be a


Expected rows Exp_Rows

Status: Optional

Can contain a maximum of 10 charactersThe number of instances of this entity type expected when

you define the data model. This can be a numeric value from0 to 9,999,999,999.

N/A AveGrowthRateStatus: Optional

Can contain a maximum of four characters

Table 2-18 Entity Properties (Continued)



38/184

2-24 Entity Types

Entity Types

Logical Process affects Entity

Problem affects Enti ty

Problem is-caused by Entity

Process impacts Entity

Success Factor is-supported-by Entity

Event

The Event entity type (Figure2-13) represents an incident that acts as a stimulus to a business, system orobject. It usually causes some activity or processing to be undertaken and may change the state of objectswithin the business or system. Events can be classified as external, internal or temporal. Examples areCustomer_Calls, Accident_Reported, or Customer_Enters.

Figure 2-13 Event Properties Dialog

Relationships

Event causes Transition

Event composes Event

Event is-composed-of Event

Event has-a-process-dependency Drawing


Table 2-19 Event Properties


Description Event_Description

Status: Optional

Up to 30 characters of additional information that describes theevent.

Event type Event_Type

Status: Optional

Up to 10 characters of additional information that describes thetype of event.

Event class Event_Class


Default is External

mDomEventClassThe choices are: External, Internal, Temporal


39/184

Entity Types


Event triggers Process

Event triggers Logical Process


Logical Process initiates Event

Business Object owns Event

Field

The Field entity type (Figure2-14) records information about part of a file (such as a column in a DB2Table), or part of the input or output definition of other entity types (such as the view owned by awindow). The properties of a field describe the type and size of the data it contains.

The Field entity type is where you store the definition for each of the fields your application uses. Theproperties of the Field entity type allow you to specify part icular quali ties for the data that can populatethat field (such as integers, characters, and decimals). Also, see Includes (is-included-in) on page3-20,

and View on page2-58.

Figure 2-14 Field Properties Dialog


40/184

2-26 Entity Types

Entity Types

Table 2-20 Field Properties


Field picture-storage DB_Pic

Status: Required if Field format is PictureStatus: Irrelevant for other Field formats

Form in which the Fields Value should be stored, using the

standard COBOL editing characters S (signed number), V(virtual decimal point), and 9 (numeric Value).

Field picture-display Screen_Pic

Status: Optional if Field format is PictureStatus: Irrelevant for other Field Formats

Displays the Field Values as shown in Table 2-21, using thestandard COBOL editing characters.Note: A picture Field can accept 30 display characters, but

only 18 of them can be numeric Value (9) characters. This isa COBOL limitation.

Screen literal-long Screen_Lit

Status: OptionalStatic text Window Painter and Report Painter use as a Field

label when the Field is pasted onto a window. Maximum of 24

characters.

Field format Field_Type

Status: Required

Default is CharactermDomFieldTypeThe Fields data type. The following choices are available:

Boolean Object Reference

Character Date

Decimal

Graphic Character (DBCS) Image

Mixed Character

Picture Small Integer or Integer

Text

Time

Timestamp VarChar

Field length Fld_Len

Status: Generated if Field Format is Date, Picture, Time, or

TimestampStatus: Required for any other Field Format


Default is 15The Value range for this Attribute depends on the Field Format,

as shown in Table 2-22.

Field fraction Fld_Frac

Status: Generated if Field Format is Picture

Status: Required if Field Format is Decimal

Status: Irrelevant for any other Field FormatCan contain a maximum of 2 characters

Default is 0Number of decimal places in the Field. For Decimal Fields, theField fraction must be greater than or equal to 0 and less than

or equal to the Field length.

Range-minimum value Field_Min

Status: Optional if Field Format is Decimal, Integer, Small

Integer, or Picture

Status: Irrelevant for other formatsCan contain a maximum of 30 characters

The minimum value that can be stored in this field.


41/184

Entity Types


Range-maximum value Field_Max

Status: Optional if Field Format is Decimal, Integer, Small

Integer, or PictureStatus: Irrelevant for other formats


The maximum Value that can be stored in this field.

Reference table name Field_Ref

Status: Optional

Can contain a maximum of 8 charactersSystem ID of the instance of the set entity type associated with

the field and that lists acceptable inputs.

Screen literal-short Screen_Lit_ShortStatus: OptionalUp to 12 characters of static text that report Painter uses as a

fields short screen literal property.

Implementation name Field_Imp_Name

Status: Optional

Name that becomes the DB2 column name. It is limited to 18characters and must conform to the naming standards for theapplications database.

Table 2-21 COBOL Editing Characters and Field Display Forms

COBOL edi ting characters Field display form

9 numeric value

* check protection

, comma

+ plus sign

- minus sign

$ floating currency symbol

. decimal point

S sign

Z leading zero suppression

B embedded blank

CR credit

DB debit

Table 2-22 Minimum and Maximum Field Lengths (according to field format)

Field format Minimum length Maximum length

Character 1 4,000

Date 4 4

Decimal 1 31

Graphic character (DBCS) 1 2,000

Mixed character 1 4,000

Picture 1 30

Small integer or integer Small: 15; Integer: 31 Small: 15; Integer: 31

Time 4 4

Timestamp 12 12

VarChar 1 4,000

Table 2-20 Field Properties (Continued)



42/184

2-28 Entity Types

Entity Types

Relationships

Field has Help Text

Field refers-to Set

Field uses Language


File is-keyed-by Field

View includes Field

File

The File enti ty type (Figure2-15) represents a physical data file on a disk. Rules and components canread from and write to disk files whose file entity types they are related to. Files can be automaticallygenerated by AppBuilder tools.

Figure 2-15 File Properties Dialog

Table 2-23 File Properties


File type File_Type


Default is DB2

mDomFileTypeThe following value is available in the list box:

XA DB2 File

DBM Informix

Sybase

Oracle DB2/2

DB2/6000

Tandem

Illustra Ingres

DB2/400

MS-SQLServer DB2/UDB

Implementation name File_Imp_Name

Status: Required

Name that becomes the DB2 Table name. It is limited to 30characters and must conform to the naming standards for the

applications database.


43/184

Entity Types


Relationships

File is-forwarded-to File

File is-keyed-by Field

File owns View


Attribute is-implemented-by File

Collection is-implemented-by File

Component is-accessed-by File

Part it ion encapsulates File

Data type is-implemented-by File

Database is-accessed-by File

Entity is-implemented-by File

Identifier is-implemented-by File

Relationship is-implemented-by File

Rule is-accessed-by File

Table is-implemented-by File

Function

The Function entity type (Figure2-16) represents one of the major classes of activities for an enterprise,such as leasing, sales, and inventory control. Typically, you define instances of function enti ty typeswhen you build the process model during analysis. In the execution environment, function names

appear on the start-up menu bar. A function typically decomposes into one or more processes that canfurther decompose into additional processes.

Figure 2-16 Function Properties Dialog


44/184

2-30 Entity Types

Entity Types

Relationships

Function has Bitmap Function intersects-with Entity

Function refines-into Process

Function part it ioned by Application Configuration; the relationship already exists in the list ofrelationships


Part it ion encapsulates Function

IdentifierThe Identifier entity type (Figure2-17) is a logical key that becomes a physical key during databasedesign. An identifier consists of one or more properties that uniquely identify an instance of a parententity or cross-reference another entity.

Figure 2-17 Identif ier Properties Dialog

Table 2-24 Function Properties


Menu description Menu_DescStatus: RequiredUp to 30 characters of text that appears as the first

level of the menu bar.

Sub-process menu type Child_Menu

Status: RequiredDefault is Menu Bar

mDomChildMenuIndicates how the processes under this function appear

in the interface. The choices are: Menu Bar Pull-Down

No menu (Batch)

Application ID Work_Station_Group

Status: Optional

Up to 8 characters that identify a group of applicationsgrouped under this function.


45/184

Entity Types


Relationships

Identi fier connects-to Collection

Identif ier connects-to Column

Identi fier connects-to Key

Identi fier connects-to Table

Identi fier i s-composed-of Relationship

Identifier is-composed-of Attribute

Identi fier is-implemented-by Collection

Identif ier is-implemented-by Column

Identifier is-implemented-by File

Identi fier is-implemented-by Key

Identi fier is-implemented-by Table


ER View involves Identi fier

Entity has Identifier

Key

The Key entity type (Figure2-18) describes a key in a database. You can use a key to enforce referentialintegrity and uniqueness constraints.

Figure2-18 Key Proper t ies Dialog

Table 2-25 Identifier Properties


Type Ident_Type

Status: RequiredDefault is Primary

mDomIdentifierType

The following choices are available in the list box: Primary (key most frequently used)

Alternate (second most frequently used key)

Candidate (potential, but not preferred key)


46/184

2-32 Entity Types

Entity Types

The types of key are:

Foreign A foreign key is a unique index into another table and can be used to join two tables. Aforeign key is one or more columns that uniquely identify rows in another table that associates twoentit ies through a relationship.

Primary A primary key (the only required key) is one or more unique columns that identif ies asingle instance (a row in a table) of an entity.

Index An index key is one or more non-unique columns that can locate more than one of anentitys instances.

Relationships

Key has Column


Attribute connects-to Key

Attribute is-implemented-by Key

Collection connects-to Key

Collection is-implemented-by Key

Data type connects-to Key

Data type is-implemented-by Key

Enti ty connects-to Key

Enti ty is-implemented-by Key

Table 2-26 Key Properties


Type Key_DBType

Status: RequiredDefault is Index

mDomDBtypeKey

The type of the key. The following choices are available in the listbox:

Foreign

Primary Index

Unique (check box) Unique

Status: RequiredmDomBoolean

Specifies whether the key is unique. The choices available are: Yes No

Deletion method Key_Delete_Rule

Status: Required

Default is Null

mDomKeyDeleteRuleIndicates the method of the rule deletion. The following choices

are available in the list box:

Restrict Cascade

Null

Implementation name Key_Imp_NameStatus: OptionalMaximum of 30 characters

N/A Update_Rule Status: Optional


47/184

Entity Types


Identi fier connects-to Key

Identi fier is-implemented-by Key

Relationship connects-to Key

Relationship is-implemented-by Key

Table is-implemented-by Key

Table has Key

Table table is-referenced-by Key

Logical Process

The Logical Process entity type (Figure2-19) represents an action performed to satisfy a businessrequirement. A logical process is the smallest unit of work that it is useful to describe.

Figure 2-19 Logical Process Properties Dialog

Table 2-27 Logical Process Properties


Description

Status: Optional

Up to 30 characters of additional information that describes the Logical

Process.

LogPro_Type

Status: Required

Default is Capture

mDomLogicalProcessType

Designates the action the Logical Process performs. The following choices areavailable in the list box:

Capture

UpdateDelete

Associate

RetrieveCalculate

Validate

LogPro_Mode

Status: RequiredDefault is Action

mDomLogicalProcessMode

Designates the type of Logical Process. The following choices are available inthe list box:

Decision

Action Logical function


48/184

2-34 Entity Types

Entity Types

Relationships

Logical Process affects Entity

Logical Process contains Data Flow

Logical Process data-content-defined-by ER View

Logical Process depends-on Logical Process

Logical Process has-process-dependency Drawing

Logical Process initiates Event

ResponseNeeded

Status: Optional

Default is DaymDomDuration

The following choices are available in the list box:

Day Week

Month

Year Quarter

Minute

Hour Second

TransationCenter

Status: OptionalDefault is No

mDomBooleanThe following choices are available in the list box:

Yes

No

CentralTransform

Status: Optional

Default is NomDomBoolean


Yes No

LeafProcess

Status: Optional

Default is NomDomBoolean


Yes No

FrequencyStatus: OptionalCan contain a maximum of 4 character

Default is 0

FrequencyUnit

Status: Optional

Default is DaymDomDuration


Day Week

Month

Year Quarter

Minute

Hour Second

Table 2-27 Logical Process Properties (Continued)



49/184

Entity Types


Logical Process is-composed-of Logical Process

Logical Process is-implemented-by Rule

Logical Process is-signatured-by Data Flow

Logical Process is-supported by Opportunity

Logical Process is-supported by Problem

Logical Process supports Information Need

Logical Process supports Success Factor


Assumption is-supported-by Logical Process

Business Object owns Logical Process

Context Diagram contains Logical Process

Development Project includes Logical Process

Enti ty is-modif ied-by Logical Process Event triggers Logical Process

Goal is-supported by Logical Process

Problem affects Logical Process

Problem is-caused by Logical Process

Transition tr iggers Logical Process

Machine

The Machine enti ty type (Figure2-20) represents a workstation in a physical network.

Figure 2-20 Machine Properties Dialog

.


50/184

2-36 Entity Types

Entity Types

Relationships

Machine can-access Machine


Cell contains Machine

Part it ion encapsulates Machine

Migration

The Migration enti ty type (Table 2-29) is the focus of all migration activity. You use it to findinformation about migration, to specify migration action processing options, to view the results of batchprocessing jobs, and to organize and manage rout ine migrations. I t can be thought of as the envelopethat contains the object, object hierarchies, or migration root entity during source repository processing.

Table 2-28 Machine Properties


Operating system OS_Type

Status: RequiredDefault is MS-Windows NT

mDomOSType

The operating system executing on the machine.The following choices are available in the list box:

AIX

CICS/MVS CICS/OS2

HPUX

IMS MVS

OS/2

OS/400

SunOS Windows NT

OS release OS_ Release

Status: Optional

The version of the operating system executing on the machine.Maximum of 30 characters.

Machine group Mc_GroupStatus: OptionalThe group to which the machine belongs. Maximum of 30

characters.

Implementation name Mc_Imp_NameStatus: OptionalCan contain a maximum of 30 characters

Default is Local


51/184

Entity Types


The values for the migration states are summarized in Table2-17.

Relationships

Migration is-profiled-by Group

Table 2-29 Migration Properties


Mig_State


Default is No Action Executed

mDomMigStateRefer to Table 2-30for a list of migration states and their values.

Mig_DSNStatus: OptionalCan contain a maximum of 44 characters

Return_CodeStatus: Optional


Table 2-30 Migration states

Description Values

No Action Executed 0

Export Job Submitted 0001Export Job Executing 0002

Export Job Failed 0003

Export Job Successful 0004

Export Job Approved 0005

Load Job Submitted 1001

Load Job Executing 1002

Load Job Failed 1003

Load Job Successful 1004

Load Job Approved 1005

Analyze Job Submitted 2002

Analyze Job Executing 2002

Analyze Job Failed 2003

Analyze Job Successful 2004

Analyze Job Approved 2005

app build information model

Documents