| 1. |
- Chaudron, Michel, 1969, et al.
(författare)
-
Proceedings of the 2nd Workshop on Experiences and Empirical Studies in Software Modelling
- 2012
-
Ingår i: Research Reports in Software Engineering and Management. - Göteborg : University of Gothenburg.
-
Konferensbidrag (övrigt vetenskapligt/konstnärligt)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.
|
|
| 2. |
- Martini, Antonio, 1982, et al.
(författare)
-
A Framework for Speeding Up Interactions Between Agile Teams and Other Parts of the Organization
- 2014
-
Ingår i: Continuous Software Engineering. - Cham : Springer. - 9783319112824 ; , s. 67-82
-
Bokkapitel (övrigt vetenskapligt/konstnärligt)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.
|
|
| 3. |
- Martini, Antonio, 1982, et al.
(författare)
-
Communication factors for speed and reuse in large-scale agile software development
- 2013
-
Ingår i: 17th International Software Product Line Conference, August 26-30, Tokyo, Japan. - New York, NY, USA : Association for Computing Machinery (ACM). - 9781450319683
-
Konferensbidrag (refereegranskat)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.
|
|
| 4. |
- Martini, Antonio, 1982, et al.
(författare)
-
Enablers and inhibitors for speed with reuse
- 2012
-
Ingår i: 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
-
Konferensbidrag (refereegranskat)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.
|
|
| 5. |
- Martini, Antonio, 1982, et al.
(författare)
-
Improving Businesses Success by Managing Interactions among Agile Teams in Large Organizations
- 2013
-
Ingår i: Lecture Notes in Business Information Processing. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1865-1356 .- 1865-1348. - 9783642393358 ; 150, s. 60-72
-
Konferensbidrag (refereegranskat)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.
|
|
| 6. |
- Martini, Antonio, 1982, et al.
(författare)
-
Role of Architects in Agile Organizations
- 2014
-
Ingår i: Continuous Software Engineering. - Cham : Springer. - 9783319112824 ; , s. 39-50
-
Bokkapitel (övrigt vetenskapligt/konstnärligt)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.
|
|
| 7. |
- Martini, Antonio, 1982, et al.
(författare)
-
Teams Interactions Hindering Short-Term and Long-Term Business Goals
- 2014
-
Ingår i: Continuous Software Engineering. - Cham : Springer. - 9783319112824 ; , s. 51-65
-
Bokkapitel (övrigt vetenskapligt/konstnärligt)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.
|
|
| 8. |
- Pareto, Lars, 1966, et al.
(författare)
-
Architectural Descriptions as Boundary Objects in System and Design Work
- 2010
-
Ingår i: 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
-
Konferensbidrag (refereegranskat)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.
|
|
| 9. |
- Pareto, Lars, 1966, et al.
(författare)
-
Collaborative Prioritization of Architectural Concerns
- 2012
-
Ingår i: Journal of Systems and Software. - : Elsevier BV. - 0164-1212. ; 85:9, s. 1971-1994
-
Tidskriftsartikel (refereegranskat)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.
|
|
| 10. |
- Pareto, Lars, 1966, et al.
(författare)
-
Concern coverage in base station development: an empirical investigation
- 2012
-
Ingår i: Software and Systems Modeling. - : Springer Science and Business Media LLC. - 1619-1366 .- 1619-1374. ; 11:3, s. 409-429
-
Tidskriftsartikel (refereegranskat)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.
|
|
| 11. |
- Pareto, Lars, 1966, et al.
(författare)
-
Prioritizing Architectural Concerns
- 2011
-
Ingår i: Software Architecture (WICSA), 2011 9th Working IEEE/IFIP Conference on. 20-24 June 2011, Boulder, Colorado, USA.. - 9781612843995 ; , s. 22-31
-
Konferensbidrag (refereegranskat)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.
|
|
| 12. |
- Sandberg, Anna, et al.
(författare)
-
Agile Collaborative Research: Action Principles for Industry-Academia Collaboration
- 2011
-
Ingår i: IEEE Software. - 0740-7459 .- 1937-4194. ; 28:4, s. 74-83
-
Tidskriftsartikel (refereegranskat)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.
|
|
| 13. |
- Zhu, Xi, 1987, et al.
(författare)
-
An industrial case study on using language workbench technology for realizing model-driven engineering
- 2014
-
Ingår i: MODELSWARD 2014 - Proceedings of the 2nd International Conference on Model-Driven Engineering and Software Development. - Lisbon : SciTePress. - 9789897580079
-
Konferensbidrag (refereegranskat)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.
|
|
