Service

A Service in QualiWare typically represents a Service in the context of Service Oriented Architecture (SOA) and therefore common and reusable services that will be used in the context of Information Systems that support the processes of the business. The Service template can also be used to define Business Services; i.e., in the context of services the business either offers to its customers or clients or wishes to offer them.

On the object editor window the following properties for Service can be entered:
· Short Description – brief description of the service and its purpose.
· Operations – a listview where the user can link to Operations (i.e., The specification of a service that may be requested from objects) that are or will be used to support the Service.
· Handles Data – a listview where the user can link to multiple data related templates to show what data is handled by or required by the Service.
· On the Capability tab – the QualiWare user can link to the Capability template via the Deliver Capability listview; thus showing what Capabilities currently are or will be provided via the Service, and the Executed by Activity listview provides the ability to link the Service to one or more Activities as they may be part of one or more business processes; thus showing the linkage between Services and Business Processes.

On the Information tab – the QualiWare user can link to data related templates via the Uses Information listview and specify by clicking in the Create, Read, Update, Delete, or Source columns of the listview what action is being taken by the Service on the data item in the listview. The QualiWare user can also link to UserInterfaces that are used or will be used in the delivery or execution of the Service.

Serving : ArchiMate

The serving relationship describes how the services or interfaces offered by a behavior or active structure element serve entities in their environment. This relationship is applied for both the behavior aspect and the active structure aspect.

Compared to the earlier versions of this standard, the name of this relationship has been changed from ‘used by’ to ‘serving’, to better reflect its direction with an active verb: a service serves a user. The meaning of the relationship has not been altered. The ‘used by’ designation is still allowed but deprecated, and will be removed in a future version of the standard.

The usual interpretation of a serving relationship is that the whole of the source element serves (is used by) the target element. This means that if, for example, two services serve the same internal behavior element, both of these services are needed. If two services are alternative solutions and only one of them is needed by the internal behavior element, an or junction can be used.

Signal

Indicates that a signal is either sent or expected depending on the specification.

Software

Software is a computer program. Software can either be bound directly to a Computer or through a Software License. Using software licenses enables you to keep track of multiple licenses for each piece of software.

Software Configuration

A software configuration is way of defining standard packages of multiple programs. A configuration can contain Software objects or Software License objects which enables you to keep track of your licenses. It is also possible to make trees of configurations making administration even easier.

Software License

A software license is used to control your licenses. The license is either bound to a Computer or a Software Configuration.
Through the license you can get an overview on which computers your licenses are installed.

Specialization ArchiMate

The specialization relationship has been inspired by the generalization relationship in UML class diagrams, but is applicable to specialize a wider range of concepts. The specialization relationship can relate any instance of a concept with another instance of the same concept.
A specialization relationship is always allowed between two instances of the same element.
Alternatively, a specialization relationship can be expressed by nesting the specialized element inside the generic element.

Specialization Aspect

A selection of a property that determines which subclass a concept instance of the super class shall belong to. If it is exhaustive an instance of the superclass must always belong to at least one subclass. If it is overlapping an instance may belong to more than one subclass at a time.

State

A specific state that the object can be in.

State Transition

The state transition is the active agent on a State Event Diagram . It describes a change in state and the associated actions taken at the transition. It also describes the conditions or actions triggering the transition.