Proceedings. 10th IEEE International Workshop on Future Trends of Distributed Computing Systems, 2004. FTDCS 2004.
DOI: 10.1109/ftdcs.2004.1316607
|View full text |Cite
|
Sign up to set email alerts
|

Distributed systems design using function-class decomposition with aspects

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
3
0

Publication Types

Select...
3
2
1

Relationship

1
5

Authors

Journals

citations
Cited by 6 publications
(3 citation statements)
references
References 16 publications
0
3
0
Order By: Relevance
“…Hence, one important area of future work involves a service decomposition method to help developers identify necessary service elements, critical services and group redundant or crosscutting concerns. Fortunately, we have a generic software system decomposition method named Function-Class Decomposition with Aspects (FCD-A) [4]. For example, availability and reliability are critical concerns during the development of the service-oriented system to deliver fault-resilient ubiquitous services.…”
Section: Discussionmentioning
confidence: 99%
“…Hence, one important area of future work involves a service decomposition method to help developers identify necessary service elements, critical services and group redundant or crosscutting concerns. Fortunately, we have a generic software system decomposition method named Function-Class Decomposition with Aspects (FCD-A) [4]. For example, availability and reliability are critical concerns during the development of the service-oriented system to deliver fault-resilient ubiquitous services.…”
Section: Discussionmentioning
confidence: 99%
“…-capability for both analysis of errors and auditing -capability of usage statistic creation -capability of performance analysis -capability to measure quality of service metrics for Service-Level License Agreements (SLA) -capability of replaying and simulating a sequence of actions based on the log -providing enough information, if an error is logged [112] 10 -locate the logging mechanism in separate modules, do not mix it into the code of the application -the design needs to consider the logging mechanism [113] 11 -capability to identify components -capability to identify actions -capability to identify the global business flows based on the trace data -capability to identify the time of the action -usability for (1) mode of activation possibly with or without restarting the application, (2) access mode to the trace data through APIs, log files or a separate monitoring system, (3) data availability as the things happen or only after the trace session is finished [114] 12 -low performance impact on the application -multi-level severity: warning error, fatal, unhandled exception -capability to measure memory consumption and process time -capability for configuration, disable or enable tracing -capability to configure the output format: txt, db etc.…”
mentioning
confidence: 99%
“…To capture and organize various concerns appearing during the system decomposition, an extended FCD method called Function-Class decomposition with Aspects (FCD-A) [72] introduces the integrated concept of aspects and an additional decomposition view. FCD-A partitions a software system iteratively and progressively in two system-wide views: the function-class view and the aspect view.…”
Section: Petri Net Markup Language (Pnml)mentioning
confidence: 99%