SlideShare a Scribd company logo
1 of 31
An Introduction to Software
                        Engineering




©Ian Sommerville 2004   Software Engineering, 7th edition. Chapter 1   Slide 1
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 2
Topics covered



            FAQs about software engineering
            Professional and ethical responsibility




©Ian Sommerville 2004    Software Engineering, 7th edition. Chapter 1   Slide 3
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 4
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 5
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 6
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 7
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 8
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 9
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 10
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 11
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 12
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 13
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 14
W Develo
                        atDesign
                        er 5mode
                         fall0Integ
                        0 2 ration
                          5 7 10
                               50
                        Activity cost distribution

                        Specificat
                        It2 5 7 stem
                        erative1de
                        0 5 0 5 00
                        Specificat
                          Iterative
                               S1 0
                               y0
                        Compone
                           ineering
                        0 Develop
                          2 5Integ
                          5 0 ration
                               7
                               5
                        Specificat
                        Developm
                          003 ems
                        0 stem 400
                          1 2 0 dev
                        S Sstem
                        y y    0
©Ian Sommerville 2004         Software Engineering, 7th edition. Chapter 1   Slide 15
Product development costs



   0Develo
    2 5Sste
    5 0y 1
        70
        5
   Specific
©Ian Sommerville 2004   Software Engineering, 7th edition. Chapter 1   Slide 16
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 17
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 18
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 19
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 20
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 21
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 22
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 23
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 24
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 25
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 26
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 27
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 28
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 29
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 30
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.



©Ian Sommerville 2004     Software Engineering, 7th edition. Chapter 1   Slide 31

More Related Content

What's hot

Software evolution -- Good practices
Software evolution -- Good practicesSoftware evolution -- Good practices
Software evolution -- Good practicesNicolas Anquetil
 
Software evolution evangelisation
Software evolution evangelisationSoftware evolution evangelisation
Software evolution evangelisationNicolas Anquetil
 
Software engineering...basics
Software engineering...basicsSoftware engineering...basics
Software engineering...basicsdolon10
 
Requirements Engineering
Requirements EngineeringRequirements Engineering
Requirements EngineeringCS, NcState
 
Software engineering
Software engineeringSoftware engineering
Software engineeringh2eEdgar
 
Software engineering principles in system software design
Software engineering principles in system software designSoftware engineering principles in system software design
Software engineering principles in system software designTech_MX
 
Systems Engineering - a smarter way
Systems Engineering - a smarter waySystems Engineering - a smarter way
Systems Engineering - a smarter wayMark Borowski
 
Eight deadly defects in systems engineering and how to fix them
Eight deadly defects in systems engineering and how to fix themEight deadly defects in systems engineering and how to fix them
Eight deadly defects in systems engineering and how to fix themJoseph KAsser
 
Chapter 01
Chapter 01Chapter 01
Chapter 01ryan aja
 
E2 Manage Tech Design Implementation General 2010
E2 Manage Tech Design Implementation General 2010E2 Manage Tech Design Implementation General 2010
E2 Manage Tech Design Implementation General 2010bdwwork
 
SWE-401 - 2. Software Development life cycle (SDLC)
SWE-401 - 2. Software Development life cycle (SDLC)SWE-401 - 2. Software Development life cycle (SDLC)
SWE-401 - 2. Software Development life cycle (SDLC)ghayour abbas
 
Terry.cooke davies
Terry.cooke daviesTerry.cooke davies
Terry.cooke daviesNASAPMC
 
Software Engineering - Ch3
Software Engineering - Ch3Software Engineering - Ch3
Software Engineering - Ch3Siddharth Ayer
 
Software Architecture: Test Case Writing
Software Architecture: Test Case WritingSoftware Architecture: Test Case Writing
Software Architecture: Test Case WritingSitdhibong Laokok
 
Gen sessionthomas.riskofsystemproblemfinal23feb12
Gen sessionthomas.riskofsystemproblemfinal23feb12Gen sessionthomas.riskofsystemproblemfinal23feb12
Gen sessionthomas.riskofsystemproblemfinal23feb12NASAPMC
 
Unit 7 final
Unit 7 finalUnit 7 final
Unit 7 finalsietkcse
 

What's hot (19)

Software evolution -- Good practices
Software evolution -- Good practicesSoftware evolution -- Good practices
Software evolution -- Good practices
 
2 Process
2 Process2 Process
2 Process
 
SE
SESE
SE
 
Software evolution evangelisation
Software evolution evangelisationSoftware evolution evangelisation
Software evolution evangelisation
 
Software engineering...basics
Software engineering...basicsSoftware engineering...basics
Software engineering...basics
 
Requirements Engineering
Requirements EngineeringRequirements Engineering
Requirements Engineering
 
Software engineering
Software engineeringSoftware engineering
Software engineering
 
Software engineering principles in system software design
Software engineering principles in system software designSoftware engineering principles in system software design
Software engineering principles in system software design
 
Systems Engineering - a smarter way
Systems Engineering - a smarter waySystems Engineering - a smarter way
Systems Engineering - a smarter way
 
Eight deadly defects in systems engineering and how to fix them
Eight deadly defects in systems engineering and how to fix themEight deadly defects in systems engineering and how to fix them
Eight deadly defects in systems engineering and how to fix them
 
Chapter 01
Chapter 01Chapter 01
Chapter 01
 
E2 Manage Tech Design Implementation General 2010
E2 Manage Tech Design Implementation General 2010E2 Manage Tech Design Implementation General 2010
E2 Manage Tech Design Implementation General 2010
 
SWE-401 - 2. Software Development life cycle (SDLC)
SWE-401 - 2. Software Development life cycle (SDLC)SWE-401 - 2. Software Development life cycle (SDLC)
SWE-401 - 2. Software Development life cycle (SDLC)
 
Terry.cooke davies
Terry.cooke daviesTerry.cooke davies
Terry.cooke davies
 
Software Engineering - Ch3
Software Engineering - Ch3Software Engineering - Ch3
Software Engineering - Ch3
 
Software Architecture: Test Case Writing
Software Architecture: Test Case WritingSoftware Architecture: Test Case Writing
Software Architecture: Test Case Writing
 
Gen sessionthomas.riskofsystemproblemfinal23feb12
Gen sessionthomas.riskofsystemproblemfinal23feb12Gen sessionthomas.riskofsystemproblemfinal23feb12
Gen sessionthomas.riskofsystemproblemfinal23feb12
 
SEOC 2004-2011
SEOC 2004-2011SEOC 2004-2011
SEOC 2004-2011
 
Unit 7 final
Unit 7 finalUnit 7 final
Unit 7 final
 

Similar to Ch1

Similar to Ch1 (20)

ch1.ppt
ch1.pptch1.ppt
ch1.ppt
 
Introduction to Software Enigneering
Introduction to Software Enigneering Introduction to Software Enigneering
Introduction to Software Enigneering
 
0273710133 pp01v2
0273710133 pp01v20273710133 pp01v2
0273710133 pp01v2
 
Ch1
Ch1Ch1
Ch1
 
Software Engineering - Ch1
Software Engineering - Ch1Software Engineering - Ch1
Software Engineering - Ch1
 
Software Processes
Software Processes Software Processes
Software Processes
 
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
 
Ch26
Ch26Ch26
Ch26
 
Software Processes
Software ProcessesSoftware Processes
Software Processes
 
Se ii unit1-se_ii_intorduction
Se ii unit1-se_ii_intorductionSe ii unit1-se_ii_intorduction
Se ii unit1-se_ii_intorduction
 
香港六合彩
香港六合彩香港六合彩
香港六合彩
 
香港六合彩 » SlideShare
香港六合彩 » SlideShare香港六合彩 » SlideShare
香港六合彩 » SlideShare
 
六合彩|香港六合彩
六合彩|香港六合彩六合彩|香港六合彩
六合彩|香港六合彩
 
香港六合彩-六合彩
香港六合彩-六合彩香港六合彩-六合彩
香港六合彩-六合彩
 
六合彩,香港六合彩
六合彩,香港六合彩六合彩,香港六合彩
六合彩,香港六合彩
 
六合彩|香港六合彩
六合彩|香港六合彩六合彩|香港六合彩
六合彩|香港六合彩
 
1 se-introduction
1 se-introduction1 se-introduction
1 se-introduction
 
Ch5
Ch5Ch5
Ch5
 
Software engineering-Light presentation
Software engineering-Light presentationSoftware engineering-Light presentation
Software engineering-Light presentation
 

Ch1

  • 1. An Introduction to Software Engineering ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 1
  • 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 2
  • 3. Topics covered FAQs about software engineering Professional and ethical responsibility ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 3
  • 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 4
  • 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 5
  • 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 6
  • 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 7
  • 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 8
  • 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 9
  • 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 10
  • 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 11
  • 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 12
  • 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 13
  • 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 14
  • 15. W Develo atDesign er 5mode fall0Integ 0 2 ration 5 7 10 50 Activity cost distribution Specificat It2 5 7 stem erative1de 0 5 0 5 00 Specificat Iterative S1 0 y0 Compone ineering 0 Develop 2 5Integ 5 0 ration 7 5 Specificat Developm 003 ems 0 stem 400 1 2 0 dev S Sstem y y 0 ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 15
  • 16. Product development costs 0Develo 2 5Sste 5 0y 1 70 5 Specific ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 16
  • 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 17
  • 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 18
  • 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 19
  • 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 20
  • 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 21
  • 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 22
  • 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 23
  • 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 24
  • 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 25
  • 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 26
  • 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 27
  • 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 28
  • 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 29
  • 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 30
  • 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. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 31