Soft. Eng. I, Spring 2007Dr Driss Kettani, from I. Sommerville1 CSC-3324: Chapter 3 Title: The Feasibility study Mandatory reading: I. Sommerville, Section.

Slides:



Advertisements
Similar presentations
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapters 1,3 Slide 1 Software Engineering Software Engineering.
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.
Software Engineering Software Engineering is the science and art of building significant software systems that are: 1) on time 2) on budget 3) with acceptable.
CSE 470 : Software Engineering The Software Process.
Soft. Eng. II, Spring 2002Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter II Chap1: Software Engineering Models (Review) Mandatory reading: chapter.
 Dr. Syed Noman Hasany.  Review of known methodologies  Analysis of software requirements  Real-time software  Software cost, quality, testing and.
ISNE101 Dr. Ken Cosh. Recap  We’ve been talking about Software…  Application vs System Software  Programming Languages  Vs Natural Languages  Syntax,
Chapter 2 – Software Processes Lecture 1 1Chapter 2 Software Processes.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
Sommerville, I., Software Engineering, Pearson, 9th Ed., 2010.
Software Engineering Chapter 2: Software Project Management
Soft. Eng. I, Spring 07Dr Driss Kettani, from I. Sommerville1 CSC-3324: Chapter 5 Requirements Engineering Reading: Chap. 6, 7 + annex.
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 2 Software Processes.
Soft. Eng. II, Spr. 02Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter 6 Title : The Software Quality Reading: I. Sommerville, Chap: 24.
Soft. Eng. IDr Driss Kettani1 CSC-3324: Chapter I Introduction and definition Reading: I. Sommerville, Edition 7, Chap. 1.
Soft. Eng. I, Fall 2006Dr Driss Kettani, from I. Sommerville1 CSC-3324: Chapter 6 Software Design Section 10.3 (except )
1 CS 425/625 Software Engineering CS 425/625 Software Engineering Software Processes Based on Chapter 4 of the textbook [SE-7] Ian Sommerville, Software.
1 SOFTWARE LIFE-CYCLES Beyond the Waterfall. 2 Requirements System Design Detailed Design Implementation Installation & Testing Maintenance The WATERFALL.
Introduction to Software Engineering Dr. Basem Alkazemi
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 An Introduction to Software Engineering.
Software Engineering General Project Management Software Requirements
Soft. Eng. II, Spr. 2002Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter 7 Title : Object Oriented Analysis and Design Reading: I. Sommerville,
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Process Models.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 An Introduction to Software Engineering.
Soft. Eng. II, Spr. 2002Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter 1 (cont ’d) Title : Client requirements (Review) Mandatory reading: I.
Systems Analysis and Design in a Changing World, Tuesday, Jan 30.
Soft. Eng. II, Spr. 2002Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter 9 Title : Reliability Reading: I. Sommerville, Chap. 16, 17 and 18.
Soft. Eng. II, Spring 02Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter 6 Title : The Software Reuse Reading: I. Sommerville, Chap. 20.
1 CSC-3324: Chapter 4 Title: What is a requirement? Mandatory reading: Sommerville 6, 7 th ed., Chap.: 7.
Soft. Eng. I, Spring 07Dr Driss Kettani1 CSC-3324: Chapter II The Software life cycle & Software engineering process models Reading: I. Sommerville, Edition.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 An Introduction to Software Engineering.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
Chapter 2- Software Process Lecture 4. Software Engineering We have specified the problem domain – industrial strength software – Besides delivering the.
Chapter 3 Software Processes.
University of Toronto Department of Computer Science CSC444 Lec04- 1 Lecture 4: Software Lifecycles The Software Process Waterfall model Rapid Prototyping.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 System and Software Engineering.
CSI315 Web Applications and Technology Overview of Systems Development (342)
MANAJEMEN PROYEK PERANGKAT LUNAK Program Pendidikan Vokasi Universitas Brawijaya Tahun 2011.
UNIVERSITI TENAGA NASIONAL “Generates Professionals” CHAPTER 4 : Part 1 INTRODUCTION TO SOFTWARE DEVELOPMENT: SYSTEM ANALYSIS & DESIGN.
©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.
INTRODUCTION What is software? What is software engineering?
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
 CS 5380 Software Engineering Chapter 2 – Software Processes Chapter 2 Software Processes1.
Software Engineering Management Lecture 1 The Software Process.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 1 Slide 1 An Introduction to Software Engineering.
Chapter 1: Introduction Omar Meqdadi SE 2730 Lecture 1 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
An Introduction to Software Engineering. Communication Systems.
1 Software Engineering Ian Sommerville th edition Instructor: Mrs. Eman ElAjrami University Of Palestine.
Chapter 13: Software Life Cycle Models Omar Meqdadi SE 273 Lecture 13 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
 Dr. Syed Noman Hasany.  Review of known methodologies  Analysis of software requirements  Real-time software  Software cost, quality, testing and.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
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 Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
INFM 736 and 737: MIM Capstone Experience Information Session DR. WEAVER UNIVERSITY OF MARYLAND ISCHOOL TETYANA BEZBABNA UNIVERSITY OF.
Software Development Security Chapter 10 Part 3 Pages 1108 to 1125.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 1 Slide 1 Chapter 1 Introduction As modified by Randy Smith.
CS 310 Ch 4: Software Processes Software process: a set of activities that lead to a software system specification design and implementation validation.
Advanced Software Engineering Dr. Cheng
Software Engineering Management
Software: Process and Product
Systems Analysis & Design N106
Chapter 2 Software Processes
Software Engineering Software Engineering is the science and art of
Software Engineering Software Engineering is the science and art of
Requirements Document
Chapter 2 Software Processes
Presentation transcript:

Soft. Eng. I, Spring 2007Dr Driss Kettani, from I. Sommerville1 CSC-3324: Chapter 3 Title: The Feasibility study Mandatory reading: I. Sommerville, Section 7.1

Soft. Eng. I, Spring 2007Dr Driss Kettani, from I. Sommerville2 Wrap up... What is Software Engineering (SE) ? The major goal of SE is to produce good software cost effectively… What is good software? In order to produce good software, we need to follow a good SE process… What is a good process? Some SE process models are widely used and universally recognized… Software engineering is concerned with theories, methods and tools for professional software development Maintainability, Dependability, Efficiency, Usability Understandable, Visible, Supported, Accepted, Reliable, Rapid, etc. Structured set of activities (steps) required to develop a software system.... The waterfall model Separate and distinct phases of specification and development Prototyping development Specification and development are interleaved Component-based development The system is assembled from existing components

Soft. Eng. I, Spring 2007Dr Driss Kettani, from I. Sommerville3 The feasibility study...

Soft. Eng. I, Spring 2007Dr Driss Kettani, from I. Sommerville4 The feasibility study... No matter which SE process we want/expect to follow, we must previously perform a feasibly study in order to demonstrate: The business opportunity; The feasibility of the project in terms of technology enablers and schedule constraints… Our global understanding of the requirements and our confidence in a future better understanding… Must be quick and cheap... Typically in Morocco, it is about 10M/D, Dhs… Depends on the context…

Soft. Eng. I, Spring 2007Dr Driss Kettani, from I. Sommerville5 The feasibility study... The formal deliverable of the feasibility study is a document that contains at least the following information: An overview of the clients requirements; How the projected system will help... The feasibility of the project with respect to our expertise... The feasibility of the project with respect to the available of technology enablers... The Business opportunity for our company... A formal Go (or Stop)... An expected schedule…

Soft. Eng. I, Spring 2007Dr Driss Kettani, from I. Sommerville6 Important issues to check... What are current problems? How will the proposed system help? What will be the integration problems? (Current and projected systems) Is new technology needed? What skills? Users... Budget... Schedule...

Soft. Eng. I, Spring 2007Dr Driss Kettani, from I. Sommerville7 Homework and deliverable for next week Find out in the web the standard layout and contents of the feasibility report for the following organizations (only one) and use it in the FOD of your project: DoD: The US Department of Defense; S.E.I.: The Software Engineering Institute (Carnegie Mellon U.); C.S.E.: The Center of Software Engineering (U. of Southern California. Your feasibility and orientation report due on Feb. 12 th 2007