next up previous NU-CCS-99-04.ps [ Readme | Copyright | Tutorial | Download | Feedback ]


Next: Visuality, Symbolism of Components, Up: Understanding the Assembly-Design Space Previous: Understanding the Assembly-Design Space

Lifetimes of a Component

Components change form and appearance during their normal development and lifetime. We identify four lifetimes: (1) compile time --the embryonic stage of the component; (2) and (3) assembly time and design time --two metamorphoses periods sometimes referred to as one--building-time ; (4) runtime --component maturity.

The definitions of the first and last lifetimes are standard [3]:

Compile time:
the time when the component's source code is compiled into byte code and ``forgotten" thereafter. Typically done by third party component providers. That is, a component may originate from a different author in binary format and without its source code.
Runtime:
the time the application, which is built out of components, is executed.

The explicit distinction between assembly and design time is non-traditional, but one of importance, because often the fine line between the two environments is somewhat blurred.

Assembly time:
the time when the application (or component) is assembled from other (compiled) components. The timeframe between the compilation of the components and the compilation (or serialization) of the application.
Design time:
the time when the components' visual aspects are displayed, thus permitting a user-friendly mechanism for fine-tuning the application's look, feel, and behavior. You can also test the application at this time.


next up previous NU-CCS-99-04.ps [ Readme | Copyright | Tutorial | Download | Feedback ]


Next: Visuality, Symbolism of Components, Up: Understanding the Assembly-Design Space Previous: Understanding the Assembly-Design Space

David H. Lorenz
3/17/2000