SCALARE – SCALing SoftwARE

Even-André Karlsson

SCALARE – SCALing SoftwARE

© Addalot Consulting AB - All rights reserved

Agenda §  Background and project

§  Scaling management framework

§  Patterns

2

http://scalare.org/


Project 3, SCALARE – SCALing softwARE § 50 Billion Connected Devices"

3MORE THAN 50 BILLION CONNECTED DEVICES DRIVING FORCES

coffee makers. As the cost, size and power requirements of wireless modules fall, all kinds of devices are becoming connected – not just stationary computers and laptops, but also tablets, ultra-mobile PCs, portable game consoles, TV sets, cameras and home appliances. Reduced cost, size and power requirements will enable a paradigm shift, after which connectivity can be used to monitor and/or control almost anything.

As wireless capabilities become increasingly integrated within computer chips, the benefits of the computing world – innovation, short development cycles and low cost – are extending into mobile communications. As a result, traditionally unconnected devices are becoming connected – varying from television to cars and industrial machinery to farmland equipment.

NUMBERS BEHIND THE NUMBERTo understand how the number of connected devices could reach more than 50 billion over the next decade, it is worth considering some high-level, macro-economic trends and statistics. As a few examples, by 2020 there will be:

their lifestyles and improve personal security. In mature markets, these customers will typically possess between 5-10 connected devices each.

communicating.Development of the networked world is progressing through a number of waves, as shown in

Figure 2.

NETWORKED BUSINESSThe adoption of connected devices by business will be largely driven by customer-service enhancement, as well as opportunities to increase productivity, cost-efficiency, monitoring and control of assets. Other factors will include the need to comply with new legislation, whether in sustainability, security or other areas. Connectivity will be a core component of future service and application development.Thanks to rapid technology development, the cost of connectivity is no longer a significant factor when considering if it is worthwhile to connect an application to a network. Opportunities in connectivity are emerging in parallel with the development of cloud-based services, which are accelerating the development of applications and offering faster and simpler reuse of applications and application components across industries.

In today’s globalized business world, networks are fundamental to commercial activity and production. Production is increasingly organized among separate players and their complex web of interactions creates value chains that help drive the global economy. Global networks cover many areas of activity, including networked

Networked consumer electronics

Networked industries

Seco

nd w

ave

Networked everythingNetworked society

Improvedreach

Improved value– consumer lifestyle

Improved processefficiency

Improved humanefficiency

Third wave

First wave

Figure 2. The three waves of connected device development.

Source: Ericsson

Means a LOT of new software… …everywhere!


Increasing Role of Software

2

Increasing role of the software

ITEA Roadmap Edition 3

Source: EUREKA/ITEA


Migration to Software

Traditional technology (Mechanics, Hardware, … )

Software

Telecomm

unications

Autom

otive

Engineering Industry

Scaling Management Model


The SCALARE Consortium – Itea2

•  Lund University •  Sigrun •  Tieto •  Husqvarna •  Softhouse •  Sony Mobile •  Addalot

•  University of Limerick •  Goshido •  Qumas •  Vitalograph

Telvent, project coordinator

Kugler-Maag http://scalare.org/ https://itea3.org/project/scalare.html


Scaling Management Framework: SMF Purpose

§ Help organizations to analyse their current and future needs and abilities

§  Provide example patterns and case studies

§ More controlled and efficient scaling

Why needed?

§  Scaling is not well understood

§  Usually the company lacks competence in new technologies

§ Dependent on key people with a vision

§ Hard to describe and analyse different alternatives

§ Difficult to explain and motivate the changes


Organization

Process

Product Architecture

Business Drivers

Result

Software Abilities

Time Cost

Quality

Software Model

Explanation: Business needs drive the change (scaling) of software development An organizations ability to deliver can be ”black box” measured on the parameters Time, Cost and Quality - How fast and to what cost and what quality can the organization deliver something? The model for software development can be characterized and divided into 3 main domains: Architecture, Organization and Process

Overview of SMF


Domains and building blocks

Organization • System

organization • Process

organization • Governance • Culture &

leadership

Process • Requirements and design • Validation, review and

verification • Development paradigm • Maturity

Product Architecture • Development view • Delivery view • Execution view


Basic example §  To illustrate our model we use a

simplified examples of one person, Ed, that develops the software for a family of chainsaws.

§ He does all the work himself, and interacts directly with the mechanical engineers and the product planners.

§ Note that even a one person developing software has architecture, process and organization


§ Development view -  Code design and structure (patterns, modules, interfaces)

-  Source code CM structure (files, versioning, repositories)

-  Development environment (tools)

§ Delivery view -  How we go from source code files to running systems

-  All systems/tools that support this transformation

-  Includes all branching, configuration, customization, delivery, etc.

§  Execution view -  How the stakeholders interact with the system

-  Client/Server, Layered architecture, Internal and external API’s, Cloud, service interfaces, …

Organization

Process

Architecture

Software model – Product Architecture


Software model – Product Architecture Chain saw example:

§ Development view -  Ed has one main C source file and a standard C library

-  He uses Git for version control

§ Delivery view -  Configuration for different models are handled by if-def’s in the code

-  Ed builds one executable with the GCC compiler that is flashed into the Chain Saw during production

-  There has never been any updates of the SW in production

§  Execution view -  One processor and one executable without any external interfaces

Organization

Process

Architecture


Software model - Process §  Requirements and design

-  How is the requirements and design of the system is documented, e.g. requirements, design, test, and which tools are used?

-  Documentation of long term strategies

§  Validation, review and verification -  How do we assure that we are building the right system and that its functionality is

working as intended.

§ Development paradigm -  How do we develop our software, e.g. Waterfall, Agile, happy hacking, release

cycles?

§ Maturity -  How well do we control, measure and improve our processes, e.g. ISO 9000, CMM-I

maturity levels?

Organization

Process

Architecture


Software model - Organization

§  System organization -  How is the responsibility for the system divided? Make, buy, or open source, and

which department is responsible for what part. This looks at the organization from the architecture perspective

§  Process organization -  How is the responsibility for the process divided?

Any organization goes from long term strategy to delivered products, and we need to have someone responsible for each part of the transformation. This also covers what is organized as projects and what are line activities.

§  Governance -  Which decisions are taken by whom? Examples of decisions are shall we make a

new SW product, which features to include, shall we delay the product to get the last features, is the quality good enough, which bugs to correct now, changes in architecture, and more overall organizational or process changes etc.

§  Culture & leadership -  The general attitude in the organization. -  Attitude towards change and improvement

Organization

Process

Architecture


Patterns

A pattern is a ”large scale strategic direction” for the whole software development.

-  Safety (process) – Conference http://safety.addalot.se/

-  Scrum (process) - Open source (org.) – Pilots http://www.addalot.se/nyheter/oss

-  Inner source (org.)

- Out sourcing (org.)

- Multi sites (org.)

-  Third party API and ”eco-system” (arch.) - Cloud (arch.)

-  Product lines (arch.)

- Acquisition (org.)


Contact and collaboration § We encourage contributions and collaboration:

-  Case studies in Scaling

-  Useful patterns

-  Piloting the Scalare Open Source pattern

§  Ulf Asklund, Scalare Sweden Co-ordinator, [email protected]

§  Even-André Karlsson, Addalot, [email protected]

§  http://scalare.org/

16

[email protected] +46 706 800 533

“Excellent firms don't believe in excellence - only in constant improvement and change.”

In Search of Excellence - Tom Peters

Documents

SCALARE – SCALing SoftwARE