Systems Engineering and Software Engineering develop side-by-side for several decades, starting from a need for coping with increasing complexity of physical engineering and computation, both struggling separately to become accepted disciplines. Strangely, there is little collaboration. In reality, software-system problem is similar to the body-mind problem. As a mind cannot exist without a body, software cannot exist without a system it embedded in. Software is a Ghost in the Machine. Increasing complexity blurs boundaries between engineering, computation and management and fuses them into unified Integrative Engineering. Practically, we have single engineering, looking for technological solutions for human problems. The Academy keeps exact sciences worlds apart from human and social studies. The applied disciplines of engineering and management follow the lead of the theoretical studies. In practice, mediating professions of systems engineers, business analysts, IT implementers and systems integrators emerged to bridge the gap. Mediator business is intrinsically risky, and their practice is in dire need for scientific support. This emerging socio-technical science must realize that engineered artifacts are not the same as perceived artifacts. As a map is not the territory it describes, the technology as engineered is not the tool as used. The engineered artifacts actually disappear when used - engineers make technology, people use tools, and the mediators much guide the transformation of the technology in the lab to the tools in the field. Design is never complex, people and nature make technology complex. The mediators must manage and limit the complexity emerging from human-nature-technology interactions. How should we proceed? By understanding that systems are wholes - there is no Mind-Body-Hardware-Software problem. By teaching one unified Engineering - multiple technologies do not multiple "engineerings" make.By focusing on both development and use of technology. By developing "mediation science" and "integrative engineering", starting with exploring how people "put system to use".

1. 1

2. 2
Physical EngineeringComputation
Systems EngineeringSoftware Engineering
Increasing Complexity

3. 3

4. 4
SW
HW
Mind
Body
Mind
affects
body
Body
affects
mind
SW
controls
HW
HW
hosts
SW
In the whole human,
where is Mind?
In the whole system,
where is SW?

5. 5
EngineeringComputation
Integrative Engineering
Increasing Complexity
Management

6. 6

7. Engineering,
Physics, Chemistry,
Computer Sciences,
Mathematics
Business, Management,
Politics, Warfare
Psychology, Sociology,
Organizational Science
7
Systems Engineers,
Business Analysts,
IT implementers,
Systems Integrators
ArtifactsNeeds

8.  What ‘s on their plate:
 Emergent properties which are unacceptable to the user
 User’s needs have changed since system analysis phase
 System meets customer requirement but don’t serve user’s needs
 System level bugs make the system unreliable
 So the Integrators/Mediators are:
 hated by the users (together with the customer that “failed” the users)
 underestimated by the developers and managers– “they create nothing”
 could be saved by good systems engineering practices upstream but ... no
systems engineer is around to share the blame.
Prepared by:
Doug Cowper (Sula Systems Ltd)
Dr Michael Emes (University College London)
Prof Alan Smith (University College London)
8

9. Mediators’ Science:
Socio-technology?
Engineering Systems?
Engineering,
Physics, Chemistry,
Computer Sciences,
Mathematics
Business, Management,
Politics, Warfare
Psychology, Sociology,
Organizational Science
9

10. Collaboration
10
Tasks
Deployment Transition to Use
Perceived Artifacts – Devices, Applications, Connections
Operational/Business Use
Communication
Engineered Artifacts – Hardware, Software, Systems, Symbolic
Engineering

11. 11

12. 12

13. 13

14. 14
Systems are wholes – no more Mind-Body-HW-SW problem
Teach one Engineering, multiple technologies (SW,HW)
Focus both on the development and the use of technology
Develop “mediation science” and Integrative Engineering
Start with exploring how people “put systems to use”

15. 15