Tracing the distribution concern: Bridging the Gap

Nelly Bencomo, Gordon S. Blair, Peter Sawyer

Research output: Working paper

Abstract

Distribution is often presented as an example of a
crosscutting concern that is difficult to modularize.
This paper presents an approach for modeling
distribution using a combination of AOSD and use
cases. One of the aims of the paper is to bridge the gap
between the handling of crosscutting concerns during
the early and later phases of the lifecycle when
developing distributed applications. With our
approach the distribution concern is modularized in
control objects in Analysis, in design control classes in
Design and in distributed components in
Implementation and Deployment. Use cases are used
to establish a clear traceability among the analysis,
design, deployment and implementation stages. In this
sense, control objects of the analysis have a direct
correspondence with distributed components in the
implementation and deployment models.
Original languageEnglish
Publication statusPublished - Oct 2004

Bibliographical note

© 2004 The Authors

Keywords

  • cs_eprint_id
  • 984 cs_uid
  • 1

Cite this

@techreport{504159da6e0d4b37b90e81813eb6f489,
title = "Tracing the distribution concern: Bridging the Gap",
abstract = "Distribution is often presented as an example of acrosscutting concern that is difficult to modularize.This paper presents an approach for modelingdistribution using a combination of AOSD and usecases. One of the aims of the paper is to bridge the gapbetween the handling of crosscutting concerns duringthe early and later phases of the lifecycle whendeveloping distributed applications. With ourapproach the distribution concern is modularized incontrol objects in Analysis, in design control classes inDesign and in distributed components inImplementation and Deployment. Use cases are usedto establish a clear traceability among the analysis,design, deployment and implementation stages. In thissense, control objects of the analysis have a directcorrespondence with distributed components in theimplementation and deployment models.",
keywords = "cs_eprint_id, 984 cs_uid, 1",
author = "Nelly Bencomo and Blair, {Gordon S.} and Peter Sawyer",
note = "{\circledC} 2004 The Authors",
year = "2004",
month = "10",
language = "English",
type = "WorkingPaper",

}

Tracing the distribution concern: Bridging the Gap. / Bencomo, Nelly; Blair, Gordon S.; Sawyer, Peter.

2004.

Research output: Working paper

TY - UNPB

T1 - Tracing the distribution concern: Bridging the Gap

AU - Bencomo, Nelly

AU - Blair, Gordon S.

AU - Sawyer, Peter

N1 - © 2004 The Authors

PY - 2004/10

Y1 - 2004/10

N2 - Distribution is often presented as an example of acrosscutting concern that is difficult to modularize.This paper presents an approach for modelingdistribution using a combination of AOSD and usecases. One of the aims of the paper is to bridge the gapbetween the handling of crosscutting concerns duringthe early and later phases of the lifecycle whendeveloping distributed applications. With ourapproach the distribution concern is modularized incontrol objects in Analysis, in design control classes inDesign and in distributed components inImplementation and Deployment. Use cases are usedto establish a clear traceability among the analysis,design, deployment and implementation stages. In thissense, control objects of the analysis have a directcorrespondence with distributed components in theimplementation and deployment models.

AB - Distribution is often presented as an example of acrosscutting concern that is difficult to modularize.This paper presents an approach for modelingdistribution using a combination of AOSD and usecases. One of the aims of the paper is to bridge the gapbetween the handling of crosscutting concerns duringthe early and later phases of the lifecycle whendeveloping distributed applications. With ourapproach the distribution concern is modularized incontrol objects in Analysis, in design control classes inDesign and in distributed components inImplementation and Deployment. Use cases are usedto establish a clear traceability among the analysis,design, deployment and implementation stages. In thissense, control objects of the analysis have a directcorrespondence with distributed components in theimplementation and deployment models.

KW - cs_eprint_id

KW - 984 cs_uid

KW - 1

M3 - Working paper

BT - Tracing the distribution concern: Bridging the Gap

ER -