Chapter 1: Introduction (3705)

Chapter 1: Introduction (3705)

1. Case Studies

2. Software Engineering Ethics

   • Confidentiality
     • You should normally respect the confidentiality of your employers or clients regardless
   • Competence
     • should not misrepresent your level of competence
   • Intellectual property rights
     • patents and copyrigh
   • Computer misuse
     • should not use your technical skills to misuse other people’s computers.

3. Software engineering

   • Engineering discipline Engineers make things work by using methods and tools inside constraints
   • All aspects of software production - Technical, Planning, Development, Tools and Methods
   • Software engineering is important for two reasons:
     • Need for advanced software systems
     • cheaper, in the long run, to use software engineering methods than amateur approach
   • Four fundamental activities are common to all software processes
     • Software specification, where customers and engineers define the software that is to be produced and the constraints on its operation.
     • Software development, where the software is designed and programmed.
     • Software validation, where the software is checked to ensure that it is what the customer requires.
     • Software evolution, where the software is modified to reflect changing customer and market requirements.
   • four related issues that affect many different types of software:
     • Heterogeneity -> Increasingly, systems are required to operate as distributed systems across networks that include different types of computer and mobile devices.
     • Business and social change -> Businesses and society are changing incredibly quickly
     • Security and trust -> As software is intertwined with all aspects of our lives, it is essential that we can trust that software
     • Scale Software -> has to be developed across a very wide range of scales,

4. Introduction

   • Software failures are a consequence of two factors:
     • Increasing system complexity
     • Failure to use software engineering methods
   • software is not just the programs themselves but also all associated documentation, libraries, support websites, and configuration data that are needed to make these programs useful.
   • Professional software development- enterprise
   • Amateur software dedvelopment - self
   • Two kinds of software product:
     • Generic products - Sold on the open market. E.g. Mobile apps and PC software
       • Dev req controlled by organisation
     • Customized (or bespoke) software - Dev for specific client
       • Dev req controlled by client

5. Software engineering diversity

   • Perhaps the most significant factor in determining which software engineering methods and techniques are most important is the type of application being developed.
   • Types of application
     • Stand-alone applications
     • Interactive transaction-based applications
     • Embedded control systems These are software control systems that control and manage hardware devices.
     • Batch processing systems These are business systems that are designed to process data in large batches
     • Entertainment systems
     • Systems for modeling and simulation
     • Data collection and analysis systems
     • Systems of systems
   • Software Engineering Fundamentals
     • process, dependability, requirements, management, and reuse are important themes

6. Internet software engineering

   • Software reuse has become the dominant approach for constructing web-based systems.
   • It is now generally recognized that it is impractical to specify all the requirements for such systems in advance. Web-based systems are always developed and delivered incrementally.
   • Software may be implemented using service-oriented software engineering,
   • Interface development technology such as AJAX (Holdener 2008) and HTML5 (Freeman 2011) have emerged that support the creation of rich interfaces within a web browser.

Bilder und Dateien der Mindmap