SlideShare a Scribd company logo
1 of 31
Download to read offline
©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 1
An Introduction to Software
Engineering
©Ian Sommerville 2004 Software Engineering, 7th 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 2004 Software Engineering, 7th edition. Chapter 1 Slide 3
Topics covered
● FAQs about software engineering
● Professional and ethical responsibility
©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 4
Software engineering
● 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.
● Expenditure on software represents a
significant fraction of GNP in all developed
countries.
©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 5
Software costs
● Software costs often dominate computer 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.
©Ian Sommerville 2004 Software Engineering, 7th 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 2004 Software Engineering, 7th 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 2004 Software Engineering, 7th edition. Chapter 1 Slide 8
What is software?
● Computer programs and associated documentation such
as requirements, design models and user manuals.
● 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
e.g. PC software such as Excel or Word.
• Bespoke (custom) - developed for a single customer according
to their specification.
● New software can be created by developing new
programs, configuring generic software systems or
reusing existing software.
©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 9
What is software engineering?
● Software engineering is an engineering discipline
that 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 2004 Software Engineering, 7th 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 still insufficient to
act as a complete underpinning for software
engineering (unlike e.g. physics and electrical
engineering).
©Ian Sommerville 2004 Software Engineering, 7th 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 concerned with developing
the software infrastructure, control, applications
and databases in the system.
● System engineers are involved in system
specification, architectural design, integration
and deployment.
©Ian Sommerville 2004 Software Engineering, 7th 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 2004 Software Engineering, 7th 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;
• Iterative development;
• Component-based software engineering.
©Ian Sommerville 2004 Software Engineering, 7th 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 2004 Software Engineering, 7th edition. Chapter 1 Slide 15
Activity cost distribution
©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 16
Product development costs
©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 17
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 2004 Software Engineering, 7th edition. Chapter 1 Slide 18
What is CASE (Computer-Aided Software
Engineering)
● Software systems that 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 2004 Software Engineering, 7th edition. Chapter 1 Slide 19
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 acceptable.
● Maintainability
• Software must evolve to meet changing needs;
● Dependability
• Software must be trustworthy;
● Efficiency
• Software should not make wasteful use of system resources;
● Acceptability
• Software must accepted by the users for which it was designed.
This means it must be understandable, usable and compatible
with other systems.
©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 20
What are the key challenges facing software
engineering?
● Heterogeneity, delivery and trust.
● Heterogeneity
• Developing techniques for building software that can cope with
heterogeneous platforms and execution environments;
● Delivery
• Developing techniques that lead to faster delivery of software;
● Trust
• Developing techniques that demonstrate that software can be
trusted by its users.
©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 21
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 2004 Software Engineering, 7th edition. Chapter 1 Slide 22
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 2004 Software Engineering, 7th edition. Chapter 1 Slide 23
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 2004 Software Engineering, 7th edition. Chapter 1 Slide 24
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 2004 Software Engineering, 7th edition. Chapter 1 Slide 25
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 2004 Software Engineering, 7th edition. Chapter 1 Slide 26
Code of ethics - principles
● PUBLIC
• Software engineers shall act consistently with the public
interest.
● 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.
● PRODUCT
• Software engineers shall ensure that their products and related
modifications meet the highest professional standards possible.
©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 27
Code of ethics - principles
● JUDGMENT
• Software engineers shall maintain integrity and independence
in their professional judgment.
● MANAGEMENT
• Software engineering managers and leaders shall subscribe to
and promote an ethical approach to the management of
software development and maintenance.
● PROFESSION
• Software engineers shall advance the integrity and reputation of
the profession consistent with the public interest.
©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 28
Code of ethics - principles
● COLLEAGUES
• Software engineers shall be fair to and supportive of
their colleagues.
● 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 2004 Software Engineering, 7th edition. Chapter 1 Slide 29
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 2004 Software Engineering, 7th edition. Chapter 1 Slide 30
Key points
● Software engineering is an engineering discipline that 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 that 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 2004 Software Engineering, 7th edition. Chapter 1 Slide 31
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

What's hot

Software Process Models
Software Process ModelsSoftware Process Models
Software Process ModelsHassan A-j
 
Ch1-Software Engineering 9
Ch1-Software Engineering 9Ch1-Software Engineering 9
Ch1-Software Engineering 9Ian Sommerville
 
1.1 The nature of software.ppt
1.1 The nature of software.ppt1.1 The nature of software.ppt
1.1 The nature of software.pptJAYAPRIYAR7
 
Software requirement and specification
Software requirement and specificationSoftware requirement and specification
Software requirement and specificationAman Adhikari
 
Software Process Models
Software Process ModelsSoftware Process Models
Software Process ModelsAtul Karmyal
 
Formal Specification in Software Engineering SE9
Formal Specification in Software Engineering SE9Formal Specification in Software Engineering SE9
Formal Specification in Software Engineering SE9koolkampus
 
Chapter 01 software engineering pressman
Chapter 01  software engineering pressmanChapter 01  software engineering pressman
Chapter 01 software engineering pressmanRohitGoyal183
 
Software requirements engineering lecture 01
Software requirements engineering   lecture 01Software requirements engineering   lecture 01
Software requirements engineering lecture 01Abdul Basit
 
Software quality assurance
Software quality assuranceSoftware quality assurance
Software quality assuranceAman Adhikari
 
REQUIREMENT ENGINEERING
REQUIREMENT ENGINEERINGREQUIREMENT ENGINEERING
REQUIREMENT ENGINEERINGSaqib Raza
 
Ian Sommerville, Software Engineering, 9th Edition Ch 4
Ian Sommerville,  Software Engineering, 9th Edition Ch 4Ian Sommerville,  Software Engineering, 9th Edition Ch 4
Ian Sommerville, Software Engineering, 9th Edition Ch 4Mohammed Romi
 
Software Engineering Process Models
Software Engineering Process Models Software Engineering Process Models
Software Engineering Process Models Satya P. Joshi
 
Non Functional Requirement.
Non Functional Requirement.Non Functional Requirement.
Non Functional Requirement.Khushboo Shaukat
 
Organization and team structures
Organization and team structuresOrganization and team structures
Organization and team structuresNur Islam
 
SRS(software requirement specification)
SRS(software requirement specification)SRS(software requirement specification)
SRS(software requirement specification)Akash Kumar Dhameja
 

What's hot (20)

Software requirements
Software requirementsSoftware requirements
Software requirements
 
Software Process Models
Software Process ModelsSoftware Process Models
Software Process Models
 
Ch1-Software Engineering 9
Ch1-Software Engineering 9Ch1-Software Engineering 9
Ch1-Software Engineering 9
 
1.1 The nature of software.ppt
1.1 The nature of software.ppt1.1 The nature of software.ppt
1.1 The nature of software.ppt
 
Unit 2
Unit 2Unit 2
Unit 2
 
Software requirement and specification
Software requirement and specificationSoftware requirement and specification
Software requirement and specification
 
Software Process Models
Software Process ModelsSoftware Process Models
Software Process Models
 
Formal Specification in Software Engineering SE9
Formal Specification in Software Engineering SE9Formal Specification in Software Engineering SE9
Formal Specification in Software Engineering SE9
 
Chapter 01 software engineering pressman
Chapter 01  software engineering pressmanChapter 01  software engineering pressman
Chapter 01 software engineering pressman
 
Software engineering
Software engineeringSoftware engineering
Software engineering
 
Software requirements engineering lecture 01
Software requirements engineering   lecture 01Software requirements engineering   lecture 01
Software requirements engineering lecture 01
 
Software quality assurance
Software quality assuranceSoftware quality assurance
Software quality assurance
 
Software Evolution
Software EvolutionSoftware Evolution
Software Evolution
 
REQUIREMENT ENGINEERING
REQUIREMENT ENGINEERINGREQUIREMENT ENGINEERING
REQUIREMENT ENGINEERING
 
Software Engineering by Pankaj Jalote
Software Engineering by Pankaj JaloteSoftware Engineering by Pankaj Jalote
Software Engineering by Pankaj Jalote
 
Ian Sommerville, Software Engineering, 9th Edition Ch 4
Ian Sommerville,  Software Engineering, 9th Edition Ch 4Ian Sommerville,  Software Engineering, 9th Edition Ch 4
Ian Sommerville, Software Engineering, 9th Edition Ch 4
 
Software Engineering Process Models
Software Engineering Process Models Software Engineering Process Models
Software Engineering Process Models
 
Non Functional Requirement.
Non Functional Requirement.Non Functional Requirement.
Non Functional Requirement.
 
Organization and team structures
Organization and team structuresOrganization and team structures
Organization and team structures
 
SRS(software requirement specification)
SRS(software requirement specification)SRS(software requirement specification)
SRS(software requirement specification)
 

Viewers also liked

Software Engineering - Ch4
Software Engineering - Ch4Software Engineering - Ch4
Software Engineering - Ch4Siddharth Ayer
 
Software Engineering - Ch6
Software Engineering - Ch6Software Engineering - Ch6
Software Engineering - Ch6Siddharth Ayer
 
Software Engineering - Ch7
Software Engineering - Ch7Software Engineering - Ch7
Software Engineering - Ch7Siddharth Ayer
 
Software Engineering - Ch11
Software Engineering - Ch11Software Engineering - Ch11
Software Engineering - Ch11Siddharth Ayer
 
Software Engineering - Ch8
Software Engineering - Ch8Software Engineering - Ch8
Software Engineering - Ch8Siddharth Ayer
 
software engineering
software engineeringsoftware engineering
software engineeringramyavarkala
 
software engineering notes for cse/it fifth semester
software engineering notes for cse/it fifth semestersoftware engineering notes for cse/it fifth semester
software engineering notes for cse/it fifth semesterrajesh199155
 
Architectural patterns for real-time systems
Architectural patterns for real-time systemsArchitectural patterns for real-time systems
Architectural patterns for real-time systemssommerville-videos
 
Software engineering lecture notes
Software engineering lecture notesSoftware engineering lecture notes
Software engineering lecture notesSiva Ayyakutti
 
Software Engineering ppt
Software Engineering pptSoftware Engineering ppt
Software Engineering pptshruths2890
 
Software engineering presentation
Software engineering presentationSoftware engineering presentation
Software engineering presentationMJ Ferdous
 

Viewers also liked (11)

Software Engineering - Ch4
Software Engineering - Ch4Software Engineering - Ch4
Software Engineering - Ch4
 
Software Engineering - Ch6
Software Engineering - Ch6Software Engineering - Ch6
Software Engineering - Ch6
 
Software Engineering - Ch7
Software Engineering - Ch7Software Engineering - Ch7
Software Engineering - Ch7
 
Software Engineering - Ch11
Software Engineering - Ch11Software Engineering - Ch11
Software Engineering - Ch11
 
Software Engineering - Ch8
Software Engineering - Ch8Software Engineering - Ch8
Software Engineering - Ch8
 
software engineering
software engineeringsoftware engineering
software engineering
 
software engineering notes for cse/it fifth semester
software engineering notes for cse/it fifth semestersoftware engineering notes for cse/it fifth semester
software engineering notes for cse/it fifth semester
 
Architectural patterns for real-time systems
Architectural patterns for real-time systemsArchitectural patterns for real-time systems
Architectural patterns for real-time systems
 
Software engineering lecture notes
Software engineering lecture notesSoftware engineering lecture notes
Software engineering lecture notes
 
Software Engineering ppt
Software Engineering pptSoftware Engineering ppt
Software Engineering ppt
 
Software engineering presentation
Software engineering presentationSoftware engineering presentation
Software engineering presentation
 

Similar to Software Engineering - Ch1

Similar to Software Engineering - Ch1 (20)

Ch1
Ch1Ch1
Ch1
 
Introduction to Software Enigneering
Introduction to Software Enigneering Introduction to Software Enigneering
Introduction to Software Enigneering
 
Ian_Sommerville_Software_Engineering_6th.pdf
Ian_Sommerville_Software_Engineering_6th.pdfIan_Sommerville_Software_Engineering_6th.pdf
Ian_Sommerville_Software_Engineering_6th.pdf
 
software engineering ch-1
software engineering ch-1software engineering ch-1
software engineering ch-1
 
0273710133 pp01v2
0273710133 pp01v20273710133 pp01v2
0273710133 pp01v2
 
ch1.ppt
ch1.pptch1.ppt
ch1.ppt
 
01 unidad i introduccion
01 unidad i   introduccion01 unidad i   introduccion
01 unidad i introduccion
 
merged (1).pdf
merged (1).pdfmerged (1).pdf
merged (1).pdf
 
Software Engineering - Ch17
Software Engineering - Ch17Software Engineering - Ch17
Software Engineering - Ch17
 
Se introduction lec 1
Se  introduction lec 1Se  introduction lec 1
Se introduction lec 1
 
Week1.pptx
Week1.pptxWeek1.pptx
Week1.pptx
 
sw1.pdf
sw1.pdfsw1.pdf
sw1.pdf
 
Ch1
Ch1Ch1
Ch1
 
ch1_introduction (1).ppt
ch1_introduction (1).pptch1_introduction (1).ppt
ch1_introduction (1).ppt
 
ch1_introduction (2).ppt
ch1_introduction (2).pptch1_introduction (2).ppt
ch1_introduction (2).ppt
 
ch1_introduction.ppt
ch1_introduction.pptch1_introduction.ppt
ch1_introduction.ppt
 
SE UNIT 1 NOTES OF SE SOFTWARE ENGG AND SE
SE UNIT 1 NOTES OF SE SOFTWARE ENGG AND SESE UNIT 1 NOTES OF SE SOFTWARE ENGG AND SE
SE UNIT 1 NOTES OF SE SOFTWARE ENGG AND SE
 
Software Engineering
Software EngineeringSoftware Engineering
Software Engineering
 
Lecture 1.pptx
Lecture 1.pptxLecture 1.pptx
Lecture 1.pptx
 
SE-Lecture1.ppt
SE-Lecture1.pptSE-Lecture1.ppt
SE-Lecture1.ppt
 

Recently uploaded

"ML in Production",Oleksandr Bagan
"ML in Production",Oleksandr Bagan"ML in Production",Oleksandr Bagan
"ML in Production",Oleksandr BaganFwdays
 
TrustArc Webinar - How to Build Consumer Trust Through Data Privacy
TrustArc Webinar - How to Build Consumer Trust Through Data PrivacyTrustArc Webinar - How to Build Consumer Trust Through Data Privacy
TrustArc Webinar - How to Build Consumer Trust Through Data PrivacyTrustArc
 
Tampa BSides - Chef's Tour of Microsoft Security Adoption Framework (SAF)
Tampa BSides - Chef's Tour of Microsoft Security Adoption Framework (SAF)Tampa BSides - Chef's Tour of Microsoft Security Adoption Framework (SAF)
Tampa BSides - Chef's Tour of Microsoft Security Adoption Framework (SAF)Mark Simos
 
SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024Lorenzo Miniero
 
"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack
"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack
"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek SchlawackFwdays
 
DevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platformsDevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platformsSergiu Bodiu
 
How to write a Business Continuity Plan
How to write a Business Continuity PlanHow to write a Business Continuity Plan
How to write a Business Continuity PlanDatabarracks
 
Hyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdf
Hyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdfHyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdf
Hyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdfPrecisely
 
Streamlining Python Development: A Guide to a Modern Project Setup
Streamlining Python Development: A Guide to a Modern Project SetupStreamlining Python Development: A Guide to a Modern Project Setup
Streamlining Python Development: A Guide to a Modern Project SetupFlorian Wilhelm
 
Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!Commit University
 
What's New in Teams Calling, Meetings and Devices March 2024
What's New in Teams Calling, Meetings and Devices March 2024What's New in Teams Calling, Meetings and Devices March 2024
What's New in Teams Calling, Meetings and Devices March 2024Stephanie Beckett
 
Dev Dives: Streamline document processing with UiPath Studio Web
Dev Dives: Streamline document processing with UiPath Studio WebDev Dives: Streamline document processing with UiPath Studio Web
Dev Dives: Streamline document processing with UiPath Studio WebUiPathCommunity
 
Story boards and shot lists for my a level piece
Story boards and shot lists for my a level pieceStory boards and shot lists for my a level piece
Story boards and shot lists for my a level piececharlottematthew16
 
Anypoint Exchange: It’s Not Just a Repo!
Anypoint Exchange: It’s Not Just a Repo!Anypoint Exchange: It’s Not Just a Repo!
Anypoint Exchange: It’s Not Just a Repo!Manik S Magar
 
How AI, OpenAI, and ChatGPT impact business and software.
How AI, OpenAI, and ChatGPT impact business and software.How AI, OpenAI, and ChatGPT impact business and software.
How AI, OpenAI, and ChatGPT impact business and software.Curtis Poe
 
TeamStation AI System Report LATAM IT Salaries 2024
TeamStation AI System Report LATAM IT Salaries 2024TeamStation AI System Report LATAM IT Salaries 2024
TeamStation AI System Report LATAM IT Salaries 2024Lonnie McRorey
 
H2O.ai CEO/Founder: Sri Ambati Keynote at Wells Fargo Day
H2O.ai CEO/Founder: Sri Ambati Keynote at Wells Fargo DayH2O.ai CEO/Founder: Sri Ambati Keynote at Wells Fargo Day
H2O.ai CEO/Founder: Sri Ambati Keynote at Wells Fargo DaySri Ambati
 
Connect Wave/ connectwave Pitch Deck Presentation
Connect Wave/ connectwave Pitch Deck PresentationConnect Wave/ connectwave Pitch Deck Presentation
Connect Wave/ connectwave Pitch Deck PresentationSlibray Presentation
 

Recently uploaded (20)

"ML in Production",Oleksandr Bagan
"ML in Production",Oleksandr Bagan"ML in Production",Oleksandr Bagan
"ML in Production",Oleksandr Bagan
 
TrustArc Webinar - How to Build Consumer Trust Through Data Privacy
TrustArc Webinar - How to Build Consumer Trust Through Data PrivacyTrustArc Webinar - How to Build Consumer Trust Through Data Privacy
TrustArc Webinar - How to Build Consumer Trust Through Data Privacy
 
Tampa BSides - Chef's Tour of Microsoft Security Adoption Framework (SAF)
Tampa BSides - Chef's Tour of Microsoft Security Adoption Framework (SAF)Tampa BSides - Chef's Tour of Microsoft Security Adoption Framework (SAF)
Tampa BSides - Chef's Tour of Microsoft Security Adoption Framework (SAF)
 
SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024
 
"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack
"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack
"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack
 
DevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platformsDevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platforms
 
How to write a Business Continuity Plan
How to write a Business Continuity PlanHow to write a Business Continuity Plan
How to write a Business Continuity Plan
 
Hyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdf
Hyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdfHyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdf
Hyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdf
 
Streamlining Python Development: A Guide to a Modern Project Setup
Streamlining Python Development: A Guide to a Modern Project SetupStreamlining Python Development: A Guide to a Modern Project Setup
Streamlining Python Development: A Guide to a Modern Project Setup
 
E-Vehicle_Hacking_by_Parul Sharma_null_owasp.pptx
E-Vehicle_Hacking_by_Parul Sharma_null_owasp.pptxE-Vehicle_Hacking_by_Parul Sharma_null_owasp.pptx
E-Vehicle_Hacking_by_Parul Sharma_null_owasp.pptx
 
Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!
 
What's New in Teams Calling, Meetings and Devices March 2024
What's New in Teams Calling, Meetings and Devices March 2024What's New in Teams Calling, Meetings and Devices March 2024
What's New in Teams Calling, Meetings and Devices March 2024
 
Dev Dives: Streamline document processing with UiPath Studio Web
Dev Dives: Streamline document processing with UiPath Studio WebDev Dives: Streamline document processing with UiPath Studio Web
Dev Dives: Streamline document processing with UiPath Studio Web
 
Story boards and shot lists for my a level piece
Story boards and shot lists for my a level pieceStory boards and shot lists for my a level piece
Story boards and shot lists for my a level piece
 
DMCC Future of Trade Web3 - Special Edition
DMCC Future of Trade Web3 - Special EditionDMCC Future of Trade Web3 - Special Edition
DMCC Future of Trade Web3 - Special Edition
 
Anypoint Exchange: It’s Not Just a Repo!
Anypoint Exchange: It’s Not Just a Repo!Anypoint Exchange: It’s Not Just a Repo!
Anypoint Exchange: It’s Not Just a Repo!
 
How AI, OpenAI, and ChatGPT impact business and software.
How AI, OpenAI, and ChatGPT impact business and software.How AI, OpenAI, and ChatGPT impact business and software.
How AI, OpenAI, and ChatGPT impact business and software.
 
TeamStation AI System Report LATAM IT Salaries 2024
TeamStation AI System Report LATAM IT Salaries 2024TeamStation AI System Report LATAM IT Salaries 2024
TeamStation AI System Report LATAM IT Salaries 2024
 
H2O.ai CEO/Founder: Sri Ambati Keynote at Wells Fargo Day
H2O.ai CEO/Founder: Sri Ambati Keynote at Wells Fargo DayH2O.ai CEO/Founder: Sri Ambati Keynote at Wells Fargo Day
H2O.ai CEO/Founder: Sri Ambati Keynote at Wells Fargo Day
 
Connect Wave/ connectwave Pitch Deck Presentation
Connect Wave/ connectwave Pitch Deck PresentationConnect Wave/ connectwave Pitch Deck Presentation
Connect Wave/ connectwave Pitch Deck Presentation
 

Software Engineering - Ch1

  • 1. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 1 An Introduction to Software Engineering
  • 2. ©Ian Sommerville 2004 Software Engineering, 7th 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 2004 Software Engineering, 7th edition. Chapter 1 Slide 3 Topics covered ● FAQs about software engineering ● Professional and ethical responsibility
  • 4. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 4 Software engineering ● 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. ● Expenditure on software represents a significant fraction of GNP in all developed countries.
  • 5. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 5 Software costs ● Software costs often dominate computer 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.
  • 6. ©Ian Sommerville 2004 Software Engineering, 7th 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 2004 Software Engineering, 7th 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 2004 Software Engineering, 7th edition. Chapter 1 Slide 8 What is software? ● Computer programs and associated documentation such as requirements, design models and user manuals. ● 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 e.g. PC software such as Excel or Word. • Bespoke (custom) - developed for a single customer according to their specification. ● New software can be created by developing new programs, configuring generic software systems or reusing existing software.
  • 9. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 9 What is software engineering? ● Software engineering is an engineering discipline that 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 2004 Software Engineering, 7th 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 still insufficient to act as a complete underpinning for software engineering (unlike e.g. physics and electrical engineering).
  • 11. ©Ian Sommerville 2004 Software Engineering, 7th 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 concerned with developing the software infrastructure, control, applications and databases in the system. ● System engineers are involved in system specification, architectural design, integration and deployment.
  • 12. ©Ian Sommerville 2004 Software Engineering, 7th 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 2004 Software Engineering, 7th 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; • Iterative development; • Component-based software engineering.
  • 14. ©Ian Sommerville 2004 Software Engineering, 7th 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 2004 Software Engineering, 7th edition. Chapter 1 Slide 15 Activity cost distribution
  • 16. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 16 Product development costs
  • 17. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 17 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.
  • 18. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 18 What is CASE (Computer-Aided Software Engineering) ● Software systems that 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.
  • 19. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 19 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 acceptable. ● Maintainability • Software must evolve to meet changing needs; ● Dependability • Software must be trustworthy; ● Efficiency • Software should not make wasteful use of system resources; ● Acceptability • Software must accepted by the users for which it was designed. This means it must be understandable, usable and compatible with other systems.
  • 20. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 20 What are the key challenges facing software engineering? ● Heterogeneity, delivery and trust. ● Heterogeneity • Developing techniques for building software that can cope with heterogeneous platforms and execution environments; ● Delivery • Developing techniques that lead to faster delivery of software; ● Trust • Developing techniques that demonstrate that software can be trusted by its users.
  • 21. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 21 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.
  • 22. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 22 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.
  • 23. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 23 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).
  • 24. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 24 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.
  • 25. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 25 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:
  • 26. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 26 Code of ethics - principles ● PUBLIC • Software engineers shall act consistently with the public interest. ● 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. ● PRODUCT • Software engineers shall ensure that their products and related modifications meet the highest professional standards possible.
  • 27. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 27 Code of ethics - principles ● JUDGMENT • Software engineers shall maintain integrity and independence in their professional judgment. ● MANAGEMENT • Software engineering managers and leaders shall subscribe to and promote an ethical approach to the management of software development and maintenance. ● PROFESSION • Software engineers shall advance the integrity and reputation of the profession consistent with the public interest.
  • 28. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 28 Code of ethics - principles ● COLLEAGUES • Software engineers shall be fair to and supportive of their colleagues. ● 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.
  • 29. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 29 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.
  • 30. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 30 Key points ● Software engineering is an engineering discipline that 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 that 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.
  • 31. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 31 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.