Software business : A short history and trends for the future

During its 70 years of existence, the software business has been following an evolution curve that can be considered typical for several fields of industrial businesses. Technological breakthroughs and innovations are typically seen as enablers for business evolution in the domain of technology and innovation management. Software, data collection, and data analysis represent a greater and greater part of the value of products and services, and today, their role is also becoming essential in more traditional fields. This, however, requires business and technology competences that traditional industries do not have. The transformation also enables new ways of doing business and opens the field for new kinds of players. Together, all this leads to transformation and new possibilities for the software industry. In this paper we study the overall trajectory of the software business, and then offer some viewpoints on the change in different elements of business models. Copyright © by the paper's authors. Copying permitted only for private and academic purposes.Peer reviewe

Towards practical typology of energy communities : main differentiating elements and examples of promising implementations

publishedVersionPeer reviewe

Based Round-Trip Engineering

presentations, which were organized into three sessions: From Interaction Diagrams to State Machines, Forwar

6Aika:Tulevaisuuden toimijariippumaton dataintegraatioalusta (CityIoT). Vaatimusmäärittely V1.00 FIN

Tiivistelmä Määrittely perustuu Oulussa pidettyyn työpajaan, Webpropol kyselyyn sekä Tampereen SmartCity projektin vaatimuksiin. Documentissa esitellyt vaatimukset painottuvat dataalustaan ja datan keräämiseen sillä nämä ovat CityIoT-projektin ytimessä. Muut IoT järjestelmiin liittyvät vaatimukset on rajattu tämän dokumentin ulkopuolelle. Projektisuunnitelman mukaisesti tätä dokumenttia päivitetään säännöllisesti projektin aikana. Projektin löydökset, kokemukset ja sidosryhmien palaute tulee vaikuttamaan dokumentin sisältöön. Kommentit tähän dokumenttiin ovat tervetulleita ja pyydetään lähettämään osoitteeseen [email protected]

Representing Embedded System Sequence Diagrams As A Formal Language

Sequence Diagrams (SDs) have proven useful for describing transaction-oriented systems, and can form a basis for creating statecharts

Information needs and presentation in agile software development

Abstract Context: Agile software companies applying the DevOps approach require collaboration and information sharing between practitioners in various roles to produce value. Adopting new development practices affects how practitioners collaborate, requiring companies to form a closer connection between business strategy and software development. However, the types of information management, sales, and development needed to plan, evaluate features, and reconcile their expectations with each other need to be clarified. Objective: To support practitioners in collaborating and realizing changes to their practices, we investigated what information is needed and how it should be represented to support different stakeholders in their tasks. Compared to earlier research, we adopted a holistic approach – by including practitioners throughout the development process – to better understand the information needs from a broader viewpoint. Method: We conducted six workshops and 12 semi-structured interviews at three Finnish small and medium-sized enterprises from different software domains. Thematic analysis was used to identify information-related issues and information and visualization needs for daily tasks. Three themes were constructed as the result of our analysis. Results: Visual information representation catalyzes stakeholder discussion, and supporting information exchange between stakeholder groups is vital for efficient collaboration in software product development. Additionally, user-centric data collection practices are needed to understand how software products are used and to support practitioners’ daily information needs. We also found that a passive way of representing information, such as a dashboard that would disturb practitioners only when attention is needed, was preferred for daily information needs. Conclusion: The software engineering community should consider reviewing the information needs of practitioners from a more holistic view to better understand how tooling support can benefit information exchange between stakeholder groups when making product development decisions and how those tools should be built to accommodate different stakeholder views

Towards stakeholder specific visualization of learning paths in software engineering teaching

Abstract In software engineering and other technology related teaching educators increasingly integrate defacto online tools into coursework. However, the impact of using these tools is not clearly understood. To this end, this research project will provide a visual dashboard with extensive and stakeholderspecific visualizations to serve the diverse needs of different stakeholders, e.g., teachers, teaching assistants, administrative personnel and students. This paper reports the results of our initial analysis of what kind of views teachers want to take to their courses and what kind of information teachers see as valuable visualizations on learners’ progress. We conducted 17 semi-structured interviews in two universities. The interviews were thematically analysed, giving as results three key themes. The results give a good starting point to create a visual course dashboard. Our study takes a step towards supporting various stakeholders in learning environments through visual means. While the input data, metrics and visualizations are based on the tools used in software engineering courses, we see that several results can be applied to other contexts

Roadmapper:a tool for supporting communication in software product roadmapping

Abstract Software product roadmaps are practical tools that provide direction for product development. Software product roadmapping combines the reasoning why something is done with what should be done, often in the form of items to be delivered when constructing a software product. Successful roadmapping activities require collaboration from multiple stakeholder groups, such as business, development and management. However, aligning company goals, business strategy and development efforts is far from trivial. To this end, we conducted an action research study investigating how information exchange should be supported in software product roadmapping. As our results, we contribute the open-sourced Roadmapper tool and provide insights on how information exchange should be supported in software product roadmapping. Roadmapper supports information exchange in software product roadmapping by allowing different parties to clarify their views and making them understandable to other stakeholders, facilitating the discussion when they meet. Thus, Roadmapper visualises a common situational picture of software product development and acts as a group memory — helping to remember what the other stakeholders think about the matter

Free innovation environments: lessons learned from the software factory Initiatives

Entrepreneurs and Small and Medium Enterprises usually have issues on developing new prototypes, new ideas or testing new techniques. In order to help them, in the last years, academic Software Factories, a new concept of collaboration among universities and companies has been developed. Software Factories provide a unique environment for students and companies. Students benefit from the possibility of working in a real work environment learning how to apply the state of the art of the existing techniques and showing their skills to entrepreneurs. Companies benefit from the risk-free environment where they can develop new ideas, in a protected environment. Universities, finally benefit from this setup as a perfect environment for empirical studies in industrial-like environment. In this paper, we present the network of academic Software Factories in Europe, showing how Companies had already benefit from existing Software Factories and reporting success stories. The results of this paper can increase the network of the factories and help other universities and companies to setup similar environment to boost the local economy