1. IT-Universitetet i København Rued Langgaardsvej 7 DK-2300 København S Software Engineering Beyond the Project Yvonne Dittrich IT-University in Copenhagen Software Development Group

2. IT-Universitetet i København Rued Langgaardsvej 7 DK-2300 København S Roadmap  What is a project in software engineering?  Examples of software development practice  Inhouse software development at a telecommunications provider  Product development I: a booking system for municipalities  Product developement II: communication between municipalities and citizens  Product development III: GUI framework for high-end mobile phone  What are the challenges for software engineering?  And back to the ESP network.

3. IT-Universitetet i København Rued Langgaardsvej 7 DK-2300 København S ‘A project is a managed set of interrelated resources that delivers one or more products to a customer or end user. It has a beginning and an end and typically operates according to a plan. A project can be composed of projects.’ Definition from the ©CMMI What is a ‘Project’?

4. IT-Universitetet i København Rued Langgaardsvej 7 DK-2300 København S A ‘Project’...  is regarded as opposite of routine work.  has the goal to develop a product.  requires different expertises.  requires coordination of sub tasks.  has to cope with limited expertise, budget and time.

5. IT-Universitetet i København Rued Langgaardsvej 7 DK-2300 København S What is problematic with the SE perspective on software projects?  Projects are regarded as closed units that should only have controlled interfaces to the rest of the world.  The influences from the environment is regarded as disturbance.  They are organised disregarding history and future.

6. IT-Universitetet i København Rued Langgaardsvej 7 DK-2300 København S Inhouse software development at a telecommunications provider  Participants: a telecommunication provider, a small software developer and the university  Case: a business application to administrate contracts and compute payments based on the contracts and triggered by certain events  Context: rapidly changing business practices require a flexible adaptable system

7. IT-Universitetet i København Rued Langgaardsvej 7 DK-2300 København S ‘Beyond the project’  Developers and users cooperate in the projects, in some cases since several years.  The history of the systems relevant for the state of affairs and future development.  Developers are responsible for maintenance as well.  The individual programs are part of a complex infrastructure. The development has to be coordinated across the infrastructure.  The discussed system is already the 2nd version, the need to develop a new version is already on the horizon.

8. IT-Universitetet i København Rued Langgaardsvej 7 DK-2300 København S Product development I: booking systems for municipalities  Participatory Design in the wild: the one-stop shop designs the IT infrastructure  ’The Designers? That’s us!’  Who is designing what, when for whom?  shifting foci of design  no clearly cut projects, but a diversity of interlaced practices of design and use  flexibilisation of software processes

9. IT-Universitetet i København Rued Langgaardsvej 7 DK-2300 København S Looking at ’the best’ software provider  a 5 person company selling an off-the-shelf booking system:  using the support line to collect feed back and improvement proposals  user meetings for the same purpose and to develop a community of mutually supportive users  recruiting pilot users for major changes  ca 20 releases/year for error fixes and small improvements.

10. IT-Universitetet i København Rued Langgaardsvej 7 DK-2300 København S Beyond the Project  Where is the project gone?  Continuous development in tight reaction to the issues raised via the support line.  Developments in the use context can be accommodated rapidly by the development.

11. IT-Universitetet i København Rued Langgaardsvej 7 DK-2300 København S Product development II: citizen participation via internet  Again a small software provider who develops mainly for municipalities  Because of recurring requirements the software was split into a number of configurable modules that can easily be plugged together.  And again: an agile development practice.

12. IT-Universitetet i København Rued Langgaardsvej 7 DK-2300 København S Beyond the Project  Implementing agile development principles, the projects are closely coordinated with the developing requirements of the customer.  The product is based on configurable modules. Conversely, the projects motivate the further development of new modules.  Domain specific expertise developed of years and projects is the the base for each specific project.

13. IT-Universitetet i København Rued Langgaardsvej 7 DK-2300 København S Product development III: UI-framework for high end mobile phones  The development of the framework takes place parallel and through application development for owners and customers.  Through these projects, expertise regarding technical areas and also interaction design is developed and maintained through the different projects.  E.g. the interaction design group built up and maintains contact to a network of pilot users that is used to recruit participants for usability tests, focus groups and field studies.

14. IT-Universitetet i København Rued Langgaardsvej 7 DK-2300 København S Beyond the Project  Expertise is not developed for a specific project or product but related to a technical or design domain.  The product is split in a general framework part and a application specific part.  In and though each project both levels are developed.  Expertise regarding domain and methods as well as the necessary infrastructure is developed to support a serious of development projects.

15. IT-Universitetet i København Rued Langgaardsvej 7 DK-2300 København S Summing up  ‘The project’ is a social construct to isolate part of an ongoing interlace of different development activities in order to better control that part.  Projects therefore should be explicitly coordinated with parallel developments and take the history and the future development into account.  Software products are developed and in layers - this layered development has to be supported by the technical design.  The development on the different layers has to be coordinated.

16. IT-Universitetet i København Rued Langgaardsvej 7 DK-2300 København S Related Work  Software Evolution (Lehmann)  framework based development, domain analysis, generative programming, programming language technology  product line architecture, variability management  End-User Development, End-User tailoring  agile software development  software development as co-operative work, knowledge management But…

17. IT-Universitetet i København Rued Langgaardsvej 7 DK-2300 København S Back to the ESP-Network  What kinds of techniques are applicable for what kinds of software products?  How to coordinate development on different levels and in different contexts methodologically and technically?  How to communicate design rationale across several cycles of evolution.  What are the implications for software development processes and methods?

18. IT-Universitetet i København Rued Langgaardsvej 7 DK-2300 København S The presentation is based on: Y. Dittrich, O. Lindeberg Designing for Changing Work and Business Practices. In: N. Patel (ed.) Evolutionary and Adaptive Information Systems, Idea: 2003. Y. Dittrich, O. Lindeberg How use-oriented development can take place. Organising Software Development to allow for User-Developer Co-operation. Information and Software Technology 46 (2004), No. 9, pp. 603-617. Y. Dittrich, S. Eriksén, C. Hansson PD in the Wild: Evolving Practices of Design in Use. PDC 2002, Malmö, Sweden. C. Hansson, Y. Dittrich, D. Randall How to Include Users in the Development of Off-the- Shelf Software: A Case for Comple-menting Participatory Design with Agile Development. HICCS, January 4-7th 2006. C. Hansson, Y. Dittrich, B. Gustafsson, S.Zarnak How Agile are Industrial Software Development Practices? Accepted by the Journal of Systems and Software. K. Rönkkö, B. Kilander, M. Hellman, Y. Dittrich Personas is not Applicable: Local Remedies Interpreted in a Wider Context. PDC 2004, Toronto, July 27 - 31, 2004. Y. Dittrich Doing Empirical Research in Software Engineering – finding a path between understanding, intervention and method development. In: Y. Dittrich, Chr. Floyd, R. Klischewski (eds.) Social thinking – Software practice. MIT Press: 2002.