 CS 5380 Software Engineering Chapter 10 Sociotechnical Systems.

  • Published on
    03-Jan-2016

  • View
    212

  • Download
    0

Transcript

Figures Chapter 4

CS 5380 Software Engineering

Chapter 10 Sociotechnical SystemsSSection 2 of bookSection 2: Dependability and SecurityIntroductory statementDependability and Security can be more important than functionalityInsulin pumpAncestry.comVoter targetingMS WordFlight controllerChapter 7 - Design and Implementation2SystemsAuthor: A system is a purposeful collection of interrelated components of different kinds which work together to achieve some objective

Chapter 7 - Design and Implementation3SocioTechnical SystemsTerm since 1950sSystem of more than hardware and softwareFactorsPeopleProcessesLaws, RegulationsOrganizaitons Physical EnvironmentChapter 7 - Design and Implementation4SocioTechnical SystemStackSociotechnical System StackEquipmentOperating SystemCommunications and data managementApplication layerBusiness Process layerOrganizational layerSocial LayerIssues in one area affect others

Chapter 7 - Design and Implementation5FactorsFactors that affect the entire system (at creation or change)Process changesDo you require a process change for a new s/w system?Desired change in process drives changeJob changes new rolesobsolete rolesOrganizational / politicalImportant/unimportant rolesChapter 7 - Design and Implementation6Characteristicsof SocioTechnical SystemsEmergent propertiesAppear after system startsNondeterministicHardware generally deterministicSoftware may changeOther factors are hard to controlAcceptability of system will change due to various factorsChapter 7 - Design and Implementation7Emergent System PropertyEmergent system propertiesAppear after systems implementedCAD systemsMultiple vendorsNo universal interchange formatAttempts plotting, consortiumAutodesk file formatInitially, just another formatAfter market share achieved, defacto standardLevel of sociotechnical system stack?

Chapter 7 - Design and Implementation8Emergent System PropertiesEmailUntil a sufficient population has the same technology, it is not accepted.Collective understanding of email affects its useEtiquette (forwarding, tone)AttachmentsStandards of organizations SecurityStorage allowancesLevel of Sociotechnical Systems Stack?Chapter 10 Socio Technical Systems9Non DeterminismVoter tracking databaseCreated by incorporation of data from StatesCountiesData providersStandardization of formats limitedUSPS, yes. Few follow the rulesChapter 7 - Design and Implementation10Multilevel IssuesIntegration of data from diverse sourcesDifferent 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 errorsChapter 7 - Design and Implementation11Wicked ProblemsNo clear solutionContradictory requirementsChanging requirementsToo many stakeholders

Chapter 7 - Design and Implementation12Gradebook SystemGoal: coordinate gradebook information.Master Database of Teachers, Classes, Students, GradesIndividual database at teacher computerPeriodic grade reporting electronicallyPre- internetData cardIssuesAcceptance, training, integrationChapter 7 - Design and Implementation13GIS SystemGeograpic Information SystemDatanbase of geographic featuresStreetsProperties, Ownership, EasementsGas, Electric, Phone linesPolitical Boundaries (precincts, zip codes, )UsesRight of way procurementsMaintenance diggingPublic announcementsIssues: Usability of system before data set up

Chapter 7 - Design and Implementation14Group ExerciseDistributed in classChapter 7 - Design and Implementation15StagesProcurementDevelopmentOperationChapter 7 - Design and Implementation16

Recommended

View more >