-------
OSWER DIR.//9023.00
cj
C/3
V •• X
a < £
NOIJ.INIJ
kl
Q
f*
J
3
^
•3
e
o
e «•
ly and docur
i requirement
s 2
S 4
U 73
2
. 5"
2 e
e s
S f S
•J A .2
5 — a.
3 «
led Data Req
iicmcnts Dai;
Management
3 a m
— f —
u u •
a at c
CJ
3
r\
ACTIVITIES
PRODUCTS
S_
2
-
r-
Z
en
kl
i-
1
2
•5
u
_3
"5
>
C
at 5;
e -
11
2 5
« «•
tu 5 '
ez
u —
J?Q
73 2 O
4^
•v
PRODUCTION
s
. «
-7 •"
1 1
J£
C)pcraie/use data
Maintain and en
^ § s4
11 =
flB ••• ^
Production Data
Production Data
Dau Managemci
-------
OSWER DIR.//9023.00
2
i
il
£VJ
OH
vis
14
P
I
10-16
-------
OSWER DIR.//9028.00
C/3
r •
>w
C
e
",1
z
X
g
Ul
2
3
O
Q
NEW/UPDA1
MM
6
O
H
<
£
latHNi Decision Paper
ijcct Management Plan
i £
ai
•s ' i
•2 1
j i
•o t
oblcm (the solution
icfil).
rail project (or syslci
tUnale.
s. r: o «•
_ J5 5 «
Describe information nunagemcn
represents the overall objective or
Prepare a preliminary estimate of i
represents Ihc initial high level Co
I
^
z
I
I
i
3 3
9 5-
— 1 1
1" a "«
l s. r
tl -w. ?
>icm Cunccpt (Contains complcti
nccpt Dccutoa Paper (Summaq
Project Management Plan (Sunn
JTO |
Z 3
^
*
3 ..
:ycle benefits and co
detail u possible fa
£ "^
Pcrfonn assessment of complete Ii
alternative approaches, with as mu
recommended system concept.
s
u
p
1
|
1
3 I
! f
1 r
>. c
imtiun Decision Paper (Summar
Project Management Plan (Sum
£ t
I J
"^ ^
M S
t better undenundin
al and dau rcquucm
J2 I
Refine and/or revise analysis to rcf
benefits and costs of specific functj
Z
$
1
^
i
s -^
3 •»
i !
s i
ign Dcasion Papa (Summary p
Project Management Plan (Sum
^ 1
1 1
•3
M
i belter undenundin
ksigo fealurca.
J2 S
Refine and/or nvisc analysis lo rcf
bencfiu and cosU of specific sysic
Z
2
a
•£
1
1
3
I I
! 1
i>
iclopmcnl Dcasion Paper (Sunui
Project Management Plan (Sum
& ~i
1 1
si
J2
y
1 the impact of any c
upincnt. and the imp
ne
a-z —
w ~
e= > ^
Refine and/or revise analysis to rcl
Ihc system design nude dunng DC
known changes to be made in the 1
fc
Z
1
!>
Q
a
|
3
g ^
9 s
c 3.
1 ^
r |
ilcmenunon Decision Paper (Sui
Project Management Plan (Sum
1 5
1 1
2-8
*J —
si
J §•
i ihc impact of any c
mcnuoon. and the n
. future.
w u U
r= "5. 'S
Refine and/or revise analysis lo rcl
the system design made dunng Im
any known changes to be nude in
O
<
1
3
-
1
u
90
|
1
^
g
f
s 1
icm Change Requests (or cquival
Project Management Plan (Sumi
enhancements only)
J? i
1 i
*5
3
3
|
•a
W
I
•9
Conduct benefit-cost analyses of in
enhancements lo the system.
Z
i
§
a.
1
U
|
1
1
s
m
1
r
tem Evaluation Reports
Project Management Plan (Sunn
enhancements only)
>> -^
1 I
1
cxpcncncc to date, i
a
Update benefit-con analysis lo re 11
recommended future changes.
Z
2
Si
•
1
Z
>
0
X
10-17
-------
-------
OSWER DIR.//9023.00
APPENDIX A: GLOSSARY
This appendix defines key terms used in OSWER1s System Life
Cycle Management Guidance and related documents.
TERM
DEFINITION
Acceptance
Testing
Access
Approval
Archive
Archive Data
Audit
Testing performed by program staff (not project
staff) during Implementation to verify that the
system solves the information management
problem, performs satisfactorily, and is ready
for release to users.
The operation of
extracting) data.
viewing or copying (including
An examination of life cycle products, and the
results of the project review process, by OSWER
program management. The approval process has
three purposes: first, to confirm che results
(i.e., the concepts, products, and management
direction) of life cycle efforts to date;
second, • to approve continuation with the next
stage of 'the life cycle; and third, to confirm
the continued commitment of resources to the
project. The OSWER life cycle model requires
formal approvals at the end of the Initiation
and Concept phases, and the Definition, Design,
Development; and Implementation stages.
The third stage of the Operation phase, and the
final stage of the system life cycle. Its
purpose is to terminate the operation of the
system in an orderly, planned manner, ensuring
that software and data are properly archived or
incorporated into other systems.
The routine storage of data for an operational
system, usually done to provide efficient
performance. For example, archiving certain
data at the end of a fiscal year.
A guidance- and standards-oriented examination
of the products and related documentation
contained in a baseline to assure that they are
complete, clearly presented, and internally
consistent to support a product review. The
OSWER life cycle provides for five audits;
Concept, Definition, Design, Development, and
Operational. Audits are performed by the
project staff. Any audit may be repeated as
A-l
-------
OSWER DIR.//9028.00
Baseline
Change
Change Control
Concept
Conceptual Data
Model
Configuration
Accounting
necessary. A system life cycle audit is not the
same as, and is not intended to substitute for,
an audit conducted by the Office of the
Inspector General (OIG).
The set of life cycle products and other related
documentation which officially comprise the
system at a given point in time. The OSWER life
cycle model provides for five baselines:
Initiation, Definition, Design, Development, and
Operational. The products contained in each
baseline are always reviewed prior to inclusion
in the baseline.
A modification to the system or data base(s) for
maintenance or performance purposes, without
affecting the functionality or structure of the
system or data base(s). Other modifications,
which do alter the functionality structure, are
referred to as enhancements.
A process for controlling modifications (i.e.,
changes and enhancements) to a system. Change
control provides a review of requested
modifications, and consideration of their impact
on a system, before they are made; it also
ensures that modifications are made in a manner
that does not disrupt ongoing system operation.
The second phase of the system life cycle. This
phase provides a high level of functional and
data requirements that relate to an information
management problem, and a comprehensive model of
a solution to meet the requirements.
A depiction of data requirements from an
organizational perspective. Corresponds to the
conceptual schema of a three-schema architecture
as defined by the American National Standards
Institute. Entity relationship diagrams are
often used to depict the conceptual data model.
The conceptual data model forms part of the
System Concept.
A process for maintaining system baselines,
including adding products to a baseline,
denoting the components of each product
(referred to as configuration items), and
monitoring and recording the disposition of
requested modifications to the system.
4
A-2
-------
OSWZR DIR.//9023.00
Configuration
Management
Custodianship
Data
Data
Administration
Data
Administration
Program
Data Attribute
Data Base
A function which serves to systematically
identify the items that make up a system, and
formally control any modifications to those
items, in order to help maintain the integrity
of the system, and facilitate communication
about the system throughout its life cycle.
The functions and responsibilities of an
organization, such as an ADP organization, with
physical custody of data that supports the work
of another organization, such as a program
office. For example, the custodian ensures the
physical integrity of the data and software
under its control; safeguards the media storing
data; ensures the data is secure from
unauthorized access, modification, or
destruction; makes data accessible to users; and
implements requested hardware or software
modifications.
Representations of facts,
instructions in symbols
communication, interpretation
human or automated means.
concepts, or
suitable for
or processing by
The management function responsible for the
planning, definition, organization, protection,
and efficiency of data and data bases within
OSWER. The goal of Data Administration is the
cost-effective provision of data of sufficient
quality to support the OSWER mission.
A management initiative which includes policies,
standards, and procedures that increase an
agency's knowledge and management of the:
composition of data, source of data, processing
of data, meaning of data, flow of data, and
dissemination
Administration
management of
that address:
determination,
or collection,
data usage
data disposal.
of data. A successful Data
program will improve the
data by introducing procedures
data standards, data requirements
data definition, data acquisition
data processing, data storage,
including sharing and access), and
A characteristic of a unit of data such as
length, value, or method of representation.
A collection of interrelated data stored
together with controlled redundancy to serve one
or more systems or applications.
A-3
-------
OSWER DIR.//902S.OO
Data Base
Management
System (DBMS)
Data Collection
Data Definer
Data Dictionary
Data Element
Data Entity
Data
Independence
Data Integrity
Data Life Cycle
Data Management
A software system facilitating the creation and
maintenance of a data base and the execution of
computer programs using the data base.
The recording and capturing of data on behalf of
an organization.
The person or organization who determines the
essential qualities or meaning of data, and who
prescribes and defines procedures which
aggregate and refine data. This includes
describing the formatting of the resulting
information to serve a specific decision-making
context.
A centralized repository -of information about
data, including its meaning, relationship to
other data, origin, usage and format.
The smallest unit of data that has meaning in
describing information. A piece of'data which
would not be meaningful if decomposed further.
See "Entity"
The property of a data base management system
that enables data to be processed independently
of access mode, storage method or arrangement.
Data independence reduces the need to modify
Data independence
application programs wnen
access methods are modified.
data storage and
The quality of data that exists as long as
accidental or malicious destruction,
modification, or loss of data are prevented.
This results in preservation of data in its
intended format, length and contents while
within a data base.
The data life cycle begins with the definition
of data to support new regulations or other
program needs, and includes strategic data
planning, data standardization, and the methods
and standards during the collection, storing,
accessing, and archiving of data.
A subfunction of Data Administration which is
responsible for data-related activities of the
system life cycle, such as logical data modeling
during requirements definition, data base
design, data base management, and the -
documentation of data-related decisions and •
products.
A-4
-------
OSWER DIR.//9023.00
Data Security
Data
Stewardship
Decision Paper
Definition
Definition and
Design
Design
Design Data
Dictionary
Development
The protection of data against unauthorized
disclosure, transfer, modification, or
destruction, whether accidental or intentional.
See "Stewardship"
A decision document presented to management. It
summarizes those aspects of the analysis and
decisions of a given phase or stage that are
important to program management, and requests
approval to continue the project. The OSWER
life cycle model provides for Decision Papers to
be prepared at the end of Initiation, Concept,
Definition, Design, Development, and
Implementation.
The first stage of the Definition and Design
phase. Its purpose is to define specific,
detailed functional and data requirements for
the system within the context of the System
Concept.
The third phase of the system life cycle,
consisting of two stages: Definition and Design.
(See individual definitions of each of these
terms).
The second stage of the Definition and Design
phase. Its purpose is to produce detailed
specifications for the system to meet the
functional and data requirements within the
context of the System Concept.
Data dictionary created during Design to support
design and development of the information
system. It represents an expansion of the
Requirements Data Dictionary, and contains all
the metadata stored in dictionary. In addition,
it contains descriptions of the physical data
base structures and the manner in which they are
implemented in the test versions of the daca
base(s). These descriptions include physical
records, segments, data sets (or files), keys,
block sizes, data set allocation, and physical
size limits.
The first stage of the Development and
Implementation phase. Its purpose is to produce
a system which is ready for acceptance testing
and suitable for implementation.
A-5
-------
OSWER DIR.//9023.00
Development and
Implemencation
Domain
Enhancement
Entity
Evaluation
Implementation
Information
Information
System
The fourth phase of the life cycle. Its purpose
is to produce a complete system, fully tested
and available for use in normal production mode.
There are two stages 'in this phase: Development
and Implementation.
A set of all values that a particular data
element may posses in actual or potential usage.
A modification to a system that results in
substantially improved capabilities and, in some
way, alters the functionality or structure of
the system. Other modifications, which do net
alter the structure, are referred to as changes.
Examples of enhancements include the addition cf
new data elements, changing the system (or a
part of the system) to run in a different
software environment, and replacing data entry
screens to improve the user interface and/or
improve performance.
A person, place, thing, concept, or event that
is of interest to an enterprise. An entity is
something about which we store data. Examples
of entities are: waste site, contract, EMPLOYEE.
An entity has various attributes, or data
elements, which should be recorded. Examples of
data elements for the entity "contract" could
include CONTRACT-NUMBER, DATE, and
OBLIGATION-CEILING.
The second
purpose is
effectively
operating
managed.
stage of the Operation phase. Its
to determine whether the system is
meeting the stated requirements, is
efficiently and is effectively
The second stage
Implementation phase.
a fully tested system
at start-up, and to
the intended users.
of the Development and
Its purpose is to produce
containing the data needed
provide needed training to
Any set of data which has been aggregated by
processing in order to establish a specific
meaning and serve in a decision-making context.
See "System"
A-6
-------
OSWER DIR.#9023.00
Initiation
Integration
Testing
Internal
Testing
Life Cycle
Life Cycle
Management
Logical Data
Model
Maintenance
The first phase of the system life cycle. Its
purpose is to define an information management
problem within OSWER and to determine whether
resources should be committed to exploring ways
to address it.
Testing performed by project staff during
Development, following the completion of unit
tests for individual components. Components are
assembled in the development environment and
tested to verify that they function correctly
together. Integration testing is iterative,
testing additional modules for which unit tests
are successfully completed.
The first kind of testing performed by project
staff during Development. While each system
component is being developed, it is continually
checked to assure that it is internally
consistent and conforms to specifications.
See "System Life Cycle"
The process of managing a system through its
life cycle. As practiced by OSWER, it is not a
rigid process, but rather a disciplined means
for selecting and practicing the management
approaches and techniques that are most
appropriate for a given information management
problem and/or system.
A depiction of the logical, or programmatic,
data needed to support an organizational
mission. The components of a logical data model
include data entities and relations, data
elements and attributes, keys, secondary keys,
and relationships between entities (if data
entities are used). The logical data model is a
more detailed depiction of the conceptual data
model of an organization. It may correspond to
the external schema as defined by the American
National Standards Institute. The logical data
model forms part of the Detailed Data
Requirements.
The set of activities that keep a system and
data base(s) in operating condition.
Maintenance also focuses on optimizing the
existing system and data base(s), without
affecting functionality or the structure of the
system or data base(s).
Metadata
Data about data, such as
physical characteristics.
its definition or its
A-7
-------
OSWER DIR.09028.00
Modification
Normalization
Operation
Phase
Privacy
Production
Production
Dictionary
Data
Project
A change
"Enhancement
or
enhancement
See "Change,"
The process of reducing a logical data model
(structure) to its most basic form, so that the
data model is stable, flexible, and without
redundancy. A normalized data model is composed
of normalized data entities. A normalized data
entity includes no repeating . groups or data
elements among its attributes, contains
attributes (data elements) only about the entity
being described, and does not include attributes
which are dependent on the key of another
entity.
The fifth phase of the life cycle. Its purpose
is* to operate the system in normal production
mode, monitoring and maintaining its
performance, until the end of the life cycle,
and then to terminate operation. There are
three stages in this phase: Production,
Evaluation, and Archive.
The major
There are
segments of the system life cycle.
five phases in the OSWER system life
cycle: Initiation; Concept; Definition and
Design; Development and Implementation; and
Operation.
The right of
constrain the
themselves.
individuals or organizations to
collection and use of data about
The first stage of the Operation phase. Its
purpose is to make the system available to
users, and make required changes and
enhancements to ensure that it contains to
address the information management problem in a
cost effective manner.
Data dictionary produced during Implementation
by copying the metadata in the last version of
the Design Data Dictionary, for use in testing,
implementing, and operating the production
system.
An organized effort to solve an information
management problem. In most cases, a project
extends over the entire system life cycle. In
some cases a project extends only through the
portion of the life cycle that can be foreseen
with confidence, e.g., through Production if the
timing for ceasing operation is uncertain.
A-8
-------
OSWER DIR.//9028.00
Project
Execution
Project
Management
Quality
Assurance
Record
Release
Management
The set of activities which produce the concept,
definition, design, and production versions of a
system.
The set of activities which monitor and control
project execution to ensure that they are
performed • effectively and in accordance with
applicable policies, guidances and practices;
and that its products solve the identified
information management need.
A function that ensures that all products of the
life cycle are substantively accurate and
address the stated information management
problem. Quality assurance is accomplished
through the efforts or skilled professionals on
the project team, and through formal reviews.
A group of related data elements
unit by an application program.
treated as a
The functions and responsibilities associated
with the implementation of modifications to an
operational system during the Production stage,
and making the revised system available at all
user locations.
Requirements Data dictionary produced by data modeling
Data Dictionary activities during Concept and Definition.
Metadata recorded about each data entity and
data element includes name, programmatic
definition, purpose, data steward, data definer,
and source.
Review
A formal, quality-oriented examination of a set
of related products, to verify that they solve
the information management problem. The OSWER
life cycle model provides for five reviews:
Concept, Definition, Design, Development, and
Post-Implementation. Reviews are performed by
designated OSWER program staff and supporting
program and technical experts. Any review may
be repeated as necessary to ensure that all
deficiencies in the products have been fully and
adequately addressed.
Shared Data
Data stored that is created, accessed, updated,
or deleted by more than one organizational unit.
A-9
-------
OSWER DIR.//9028.00
Stage
Stewardship
System
System
Component
System Concept
System Decision
Paper
The segments of the system life cycle that occur
within certain larger phases. The OSWER system
life cycle divides the Definition and Design
phase into two stages: Definition and Design.
The development phase is divided into two
stages: Development and Implementation. The
Operation phase is divided into three stages.:
Production, Evaluation, and Archive. The phases
Initiation and Concept are not divided into
stages.
The functions and responsibilities of an
organizational entity that exercises control
over data on behalf of OSWER. Organizations
that require data to be collected, processed,
stored or used in support of OSWER's mission
have stewardship responsibilities. These
responsibilities include ensuring that: (1) Only
data relevant to OSWER1s missions is collected.
(2) Data that is collected is of sufficient
quality to support OSWER's missions. (3) Data
is reused wherever appropriate within OSWER.
(4) Data is clearly defined and documented in
compliance with established directives. (5)
systems practices under the organization's
stewardship conform t'o EPA Data Administration
guidance.
An organized set of functions, data, procedures,
hardware, software, communications, and/or
documentation which enables OSWER to solve a
specific information management problem. A
system need not necessarily be automated; but
most instances of life cycle management will
apply to automated information systems.
A well-defined portion of an information system.
Categories of components include, but are not
limited to, hardware, software, communications,
procedures, reference manuals, user procedures,
system administrator procedures, and user
support materials.
A high-level complete description of a system
(including data, processing capabilities,
hardware, software and communications). It is
produced during the Concept phase and serves as
both a check on the validity and completeness of
the problem, and the basis for defining more
detailed functional and data requirements.
See "Decision Paper"
A-10
-------
OSWER DIR.09028.00
System Life The evolution of a system from the initial
Cycle identification of an information management
problem through system termination or
replacement.
System Testing Testing performed by project staff during
Implementation, following integration testing
and prior to acceptance testing.. The completed
system is installed in a simulation of the
production environment and tested to verify that
the system operates correctly in its entirety
and satisfies the functional and data
requirements. (Note: the term "system testing"
is also used to refer generically to all testing
performed by project staff: internal, unit,
integration, and system testing.)
Threshold The process of determining the appropriate
Analysis review and approval levels for an OSWER system
project.
Unit Testing Testing performed by project staff during
Development, as each system component is
completed, to ensure that it operates correctly.
Walkthrough A . highly-structured meeting to re'view the
completeness and quality of selected module(s)
of the system, or of the entire system..
Walkthroughs are usually conducted by the
project team, often are intended by user
representatives, and may be held at any point in
the system life cycle.
A-ll
-------
OSWER DIR.//9028.00
APPENDIX B: PRODUCTS
This Appendix presents a comprehensive outline of
each system life cycle product (i.e., the material
to be contained in the product by the stage during
which it is completed).
-------
-------
OSWER DIR.//9028.QO
3ADDHV
at at,
CJ CJ
NOLLVmVA3
as *
Cfl
H
Q
O
H
Z
o
<
2
ocatececatet at at at atat atotat atx atac, otat at at at
NOLLVlNHWiTkiWl
at at otat at at at at at atat at at at at at at at at at
at atat atat at at at atat atatu OU (J
C/3
«i
O
£
M
«
s, ^,
.1
!i*
I |*
f 3l.i
1 Ta8
•g ScSd8
a ii 3
il1
i.H
f C U _
v- ij"^"^
e >>U"o
2-2 Ji 2
?.I5
'
o. a "r W R
:j3i££
t» -5
i^
H
S.3
S.Tj-3
S3 O
->"32-
L| £ I
j 2^ f
i-agl
!£8I
• ^
ti
<
53
u ^
l!
si
P
it i i (_ i i i t i i i i i i i i * i
-------
.-J .
Z
o
u
£!
Q
^:
O
H
Z
rv
-
— 4 E
O v.
-t 41
•W W
fl u
N fl
—4 3
C CP
fl TJ
u 4)
O Z
I
1
solution is
fl
j=
u
in j£
C X
O
-4 e
4V ->4
fl S.
N *V
•^4 '+4
c s
fl
IT 4>
w E
O fl
u
41 TJ
0 C
fl
fl E
4V L|
C 4)
41 4V
4) 4V
U Li
U O
C £
~« in
i
i
e.
4>
f—i
XJ
0
u
O>
4)
J£M
w
o*
c
.>
o
in
, information,
in
4)
u
3
TJ
4*
U
O
U
a
4V
C
41
U
Wi
3
U
4V
C
41
C
.-4
4V
U
41
a.
in
0)
4V
in
^
in
TJ
fl
41
in
4V
..4
tv
4)
C
41
.2
T3
C
fl
in
4)
£
O
U
4V
3
0
"2
4V
U
01
a
X
u
improved
*
in
C
o
•vH
4V
fl
3
4)
U
f
4V
.^
S
4>
U
C
fl
•—*
a.
o
u
fl
4V
fl
TJ
U
U
C
fl
x:
c
4>
^
C
O
4V
fl
u
4)
Q-
O
^n
u
^
o
u
a
in
u
41
r*
4V
o
^
C"
c
u
fl
z.
in
^,
O
C
o
4V
U
,**
—*
O
u
£
u
fl
o
u
cu
CL
fl
4V
U
41
O
u
a
.-— I
^H
fl
u
0)
>
o !
l/l
u
o
•~4
4V
U
3
•8
u
4V
e
>^
f this Initiation Decision
o
4)
in
a
u
3
0*
1
1
e., the decision to be made)
ion submitting the Initiation
• 4V
~4 (tj
^ N
•H
U C
41 fl
a, &
fl U
a. o
i
i
u
4)
a
fl
a,
c
o
•«4
in
•^
u
4)
a
s) addressed
s^
fl
4)
U
fl
c
0
..V
4V
C"
4J
•*~ff
41
««4
J3
O
u
a
4)
£
4V
ItV
0
4)
u
3
4V
fl
2
I
1
on, flows, processing
.»4
4V
fl
E
u
O
<4V
C
.— 1
g., new legislation,
^-s .
"S *
U
.-4 41
3 in
cr 3
4) fl
u U
1
1
fe
in
4)
•H
4V
•H
^•4
•H
ja
a
fl
u
o>
c
.^4
4V
in
•H
X
4)
C —
—I 4)
U
>4 C
U 4)
C U
41 in
•-4 4>
U — •
•-i O
u-j in
oi .a
TJ O
1
*— t
o
o
w
a
01
(-•
.W
>.
J3
"8
in
3
fl
U
"8
0)
c
o
•f^
4V
fl
e
w
O
«-i
C
t— 4
1
1
B-2
-------
OSWER DIR.J9023.00
^
3
C
^^^^
^•P
C
• o
N^^^
fk^
^^^^
^^^^
^"*j
piriiM
CM
^^
^^^
^
PM
z
o
2
M
•••
a
.7
^ i
o
^••rf
H
^^
^^L
^*^
^••1
^^^^
^
P^BQ
Z
5e |
w f.§
0-
X
0)
IA ^
•^ 4)
in u
-i C
fl O
CM '•• 4 ^^
rtj 4J r-J
(B iB
TJ 4J c
^ c o
O 4) -4
£ e 4^
in
«u w C
O T3 41
in ai 0)
ii i u
3 O 3
in u a*
4) 01 4)
a ix u
i i
i i
c
o
in
in
—4
s
1
O i
O
a,
0)
u
o
u
i
4-1
in
^,
c/3
0
4-1
0)
— t
0* 4-f
C -4
T3 0)
C U
3 *— ^
a
C 4-1 X
IQ in 4)
c. o
U U « >> o
4J (J — 4
•*4 4^
X Ol (0
O) vw U
^* -«4 O
a-. -^
U u C
(TJ (TJ
(w C
O — ( «
E u
*H -- 4 0)
4) ^ ^
> 01 £
01 U 3
-3 a, z
1 1 1
1 1 1
B-3