16. Fast, responsive, iterative development
Current and Potential Users
DevTeam
Customer
Representative
Ratings
& reviews
1%
Praise
Value
17. Summary of the world today
• Unknowns dwarf the known
• For users: which apps suit them and satisfy them
• For developers: what to develop (functionalities) and how
• Feedback is flawed, incomplete, limited.
19. Apps as an interactive Channel
• Apps incorporate a channel where users and developers communicate
directly about the quality of the app
• The developers can iterate rapidly, delivering improvements based on
interactions and feedback
• Effective communications between the two sides, similar to add an
interactiveTV channel to mobile app
Inspired by Prof Anthony Finkelstein (Turn on,Tune in 2011)
20. Channel Paradigm
• New paradigm – software as a channel – software not as a static artifact moved
to dynamic: a vehicle for software development and user/consumer
• Some software channels are broad while others are narrow and more specialised
such asTV Sport Channels
• Application should be adapted and grow with the users
• The app can present the users new opportunities
• The main aim of a software engineer is to engage the user as the continuous
changes are the key to ongoing business
• It changes the orientation from product/service delivery to a relational stance.
23. Approach and Objectives
• Apps incorporate a channel where users
and developers communicate directly
about the quality of the app
• The communication can be richer than
the one offered by existing options
• Communication can be kept private and
protected from competitors
• Effective communications between the
two sides, similar to add an interactive
TV channel to mobile app
1. To understand the factors that matter to
app users by information analytics and
market analysis
2. To localise requirements to recommend
design decisions in architecture by
combining reverse engineering and structural
traceability retrieval
3. To evaluate the effectiveness of
communications by ethnographic studies
and experimental case studies
25. Example Challenges: Communications
• Providing Users ways to provide timely feedback while they remember
• Most community feedback does not align with developer’s mission
• Obtaining feedback from across the desired user-base
• Multi-modal communications
• Languages
• Latencies
• Signal to Noise ratios
Technology-facing
Design-facing
Feature-facing
http://modeling-languages.com/on-the-automation-of-the-horse-shoe-model-for-software-modernization/
Based on the original by: R. Kazman, S. G. Woods, and S. J. Carrière, “Requirements for Integrating Software Architecture and Reengineering Models : CORUM II,” in WCRE conf., 1998
Customer Representatives
Customers
We want to find ways to improve the communications between users and the developers in order to develop more suitable apps with less waste. Fast iterations.
The recent rise of Instant Apps might help
The communication can be richer than the one offered by existing options
Communication can be kept private and protected from competitors
Increase loyalty
Infinite Flight iOS app: Highly active Games App as an example
N = learning from other apps
Not copy paste, looking at how they achieve the quality of their apps.
Localisation: Locating where the implementation for the Quality Attributes from other apps.
Relevant, feedback developers can action
Apptentive: a bi-directional channel
SafeDK: quality analysis of libraries – to help developers pick ones that work well and are suitable
Monkop: automated assessment of various quality aspects