Towards a View-Based Process for Designing and Documenting RESTful Service Architectures
|
|
- Melvin Stewart
- 6 years ago
- Views:
Transcription
1 Towards a View-Based Process for Designing and Documenting RESTful Service Architectures Bruno Costa PPGI/Federal University of Rio de Janeiro (UFRJ) Rio de Janeiro, Brazil brunocosta.dsn@gmail.com Paulo F. Pires PPGI/Federal University of Rio de Janeiro (UFRJ) Rio de Janeiro, Brazil paulo.f.pires@gmail.com Flávia C. Delicato PPGI/Federal University of Rio de Janeiro (UFRJ) Rio de Janeiro, Brazil fdelicato@gmail.com Flávio Oquendo IRISA-UMR/CNRS Université de Bretagne-Sud Vannes, France flavio.oquendo@irisa.fr ABSTRACT Representational State Transfer (REST) is an architectural style for service-based design. Regarded to be used in massively distributed and loosely coupled hypermedia systems, REST has been the de facto architecture style for REST-based web services (called RESTful services). Besides business functionality, RESTful services should address quality attribute requirements, which are commonly described in scenarios (textual descriptions of how to achieve such attribute in the system s context). However, to properly mapping scenarios into architectural elements is a non-trivial task. Furthermore, architects often fail to document adequately the design decisions taken during such mapping. These issues can result in low-quality RESTful services. In this paper, we present a view-based process that provides mechanisms to represent quality attribute scenarios as concrete design decisions that can be later used in the design of RESTful service architectures. Categories and Subject Descriptors D.2.11 [Software Engineering]: Software Architectures Data abstraction, Languages, Patterns. General Terms Design, Verification, Documentation. Keywords Rest, architectural decisions, model-driven architecture. 1. INTRODUCTION Views and viewpoints have been used to describe software architectures since the establishment of Software Architecture as a distinct discipline in the early 90s [11]. After 25 years, the usage of multiple views is a common practice in software design [4]. In this context, ISO/IEC standard [18] provides a widely accepted conceptual definition of architectural views, viewpoints, and models. An architectural view is a representation comprised of one or more architectural elements to address a set of design concerns from a specific viewpoint; while an architectural viewpoint is a specification of elements and conventions available Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. ECSAW '15, September 07-11, 2015, Dubrovnik/Cavtat, Croatia 2015 ACM. ISBN /15/09 $15.00 DOI: for constructing and using an architectural view. A view may consist of one or more models, which can be represented in diagrams. In turn, each diagram is developed using a set of graphical icons and conventions for visual representation from an associated language. When designing software, to reuse proven good design structures, the architecture is commonly designed according to existent architectural patterns and styles. In the last years, Representational State Transfer (REST) has been de facto architecture style used to design interoperable systems that exchange their information through web services [17], the so-called RESTful services. However, as demonstrated by [8] and [5], the adoption of RESTful services brings several benefits, but also poses new challenges and risks, primarily because the use of such style is pervasive across architectural modules and components of the system. Particularly important among those risks are failures to address effectively quality attribute requirements, such as Performance and Security, which results in low-quality services. Harrison and colleagues demonstrate another problem related to software design: the architects often fail to document adequately their decisions made during the activity of mapping from quality attribute requirements to architectural elements [7]. This leads to several problems, for instance, when decisions made during subsequent development interactions conflict with the original architectural decisions. In this context, this paper presents a view-based process to deal with the challenge of properly address quality attribute requirements and adequately document architectural decisions in the design of RESTful service architectures. We argue that the quality attribute requirements can be seen as stakeholders concerns and, thus, can be addressed in Quality Attribute Views of the system. Furthermore, in our approach we introduce the concept of Quality Attribute Viewpoints Library, which provides a set of quality attribute viewpoints to be used as foundations to model quality attribute views. In addition to assisting the mapping of quality attribute requirements into the RESTful service architecture, our approach also aims to improve the documentation of architectural decisions taken during such mapping. The remainder of this paper is organized as follows. Section 2 we discuss related work. Section 3 describes the proposed process. We present Exposer in Section 4. Section 5 presents a proof of concept. Finally, Section 6 presents the conclusion and future work.
2 2. RELATED WORK In the last years, there has been a range of proposals for the design of RESTful services by academia and industry. For example, Mulesoft RAML [13] is a non-proprietary domain-specific language (DSL) that implements standards, like YAML and JSON, to assist developers to create RESTful services. Based on the Eclipse Modeling Project (EMF), EMF-REST [6] enables the generation of RESTful services from Ecore models. was proposed to specify RESTful ser-vices based on a set of metamodels and transformations. Table 1 shows a comparison between our approach and the aforementioned works. The main distinguished features of our work are: (i) to be organized using views; (ii) to consider quality attribute requirements to create RESTful services, and; (iii) to aid in the documentation of architectural decisions. Tool Table 1: Comparison between our approach and related works Associated process MDA capabilities View-based Quality attribute requirements considered Documentation of arch. decisions Our approach Yes Yes Yes Yes Yes Yes Laitkorpi et al. Yes Yes Yes No No No Haupt et al. Yes Yes Yes No No No EMF-REST Yes Yes Yes No No No RAML Yes No No No No No From a research perspective, Laitkorpi and associates from Nokia Research Center, proposed one of the first systematic approaches to applying MDA to build RESTful web services [12]. In their work, they pointed out that the refinement of a functional specification into a RESTful service, which is resource-oriented, is not a trivial task. To deal with such complexity they proposed a set of model transformations, starting from service functionalities, specified in a UML sequence diagram, transformed to a resource model (a UML class diagram that expresses resource elements), followed by the service translation and code generation. Haupt and colleagues [8] present another model-driven approach to developing RESTful services. Such research proposes means to fulfill properly the REST constraints, focusing on uniform interface (U) and stateless (S). The authors advocate that the other constraints (like Client-Server and Code on Demand) are already realized or reflected by the HTTP protocol. An MDA environment 3. PROCESS DESCRIPTION In this section, we describe the proposed view-based process to design RESTful services. The entire process is split into two independent subprocesses: (i) the creation of quality attribute viewpoints library and (ii) the creation of quality attribute views, according to the viewpoints, followed by the generation of the service. The UML activity diagram depicted in Figure 1 shows the process as a whole with its subprocesses, input and output artifacts. We envision two user profiles in our approach: REST Specialist and REST Architect. The REST Specialist is responsible for creating the quality attribute viewpoints library based on REST quality attribute general scenarios and a REST meta-model. The REST Architect is responsible for the creation of the RESTful service views according to quality attributes concrete scenarios and quality attribute viewpoints from the library. Finally, the Figure 1: The proposed view-based process for designing RESTful Services
3 architect generates the deployable RESTful Service. The proposed process is based on quality attribute scenarios, which are unambiguous and testable structured descriptions of how to achieve such attribute in the system s context [3]. In the literature, there are several studies that prove the efficiency of scenarios to express quality attribute requirements, such as [1][3]. In general, a well-formed scenario has a stimulus and response structure [2]: The system receives a stimulus (stimulus) and some desirable response is observed (response). There are two types of scenarios: concrete and general. The former describes scenarios that are specific to a particular system. The latter describes system independent scenarios, which are commonly used as basis to define the system s concrete scenarios [10]. In the next subsections, we describe in detail each activity with their sub-activities and artifacts. 3.1 Quality Attribute Elements and Parameters Identification The objective of this activity is to identify elements and parameters of a specific quality attribute general scenario in light of a REST meta-model and generates a textual document describing them. Regarding ISO/IEC 42010, such general scenarios are considered as concerns that will be addressed in the viewpoints. In this activity, the REST Specialist analyzes the quality attribute general scenarios in order to identify architectural elements and parameters that the quality attributes are sensitive. To identify and express such elements and parameters, it is used a meta-model that formally describes the REST style concepts and their relations. Such meta-model is the second input of Quality Attribute Elements and Parameters Identification activity. As an example, in this work we borrow the REST meta-model proposed by Schreier in [15] and REST quality attribute general scenarios presented by Costa et al. [6]. The main element in REST architectural style is the resource. A resource represents any important concept in the system domain that we want to make accessible through a service. Designing a RESTful service involves finding resources and their relationships, selecting operations for each resource, and defining data formats for them. The REST meta-model introduces the concept of ResourceType to describe resources of the system domain that can be a PrimaryResourceType, describing a single resource or an AggregationResourceType, which is comprised of two or more single resources. The representation of a resource refers to a media type (element MediaType in the meta-model), which is a hypermedia document that brings any useful information about the state of the resource and links to other associated resources. With the quality attribute general scenarios and the REST metamodel, the REST Specialist identifies the elements from the metamodel that are presented in the scenario description with its parameters. For example, the interoperability scenario: A service consumer A requests a resource R1 in a specific format (media type) and receives the representation of the actual state of R1 in response according to the requested format, two architectural elements can be identified: ResourceType and MediaType; the parameter is the format of the media type (e.g. XML, JSON). To perform such identification in the scenario description, the REST Specialist takes into account the detailed description of the metamodel and his/her empirical experience. 3.2 Viewpoint Specification The objective of Viewpoint Specification activity is to create viewpoints that represent the quality attribute general scenarios. To create them, the REST Specialist takes the elements and parameters identified in the Quality Attribute Elements and Parameters activity as an input and generates viewpoint models. Such models are created with a concrete syntax of the REST meta-model. The quality attribute viewpoints created in this activity comprise the quality attribute viewpoints library that will be used by the REST Architect to create quality attribute views. For each quality attribute general scenario, there is a quality attribute view-point. In the following, we describe how the viewpoints library is used by the REST Architect. 3.3 Create Quality Attribute Views To create views, the first input is a RESTful service architecture Figure 2: Applying views in RESTful Service Architecture
4 model. Such model must be created with the same concrete syntax of the viewpoints. The second input is the quality attribute requirements for the service described as quality attribute concrete scenarios. As a result of this activity, we have a set of quality attribute views of the RESTful service, each one addressing a specific quality attribute concrete scenario and the rationale used to specify them. The sub-activities of this activity and their artifacts are depicted in the UML activity diagram depicted in Figure 2. To create the views and generate the service (next activity), we recommend the support of an MDA tool in order to perform some activities automatically. In our approach, we propose the Exposer 1, an MDA 2 tool that offers capabilities for the specification, analysis, code generation and deployment of RESTful services. In Section 4 we provide more details about Exposer. In the following, we describe the activities on how the REST Architect uses the viewpoint library (Figure 2). Once the RESTful service architecture was created, the REST Architect analyzes the concrete quality attribute scenarios in order to address them in the architecture. Such scenarios provide the parameters that must be configured in the quality attribute views that will be created. First, the architect selects the respective quality attribute viewpoint from the library. After selecting the viewpoint, Exposer verifies if the elements and parameters from the quality attribute viewpoint were addressed in the service architecture (this means that all elements that exist in the quality attribute viewpoint must be in the architecture model). If so, Exposer hides the model elements that are not related to the quality attribute viewpoint, and shows only the elements related to the quality attribute viewpoint (note that, even if the service architecture model is comprised of several elements, Exposer will show only the elements related to the viewpoint to compose the quality attribute view of the service). After, Exposer exhibit the elements related to the viewpoint in order to REST Architect configure the required parameters. However, if Exposer could not find all elements and parameters related to the quality attribute viewpoint in the service architecture model, it will ask to the REST Architect if he/she wants to create such quality attribute view. When the architect confirms the creation of the view, Exposer includes the elements related to the view-point in the service architecture model and asks the architect to configure the related parameters. The specification of the quality attribute views and related configuration of their parameters are architectural decisions made by the REST architect in order to map quality attribute requirements into architectural elements. The rationale about architectural decisions is also registered as a textual description in the created view. Therefore, each view addresses a concrete scenario and the rationale to create them is registered in order to promote the documentation about the design decisions. 3.4 Generate the RESTful Service After creating the quality attribute views, the architectural elements are ready to be used to generate a deployable RESTful service. 4. EXPOSER Exposer is an MDA tool conceived to support the proposed viewbased process to develop RESTful services. Exposer implements 1 Exposer website: 2 Model-Driven Architecture: the extended Schreier s REST meta-model described in Subsection 2.1as the basis for its modeling language. Exposer is comprised by two components, namely Modeling Workbench, and Service Generator. The tool is an Eclipse IDE plugin created by exploring the capabilities provided by Eclipse Modeling Framework (EMF) [16] and related frameworks. The Exposer Modeling Workbench is used by both REST Specialists and REST Architects to create the quality attribute viewpoints library and the RESTful services views. The REST concepts presented in Subsection 2.1 compose the abstract syntax of the design language used in the modeling workbench. Based on such meta-model, we develop the concrete syntax as shown in Figure 3. In the palette, the section Quality Attribute Viewpoints Library contains three examples of quality attribute viewpoints. Figure 3: Exposer Modeling Workbench The Service Generator component is responsible to generate deployable RESTful services according to the service architecture model created in the Modeling Work-bench. For this task, the architect just has to configure the desired REST framework to be used in the service implementation, such as or RESTEasy [14]. The generated service can be deployed on application servers that implement the chosen framework. For example the JBoss [9]. 5. PROOF OF CONCEPT This Section presents a proof-of-concept aimed at verifying whether, by following the proposed process and using Exposer, a given a set of quality attribute requirements can be properly addressed in the service architecture. Moreover, we aim to assess if the architectural decisions are adequately documented. Finally, the result of the process should be a deployable service that follows such architectural decisions. 5.1 Creating Quality Attribute Viewpoints Library According to the process presented in Section 3 the first activity to be conducted by the REST Specialist is the identification of elements and parameters that the quality attribute is sensitive in order to generate the quality attribute viewpoints that will comprise the library. Such library can be used in any RESTful services design, however, in the proof-of-concept we will present the creation of the quality attribute viewpoint library followed by the subprocess to analyze the service architecture and generation of RESTful Services. To create the viewpoint models, we will use two REST quality attribute general scenarios as proposed by Costa and colleagues [5] and described in Table 2.
5 Table 2: Interoperability and reliability general scenarios Quality Attribute Interoperability Reliability General Scenario A service consumer A requests a resource R1 in a specific format (media type) and receives the representation of the actual state of R1 in response according to the requested format A service consumer A requests a resource R1 in a specific version specified directly in the URI and receives the representation of the actual state of R1 in the response message. Analyzing the interoperability general scenario, two architectural elements can be identified, ResourceType and MediaType. Furthermore, the parameter is the format (e.g. XML, JSON) that the resource will be represented. In Exposer, to create the viewpoint model, in addition to such identified elements, the REST Specialist can include other ones that he/she consider as important to the quality attribute. The idea is that the views that are based on the viewpoint must contain all elements addressed in the viewpoint by the specialist and their respective configured parameters. In our example, the viewpoint specifies that the related interoperability views must contain at least one aggregation resource with at least one primary resource and a media type associated and configured (the name and extension of the format). The interoperability viewpoint model is depicted in Figure 4 (a). There are two elements identified in the reliability general scenario in Table 2: ResourceType and Version; the parameter is the definition of the resource version. The reliability viewpoint model defines that it is necessary at least one AggregationResource and one PrimaryResource in a reliability view, and the definition of its version is required, as depicted in Figure 4 (b) Service Example: Bookstore Suppose that a bookstore wants to create a RESTful service to expose the information about their books and magazines via the web. The business goal is to provide means to third-party developers and companies create applications that use the information about their books. In the example, we will consider the interoperability and reliability concrete scenarios described in Table 3, created in light of the general scenarios described in Table 2: Table 3: Interoperability and reliability general scenarios Quality Attribute Reliability Testability Concrete Scenarios (CSs) CS1- A service consumer External_App requests a resource Book in a specific version specified directly in the URI and receives the representation of the actual state of Book in the response message. CS2- The developer of a Bookstore service consumer finds clear and up-to-date documentation of the service The RESTful Service Architecture of the Bookstore To create views, the first input is a RESTful service architecture model. This model can be seen as a structural view that contains the elements of the RESTful service, such as resources and media types, responsible for specifying the information that will be exposed by the service. Figure 5 depicts the RESTful service architecture model for the bookstore example. Figure 4: REST interoperability quality attribute viewpoint model (a); (b) REST reliability viewpoint model 5.2 Analysis of the Service Architecture and Generation of RESTful Services Once the quality attribute viewpoint library has been created, the REST Architect can analyze the RESTful service architecture in light of quality attribute concrete scenarios, create views for each quality attribute, and finally generate the RESTful service. (a) (b)
6 Figure 5: The RESTful Service Architecture of the Bookstore Bookstore Service Architecture Analysis With the service architecture model, the architect must analyze the model in order to create quality attribute views. In the bookstore service, there are three quality attribute requirements, specified by concrete scenarios in Table 3 (interoperability and reliability). Starting the analysis from the interoperability concrete scenarios, they specify that the resource must be represented by two different media types, thus the architectural decision was to specify two media type elements to the bookstore service, configuring XML and JSON as formats. To realize such decision in the service model, the architect selects the related viewpoint from the viewpoints library palette and Exposer automatically verifies if all viewpoint elements (at least one AggregationResource, one PrimaryResource and one related MediaType) exist in the service model. Since the viewpoint elements are missing, Exposer asks the architect to configure at least one media type (in the example, XML). As the concrete scenario describes that the service must have two media types, the architect includes another one manually, configuring the media type parameter as JSON format. For the reliability concrete scenario, the architectural decision was to configure the version to the service model. After the architect selects the related viewpoint, Exposer verifies that all elements of reliability viewpoint model (AggregationResource and PrimaryResource) are presented in the service architecture model, however, the version is not configured. So, Exposer asks the architect to configure the version in order to create such reliability view. Fig. 6 (a) depicts the interoperability view and (b) shows the reliability view (with a focus on the resource version) of the bookstore service model Bookstore RESful Service Generation The last activity is to generate the RESTful service. The bookstore service generated by the Exposer Service Generator is showed in Figure 7: Deployable bookstore RESful service 6. CONCLUSIONS AND FUTURE WORK In this paper, we presented a view-based process to deal with the challenge of addressing quality attribute requirements in RESTful services and to document the related architectural decisions. The process is supported by an MDA tool, named Exposer, which offers capabilities for the analysis, code generation, and deployment of RESTful services. In our approach, we introduce the concepts of quality attribute viewpoints library and quality attribute view. The library can be used in any RESTful service architecture to address quality attribute requirements through quality attribute views. Furthermore, the quality attribute views also compose the documentation of architectural decisions made in order to address the quality attribute requirements in the service architecture. Thus, the approach provides mechanisms to deal with a major problem in documenting architectural decisions: the knowledge vaporization [17], where architects fail to record their decisions, and such knowledge dissipates. As demonstrated by the proof-of-concept, we believe that by following our proposed process, quality attributes requirements can be addressed in the service architecture model. The architectural documentation is also enhanced once the decisions (a) (b) Figure 6: Interoperability view (a) and the reliability view (b) of the bookstore service Figure 6. The interoperability quality attribute was addressed by the methods that generate XML and JSON media types (lines 12 and 17). In line 7, the version (1.0.0) is defined, addressing the reliability quality attribute requirement. must be modeled as quality attribute views. Finally, by using MDA capabilities of Exposer, it is possible to generate quality RESTful services.
7 Our current and future work involves the improvements in views and viewpoints designing by using analytic models [8] and Reasoning Frameworks [9], respectively. Another aspect we are very interested in is a systematic evaluation of our process in realworld REST development. 7. ACKNOWLEDGMENTS This work was partially supported by Brazilian Funding Agencies FAPERJ (under grant E-26/ /2012 for Flavia C. Delicato) and CNPq (under grant / for Flavia Delicato and, / and / for Paulo F. Pires). We would like to thank Rich Hilliard, Simon Brown, Paulo Merson, and Matthias Naab, who provide valuable comments in discussions related to views and viewpoints in the SATURN Software Architecture Community. 8. REFERENCES [1] F. Bachmann, L. Bass, M. Klein, and C. Shelton. Designing software architectures to achieve quality attribute requirements. Software, IEE Proceedings, 152(4): , August [2] L. Bass, M. Klein, and G. Moreno. Applicability of General Scenarios to the Architecture Tradeoff Analysis Method. Technical Report CMU/SEI-2001-TR-014. Software Engineering Institute, Carnegie Mellon University, [3] L. Bass, P. Clements, and R. Kazman. Software Architecture in Practice. Addison-Wesley, [4] P. Clements, et al. Documenting Software Architectures: Views and Beyond. Pearson Education, [5] B. Costa, P. F. Pires, F. C. Delicato, ando P. Merson. Evaluating a Representational State Transfer (REST) Architecture - What is the impact of REST in my architecture? In IEEE/IFIP Conference on Software Architecture (WICSA) Proceedings, pages April [6] EMF-REST: Accessed: [7] N. B. Harrison, P. Avgeriou, and U. Zdun. Using Patterns to Capture Architectural Decisions. IEEE Software, 24(4): 38-45, July [8] F. Haupt, D. Karastoyanova, F. Leymann, and B. Schroth. A Model-Driven Approach for REST Compliant Services. In IEEE International Conference on Web Services Proceedings, pages June [9] JBoss AS - Project Documentation: Accessed: [10] J. Knodel, and M. Naab. Software Architecture Evaluation in Practice: Retrospective on More Than 50 Architecture Evaluations in Industry. In IEEE/IFIP Conference on Software Architecture (WICSA) Proceedings, pages April [11] P. Kruchten, H. Obbink, and J. Stafford. The Past, Present, and Future for Software Architecture. IEEE Software, 23(2): 22 30, March [12] M. Laitkorpi, P. Selonen, and T. Systa. Towards a modeldriven process for designing restful web services. In IEEE International Conference on Web Services (ICWS) Proceedings, pages July [13] RAML - RESTful API modeling language: Accessed: [14] RESTEasy: Accessed: [15] S. Schreier. Modeling RESTful applications. In Second International Workshop on RESTful Design (WS-REST) Proceedings, pages March [16] D. Steinberg, F. Budinsky, M. Paternostro, and E. Merks. Emf: Eclipse Modeling Framework 2.0 (2nd ed.). Addison- Wesley Professional, [17] E. Wilde, and C. Pautasso, C. REST: From Research to Practice. Springer Science & Business Media, [18] ISO/IEC/IEEE 42010: Systems and software engineering -- Architecture description.
Software Language Engineering of Architectural Viewpoints
Software Language Engineering of Architectural Viewpoints Elif Demirli and Bedir Tekinerdogan Department of Computer Engineering, Bilkent University, Ankara 06800, Turkey {demirli,bedir}@cs.bilkent.edu.tr
More informationArchitecture Viewpoint Template for ISO/IEC/IEEE 42010
Architecture Viewpoint Template for ISO/IEC/IEEE 42010 Rich Hilliard r.hilliard@computer.org VERSION 2.1b Abstract This is a template for specifying architecture viewpoints in accordance with ISO/IEC/IEEE
More informationModel Driven Development of Context Aware Software Systems
Model Driven Development of Context Aware Software Systems Andrea Sindico University of Rome Tor Vergata Elettronica S.p.A. andrea.sindico@gmail.com Vincenzo Grassi University of Rome Tor Vergata vgrassi@info.uniroma2.it
More informationIntegrating decision management with UML modeling concepts and tools
Downloaded from orbit.dtu.dk on: Dec 17, 2017 Integrating decision management with UML modeling concepts and tools Könemann, Patrick Published in: Joint Working IEEE/IFIP Conference on Software Architecture,
More informationModel Driven Ontology: A New Methodology for Ontology Development
Model Driven Ontology: A New Methodology for Ontology Development Mohamed Keshk Sally Chambless Raytheon Company Largo, Florida Mohamed.Keshk@raytheon.com Sally.Chambless@raytheon.com Abstract Semantic
More informationRARep: a Reference Architecture Repository
RARep: a Reference Architecture Repository Tales Prates Correia, Milena Guessi, Lucas Bueno Ruas Oliveira and Elisa Yumi Nakagawa University of São Paulo - USP, São Carlos, Brazil University of South Brittany
More informationA Lightweight Language for Software Product Lines Architecture Description
A Lightweight Language for Software Product Lines Architecture Description Eduardo Silva, Ana Luisa Medeiros, Everton Cavalcante, Thais Batista DIMAp Department of Informatics and Applied Mathematics UFRN
More informationDesigning a System Engineering Environment in a structured way
Designing a System Engineering Environment in a structured way Anna Todino Ivo Viglietti Bruno Tranchero Leonardo-Finmeccanica Aircraft Division Torino, Italy Copyright held by the authors. Rubén de Juan
More informationSequence Diagram Generation with Model Transformation Technology
, March 12-14, 2014, Hong Kong Sequence Diagram Generation with Model Transformation Technology Photchana Sawprakhon, Yachai Limpiyakorn Abstract Creating Sequence diagrams with UML tools can be incomplete,
More informationComposition-centered architectural pattern description language
Composition-centered architectural pattern description language Tu Minh Ton That, Salah Sadou, Flavio Oquendo, Isabelle Borne To cite this version: Tu Minh Ton That, Salah Sadou, Flavio Oquendo, Isabelle
More informationINTRODUCING A MULTIVIEW SOFTWARE ARCHITECTURE PROCESS BY EXAMPLE Ahmad K heir 1, Hala Naja 1 and Mourad Oussalah 2
INTRODUCING A MULTIVIEW SOFTWARE ARCHITECTURE PROCESS BY EXAMPLE Ahmad K heir 1, Hala Naja 1 and Mourad Oussalah 2 1 Faculty of Sciences, Lebanese University 2 LINA Laboratory, University of Nantes ABSTRACT:
More informationFundamentals to Creating Architectures using ISO/IEC/IEEE Standards
Fundamentals to Creating Architectures using ISO/IEC/IEEE Standards What to Architect? How to Architect? IEEE Goals and Objectives Chartered by IEEE Software Engineering Standards Committee to: Define
More informationMEMOCenterNG A full-featured modeling environment for organization modeling and model-driven software development
MEMOCenterNG A full-featured modeling environment for organization modeling and model-driven software development Jens Gulden and Prof. Dr. Ulrich Frank University Duisburg-Essen, Universitaetsstr. 9,
More informationA Domain-Driven Approach for Enterprise Development, using BPM, MDA, SOA and Web Services
A Domain-Driven Approach for Enterprise Development, using BPM, MDA, SOA and Web Services Fabio Perez Marzullo Federal University of Rio de Janeiro UFRJ, COPPE Database Laboratory, Brazil fpm@cos.ufrj.br
More informationSelf-Adaptive Middleware for Wireless Sensor Networks: A Reference Architecture
Architecting Self-Managing Distributed Systems Workshop ASDS@ECSAW 15 Self-Adaptive Middleware for Wireless Sensor Networks: A Reference Architecture Flávia C. Delicato Federal University of Rio de Janeiro
More informationArchitecting IoT Applications with SysADL
2017 IEEE International Conference on Software Architecture Workshops Architecting IoT Applications with SysADL Jair Leite, Thais Batista Computer Science Department Federal University of Rio Grande do
More informationScenarios, Quality Attributes, and Patterns: Capturing and Using their Synergistic Relationships for Product Line Architectures
Scenarios, Quality Attributes, and Patterns: Capturing and Using their Synergistic Relationships for Product Line Architectures Muhammad Ali Babar National ICT Australia Ltd. and University of New South
More informationPerspectives on User Story Based Visual Transformations
Perspectives on User Story Based Visual Transformations Yves Wautelet 1, Samedi Heng 2, and Manuel Kolp 2 1 KU Leuven, Belgium yves.wautelet@kuleuven.be, 2 LouRIM, Université catholique de Louvain, Belgium
More informationCISC836: Models in Software Development: Methods, Techniques and Tools
CISC836: Models in Software Development: Methods, Techniques and Tools Topic 4: Code Generation with EMF Meta modeling Languages for meta models: Ecore Using EMF and Ecoreto define a data model Using EMF
More informationQuality-Driven Architecture Design Method
Quality-Driven Architecture Design Method Matinlassi Mari, Niemelä Eila P.O. Box 1100, 90571 Oulu Tel. +358 8 551 2111 Fax +358 8 551 2320 {Mari.Matinlassi, Eila.Niemela}@vtt.fi Abstract: In this paper
More informationWeb Service Security Method To SOA Development
Web Service Security Method To SOA Development Nafise Fareghzadeh Abstract Web services provide significant new benefits for SOAbased applications, but they also expose significant new security risks.
More informationSoftware Architecture Recovery based on Dynamic Analysis
Software Architecture Recovery based on Dynamic Analysis Aline Vasconcelos 1,2, Cláudia Werner 1 1 COPPE/UFRJ System Engineering and Computer Science Program P.O. Box 68511 ZIP 21945-970 Rio de Janeiro
More informationArchitectural design of MDX compiler via attribute-driven design *
Jul. 2009, Volume 6, No.7 (Serial No.56) Journal of Communication and Computer, ISSN 1548-7709, USA Architectural design of MDX compiler via attribute-driven design * ZHANG Ping-jian, XI Jian-qing, ZHAO
More informationQoS-aware model-driven SOA using SoaML
QoS-aware model-driven SOA using SoaML Niels Schot A thesis submitted for the degree of MSc Computer Science University of Twente EEMCS - TRESE: Software Engineering Group Examination committee: Luís Ferreira
More informationIntroduction to software architecture Revision : 732
Introduction to software architecture Revision : 732 Denis Conan Septembre 2018 Foreword The content of these slides is extracted from the following references: L. Bass, P. Clements, and R. Kazman. Software
More informationAchieving Goals through Architectural Design Decisions
Journal of Computer Science 6 (12): 1424-1429, 2010 ISSN 1549-3636 2010 Science Publications Achieving Goals through Architectural Design Decisions Lena Khaled Department of Software Engineering, Faculty
More informationExploring Ontologies to Support the Establishment of Reference Architectures: An Example on Software Testing
Exploring Ontologies to Support the Establishment of Reference Architectures: An Example on Software Testing Elisa Yumi Nakagawa 1, Ellen Francine Barbosa 1, José Carlos Maldonado 1 1 Instituto de Ciências
More informationComparative Analysis of Architectural Views Based on UML
Electronic Notes in Theoretical Computer Science 65 No. 4 (2002) URL: http://www.elsevier.nl/locate/entcs/volume65.html 12 pages Comparative Analysis of Architectural Views Based on UML Lyrene Fernandes
More informationUsing SLE for creation of Data Warehouses
Using SLE for creation of Data Warehouses Yvette Teiken OFFIS, Institute for Information Technology, Germany teiken@offis.de Abstract. This paper describes how software language engineering is applied
More informationOn the link between Architectural Description Models and Modelica Analyses Models
On the link between Architectural Description Models and Modelica Analyses Models Damien Chapon Guillaume Bouchez Airbus France 316 Route de Bayonne 31060 Toulouse {damien.chapon,guillaume.bouchez}@airbus.com
More informationDesign Specification of Cyber-Physical Systems: Towards a Domain-Specific Modeling Language based on Simulink, Eclipse Modeling Framework, and Giotto
Design Specification of Cyber-Physical Systems: Towards a Domain-Specific Modeling Language based on Simulink, Eclipse Modeling Framework, and Giotto Muhammad Umer Tariq, Jacques Florence, and Marilyn
More informationDeveloping Software Applications Using Middleware Infrastructure: Role Based and Coordination Component Framework Approach
Developing Software Applications Using Middleware Infrastructure: Role Based and Coordination Component Framework Approach Ninat Wanapan and Somnuk Keretho Department of Computer Engineering, Kasetsart
More information4.2.2 Usability. 4 Medical software from the idea to the finished product. Figure 4.3 Verification/validation of the usability, SW = software
4.2.2 Usability Intended purpose, Market Validation Usability Usability Risk analysis and measures Specification of the overall system SW SW architecture/ of SW SW design Software design & integration
More informationThe Case for Meta-modeling Frameworks Specialisation
The Case for Meta-modeling Frameworks Specialisation S. Temate 1, L. Broto 1, and D. Hagimont 1 1 IRIT/ENSEEIHT, 2 rue Charles Camichel - BP 7122 31071 Toulouse cedex 7 (France) Abstract Domain Specific
More informationFSToolkit: Adopting Software Engineering Practices for Enabling Definitions of Federated Resource Infrastructures
FSToolkit: Adopting Software Engineering Practices for Enabling Definitions of Federated Resource Infrastructures Christos Tranoris and Spyros Denazis University of Patras, Greece tranoris@ece.upatras.gr,
More informationObject-Oriented Design
Object-Oriented Design Lecture 18 Department of Computer Engineering Implementation Workflow 1 Implementation Workflow Implementation is primarily about creating code. However, the OO analyst/designer
More informationGlobal Reference Architecture: Overview of National Standards. Michael Jacobson, SEARCH Diane Graski, NCSC Oct. 3, 2013 Arizona ewarrants
Global Reference Architecture: Overview of National Standards Michael Jacobson, SEARCH Diane Graski, NCSC Oct. 3, 2013 Arizona ewarrants Goals for this Presentation Define the Global Reference Architecture
More informationGeneric Modeling using UML extensions for variability
Generic Modeling using UML extensions for variability Intershop Research Intershop, Jena Matthias Clauß Software Engineering Group Dresden University of Technology M.Clauss@intershop.com September 14,
More informationA Metamodel for Specifying Quality Models in Model- Driven Engineering
A Metamodel for Specifying Quality Models in Model- Driven Engineering Parastoo Mohagheghi, Vegard Dehlen SINTEF, P.O.Box 124 Blindern N-0314 Oslo, Norway {Parastoo.Mohagheghi, Vegard.Dehlen}@sintef.no
More informationHyperFrame - A Framework for Hypermedia Authoring
HyperFrame - A Framework for Hypermedia Authoring S. Crespo, M. F. Fontoura, C. J. P. Lucena, D. Schwabe Pontificia Universidade Católica do Rio de Janeiro - Departamento de Informática Universidade do
More informationAutomatic Generation of Graph Models for Model Checking
Automatic Generation of Graph Models for Model Checking E.J. Smulders University of Twente edwin.smulders@gmail.com ABSTRACT There exist many methods to prove the correctness of applications and verify
More informationSOFTWARE testing is one of the main steps of each development
Proceedings of the 2014 Federated Conference on Computer Science and Information Systems pp. 1569 1574 DOI: 10.15439/2014F342 ACSIS, Vol. 2 Automating Acceptance Testing with tool support Tomasz Straszak,
More informationA Framework for the Structural Analysis of REST APIs
Institute of Architecture of Application Systems A Framework for the Structural Analysis of REST APIs Florian Haupt, Frank Leymann, Anton Scherer, Karolina Vukojevic-Haupt Institute of Architecture of
More informationTransformation of analysis model to design model
2010 International Conference on E-business, Management and Economics IPEDR vol.3 (2011) (2011) IACSIT Press, Hong Kong Transformation of analysis model to design model Lalji Prasad Truba College of Engineering
More informationModel-driven Development of RESTful APIs
Model-driven Development of RESTful APIs Vitaliy Schreibmann and Peter Braun Faculty of Computer Science, University of Applied Science Würzburg-Schweinfurt, Sanderheinrichsleitenweg 20, Würzburg, Germany
More informationSpemmet - A Tool for Modeling Software Processes with SPEM
Spemmet - A Tool for Modeling Software Processes with SPEM Tuomas Mäkilä tuomas.makila@it.utu.fi Antero Järvi antero.jarvi@it.utu.fi Abstract: The software development process has many unique attributes
More informationDescribing Information Systems Moving Beyond UML
Describing Information Systems Moving Beyond UML Eoin Woods Artechra eoin@artechra.com Nick Rozanski Artechra nick@artechra.com Timetable 10:00-10:10 Introductions 10:10-10:25 - Presentation: Architectural
More informationSOFTWARE ARCHITECTURE & DESIGN INTRODUCTION
SOFTWARE ARCHITECTURE & DESIGN INTRODUCTION http://www.tutorialspoint.com/software_architecture_design/introduction.htm Copyright tutorialspoint.com The architecture of a system describes its major components,
More informationDesignMinders: A Design Knowledge Collaboration Approach
DesignMinders: A Design Knowledge Collaboration Approach Gerald Bortis and André van der Hoek University of California, Irvine Department of Informatics Irvine, CA 92697-3440 {gbortis, andre}@ics.uci.edu
More informationBridging Missions and Architecture in Software-intensive Systems-of-Systems
Bridging Missions and Architecture in Software-intensive Systems-of-Systems Eduardo Silva, Everton Cavalcante, Thais Batista Department of Informatics and Applied Mathematics Federal University of Rio
More informationUniversity of Groningen. Towards Variable Service Compositions Using VxBPEL Sun, Chang-ai; Aiello, Marco
University of Groningen Towards Variable Service Compositions Using VxBPEL Sun, Chang-ai; Aiello, Marco Published in: International Conference on Software Reuse IMPORTANT NOTE: You are advised to consult
More informationViewpoints for Sensor based Environmental Information Systems
Viewpoints for Sensor based Environmental Information Systems Ruthbetha Kateule, Andreas Winter {kateule, winter}@se.uni-oldenburg.de Abstract: Sensor based environmental information systems are in use
More informationA UML SIMULATOR BASED ON A GENERIC MODEL EXECUTION ENGINE
A UML SIMULATOR BASED ON A GENERIC MODEL EXECUTION ENGINE Andrei Kirshin, Dany Moshkovich, Alan Hartman IBM Haifa Research Lab Mount Carmel, Haifa 31905, Israel E-mail: {kirshin, mdany, hartman}@il.ibm.com
More informationInformation Hiding and Aspect-Oriented Modeling
Information Hiding and Aspect-Oriented Modeling Wisam Al Abed and Jörg Kienzle School of Computer Science, McGill University Montreal, QC H3A2A7, Canada Wisam.Alabed@mail.mcgill.ca, Joerg.Kienzle@mcgill.ca
More informationModels in Conflict Towards a Semantically Enhanced Version Control System for Models
Models in Conflict Towards a Semantically Enhanced ersion Control System for Models Kerstin Altmanninger Department of Telecooperation, Johannes Kepler University Linz, Austria kerstin.altmanninger@jku.at
More informationA Model-Driven Framework for Domain Specific Process Design and Governance
A Model-Driven Framework for Domain Specific Process Design and Governance Adrian Mos 1, Mario Cortes-Cornax 1, José Miguel Pérez-Álvarez1,2, María Teresa Gómez-López 2 1 Xerox Research Center, 6 Chemin
More informationAn Approach to Quality Achievement at the Architectural Level: AQUA
An Approach to Quality Achievement at the Level: AQUA Heeseok Choi 1, Keunhyuk Yeom 2, Youhee Choi 3, and Mikyeong Moon 2 1 NTIS Organization, Korea Institute of Science and Technology Information Eoeun-dong
More informationA model-driven approach for REST compliant services
A model-driven approach for REST compliant services University of Stuttgart Universitätsstr. 38 70569 Stuttgart Germany Florian Haupt Institute of Architecture of Application Systems florian.haupt@iaas.uni-stuttgart.de
More informationModel Driven Architecture based Testing Tool based on Architecture Views
Model Driven Architecture based Testing Tool based on Architecture Views Burak Uzun and Bedir Tekinerdogan Information Technology Group, Wageningen University, Wageningen, The Netherlands Keywords: Abstract:
More informationAdaptive Hypermedia Systems Analysis Approach by Means of the GAF Framework
Adaptive Hypermedia Systems Analysis Approach by Means of the GAF Framework Evgeny Knutov, Paul De Bra, and Mykola Pechenizkiy Department of Computer Science, Eindhoven University of Technology, P.O. Box
More informationTowards Decision Centric Repository of Architectural Knowledge
Towards Decision Centric Repository of Architectural Knowledge Bartosz Michalik and Jerzy Nawrocki Poznan University of Technology, Institute of Computing Science, ul. Piotrowo 2, 60-965 Poznań, Poland
More informationSOFTWARE ARCHITECTURE INTRODUCTION TO SOFTWARE ENGINEERING PHILIPPE LALANDA
SOFTWARE ARCHITECTURE INTRODUCTION TO SOFTWARE ENGINEERING PHILIPPE LALANDA PURPOSE OF THIS CLASS An introduction to software architecture What is an architecture Why it is important How it is represented
More informationDomain Models for Laboratory Integration
Models for Laboratory Integration ANCA DANIELA IONITA Computers and Industrial Informatics Department University Politehnica of Bucharest Spl. Independentei 313, 060042, Bucharest ROMANIA Abstract: - Laboratory
More informationARCADIA: Model-Based Collaboration for System, Software and Hardware Engineering
www.thalesgroup.com ARCADIA: Model-Based Collaboration for System, Software and Hardware Engineering An architecture-centric, tool-supported method Jean-Luc Voirin & Stéphane Bonnet RETEX AFIS - May 2014
More informationA component-centric UML based approach for modeling the architecture of web applications.
International Journal of Recent Research and Review, Vol. V, March 2013 ISSN 2277 8322 A component-centric UML based approach for modeling the architecture of web applications. Mukesh Kataria 1 1 Affiliated
More informationModeling variability with UML
Modeling variability with UML Matthias Clauß Intershop Research Software Engineering Group Intershop, Jena Dresden University of Technology Matthias.Clauss@gmx.de Keywords: product families, domain modeling,
More informationA Process Framework for Designing Software Reference Architectures for Providing Tools as a Service
Downloaded from orbit.dtu.dk on: Dec 20, 2017 A Process Framework for Designing Software Reference Architectures for Providing Tools as a Service Chauhan, Muhammad Aufeef; Babar, Muhammad Ali; Probst,
More informationArchitecture-Centric Evolution in Software Product Lines:
Architecture-Centric Evolution in Software Product Lines: Position Paper Hassan Gomaa Department of Information and Software Engineering George Mason University Fairfax, Virginia 22030, USA hgomaa@gmu.edu
More informationUnit 1 Introduction to Software Engineering
Unit 1 Introduction to Software Engineering João M. Fernandes Universidade do Minho Portugal Contents 1. Software Engineering 2. Software Requirements 3. Software Design 2/50 Software Engineering Engineering
More informationUsing the UML for Architectural Description Rich Hilliard
Using the UML for Architectural Description Rich Hilliard rh@isis2000.com Outline What is IEEE P1471? The IEEE P1471 Conceptual Framework Requirements on Architectural Descriptions Using the UML in the
More informationA Meta-Model for Fact Extraction from Delphi Source Code
Electronic Notes in Theoretical Computer Science 94 (2004) 9 28 www.elsevier.com/locate/entcs A Meta-Model for Fact Extraction from Delphi Source Code Jens Knodel and G. Calderon-Meza 2 Fraunhofer Institute
More informationSoftware Architecture Viewpoint Models: A Short Survey
Software Architecture Viewpoint Models: A Short Survey Valiallah Omrani 1, Seyyed Ali Razavi Ebrahimi 2 1 Computer Science & Information Technology, Payam Noor University (PNU), Tehran, Iran omrani@inio.ac.ir
More informationPattern-Based Architectural Design Process Model
Pattern-Based Architectural Design Process Model N. Lévy, F. Losavio Abstract: The identification of quality requirements is crucial to develop modern software systems, especially when their underlying
More informationA Comparison of Ecore and GOPPRR through an Information System Meta Modeling Approach
A Comparison of Ecore and GOPPRR through an Information System Meta Modeling Approach Vladimir Dimitrieski, Milan Čeliković, Vladimir Ivančević and Ivan Luković University of Novi Sad, Faculty of Technical
More informationADD 3.0: Rethinking Drivers and Decisions in the Design Process
ADD 3.0: Rethinking Drivers and Decisions in the Design Process Rick Kazman Humberto Cervantes SATURN 2015 Outline Presentation Architectural design and types of drivers The Attribute Driven Design Method
More informationCurrent trends and frameworks for modeldriven approaches to software development
1 Current trends and frameworks for modeldriven approaches to software development Trial Lecture Odd Petter Nord Slyngstad Trondheim, 1 st April 2011 Anita Gupta 28/05/2009 2 Overview What is a model-driven
More informationVARIABILITY MODELING FOR CUSTOMIZABLE SAAS APPLICATIONS
VARIABILITY MODELING FOR CUSTOMIZABLE SAAS APPLICATIONS ABSTRACT Ashraf A. Shahin 1, 2 1 College of Computer and Information Sciences, Al Imam Mohammad Ibn Saud Islamic University (IMSIU) Riyadh, Kingdom
More informationDeveloping Web-Based Applications Using Model Driven Architecture and Domain Specific Languages
Proceedings of the 8 th International Conference on Applied Informatics Eger, Hungary, January 27 30, 2010. Vol. 2. pp. 287 293. Developing Web-Based Applications Using Model Driven Architecture and Domain
More informationTWO APPROACHES IN SYSTEM MODELING AND THEIR ILLUSTRATIONS WITH MDA AND RM-ODP
TWO APPROACHES IN SYSTEM MODELING AND THEIR ILLUSTRATIONS WITH MDA AND RM-ODP Andrey Naumenko, Alain Wegmann Laboratory of Systemic Modeling, Swiss Federal Institute of Technology - Lausanne, EPFL-I&C-LAMS,1015
More informationProduct Lines, Features, and MDD 1
Product Lines, Features, and MDD 1 Bruno González-Baixauli, Miguel A. Laguna, Yania Crespo Department of Computer Science, University of Valladolid, Campus M. Delibes, 47011 Valladolid, Spain {bbaixauli,
More informationWhole Platform Foundation. The Long Way Toward Language Oriented Programming
Whole Platform Foundation The Long Way Toward Language Oriented Programming 2008 by Riccardo Solmi made available under the Creative Commons License last updated 22 October 2008 Outline Aim: Engineering
More informationMDA Driven xuml Plug-in for JAVA
2012 International Conference on Information and Network Technology (ICINT 2012) IPCSIT vol. 37 (2012) (2012) IACSIT Press, Singapore MDA Driven xuml Plug-in for JAVA A.M.Magar 1, S.S.Kulkarni 1, Pooja
More informationQuantifying and Assessing the Merge of Cloned Web-Based System: An Exploratory Study
Quantifying and Assessing the Merge of Cloned Web-Based System: An Exploratory Study Jadson Santos Department of Informatics and Applied Mathematics Federal University of Rio Grande do Norte, UFRN Natal,
More informationA Comparative Analysis of Architecture Frameworks
A Comparative Analysis of Architecture Frameworks Antony Tang Jun Han Pin Chen School of Information Technology DSTO C3 Research Centre Swinburne University of Technology Department of Defence Melbourne,
More informationThe Unified Modelling Language. Example Diagrams. Notation vs. Methodology. UML and Meta Modelling
UML and Meta ling Topics: UML as an example visual notation The UML meta model and the concept of meta modelling Driven Architecture and model engineering The AndroMDA open source project Applying cognitive
More informationDominique Blouin Etienne Borde
Dominique Blouin Etienne Borde dominique.blouin@telecom-paristech.fr etienne.borde@telecom-paristech.fr Institut Mines-Télécom Content Domain specific Languages in a Nutshell Overview of Eclipse Modeling
More informationSoftware Architecture in Action. Flavio Oquendo, Jair C Leite, Thais Batista
Software Architecture in Action Flavio Oquendo, Jair C Leite, Thais Batista Motivation 2 n In this book you can learn the main software architecture concepts and practices. n We use an architecture description
More informationComponent-based Development Process and Component Lifecycle
Journal of Computing and Information Technology - CIT 13, 2005, 4, 321-327 321 Component-based Development Process and Component Lifecycle Ivica Crnkovic 1, Stig Larsson 2 and Michel Chaudron 3 1 Mälardalen
More informationCOrDeT Cannes : Use of domain engineering process to develop reusable architectures and building-blocks
COrDeT Cannes : Use of domain engineering process to develop reusable architectures and building-blocks G. Garcia 1, X. Olive 1, A. Pasetti 2, O. Rohlik 2, T. Vardanega 3, A.-I. Rodríguez-Rodríguez 4 A.
More informationEvaluation of Commercial Web Engineering Processes
Evaluation of Commercial Web Engineering Processes Andrew McDonald and Ray Welland Department of Computing Science, University of Glasgow, Glasgow, Scotland. G12 8QQ. {andrew, ray}@dcs.gla.ac.uk, http://www.dcs.gla.ac.uk/
More informationFoundations of Software Engineering
Foundations of Software Engineering Lecture 9: Architecture Documentation, Patterns, and Tactics Christian Kaestner 1 Learning Goals Use notation and views to describe the architecture suitable to the
More informationFirst Steps Towards Conceptual Schema Testing
First Steps Towards Conceptual Schema Testing Albert Tort and Antoni Olivé Universitat Politècnica de Catalunya {atort,olive}@lsi.upc.edu Abstract. Like any software artifact, conceptual schemas of information
More informationWinery A Modeling Tool for TOSCA-Based Cloud Applications
Winery A Modeling Tool for TOSCA-Based Cloud Applications Oliver Kopp 1,2, Tobias Binz 2,UweBreitenbücher 2, and Frank Leymann 2 1 IPVS, University of Stuttgart, Germany 2 IAAS, University of Stuttgart,
More informationApplying Microservices in Webservices, with An Implementation Idea
International Conference on Computer Applications 64 International Conference on Computer Applications 2016 [ICCA 2016] ISBN 978-81-929866-5-4 VOL 05 Website icca.co.in email icca@asdf.res.in Received
More informationChristian Doppler Laboratory
Christian Doppler Laboratory Software Engineering Integration For Flexible Automation Systems AutomationML Models (in EMF and EA) for Modelers and Software Developers Emanuel Mätzler Institute of Software
More informationDefinition of Visual Language Editors Using Declarative Languages
Definition of Visual Language Editors Using Declarative Languages Torbjörn Lundkvist TUCS Turku Centre for Computer Science SoSE Graduate School on Software Systems and Engineering Department of Information
More informationProceedings of the 6th Educators Symposium: Software Modeling in Education at MODELS 2010 (EduSymp 2010)
Electronic Communications of the EASST Volume X (2010) Proceedings of the 6th Educators Symposium: Software Modeling in Education at MODELS 2010 (EduSymp 2010) m2n: Translating Models to Natural Language
More informationSoftware Architecture
Software Architecture Benjamin Satzger Distributed Systems Group TU Wien http://www.infosys.tuwien.ac.at/staff/ bsatzger Models Terms Unified Modeling Language (UML) Architecture Description Language (ADL)
More informationComputation Independent Model (CIM): Platform Independent Model (PIM): Platform Specific Model (PSM): Implementation Specific Model (ISM):
viii Preface The software industry has evolved to tackle new approaches aligned with the Internet, object-orientation, distributed components and new platforms. However, the majority of the large information
More informationTOWARDS AUTOMATED TOOL SUPPORT FOR EXTRACTING INFORMATION FROM KNOWLEDGE REPOSITORY
I J I T E ISSN: 2229-7367 3(1-2), 2012, pp. 301-305 TOWARDS AUTOMATED TOOL SUPPORT FOR EXTRACTING INFORMATION FROM KNOWLEDGE REPOSITORY 1 C. DHAYA AND 2 G. ZAYARAZ 1 Research Scholar, 2 Associate Professor
More information