Oplægget blev holdt ved et seminar i InfinIT-interessegruppen Softwaretest den 26. maj 2009.
Læs mere om interessegruppen på http://www.infinit.dk/dk/interessegrupper/softwaretest/softwaretest.htm
Oplægget blev holdt ved et seminar i interessegruppen Softwaretest, der blev afholdt den 4. juni 2013. Læs mere om arrangementet her: http://www.infinit.dk/dk/arrangementer/tidligere_arrangementer/seminar_i_interessegruppen_softwaretest_02.htm
The document discusses different approaches to representing ideas and problems when developing software systems, including icons, prototypes, metaphors, and propositions. It uses the example of developing a wearable technology system called "Psyche" to monitor the mental health of patients. The team developing Psyche considers representing the problem using each of the four approaches to help define key objects, events, and qualities to address. They choose to use an icon representation focused on timely response to emerging conditions and problem identification for citizens.
The document summarizes an experience report on modelling and simulating railway emergency response plans. It discusses using declarative process models and collaborative simulation to study how emergency plans may be impacted by combined physical and cyber attacks. Key steps involved collaboratively mapping out emergency response procedures with experts, and then simulating scenarios using the process model to explore vulnerabilities and make recommendations. The approach was tested on a case study of the Great Belt Bridge incident, and conclusions were that collaborative mapping and simulation is a viable way to study cyber-physical vulnerabilities in critical infrastructure.
Oplægget blev holdt ved et seminar i InfinIT-interessegruppen Softwaretest den 26. maj 2009.
Læs mere om interessegruppen på http://www.infinit.dk/dk/interessegrupper/softwaretest/softwaretest.htm
Oplægget blev holdt ved et seminar i interessegruppen Softwaretest, der blev afholdt den 4. juni 2013. Læs mere om arrangementet her: http://www.infinit.dk/dk/arrangementer/tidligere_arrangementer/seminar_i_interessegruppen_softwaretest_02.htm
The document discusses different approaches to representing ideas and problems when developing software systems, including icons, prototypes, metaphors, and propositions. It uses the example of developing a wearable technology system called "Psyche" to monitor the mental health of patients. The team developing Psyche considers representing the problem using each of the four approaches to help define key objects, events, and qualities to address. They choose to use an icon representation focused on timely response to emerging conditions and problem identification for citizens.
The document summarizes an experience report on modelling and simulating railway emergency response plans. It discusses using declarative process models and collaborative simulation to study how emergency plans may be impacted by combined physical and cyber attacks. Key steps involved collaboratively mapping out emergency response procedures with experts, and then simulating scenarios using the process model to explore vulnerabilities and make recommendations. The approach was tested on a case study of the Great Belt Bridge incident, and conclusions were that collaborative mapping and simulation is a viable way to study cyber-physical vulnerabilities in critical infrastructure.
The document discusses using gamification to support digitalization and process orientation. It describes a workshop to discuss how gamification could be used when processes must be described and maintained, and tasks completed by people. Examples are provided of using gamification in business process management. The document also summarizes a case from Switzerland on using a combined approach of user-centered design and gamification for an e-government process sharing portal. It concludes that virtual rewards in gamification must be meaningful, and the needs and goals of different users must be understood.
Fra seminar om softwareudvikling og softwareteams den 25. november 2014
http://www.infinit.dk/dk/arrangementer/tidligere_arrangementer/seminar_om_softwareudvikling_of_softwareteams.htm
The document discusses processes at Nykredit, a Danish bank. It notes that processes have become more complex over time as the bank has expanded. Historically, process work focused on internal optimization but now there is increased focus on customers. The bank is working to improve digitization of processes to reduce costs and create more self-service options for customers. There is a shift towards considering processes from an "outside-in" perspective that understands customers' contexts rather than just optimizing internally. Developing the right competencies is important, such as using methods like customer journeys to design processes around customer experiences instead of just internal mapping.
The document discusses flexible process digitization. It provides background on the speaker, Thomas Hildebrandt, including his educational background and research experience in business process management (BPM) and digitization of workflows. The presentation covers the history of efforts to digitize processes going back to the 1970s, standards that have been developed, and challenges with traditional flow chart representations of processes. It introduces process-oriented architecture and notes the need for improved support for process diagnosis, design, and flexibility.
The document discusses a project to develop a software system called Psyche to help improve the quality of life for people with acute depression. The system would use data from a user's digital diary, questionnaire responses and sensors to try to anticipate depressive periods and alleviate symptoms. An initial configuration table is presented outlining the project vision, key elements, components, scenarios and features. Reviews find that while anticipation works, detection and alleviation measures are inadequate and need improvement to better fit the user's individual context.
(1) Intrapreneurship refers to entrepreneurial behavior within existing organizations that leads to innovations such as new products, services, and ventures. It involves stretching organizational boundaries.
(2) The document defines intrapreneurship and differentiates it from related concepts like diversification, capabilities, organizational learning, and innovation.
(3) Intrapreneurship is described as a multidimensional concept involving eight dimensions: new ventures, new businesses, product/service innovativeness, process innovativeness, self-renewal, risk taking, proactiveness, and competitive aggressiveness.
The document discusses software engineering and development approaches at AAU, including:
1. Several bachelor's and master's programs are mentioned, including computer science, software engineering, and interaction design.
2. The curriculum for the bachelor's and master's programs in computer science and software engineering is outlined, including required courses and projects in various topics.
3. An overview is given of agile and plan-driven software development approaches, along with readings and method comparisons. Key differences between the approaches are discussed.
This document discusses development processes when using external providers and addresses several questions:
1. It provides an overview of development processes based on ISO 15504 and shows how external providers in different locations are managed and coordinated on a daily basis.
2. It includes a checklist of important aspects to consider in relationships with external providers such as management setup, requirements, documentation, development frameworks, and meeting frequency.
3. It discusses ensuring the competence and maturity levels of external providers through assessments, process reviews, and comparing their processes to standards like ISO 15504 and CMMI.
This document discusses challenges with hardware-near programming and proposes solutions like object-oriented design, test-driven development, and mocking hardware for testing in C. It provides examples of encapsulating hardware registers in C and writing tests that check register values and function outputs without the physical hardware. The document concludes that while setting up the tools is an initial investment, TDD is possible and helps create safe, maintainable low-level software.
The document discusses using gamification to support digitalization and process orientation. It describes a workshop to discuss how gamification could be used when processes must be described and maintained, and tasks completed by people. Examples are provided of using gamification in business process management. The document also summarizes a case from Switzerland on using a combined approach of user-centered design and gamification for an e-government process sharing portal. It concludes that virtual rewards in gamification must be meaningful, and the needs and goals of different users must be understood.
Fra seminar om softwareudvikling og softwareteams den 25. november 2014
http://www.infinit.dk/dk/arrangementer/tidligere_arrangementer/seminar_om_softwareudvikling_of_softwareteams.htm
The document discusses processes at Nykredit, a Danish bank. It notes that processes have become more complex over time as the bank has expanded. Historically, process work focused on internal optimization but now there is increased focus on customers. The bank is working to improve digitization of processes to reduce costs and create more self-service options for customers. There is a shift towards considering processes from an "outside-in" perspective that understands customers' contexts rather than just optimizing internally. Developing the right competencies is important, such as using methods like customer journeys to design processes around customer experiences instead of just internal mapping.
The document discusses flexible process digitization. It provides background on the speaker, Thomas Hildebrandt, including his educational background and research experience in business process management (BPM) and digitization of workflows. The presentation covers the history of efforts to digitize processes going back to the 1970s, standards that have been developed, and challenges with traditional flow chart representations of processes. It introduces process-oriented architecture and notes the need for improved support for process diagnosis, design, and flexibility.
The document discusses a project to develop a software system called Psyche to help improve the quality of life for people with acute depression. The system would use data from a user's digital diary, questionnaire responses and sensors to try to anticipate depressive periods and alleviate symptoms. An initial configuration table is presented outlining the project vision, key elements, components, scenarios and features. Reviews find that while anticipation works, detection and alleviation measures are inadequate and need improvement to better fit the user's individual context.
(1) Intrapreneurship refers to entrepreneurial behavior within existing organizations that leads to innovations such as new products, services, and ventures. It involves stretching organizational boundaries.
(2) The document defines intrapreneurship and differentiates it from related concepts like diversification, capabilities, organizational learning, and innovation.
(3) Intrapreneurship is described as a multidimensional concept involving eight dimensions: new ventures, new businesses, product/service innovativeness, process innovativeness, self-renewal, risk taking, proactiveness, and competitive aggressiveness.
The document discusses software engineering and development approaches at AAU, including:
1. Several bachelor's and master's programs are mentioned, including computer science, software engineering, and interaction design.
2. The curriculum for the bachelor's and master's programs in computer science and software engineering is outlined, including required courses and projects in various topics.
3. An overview is given of agile and plan-driven software development approaches, along with readings and method comparisons. Key differences between the approaches are discussed.
This document discusses development processes when using external providers and addresses several questions:
1. It provides an overview of development processes based on ISO 15504 and shows how external providers in different locations are managed and coordinated on a daily basis.
2. It includes a checklist of important aspects to consider in relationships with external providers such as management setup, requirements, documentation, development frameworks, and meeting frequency.
3. It discusses ensuring the competence and maturity levels of external providers through assessments, process reviews, and comparing their processes to standards like ISO 15504 and CMMI.
This document discusses challenges with hardware-near programming and proposes solutions like object-oriented design, test-driven development, and mocking hardware for testing in C. It provides examples of encapsulating hardware registers in C and writing tests that check register values and function outputs without the physical hardware. The document concludes that while setting up the tools is an initial investment, TDD is possible and helps create safe, maintainable low-level software.
This document summarizes an embedded software project that used object-oriented modeling and design with UML, along with Safety-Critical Java and C programming. A team of students created a model car that could be remotely controlled via an app. The project followed an object-oriented development process, including use case modeling, component diagrams, and testing of components using mock objects. The design included a layered architecture with hardware abstraction and platform abstraction layers. Missions in Safety-Critical Java were used to model different car modes like Park and Drive. Unit testing of components and testing on the execution platform helped evaluate memory usage and schedulability. The document concludes that this approach helped manage complexity in the embedded system.
The document summarizes a company's conversion of its embedded controller software from C to C++ over a two month period. It involved converting 8 projects with 30% shared code across 18 developers. Challenges included converting callbacks and dealing with scripting errors. Opportunities included improving code quality, team building, and evaluating new static analysis tools. The conversion was successful with minimal performance impacts and many bugs were found and fixed during the process. Future plans include C++ training and refactoring code to fully utilize C++ features.
This document discusses embedded Linux development from a manager's perspective. It provides the speaker's background working with C and C++ on embedded systems. Key expectations of programming languages for embedded systems are outlined, including flexibility, low cost, and real-time performance. The document discusses why C is commonly used for embedded development and outlines best practices like code reviews when using C to avoid issues. It also discusses moving to C++ and using Linux for embedded projects.
The document discusses the C programming language. It provides some key facts about C:
- C was developed in the late 1960s and early 1970s by Dennis Ritchie at Bell Labs.
- C became popular due to its use in developing the UNIX operating system.
- The IT world widely uses C, as evidenced by its use in operating systems like Linux, Windows, and iOS.
- The C language has undergone standardization with standards published in 1989 (C89), 1999 (C99), 2011 (C11), and 2018 (C18).
- C influenced many other popular programming languages and remains one of the most widely used languages today.
The document discusses the evolution of industrial revolutions and key elements of Industry 4.0, including intelligent automation and production facilities, smart products, virtual production, and more. It also examines the increasing need for systems engineering as products and production become more complex. Finally, it outlines six key fields that must be mastered for successful digital transformation: usage, data, technology, process, role, and culture.
Emergent synthetic processes (ESP) is a new paradigm for implementing process changes without needing agreement from all participants. It works by having organizational members define service descriptions stating what tasks they are willing to do and under what conditions. Processes are then synthesized in real-time from these service descriptions for each specific case, finding the optimal route through the organization. This allows service descriptions and partially completed processes to be updated at any time without requiring agreement. ESP enables a more flexible and distributed approach to processes and workflow.
This document discusses the integration of DCR (Dynamic Case Resolution) with the KMD Workzone case management platform to enable more automated and adaptive case resolution. It envisions using technologies like machine learning, artificial intelligence, and automation to handle more routine case activities while still allowing for human judgment and deviations from standard workflows. The approach is described as evolutionary rather than revolutionary, breaking large changes into smaller, configurable steps and getting users involved to identify automatable activities and ensure the system meets their needs. Demostrations are provided of Workzone's flexible configuration capabilities and how DCR could be integrated to iteratively introduce more automated case resolution over time.
SupWiz is a spin-off from world-leading AI experts that develops omni-channel AI software to disrupt customer service and support. Their platform makes different customer service channels intelligent and links them together using techniques like intelligent virtual agents, knowledge management, and analytics. The platform integrates with infrastructure components and has been proven valuable at several customers, accurately answering questions and reducing response times. SupWiz aims to improve the customer experience throughout the entire journey with AI-powered solutions.
The document discusses NNIT's vision for its Service Support Center to improve user productivity through reducing demand for support. Key points include:
- Integrating all user interaction data across systems to create a single source of truth data warehouse for metrics and reporting.
- Implementing configuration management policies, SLA policies, and integrating different levels of knowledge and problem management to reduce support demand and minimize downtime.
- The goal is machine-learning enabled intelligent automation that is flexible, consistent and cost-efficient to provide support across channels like phone, chat, and with multi-language translation available 24/7 globally.
- Statistics are presented on ticket routing optimization using AI to reduce unnecessary ticket jumps between support agents.
This document discusses how natural language processing (NLP) can be used for customer support. It outlines several NLP applications for customer support like search, fraud detection, and translation. It also discusses how NLP can help answer previously unasked questions by generating questions from knowledge bases and documents. Finally, it proposes a "customer support Turing test" to evaluate NLP systems for their ability to fool classifiers that distinguish customer support agents from customers.
This document provides information about an AI conference on the future of customer service. The conference will feature presentations from leaders in various AI and data organizations, as well as a panel debate. Statistics are presented showing the growing importance and impact of AI and chatbots on customer service interactions and cost savings over the coming years. The AMAOS project from the University of Copenhagen is also introduced, which focuses on advanced machine learning for automated omni-channel customer support.
The document discusses a project aimed at improving quality of life for citizens with affective disorders like depression. It outlines a vision called "Psyche" that aims to anticipate and alleviate acute depression through a digital platform. A configuration table presents the rationale, strategy, and tactics for a prospect to realize this vision, including leveraging the user's digital diary and questionnaire responses to detect emerging depressive episodes and provide alleviation measures. The table identifies challenges like ineffective intervention and underused platform potential, noting that anticipation works but could be improved and alleviation measures are sometimes weak or misplaced.
Proof of Concept af en fleksibel løsning til små online møder
1. POC PÅ
SKYPE FOR BUSINESS
1 0 . M A RT S 2 0 1 6 1
I T S E RV I C E S
A A L B O R G U N I V E R S I T E T
2. • Videokonferenceprojekt (VK) med ønske om fleksible
online møder
• Ikke-supporteret Lync løsning
• Mangel på ressourcer i infrastruktur
BAGGRUND FOR POC
1 0 . M A RT S 2 0 1 6
I T S E RV I C E S
A A L B O R G U N I V E R S I T E T
3. • Afprøve om SfB kan erstatte (noget af) brugen af VK-
mødelokaler
• Afprøve underleverandør på ikke-kritisk system
• Teste udrulning til helt nye brugere
• Afprøve telefoni vis SfB
FORMÅL
1 0 . M A RT S 2 0 1 6
I T S E RV I C E S
A A L B O R G U N I V E R S I T E T
4. Kører PoC i 6 måneder
Ca 300 brugere
FORLØB
1 0 . M A RT S 2 0 1 6 4
I T S E RV I C E S
A A L B O R G U N I V E R S I T E T
Uge 7 Uge 10 Uge 13 Uge 15
Eksisterende brugere
Ny gruppe I
Ny gruppe II
Linux brugere
Mødelokaler
5. • To underleverandører som skulle fremstå som én
• Forsinkelse med installationer
• Tidsforbrug for AAU ITS
• Medarbejdere ønsker ikke outsourcing
• Mange platforme som skal supporteres
• Success og ”krav” om hurtig udbredelse
UDFORDRINGER
1 0 . M A RT S 2 0 1 6 5
I T S E RV I C E S
A A L B O R G U N I V E R S I T E T
6. Erfaring med:
• SfB på de forskellige platforme
• Processer for udrulning
• Udrulning til nye brugere
• Betydning for brug af dedikerede anlæg
• Internt tidsforbrug ved brug af underleverandør
• Support fra underleverandør
• Pris ved outsourcing vs indsats ved eget set-up
FORVENTET OUTPUT
1 0 . M A RT S 2 0 1 6 6
I T S E RV I C E S
A A L B O R G U N I V E R S I T E T
Editor's Notes
Husk kablet forbindelse når man skal præsentere.
Husk headset når snakker.
Kører dårlig hvis via citrix.
Undervisere som brugere – hvad hvis opkald i undervisning?
Er der nok båndbredde bagved hvis der er mange deltager og mange møder på én gang?
Timing i forhold til årsrul.