COMP 2007 R J Walters. COMP 2007 - 2 Last time Software Engineering is important It is “soft” - Not easy Making things using an “engineering” approach.

Slides:



Advertisements
Similar presentations
Chapter 24 Quality Management.
Advertisements

Configuration management
Software change management
AGILE DEVELOPMENT Outlines : Quick Look of agile development Agility
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 المحاضرة الثانية.
COMP 474 Software Engineering Professor William L. Honig.
CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.
1 SWE 513: Software Engineering Requirements II. 2 Details in Requirements Requirements must be specific Examples -- university admissions system Requests.
8 September Announcements  GIT Class: Friday 3-5 SN 115 (Peter Parente)  Information for Project Links PageProject Links Page  Hot Topics Teams.
CS 290C: Formal Models for Web Software Lecture 10: Language Based Modeling and Analysis of Navigation Errors Instructor: Tevfik Bultan.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
7M701 1 Software Engineering Software Requirements Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 5
Overview of Software Requirements
COMP 2007 R J Walters. COMP Remember - Documentation Defines your Engineering process Includes Requirements Design Testing User manuals Other.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 An Introduction to Software Engineering.
7M822 Software Requirements Introduction 7 September 2010.
An Introduction to Software Engineering
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 5 Slide 1 Requirements engineering l The process of establishing the services that the.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
Software Documentation Written By: Ian Sommerville Presentation By: Stephen Lopez-Couto.
CASE Tools And Their Effect On Software Quality Peter Geddis – pxg07u.
1 Software Engineering CEN5035 copyright © 1996, 2001 R.S. Pressman & Associates, Inc.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 6 Slide 1 Software Requirements.
1 Chapter 5 Practice: A Generic View Software Engineering: A Practitioner’s Approach, 6th edition by Roger S. Pressman.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
©Ian Sommerville Software Engineering Slide 1 Software Requirements l Definition: Description and Specifications of a system l Topics covered: Functional.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 The requirements engineering process.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 1 Slide 1 An Introduction to Software Engineering.
Software Requirements Engineering: What, Why, Who, When, and How
Fun, fun, fun. But first … the code review Preparation Process.
COMP 2007 R J Walters. COMP Introduction Try to place this course in context A bit of history “Engineering”?
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Analysis Workflow l The primary activities of the Analysis workflow are.
Software Engineering. Introduction Objective To familiarize students to the fundamental concepts, techniques, processes, methods and tools of Software.
© Bennett, McRobb and Farmer Avoiding the Problems Based on Chapter 3 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design.
Software Production ( ) First Semester 2011/2012 Dr. Samer Odeh Hanna (PhD)
1 Software Requirements l Specifying system functionality and constraints l Chapters 5 and 6 ++
Software Engineering, 8th edition. Chapter 7 1 Courtesy: ©Ian Sommerville 2006 March 20 th, 2008 Lecture # 12 Requirements Engineering Processes.
The Software Development Process
Systems Development Life Cycle
Copyright 2010, The World Bank Group. All Rights Reserved. Testing and Documentation Part II.
Introduction to Testing. Topics Who are we? Who are we? Software Testing Definition and Goals Software Testing Definition and Goals Facts and Numbers.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Packets.
LehighUML Project John Pequeno, Adam Balgach, Sally Moritz & Professor Glenn Blank.
The Art of Programming. The process of breaking problems down into smaller, manageable parts By breaking the problem down, each part becomes more specific.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
COMP2110 Software Design in 2003 ● a(nother) framework for Software Engineering ● the Software Engineering ideas and concepts in comp2110 ● Organisation.
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.
Requirements Analysis
Software Engineering INTRODUCTION TO SOFTWARE DEVELOPMENT.
Professional Development of Software Engineers First day summary.
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
1 Introduction to Software Engineering Wen-Yang Lin Dept. of Computer Science and Information Engineering National University of Kaohsiung February, 2007.
Requirement Analysis SOFTWARE ENGINEERING. What are Requirements? Expression of desired behavior Deals with objects or entities, the states they can be.
DE?!GN software. COMP2110 Software Design in 2004 Chris Johnson 1.Software Requirements and Software Design in a framework for Software Engineering 2.The.
Requirements. Outline Definition Requirements Process Requirements Documentation Next Steps 1.
1 The Software Engineering Education at CSULA Jiang Guo Jose M. Macias June 4, 2010.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 6 Slide 1 Software Requirements (utvalgte foiler fra Kap 6 og 7 i Sommerville)
CIS 339 Entire Course (UOP) FOR MORE CLASSES VISIT CIS 339iLab 1 System Requirements CIS 339 iLab 2 of 7 CIS 339iLab 3 - Structural.
CIS 339 Competitive Success/snaptutorial.com
CIS 339 Education for Service/snaptutorial.com
Basic SDLC Models SDLC  System Development Life Cycle.
FInal Presentation : Object Oriented Software Engineeering
Software requirements
Software Requirements
Software Requirements
Commenting on Artifacts
Presentation transcript:

COMP 2007 R J Walters

COMP Last time Software Engineering is important It is “soft” - Not easy Making things using an “engineering” approach Building good systems People working in teams We don’t have all the answers

COMP Today General comments on documentation Requirements

COMP Documentation Shouldn’t be an afterthought Defines your process Includes: Requirements Design Code Testing User manuals Other things

COMP Documentation You have already seen what you need UML Remember what you are doing it for So you know what you are doing Smooth operation of your team So others can see what you did An aid to maintenance Because the clients asked for it

COMP Documentation - style High/low ceremony Do you want/need copious supporting evidence for everything? Would something informal be appropriate? Something in between? Fix it up later? “Faking it” A Rational Design Process: How and why to fake it - David L. Parnas (and others)

COMP

Requirements Why do they matter? What are they? Techniques

COMP Why do requirements matter? Starting point for what you are going to make Form the basis of your contract with the client They are what you test against

COMP What are requirements? The definition of what the required system should do Who it is for, what it does, what it looks like, what it does who will use it … Don’t forget Non Functional Requirements …

COMP Techniques You have seen this before In UML Use cases Sequence diagrams … Other methods possible Structured English

COMP Where does it go wrong? Clients and developers struggle to communicate Clients ask for what they think you can deliver Developers offer what they think the client wants Moving target Need for management

COMP Spiral model fits here Diagram by from Software Engineering 7 by Ian Sommerville

COMP Requirements - Observations Historically there wasn’t much need First machines built to solve specific problems (Eniac, Colossus) Done badly (or not at all) Lack of clarity and precision Misunderstandings Errors Creep

COMP Summary Software Engineering is … Documentation Requirements

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

COMP