Software engineering is in its way from art to science. This presentation shows what it is to develop software by science, the benefits and steps to do so.

1. Develop better software of any
size cheaper and faster by science
1

2. “Software engineering is not yet a
true engineering discipline, but it
has the potential to become one.”
Prof. Mary Shaw, CMU
All established engineering branches
underwent a transition from art to science.

3. The Transformation of Civil Eng
3
Too much labor
Too much stone
Too long time to build
Only small bridges
Prescience Stage Scientific Stage
1800
Better, Cheaper, Faster
No limitation to Size

4. The First Building Built by Science
England's Crystal Palace
built in 1850

5. SE, a branch of Eng, is art today
Today’s software Software made by science

6. Science v.s. Art: Product Lifecycle Cost
Development
Cost
Maintenance
Cost
Development
Cost
Maintenance
Cost
Develop
healthcare.gov by art
Develop healthcare.gov
by science

7. Soft Eng is on its way to science
7
“The Engineering discipline of software already exists.
But it is not common sense.” – Mary Shaw, 1990.
There are two principles in the Eng discipline of software.
1. Mature fundamentals of design common to all engineering.
2. Principle of design specific to software.
The first principle is in the discipline of product development.
The second principle is in the enterprise architecture practice.

8. Scientifically Design Software
Software Development Life Cycle
Product Development
Enterprise Architecture

9. Enterprise Architecture
Business
Strategy
Technology
Implementation
Enterprise
Architecture
Architectures of
different dimensions
Implementation
plan

10. Product Design
Design is described by technical drawings
(four types of data)
Shape &
dimension
of parts
Materials of
parts to be
made of
Manufacturing
techniques
Ways that
parts are
assembled

11. Software Product Design
• UI architecture
• Business architecture
• Application architecture
• Data architecture
Shape & dimension
of parts
• Computer languages
Materials of parts
to be made of
• Implementation Plan
• Activity and data flow
diagrams for each app
Manufacturing
techniques
• Integration between
applications
Ways that parts are
assembled

12. Application architecture
• Application architecture is the logic partition of
the software system into subsystems, called
applications, with nothing leftover. It is like
floors (subsystems) of a tall building (software).
• The application architecture explains how the
business architecture is realized.
• The data architecture determines the
dependencies of the applications that, in turn,
determines the order of implementation.
12

13. Software Product Design Process
Define 4
Architectures
Define
Activity/Data
Flows for an
Application
Implement
& Test the
App
Implmt
Plan
Next Application
The above process is a not waterfall but a theory construction process.

14. The what, how and why
The theory of a software
system is the axiomatic
representation of the
invariant property (e.g.
business rules) of the
application domain and is
constructed throughout of
the development process.
The theory is used to explain
and prove the truthfulness of
the system (under
development) satisfying
business wants .
• Much smaller information volume of all work products (models
of all kinds and software) hence better, better, and faster.
• Complete project visibility and stability of task breakdowns and
project schedule.
• Intellectual security and maximum objectivity.

15. Summary
Today’s software is made by handicrafts, costing
too much labor, too many lines of code.
Companies can scientifically develop better
software of any size cheaper & faster today.
The scientific approach has been tested in
marketplace such as www.dust2pearl.com
Contact Jerry to know in what extent you can
be better, cheaper and faster and steps to do so.
15
Dr. Jerry Zhu, TOGAF, ITIL
Jerry.zhu@ucsoft.biz