《Software Engineering Ethics - CSSE Center for Systems ：软件工程伦理为中心系统的话.ppt》由会员分享，可在线阅读，更多相关《Software Engineering Ethics - CSSE Center for Systems ：软件工程伦理为中心系统的话.ppt（28页珍藏版）》请在三一文库上搜索。
1、 USC-CSSE,1,Barry Boehm Fall 2011,Software Engineering Ethics,1/29/2020, USC-CSSE,2,Outline,Definitions and context Power to do public harm or good ACM/IEEE Software Engineering Code of Ethics Principles and examples Rawls Theory of Justice Relation to stakeholder win-win Case study: Mercy Hospital
2、Integrating ethics into daily software engineering practices VBSE/MBASE/Win Win Spiral Model CS 577 ethics situations,1/29/2020, USC-CSSE,3,Definition of “Ethics” -Webster, 1993,The discipline dealing with what is good and bad And with moral duty and obligation A theory, system, or set of moral prin
3、ciples or values The principles of conduct governing an individual or group Professional ethics,1/29/2020, USC-CSSE,4,Context,Software engineers have increasing power to do public harm or good Intellectual property, privacy, confidentiality, quality of work, fairness, liability, risk disclosure, con
4、flict of interest, unauthorized access Professional societies have developed codes of ethics Hard to integrate value-based ethics into value-neutral software engineering practices VBSE/MBASE/Win Win Spiral enable ethics integration,1/29/2020, USC-CSSE,5,Power to Do Public Harm or Good I,Intellectual
5、 Property: use without credit; use copyrighted material Privacy: credit, health, personal information Confidentiality: competitive information, political sensitivity Quality of work: many dimensions; see table,1/29/2020, USC-CSSE,6,Example: Confidentiality,Government agency hires company to support
6、SW procurement Provides data under nondisclosure agreement Employee and company consultant prepare cost estimate Employee: “ I dont see how anyone can do all this for $8M” Consultant provides $8M target cost to some bidders Government agency angry with company for leak Whose fault? How could it be a
7、voided?,1/29/2020, USC-CSSE,7,Quality Concerns Vary by Stakeholders Role,Acquirers,Administrators,Developers, Maintainers,System Controllers,Information Consumers,Info Brokers,System Dependents,Info Suppliers,Stakeholder Classes,*Critical *Significant 0 Insignificant or indirect,1/29/2020, USC-CSSE,
8、8,Power to Do Public Harm or Good - II,Fairness: equality of opportunity/treatment; fair reward system Liability: accountability; parity of authority and responsibility Risk Disclosure: safety tests, COTS capabilities; schedule slips Conflict of Interest: source selection; personnel or product revie
9、ws Unauthorized Access: reading, copying, modifying; denial of service,1/29/2020, USC-CSSE,9,Examples: Fairness,Enron software to schedule power outages, raise prices Suppose you had been asked to develop it? Urban fire dispatching system Inefficient old system caused $700M property loss New-system
10、spec. includes dispatching algorithm to minimize property loss Any fairness issues?,1/29/2020, USC-CSSE,10,CS 577 Ethics Accountability,Honoring commitments to CS 577b Team LCA Life Cycle Plan for 577b should identify 577b continuing team members and roles. If you signed that you will continue in 57
11、7b in the basic 577a questionnaire, we are expecting you to honor your commitment. If you are considering not honoring your commitment, please meet with me as soon as possible.,1/29/2020, USC-CSSE,11,Example: Safety Tests,Your company is delivering a drug prescription fulfillment system Reusing soft
12、ware from a warehouse inventory system You are the quality assurance manager With company responsibility for certifying product safety The software has passed all the contracted tests But many off-nominal conditions untested Some have shown unsafe outcomes You feel more off-nominal testing if necess
13、ary Company president says if you dont certify safety by delivery date, company may go out of business What should you do?,1/29/2020, USC-CSSE,12,ACM/IEE Software Engineering Code of Ethics -Table of Contents,Products: achievable goals, realistic estimates, high quality Public: safety, respect of di
14、versity, public interest first Judgment: objectivity, no bribes or conflicts of interest Client and Employer: no employer-adverse interests, surface problems Management: fair, ethical work rules, due process for violations Profession: support profession and ethics code, dont misrepresent software Co
15、lleagues: credit colleagues work, give colleagues a fair hearing Self: improve your technical and ethical knowledge and practices,1/29/2020, USC-CSSE,13,Code of Ethics 2. Public,2.01 Disclose any software-related dangers 2.02 Approve only safe, well tested software 2.03 Only sign documents in area o
16、f competence 2.04 Cooperate on matters of public concern 2.05 Produce software that respects diversity 2.06 Be fair and truthful in all matters 2.07 Always put the publics interest first 2.08 Donate professional skills to good causes 2.10 Accept responsibility for your own work,1/29/2020, USC-CSSE,1
17、4,Code of Ethics 4. Client and Employer,4.01 Provide services only where competent 4.02 Ensure resources are authentically approved 4.03 Only use property as authorized by the owner 4.04 Do not use illegally obtained software 4.05 Honor confidentiality of information 4.06 Raise matters of social con
18、cern 4.07 Inform when a project becomes problematic 4.08 Accept no detrimental outside work 4.09 Represent no interests adverse to your employer,1/29/2020, USC-CSSE,15,Outline,Definitions and context Power to do public harm or good ACM/IEEE Software Engineering Code of Ethics Principles and examples
19、 Rawls Theory of Justice Relation to stakeholder win-win Case study: Mercy Hospital Integrating ethics into daily software engineering practices VBSE/MBASE/Win Win Spiral Model CS 577 ethics situations,1/29/2020, USC-CSSE,16,Rawls Theory of Justice (1971) -Following Collins et al., “How Good Is Good
20、 Enough?” Comm.ACM, Jan. 1994,Fair rules of conduct Principles of justice Participants and obligations Provider (developer) Buyer (acquirer) User(s) Penumbra (general public) Negotiate mutually satisfactory (win-win) agreements,1/29/2020, USC-CSSE,17,Rawls Theory of Justice - II,Fair rules of conduc
21、t Negotiation among interested parties Veil of ignorance (about what affects whom) Rationality Principles Least Advantaged - dont increase harm to them Harm = probability x magnitude (risk exposure) Risking harm - dont risk increasing harm Dont use “low-threat” software in “high-threat” context Publ
22、icity test - defensible with honor before an informed public Use for difficult cost-benefit tradeoffs,1/29/2020, USC-CSSE,18,Obligations of the Software Provider,1/29/2020, USC-CSSE,19,Obligations of the Software Buyer,1/29/2020, USC-CSSE,20,Obligations of the Software User,1/29/2020, USC-CSSE,21,Ob
23、ligations of the Software Penumbra,1/29/2020, USC-CSSE,22,Case Study: Mercy Hospital Pharmacy System -Collins et al., 1994,Growing hospital Manual pharmacy information system reaching overload Spec developed for PC-based information system Rachel: VP, Records & Automation George: Chief Pharmacist Sy
24、stem developed by consultants Hired by George Rachel: test procedures Based on mature warehouse inventory system Budgeted 50% more testing than other bidders Installation & Training discovers problems Helen: consultant in charge of installation & training Ann: skeptical nurse cross-checking computer
25、 outputs,1/29/2020, USC-CSSE,23,Mercy Hospital Pharmacy System: Problems,Dosage problems from data entry errors 10x dosage; wrong patient Cross-checking incomplete; not trusted by some doctors Heavier data-entry load Formalizing automated procedures more info. needed Pharmacy info warehouse info Hel
26、en: Should go back to old system during cleanup George: - 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?,1/29/2020, USC-CSSE,24,Outline,Definitions and context Power to do public harm or go
27、od ACM/IEEE Software Engineering Code of Ethics Principles and examples Rawls Theory of Justice Relation to stakeholder win-win Case study: Mercy Hospital Integrating ethics into daily software engineering practices VBSE/MBASE/Win Win Spiral Model CS 577 ethics situations,1/29/2020, USC-CSSE,25,Merc
28、y Hospital : Use of VBSE/MBASE/Win Win Spiral,Results chain Add patient safety outcome, patient stakeholder representative Rework-business-workflows initiative, including safety checks; add clerical-staff stakeholder Stakeholder Win Win Patient representative: safety criteria; parallel-operation pha
29、se-in Clerical staff: prototype GUI, including safety-check support Business Case: includes added safety costs and benefits Risk Management: assess warehouse package safety, effects of workflow changes.,1/29/2020, USC-CSSE,26,Use of VBSE/MBASE/Win Win Spiral-II,Concurrent Engineering Concurrently ad
30、dress business workflows, GUI prototypes, COTS alternatives, feature prioritization, cost/schedule/benefits analysis, other risks Prepare to pass LCO, LCA, CCD, and IOC anchor point milestone reviews Monitoring and Control: Use Balanced Scorecard to track progress with respect to plans; apply correc
31、tive actions as necessary Change as Opportunity: Look for emerging COTS pharmacy-related fulfillment systems,1/29/2020, USC-CSSE,27,CS 577 Ethics Situations,Assuming your priorities match those of other stakeholders Users: GUI; quality factor priorities Maintainers: programming language, reuse, docu
32、mentation Customers/Owners: legacy compatibility, advanced vs. mature technology, full business case Favoring stakeholders who agree with you Excessive privacy protection: customers vs. users Weighting stakeholders equally on each issue Users on GUI; owners on legacy compatibility: developers on cos
33、t/schedule/risk Promising more than you can deliver Borrowing from other projects without credit Suppressing or delaying bad news,QR for LCO Package,1/29/2020, USC-CSSE,28,Conclusions,Software engineers have increasing power to do public harm or good Value-based codes of ethics are hard to integrate
34、 with value-neutral software engineering practices Rawls Theory of Justice enables constructive approach for integrating ethics into daily software engineering practice Stakeholder win-win with least-advantaged system dependents as success-critical stakeholders Win Win Spiral Model/MBASE/VBSE provides daily-practice framework,1/29/2020,