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

publishedVersionPeer reviewe

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]

and future trends

Empirical studies in reverse engineering: state of the ar

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