1,822 research outputs found
Ontology-based patterns for the integration of business processes and enterprise application architectures
Increasingly, enterprises are using Service-Oriented Architecture (SOA) as an approach to Enterprise Application Integration (EAI). SOA has the potential to bridge
the gap between business and technology and to improve the reuse of existing applications and the interoperability with new ones. In addition to service architecture
descriptions, architecture abstractions like patterns and styles capture design knowledge and allow the reuse of successfully applied designs, thus improving the quality of
software. Knowledge gained from integration projects can be captured to build a repository of semantically enriched, experience-based solutions. Business patterns identify the interaction and structure between users, business processes, and data.
Specific integration and composition patterns at a more technical level address enterprise application integration and capture reliable architecture solutions. We use an
ontology-based approach to capture architecture and process patterns. Ontology techniques for pattern definition, extension and composition are developed and their
applicability in business process-driven application integration is demonstrated
(SAKM) Software Architecture Knowledge Management and its recent Practices, Models, Tools and Challenges
Management of knowledge for software architecture means to capture convenient experience and then translating it in generalized architectural knowledge. For refining the organizational architectural competences, architectural knowledge management is very much important. Architectural knowledge is valuable in the Software Architecture design process. This knowledge will help the stakeholders for communication in different phases of software development life cycle(SDLC). Properly managing the architectural knowledge is very much important as it is progressively more regarded the same as an organizational positive feature and that is why so many researchers around the world are proposing tools, methods, models and different frameworks for the effective knowledgemanagement [1]. This article contributes in exploring current work in field of software architectural knowledge management (AKM) from 2010 to 2017. This article highlights recent architectural AKM challenges and issues which are still not settled and here we also discuss different AKM tools, practicesand models
Comprehensive measurement framework for enterprise architectures
Enterprise Architecture defines the overall form and function of systems
across an enterprise involving the stakeholders and providing a framework,
standards and guidelines for project-specific architectures. Project-specific
Architecture defines the form and function of the systems in a project or
program, within the context of the enterprise as a whole with broad scope and
business alignments. Application-specific Architecture defines the form and
function of the applications that will be developed to realize functionality of
the system with narrow scope and technical alignments. Because of the magnitude
and complexity of any enterprise integration project, a major engineering and
operations planning effort must be accomplished prior to any actual integration
work. As the needs and the requirements vary depending on their volume, the
entire enterprise problem can be broken into chunks of manageable pieces. These
pieces can be implemented and tested individually with high integration effort.
Therefore it becomes essential to analyze the economic and technical
feasibility of realizable enterprise solution. It is difficult to migrate from
one technological and business aspect to other as the enterprise evolves. The
existing process models in system engineering emphasize on life-cycle
management and low-level activity coordination with milestone verification.
Many organizations are developing enterprise architecture to provide a clear
vision of how systems will support and enable their business. The paper
proposes an approach for selection of suitable enterprise architecture
depending on the measurement framework. The framework consists of unique
combination of higher order goals, non-functional requirement support and
inputs-outcomes pair evaluation. The earlier efforts in this regard were
concerned about only custom scales indicating the availability of a parameter
in a range.Comment: 22 Page
Integrating enterprise architecture and Np Iso 4457
The growing importance of NP ISO 4457 and Enterprise Architecture (EA) is becoming
increasingly recognized. However, since they are distinct governance approaches with different
perspectives, organizations end up facing several challenges, which leads to efficiency
problems, waste of resources and misalignment.
This thesis proposes to overcome such problems by integrating NP ISO 4457 with EA. This
way, a Reference Architecture is developed, using Archimate, which helps organizations to
conform to the Standard’s requirements, by determining how processes and resources are
organized and realized. This is a unique contribution, since the Reference Architecture can be
applied generically to every organization
A Value-Driven Framework for Software Architecture
Software that is not aligned with the business values of the organization for which it
was developed does not entirely fulfill its raison d’etre. Business values represent what
is important in a company, or organization, and should influence the overall software
system behavior, contributing to the overall success of the organization. However, approaches
to derive a software architecture considering the business values exchanged
between an organization and its market players are lacking. Our quest is to address this
problem and investigate how to derive value-centered architectural models systematically.
We used the Technology Research method to address this PhD research question.
This methodological approach proposes three steps: problem analysis, innovation, and
validation. The problem analysis was performed using systematic studies of the literature
to obtain full coverage on the main themes of this work, particularly, business value
modeling, software architecture methods, and software architecture derivation methods.
Next, the innovation step was accomplished by creating a framework for the derivation
of a software reference architecture model considering an organization’s business values.
The resulting framework is composed of three core modules: Business Value Modeling,
Agile Reference Architecture Modeling, and Goal-Driven SOA Architecture Modeling.
While the Business value modeling module focuses on building a stakeholder-centric
business specification, the Agile Reference Architecture Modeling and the Goal-Driven
SOA Architecture Modeling modules concentrate on generating a software reference architecture
aligned with the business value specification. Finally, the validation part of
our framework is achieved through proof-of-concept prototypes for three new domain
specific languages, case studies, and quasi-experiments, including a family of controlled
experiments. The findings from our research show that the complexity and lack of rigor
in the existing approaches to represent business values can be addressed by an early requirements
specification method that represents the value exchanges of a business. Also,
by using sophisticated model-driven engineering techniques (e.g., metamodels, model
transformations, and model transformation languages), it was possible to obtain source
generators to derive a software architecture model based on early requirements value
models, while assuring traceability throughout the architectural derivation process. In conclusion, despite using sophisticated techniques, the derivation process of a software
reference architecture is helped by simple to use methods supported by black box
transformations and guidelines that facilitate the activities for the less experienced software
architects. The experimental validation process used confirmed that our framework
is feasible and perceived as easy to use and useful, also indicating that the participants
of the experiments intend to use it in the future
Model-Driven Methodology for Rapid Deployment of Smart Spaces based on Resource-Oriented Architectures
Advances in electronics nowadays facilitate the design of smart spaces based on physical mash-ups of sensor and actuator devices. At the same time, software paradigms such as Internet of Things (IoT) and Web of Things (WoT) are motivating the creation of technology to support the development and deployment of web-enabled embedded sensor and actuator devices with two major objectives: (i) to integrate sensing and actuating functionalities into everyday objects, and (ii) to easily allow a diversity of devices to plug into the Internet. Currently, developers who are applying this Internet-oriented approach need to have solid understanding about specific platforms and web technologies. In order to alleviate this development process, this research proposes a Resource-Oriented and Ontology-Driven Development (ROOD) methodology based on the Model Driven Architecture (MDA). This methodology aims at enabling the development of smart spaces through a set of modeling tools and semantic technologies that support the definition of the smart space and the automatic generation of code at hardware level. ROOD feasibility is demonstrated by building an adaptive health monitoring service for a Smart Gym
A Framework for Evaluating Model-Driven Self-adaptive Software Systems
In the last few years, Model Driven Development (MDD), Component-based
Software Development (CBSD), and context-oriented software have become
interesting alternatives for the design and construction of self-adaptive
software systems. In general, the ultimate goal of these technologies is to be
able to reduce development costs and effort, while improving the modularity,
flexibility, adaptability, and reliability of software systems. An analysis of
these technologies shows them all to include the principle of the separation of
concerns, and their further integration is a key factor to obtaining
high-quality and self-adaptable software systems. Each technology identifies
different concerns and deals with them separately in order to specify the
design of the self-adaptive applications, and, at the same time, support
software with adaptability and context-awareness. This research studies the
development methodologies that employ the principles of model-driven
development in building self-adaptive software systems. To this aim, this
article proposes an evaluation framework for analysing and evaluating the
features of model-driven approaches and their ability to support software with
self-adaptability and dependability in highly dynamic contextual environment.
Such evaluation framework can facilitate the software developers on selecting a
development methodology that suits their software requirements and reduces the
development effort of building self-adaptive software systems. This study
highlights the major drawbacks of the propped model-driven approaches in the
related works, and emphasise on considering the volatile aspects of
self-adaptive software in the analysis, design and implementation phases of the
development methodologies. In addition, we argue that the development
methodologies should leave the selection of modelling languages and modelling
tools to the software developers.Comment: model-driven architecture, COP, AOP, component composition,
self-adaptive application, context oriented software developmen
- …