Software Engineering COMP 201

Similar documents
System and Software Engineering. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 1

Software Engineering

CMSC 435: Software Engineering Section Back to Software. Important: Team Work. More Resources

Software Processes. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1

Pertemuan 2. Software Engineering: The Process

Software Processes. Objectives. Topics covered. The software process. Waterfall model. Generic software process models

Course Organization. Lecture 1/Part 1

The software process

CSE320 :: Gurbakash Phonsa: Assistant Professor : CSE. Software Engineering

Lectures 2 & 3. Software Processes. Software Engineering, COMP201 Slide 1

Introduction to Software Engineering

CS 501: Software Engineering. Lecture 2. Software Processes

Objectives. The software process. Topics covered. Waterfall model. Generic software process models. Software Processes

Topics covered. Software process models Process iteration Process activities The Rational Unified Process Computer-aided software engineering

Software LEIC. Lecture 23

SE curriculum in CC2001 made by IEEE and ACM: What is Software Engineering?

INFORMATION SYSTEMS ANALYSIS AND DESIGN

Software tool support for software development

CTIS 359 Principles of Software Engineering

Software Engineering & Architecture

The good news. 34% of software projects succeed. Standish Group, CHAOS Report, 2003

Software Engineering. SOFTWARE ENGINEERING Subject Code: 10IS51 I.A. Marks : 25 Hours/Week : 04 Exam Hours: 03 Total Hours : 52 Exam Marks: 100 PART A

Software Construction

PEARSON. Addison Wesley

Requirements Engineering. Massimo Felici Room 1402, JCMB, KB

Development Process and Analysis. LTOOD/OOAD - Verified Software Systems 1

Software Engineering QUESTION BANK

SWE 211 Software Processes

Learning Approach. Evaluation. Text Book. - Written Test : 20% - Assignment/Project : 30%

Lecture 1. In practice, most large systems are developed using a. A software process model is an abstract representation

II. Software Life Cycle. Laurea Triennale in Informatica Corso di Ingegneria del Software I A.A. 2006/2007 Andrea Polini

Software Engineering COMP 201

Explore Comparative Analysis Software Development Life Cycle Models

03. Perspective Process Models

Course title: SOFTWARE ANALYSIS AND DESIGN

In this Lecture you will Learn: Development Process. Unified Software Development Process. Best Practice

BCS THE CHARTERED INSTITUTE FOR IT. BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 6 Professional Graduate Diploma in IT SOFTWARE ENGINEERING 2

Software Engineering with Objects and Components. Massimo Felici Room 1402, JCMB, KB

A Comparison Between Two Software Engineering Processes, RUP And Waterfall Models

Solutions Manual. Object-Oriented Software Engineering. An Agile Unified Methodology. David Kung

BCS Certificate in Systems Development Essentials Syllabus

MTAT Introduction to Informatics

Quality Assurance for Systems Engineering (INSE 6280/2-WW)

Based on Software Engineering, by Ian Sommerville Coherent sets of activities for specifying, designing, implementing and testing software systems

Organising Requirements

A Software Measurement Case Study Using GQM

TDT4252 Modelling of Information Systems Advanced Course

Software development processes: from the waterfall to the Unified Process

Darshan Institute of Engineering & Technology for Diploma Studies Rajkot Unit-1

7. What is planning? It is an act of formulating a program for a definite course of action. Planning is to decide what is to be done.

COMP 354 Introduction to Software Engineering

Software processes, quality, and standards VTV, fast methods, automation

Introduction to Software Engineering

II-IT IV-SEM. 1. Software product and process. Software Engineering and Quality Assurance. Objectives:

Software Modeling & Analysis. - Fundamentals of Software Engineering - Software Process Model. Lecturer: JUNBEOM YOO

TOGAF usage in outsourcing of software development

SRM UNIVERSITY FACULTY OF ENGINEERING AND TECHNOLOGY SCHOOL OF COMPUTING DEPARTMENT OF CSE COURSE PLAN

IBM Rational Systems Developer, Version 7.0

DEVOPS A NEW DEVOPS MODEL FOR ACHIEVING MARKET AGILITY BY SEYHAN BAKI

INTRODUCTION TO R FOR DATA SCIENCE WITH R FOR DATA SCIENCE DATA SCIENCE ESSENTIALS INTRODUCTION TO PYTHON FOR DATA SCIENCE. Azure Machine Learning

7. Project Management

Module Documentation

Software Engineering I (02161)

Enterprise engineering based IT systems for organizations

Professor Christina Romer. LECTURE 1 SCARCITY AND CHOICE January 16, 2018

MCT610 Software Engineering Module Handbook

Software Engineering Ian Sommerville Pearson Education File Type

Development Process Bennett, McRobb and Farmer 1

Software Engineering. Lecture 1: Introduction

2068 I. Attempt any ten questions. (10x6=60)

Note 10: Software Process

IBM Continuous Engineering augmenting PLM with ALM and Systems Engineering

Enhancing. PeopleSoft Applications With Oracle Fusion Middleware

Software Development Methodologies

Best Practices for Collecting User Requirements. Gerry Clancy Glenn Berger

MODPROD 2017, Linköping February 8, 2017

Lecture 2: Software Quality Factors, Models and Standards. Software Quality Assurance (INSE 6260/4-UU) Winter 2016

Software Development Methodologies

Requirements Engineering

Chapter 1. Contents. What is Software Engineering 9/9/13. Shari L. Pfleeger Joanne M. Atlee. 4 th Edition

2009 Spring. Software Modeling & Analysis. - Software Process Model. Lecturer: JUNBEOM YOO

IEEE s Recommended Practice for Architectural Description

Test Workflow. Michael Fourman Cs2 Software Engineering

Literature Review M.Y. Suhaila, W.K. Wan Mohd Nasir, Member, IAENG, 2011 Raed Shatnawi and Ahmad Alzu bi, IMECS 2011

Software processes. Software Applications A.Y. 2018/2019

Objectives. Rapid software development. Topics covered. Rapid software development. Requirements. Characteristics of RAD processes

Credit where Credit is Due. Lecture 2: Software Engineering (a review) Goals for this Lecture. What is Software Engineering

Real-Time and Embedded Systems

Architecture Practice: a fundamental discipline for information systems

Introduction to Software Life Cycles. CSCI 5828: Foundations of Software Engineering Lecture 06 09/08/2016

7. Model based software architecture

Simulation Software. Chapter 3. Based on the slides provided with the textbook. Jiang Li, Ph.D. Department of Computer Science

SOFTWARE ENGINEERING

The Top Thrill Dragster

Quality Assurance Activities in Object-Oriented Software Development


Fit-For-Future Land Administration: Unlocking the Benefits of Sustainable, Cost-Effective Technologies

Analyze, Design, and Develop Applications

Chapter 1. Contents. 1.1 What is Software Engineering! Solving Problems. Objectives. What is Software Engineering

PI-MDD Executive Summary

Transcription:

Software Engineering COMP 201 Lecturer: Dr. Igor Potapov Chadwick Building, room 2.09 E-mail: igor@csc.liv.ac.uk COMP 201 web-page: http://www.csc.liv.ac.uk/~igor/comp201 Software Engineering, COMP201 Slide 1

Why Software Engineering? Software development is hard! Important to distinguish easy systems (one developer, one user, experimental use only) from hard systems (multiple developers, multiple users, products) Experience with easy systems is misleading One person techniques do not scale up Analogy with bridge building: Over a stream = easy, one person job Over River Severn? (the techniques do not scale) Software Engineering, COMP201 Slide 2

Why Software Engineering? The problem is complexity Many sources, but size is key: UNIX contains 4 million lines of code Windows 2000 contains 10 8 lines of code Software engineering is about managing this complexity. Software Engineering, COMP201 Slide 3

Teaching method Series of 30-33 lectures ( 3hrs per week ) Lecture Monday 12.00 Lecture Wednesday 9.00 Lecture Thursday 14.00 Practical work (2 Assignments) ----------------------- Course Assessment ---------------------- A two-hour examination 80% Coursework 20% ----------------------------------------------------------------------- Software Engineering, COMP201 Slide 4

Recommended Course Textbooks Sommerville I. (2001,2004) Software Engineering 6 th or 7 th Edition, Addison-Wesley, Harlow, Essex,UK Stevens P. with Pooley, R. (2000) Using UML: Software Engineering with Objects and Components, Addison-Wesley, Harlow, Essex, UK Introducing Asml (2001) Microsoft corporation Sommerville + Stevens Bundle Software Engineering, COMP201 Slide 5

Outline Syllabus Introduction to Software Engineering Formal Specification using ASML (Abstract State Machines Language) Software Design and Implementation Using the UML (Unified Modeling Language) Software verification, validation and testing Software Engineering, COMP201 Slide 6

FAQs about software engineering What is software? software process? software engineering? software process model? What is software engineering? What is the difference between software engineering and computer science? between software engineering and system engineering? Software Engineering, COMP201 Slide 7

What is software? Computer programs and associated documentation Software products may be developed for a particular customer or may be developed for a general market Software products may be Generic - developed to be sold to a range of different customers Bespoke (custom) - developed for a single customer according to their specification Software Engineering, COMP201 Slide 8

What is software engineering? Software engineering is an engineering discipline which is concerned with all aspects of software production Software engineers should adopt a systematic and organised approach to their work use appropriate tools and techniques depending on the problem to be solved, the development constraints and the resources available Software Engineering, COMP201 Slide 9

What is the difference between software engineering and computer science? Computer Science theory fundamentals is concerned with Software Engineering the practicalities of developing delivering useful software Computer science theories are currently insufficient to act as a complete underpinning for software engineering, BUT it is a foundation for practical aspects of software engineering Software Engineering, COMP201 Slide 10

What is the difference between software engineering and system engineering? Software engineering is part of System engineering System engineering is concerned with all aspects of computer-based systems development including hardware, software and process engineering System engineers are involved in system specification, architectural design, integration and deployment Software Engineering, COMP201 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 Software Engineering, COMP201 Slide 12

What is a software process model? A simplified representation of a software process, presented from a specific perspective Examples of process perspectives: Workflow perspective represents inputs, outputs and dependencies Data-flow perspective represents data transformation activities Role/action perspective represents the roles/activities of the people involved in software process Generic process models Waterfall Evolutionary development Formal transformation Integration from reusable components Software Engineering, COMP201 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 Software Engineering, COMP201 Slide 14

What is CASE? (Computer-Aided Software Engineering) Software systems which are intended to provide automated support for software process activities, such as requirements analysis, system modelling, debugging and testing 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 Software Engineering, COMP201 Slide 15

What are the attributes of good software? The software should deliver the required functionality and performance to the user and should be maintainable, dependable and usable Maintainability Software must evolve to meet changing needs Dependability Software must be trustworthy Efficiency Software should not make wasteful use of system resources Usability Software must be usable by the users for which it was designed Software Engineering, COMP201 Slide 16

What are the key challenges facing software engineering? Software engineering in the 21 st century faces three key challenges: Legacy systems Old, valuable systems must be maintained and updated Heterogeneity Systems are distributed and include a mix of hardware and software Delivery There is increasing pressure for faster delivery of software Software Engineering, COMP201 Slide 17

Next lecture Software Processes Wednesday 9.00 a.m. COMP 201 web-page: http://www.csc.liv.ac.uk/~igor/comp201 Software Engineering, COMP201 Slide 18