Social and Ethical Issues Rights and responsibilities of Software Developers.

Slides:



Advertisements
Similar presentations
System Integration Verification and Validation
Advertisements

Software Quality Assurance Plan
Control and Accounting Information Systems
Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.
Legislation & ICT By Savannah Inkster. By Savannah Computer Laws 1.Data Protection ActData Protection Act 2.Computer Misuse ActComputer Misuse Act 3.Copyright,
ICS 417: The ethics of ICT 4.2 The Ethics of Information and Communication Technologies (ICT) in Business by Simon Rogerson IMIS Journal May 1998.
Software Engineering Software quality. Software quality characteristics:  External: user is aware of. User cares about.  Internal: programmer is aware.
Ethics CS-480b Network Security Dick Steflik. ACM Code of Ethics This Code, consisting of 24 imperatives formulated as statements of personal responsibility,
1 An Overview of Computer Security computer security.
Chapter 7 Control and AIS Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 7-1.
Software Copyright. Learning Objectives: By the end of this topic you should be able to:
SE 555 Software Requirements & Specification Requirements Quality Attributes.
OHT 3.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The need for comprehensive software quality requirements Classification.
Maintenance of a system
Introduction to Software Testing
Software Testing and QA Theory and Practice (Chapter 16: Test Team Organization) © Naik & Tripathy 1 Software Testing and Quality Assurance Theory and.
Non-functional requirements
Information Systems Controls for System Reliability -Information Security-
OHT 3.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
Commercial Database Applications Testing. Test Plan Testing Strategy Testing Planning Testing Design (covered in other modules) Unit Testing (covered.
Term 2, 2011 Week 3. CONTENTS The physical design of a network Network diagrams People who develop and support networks Developing a network Supporting.
Chapter 8 Introduction to Internal Control Systems
Managing Software Quality
Quality Assurance ITEC Rick Price. Expectations This course is not purely a lecture course – Classroom participation is a large portion – Everyone.
ConfidentialPA Testing Mobile Applications A Model for Mobile Testing.
1 Software Testing and Quality Assurance Theory and Practice Chapter 16 Test Team Organization.
Module CC3002 Post Implementation Issues Lecture for Week 6 AY 2013 Spring.
Presented to President’s Cabinet. INTERNAL CONTROLS are the integration of the activities, plans, attitudes, policies and efforts of the people of an.
Information ITIL Technology Infrastructure Library ITIL.
Software Inspection A basic tool for defect removal A basic tool for defect removal Urgent need for QA and removal can be supported by inspection Urgent.
Introduction to Internal Control Systems
Vijay V Vijayakumar.  SOX Act  Difference between IT Management and IT Governance  Internal Controls  Frameworks for Implementing SOX  COSO - Committee.
University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Prepared By Ahmed Obaid Wassim Salem Supervised.
Software Engineering Quality What is Quality? Quality software is software that satisfies a user’s requirements, whether that is explicit or implicit.
CPRG 215 Introduction to Object-Oriented Programming with Java Module 1-Introduction to Java Topic 1.1 Basics of Java Produced by Harvey Peters, 2008 Copyright.
INFS 6225 Object-Oriented Systems Analysis & Design Chapter 11: Physical Architecture Layer Design.
Fundamentals I: Accounting Information Systems McGraw-Hill/Irwin Copyright © 2012 by The McGraw-Hill Companies, Inc. All rights reserved.
Bank Audit. Internal Audit Internal audit is an independent, objective assurance activity and can give valuable insight in providing assurance that major.
Test Team Organization. 2  Test Groups  Integration Test Group  System Test Group  Software Quality Assurance Group  Quality.
OHT 1.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The uniqueness of software quality assurance The environments for which.
Software quality factors
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
Ethics.
Prepared by: Hussein Alhashimi.  This course introduces fundamental concepts related to Quality Assurance and Measurements and Metrics in the software.
Csci5233 computer security & integrity 1 An Overview of Computer Security.
SEN 460 Software Quality Assurance
©2007 · Georges Merx and Ronald J. NormanSlide 1 Chapter 9 Software Quality Assurance.
Test Strategy Best Practices By Gabriel Rodriguez.
Copyright 2010, The World Bank Group. All Rights Reserved. Recommended Tabulations and Dissemination Section B.
Copyright © 2007 Pearson Education Canada 9-1 Chapter 9: Internal Controls and Control Risk.
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
Learning Intention Security of Information. Why protect files? To prevent unauthorised access to confidential information To prevent virus/corruption.
By the end of this lesson you will be able to: 1. Determine the preventive support measures that are in place at your school.
Lecture 5 Control and AIS Copyright © 2012 Pearson Education 7-1.
Governance, risk and ethics. 2 Section A: Governance and responsibility Section B: Internal control and review Section C: Identifying and assessing risk.
Welcome to the ICT Department Unit 3_5 Security Policies.
Information ITIL Technology Infrastructure Library ITIL.
PREPARED BY G.VIJAYA KUMAR ASST.PROFESSOR
Software Quality Control and Quality Assurance: Introduction
CHAPTER FOUR OVERVIEW SECTION ETHICS
SEVERITY & PRIORITY RELATIONSHIP
Software Quality Assurance Software Quality Factor
McCall’s Quality Factors
Governance & Control in ERP Systems
مقدمه اي بر مهندسي نيازمنديها
Introduction to Software Testing
INTRODUCTION TO PUBLIC FINANCE MANAGEMENT
Thursday’s Lecture Chemistry Building Musspratt Lecture Theatre,
CHAPTER FOUR OVERVIEW SECTION ETHICS
CS-480b Network Security Dick Steflik
Presentation transcript:

Social and Ethical Issues Rights and responsibilities of Software Developers.

Introduction  Software developers have both rights and responsibilities when developing software.  They have the right to be acknowledged and compensated for any work performed, and they have the responsibility to create a high quality product.

Rights of Software Developers

Rights  Copyright protection  Acknowledgment for work performed  Financial Compensation.

Copyright Protection  International laws apply to the copyright of created work such as software.  These laws are designed to protect the author of the work.  They try to prevent other people from illegally copying their work by issuing penalties such as fines and jail sentences.

Acknowledgment  If an author has contributed in any way to the development of software, they have the right to be acknowledged in some way for their work.  Usually financial, and name recognition.

Financial compensation  To encourage the development of new software, developers have the right to expect financial compensation for their work.

Responsibilities of Software Developers

Responsibilities  Authorship  Reliability  Quality  Response to problems  Code of conduct  Viruses.

Authorship  All contributors to the development of a piece of software need to be acknowledged.  If code has been outsourced or acquired elsewhere, the original authors need to be compensated in some way.

Reliability  Factors that may affect the reliability of a product include: –Hardware –Operating System –Other software –Run time errors

Reliability - Hardware  Software should be able to run on different hardware configurations, therefore it should be tested on different configurations.  Developers have a responsibility to perform this testing.

Reliability - Operating Systems  New software products should be compatible with various operating systems, and should not change default settings.  Again, thorough testing with different operating systems should be performed by the developer.

Reliability - Other Software  New software should not affect or be affected by other software applications.

Reliability - Run time errors  Error checking and detection modules should be a standard part of code. These prevent or recover an application from crashing.  An automatic save module should be implemented in the case of a ‘fatal error’  Thorough checking for errors is a major responsibility.

Quality  Quality Assurance departments are a major component of software development organisations.  They are used to ensure that a software product meets or exceeds user expectations.

Quality  Factors that can affect quality include: –Correctness –Reliability –Efficiency –Integrity –Useability –Maintainability –Flexibility –Testability –Portability –Re-useability –Interoperability

Response to problems  Customer service  Help Desks  Technical support  Identification and resolution of errors are all responsibilities of developers.

Code of Conduct  A Software Developers ‘Code of Conduct’ is a set of standards to which developers agree to abide by. (Example page 11 Davis).  It is the responsibility of individual developers to adhere to this code of conduct.

Viruses  It is a major responsibility of developers to ensure that viruses are not spread as a result of their product.  Policies should be in place to enforce this.

Activity  For each responsibility identified, outline a method that can be used to ensure the software developers responsibilities are maintained.