CoreLinux++
|
Goals
|
Developer's Corner
|
Contacts
|
|
MetaClass Use Case Report
MetaClass Use Case Report
Generated at: Sun, Sep 24, 2000
07:38:12
TABLE OF CONTENTS
- REPORT BODY
- Use case report
- Class report
- Data package
- Model dictionary
- SUMMARY
REPORT BODY
Use case report
- actor Implementor
- Superclasses:
- Data::Roles::Developer
- Documentation:
Implementor is a developer that uses either the corelinux or extension types into solution space applications.
- actor Developer
- Documentation:
Developer
use case Add MetaAttribute
- Documentation:
The meta-attributes are added to the meta-class.
- Extends:
Specialize MetaClass use case
use case Define metaclass
- Documentation:
Developers define meta-classes to capture type information about classes.
- Includes:
Add MetaAttribute use case
use case Specialize MetaClass
- Documentation:
Developers specialize a meta-class through meta-attributes.
Class report
- package Data
- package Data::Data types
- class byte
- class double
- class int
- class char
- class boolean
- class void
- class long
- class short
- class float
- package Data::Component View
- package Data::Roles
- package Data::Use Cases
- package Data::Use Cases::Developer Use Cases
- package Data::Abstraction
- class MetaAttribute
- Documentation:
MetaAttributes are properties of a MetaClass that codify the information about a relationship of the MetaClass to other MetaClasses.
- class Ontology
- Documentation:
An ontology is an explicit specification of some topic. It is a formal and declarative representation which includes the vocabulary for referring to terms in that subject area and the logical statements that describe what the terms are, how they are related to each other, and how they can or cannot be related to each other. Ontologies therefore provide a vocabulary (the universe of discourse) for representing and communicating knowledge about some topic and a set of relationships that hold among the terms in that vocabulary.
The representation of types and relationships in the vocabulary of the ontology is codified in a meta-classes.
- class MetaClass
- Documentation:
MetaClass captures the type and semantic information of classes. It is the codification of the class of a class.
The information that the is captured is done so in MetaAttributes.
Model dictionary
A B C D F I L M O R S U V
A
- Abstraction ModelPackage Abstraction
- Add MetaAttribute UseCase Add MetaAttribute from ModelPackage Developer Use Cases Use Cases.Developer Use Cases
B
- boolean DataType boolean from ModelPackage Data types Data types
- byte DataType byte from ModelPackage Data types Data types
C
- char DataType char from ModelPackage Data types Data types
- Component View ModelPackage Component View
D
- Data Model Data
- Data types ModelPackage Data types
- Define metaclass UseCase Define metaclass from ModelPackage Developer Use Cases Use Cases.Developer Use Cases
- Developer Actor Developer from ModelPackage Roles Roles
- Developer Use Cases ModelPackage Developer Use Cases from ModelPackage Use Cases Use Cases
- double DataType double from ModelPackage Data types Data types
F
- float DataType float from ModelPackage Data types Data types
I
- Implementor Actor Implementor from ModelPackage Roles Roles
- int DataType int from ModelPackage Data types Data types
L
- long DataType long from ModelPackage Data types Data types
M
- MetaAttribute Class MetaAttribute from ModelPackage Abstraction Abstraction
- MetaClass Class MetaClass from ModelPackage Abstraction Abstraction
O
- Ontology Class Ontology from ModelPackage Abstraction Abstraction
R
- Roles ModelPackage Roles
S
- short DataType short from ModelPackage Data types Data types
- Specialize MetaClass UseCase Specialize MetaClass from ModelPackage Developer Use Cases Use Cases.Developer Use Cases
U
- Use Cases ModelPackage Use Cases
V
- void DataType void from ModelPackage Data types Data types
SUMMARY
- Total packages reported: 7
- Total classes reported: 12
- Total use cases reported: 3
Copyright © 1999, 2000 by CoreLinux Consortium
This material may be distributed only subject to the terms and conditions set forth in the
Open Publication License
|
|
|