DOC PREVIEW
USC CSCI 510 - EC-26-SW_Ethics

This preview shows page 1-2-3-26-27-28 out of 28 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 28 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 28 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 28 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 28 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 28 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 28 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 28 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Software Engineering EthicsOutlineDefinition of “Ethics” -Webster, 1993ContextPower to Do Public Harm or Good – IExample: ConfidentialityQuality Concerns Vary by Stakeholders RolePower to Do Public Harm or Good - IIExamples: FairnessCS 577 Ethics AccountabilityExample: Safety TestsACM/IEE Software Engineering Code of Ethics -Table of ContentsCode of Ethics 2. PublicCode of Ethics 4. Client and EmployerSlide 15Rawls’ Theory of Justice (1971) -Following Collins et al., “How Good Is Good Enough?” Comm.ACM, Jan. 1994Rawls’ Theory of Justice - IIObligations of the Software ProviderObligations of the Software BuyerObligations of the Software UserObligations of the Software PenumbraCase Study: Mercy Hospital Pharmacy System -Collins et al., 1994Mercy Hospital Pharmacy System: ProblemsSlide 24Mercy Hospital : Use of VBSE/MBASE/Win Win SpiralUse of VBSE/MBASE/Win Win Spiral-IICS 577 Ethics SituationsConclusionsUniversity of Southern CaliforniaCenter for Software Engineering C S E USC© USC-CSSE 1Barry BoehmFall 2011Software Engineering Ethics01/14/19University of Southern CaliforniaCenter for Software Engineering C S E USC© USC-CSSE 2Outline•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•Integrating ethics into daily software engineering practices–VBSE/MBASE/Win Win Spiral Model–CS 577 ethics situations01/14/19University of Southern CaliforniaCenter for Software Engineering C S E USC© USC-CSSE 3Definition 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 principles or values•The principles of conduct governing an individual or group–Professional ethics01/14/19University of Southern CaliforniaCenter for Software Engineering C S E USC© USC-CSSE 4Context•Software engineers have increasing power to do public harm or good–Intellectual property, privacy, confidentiality, quality of work, fairness, liability, risk disclosure, conflict 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 integration01/14/19University of Southern CaliforniaCenter for Software Engineering C S E USC© USC-CSSE 5Power to Do Public Harm or Good – I•Intellectual Property: use without credit; use copyrighted material•Privacy: credit, health, personal information•Confidentiality: competitive information, political sensitivity•Quality of work: many dimensions; see table01/14/19University of Southern CaliforniaCenter for Software Engineering C S E USC© USC-CSSE 6Example: Confidentiality•Government agency hires company to support SW procurement–Provides data under nondisclosure agreement•Employee and company consultant prepare cost estimate–Employee: “ I don’t 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 avoided?01/14/19University of Southern CaliforniaCenter for Software Engineering C S E USC© USC-CSSE 7Quality Concerns Vary by Stakeholders Role    Mission -    Protection    critical uncrit.     Safety  **  **  **    Security * ** ** **  **    Privacy **  *      Robustness          Reliability   ** **  ** * *  Availability   ** **  ** * *  Survivability  ** ** **  **   Quality of Service          Performance   ** ** * ** * *  Accuracy, Consistency **  ** ** * **  *  Accessibility, ease of use; *  ** ** ** **  *  difficulty of misuse         Evolvability   ** ** * * ** ** **Interoperability   **     * **Correctness       **  **Cost       *  **Schedule   *    **  **Reusability       ** * *AcquirersAdministratorsDevelopers, MaintainersSystem ControllersInformation ConsumersInfo BrokersSystem DependentsInfo SuppliersStakeholder Classes**Critical*Significant0 Insignificant orindirect01/14/19University of Southern CaliforniaCenter for Software Engineering C S E USC© USC-CSSE 8Power 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 reviews•Unauthorized Access: reading, copying, modifying; denial of service01/14/19University of Southern CaliforniaCenter for Software Engineering C S E USC© USC-CSSE 9Examples: 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 spec. includes dispatching algorithm to minimize property loss•Any fairness issues?01/14/19University of Southern CaliforniaCenter for Software Engineering C S E USC© USC-CSSE 10CS 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 577b 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. 01/14/19University of Southern CaliforniaCenter for Software Engineering C S E USC© USC-CSSE 11Example: Safety Tests•Your company is delivering a drug prescription fulfillment system–Reusing software 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 necessary•Company president says if


View Full Document

USC CSCI 510 - EC-26-SW_Ethics

Download EC-26-SW_Ethics
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view EC-26-SW_Ethics and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view EC-26-SW_Ethics 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?