course introduction and overviewtddc93/timetable/1introduction-4.pdf · 2008-08-26 · 1 course...

Course Introduction

and OverviewLecture 1

Kristian Sandahl

Department of Computer and Information Science

Linköping University, Sweden

krisa@ida.liu.se

Software Engineering

TDDC88-theory/TDDC93

Autumn 2008

Part I

Definition and role of SE

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Who am I

Gotland Småland Linköping

Naval HQ Protein purification Ericsson

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Who are you?

TDDC934 ECTS

Software Engineering TheoryY-program

D-program

C-program

IT-progamTheory

TDDC8812 hp/ECTS

Project

6hp Theory

Software Engineering I-program

Ii-program

Master students

Exchange students

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Agenda - What will you learn today?

Part I – Definition and role of

software engineering

Part II – A life cycle model

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Part I

Definition and role of Software Engineering

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

A typical Software Project

How the customer explained it

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

How the project leader understood it

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

How the analyst designed it

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

How the programmer wrote it

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

How the business consultant described it

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

How the project was documented

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

What operations installed

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

How the customer was billed

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

How it was supported

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Finally, what the customer really needed

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Why do we need SE?

� Frequent failures:

� Space shuttle

� Nike

� Denver airport

� LA airport

Charette, R.N. (2005) Why Software

Fails, IEEE Spectrum, September 2005

Geppert, L (2004) Lost Radio Contact Leaves

Pilots On Their Own, IEEE Spectrum, Nov 2004

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Beehive Exercise

10 minutes beehive!1. Discuss in pairs

� Why is it hard to communicate about

software?

� Why do we read about frequent software

failures

� What can we do about it?

List at least 4 problems/solutions

2. Write on the whiteboard

� Go down to the whiteboard and write

down a problem / a solution

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Software Engineering

� Application of systematic, disciplined, quantifiable approach to

software development, operation and maintenance of software. (IEEE-Std.)

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Challenges to SE

� Different types of software:� criticality

� # users

� # developers

� # platforms

� risk

� cost

� There will be changes� degrading performance

� maintenance account for 70% of life cycle cost

� Everyone want the latest technology

� Increased demands for software with:� high quality� high complexity

� delivered promptly� low price

� Different types of knowledge:

� Understanding customers

� Understanding users

� Managing projects and people

� Communication

� Staffing

� Design at many levels

� Programming tools

� Components

� Testing

� Quality assurance

� Business

� Risk management

� Technology assessment

� ......

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Studying SE theory

� Reading about concepts and methods derived from

experience

� Almost everything have their pros and cons

� Quite little is based on mathematical theory

� Requires disciplined plan for reading different sources

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Studying SE theory

Your job

� Find central concepts and methods over the entire field

� Study their applicability, pros and cons

� Practice analysing and

designing small examples

� Participate in examination

� Ask me questions

� Give me suggestions for

further improvement

My job

� Account for the most central concepts in lectures

� Set things in context

� Discuss industrial relevance

� Arrange examination

� Answer your questions

� Listen to feed-back:

� Muddy-card

� Personal communication

� Student’s evaluation

krisa@ida.liu.se 0706-68 19 57 3B:470

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Mail me

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Ambition level

� You will know enough to communicate easily with

professional software engineers

� You will have the basic knowledge to start generating

your own experience already in student projects

� You will have a curious, but critical, attitude towards existing and new methods

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Part II

Contents of a Software Life Cycle

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Scope of a software life-cycle model

Idea Software Product

Usage Operation & maintenance Replacement

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Model of a life-cycle

Abstraction

Carolthe customer

Dianathe developer

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Requirements

Elicitation

Collect user

requirement

Analyze

Understand

Specify

Document

Validate

Check that it matches

user requirements

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Requirements

Functional requirements A required behavior or functionE.g. "delete material items"

Non-Functional requirementsQuality requirements

E.g. performance, scalability, usabilitymaintainability, etc.

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Requirements and Acceptance Test

Requirements Acceptance Test(Release testing)

Validate Requirements, Verify Specification

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

System Design

System Design(Architecture,

High-level Design)

Decompose into sub-systems or modules

• Well-defined interfaces

• High level of abstraction

Module 1 Module 2

Module 3

Architecture styles, e.g.

• Client-server

• Layered Models

• Pipes and Filters

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

System and Module Design

High-level Design)

Module Design(Program Design,

Detailed Design)

Unified Modeling Language (UML)

Use a standardized way to model system

graphically

Design Patterns

Reuse design solution that has worked before

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Testing

High-level Design)

Detailed Design)

System Testing(Integration testing of modules)

Implementationof Units (classes, procedures,

functions)

Unit testing

Verify Implementation

Module Testing(Integration testing of units)

Verify Module Design

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Testing

High-level Design)

Detailed Design)

functions)

Unit testing

Integration testing

• Dependencies between modules

Approaches

• Top-down (need stubs)• Bottom-up (need drivers)

• Sandwich

• Big-bag

Module 1 Module 2

Module 3

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Verify System Design

Supporting Processes

High-level Design)

Detailed Design)

functions)

Unit testing

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Inspection

High-level Design)

Detailed Design)

functions)

Unit testing

Inspection

Formal Inspection

• Reviewing with a defined process• Aim at finding defects

• Works in practice

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Software Life Cycles, Configuration Mgm.

High-level Design)

Detailed Design)

functions)

Unit testing

Software Life Cycles and Configuration

Management

V-model

Waterfall model

Iterative models

Configuration Management (CM)

Keep track of versions. Used the wrong code-base.

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Software Quality Management

High-level Design)

Detailed Design)

functions)

Unit testing

Lecture 12 - Software Quality Management

Different qualities

• Quality of product

• Quality of process• Quality in a business environment

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Software Life Cycles, Configuration Mgm.

High-level Design)

Detailed Design)

functions)

Unit testing

Project Management

Time plan

Milestones Time-budget

Resources Calendar-time

Activities

- Minimize

- Transfer - Accept

Risk Management

Identify Analyze Plan

• Resource management• Time-buffer

• Internal milestones - keep track

probability - consequence

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

A Software Life-cycle

Requirements

High-level Design)

Detailed Design)

functions)

Unit testing

Acceptance Test(Release testing)

Project Management, Software Quality Assurance (SQA), Supporting Tools, Education

Maintenance

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

A Software Life-cycle Model

Which part will we talk about today?

Requirements

High-level Design)

Detailed Design)

functions)

Unit testing

Maintenance

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Theory Lecture Plan

L1 - Course Introduction and Overview

L2 - Project Management

L3 - Requirements

L4 - Acceptance Testing and Quality Factors

L5 - Design Patterns

L6 - UML

L7 - System Design and Architecture

L8 - Testing Theory

L9 - Testing in Practice

L10 - Inspection

L11 - Software Life Cycles and Configuration Management

L12 - Software Quality Management

L13 - Course Summary, Exam examples, Questions

L1 - Course Introduction and Overview

Part I

Part II

A life cycle model

Kristian Sandahl

krisa@ida.liu.se

Summary - What have we learned today?

Requirements

High-level Design)

Detailed Design)

functions)

Unit testing

Maintenance

course introduction and overviewtddc93/timetable/1introduction-4.pdf · 2008-08-26 · 1 course...

Documents

code generation (chapter 7) 1 course overview part i:...

teams unleashed: a complete field guide to team coaching w/...

syllabus (1) weekchapters 1introduction to the course, basic...

1introduction - maths.dur.ac.uk

1introduction - mit economics

1introduction - econometica

alamin 1introduction, industry, mkt seg00001

1introduction - stg2-uk.sagepub.com

1introduction 2graphs - wordpress.com

1introduction to cad

course curriculum module 1introduction module 2laws &...

1introduction to upf-it

contextual analysis (chapter 5) 1 course overview part i:...

1introduction to arduino thinnkware

training for the weights and measures official course...

1introduction - nber

runtime organization (chapter 6) 1 course overview part i:...

1introduction to research1

review (chapter 9) 1 course overview part i: overview...

1introduction 2systemrequirements