| 1. |
- Börjesson, Anna, et al.
(author)
-
Continuing Professional Development by Practitioner Integrated LearningContinuing Professional Development by Practitioner Integrated Learning
- 2007
-
In: OOPSLA - Object-Oriented Programing Languages.
-
Conference paper (peer-reviewed)abstract
- To prevent skilled professionals from being phased out or forced into professions for which they are not talented, organized forms of lifelong learning are needed. Continuing professional devel-opment is an approach supporting lifelong learning. This ap-proach is however criticized for being expensive and not providing the necessary knowledge. In response to this, we have executed a study in order to understand how universities can ef-fectively support continuous professional development. By in-volving industry professionals as participants in university courses using problem based learning, we have designed what we call Practitioner Integrated Learning (PIL). This learning ap-proach has shown positive effects in terms of level of learning, realism, knowledge diffusion, study load and costs. We present a 15-months action research project integrating 16 industry manag-ers and 16 university students in a continuing professional devel-opment effort. Based on this study, we argue that PIL is a learning approach that effectively supports continuing professional devel-opment.
|
|
| 2. |
- Chaudron, Michel, 1969, et al.
(author)
-
Proceedings of the 2nd Workshop on Experiences and Empirical Studies in Software Modelling
- 2012
-
In: Research Reports in Software Engineering and Management. - Göteborg : University of Gothenburg.
-
Conference paper (other academic/artistic)abstract
- The International Workshop on Experiences and Empirical Studies in Software Modelling (EESSMod) is a satellite event of the ACM/IEEE International Conference on Model Driven Engineering Languages and Systems (MoDELS), with professionals and researchers interested in software modelling as intended audience, and with the bjective to 1) build a better understanding of the industrial use of modelling techniques, languages and tools; 2) start building theories about the effectiveness of modelling approaches; 3) identify directions for future research in the field; 4) facilitate and encourage joint research and experimentation in software modelling.The report contains the proceedings of the 2nd edition of the workshop, held in Innsbruck, Oct 2, 2012.
|
|
| 3. |
- Gellerstedt, Martin, 1966-, et al.
(author)
-
The Goalkeeper : a tool for monitoring learning outcomes in PhD education
- 2015
-
In: ICERI2015 Proceedings. - : IATED Academy. - 9788460826576 ; , s. 6223-6230
-
Conference paper (peer-reviewed)abstract
- The journey from being a new Ph. D.-candidate towards passing the doctorate grade is often a bumpy road with both unexpected and complex challenges that has to be turned in to learning experiences that adds to progression. In this paper we describe the development and use of a tool (the Goalkeeper) designed to support, structure and visualize this journey. It is a tool for supervisors, doctorate students as well as people responsible for quality assurance of a doctorate education. Based on our experiences of having utilised the tool we argue that it is important that the implementation of such a tool is firmly grounded in a quality culture where support of progression and formative assessment dominate over summative assessment and control.
|
|
| 4. |
- Martini, Antonio, 1982, et al.
(author)
-
A Framework for Speeding Up Interactions Between Agile Teams and Other Parts of the Organization
- 2014
-
In: Continuous Software Engineering. - Cham : Springer. - 9783319112824 ; , s. 67-82
-
Book chapter (other academic/artistic)abstract
- A known problem in large software companies is to balance the return on investment coming from short-term and long-term business goals dependent on the responsiveness of the companies. In the previous chapter we have found challenges in interactions between the Agile team and other parts of the organization. We have conducted an investigation on three large product line companies employing Agile software development in order to find practices that would mitigate the challenges.
|
|
| 5. |
- Martini, Antonio, 1982, et al.
(author)
-
A multiple case study on the inter-group interaction speed in large, embedded software companies employing agile
- 2016
-
In: Journal of Software: Evolution and Process. - : Wiley. - 2047-7481 .- 2047-7473. ; 28:1, s. 4-26
-
Journal article (peer-reviewed)abstract
- The adoption of Agile Software Development in large companies is a recent phenomenon of great interest both for researchers and practitioners. Although intra-team interaction is well supported by established agile practices, the critical interaction between the agile team and other parts of the organization is still unexplored in literature. Such interactions slow down the development, hindering the achievement of business goals based on speed: short time to market, quick replication of products of a product-line, and reaction time for product evolution.We have employed a two-year long multiple-case case-study, collecting data through interviews and a survey in three large companies developing embedded software. Through a combination of qualitative and quantitative analysis, we have found strong evidence that interaction challenges between the development team and other groups in the organization hinder speed and are widespread in the organizations.This paper also identifies current practices in use at the studied companies and provides detailed guidelines for novel solutions in the investigated domain. Such practices are called boundary-spanning activities in information system research and coordination theory. We present a comparison between large embedded software companies employing agile and developing a line of products based on reused assets and agile companies developing pure software. We highlight specific contextual factors and areas where novel spanning activities are needed for mitigating the interaction challenges hindering speed.
|
|
| 6. |
- Martini, Antonio, 1982, et al.
(author)
-
Communication factors for speed and reuse in large-scale agile software development
- 2013
-
In: 17th International Software Product Line Conference, August 26-30, Tokyo, Japan. - New York, NY, USA : Association for Computing Machinery (ACM). - 9781450319683
-
Conference paper (peer-reviewed)abstract
- An open issue in industry is the combination of software reuse in the context of large scale Agile Software Development. The speed offered by Agile Software Development is needed for short time to market, while reuse strategies such as Software Product Line Engineering are needed for long-term productivity, efficiency, and profit. The paper investigates, through a survey, communication factors affecting both speed and reuse in 3 large companies developing embedded systems and employing Agile Software Development and Software Product Line Engineering. Our results include a prioritized list of communication related factors obtained by statistical analysis and the recognition and spread of the factors in the companies. We have recognized 5 interfaces with the Agile development team that need to be improved: system engineers (architects), product management, distributed teams, inter-project teams and sales unit. Few factors (involving inter-project communication) depend on the business drivers for the company. We also reveal that Agile teams need strategic and architectural inputs in order to be implanted in a large company employing Software Product Line Engineering. Academic and industrial training as well as different tactics for co-location would improve the communication skills of engineers. There is also a need for solutions, in the reference architecture, for fostering Agile Software Development: the goal is the combination of the focus on customer value of the teams, reusability, system requirements and avoidance of organizational dependencies.
|
|
| 7. |
- Martini, Antonio, 1982, et al.
(author)
-
Enablers and inhibitors for speed with reuse
- 2012
-
In: ACM International Conference Proceeding Series: 16th International Software Product Line Conference, SPLC 2012; Salvador; 2 September 2012 through 7 September 2012. - New York, NY, USA : ACM. - 9781450310956 - 9781450310949 ; , s. 116-125
-
Conference paper (peer-reviewed)abstract
- An open issue in industry is software reuse in the context of large scale Agile product development. The speed offered by agile practices is needed to hit the market, while reuse is needed for long-term productivity, efficiency, and profit. The paper presents an empirical investigation of factors influencing speed and reuse in three large product developing organizations seeking to implement Agile practices. The paper identifies, through a multiple case study with 3 organizations, 114 business-, process-, organizational-, architecture-, knowledge- and communication factors with positive or negative influences on reuse, speed or both. Contributions are a categorized inventory of influencing factors, a display for organizing factors for the purpose of process improvement work, and a list of key improvement areas to address when implementing reuse in organizations striving to become more Agile. Categories identified include good factors with positive influences on reuse or speed, harmful factors with negative influences, and complex factors involving inverse or ambiguous relationships. Key improvement areas in the studied organizations are intra-organizational communication practices, reuse awareness and practices, architectural integration and variability management. Results are intended to support process improvement work in the direction of Agile product development. Feedback on results from the studied organizations has been that the inventory captures current situations, and is useful for software process improvement work.
|
|
| 8. |
- Martini, Antonio, 1982, et al.
(author)
-
Improving Businesses Success by Managing Interactions among Agile Teams in Large Organizations
- 2013
-
In: Lecture Notes in Business Information Processing. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1865-1356 .- 1865-1348. - 9783642393358 ; 150, s. 60-72
-
Conference paper (peer-reviewed)abstract
- To achieve successful business, large software companies employ Agile Software Development to be fast and responsive in addressing customer needs. However, a large number of small, independent and fast teams suffer from excessive inter-team interactions, which may lead to paralysis. In this paper we provide a framework to understand how such interactions affect business goals dependent on speed. We detect factors causing observable interaction effects that generate speed waste. By combining data and literature, we provide recommendations to manage such factors, complementing current Agile practices so that they can be adapted in large software organizations.
|
|
| 9. |
- Martini, Antonio, 1982, et al.
(author)
-
Role of Architects in Agile Organizations
- 2014
-
In: Continuous Software Engineering. - Cham : Springer. - 9783319112824 ; , s. 39-50
-
Book chapter (other academic/artistic)abstract
- Agile software development is broadly adopted in industry and works well for small-scale projects. In the context of large-scale development, however, there is a need for additional structure in the form of roles and practices, especially in the area of software architecture. In this chapter, we introduce the CAFFEA framework that defines a model for architecture governance. The framework defines three roles, i.e., chief architect, governance architect, and team architect, as well as a set of practices and responsibilities assigned to these roles. The CAFFEA framework has been developed and validated in close collaboration with several companies.
|
|
| 10. |
- Martini, Antonio, 1982, et al.
(author)
-
Teams Interactions Hindering Short-Term and Long-Term Business Goals
- 2014
-
In: Continuous Software Engineering. - Cham : Springer. - 9783319112824 ; , s. 51-65
-
Book chapter (other academic/artistic)abstract
- A known problem in large software companies is to balance the return on investment coming from short-term and long-term business goals dependent on the responsiveness of the companies. We have conducted an investigation on three large product line companies employing Agile software development (ASD) to better understand this problem: we have recognized several challenges that were hindering one or both kinds of business goals. Interaction challenges were quite critical among the Agile teams but also between the Agile team and other parts of the organization, such as architects and product management. We also further investigated which root factors were behind the interaction challenges, what symptoms can be recognized in the organization to spot the interaction challenges, and how they were related to the recent employment of ASD in the companies.
|
|
| 11. |
- Martini, Antonio, 1982, et al.
(author)
-
Towards introducing agile architecting in large companies: The CAFFEA framework
- 2015
-
In: Lecture Notes in Business Information Processing, Agile Processes in Software Engineering, and Extreme Programming 16th International Conference, XP 2015, Helsinki, Finland, May 25-29, 2015. - Cham : Springer International Publishing. - 1865-1348 .- 1865-1356. - 9783319186115 ; 212
-
Conference paper (peer-reviewed)abstract
- To continuously deliver value both in short-term and long-term, a key goal for large product lines companies is to combine Agile Software Development with the continuous development and management of software architecture. We have conducted interviews involving several roles at 3 sites from 2 large companies employing Agile. We have identified current architect roles and gaps in the practices employed at the organizations. From such investigation, we have developed an organizational framework, CAFFEA, for Agile architecting, including roles, teams and practices.
|
|
| 12. |
- Pareto, Lars, 1966, et al.
(author)
-
A Quality Model for Design Documentation in Model-centric Projects
- 2006
-
In: Proceedings of the Third International Workshop on Software Quality Assurance (SOQUA 2006), Portland, Oregon, USA.
-
Conference paper (peer-reviewed)abstract
- Model-centric software processes, such as RUP, involve a rich set of artefacts (e.g., requirements specifications, design models, code) used for many activities (e.g., cost estimation, construction, communication, maintenance, archiving) by engineers in many roles (e.g., analysts, designers, developers, testers, managers). This diversity makes organisation and implementation of infrastructure for artefacts (such as document repositories, web portals, editors, indexes) a challenge: without analysis of involved tasks, and validation of the infrastructure’s implementation, some tasks may not be properly supported. This paper presents a quality model for design documentation (i.e., for artefacts on the abstraction level between requirements specifications and code) intended to be used for requirements engineering of such. Twenty two qualities, most of which concern nonfunctional requirements on the design documentation are identified. The model is based on qualitative analysis of interviews with engineers and managers in a large software development organisation with 8 years experience of implementing RUP.
|
|
| 13. |
- Pareto, Lars, 1966, et al.
(author)
-
Architectural Descriptions as Boundary Objects in System and Design Work
- 2010
-
In: Lecture Notes in Computer Science. 13th International Conference on Model Driven Engineering Languages and Systems, MODELS 2010, Oslo, 3-8 October 2010. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 0302-9743. - 9783642161285 ; 6395, s. 406-419
-
Conference paper (peer-reviewed)abstract
- Lean and Agile processes have resolved longstanding problems in engineering communication by replacing document based communication with face-to-face collaboration, but do not yet scale to very large and heterogeneous projects. This paper proposes a compatible extension to lean and agile processes that addresses this limitation. The core idea is to adopt the view of documentation as boundary objects: shared artefacts that maintain integrity across a project’s intersecting social worlds. The paper presents a case study, in which interviews with system engineers and designers were analysed to obtain requirements on an architectural description serving as boundary objects in a telecommunications project. The main result is a list of 18 empirically grounded, elementary requirements, worth considering when implementing lean and agile processes in the large.
|
|
| 14. |
- Pareto, Lars, 1966, et al.
(author)
-
Collaborative Prioritization of Architectural Concerns
- 2012
-
In: Journal of Systems and Software. - : Elsevier BV. - 0164-1212. ; 85:9, s. 1971-1994
-
Journal article (peer-reviewed)abstract
- Efficient architecture work involves balancing the degree of architectural documentation with attention to needs, costs, agility and other factors. This paper presents a method for prioritizing architectural concerns in the presence of heterogeneous stakeholder groups in large organizations that need to evolve existing architecture. The method involves enquiry, analysis, and deliberation using collaborative and analytical techniques. Method outcomes are action principles directed to managers, and assessment of user needs directed to architects, along with evidence. The method results from 4 years of action research at Ericsson AB with the purpose of adding missing views to architectural documentation and removing superfluous ones. It is illustrated on a case where 29 senior engineers and managers within Ericsson prioritized 37 architectural concerns areas to arrive at 8 action principles, 5 prioritized improvement areas, and 24 improvement suggestions. Feedback from the organization is that the method has been effective in prioritizing architectural concerns, that data collection and analysis is more extensive compared to traditional prioritization practices, but that extensive analysis seems inevitable in architecture improvement work.
|
|
| 15. |
- Pareto, Lars, 1966, et al.
(author)
-
Concern coverage in base station development: an empirical investigation
- 2012
-
In: Software and Systems Modeling. - : Springer Science and Business Media LLC. - 1619-1366 .- 1619-1374. ; 11:3, s. 409-429
-
Journal article (peer-reviewed)abstract
- Contemporary model driven development tools only partially support the abstractions occurring in complex embedded systems development. This article presents an interpretive case study in which architectural concerns important to seven engineers in a large product developing organization were compared to the views actually provided by the organization's models. The paper's main finding is an empirically grounded catalogue of architectural concerns for a large, complex embedded systems project, and an assessment of the degree to which the studied organization has managed to realize support for these concerns within economical and organizational constraints. In the studied case, 114 different architectural concerns were found to be important to the interviewed engineers. Of this sample, 75% were documented in models, structured text, or informal documentation, whereas 47% of all documented concerns were modeled. The paper's conclusion is that current modeling languages and methods inadequately address the full set of concerns that are important to engineers in base station development.
|
|
| 16. |
- Pareto, Lars, 1966, et al.
(author)
-
Concern Visibility in Base Station Development - an Empirical Investigation
- 2009
-
In: Andy Schuerr, Bran Selic (Eds): Model Driven Engineering Languages and Systems, 12th International Conference, MODELS 2009, Denver, Colorado, USA, Proceedings. Lecture Notes in Computer Science 5795,Springer Verlag (2009). ; LNCS 5975
-
Conference paper (peer-reviewed)abstract
- Contemporary model driven development tools only partially support the abstractions occurring in complex embedded systems development. The paper presents an interpretive case study in which the concerns held by 7 engineers in a large product developing organization were compared to the concerns supported by modeling tools in use. The paper’s main finding is an empirically grounded catalogue of concerns, categorized with respect to visibility in models and other artefacts in use. In the studied case, 26% of the concerns were visible in the models, whereas 38% were visible elsewhere and 36% not visible at all. The catalogue has been presented to several stakeholders in the unit studied, with positive feedback: particularly appreciated were the notion of concern visibility as indicator of degree of implementation of model driven development, and that concerns have traceable connections to experiences of the unit’s engineers.
|
|
| 17. |
- Pareto, Lars, 1966
(author)
-
Design Abstraction of Formal Requirement Models within the Unified Modeling Language
- 2005
-
In: Fifth Conference on Software Engineering Research and Practice in Sweden (SERPS2005).
-
Conference paper (peer-reviewed)abstract
- Design abstraction is a method to reduce state space sizes of software verification models; it allows also large software models to be verified. Design abstraction has long been used in conjunction with text-based approaches to software modeling and verification. Its use together with graphical such approaches is less common: most graphical modeling notations provide weaker support for design abstraction than text based notations do. This makes verification of large graphical models more difficult than verification of large text-based models. This paper shows how the graphical software modeling notation UML may be used to express some of the design abstractions that arise when large UML requirement models are subject to formal verification. The paper presents a dialect of UML to support design abstractions and exemplifies its use for requirements modeling of an embedded systems specification.
|
|
| 18. |
- Pareto, Lars, 1966, et al.
(author)
-
Ontology guided evolution of complex embedded systems projects in the direction of MDA
- 2008
-
In: Proceedings of the 11th International Conference on Model Driven Engineering Languages and Systems, MoDELS 2008, Toulouse, France, September 28 - October 3, 2008, Lecture Notes in Computer Science (LNCS). - 9783540878742 ; 5301, s. 874-888
-
Conference paper (peer-reviewed)abstract
- Implementation of MDA in large, product developing organizations involves changing processes, practices, tools, and communication infrastructures. The paper presents a case study, in which modeling related needs of a unit within Ericsson were compared to features of current and envisioned MDA tools, using qualitative methods. The paper’s main contribution is an ontology defining areas and sub-areas of improvement associated with the introduction of MDA in complex embedded systems projects. The ontology is grounded in interviews with senior modellers at Ericsson and in survey publications from within the field of MDA. It identifies 26 improvement areas concerned with model content, modeling activities, and the management of modeling projects. The ontology has been presented to stakeholders within the unit studied, with positive feedback: appreciated were its groundedness, traceability, holistic scope, and potential as platform and checklist for several recurrent analysis and communication tasks related to software process improvement within Ericsson.
|
|
| 19. |
- Pareto, Lars, 1966, et al.
(author)
-
Prioritizing Architectural Concerns
- 2011
-
In: Software Architecture (WICSA), 2011 9th Working IEEE/IFIP Conference on. 20-24 June 2011, Boulder, Colorado, USA.. - 9781612843995 ; , s. 22-31
-
Conference paper (peer-reviewed)abstract
- Efficient architecture work involves balancing the degree of architectural documentation with attention to needs, costs, agility and other factors. This paper presents a method for prioritizing architectural concerns in the presence of heterogeneous stakeholder groups in large organizations that need to evolve existing architecture. The method involves enquiry, analysis, and deliberation using collaborative and analytical techniques. Method outcomes are action principles directed to managers and improvement advice directed to architects along with evidence for recommendations made. The method results from 3 years of action research at Ericsson AB with the purpose of adding missing views to architectural documentation and removing superfluous ones. It is illustrated on a case where 29 senior engineers and managers within Ericsson prioritized 37 architectural concerns areas to arrive at 8 action principles, 5 prioritized improvement areas, and 24 improvement suggestions. Feedback from the organization is that the method has been effective in prioritizing architectural concerns, that data collection and analysis is more extensive compared to traditional prioritization practices, but that extensive analysis seems inevitable in architecture improvement work.
|
|
| 20. |
|
|
| 21. |
- Pareto, Lars, 1966, et al.
(author)
-
Strategic software process improvement by technology roadmapping
- 2008
-
In: Proceedings of the Nordic Workshop on Model Driven Engineering NW-MoDE 2008 Reykjavík, Iceland 20-22 August, 2008, Engineering Research Institute, University of Iceland.. - 9789979704836 ; , s. 145-159
-
Conference paper (peer-reviewed)abstract
- Technology roadmapping is a well known technique for knowledge building in the context of strategic product development, recently being applied also in the context of organizational development. This paper presents experiences from using roadmapping to support software process improvement work at one Ericsson unit; the unit develops embedded software for telecom network products, and seeks to improve its ability to assess and utilize emerging techniques for model based software engineering. The paper explores roadmapping and two other knowledge building techniques (grounded theory and maturity assessment) found to be valuable supplements to roadmapping in certain situations. The approach has been well received by the unit: appreciated features are that (1) the roadmap is grounded in data sources describing internal needs and technological options, and (2) that it provides a common knowledge base on top of which focused analyses may be built. The paper’s main ontribution is a set of action principles for knowledge building in the context of software process improvement.
|
|
| 22. |
|
|
| 23. |
- Pareto, Lars, 1966
(author)
-
Types for Crash Preventionn
- 2000
-
Doctoral thesis (other academic/artistic)abstract
- This thesis seeks to strengthen the capabilities of static polymorphic type-checking (as known from typed lambda calculus and functional programming) to allow a larger class of programming errors to be caught at compile time: the goal is to not only prevent illegal uses of data, but to also errors that lead to busy-loops, deadlocks, stack-overflows and heap-overflows. The thesis exploits that, for recursive programs, many correctness properties (including freedom from errors leading to busy-loops, etc.) can be showed by induction. By the introduction of a type-based induction principle built-into the type inference rule for recursive functions, and by the definition of type systems to support its use, the desired strengthenings are achieved. The method is limited to certain programming styles: it assumes the use of recursive programming techniques, and process interaction in synchronous data-flow style. The thesis explores these styles for soft real-time embedded programming - a field in which prevention of run-time crashes is an issue, and in which type-based crash-prevention techniques would complement the traditional techniques of the field, i.e., formal methods and testing. The thesis contributes with two experimental language designs that each presents a strengthening of Milner and Damas's type-system: one higher-order, functional language with lazy semantics and implicit storage management, and in which well-typed programs dot not busy-loop, nor deadlock; one first-order, functional language with strict semantics and explicit storage management, and in which well-typed programs do not run out of stack-space, nor heap-space. It contributes with two semantic theories that are used to prove the correctness of the stronger type systems: one denotational theory in which crashing programs are viewed as `bottom', in which types excluding this value can be expressed, and in which recursive functions can be shown to be total mappings on such types by fix-point induction; one operational theory, in which a typed abstract machine is used to show that well-typed programs do not get stuck along a chain of reductions, and that a machine-configuration's stack and store never exceed bounds stated in its type. It contributes with a type checking algorithm for the first of the two type-systems.
|
|
| 24. |
- Sandberg, Anna, et al.
(author)
-
Agile Collaborative Research: Action Principles for Industry-Academia Collaboration
- 2011
-
In: IEEE Software. - 0740-7459 .- 1937-4194. ; 28:4, s. 74-83
-
Journal article (peer-reviewed)abstract
- Both the software industry and academia promote collaboration to solve challenges together that neither can solve alone. Collaboration brings opportunities to understand and improve in ways not possible when working apart, but it succeeds only if both parties are contributing. A collaboration model developed from eight years' experience setting up and managing a research center explicitly focused on industry needs is based on five success factors enabling research results (need orientation, industry goal alignment, deployment impact, industry benefit, and innovativeness), five success factors enabling research activities (management engagement, network access, collaborator match, communication ability, and continuity), and 10 action principles for industry-academia collaboration management.
|
|
| 25. |
- Sjösten-Andersson, Erik, et al.
(author)
-
Costs and Benefits of Structure-aware Capture/Replay tools for Graphical User Interface Testing
- 2006
-
In: Proceedings of the Sixth Conference on Software Engineering Research and Practice in Sweden (SERPS06).
-
Conference paper (peer-reviewed)abstract
- Manual regression testing of graphical user interfaces is a time consuming task that a family of tools known as capture/replay tools seeks to automate. This paper presents a case study that compares the costs and benefits of a state of the art capture/replay tool (Rational Functional Tester) to the costs and benefits of manual regression testing. Our findings suggest that, for projects with infrequent product releases, manual regression testing of graphical user interfaces is more cost effective than testing with capture/replay tools.
|
|
| 26. |
- Zhu, Xi, 1987, et al.
(author)
-
An industrial case study on using language workbench technology for realizing model-driven engineering
- 2014
-
In: MODELSWARD 2014 - Proceedings of the 2nd International Conference on Model-Driven Engineering and Software Development. - Lisbon : SciTePress. - 9789897580079
-
Conference paper (peer-reviewed)abstract
- Model Driven Engineering (MDE) is a proven approach to improve software development processes by automation. However, traditional development of MDE tooling requires a high upfront cost. Recent developments in language workbench technologies promise to significantly reduce these investment costs. By providing domain experts with targeted projections, the speed and quality of delivering customer value is improved. This paper provides results from an industrial case study in the telecommunications domain and compares the value of using a language workbench to traditional MDE technologies. Evaluation of the approach was based on qualitative research strategy which involved a proof of concept implementation and effort estimations by tooling experts. Our results, using the Intentional Domain Workbench, indicate that applying a language workbench promises significant improvements in several aspects of MDE based software development. Most notably in this paper: (1) improved speed in development of domain specific tooling and (2) improved speed in software development process re-engineering.
|
|
