# t_efforttypes

Notes:
The construction phase is concerned with designing and building the components necessary to implement the system as specified.


Notes:
The elaboration phase is concerned with refining the system specification, setting up project infrastructure and agreeing on the body of work to be completed.


Notes:
The Transition phase revolves around the implementation of the project and the acceptance testing carried out by the end user


# t_genopt

Option:
_AFX_NO_DEBUG_CRT;_AFX_NO_OCC_SUPPORT;_AFX_OLD_EXCEPTIONS;_AFX_PACKING;_AFXDLL;_DEBUG;_MSC_VER;_UNICODE;AFX_CDECL;AFX_COMDAT;AFX_DATA;AFX_DATADEF;AFX_NOVTABLE;AFXAPI;APICALL;BEGIN_INTERFACE_PART ^ END_INTERFACE_PART;BEGIN_PARAM_MAP ^ END_PARAM_MAP;CONTROLLER_API;DECLARE_DYNAMIC();DECLARE_DYNCREATE();DECLARE_INTERFACE_MAP();DECLARE_MESSAGE_MAP();defined();PASCAL;SWLAPI;WINAPI;


# t_metrictypes

Notes:
Measures such as function points, SLOC, scenarios, test cases.


# t_object

Note:
Note: the WorkingGroup's model had many more segment types as separate physical objects all relating to a LogicelSegment. The DDI3 imported Segment doesn't support this.


Note:
Notes:    revised 2015-09-09
Classes in blue are already in DDI4.
OrderRelations are used to define order or equality of LogicalResources, DataStores(files)  and logical or physical segments.
Physical segments in different media are related through relationship to the same LogicalSegment.


Note:
Questions:
Do we need PhysicalSegments in their own collection. How does this relate to the SegmentSet collection?
Datastore is not now a Member - should it be?


Note:
Notes: In the earlier model we had new objects AnalyticCode and AnalyticCategory inheriting from ResearchMetadata. But this didn't allow for reuse of existing Code/Category schemes. 
In this model the AnalyticMetadatum is an extra level but allows the use of any of the options.
Other suggestions are welcome.


Note:
Would VocabularyEntry be a better choice for SegmentByNomenclature than CodeValueType? Is a code more machine actionable?


# t_projectroles

Description:
Define and model the application structure


Notes:
Define and communicate application architecture


# t_requiretypes

Description:
System will display in a specified format

Notes:
Information will be displayed in a particular way


Notes:
The system must meet some performance criteria


Notes:
The system will allow the user(s) to print out some artifact as required by the specification.


Notes:
The system will have the facility to produce a report as required


Notes:
The system will validate a specific rule as supplied in the business requirements


# t_scenariotypes

Notes:
Path of execution that includes exceptional conditions.


Notes:
The standard execution path with no exceptions


# t_stereotypes

Description:
A classifier whose instances represent a flow


Description:
Source class will be notified when an event occurs in target


Description:
A worker who directly interacts with actors outside the system


Description:
Passive class accessed and manipulated by workers


Description:
A worker that interacts with other workers and entities inside the system.


Description:
An abstraction of a human that works within the system.


Description:
Contains business process objects, work units, organization units and relationships


Description:
Subsystem corresponding to an organizational unit of the actual business


Description:
Specifies an element that is at the system boundary (e.g.. User Interface)


Description:
A class that represents a client based web page


Description:
Specifies an element that controls the work and lifetimes of other objects


Description:
Specifies a persistent element mainly concerned with managing its own state


Description:
An event may be thrown or caught by operation


Description:
A class that represents a html frame set


Description:
Implementation of a class in some programming language


Description:
A collection of operations that specify a service of a class or component


Description:
A classifier whose objects are all children of a given parent


Description:
A library of subroutines/functions for web pages


Description:
A class that represents a server based web page


Description:
Specifies an asynchronous stimulus communicated amongst instances


Description:
The classifier is a stereotype that may be applied to other elements


Description:
A class that represents a database table


Description:
A classifier whose instances represent a lightweight flow of control


Description:
An abstract class specifying the structure but not implementation of a set of objects


Description:
A class whose attributes and operations are all class-scoped


Description:
A classifier whose objects are all classes


Description:
Specifies a desired feature, property or behavior of system


Description:
Specifies a contract by or an obligation of a class


Description:
Component represents a document containing source code


Description:
A component that represents a database table


Description:
Constrain must always hold for associated element


Description:
A constraint must hold after the invocation of an element


Description:
A constraint that must hold before an element is invoked


Description:
Public contents of target are accessible to namespace of source


Description:
Source instantiates target template using given parameters


Description:
Source is given special visibility of target


Description:
Public contents of target are imported into source namespace


Description:
The source object is an instance of the target


Description:
Operations on the source class create instances of the target class


Description:
Source is at a finer degree of abstraction than source


Description:
The target is an historical ancestor of source


Description:
The semantics of the source depend on the public part of the target


Description:
Child inherits implementation of parent but does not support its interfaces


Description:
A GUI element that forces user selection


Description:
A GUI element for grouping other controls


Description:
A List of Information with an expandable text field


Description:
A List of Information with a tree structure


Description:
Corresponding object is visible because of enclosing scope


Description:
The corresponding object is visible in local scope


Description:
The corresponding element is visible because it is a parameter


Description:
The corresponding object is visible because it is the dispatcher


Description:
Target is same as source but later in time


Description:
Target is exact but independent copy of source


Description:
Contains analysis classes - entities, boundaries and control elements


Description:
Contains implementation subsystems and/or components and relationships


Description:
Specifies the services offered to the users


Description:
A class that represents a personal computer


Description:
A class that represents a storage device


Description:
A Check constraint to enforce domain integrity


Description:
A trigger which executes automatically when an UPDATE, INSERT, or DELETE statement is issued


Description:
A Unique constraint to enforce the integrity of a database automatically


Description:
Package is a view of another concrete package


Description:
A semantically closed abstraction of a system


Description:
A package serves as a proxy for the public contents of another package


Description:
A grouping of elements that constitute a specification of behavior offered by other contained elements


Description:
A package representing the entire system being modeled


Description:
Communication between actor and use case


Description:
Target use case extends the source at a given extension point


Description:
Source use case explicitly includes the behavior of target


# t_tcf

Description:
Response or throughput performance objectives


Description:
Special user training faciities are required


