Preferencje help
Widoczny [Schowaj] Abstrakt
Liczba wyników
Powiadomienia systemowe
  • Sesja wygasła!

Znaleziono wyników: 2

Liczba wyników na stronie
first rewind previous Strona / 1 next fast forward last
Wyniki wyszukiwania
help Sortuj według:

help Ogranicz wyniki do:
first rewind previous Strona / 1 next fast forward last
EN
There exist numerous models of software architecture (box models, ADL’s, UML, architectural decisions), architecture modelling frameworks (views, enterprise architecture frameworks) and even standards recommending practice for the architectural description. We show in this paper, that there is still a gap between these rather abstract frameworks/standards and existing architecture models. Frameworks and standards define what should be modelled rather than which models should be used and how these models are related to each other. We intend to prove that a less abstract modelling framework is needed for the effective modelling of large scale software intensive systems. It should provide a more precise guidance kinds of models to be employed and how they should relate to each other. The paper defines principles that can serve as base for an integrated model. Finally, structure of such a model has been proposed. It comprises three layers: the upper one – architectural policy – reflects corporate policy and strategies in architectural terms, the middle one –system organisation pattern – represents the core structural concepts and their rationale at a given level of scope, the lower one contains detailed architecture models. Architectural decisions play an important role here: they model the core architectural concepts explaining detailed models as well as organise the entire integrated model and the relations between its submodels.
2
Content available An evolution process for service-oriented systems
EN
Evolution of service-oriented systems is quite a new research area, which becomes more and more important as engineering challenges move from enabling service-orientation onto the maintenance and evolution of already developed service-oriented systems. However, the development of suitable evolution processes and methodologies is still an open research problem. The evolution process presented in this paper has been designed to address the evolution of service-oriented systems, which are technically built out of a set of service compositions. The presented process comprises phases and tasks compliant with ISO 20000. The underlying model of service-oriented system consisting of business processes and corresponding service composition models has also been presented. A traceability model and tools supporting change impact analysis have also been provisioned for. Preliminary industrial validation indicates that the evolution process should be easy to adapt by the industry.
first rewind previous Strona / 1 next fast forward last
JavaScript jest wyłączony w Twojej przeglądarce internetowej. Włącz go, a następnie odśwież stronę, aby móc w pełni z niej korzystać.