• Example Architectures

Health Care Architecture

This documentation follows the Rational Unified Process (RUP) recommendation for architetcure documentation. It includes:

Use-Case View: Describes the actors and use cases for the system, this view presents the needs of the user and

is elaborated further at the design level to describe discrete flows and constraints in more detail. This domain

vocabulary is independent of any processing model or representational syntax (i.e. XML).

• Domain Vocabulary View: Describes the key abstractions that make up the domain of discourse. For example

the notions of “Member” or “Scientific Journal” are included in the MedBiquitous domain whereas “Engine”,

“Body”, “Number of Wheels” are not (though may be included in a truck manufacturing domain).

• Service View: Describes the high-level components that make up the dynamic aspects of the system. A

fundamental constraint of this architecture is that it follows a Service-Oriented architectural style as opposed to

a distributed object broker style for example.

• Portal View: Describes the behavior of the portal infrastructure in aggregating information and presenting it to

the user. Key mechanisms, such as information acquisition, query, aggregation, syndication etc. are described

here. As far as the user is concerned this is the primary client interface into the MedBiquitous information

infrastructure.

• Deployment View: Describes potential deployment structures, by including known and anticipated deployment

scenarios in the architecture we allow the implementers to make certain assumptions on network performance,

system interaction and so forth.