COMP 2007 R J Walters. COMP 2007 - 1 Introduction Try to place this course in context A bit of history “Engineering”?

Slides:



Advertisements
Similar presentations
Adaptive Processes Introduction to Software Engineering Adaptive Processes.
Advertisements

Chapter 24 Quality Management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design 1.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 12Slide 1 Software Design l Objectives To explain how a software design may be represented.
AGILE DEVELOPMENT Outlines : Quick Look of agile development Agility
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
CS3773 Software Engineering Lecture 01 Introduction.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
Software Processes Coherent sets of activities for specifying, designing, implementing and testing software systems.
Difference between project and other assignments  real customer  before programming: negotiations with client to clarify requirements  often.
Event INFO 1010 Personal / Professional Development Hugh Davis
Software Engineering Dr.Basem Alkazemi
Introduction to Software Engineering Dr. Basem Alkazemi
7M822 Software Engineering Introduction 7 September 2010.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 An Introduction to Software Engineering.
Software Engineering COMP 201
1 Course Intro Construction & Evolution CSSE 375 Steve Chenoweth.
COMP 2007 R J Walters. COMP Last time Software Engineering is important It is “soft” - Not easy Making things using an “engineering” approach.
COMP 2007 R J Walters. COMP Remember - Documentation Defines your Engineering process Includes Requirements Design Testing User manuals Other.
CSSE September.2008 Variations of PM approaches Chapter 2, pages
Software engineering Olli Alm Lecture 2: requirements, modelling & representation.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Software Engineering Course Instructor: Aisha Azeem.
Requirement engineering for an online bookstore system
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System modeling 1.
Course Objectives and Instructor Information. To understanding of current software engineering theory and practice To study various software development.
CS4/542- Software Engineering  Software Design and Development  Required Text -- Code Complete by Steve McConnell  (Focuses on the problems of designing.
Introduction. Classes: Tuesdays & Thursdays 8:30 – 10:00 am Groups: We will work in a group of 3 Sessions will be highly interactive! Prior learning is.
1 KAN’S INTRO AND OVERVIEW MODELS Ch1 & 2 in his book Steve Chenoweth, CSSE.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management 1.
1 Software Engineering CEN5035 copyright © 1996, 2001 R.S. Pressman & Associates, Inc.
INTROSE Introduction to Software Engineering Raymund Sison, PhD College of Computer Studies De La Salle University Software: Definitions,
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
Software Engineering DKT311 ROHANI BINTI S MOHAMED FAROOK MOHAMED ELSHAIKH KKF 8A – room 4.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 1 Software Processes (Chapter 3)
University of Toronto Department of Computer Science CSC444 Lec05- 1 Lecture 5: Decomposition and Abstraction Decomposition When to decompose Identifying.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
Software Engineering Course Contents and Copyrights Slide 1 Software Engineering: An Introduction By: Prof. Dr. Eng. Ghazy Assassa, CMC-IMC Certified Management.
Lecture 1Software Engineering1 (Trimester I Session 2002/2003) Lecturer / Tutor Name : Mr. R. Logeswaran
Software Engineering EKT 420 MOHAMED ELSHAIKH KKF 8A – room 4.
10/20/2015 ©2007 Scott Miller, University of Victoria. 1 SENG130 Engineering Software Systems Introduction Rev. 2.1.
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
Designing Complex Software Systems: Introduction CS 6961 – Lecture 0 Nathan Dykman.
National Diploma Unit 4 Introduction to Software Development Introduction to Programming Languages.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
Software Engineering. Introduction Objective To familiarize students to the fundamental concepts, techniques, processes, methods and tools of Software.
Chapter 4 프로세스 모델 Process Models
EEE499 Real-Time Embedded Systems Introduction & Course Outline.
1/26 On-demand Learning Series Software Engineering of Web Application - Object-Oriented Development & UML Hunan University, Software School.
ECE450 - Software Engineering II1 ECE450 – Software Engineering II Today: Introduction to Software Architecture.
1 Software Engineering Textbook:“Software Engineering -- A Practitioner’s Approach,” 5th Edition by Roger S. Pressman URL:
Software Engineering Jon Walker. What is Software Engineering? Why do we call it Software Engineering? Why not just call it programming or software development?
SOFTWARE ENGINEERING. Objectives Have a basic understanding of the origins of Software development, in particular the problems faced in the Software Crisis.
CS 1110/1111 The Case for Computer Science CS 1110/1111 – Introduction to Programming.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Software Project Management Lecture # 9. Outline Chapter 25 – Risk Management  What is Risk Management  Risk Management Strategies  Software Risks.
Software Engineering (CSI 321) Introduction. Introduction Course Title: Software Engineering Course Code: CSI-321 Credit Hours: 3 Section: 1 2.
1 Introduction to Software Engineering Wen-Yang Lin Dept. of Computer Science and Information Engineering National University of Kaohsiung February, 2007.
MANAGING COMPLEXITY Lecture OO01 Introduction to Object-oriented Analysis and Design Abstract Data Types.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 1 Slide 1 Chapter 1 Introduction As modified by Randy Smith.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 6/6/2016 1/25 IT076IU Software Engineering Project Review 2.
FCE Speaking Test – Part 3
1 Use Cases Object-Oriented Modeling and Design with UML (Second Edition) Blaha & Rumbaugh Sections 7.1, 8.1.
Information System Design IT60105 Dr. D. Samanta Contact:
Lecture 0 Software Engineering Course Introduction
The Unified/Rational Unified Process (UP/RUP) Defined
Advanced Programing practices
Object-Oriented and Classical Software Engineering Sixth Edition, WCB/McGraw-Hill, 2005 Stephen R. Schach
Presentation transcript:

COMP 2007 R J Walters

COMP Introduction Try to place this course in context A bit of history “Engineering”?

COMP Software Engineering: Who cares? I do Its what this course is about I don’t really trust the way we make software these days It should lead to better software (I’m being paid to)

COMP Who cares? You do You need it to pass this course You need it for the group project, and your own project next year It’s what real developers get paid to do It might help you get a job I’ll be marking some of this course and COMP 2012

COMP What Am I talking about? Compare Software with Hardware Characteristics of the activity of building Software It is new It isn’t constrained by the “real world” It can be very big (complex)

COMP Where are we now? Clever systems are everywhere Many of them are a bit suspect Describing the way we build software as Engineering is still stretching things a bit

COMP How did we get into this mess? Initial concentration on hardware Complacency Tolerance Crisis? What crisis?

COMP Where have we been? Rats nest Machine language and assembler The flow-chart and the goto Structured programming Modules, dataflow, SSADM, Jackson (JSD) and all the rest Objects Java, UML

COMP A few asides “Proprietary” methods Formal methods Extreme programming Prototyping Component based systems

COMP Where will it end? OO might be it Or it might not Engineering software is what we ought to be doing

COMP Engineering? Build things in such a way that we know: It will do the job and how reliable it will be How much it will cost and how long it will take to make What we did and how to make another (better) one

COMP Engineering? There is more to Software Engineering than the programming paradigm Requirements and Specification Design Testing Maintenance Documentation Process Standards?

COMP To sum up Software Engineering is something we have to worry about It is more than the programming language we use It is what enables teams to build big systems We don’t have all the answers

COMP Questions? Suggested reading Your UML reference Software Engineering, 7th Edition, Ian Sommerville Software Engineering: A Practitioner's Approach, Roger Pressman

COMP