| 1. |
- Börjesson, Anna, et al.
(författare)
-
Continuing Professional Development by Practitioner Integrated LearningContinuing Professional Development by Practitioner Integrated Learning
- 2007
-
Ingår i: OOPSLA - Object-Oriented Programing Languages.
-
Konferensbidrag (refereegranskat)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. |
- Pareto, Lars, 1966, et al.
(författare)
-
A Quality Model for Design Documentation in Model-centric Projects
- 2006
-
Ingår i: Proceedings of the Third International Workshop on Software Quality Assurance (SOQUA 2006), Portland, Oregon, USA.
-
Konferensbidrag (refereegranskat)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.
|
|
| 3. |
- Pareto, Lars, 1966, et al.
(författare)
-
Concern Visibility in Base Station Development - an Empirical Investigation
- 2009
-
Ingår i: 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
-
Konferensbidrag (refereegranskat)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.
|
|
| 4. |
- Pareto, Lars, 1966
(författare)
-
Design Abstraction of Formal Requirement Models within the Unified Modeling Language
- 2005
-
Ingår i: Fifth Conference on Software Engineering Research and Practice in Sweden (SERPS2005).
-
Konferensbidrag (refereegranskat)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.
|
|
| 5. |
- Pareto, Lars, 1966, et al.
(författare)
-
Ontology guided evolution of complex embedded systems projects in the direction of MDA
- 2008
-
Ingår i: 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
-
Konferensbidrag (refereegranskat)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.
|
|
| 6. |
- Pareto, Lars, 1966
(författare)
-
Requirements modeling within iterative, incremental processes
- 2005
-
Ingår i: Proceedings of the third ACM-IEEE International Conference on Formal Methods and Models for Codesign (MEMOCODE'05), 11-14 July, 2005, Verona. ; , s. 249-250
-
Konferensbidrag (övrigt vetenskapligt/konstnärligt)
|
|
| 7. |
- Pareto, Lars, 1966, et al.
(författare)
-
Strategic software process improvement by technology roadmapping
- 2008
-
Ingår i: 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
-
Konferensbidrag (refereegranskat)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.
|
|
| 8. |
|
|
| 9. |
- Sjösten-Andersson, Erik, et al.
(författare)
-
Costs and Benefits of Structure-aware Capture/Replay tools for Graphical User Interface Testing
- 2006
-
Ingår i: Proceedings of the Sixth Conference on Software Engineering Research and Practice in Sweden (SERPS06).
-
Konferensbidrag (refereegranskat)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.
|
|
