A classifier is a category of Unified Modeling Language (UML) elements that have some

common features, such as attributes or methods.

A classifier is an abstract metaclass classification concept that serves as a mechanism to

show interfaces, classes, datatypes and components.

A classifier describes a set of instances that have common behavioral and structural
features (operations and attributes, respectively).

A classifier is a namespace whose members can specify a generalization hierarchy by

referencing its general classifiers.

A classifier is a type and can own generalizations, thereby making it possible to define
generalization relationships to other classifiers.

A classifier is a redefinable element, as it is possible to redefine nested classifiers.

All objects that can have instances are classifiers.

XML:

Extensible Markup Language (XML) is a set of rules for encoding documents in

machine-readable form. It is defined in the XML 1.0 Specification[4] produced by the
W3C, and several other related specifications, all gratis open standards.[5]

XML's design goals emphasize simplicity, generality, and usability over the Internet.[6] It
is a textual data format with strong support via Unicode for the languages of the world.
Although the design of XML focuses on documents, it is widely used for the
representation of arbitrary data structures, for example in web services.

Many application programming interfaces (APIs) have been developed that software
developers use to process XML data, and several schema systems exist to aid in the
definition of XML-based languages.

As of 2009, hundreds of XML-based languages have been developed,[7] including RSS,

Atom, SOAP, and XHTML. XML-based formats have become the default for most
office-productivity tools, including Microsoft Office (Office Open XML),
OpenOffice.org (OpenDocument), and Apple's iWork.[8]

XMI:
The XML Metadata Interchange (XMI) is an Object Management Group (OMG)
standard for exchanging metadata information via Extensible Markup Language (XML).

It can be used for any metadata whose metamodel can be expressed in Meta-Object
Facility (MOF).

The most common use of XMI is as an interchange format for UML models, although it
can also be used for serialization of models of other languages (metamodels).

COMPOSITE STRUCTURE DIAGRAM:

Composite structure diagram in the Unified Modeling Language (UML) is a type of

static structure diagram, that shows the internal structure of a class and the
collaborations that this structure makes possible.

This diagram can include internal parts, ports through which the parts interact with each
other or through which instances of the class interact with the parts and with the outside
world, and connectors between parts or ports. A composite structure is a set of
interconnected elements that collaborate at runtime to achieve some purpose. Each
element has some defined role in the collaboration.

Composite structure concepts

The key composite structure entities identified in the UML 2.0 specification are
structured classifiers, parts, ports, connectors, and collaborations[1].

• Part : A part represents a role played at runtime by one instance of a class or by a

collection of instances. The part may only name the role, it may name an abstract
superclass, or it may name a specific concrete class. The part can include a
multiplicity factor, such as the [0..*] shown for Viewer in the diagram.

• Port : A port is an interaction point that can be used to connect structured

classifiers with their parts and with the environment. Ports can optionally specify
the services they provide and the services they require from other parts of the
system. In the diagram, each of the small squares is a port. Each port has a type
and is labelled with a name, such as "var", "indVar1", or "view" in the diagram.
Ports may contain a multiplicity factor, for example [3].

Ports can either delegate received requests to internal parts, or they can deliver
these directly to the behavior of the structured classifier that the port is contained
within. Public ports that are visible in the environment are shown straddling the
boundary, while protected ports that are not visible in the environment are shown
inside the boundary. All the ports in the diagram are public, except for the view
port along the right boundary of FibonacciSystem.
 • Connector : A connector binds two or more entities together, allowing them to
interact at runtime. The connector is shown as a line between some combination
of parts, ports and structured classifiers. The diagram shows three connectors
between ports, and one connector between a structured classifier and a part.

• Collaboration : A collaboration is generally more abstract than a structured

classifier. It is shown as a dotted oval containing roles that instances can play in
the collaboration.

• Structured classifier : A StructuredClassifier represents a class, often an abstract

class, whose behavior can be completely or partially described through
interactions between parts.

An EncapsulatedClassifier is a type of structured classifier that contains ports. In

the diagram above, both FibonacciSystem and Variable are encapsulated
classifiers because they both have ports along their boundaries.

EMBEDDED APPLICATION :

An embedded system is a computer system designed to perform one or a few dedicated

functions[1][2] often with real-time computing constraints. In computer science, real-time
computing (RTC), or reactive computing, is the study of hardware and software
systems that are subject to a "real-time constraint"—i.e., operational deadlines from event
to system response. Real-time programs must execute within strict constraints on
response time.

It is embedded as part of a complete device often including hardware and mechanical

parts. By contrast, a general-purpose computer, such as a personal computer (PC), is
designed to be flexible and to meet a wide range of end-user needs. Embedded systems
control many devices in common use today.[3]

Embedded systems are controlled by one or more main processing cores that are typically
either microcontrollers or digital signal processors (DSP).[4] The key characteristic,
however, is being dedicated to handle a particular task, which may require very powerful
processors. For example, air traffic control systems may usefully be viewed as embedded,
even though they involve mainframe computers and dedicated regional and national
networks between airports and radar sites (each radar probably includes one or more
embedded systems of its own).