A technology service exposes the functionality of a node to its environment. This functionality is accessed through one or more technology interfaces. It may require, use, and produce artifacts.
A technology service should be meaningful from the point of view of the environment; it should provide a unit of behavior that is, in itself, useful to its users, such as application components and nodes.
Typical technology services may, for example, include messaging, storage, naming, and directory services. It may access artifacts; e.g., a file containing a message.
A technology service may serve application components or nodes. A technology service is realized by a technology function or process. A technology service is exposed by a node by assigning technology interfaces to it. A technology service may access artifacts. A technology service may consist of sub-services.
The name of a technology service should preferably be a verb ending with “ing”; e.g., “messaging”. Also, a name explicitly containing the word “service” may be used.
Archives: Templates
Templates and model types in the QualiWare platform.
Term
The denomination of a concept used by a party such as a person, a role or an organization unit.
Test Case
A specification of some test scenario that tests a specified aspect of an item.
Test Design
A refinement of a test requirement.
Test Requirement
A component that holds summary information about what to a subsystem for.
Text Annotation
The Text Annotation template in QualiWare permits the user to add an object where any amount of text can be included on the diagram to support what is going on with one Activity, or other BPMN based template. The Text field on the Text Annotation tab in the Object Editor is where the text is entered and upon saving and closing the object editor, the text will appear on the diagram within the Text Annotation object. The Text Annotation is then linked to the applicable Activity or other object using the Association symbol/connector.
Association
A relationship between two classes.
In the Unified Modeling Language (UML), there are five different types of relationships: association, aggregation, composition, dependency, and inheritance.
Association is a semantically weak relationship (a semantic dependency) between otherwise unrelated objects. An association is a ‘using’ relationship between two or more objects in which the objects have their own lifetime and there is no owner.
As an example, imagine the relationship between a doctor and a patient. A doctor can be associated with multiple patients. At the same time, one patient can visit multiple doctors for treatment or consultation. Each of these objects has its own life cycle and there is no ‘owner’ or parent. The objects that are part of the association relationship can be created and destroyed independently.
In UML an association relationship can be represented as one-to-one, one-to-many, or many-to-many (also known as cardinality).
Appraisal Interview
Human relations interview are used data and results concerning an interview between a supervisor and a subordinate. Basically there are two types of interviews: Appraisal interview and Exit interview