1.  CS 5380 Software Engineering Chapter 10 Sociotechnical Systems

2. Section 2 of book  Section 2: Dependability and Security  Introductory statement  Dependability and Security can be more important than functionality  Insulin pump  Ancestry.com  Voter targeting  MS Word  Flight controller Chapter 7 - Design and Implementation2

3. Systems  Author: A system is a purposeful collection of interrelated components of different kinds which work together to achieve some objective Chapter 7 - Design and Implementation3

4. SocioTechnical Systems  Term since 1950s  System of more than hardware and software  Factors  People  Processes  Laws, Regulations  Organizaitons  Physical Environment Chapter 7 - Design and Implementation4

5. SocioTechnical System Stack  Sociotechnical System Stack  Equipment  Operating System  Communications and data management  Application layer  Business Process layer  Organizational layer  Social Layer  Issues in one area affect others Chapter 7 - Design and Implementation5

6. Factors  Factors that affect the entire system (at creation or change)  Process changes  Do you require a process change for a new s/w system?  Desired change in process drives change  Job changes  new roles  obsolete roles  Organizational / political  Important/unimportant roles Chapter 7 - Design and Implementation6

7. Characteristics of SocioTechnical Systems  Emergent properties  Appear after system starts  Nondeterministic  Hardware generally deterministic  Software may change  Other factors are hard to control  Acceptability of system will change due to various factors Chapter 7 - Design and Implementation7

8. Emergent System Property  Emergent system properties  Appear after systems implemented  CAD systems  Multiple vendors  No universal interchange format  Attempts – plotting, consortium  Autodesk file format  Initially, just another format  After market share achieved, defacto standard  Level of sociotechnical system stack? Chapter 7 - Design and Implementation8

9. Emergent System Properties  Email  Until a sufficient population has the same technology, it is not accepted.  Collective understanding of email affects its use  Etiquette (forwarding, tone)  Attachments  Standards of organizations  Security  Storage allowances  Level of Sociotechnical Systems Stack? Chapter 10 – Socio Technical Systems9

10. Non Determinism  Voter tracking database  Created by incorporation of data from  States  Counties  Data providers  Standardization of formats limited  USPS, yes. Few follow the rules Chapter 7 - Design and Implementation10

11. Multilevel Issues  Integration of data from diverse sources  Different formats (csv, fixed cell, spreadsheet)  Different intents (employee list, parent list, band booster)  Different standards of quality (employee list, band booster, voter file)  Different standards of content (fields – name, address, phone, zip)  Human errors Chapter 7 - Design and Implementation11

12. Wicked Problems  No clear solution  Contradictory requirements  Changing requirements  Too many stakeholders Chapter 7 - Design and Implementation12

13. Gradebook System  Goal: coordinate gradebook information.  Master Database of Teachers, Classes, Students, Grades  Individual database at teacher computer  Periodic grade reporting electronically  Pre- internet  Data card  Issues  Acceptance, training, integration Chapter 7 - Design and Implementation13

14. GIS System  Geograpic Information System  Datanbase of geographic features  Streets  Properties, Ownership, Easements  Gas, Electric, Phone lines  Political Boundaries (precincts, zip codes, …)  Uses  Right of way procurements  Maintenance – digging  Public announcements  Issues:  Usability of system before data set up Chapter 7 - Design and Implementation14

15. Group Exercise  Distributed in class Chapter 7 - Design and Implementation15

16. Stages  Procurement  Development  Operation Chapter 7 - Design and Implementation16