Managing Evolution in Telecommunication Systems

Koutsoukos, Georgios; Gouveia, João; Andrade, Luis Filipe; Fiadeiro, José Luiz

doi:10.1007/0-306-47005-5_12

Cited by 12 publications

(9 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A more detailed discussion on how contracts can support evolution, as well as a number of examples from different application domains such as banking, telecommunications, and stock-trading, can be found in [1,10,11]. In the following section we present a development environment that puts contracts in practice.…”

Section: W I T H D R a W A L ( Z ) End C O N T R A C Tmentioning

confidence: 99%

“…As a result, it is not surprising that, as shown by numerous scientific studies on large-scale software systems, more than 80% of the total cost of software development is still devoted to maintenance. In this paper, based on experience gathered in several application domains [10,11] and a solid mathematical semantics [2], we show how the "coordination contract" modeling primitive presented in [3] can promote the flexibility offered by certain design patterns to the business modeling level, and serve as a basis for a software development discipline that can lead to information systems that are adaptive to change.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Support for business-driven evolution with coordination technologies

Andrade

Fiadeiro

Gouveia

et al. 2002

Proceedings of the 4th International Workshop on Principles of Software Evolution - IWPSE '01

Self Cite

View full text Add to dashboard Cite

Software evolution is, ever more, a critical concern for most business organizations. In spite of many promises, software development techniques, such as Object-Oriented ones, have fallen short of addressing this problem. We show how new technologies based on the notion of "coordination contract" can be deployed for managing the levels of change imposed by the evolution of requirements and technological environments, both in terms of semantic modeling and tool support.

show abstract

Section: W I T H D R a W A L ( Z ) End C O N T R A C Tmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Support for business-driven evolution with coordination technologies

Andrade

Fiadeiro

Gouveia

et al. 2002

Proceedings of the 4th International Workshop on Principles of Software Evolution - IWPSE '01

Self Cite

View full text Add to dashboard Cite

show abstract

“…In business modelling, coordination laws can be used to model the rules according to which organisations make available to the market the services that their core entities provide [16,17]. In control systems, they can be used to model the mechanisms that need to be superposed over the components of the target plant to monitor their behaviour, adapt them to new modes of operation, or interconnect them to ensure required emergent behaviour [4].…”

Section: Figure 3: Enriched Problem Frame Diagrammentioning

confidence: 99%

Problem Frames: A Case for Coordination

Barroca

Fiadeiro

Jackson

et al. 2004

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

show abstract

“…">MOTIVATIONThe engineering of Business Systems is under the increasing pressure to come up with software solutions that allow companies to face very volatile and turbulent environments (as in the telecommunications domain [3]). This means that the complexity of software has definitely shifted from construction to evolution, and that new methods and technologies are required.…”

mentioning

confidence: 99%

A coordination methodology and technology for agile businesses

Andrade¹,

Fiadeiro²,

Gouveia³

et al. 2002

Companion of the 17th Annual ACM SIGPLAN Conference on Object-Oriented Programming, Systems, Languages, and Applications

View full text Add to dashboard Cite

MOTIVATIONThe engineering of Business Systems is under the increasing pressure to come up with software solutions that allow companies to face very volatile and turbulent environments (as in the telecommunications domain [3]). This means that the complexity of software has definitely shifted from construction to evolution, and that new methods and technologies are required.Most often, the nature of changes that occur in the business are not at the level of the components that model business entities, but at the level of the business rules that regulate the interactions between the entities. Therefore, we believe that sucessful methodologies and technologies will have to provide abstractions that reflect the architecture of such systems by supporting a clear separation between computation, as performed by the core business components, and coordination, as prescribed by business rules. This separation should help in localising change in the system, both in terms of identifying what needs to be changed in the system and circumscribing the effects of those changes.In our opinion, the lack of abstractions for supporting the modelling of interactions and architectures explains why componentbased and object-oriented approaches have not been able to deliver their full promise regarding system evolution. Usually, interactions are coded in the way messages are passed, features are called, and objects are composed, leading to intricate spaghetti-like structures that are difficult to understand, let alone change. Moreover, new behaviour is often introduced through new subclasses which do not derive from the "logic" of the business domain, widening the gap between specification and design.The approach we have been developing [1] builds on previous work on coordination models and languages, software architecture, and parallel program design languages. Instead of delegation we use explicit architectural connectors that encapsulate coordination aspects: this makes a clear separation between computations and interactions and externalises the architecture of the system. Instead of subclassing we advocate superposition as a structuring principle:Copyright is held by the author/owner. OOPSLA'02, November 4-8, 2002, Seattle, Washington, USA. ACM 1-58113-626-9/02/0011.interactions are superposed on components in a non-intrusive and incremental way, allowing evolution through reconfiguration, even at run-time.The main advantages of our approach are adequacy and flexibility. The former is achieved by having a strict separation of computation, coordination, and configuration, with one primitive for each concept, stating clearly the pre-conditions for each coordination and reconfiguration rule. As for flexibility, interactions among components can be easily altered at run-time through (un)plugging of coordination rules, and it is possible to state exactly which coordination rules are in effect for which components, and which configuration policies apply to which parts of the system.In the following sections we briefly summafise our approa...

show abstract

Managing Evolution in Telecommunication Systems

Cited by 12 publications

References 3 publications

Support for business-driven evolution with coordination technologies

Support for business-driven evolution with coordination technologies

Problem Frames: A Case for Coordination

A coordination methodology and technology for agile businesses

Contact Info

Product

Resources

About