Workshop Proceedings of the Sixth International Conference on Web Engineering - ICWE '06 2006
DOI: 10.1145/1149993.1150002
|View full text |Cite
|
Sign up to set email alerts
|

Formalizing and validating UML architecture description of web systems

Abstract: Web systems are self-descriptive software components which can automatically be discovered and engaged, together with other web components, to complete tasks over the Internet. Unified Modeling Language (UML), a widely accepted object-oriented system modeling and design language, and adapted for software architecture descriptions for several years, has been used for the web system description recently. However, it is hard to detect the system problems, such as correctness, consistency etc., of the integration … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
4
0

Year Published

2007
2007
2009
2009

Publication Types

Select...
6
1

Relationship

1
6

Authors

Journals

citations
Cited by 9 publications
(4 citation statements)
references
References 19 publications
0
4
0
Order By: Relevance
“…UML is another widely accepted object-oriented system modeling and design language, which has been accepted for software architecture descriptions in recent years. However, they cannot describe non-functional attributes, such as reliability, safety, etc [5] .…”
Section: Related Workmentioning
confidence: 99%
“…UML is another widely accepted object-oriented system modeling and design language, which has been accepted for software architecture descriptions in recent years. However, they cannot describe non-functional attributes, such as reliability, safety, etc [5] .…”
Section: Related Workmentioning
confidence: 99%
“…Existing researches have used UML extension to describe the web system's architecture. However, it is hard to detect the system problems, such as correctness, consistency etc., of the composition of Web services without a formal semantics of web services architecture [5]. UML models contain business elements in software model levels, e.g., objects, operations, events, which are all finer-grained semantics, and lacks of the ability to support coarse-grained semantic modeling [6,7].…”
Section: Introductionmentioning
confidence: 99%
“…Architecture describes the components to be assembled and the acceptable patterns of composition, and supports dynamic evolution as required for agility. The architecture-based modeling approach is a good approach to support tackling the inherent complexity of the eEnterprise [10,11] . In this paper, the term 'semantic' not only denotes the semantic specification of the business component and service component for automated discovery of partners and services but also denotes the semantic definition of component relationships for automated verification of component relationships.…”
Section: Introductionmentioning
confidence: 99%