©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Review 1.

Slides:



Advertisements
Similar presentations
Objectives To introduce software project management and to describe its distinctive characteristics To discuss project planning and the planning process.
Advertisements

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 المحاضرة الثانية.
1 Chapter 4 - Part 1 Software Processes. 2 Software Processes is: Coherent (logically connected) sets of activities for specifying, designing, implementing,
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.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Project.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 Project management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Review 2.
1 SOFTWARE LIFE-CYCLES Beyond the Waterfall. 2 Requirements System Design Detailed Design Implementation Installation & Testing Maintenance The WATERFALL.
7M701 1 Software Engineering Software Requirements Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 5
Software Engineering General Project Management Software Requirements
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 COMP201 Project Management.
Review for Exam #1 Chapters 1 - 8
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Process Models.
©Ian Sommerville 2000 Software Engineering, 6th edition Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing.
Overview of Software Requirements
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Review 1.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 5 Slide 1 Project management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
7M822 Software Requirements Introduction 7 September 2010.
©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 5 Slide 1 Project management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Chapter 4 Project Management.
Chapter 3 Software Processes.
Chapter 3 Project Management
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Rapid software development to validate requirements.
©Ian Sommerville 2006Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
©Ian Sommerville 2000Software Engineering, 7th edition. Chapter 5 Slide 1 Chapter 5 Project Management Modified by Randy K. Smith.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Concerned with activities involved in ensuring that software is delivered: on.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
1 Software Engineering Chap 1 Instructor : Haya Samamneh.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Animating and.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 1 Software Processes (Chapter 3)
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 3 Slide 1 Software Processes l Coherent sets of activities for specifying, designing,
Software Engineering Management Lecture 1 The Software Process.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Project management l Organising, planning and scheduling software projects.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
Course Overview Stephen M. Thebaut, Ph.D. University of Florida Software Engineering Foundations.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Software Engineering, 8th edition. Chapter 5 1 Courtesy: ©Ian Sommerville 2006 Oct 13 th, 2008 Lecture # 6 Project management.
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 systems analysis 1 what is systems analysis? preparation of the system’s requirements/definition,
©Ian Sommerville 2000Software Engineering, 7th edition. Chapter 26Slide 1 Software cost estimation l Predicting the resources required for a software development.
Software Life Cycle The software life cycle is the sequence of activities that occur during software development and maintenance.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Packets.
Dr Izzat M Alsmadi Edited from ©Ian Sommerville & others Software Engineering, Chapter 3 Slide 1 Project management (Chapter 5 from the textbook)
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Project management l Organising, planning and scheduling software projects.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 6/6/2016 1/25 IT076IU Software Engineering Project Review 2.
Chapter 3 Project Management Parts of this presentation is extracted from Ian Sommerville’s slides located at
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 6 Slide 1 Software Requirements (utvalgte foiler fra Kap 6 og 7 i Sommerville)
Overview of Software Project Management cont Review – Class 6 Scheduling Tasks Project Management Activities CEN 4010 Class 8 – 09/22.
HNDIT23082 Lecture 10:Software Project Management
Software Engineering Management
Requirements Analysis
Presentation transcript:

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Review 1

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 2 Exam 1 l Tuesday, 03/11/08 l 1-hour l Closed book l Chapters 1,3-7 l 20% of your total grade

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 3 Exam topics -1 l Chapter 1 Software engineering vs. system engineering Software process Software cost

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 4 Exam topics -2 l Chapter 3 Critical system Reliability and availability Safety and security l Chapter 4 Waterfall model Evolutionary development Exploratory development and throw-away prototype Component-based development Process iteration CASE tool

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 5 Exam topics -3 l Chapter 5 Project planning Milestones Deliverables Project scheduling Bar charts and activity networks Risk management

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 6 Exam topics -4 l Chapter 6 User requirements System requirements Functional/non-functional requirements Domain requirements Requirement documents

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 7 Exam topics -5 l Chapter 7: Requirement Engineering Process Stakeholders Viewpoints Feasibility studies Scenarios User cases Requirement validation Requirement management

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 8 Sample exam questions - 1 l 1. Are the following statements about the software requirements document true or false? (1) Software engineering is only useful for those who become software engineers. (2) The requirements document should not specify responses to undesirable events.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 9 Sample exam questions - 2 l (2) System Requirements are A. A detailed list of services and constraints of a proposed system B. A natural language statement of the functionality a system should provide C. A list of basic requirements the system must meet to run the software D. Not on this test (wishful thinking) E. None of the above

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 10 Sample exam questions - 3 l (3) User Requirements are A. A detailed list of services and constraints of a proposed system B. A natural language statement of the functionality a system should provide C. A list of basic requirements the user must meet before using a given system D. Not condoned by my religion E. None of the above

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 11 Sample exam questions - 4 l 3. Short answers l (1) Describe the waterfall model of software development. What are some of its advantages and disadvantages? What alternatives exist? l (3) What is the difference between exploratory and throw-away prototyping? l (4) What is one major difference between System Engineering and Software Engineering, as disciplines?

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 12 Sample exam questions - 5 l (5) Give one specific example of an organizational non-functional requirement of each variety below. (a) Delivery: (b) Implementation: (c) Standards:

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 13 Sample exam questions - 6 l 4. Match each system to the most appropriate model and briefly justify your decision. l Software Process Models A. Waterfall Model B. Evolutionary Development C. Reuse-oriented Development l __3D modeling and animation software designed to have a revolutionary user interface and novel algorithms for creating surreal scenes __A shopping cart module for a website that needs to be up and running with basic functionality within a week __Implementation of a Linux driver for a hardware device where full specifications are available from the manufacturer

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 14 Sample exam questions - 7 l 6. Describe functional and non-functional requirements in the following categories. Functional requirementNon-functional requirement Definition List the requirements (three for each type) for a university library system

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 15 Sample exam questions - 8 TaskDuration (days)Dependencies T110 T210T1 T315 T45T1,T3 T515T2 T615T3 T715 T815T3,T4,T5 T935T7 T1020T4,T6 T1110T9 T1220T10 T1315T4,T5 T1410T11,T8 T1520T12,T14 T1615T13,T15 The accompanying table sets out a number of activities, durations, and dependencies. Draw an activity chart and identify the critical path(s). What is the length of the critical path?