I n t r o d u c t i o n to S o f t w a r e En g i n e e r i n g

Slides:



Advertisements
Similar presentations
Chapter 1- Introduction Lecture 1. Topics covered  Professional software development  What is meant by software engineering.  Software engineering.
Advertisements

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 An Introduction to Software Engineering.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 An Introduction to Software Engineering.
SE 112 Slide 1 SE 112 l
Frequently asked questions about software engineering
Lecture 1.
Chapter 1 Introduction Yonsei University 2 nd Semester, 2014 Sanghyun Park.
Chapter 1- Introduction
Chapter 1- Introduction Lecture 1 Ready, fire, aim (the fast approach to software development). Ready, aim, aim, aim, aim... (the slow approach to software.
Chapter 1- “Diversity” “In higher education they value diversity of everything except thought.” George Will.
Chapter 1- Introduction To SE Lecture 1. Software engineering  The economies of ALL developed nations are dependent on software.  More and more systems.
1 An Introduction to Software Engineering. 2 Objectives l To introduce software engineering and to explain its importance l To set out the answers to.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 An Introduction to Software Engineering.
Chapter 1- Introduction
CSc 461/561 Information Systems Engineering Lecture1 - Introduction.
Chapter 1- Introduction Lecture 1. Topics covered  Professional software development  What is meant by software engineering.  Software engineering.
Chapter 1- Introduction Lecture 1. Topics covered  Professional software development  What is meant by software engineering.  Software engineering.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 1 Slide 1 Chapter 1 Introduction.
Chapter 1- Introduction Lecture 1. Topics covered  Professional software development  What is meant by software engineering.  Software engineering.
1 Software Engineering, 8th edition. Chapter 1 Jan 28 th, 2009 Lecture # 1 Courtesy: ©Ian Sommerville 2006 An Introduction to Software Engineering.
Chapter 1- Introduction. Topics covered  Professional software development  What is meant by software engineering.  Software engineering ethics  A.
An Introduction to Software Engineering. Objectives  To introduce software engineering and to explain its importance  To set out the answers to key.
Software Engineering Chapter 1- Introduction. Topics covered  Professional software development  What is meant by software engineering.  Software engineering.
Chapter 1- Introduction Lecture 1. Topics covered  Professional software development  What is meant by software engineering.  Software engineering.
Chapter 1- Introduction Lecture 1. Topics covered  Professional software development  What is meant by software engineering.  Software engineering.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 An Introduction to Software Engineering.
CS 389 – Software Engineering Lecture 1b Introduction Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed.
Chapter 1- Introduction. Topics covered  Professional software development  What is meant by software engineering.  Software engineering ethics  A.
CS220:INTRODUCTION TO SOFTWARE ENGINEERING CH1 : INTRODUCTION 1.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 An Introduction to Software Engineering.
CASE STUDIES * System Engineering, 9th Edition Sommerville.
CompSci 280 S Introduction to Software Development
CompSci 280 S Introduction to Software Development
Chapter 1- Introduction
Software Engineering An Introduction.
CS390: Software Engineering
An Introduction to Software Engineering
An Introduction to Software Engineering
Software Engineering Unit- 1 Engineered for Tomorrow CSE, MVJCE.
INTRODUCTION The economies of ALL developed nations are dependent on software. More and more systems are software controlled Software engineering is concerned.
Chapter 1- Introduction
CS281 – Introduction to Software Engineering Chapter1: Introduction
Chapter 1: Introduction to Software Engineering
MISY 301 Mr.Mohammed Rafeeque.
An Introduction to Software Engineering
Software Engineering Introduction.
Software Engineering Lecture 1b Introduction Adapted from:
CSE305 Software Engineering
Chapter 1- Introduction
Chapter 1- Introduction
Frequently asked questions about software engineering
I n t r o d u c t i o n to S o f t w a r e En g i n e e r i n g
Chapter 1- Introduction
Chapter 1- Introduction
Chapter 1- Introduction
CS281 – Introduction to Software Engineering Chapter1: Introduction
Physical Design and Implementation with Emerging Environment INFS 360
Chapter 1: Introduction to Software Engineering
CS385T Software Engineering Dr.Doaa Sami
An Introduction to Software Engineering
Chapter 1- Introduction
Chapter 1- Introduction
Chapter 1- Introduction
An Introduction to Software Engineering
Chapter 1 Introduction.
An Introduction to Software Engineering
Chapter 1- Introduction
An Introduction to Software Engineering
An Introduction to Software Engineering
An Introduction to Software Engineering
Presentation transcript:

I n t r o d u c t i o n to S o f t w a r e En g i n e e r i n g C h a p t e r 1 I n t r o d u c t i o n to S o f t w a r e En g i n e e r i n g Dr.Doaa Sami Modified from Sommerville’s originals

Objectives  To introduce software engineering 2  To introduce software engineering  To explain the importance of software engineering  To give the basic software properties  To introduce ethical and professional issues

Software List as many as you can … 3 Think about all the devices and systems that you encounter in your everyday life which have software controlling them List as many as you can … Virtually all countries depend on computer

Introduction dependent on software. 4  The economies of ALL developed nations are dependent on software.  More and more life systems such as hospitals, universities and ministries are software controlled.  More and more, individuals and society rely on advanced software systems. We need to be able to produce reliable and trustworthy systems economically and quickly.

Software Crisis r9cYp3tTE Example 1 :Airplane Explosion 5 Example 1 :Airplane Explosion  European Space Agency spent 10 years and $7 billion to produce Ariane 5.  Crash after 36.7 seconds .  Caused by an overflow error. Trying to store a 64-bit number into a 16-bit space.  Watch the video http://www.youtube.com/watch?v=z- r9cYp3tTE

Software Crisis Example 2: London Ambulance Service 6 Example 2: London Ambulance Service  Considered the largest ambulance service in the world.  It was unable to keep track of the ambulances and their statuses. Sending multiple units to some locations and no units to other locations.  Generates many exceptions messages.  Overloaded problem  46 deaths.

Software Definition Computer Programs. 7  The term “Software” does not refer to computer programs only, But includes: Computer Programs. Associated documentation such as requirements, design models and user manuals. Configuration data that is needed to make these programs operate correctly.  Software Engineers: are concerned with developing software products.

What is Software 8 Software: computer programs, associated documentation and configuration data. Good software should deliver the required functionality and performance to the user and should be maintainable, dependable and usable. Programs Software System Documentation User Data Documentation

Software Engineering 9  Software Crisis The term "software engineering" first appeared in the1968 NATO Software Engineering Conference, and was meant to provoke thought regarding what was then called the “software crisis”.  Software Engineering (SWE) Discipline of engineering that is concerned with all aspects of software production, from the early stages of system specification through to maintaining the system after it has gone into use.

Software Products Types 10  Generic products  Stand-alone systems that are marketed and sold to any customer who wishes to buy them. Examples: PC software such as graphics programs, Excel or Word, CAD software and project management tools.  Customized products (Bespoke)  Software that is commissioned by a specific customer to meet their own needs. Examples: embedded control systems, air traffic control software, traffic monitoring systems and systems that support business process.  Sometimes, these two types are overlapped  You can buy standalone software and then you could do some customization to it such as ERP system (SAP).

Software Process Activities 11  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.

Importance of Software Engineering 12  It is usually cheaper, in the long run, to use software engineering methods and techniques for software systems rather than just write the programs as if it was a personal programming project.  For most types of systems, the majority of costs are the costs of changing the software after it has gone into use.

Software Cost  Software costs often dominate computer system costs. 13  Software costs often dominate computer system costs.  Software on a PC  the hardware cost.  Software maintenance cost  the cost of developing it. For systems with a long life, maintenance costs may be several times of development costs. Ex. Aircraft software.  Software engineering is concerned with cost- effective software development.

Cost of Software Engineering 14  Depends on :  The process used, and  The type of software being developed  Each generic approach has a different profile of cost distribution.  Roughly 60% of costs are development costs, 40% are testing costs.  For custom software, evolution costs often exceed development costs.

Software Engineering & Computer Science 15 Computer Science  Theory + Fundamentals that underlie computers and software systems. SWE  practical of developing and delivering useful software.

Software Engineering & System Engineering 16  System Engineering:  Interdisciplinary engineering field (computer, software, and process engineering).  Focuses on how complex engineering projects should be designed and managed. System Engineering Software Engineering • All aspects of • Deals with the design, computer-based development and systems development: delivery of SW. HW + SW + Process. • Is part of System • Older than SWE. Engineering.

 A set of activities that aims to produce SW product. What is a Software Process? 17  A set of activities that aims to produce SW product. SW Process Activity What is going on there? Specification What does the customer need? Development Design & programming Validation Checking whether it meets requirements Evolution Modifications (e.g. customer/market) What are the constraints?

Software Process Models Example 18  Waterfall approach Requirements definitions System and software design Implementation and unit testing Integration and system testing Operation and maintenance

Component-Based Software Engineering 19  Component-Based Software Engineering (CBSE):  This technique assumes that parts of the system already exist.  The system development process focuses on integrating these parts rather than developing them from scratch.

Essential Attributes of Good Software 20  Maintainability  Software should be written in such a way so that it can evolve to meet the changing needs of customers.  Dependability  Dependable software should not cause damage in the event of system failure.  Efficiency  System resources: memory waste, processing time.  Acceptability  This means that it must be understandable, usable and compatible with other systems that they use.

Key Challenges Facing Software Engineering 21  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  Business and society are changing incredibly quickly as emerging economies develop and new technologies become available. They need to be able to change their existing software and to rapidly develop new software.  Security and trust  As software is intertwined with all aspects of our lives, it is essential that we can trust that software.

Application Types  Stand-alone applications 22  Stand-alone applications  These are application systems that run on a local computer, such as a PC. They include all necessary functionality and do not need to be connected to a network.  Interactive transaction-based applications  Applications that execute on a remote computer and are accessed by users from their own PCs or terminals. These include web applications such as e-commerce applications.  Embedded control systems  These are software control systems that control and manage hardware devices. Numerically, there are probably more embedded systems than any other type of system. 19

Application Types  Batch processing systems 23  Batch processing systems  They process large numbers of individual inputs to create corresponding outputs such as payroll system and invoice system.  Systems for modeling and simulation  These are systems that are developed by scientists and engineers to model physical processes or situations, which include many, separate, interacting objects.  Data collection systems  These are systems that collect data from their environment using a set of sensors and send that data to other systems for processing. 20

Software Engineering Diversity 24  There are many different types of software systems and there is no universal set of software techniques that is applicable to all of these.  The software engineering methods and tools used depend on the type of application being developed, the requirements of the customer and the background of the development team.

Software Engineering Ethics 25  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 but involves following a set of principles that are morally correct.

Ethical Dilemmas systems or nuclear systems. 26  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.

Case Studies  A mental health case patient management system 27  A personal insulin pump An embedded system in an insulin pump used by diabetics to maintain blood glucose control.  A mental health case patient management system A system used to maintain records of people receiving care for mental health problems.  A wilderness weather station A data collection system that collects data about weather conditions in remote areas.

Insulin pump control system Collects data from a blood sugar sensor and calculates the amount of insulin required to be injected. Calculation based on the rate of change of blood sugar levels. Sends signals to a micro-pump to deliver the correct dose of insulin. Safety-critical system as low blood sugars can lead to brain malfunctioning, coma and death; high-blood sugar levels have long-term consequences such as eye and kidney damage. Dr.Doaa Sami

Insulin pump hardware architecture Dr.Doaa Sami

Activity model of the insulin pump Dr.Doaa Sami

Essential high-level requirements The system shall be available to deliver insulin when required. The system shall perform reliably and deliver the correct amount of insulin to counteract the current level of blood sugar. The system must therefore be designed and implemented to ensure that the system always meets these requirements. Dr.Doaa Sami

A patient information system for mental health care A patient information system to support mental health care is a medical information system that maintains information about patients suffering from mental health problems and the treatments that they have received. Most mental health patients do not require dedicated hospital treatment but need to attend specialist clinics regularly where they can meet a doctor who has detailed knowledge of their problems. To make it easier for patients to attend, these clinics are not just run in hospitals. They may also be held in local medical practices or community centres. Dr.Doaa Sami

MHC-PMS The MHC-PMS (Mental Health Care-Patient Management System) is an information system that is intended for use in clinics. It makes use of a centralized database of patient information but has also been designed to run on a PC, so that it may be accessed and used from sites that do not have secure network connectivity. When the local systems have secure network access, they use patient information in the database but they can download and use local copies of patient records when they are disconnected. Dr.Doaa Sami

MHC-PMS goals To generate management information that allows health service managers to assess performance against local and government targets. To provide medical staff with timely information to support the treatment of patients. Dr.Doaa Sami

The organization of the MHC-PMS Dr.Doaa Sami

MHC-PMS key features Individual care management Patient monitoring Clinicians can create records for patients, edit the information in the system, view patient history, etc. The system supports data summaries so that doctors can quickly learn about the key problems and treatments that have been prescribed. Patient monitoring The system monitors the records of patients that are involved in treatment and issues warnings if possible problems are detected. Administrative reporting The system generates monthly management reports showing the number of patients treated at each clinic, the number of patients who have entered and left the care system, number of patients sectioned, the drugs prescribed and their costs, etc. Dr.Doaa Sami

MHC-PMS concerns Privacy Safety It is essential that patient information is confidential and is never disclosed to anyone apart from authorised medical staff and the patient themselves. Safety Some mental illnesses cause patients to become suicidal or a danger to other people. Wherever possible, the system should warn medical staff about potentially suicidal or dangerous patients. The system must be available when needed otherwise safety may be compromised and it may be impossible to prescribe the correct medication to patients. Dr.Doaa Sami

Wilderness Weather Station 28  The government of a country with large areas of wilderness decides to deploy several hundred weather stations in remote areas.  Weather stations collect data from a set of instruments that measure temperature and pressure, sunshine, rainfall, wind speed and wind direction. The weather station includes a number of instruments that measure weather parameters such as the wind speed and direction, the ground and air temperatures, the barometric pressure and the rainfall over a 24-hour period. Each of these instruments is controlled by a software system that takes parameter readings periodically and manages the data collected from the instruments.

The Weather Station’s Environment 29 Weather station system: collecting weather data and transmitting them to the data management system. Data management and archiving system: collects data from all of wilderness weather stations, carries out data processing and archives the data. Station maintenance system: communicate by satellite with all wilderness weather stations to monitor the health of these systems and provide reports of problems.

Summary maintainability, dependability and security, efficiency 30 Software engineering is an engineering discipline that is concerned with all aspects of software production.  Essential software product attributes are maintainability, dependability and security, efficiency and acceptability. The high-level activities of specification, development, validation and evolution are part of all software processes.  Software engineers have responsibilities to the engineering profession and society. They should not simply be concerned with technical issues.

Thank you End of Chapter 1