Application Architecture Design Sample Clauses

Application Architecture Design. The Application Architecture Design phase is concerned with the design of the applications from both functional and non-functional points of view. Moreover, in order to enable composition, the services provided by the different eDIANA devices have to be defined, not only at syntactical level, but also at behavioural and semantic levels. The goal of the Application Architecture Design phase is to produce a platform independent model of an eDIANA device or application. The phase produces the following views: Structural view. The structural view contains the definition of DAS (i.e. interaction between jobs), the jobs, LIFs and messages that take part in the application under design. Syntactical view. The syntactical view contains the description of the protocols that manage the access to a certain service. (The interface description is partly defined by the structural view and the syntactical view). Behavioural view. The behavioural view defines the behaviour of the application at two levels: as behaviour of the application and as behaviour of the jobs involved in the application. Semantic view. The semantic view provides information regarding the semantics of the application service. The semantic view is related to a service ontology that will be an enabler for service composition engines. Again, these views can be provided by different languages; however, they must be integrable with the UML+▇▇▇▇▇ modelling approach. It is possible that many diagrams are included in a single view. It is also possible to describe two or more views in the same diagram but it is against the separation of concerns, one of the architecture design laws and breaching that law will lead to serious problems in architecture evolution. In order to provide developers with models that are expressive enough, it is important to present the structures of the services and jobs in application architecture. The next sub-sections will cover the modelling of each of these views using UML2 and the ▇▇▇▇▇ profile. ▇▇▇▇▇ is a UML2 profile and, therefore, it cannot be used without it. It is important to note that UML provides several ways to describe the same aspects of the system models. This fact makes it difficult to provide a unique method to create the models as many different diagrams can be used to specify the same aspects in the models. For example, in many cases state machines and activity diagrams can address the same behaviour. Therefore these sections provide a best practices guide for u...