692 research outputs found
Aligning a Service Provisioning Model of a Service-Oriented System with the ITIL v.3 Life Cycle
Bringing together the ICT and the business layer of a service-oriented system
(SoS) remains a great challenge. Few papers tackle the management of SoS from
the business and organizational point of view. One solution is to use the
well-known ITIL v.3 framework. The latter enables to transform the organization
into a service-oriented organizational which focuses on the value provided to
the service customers. In this paper, we align the steps of the service
provisioning model with the ITIL v.3 processes. The alignment proposed should
help organizations and IT teams to integrate their ICT layer, represented by
the SoS, and their business layer, represented by ITIL v.3. One main advantage
of this combined use of ITIL and a SoS is the full service orientation of the
company.Comment: This document is the technical work of a conference paper submitted
to the International Conference on Exploring Service Science 1.5 (IESS 2015
Aligning an ISO/EIC 42010 System Architecture Model and Agile Practice
The ISO/EIC 42010 system architecture description standard evolved over a number of years with substantial practitioner inputs. It presents a high level, top-down view of requirements that may be interpreted as needed for different applications. Agile system development methods have proved effective in practice, but represent a bottom up view drawing on user stories. The question considered in this paper is how they might be harmonised. Experience from using these tools over several years in practical masters degree student projects has been used to explore this question. We suggest a logical compatibility lies in their core themes: stakeholder needs (who) frame architecture descriptions (what) and the associated rationale (why). A particular interpretation of ISO/EIC 42010 and a model outlining the evolution of architecture in an agile environment are presented. Several suggestions for future research are made
Reference Architecture for e-Learning Solutions
In deze scriptie worden de volgende drie modellen en raamwerken voor e-Learning
besproken: het e-Learning raamwerk ontwikkeld voor de UKeU, het model voor Web-based
Instructional Systems ontwikkeld door Retalis en Avgeriou en het LTSA ontwikkeld door
het IEEE. Deze drie modellen vormen de theoretische basis voor een Managed Learning
Environment die als domeinmodel dienen voor e-Learning oplossingen
Requirement Specification Stage of the Project Lifecycle of Computerized Systems & the Standards that Can Be Implemented
Understanding requirement specifications was an integral part of information systems design and was critical to the success of interactive systems. However, specifying these requirements was not simple to achieve. This research, including a literature review, describes general methods to support requirement specification analysis that can be adapted into a range of situations in accordance with relevant standards. The main techniques discussed were risk management, stage-based lifecycle models and frameworks. Additionally, as part of the methodology and project history, the methods for implementation, process improvements and schedule of the research was examined. A case study with statistical analysis was described to illustrate how these techniques, methods and standards have been applied in practice and the advantages and disadvantages experienced
Approach for Highly Dependable Software-Intensive Systems
Author-contributed print itemhe objectives of the proposal are creating new methods and tools for effective constructing software-intensive systems based on multiple perspectives that are used to reflect differing stakeholder's concerns. The models and methods will incorporate rapid prototyping, explicit architecting and consistent engineering techniques into a synthesis approach for highly dependable software-intensive systems (HDSIS)
Feature-based methodology for supporting architecture refactoring and maintenance of long-life software systems
Zusammenfassung
Langlebige Software-Systeme durchlaufen viele bedeutende Veraenderungen im Laufe ihres Lebenszyklus,
um der Weiterentwicklung der Problemdomaenen zu folgen. Normalerweise ist es schwierig eine
Software-Systemarchitektur den schnellen Weiterentwicklungen einer Problemdomaene anzupassen und
mit der Zeit wird der Unterschied zwischen der Problemdomaene und der Software-Systemarchitektur
zu groĂź, um weitere Softwareentwicklung sinnvoll fortzufuehren. Fristgerechte Refactorings der Systemarchitektur
sind notwendig, um dieses Problem zu vermeiden.
Aufgrund des verhaeltnismaeĂźig hohen Gefahrenpotenzials und des zeitlich stark verzoegerten Nutzens
von Refactorings, werden diese MaĂźnahmen normalerweise bis zum letztmoeglichen Zeitpunkt hinausgeschoben.
In der Regel ist das Management abgeneigt Architektur-Refactorings zu akzeptieren,
auĂźer diese sind absolut notwendig. Die bevorzugte Vorgehensweise ist, neue Systemmerkmale ad hoc
hinzuzufuegen und nach dem Motto ”Aendere nie etwas an einem funktionierenden System!” vorzugehen.
Letztlich ist das Ergebnis ein Architekturzerfall (Architekturdrift). Die Notwendigkeit kleiner
Refactoring-Schritte fuehrt zur Notwendigkeit des Architektur-Reengineerings. Im Gegensatz zum
Refactoring, das eine normale Entwicklungstaetigkeit darstellt, ist Reengineering eine Form der Software-
”Revolution”. Reengineeringprojekte sind sehr riskant und kostspielig. Der Nutzen des Reengineerings
ist normalerweise nicht so hoch wie erwartet. Wenn nach dem Reengineering schlieĂźlich die erforderlichen
Architekturaenderungen statt.nden, kann dies zu spaet sein. Trotz der enormen in das Projekt
gesteckten Bemuehungen erfuellen die Resultate des Reengineerings normalerweise nicht die Erwartungen.
Es kann passieren, dass sehr bald ein neues, kostspieliges Reengineering erforderlich wird.
In dieser Arbeit werden das Problem der Softwareevolution und der Zerfall von Softwarearchitekturen
behandelt. Eine Methode wird vorgestellt, welche die Softwareentwicklung in ihrer entscheidenden
Phase, dem Architekturrefactoring, unterstuetzt. Die Softwareentwicklung wird sowohl in technischer
als auch organisatorischer Hinsicht unterstuetzt. Diese Arbeit hat neue Techniken entwickelt,
welche die Reverse-Engineering-, Architecture-Recovery- und Architecture-Redesign-Taetigkeiten unterst
uetzen. Sie schlaegt auch Aenderungen des Softwareentwicklungsprozesses vor, die fristgerechte Architekturrefactorings
erzwingen koennen und damit die Notwendigkeit der Durchfuehrung eines Architektur-
Reengineerings vermeiden.
In dieser Arbeit wird die Merkmalmodellierung als Hauptinstrument verwendet. Merkmale werden
genutzt, um die Abstraktionsluecke zwischen den Anforderungen der Problemdomaene und der Systemarchitektur
zu fuellen. Merkmalmodelle werden auch als erster Grundriss fr die Wiederherstellung
der verlorenen Systemarchitektur genutzt. Merkmalbasierte Analysen fuehren zu diversen, nuetzlichen
Hinweisen fuer den erneuten Entwurf (das Re-Design) einer Architektur. SchlieĂźlich wird die Merkmalmodellierung
als Kommunikationsmittel zwischen unterschiedlichen Projektbeteiligten (Stakeholdern)
im Verlauf des Softwareengineering-Prozesses verwendet und auf dieser Grundlage wird ein neuer
Anforderungsde.nitionsprozess vorgeschlagen, der die erforderlichen Architekturrefactorings erzwingt.The long-life software systems withstand many significant changes throughout their life-cycle in order
to follow the evolution of the problem domains. Usually, the software system architecture can not
follow the rapid evolution of a problem domain and with time, the diversion of the architecture in
respect to the domain features becomes prohibiting for software evolution. For avoiding this problem,
periodical refactorings of the system architecture are required.
Usually, architecture refactorings are postponed until the very last moment, because of the relatively
high risk involved and the lack of short-term profit. As a rule, the management is unwilling to accept
architecture refactorings unless they become absolutely necessary. The preferred way of working is to
add new system features in an ad-hoc manner and to keep the rule ”Never touch a running system!”.
The final result is an architecture decay. The need of performing small refactoring activities turns into
need for architecture reengineering. In contrast to refactoring, which is a normal evolutionary activity,
reengineering is a kind of software ”revolution”. Reengineering projects are risky and expensive. The
effectiveness of reengineering is also usually not as high as expected. When finally after reengineering
the required architecture changes take place, it can be too late. Despite the enormous invested efforts,
the results of the reengineering usually do not satisfy the expectations. It might happen that very
soon a new expensive reengineering is required.
This thesis deals with the problem of software evolution and the decay of software architectures.
It presents a method, which assists software evolution in its crucial part, the architecture refactoring.
The assistance is performed for both technical and organizational aspects of the software evolution.
The thesis provides new techniques for supporting reverse engineering, architecture recovery and redesigning
activities. It also proposes changes to the software engineering process, which can force
timely architecture refactorings and thus avoid the need of performing architecture reengineering.
For the work in this thesis feature modeling is utilized as a main asset. Features are used to fill the
abstraction gap between domain requirements and system architecture. Feature models are also used
as an outline for recovering of lost system architectures. Through feature-based analyses a number of
useful hints and clues for architecture redesign are produced. Finally, feature modeling is used as a
communication between different stakeholders of the software engineering process and on this basis a
new requirements engineering process is proposed, which forces the needed architecture refactorings
Personalized architectural documentation based on stakeholders' information needs
The stakeholders of a software system are, to a greater or lesser extent, concerned about its software architecture, as an essential artifact for capturing the key design decisions of the system. The architecture is normally documented in the Software Architecture Document (SAD), which tends to be a large and complex technical description, and does not always address the information needs of every stakeholder. Individual stakeholders are interested in dierent, sometimes overlapping, subsets of the SAD and they also require varying levels of detail. As a consequence, stakeholders are aected by an information overload problem, which in practice discourages the usage of the architectural knowledge and diminishes its value for the organization. Along this line, this work presents a semi-automated approach to recommend relevant contents of a given SAD to specific stakeholder profiles. Our approach assumes that SADs are hosted in Wikis, which not only favor communication and interactions among stakeholders, but also enable us to apply User Profiling techniques to infer stakeholders´ interests with respect to particular documents. We have built a recommendation tool implementing our approach, which was tested in two experiments with Wiki-based SADs. Although preliminary, the results have shown that the recommendations of the tool help to nd the architectural documents that best match the stakeholders´ interests.Fil: Tommasel, Antonela. Consejo Nacional de Investigaciones CientĂficas y TĂ©cnicas. Centro CientĂfico TecnolĂłgico Tandil. Instituto Superior de Ingenieria del Software; ArgentinaFil: Nicoletti, MatĂas Alberto. Consejo Nacional de Investigaciones CientĂficas y TĂ©cnicas. Centro CientĂfico TecnolĂłgico Tandil. Instituto Superior de Ingenieria del Software; ArgentinaFil: Diaz Pace, Jorge Andres. Consejo Nacional de Investigaciones CientĂficas y TĂ©cnicas. Centro CientĂfico TecnolĂłgico Tandil. Instituto Superior de Ingenieria del Software; ArgentinaFil: Schiaffino, Silvia Noemi. Consejo Nacional de Investigaciones CientĂficas y TĂ©cnicas. Centro CientĂfico TecnolĂłgico Tandil. Instituto Superior de Ingenieria del Software; ArgentinaFil: Godoy, Daniela Lis. Consejo Nacional de Investigaciones CientĂficas y TĂ©cnicas. Centro CientĂfico TecnolĂłgico Tandil. Instituto Superior de Ingenieria del Software; Argentin
Model-driven engineering of software architecture viewpoints
Ankara : The Department of Computer Engineering and the Graduate School of Engineering and Science of Bilkent University, 2012.Thesis (Master's) -- Bilkent University, 2012.Includes bibliographical references.A common practice in software architecture design is to apply so-called
architectural views to design software architecture for the various stakeholder
concerns. Architectural views are usually developed based on architectural
viewpoints which define the conventions for constructing, interpreting and
analyzing views. So far most architectural viewpoints seem to have been primarily
used either to support the communication among stakeholders, or at the best to
provide a blueprint for the detailed design.
In this thesis, we provide a software language engineering approach to define
viewpoints as domain specific languages. This enhances the formal precision of
architectural viewpoints and leads to executable views that can be interpreted and
analyzed by tools. We illustrate our approach for defining domain specific
languages for the viewpoints of the Views and Beyond framework. The approach
is implemented as an Eclipse plug-in, SAVE-Bench tool, which can be used to
define different views based on the predefined software architecture viewpoints.
The tool also supports automatic generation of architecture documentation from
view models.Demirli, ElifM.S
- …