SlideShare a Scribd company logo
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 1
Introduction
 Getting started with software
engineering
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 2
Objectives
 To introduce software engineering and to explain
its importance
 To set out the answers to key questions about
software engineering
 To introduce ethical and professional issues and
to explain why they are of concern to software
engineers
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 3
Topics covered
 FAQs about software engineering
 Professional and ethical responsibility
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 4
 The economies of ALL developed nations are
dependent on software
 More and more systems are software controlled
 Software engineering is concerned with theories,
methods and tools for professional software
development
 Software engineering expenditure represents a
significant fraction of GNP in all developed
countries
Software engineering
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 5
 Software costs often dominate system costs. The
costs of software on a PC are often greater than
the hardware cost
 Software costs more to maintain than it does to
develop. For systems with a long life,
maintenance costs may be several times
development costs
 Software engineering is concerned with cost-
effective software development
Software costs
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 6
FAQs about software engineering
 What is software?
 What is software engineering?
 What is the difference between software
engineering and computer science?
 What is the difference between software
engineering and system engineering?
 What is a software process?
 What is a software process model?
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 7
FAQs about software engineering
 What are the costs of software engineering?
 What are software engineering methods?
 What is CASE (Computer-Aided Software
Engineering)
 What are the attributes of good software?
 What are the key challenges facing software
engineering?
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 8
What is software?
 Computer programs and associated
documentation
 Software products may be developed for a
particular customer or may be developed for a
general market
 Software products may be
• Generic - developed to be sold to a range of different customers
• Bespoke (custom) - developed for a single customer according
to their specification
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 9
What is software engineering?
 Software engineering is an engineering discipline
which is concerned with all aspects of software
production
 Software engineers should adopt a systematic and
organised approach to their work and use
appropriate tools and techniques depending on
the problem to be solved, the development
constraints and the resources available
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 10
What is the difference between software
engineering and computer science?
 Computer science is concerned with theory and
fundamentals; software engineering is concerned
with the practicalities of developing and
delivering useful software
 Computer science theories are currently
insufficient to act as a complete underpinning for
software engineering
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 11
What is the difference between software
engineering and system engineering?
 System engineering is concerned with all aspects
of computer-based systems development
including hardware, software and process
engineering. Software engineering is part of this
process
 System engineers are involved in system
specification, architectural design, integration and
deployment
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 12
What is a software process?
 A set of activities whose goal is the development
or evolution of software
 Generic activities in all software processes are:
• Specification - what the system should do and its development
constraints
• Development - production of the software system
• Validation - checking that the software is what the customer
wants
• Evolution - changing the software in response to changing
demands
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 13
What is a software process model?
 A simplified representation of a software process,
presented from a specific perspective
 Examples of process perspectives are
• Workflow perspective - sequence of activities
• Data-flow perspective - information flow
• Role/action perspective - who does what
 Generic process models
• Waterfall
• Evolutionary development
• Formal transformation
• Integration from reusable components
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 14
What are the costs of software engineering?
 Roughly 60% of costs are development costs,
40% are testing costs. For custom software,
evolution costs often exceed development costs
 Costs vary depending on the type of system being
developed and the requirements of system
attributes such as performance and system
reliability
 Distribution of costs depends on the development
model that is used
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 15
What are software engineering methods?
 Structured approaches to software development
which include system models, notations, rules,
design advice and process guidance
 Model descriptions
• Descriptions of graphical models which should be produced
 Rules
• Constraints applied to system models
 Recommendations
• Advice on good design practice
 Process guidance
• What activities to follow
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 16
What is CASE (Computer-Aided
Software Engineering)
 Software systems which are intended to provide
automated support for software process activities.
CASE systems are often used for method support
 Upper-CASE
• Tools to support the early process activities of requirements and
design
 Lower-CASE
• Tools to support later activities such as programming,
debugging and testing
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 17
What are the attributes of good software?
 The software should deliver the required
functionality and performance to the user and
should be maintainable, dependable and usable
 Maintainability
• Software must evolve to meet changing needs
 Dependability
• Software must be trustworthy
 Efficiency
• Software should not make wasteful use of system resources
 Usability
• Software must be usable by the users for which it was designed
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 18
What are the key challenges facing
software engineering?
 Coping with legacy systems, coping with
increasing diversity and coping with demands for
reduced delivery times
 Legacy systems
• Old, valuable systems must be maintained and updated
 Heterogeneity
• Systems are distributed and include a mix of hardware and
software
 Delivery
• There is increasing pressure for faster delivery of software
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 19
Professional and ethical responsibility
 Software engineering involves wider
responsibilities than simply the application of
technical skills
 Software engineers must behave in an honest and
ethically responsible way if they are to be
respected as professionals
 Ethical behaviour is more than simply upholding
the law.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 20
Issues of professional responsibility
 Confidentiality
• Engineers should normally respect the confidentiality of their
employers or clients irrespective of whether or not a formal
confidentiality agreement has been signed.
 Competence
• Engineers should not misrepresent their level of competence.
They should not knowingly accept work which is outwith their
competence.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 21
Issues of professional responsibility
 Intellectual property rights
• Engineers should be aware of local laws governing the use of
intellectual property such as patents, copyright, etc. They should
be careful to ensure that the intellectual property of employers
and clients is protected.
 Computer misuse
• Software engineers should not use their technical skills to
misuse other people’s computers. Computer misuse ranges from
relatively trivial (game playing on an employer’s machine, say)
to extremely serious (dissemination of viruses).
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 22
ACM/IEEE Code of Ethics
 The professional societies in the US have
cooperated to produce a code of ethical practice.
 Members of these organisations sign up to the
code of practice when they join.
 The Code contains eight Principles related to the
behaviour of and decisions made by professional
software engineers, including practitioners,
educators, managers, supervisors and policy
makers, as well as trainees and students of the
profession.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 23
Code of ethics - preamble
 Preamble
• The short version of the code summarizes aspirations at a high
level of the abstraction; the clauses that are included in the full
version give examples and details of how these aspirations
change the way we act as software engineering professionals.
Without the aspirations, the details can become legalistic and
tedious; without the details, the aspirations can become high
sounding but empty; together, the aspirations and the details
form a cohesive code.
• Software engineers shall commit themselves to making the
analysis, specification, design, development, testing and
maintenance of software a beneficial and respected profession.
In accordance with their commitment to the health, safety and
welfare of the public, software engineers shall adhere to the
following Eight Principles:
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 24
Code of ethics - principles
 1. PUBLIC
• Software engineers shall act consistently with the public
interest.
 2. CLIENT AND EMPLOYER
• Software engineers shall act in a manner that is in the
best interests of their client and employer consistent with
the public interest.
 3. PRODUCT
• Software engineers shall ensure that their products and
related modifications meet the highest professional
standards possible.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 25
Code of ethics - principles
 JUDGMENT
• Software engineers shall maintain integrity and
independence in their professional judgment.
 5. MANAGEMENT
• Software engineering managers and leaders shall
subscribe to and promote an ethical approach to the
management of software development and maintenance.
 6. PROFESSION
• Software engineers shall advance the integrity and
reputation of the profession consistent with the public
interest.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 26
Code of ethics - principles
 7. COLLEAGUES
• Software engineers shall be fair to and supportive of their
colleagues.
 8. SELF
• Software engineers shall participate in lifelong learning
regarding the practice of their profession and shall
promote an ethical approach to the practice of the
profession.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 27
Ethical dilemmas
 Disagreement in principle with the policies of
senior management
 Your employer acts in an unethical way and
releases a safety-critical system without finishing
the testing of the system
 Participation in the development of military
weapons systems or nuclear systems
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 28
Key points
 Software engineering is an engineering discipline which is
concerned with all aspects of software production.
 Software products consist of developed programs and
associated documentation. Essential product attributes are
maintainability, dependability, efficiency and usability.
 The software process consists of activities which are involved
in developing software products. Basic activities are software
specification, development, validation and evolution.
 Methods are organised ways of producing software. They include
suggestions for the process to be followed, the notations to be used,
rules governing the system descriptions which are produced and
design guidelines.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 29
Key points
 CASE tools are software systems which are designed to
support routine activities in the software process such as
editing design diagrams, checking diagram consistency and
keeping track of program tests which have been run.
 Software engineers have responsibilities to the engineering
profession and society. They should not simply be concerned
with technical issues.
 Professional societies publish codes of conduct which set out
the standards of behaviour expected of their members.

More Related Content

PDF
Ian_Sommerville_Software_Engineering_6th.pdf
PDF
software engineering ch-1
PPT
ch1-An Introduction to Software Engineering.ppt
PPT
Introduction_ to _Software _Engineering_
PPTX
0273710133 pp01v2
PPT
Introduction to Software Enigneering
PPT
PDF
Software Engineering - Ch1
Ian_Sommerville_Software_Engineering_6th.pdf
software engineering ch-1
ch1-An Introduction to Software Engineering.ppt
Introduction_ to _Software _Engineering_
0273710133 pp01v2
Introduction to Software Enigneering
Software Engineering - Ch1

Similar to SOFTWAREENGINEERING CONCEPTS INJNTUK MO (20)

PDF
PDF
01 unidad i introduccion
PDF
PDF
merged (1).pdf
PPTX
Week1.pptx
PPT
Lo 18
PPTX
SE - Lecture 1 - Introduction to S Engineering.pptx
PPTX
1-SUMSEM2024-25_CSI3014_TH_VL2024250700241_2025-05-13_Reference-Material-I.pptx
PPT
ch1_introduction.pptgtsytrsytryhtrhgrreqreedwds
PDF
sw1.pdf
PPTX
Veternary Medicene Data management tool for ppt
PPTX
software engineerning maetrial for developing
PPT
Software Engineering
PPT
ch1_introduction.ppt
PPT
ch1_introduction (1).ppt
PPT
ch1_introduction (2).ppt
PPT
SE UNIT 1 NOTES OF SE SOFTWARE ENGG AND SE
PPT
SE-Lecture1.ppt
PPTX
Slidesnumber1of the main course and this is the final show
01 unidad i introduccion
merged (1).pdf
Week1.pptx
Lo 18
SE - Lecture 1 - Introduction to S Engineering.pptx
1-SUMSEM2024-25_CSI3014_TH_VL2024250700241_2025-05-13_Reference-Material-I.pptx
ch1_introduction.pptgtsytrsytryhtrhgrreqreedwds
sw1.pdf
Veternary Medicene Data management tool for ppt
software engineerning maetrial for developing
Software Engineering
ch1_introduction.ppt
ch1_introduction (1).ppt
ch1_introduction (2).ppt
SE UNIT 1 NOTES OF SE SOFTWARE ENGG AND SE
SE-Lecture1.ppt
Slidesnumber1of the main course and this is the final show
Ad

More from tpvvsreenivasarao (11)

PPT
funcrttionadl asfkjoefweno alsdfjoweefwf
PPTX
unit-4-part-1- spectroscopy2chemist.pptx
PPTX
BASIC TREE AND TYPES OF DI CONCEPTS.pptx
PPT
CNS_06 DES ALGORITHM AND ITS IMPLEMENTAT
PPT
ch-15 Key-Management IN CNS STUDENTSASEE
PPT
ch-13 Digital Signature FOR CNS STUDENTS
PPT
AI algorithms with alpha beta stratagy 1
PPT
concepts-of-computer.ppt
PPTX
lec-9.pptx
PPT
i-Twin-Limitless-Pendrive-Technology.ppt
PPT
CSE WIBREE ppt.ppt
funcrttionadl asfkjoefweno alsdfjoweefwf
unit-4-part-1- spectroscopy2chemist.pptx
BASIC TREE AND TYPES OF DI CONCEPTS.pptx
CNS_06 DES ALGORITHM AND ITS IMPLEMENTAT
ch-15 Key-Management IN CNS STUDENTSASEE
ch-13 Digital Signature FOR CNS STUDENTS
AI algorithms with alpha beta stratagy 1
concepts-of-computer.ppt
lec-9.pptx
i-Twin-Limitless-Pendrive-Technology.ppt
CSE WIBREE ppt.ppt
Ad

Recently uploaded (20)

PPTX
Construction Project Organization Group 2.pptx
PPTX
Infosys Presentation by1.Riyan Bagwan 2.Samadhan Naiknavare 3.Gaurav Shinde 4...
PDF
Evaluating the Democratization of the Turkish Armed Forces from a Normative P...
PDF
BMEC211 - INTRODUCTION TO MECHATRONICS-1.pdf
PPTX
CH1 Production IntroductoryConcepts.pptx
PPTX
Welding lecture in detail for understanding
PDF
Operating System & Kernel Study Guide-1 - converted.pdf
PPTX
Recipes for Real Time Voice AI WebRTC, SLMs and Open Source Software.pptx
PPTX
Foundation to blockchain - A guide to Blockchain Tech
PPTX
Geodesy 1.pptx...............................................
PDF
Model Code of Practice - Construction Work - 21102022 .pdf
PDF
keyrequirementskkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk
DOCX
ASol_English-Language-Literature-Set-1-27-02-2023-converted.docx
PDF
July 2025 - Top 10 Read Articles in International Journal of Software Enginee...
PPTX
Lecture Notes Electrical Wiring System Components
PDF
Embodied AI: Ushering in the Next Era of Intelligent Systems
PDF
R24 SURVEYING LAB MANUAL for civil enggi
PPTX
M Tech Sem 1 Civil Engineering Environmental Sciences.pptx
PDF
SM_6th-Sem__Cse_Internet-of-Things.pdf IOT
PPTX
KTU 2019 -S7-MCN 401 MODULE 2-VINAY.pptx
Construction Project Organization Group 2.pptx
Infosys Presentation by1.Riyan Bagwan 2.Samadhan Naiknavare 3.Gaurav Shinde 4...
Evaluating the Democratization of the Turkish Armed Forces from a Normative P...
BMEC211 - INTRODUCTION TO MECHATRONICS-1.pdf
CH1 Production IntroductoryConcepts.pptx
Welding lecture in detail for understanding
Operating System & Kernel Study Guide-1 - converted.pdf
Recipes for Real Time Voice AI WebRTC, SLMs and Open Source Software.pptx
Foundation to blockchain - A guide to Blockchain Tech
Geodesy 1.pptx...............................................
Model Code of Practice - Construction Work - 21102022 .pdf
keyrequirementskkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk
ASol_English-Language-Literature-Set-1-27-02-2023-converted.docx
July 2025 - Top 10 Read Articles in International Journal of Software Enginee...
Lecture Notes Electrical Wiring System Components
Embodied AI: Ushering in the Next Era of Intelligent Systems
R24 SURVEYING LAB MANUAL for civil enggi
M Tech Sem 1 Civil Engineering Environmental Sciences.pptx
SM_6th-Sem__Cse_Internet-of-Things.pdf IOT
KTU 2019 -S7-MCN 401 MODULE 2-VINAY.pptx

SOFTWAREENGINEERING CONCEPTS INJNTUK MO

  • 1. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 1 Introduction  Getting started with software engineering
  • 2. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 2 Objectives  To introduce software engineering and to explain its importance  To set out the answers to key questions about software engineering  To introduce ethical and professional issues and to explain why they are of concern to software engineers
  • 3. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 3 Topics covered  FAQs about software engineering  Professional and ethical responsibility
  • 4. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 4  The economies of ALL developed nations are dependent on software  More and more systems are software controlled  Software engineering is concerned with theories, methods and tools for professional software development  Software engineering expenditure represents a significant fraction of GNP in all developed countries Software engineering
  • 5. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 5  Software costs often dominate system costs. The costs of software on a PC are often greater than the hardware cost  Software costs more to maintain than it does to develop. For systems with a long life, maintenance costs may be several times development costs  Software engineering is concerned with cost- effective software development Software costs
  • 6. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 6 FAQs about software engineering  What is software?  What is software engineering?  What is the difference between software engineering and computer science?  What is the difference between software engineering and system engineering?  What is a software process?  What is a software process model?
  • 7. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 7 FAQs about software engineering  What are the costs of software engineering?  What are software engineering methods?  What is CASE (Computer-Aided Software Engineering)  What are the attributes of good software?  What are the key challenges facing software engineering?
  • 8. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 8 What is software?  Computer programs and associated documentation  Software products may be developed for a particular customer or may be developed for a general market  Software products may be • Generic - developed to be sold to a range of different customers • Bespoke (custom) - developed for a single customer according to their specification
  • 9. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 9 What is software engineering?  Software engineering is an engineering discipline which is concerned with all aspects of software production  Software engineers should adopt a systematic and organised approach to their work and use appropriate tools and techniques depending on the problem to be solved, the development constraints and the resources available
  • 10. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 10 What is the difference between software engineering and computer science?  Computer science is concerned with theory and fundamentals; software engineering is concerned with the practicalities of developing and delivering useful software  Computer science theories are currently insufficient to act as a complete underpinning for software engineering
  • 11. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 11 What is the difference between software engineering and system engineering?  System engineering is concerned with all aspects of computer-based systems development including hardware, software and process engineering. Software engineering is part of this process  System engineers are involved in system specification, architectural design, integration and deployment
  • 12. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 12 What is a software process?  A set of activities whose goal is the development or evolution of software  Generic activities in all software processes are: • Specification - what the system should do and its development constraints • Development - production of the software system • Validation - checking that the software is what the customer wants • Evolution - changing the software in response to changing demands
  • 13. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 13 What is a software process model?  A simplified representation of a software process, presented from a specific perspective  Examples of process perspectives are • Workflow perspective - sequence of activities • Data-flow perspective - information flow • Role/action perspective - who does what  Generic process models • Waterfall • Evolutionary development • Formal transformation • Integration from reusable components
  • 14. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 14 What are the costs of software engineering?  Roughly 60% of costs are development costs, 40% are testing costs. For custom software, evolution costs often exceed development costs  Costs vary depending on the type of system being developed and the requirements of system attributes such as performance and system reliability  Distribution of costs depends on the development model that is used
  • 15. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 15 What are software engineering methods?  Structured approaches to software development which include system models, notations, rules, design advice and process guidance  Model descriptions • Descriptions of graphical models which should be produced  Rules • Constraints applied to system models  Recommendations • Advice on good design practice  Process guidance • What activities to follow
  • 16. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 16 What is CASE (Computer-Aided Software Engineering)  Software systems which are intended to provide automated support for software process activities. CASE systems are often used for method support  Upper-CASE • Tools to support the early process activities of requirements and design  Lower-CASE • Tools to support later activities such as programming, debugging and testing
  • 17. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 17 What are the attributes of good software?  The software should deliver the required functionality and performance to the user and should be maintainable, dependable and usable  Maintainability • Software must evolve to meet changing needs  Dependability • Software must be trustworthy  Efficiency • Software should not make wasteful use of system resources  Usability • Software must be usable by the users for which it was designed
  • 18. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 18 What are the key challenges facing software engineering?  Coping with legacy systems, coping with increasing diversity and coping with demands for reduced delivery times  Legacy systems • Old, valuable systems must be maintained and updated  Heterogeneity • Systems are distributed and include a mix of hardware and software  Delivery • There is increasing pressure for faster delivery of software
  • 19. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 19 Professional and ethical responsibility  Software engineering involves wider responsibilities than simply the application of technical skills  Software engineers must behave in an honest and ethically responsible way if they are to be respected as professionals  Ethical behaviour is more than simply upholding the law.
  • 20. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 20 Issues of professional responsibility  Confidentiality • Engineers should normally respect the confidentiality of their employers or clients irrespective of whether or not a formal confidentiality agreement has been signed.  Competence • Engineers should not misrepresent their level of competence. They should not knowingly accept work which is outwith their competence.
  • 21. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 21 Issues of professional responsibility  Intellectual property rights • Engineers should be aware of local laws governing the use of intellectual property such as patents, copyright, etc. They should be careful to ensure that the intellectual property of employers and clients is protected.  Computer misuse • Software engineers should not use their technical skills to misuse other people’s computers. Computer misuse ranges from relatively trivial (game playing on an employer’s machine, say) to extremely serious (dissemination of viruses).
  • 22. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 22 ACM/IEEE Code of Ethics  The professional societies in the US have cooperated to produce a code of ethical practice.  Members of these organisations sign up to the code of practice when they join.  The Code contains eight Principles related to the behaviour of and decisions made by professional software engineers, including practitioners, educators, managers, supervisors and policy makers, as well as trainees and students of the profession.
  • 23. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 23 Code of ethics - preamble  Preamble • The short version of the code summarizes aspirations at a high level of the abstraction; the clauses that are included in the full version give examples and details of how these aspirations change the way we act as software engineering professionals. Without the aspirations, the details can become legalistic and tedious; without the details, the aspirations can become high sounding but empty; together, the aspirations and the details form a cohesive code. • Software engineers shall commit themselves to making the analysis, specification, design, development, testing and maintenance of software a beneficial and respected profession. In accordance with their commitment to the health, safety and welfare of the public, software engineers shall adhere to the following Eight Principles:
  • 24. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 24 Code of ethics - principles  1. PUBLIC • Software engineers shall act consistently with the public interest.  2. CLIENT AND EMPLOYER • Software engineers shall act in a manner that is in the best interests of their client and employer consistent with the public interest.  3. PRODUCT • Software engineers shall ensure that their products and related modifications meet the highest professional standards possible.
  • 25. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 25 Code of ethics - principles  JUDGMENT • Software engineers shall maintain integrity and independence in their professional judgment.  5. MANAGEMENT • Software engineering managers and leaders shall subscribe to and promote an ethical approach to the management of software development and maintenance.  6. PROFESSION • Software engineers shall advance the integrity and reputation of the profession consistent with the public interest.
  • 26. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 26 Code of ethics - principles  7. COLLEAGUES • Software engineers shall be fair to and supportive of their colleagues.  8. SELF • Software engineers shall participate in lifelong learning regarding the practice of their profession and shall promote an ethical approach to the practice of the profession.
  • 27. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 27 Ethical dilemmas  Disagreement in principle with the policies of senior management  Your employer acts in an unethical way and releases a safety-critical system without finishing the testing of the system  Participation in the development of military weapons systems or nuclear systems
  • 28. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 28 Key points  Software engineering is an engineering discipline which is concerned with all aspects of software production.  Software products consist of developed programs and associated documentation. Essential product attributes are maintainability, dependability, efficiency and usability.  The software process consists of activities which are involved in developing software products. Basic activities are software specification, development, validation and evolution.  Methods are organised ways of producing software. They include suggestions for the process to be followed, the notations to be used, rules governing the system descriptions which are produced and design guidelines.
  • 29. ©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 29 Key points  CASE tools are software systems which are designed to support routine activities in the software process such as editing design diagrams, checking diagram consistency and keeping track of program tests which have been run.  Software engineers have responsibilities to the engineering profession and society. They should not simply be concerned with technical issues.  Professional societies publish codes of conduct which set out the standards of behaviour expected of their members.