Conventional software engineering processes are rather transactional and lack a common theory for the involvement of users and their communities. Users are regarded as pure consumers, who are, at most, able to report issues. In the age of easy knowledge access and social media, discounting the users of software might threaten its success. Potentially valuable experiences and volunteered resources get lost. Frustrated users might even meet in social communities to argue against the software and harm its reputation.
The goal of this research is to revolutionize the role of users, dissolving the boundaries to software engineers. We propose a novel framework for increasing the software socialness, being the degree of user and community involvement in the software lifecycle. Our framework consists of a benchmark, a process, and a reference architecture. The benchmark includes metrics for assessing and monitoring software socialness. The process enables engineering teams to systematically gather and exploit user feedback in the software lifecycle. The context aware reference architecture integrates social media into software systems and the engineering infrastructure. It observes users’ interactions while they use the software and proactively collects in situ feedback.
(paper
Context aware software engineering and maintenance: the FastFix approachWalid Maalej
Context consists of all events which can be observed or interpreted. In knowledge work it includes the actions of the user, the reaction of the applications, and the artifacts concerned. In this talk, we introduce the FastFix approach to context-awareness in software engineering and maintenance. We show how context enables remote software maintenance, as well as a systematic involvement of end users in software evolution. We also discuss other applications of context including personal productivity management and knowledge sharing amongst developers. The main research challenges include the modeling, sensing, sessionization, aggregation, and comparison of context, as well as the protection of the user's privacy.
Mipaw: Model for a Progressive Implementation of Web Accessibility - Web4AllQelios
Our presentation of MIPAW at Web 4 All 2012.
MIPAW is a model for a possible strategy of gradual implementation of Web accessibility. It aims at providing a basis for project management methodologies relying on implementation phases, while remaining focused on essential users needs.
Context aware software engineering and maintenance: the FastFix approachWalid Maalej
Context consists of all events which can be observed or interpreted. In knowledge work it includes the actions of the user, the reaction of the applications, and the artifacts concerned. In this talk, we introduce the FastFix approach to context-awareness in software engineering and maintenance. We show how context enables remote software maintenance, as well as a systematic involvement of end users in software evolution. We also discuss other applications of context including personal productivity management and knowledge sharing amongst developers. The main research challenges include the modeling, sensing, sessionization, aggregation, and comparison of context, as well as the protection of the user's privacy.
Mipaw: Model for a Progressive Implementation of Web Accessibility - Web4AllQelios
Our presentation of MIPAW at Web 4 All 2012.
MIPAW is a model for a possible strategy of gradual implementation of Web accessibility. It aims at providing a basis for project management methodologies relying on implementation phases, while remaining focused on essential users needs.
How Do Users Like This Feature? A Fine Grained Sentiment Analysis of App Revi...Walid Maalej
App stores allow users to submit feedback for downloaded apps in form of star ratings and text reviews. Recent studies analyzed this feedback and found that it includes information useful for app developers, such as user requirements, ideas for improvements, user sentiments about specific features, and descriptions of experiences with these features. However, for many apps, the amount of reviews is too large to be processed manually and their quality varies largely. The star ratings are given to the whole app and developers do not have a mean to analyze the feedback for the single features. In this paper we propose an automated approach that helps developers filter, aggregate, and analyze user reviews. We use natural language processing techniques to identify fine-grained app features in the reviews. We then extract the user sentiments about the identified features and give them a general score across all reviews. Finally, we use topic modeling techniques to group fine- grained features into more meaningful high-level features. We evaluated our approach with 7 apps from the Apple App Store and Google Play Store and compared its results with a manually, peer-conducted analysis of the reviews. On average, our approach has a precision of 0.59 and a recall of 0.51. The extracted features were coherent and relevant to requirements evolution tasks. Our approach can help app developers to systematically analyze user opinions about single features and filter irrelevant reviews.
User Involvement in Software Evolution Practice: A Case StudyDennis Pagano
User involvement in software engineering has been researched over the last three decades. However, existing studies concentrate mainly on early phases of user-centered design projects, while little is known about how professionals work with post-deployment end-user feedback. In this paper we report on an empirical case study that explores the current practice of user involvement during software evolution.
We found that user feedback contains important information for developers, helps to improve software quality and to identify missing features. In order to assess its relevance and potential impact, developers need to analyze the gathered feedback, which is mostly accomplished manually and consequently requires high effort. Overall, our results show the need for tool support to consolidate, structure, analyze, and track user feedback, particularly when feedback volume is high. Our findings call for a hypothesis-driven analysis of user feedback to establish the foundations for future user feedback tools.
Business Rules In Practice - An Empirical Study (IEEE RE'14 Paper)Walid Maalej
Business rules represent constraints in a domain, which need to be taken into account either during the development or the usage of a system. Motivated by the knowledge reuse potentials when developing systems within the same domain, we studied business rules in a large software company. We interviewed 11 experienced practitioners on how they understand, capture, and use business rules. We also studied the role of business rules in requirements engineering in the host organization. We found that practitioners have a very broad perception for this term, ranging from flows of business processes to directives for calling external system interfaces. We identified 27 types of rules, which are typically captured as a free text in requirements documents and other project documentation. Practitioners stated the need to capture this tacit form of domain knowledge and to trace it to other artifacts as it impacts all activities in a software engineering project. We distill our results in 17 findings and discuss the implications for researchers and practitioners.
How Does a Typical Tutorial for Mobile Development look like? - A research paper presented at the 2014 International Conference on Mining Software Repositories. Paper preprint available here: http://mobis.informatik.uni-hamburg.de/research/publications
Assisting Engineers in Switching Artifacts by using Task Semantic and Interac...Walid Maalej
Abstract Recent empirical studies show that software engineers use 5 tools and 14 artifacts on average for a single task. As development work is frequently interrupted and several simultaneous tasks are performed in parallel, engineers need to switch many times between these tools and artifacts. A lot of time gets wasted in repeatedly locating, reopening or selecting the right artifacts needed next. To address this problem we introduce Switch!, a context-aware artifact recommendation and switching tool. Switch! assists engineers in switching artifacts based on the type of the development task and the interaction history.
Assessing Feedback for Indirect Shared InteractionJorge Cardoso
Just skyped this presentation to OTM-MONET in Greece, about the paper:
http://www.mendeley.com/research/assessing-feedback-indirect-shared-interaction/
Supporting Social Complexity in Collaborative EnterprisesBoxer Research Ltd
The presentation explores the need for enterprises to capture new forms of indirect value in ecosystems, and the demand this creates for platform architectures that can support customers within these contexts.
Intro to Convofy for Consultancies and Agencieststaley
Convofy is a private social network app that goes farther that the rest, adding true on-the-page collaboration, even markup of web pages, as well as instant messaging.
McKinsey\'s fifth annual survey on the way organisations use social tools and technologies finds that they continue to seep into many organisations, transforming business processes and raising perforamnce.
Social Intranets - Taking Advantage of Social Within Your OrganizationPrescient Digital Media
Prescient's Vice President and General Manager Carmine Porco joins Josh Anstey, VP of Partner Engagement at Elcom to present a one hour webinar on social intranets.
To view a recording of this webinar, please visit: http://www.prescientdigital.com/articles/view-social-intranets-taking-advantage-of-social-within-your-organization
A short bullet point presentation used at the workshop for 2.0 participatory innovation practices for cultural insitutions held at CCCB-Lab, on April 22nd by the members of CItilab Expolab project. The first in a series of workshops.
How Do Users Like This Feature? A Fine Grained Sentiment Analysis of App Revi...Walid Maalej
App stores allow users to submit feedback for downloaded apps in form of star ratings and text reviews. Recent studies analyzed this feedback and found that it includes information useful for app developers, such as user requirements, ideas for improvements, user sentiments about specific features, and descriptions of experiences with these features. However, for many apps, the amount of reviews is too large to be processed manually and their quality varies largely. The star ratings are given to the whole app and developers do not have a mean to analyze the feedback for the single features. In this paper we propose an automated approach that helps developers filter, aggregate, and analyze user reviews. We use natural language processing techniques to identify fine-grained app features in the reviews. We then extract the user sentiments about the identified features and give them a general score across all reviews. Finally, we use topic modeling techniques to group fine- grained features into more meaningful high-level features. We evaluated our approach with 7 apps from the Apple App Store and Google Play Store and compared its results with a manually, peer-conducted analysis of the reviews. On average, our approach has a precision of 0.59 and a recall of 0.51. The extracted features were coherent and relevant to requirements evolution tasks. Our approach can help app developers to systematically analyze user opinions about single features and filter irrelevant reviews.
User Involvement in Software Evolution Practice: A Case StudyDennis Pagano
User involvement in software engineering has been researched over the last three decades. However, existing studies concentrate mainly on early phases of user-centered design projects, while little is known about how professionals work with post-deployment end-user feedback. In this paper we report on an empirical case study that explores the current practice of user involvement during software evolution.
We found that user feedback contains important information for developers, helps to improve software quality and to identify missing features. In order to assess its relevance and potential impact, developers need to analyze the gathered feedback, which is mostly accomplished manually and consequently requires high effort. Overall, our results show the need for tool support to consolidate, structure, analyze, and track user feedback, particularly when feedback volume is high. Our findings call for a hypothesis-driven analysis of user feedback to establish the foundations for future user feedback tools.
Business Rules In Practice - An Empirical Study (IEEE RE'14 Paper)Walid Maalej
Business rules represent constraints in a domain, which need to be taken into account either during the development or the usage of a system. Motivated by the knowledge reuse potentials when developing systems within the same domain, we studied business rules in a large software company. We interviewed 11 experienced practitioners on how they understand, capture, and use business rules. We also studied the role of business rules in requirements engineering in the host organization. We found that practitioners have a very broad perception for this term, ranging from flows of business processes to directives for calling external system interfaces. We identified 27 types of rules, which are typically captured as a free text in requirements documents and other project documentation. Practitioners stated the need to capture this tacit form of domain knowledge and to trace it to other artifacts as it impacts all activities in a software engineering project. We distill our results in 17 findings and discuss the implications for researchers and practitioners.
How Does a Typical Tutorial for Mobile Development look like? - A research paper presented at the 2014 International Conference on Mining Software Repositories. Paper preprint available here: http://mobis.informatik.uni-hamburg.de/research/publications
Assisting Engineers in Switching Artifacts by using Task Semantic and Interac...Walid Maalej
Abstract Recent empirical studies show that software engineers use 5 tools and 14 artifacts on average for a single task. As development work is frequently interrupted and several simultaneous tasks are performed in parallel, engineers need to switch many times between these tools and artifacts. A lot of time gets wasted in repeatedly locating, reopening or selecting the right artifacts needed next. To address this problem we introduce Switch!, a context-aware artifact recommendation and switching tool. Switch! assists engineers in switching artifacts based on the type of the development task and the interaction history.
Assessing Feedback for Indirect Shared InteractionJorge Cardoso
Just skyped this presentation to OTM-MONET in Greece, about the paper:
http://www.mendeley.com/research/assessing-feedback-indirect-shared-interaction/
Supporting Social Complexity in Collaborative EnterprisesBoxer Research Ltd
The presentation explores the need for enterprises to capture new forms of indirect value in ecosystems, and the demand this creates for platform architectures that can support customers within these contexts.
Intro to Convofy for Consultancies and Agencieststaley
Convofy is a private social network app that goes farther that the rest, adding true on-the-page collaboration, even markup of web pages, as well as instant messaging.
McKinsey\'s fifth annual survey on the way organisations use social tools and technologies finds that they continue to seep into many organisations, transforming business processes and raising perforamnce.
Social Intranets - Taking Advantage of Social Within Your OrganizationPrescient Digital Media
Prescient's Vice President and General Manager Carmine Porco joins Josh Anstey, VP of Partner Engagement at Elcom to present a one hour webinar on social intranets.
To view a recording of this webinar, please visit: http://www.prescientdigital.com/articles/view-social-intranets-taking-advantage-of-social-within-your-organization
A short bullet point presentation used at the workshop for 2.0 participatory innovation practices for cultural insitutions held at CCCB-Lab, on April 22nd by the members of CItilab Expolab project. The first in a series of workshops.
Workforce Intelligence and Social Analytics: Opportunity at the ConfluenceYvette Cameron
The use of enterprise social networking platforms is on the rise as organizations look to these emerging tools to facilitate employee collaboration, knowledge sharing, increased engagement, improved productivity, and even to foster fundamental shifts in culture. As more and more employee interactions take place within these enterprise collaboration tools, new and interesting data emerges about employees, teams, projects, goals, content and other aspects of the enterprise.
This new data, gleaned through analysis of the activities within the collaboration platform, includes insights into how people work and collaborate, the type and quality of content that is contributed and leveraged in the community, the effectiveness of different communications, the degree to which individuals are perceived as leaders or followers, and much more. The emergence of this new data enables much richer insights into the workforce of the organization. It enables the infusion of social intelligence into traditional talent management processes, such as performance, calibration, succession and retention. Combining social and workforce analysis enables People Insight 2.0.
In this session, we’ll look how organizations can leverage the opportunities of People Insight 2.0. We’ll cover the tools used and opportunities stemming from the analysis of network connections, community activity, sentiment analysis, employee reputation management, and others. We’ll also explore the ways by which this social data can increasingly be incorporated into workforce analytics and workforce planning platforms for a more holistic view of the workforce.
We’ll review use cases and provide practical tips for how you can immediately apply these new social workforce insights to your talent management initiatives, transforming your people processes for better business results.
CONNECT-COLLABORATE-CONTRIBUTE: How to switch to a social Intranet
May 28, 2011 – Advanced Intranet and Portal Conference 2011 – Amsterdam (Netherlands)
DAS Performics: Hypebusters: "The Golden Age of Marketing"Digiday
It can often seem like the worst of times in the media industry. In fact, there’s never been a better time to do marketing. Here’s why.
Presented by Daina Middleton, global CEO, Performics
How Can Software Engineering Support AIWalid Maalej
Flipping the Coin: How can Software & Requirements Engineering Support AI?
During the last decade, the Software Engineering and Requirements Engineering communities have profited much from advances in Machine Learning and in Natural language Processing. Recommender systems, prediction models, and even Bots are nowadays available to support many software and requirements engineering tasks: including quality assurance, documentation, or even code generation and completion.
This talk will focus on the opposite direction. I will discuss recent challenges faced by the Machine Learning/ NLP/ Data Science community and whether/how traditional as well as modern Software and Requirements Engineering can help solve some of them: in order to increase the applicability, acceptance, and reliability of Machine Learning based systems.
Walid Maalej is a professor for informatics and chair for applied software technology at the University of Hamburg, Germany. Currently he is also the Head of the Informatics Department and a member of the Board of Directors of the tech transfer institute HITeC e.V. His main research interests includes human- and data-centered software engineering, requirements engineering, feedback systems, applied machine learning, as well as tech transfer.
Work descriptions are informal notes taken by developers to summarize work achieved in a particular session. Existing studies indicate that maintaining them is a distracting task, which costs a developer more than 30 min. a day. The goal of this research is to analyze the purposes of work descriptions, and find out if automated tools can assist developers in efficiently creating them. For this, we mine a large dataset of heterogeneous work descriptions from open source and commercial projects. We analyze the semantics of these documents and identify common information entities and granularity levels. Information on performed actions, concerned artifacts, references and new work, shows the work management purpose of work descriptions. Information on problems, rationale and experience shows their knowledge sharing purpose. We discuss how work description information, in particular information used for work management, can be generated by observing developers' interactions. Our findings have many implications for next generation software engineering tools.
Paper: Walid Maalej and Hans-Jörg Happel, Can Development Work Describe Itself? In Proceedings of the 7th IEEE Conference on Mining Software Repositories, IEEE CS, 2010.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
2. Outline
of
the
Talk
1
MoHvaHon
2
So/ware
Socialness
3
SSE
Framework
4
Research
Challenges
2
3. User
Involvement
is
CriHcal
for
the
Success
of
So/ware
Projects
Reasons
for
canceled
projects
Factors
of
success
Incomplete
Requirements
13%
Customer/User
involvement
16%
No
customer
requirements
12%
Ex.
Management
support
14%
Lack
of
resources
11%
Clear
Statement
of
13%
Unrealis9c
expecta9ons
10%
requirements
Uncontrolled
changes
of
9%
Proper
planning
10%
requirements
Realis9c
expecta9ons
8%
[Standish
Group
2003,
recent
studies
with
similar
results]
3
4. State
of
the
Art
of
User
Involvement…
…in
processes
…in
systems
• Conven9onal
soRware
• Heterogeneous,
vendor
processes
are
transac'onal
specific
feedback
interfaces
regarding
users
are
pure
• User
input
is
difficult
to
consumers
provide
since
full
context
• Users
involved
in
informa9on
must
be
entered
requirements
ac9vi9es
• There
is
no
feedback
on
the
• “2nd
class
ci9zen”
user
feedback
Serious
problems
can
emerge
from
this
situa9on
[Maalej
et
al.
OOPSLA
2009]
4
5. Consequence
1:
LiWle
or
no
indicators
about
real
so/ware
usage
Only
download
or
sales
numbers
7. Consequence
2:
Valuable
experiences
and
volunteered
resources
get
lost
Knowledgeable
users
are
unable
to
contribute
easily
8. Eric
von
Hippel
of
M.I.T.,
leR,
and
Nathaniel
Sims,
with
hospital
devices
Sims
has
modified.
Von
Hippel
says
users
can
improve
on
products.
[The
New
York
Times,
2007]
8
9. Consequence
3:
Frustrated
users
can
harm
the
reputaHon
of
so/ware!
Users
organize
communi9es
against
the
soRware
12. Our
Vision
1. Revolutionizing the role of end users
2. Dissolve the boundaries to software engineers
3. Make software processes and systems social
12
13. Outline
of
the
Talk
1
MoHvaHon
2
So/ware
Socialness
3
SSE
Framework
4
Research
Challenges
13
14. Socialness
of
So/ware
Socialness
is
the
degree
of
involvement
of
its
users
and
their
communi3es
in
the
so4ware
lifecycle
User
involvement
• AcHvely
work
on
specific
project
ac9vity
(e.g.
tes9ng,
documenta9on,
development)
• Influence
management
or
engineering
decision
(e.g.
give
feedback,
vote)
Community
involvement
• Externalize
important
knowledge
• Share
common
interests
14
15. Benchmarking
Socialness
CollaboraHve
Social
User
Involvement
So/ware
So/ware
TransacHonal
Popular
So/ware
So/ware
Community
Involvement
15
16. Measuring
User
Involvement
ContribuHon
Quality
How
is
the
quality
of
the
contribu9on?
2
ContribuHon
1
Explicitness
ContribuHon
Is
the
contribu9on
Means
Individual
explicit
(intended)
or
Metrics
implicit?
Is
the
contribu9on
integrated
into
the
work
environment?
3
4
ContribuHon
Time
Does
the
contribu9on
occur
during
the
user
tasks?
16
17. Measuring
Community
Involvement
Community
Size
How
many
members
does
the
soRware
community
have?
Community
2
AcHvity
1
How
is
the
Community
communica9on
AWracHveness
Community
Community
volume
and
topic
Metrics
Metrics
How
is
the
ra9o
of
varia9on
in
the
member
gain
and
community?
member
loss?
3
4
Community
Interweaving
How
is
the
ra9o
of
contributors
in
the
whole
community?
17
18. Outline
of
the
Talk
1
MoHvaHon
2
So/ware
Socialness
3
SSE
Framework
4
Research
Challenges
18
19. Outline
of
the
Talk
1
MoHvaHon
2
So/ware
Socialness
3
SSE
Framework
Process
Architecture
19
20. SNAIL:
A
Social
So/ware
Engineering
Process
Systematic
Analysis
Engi-
neering
Decision
Proactive
Feedback
Update
User Observation
Community Observation
Time
20
21. SNAIL:
A
Social
So/ware
Engineering
Process
Con9nuous
gathering
of
context
informa9on
to
understand
circumstances
Systematic under
which
a
user
Analysis provides
feedback
Engi-
neering
Decision
Proactive
Feedback
Update
User Observation
Community Observation
Time
21
22. SNAIL:
A
Social
So/ware
Engineering
Process
Systema9c
observa9on
of
user
communi9es
to
gather
input
and
benefit
Systematic
from
social
dynamics
Analysis
Engi-
neering
Decision
Proactive
Feedback
Update
User Observation
Community Observation
Time
22
23. SNAIL:
A
Social
So/ware
Engineering
Process
Proac9vely
ask
users
to
provide
individual
and
social
feedback
to
improve
Systematic soRware
(e.g.
in
problem
Analysis situa9ons)
Engi-
neering
Decision
Proactive
Feedback
Update
User Observation
Community Observation
Time
23
24. SNAIL:
A
Social
So/ware
Engineering
Process
Reduce
the
amount
of
informa9on
for
engineers
and
iden9fy
conflic9ng
Systematic
preferences
Analysis
Engi-
neering
Decision
Proactive
Feedback
Update
User Observation
Community Observation
Time
24
25. SNAIL:
A
Social
So/ware
Engineering
Process
Give
users
the
possibility
to
influence
ac9ons
triggered
by
the
analysis
Systematic
(e.g.
vote,
rate,
comment)
Analysis
Engi-
neering
Decision
Proactive
Feedback
Update
User Observation
Community Observation
Time
25
26. SNAIL:
A
Social
So/ware
Engineering
Process
Inform
users
about
engineering
decisions
and
ra9onale
and
propagate
Systematic
changes
to
soRware
Analysis
Engi-
neering
Decision
Proactive
Feedback
Update
User Observation
Community Observation
Time
26
27. Outline
of
the
Talk
1
MoHvaHon
2
So/ware
Socialness
3
SSE
Framework
Process
Architecture
27
28. FastFix
Reference
Architecture
Applica9on
Usage
Target
Applica9on
Environment
Social
Engineering
Client
Social
Context
User
Feedback
System
System
Media
Communica9on
System
Social
Media
Bridge
Social
Engineering
Center
Communica9on
System
Social
Media
Bridge
User
Feedback
Analysis
Back-‐Feedback
Community
System
System
Center
Applica9on
Engineering
Environment
28
29. Context
ObservaHon
and
Processing
AddiHonal
feedback
InteracHon
Feedback
ReporHng
Interface
Ontology
interact
Context
System
trigger
problem
P
roblem
problem
ApplicaHon
sensors
ElicitaHon
events
Session-‐
izaHon
ExecuHon
OS
Exec.
Env.
Ontology
update
sensors
sensors
User
Profile
www.teamweaver.org
www.fasaixproject.eu
29
30. Unified
Interface
for
User
Feedback
SNAIL Feedback
Report
Provide feedback
Use this form to report on your experience.
I did not understand the export dialog. It said export to, but
instead it only saved the document to the specified folder.
Tag your report
Use tags to help other users find your report and to help
engineers understand your experience.
export, usability, difficulty
Mark similar reports
SNAIL has found reports that are similar to yours. Help to
focus by selecting relevant similar reports. Show similar reports
Share with the community
I agree to make this experience report public to create
awareness about my experience in the community.
Context information included
This report will contain additional context information that
helps to understand your experience.
Show additional information 30
31. Community
Center
on
Social
Media
SNAIL Community Center
Help others Development corner Future directions
Help other users with Contribute to make the Influence the future
their problems. software better. development directions.
Documentation Feature request list Request feature
Discussions List of known errors Vote on features
Knowledgebase Source code repository Vote on release plan
Get information Provide feedback Test bed
Browse through the know- Report on your exper- Perform tests of early
ledgebase or ask questions. ience. versions.
Documentation Report error Beta download page
Discussions Request modification Release plan
Knowledgebase Report experience Source code repository
31
32. Example
of
Community
Center
FuncHonality
SNAIL Feature Requests
Influence future directions
On this page you can request new features and vote on existing ones.
Request new feature
Creator:
1746 Add a PDF export feature.
Currently files can only be saved in the proprietary SNL
votes format. Interchange with other platforms would be a very
Dennis
!"# important feature.
Add comment View comments (17 features)
Creator:
1031 It would be helpful to be able to compare two documents.
Currently this is only possible using a workaround.
votes
Walid
!"# Add comment View comments (19 features)
32
33. Example
of
User
Feedback
Analysis
SNAIL Social Analytics
Documentation statistics
This page shows statistics about the documentation of SNAIL written by users.
Documented Features
2000
1000
April 2011 May 2011 June 2011 July 2011
Visualization options
Overall statistics By component
33
34. Outline
of
the
Talk
1
MoHvaHon
2
So/ware
Socialness
3
SSE
Framework
4
Research
Challenges
34
35. Challenges
for
So/ware
Socialness
Scalability
Huge
amount
of
gathered
Cultural
Issues
(unstructured)
data
ContribuHon
Quality
complicates
manual
Accep9ng
users
as
Unpredictable
analysis
contributors
requires
a
content
and
varying
paradigm
shiR
in
quality,
complicates
commercial
organiza9ons
automated
analysis
Different
types
of
challenges
Human
Issues
Conflict
ResoluHon
Ensure
the
privacy
of
Conflic9ng
preferences
users,
giving
incenHves
to
IntegraHon
and
input,
complica9ng
contribute
in
a
usable
manual
iden9fica9on
and
Diverse
systems
and
non-‐intrusive
manner
resolu9on
techniques
technologies
have
to
be
monitored
and
integrated
35
36. Summary
of
the
Talk
• Degree of user and community "
So/ware
involvement in the software lifecycle
Socialness
• Benchmark for assessing socialness " Making
user
of software
involvement
and
user
• Social engineering process (SNAIL) "
communiHes
SSE
involves users thoroughly and continuously
Framework
• Reference architecture integrated into target
a
first
order
application and engineering environment
concern
of
so/ware
systems
and
• Main challenges are in the systematic
processes
Challenges
analysis of continuous user feedback
• Other cultural and human challenges
36
37. For
Feedback,
QuesHons
and
CollaboraHon...
Walid Maalej
Dennis Pagano
maalejw@cs.tum.edu
pagano@cs.tum.edu
37