《Software Engineering Ethics - CSSECenter for Systems ：软件工程伦理为中心系统的话.ppt》由会员分享，可在线阅读，更多相关《Software Engineering Ethics - CSSECenter for Systems ：软件工程伦理为中心系统的话.ppt（28页珍藏版）》请在三一办公上搜索。
1、 USC-CSSE,1,Barry BoehmFall 2011,Software Engineering Ethics,2/26/2023,USC-CSSE,2,Outline,Definitions and contextPower to do public harm or goodACM/IEEE Software Engineering Code of EthicsPrinciples and examplesRawls Theory of JusticeRelation to stakeholder win-winCase study:Mercy HospitalIntegratin
2、g ethics into daily software engineering practicesVBSE/MBASE/Win Win Spiral ModelCS 577 ethics situations,2/26/2023,USC-CSSE,3,Definition of“Ethics”-Webster,1993,The discipline dealing with what is good and badAnd with moral duty and obligationA theory,system,or set of moral principles or valuesThe
3、principles of conduct governing an individual or groupProfessional ethics,2/26/2023,USC-CSSE,4,Context,Software engineers have increasing power to do public harm or goodIntellectual property,privacy,confidentiality,quality of work,fairness,liability,risk disclosure,conflict of interest,unauthorized
4、accessProfessional societies have developed codes of ethicsHard to integrate value-based ethics into value-neutral software engineering practicesVBSE/MBASE/Win Win Spiral enable ethics integration,2/26/2023,USC-CSSE,5,Power to Do Public Harm or Good I,Intellectual Property:use without credit;use cop
5、yrighted materialPrivacy:credit,health,personal informationConfidentiality:competitive information,political sensitivityQuality of work:many dimensions;see table,2/26/2023,USC-CSSE,6,Example:Confidentiality,Government agency hires company to support SW procurementProvides data under nondisclosure ag
6、reementEmployee and company consultant prepare cost estimateEmployee:“I dont see how anyone can do all this for$8M”Consultant provides$8M target cost to some biddersGovernment agency angry with company for leakWhose fault?How could it be avoided?,2/26/2023,USC-CSSE,7,Quality Concerns Vary by Stakeho
7、lders Role,Acquirers,Administrators,Developers,Maintainers,System Controllers,Information Consumers,Info Brokers,System Dependents,Info Suppliers,Stakeholder Classes,*Critical*Significant0 Insignificant orindirect,2/26/2023,USC-CSSE,8,Power to Do Public Harm or Good-II,Fairness:equality of opportuni
8、ty/treatment;fair reward systemLiability:accountability;parity of authority and responsibilityRisk Disclosure:safety tests,COTS capabilities;schedule slipsConflict of Interest:source selection;personnel or product reviewsUnauthorized Access:reading,copying,modifying;denial of service,2/26/2023,USC-C
9、SSE,9,Examples:Fairness,Enron software to schedule power outages,raise pricesSuppose you had been asked to develop it?Urban fire dispatching systemInefficient old system caused$700M property lossNew-system spec.includes dispatching algorithm to minimize property lossAny fairness issues?,2/26/2023,US
10、C-CSSE,10,CS 577 Ethics Accountability,Honoring commitments to CS 577bTeam LCA Life Cycle Plan for 577b should identify 577b continuing team members and roles.If you signed that you will continue in 577b in the basic 577a questionnaire,we are expecting you to honor your commitment.If you are conside
11、ring not honoring your commitment,please meet with me as soon as possible.,2/26/2023,USC-CSSE,11,Example:Safety Tests,Your company is delivering a drug prescription fulfillment systemReusing software from a warehouse inventory systemYou are the quality assurance managerWith company responsibility fo
12、r certifying product safetyThe software has passed all the contracted testsBut many off-nominal conditions untestedSome have shown unsafe outcomesYou feel more off-nominal testing if necessaryCompany president says if you dont certify safety by delivery date,company may go out of businessWhat should
13、 you do?,2/26/2023,USC-CSSE,12,ACM/IEE Software Engineering Code of Ethics-Table of Contents,Products:achievable goals,realistic estimates,high qualityPublic:safety,respect of diversity,public interest firstJudgment:objectivity,no bribes or conflicts of interestClient and Employer:no employer-advers
14、e interests,surface problemsManagement:fair,ethical work rules,due process for violationsProfession:support profession and ethics code,dont misrepresent softwareColleagues:credit colleagues work,give colleagues a fair hearingSelf:improve your technical and ethical knowledge and practices,2/26/2023,U
15、SC-CSSE,13,Code of Ethics 2.Public,2.01 Disclose any software-related dangers2.02 Approve only safe,well tested software2.03 Only sign documents in area of competence2.04 Cooperate on matters of public concern2.05 Produce software that respects diversity2.06 Be fair and truthful in all matters2.07 A
16、lways put the publics interest first2.08 Donate professional skills to good causes2.10 Accept responsibility for your own work,2/26/2023,USC-CSSE,14,Code of Ethics 4.Client and Employer,4.01 Provide services only where competent4.02 Ensure resources are authentically approved4.03 Only use property a
17、s authorized by the owner4.04 Do not use illegally obtained software4.05 Honor confidentiality of information4.06 Raise matters of social concern4.07 Inform when a project becomes problematic4.08 Accept no detrimental outside work4.09 Represent no interests adverse to your employer,2/26/2023,USC-CSS
18、E,15,Outline,Definitions and contextPower to do public harm or goodACM/IEEE Software Engineering Code of EthicsPrinciples and examplesRawls Theory of JusticeRelation to stakeholder win-winCase study:Mercy HospitalIntegrating ethics into daily software engineering practicesVBSE/MBASE/Win Win Spiral M
19、odelCS 577 ethics situations,2/26/2023,USC-CSSE,16,Rawls Theory of Justice(1971)-Following Collins et al.,“How Good Is Good Enough?”Comm.ACM,Jan.1994,Fair rules of conductPrinciples of justiceParticipants and obligationsProvider(developer)Buyer(acquirer)User(s)Penumbra(general public)Negotiate mutua
20、lly satisfactory(win-win)agreements,2/26/2023,USC-CSSE,17,Rawls Theory of Justice-II,Fair rules of conductNegotiation among interested partiesVeil of ignorance(about what affects whom)RationalityPrinciplesLeast Advantaged-dont increase harm to themHarm=probability x magnitude(risk exposure)Risking h
21、arm-dont risk increasing harmDont use“low-threat”software in“high-threat”contextPublicity test-defensible with honor before an informed publicUse for difficult cost-benefit tradeoffs,2/26/2023,USC-CSSE,18,Obligations of the Software Provider,2/26/2023,USC-CSSE,19,Obligations of the Software Buyer,2/
22、26/2023,USC-CSSE,20,Obligations of the Software User,2/26/2023,USC-CSSE,21,Obligations of the Software Penumbra,2/26/2023,USC-CSSE,22,Case Study:Mercy Hospital Pharmacy System-Collins et al.,1994,Growing hospitalManual pharmacy information system reaching overloadSpec developed for PC-based informat
23、ion systemRachel:VP,Records&AutomationGeorge:Chief PharmacistSystem developed by consultantsHired by GeorgeRachel:test proceduresBased on mature warehouse inventory systemBudgeted 50%more testing than other biddersInstallation&Training discovers problemsHelen:consultant in charge of installation&tra
24、iningAnn:skeptical nurse cross-checking computer outputs,2/26/2023,USC-CSSE,23,Mercy Hospital Pharmacy System:Problems,Dosage problems from data entry errors10 x dosage;wrong patientCross-checking incomplete;not trusted by some doctorsHeavier data-entry loadFormalizing automated procedures more info
25、.neededPharmacy info warehouse infoHelen:Should go back to old system during cleanupGeorge:-Is old system less risky?How do we ensure cleanup will get it right?How much will cleanup cost?Future practice:How to anticipate,avoid similar problems?,2/26/2023,USC-CSSE,24,Outline,Definitions and contextPo
26、wer to do public harm or goodACM/IEEE Software Engineering Code of EthicsPrinciples and examplesRawls Theory of JusticeRelation to stakeholder win-winCase study:Mercy HospitalIntegrating ethics into daily software engineering practicesVBSE/MBASE/Win Win Spiral ModelCS 577 ethics situations,2/26/2023
27、,USC-CSSE,25,Mercy Hospital:Use of VBSE/MBASE/Win Win Spiral,Results chainAdd patient safety outcome,patient stakeholder representativeRework-business-workflows initiative,including safety checks;add clerical-staff stakeholderStakeholder Win WinPatient representative:safety criteria;parallel-operati
28、on phase-inClerical staff:prototype GUI,including safety-check supportBusiness Case:includes added safety costs and benefitsRisk Management:assess warehouse package safety,effects of workflow changes.,2/26/2023,USC-CSSE,26,Use of VBSE/MBASE/Win Win Spiral-II,Concurrent EngineeringConcurrently addres
29、s business workflows,GUI prototypes,COTS alternatives,feature prioritization,cost/schedule/benefits analysis,other risksPrepare to pass LCO,LCA,CCD,and IOC anchor point milestone reviewsMonitoring and Control:Use Balanced Scorecard to track progress with respect to plans;apply corrective actions as
30、necessaryChange as Opportunity:Look for emerging COTS pharmacy-related fulfillment systems,2/26/2023,USC-CSSE,27,CS 577 Ethics Situations,Assuming your priorities match those of other stakeholdersUsers:GUI;quality factor prioritiesMaintainers:programming language,reuse,documentationCustomers/Owners:
31、legacy compatibility,advanced vs.mature technology,full business caseFavoring stakeholders who agree with youExcessive privacy protection:customers vs.usersWeighting stakeholders equally on each issueUsers on GUI;owners on legacy compatibility:developers on cost/schedule/riskPromising more than you
32、can deliverBorrowing from other projects without creditSuppressing or delaying bad news,QR for LCO Package,2/26/2023,USC-CSSE,28,Conclusions,Software engineers have increasing power to do public harm or goodValue-based codes of ethics are hard to integrate with value-neutral software engineering practicesRawls Theory of Justice enables constructive approach for integrating ethics into daily software engineering practiceStakeholder win-win with least-advantaged system dependents as success-critical stakeholdersWin Win Spiral Model/MBASE/VBSE provides daily-practice framework,2/26/2023,
