22 September 2010. Fundamental Steps STEPS  Requirements  Design  Implementation  Integration  Test  Deployment  Maintenance MODELS Waterfall.

Slides:



Advertisements
Similar presentations
Chapter 7: Software production process Refers to the activities that are used for building, delivering, deploying, and evolving a software product, from.
Advertisements

Information technology solutions development Fundamentals of Information Technology Session 3.
SDLC – Beyond the Waterfall
Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 المحاضرة الثانية.
Chapter 2 Modeling the Process and Life Cycle Shari L. Pfleeger
29 September Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will.
 © Ian Sommerville A software process model is an abstract representation of a process. It presents a description of a process from some particular perspective.
CS 325: Software Engineering January 13, 2015 Introduction Defining Software Engineering SWE vs. CS Software Life-Cycle Software Processes Waterfall Process.
System Development Life Cycle Process of creating and altering systems or software by using methodologies or models to develop the systems in a logical.
Chapter 2 – Software Processes Lecture 1 1Chapter 2 Software Processes.
Object-Oriented Analysis and Design
Software Process and Problem Statements CSSE 371, Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 3, 2004.
8 September Announcements  GIT Class: Friday 3-5 SN 115 (Peter Parente)  Information for Project Links PageProject Links Page  Hot Topics Teams.
20 September Importance of People Most important factor in the quality of software is the quality of the programmers If your life depended on.
SWE Introduction to Software Engineering
Software Engineering. How many lines of code? Average CS1004 assignment: 200 lines Average CS4115 project: 5000 lines Corporate e-commerce project: 80,000.
Introduction to Requirements (Chapters 1-3 of the requirements text) CSSE 371, Software Requirements and Specification Don Bagert, Rose-Hulman Institute.
1 SOFTWARE LIFE-CYCLES Beyond the Waterfall. 2 Requirements System Design Detailed Design Implementation Installation & Testing Maintenance The WATERFALL.
Software Engineering.
Requirements - Why What and How? Sriram Mohan. Outline Why ? What ? How ?
18 January Writing a Functional Spec. Administrivia How many teams will want departmental web space vs links to your own space? Please send me your CS.
SYSTEMS ANALYSIS AND DESIGN INTRODUCTION 1. Systems Analysis and Design is the process people use to create (automated) information systems Systems Analysis.
SYSTEMS ANALYSIS AND DESIGN INTRODUCTION 1. Systems Analysis and Design is the process people use to create (automated) information systems Systems Analysis.
1 CMPT 275 Software Engineering Software life cycle.
Lecture # 04 & 05 CS314 Introduction To Software Development Software Development Process (SDP) Instructor :Muhammad Janas khan
Diane Pozefsky. Engineering  Turning ideas into reality  Creating something useful from other things using science and math.
3 September Engineering  Turning ideas into reality  Creating something useful from other things using science and math.
When is Agile the Best Project Management Method? Lana Tylka.
Why Written Requirements?  Unambiguous  Defines goals  Cost of finding a requirements bug later can be 100 times more expensive.
Interaction Design CMU. Today’s objectives Continue Design approaches (UCD, ACD)  User-Centered Design  Activity-Centered Design.
Engineering  Turning ideas into reality  Creating something useful from other things using science and math.
REQUIREMENTS - WHY WHAT AND HOW? Steve Chenoweth & Chandan Rupakheti CSSE 371 Chapters Requirements Text. Question 6.
1. Introduction Iterative Development & the Unified Process.
3 September Sources of requirements  People Stakeholders ○ Who are the stakeholders? Issues: ○ Conflicting requirements ○ Wants vs. needs Helping.
Prototyping By: Michael McBee & Shere Stewart. Prototyping What is Prototyping? It is an iterative process involving analysts and users where a model.
Software Engineering - Abdul Majeed. What is software? Definition of Software Engineering Software Process Generic view of Software Engineering Software.
Chapter 13: Software Life Cycle Models Omar Meqdadi SE 273 Lecture 13 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
SWE 513: Software Engineering
Ch7: Software Production Process. 1 Waterfall models  Invented in the late 1950s for large air defense systems, popularized in the 1970s  Main characteristics:
Chapter 2 – Software Processes Lecture 1 1Chapter 2 Software Processes.
IS444: Modern tools for applications development Dr. Azeddine Chikh.
Unified Software Practices v 5.0 Copyright  1998 Rational Software, all rights reserved 1 R Rational Unified Process  “de facto standard”, framework.
Software Process Models The slides and the material of this chapter is adopted from: 1. “Software Engineering”, by I. Somerville, 7th Ed., “Software.
Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
10 September Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will.
Slide #18-1 Introduction to Assurance CS461/ECE422 Fall 2008 Based on slides provided by Matt Bishop for use with Computer Security: Art and Science.
4.2 SOFTWARE DEVELOPMENT METHODOLOGGY PRESENTED BY : AZURA IBRAHIM SYARIFAH SYAZA BTE SEYD ZULKAFLY CS230(5A)
Software Development.
Requirements sprint.
Software Engineering Processes
REQUIREMENTS Project management tools
Software Development methodologies
SOFTWARE LIFE-CYCLES Beyond the Waterfall.
Software Processes (a)
Systems Analysis and Design in a Changing World, 6th Edition
Software Process Models
Chapter 2 SW Process Models
Introduction to Software Engineering
Chapter 2 Software Processes
Lecture 2 Revision of Models of a Software Process
11/28/2018 3:34 PM © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN.
Introduction to Software Process Models
Moving from “Bolt-on” to “Build-in” Security Controls
Basic SDLC Models SDLC  System Development Life Cycle.
Chapter 2: Software Process
SOFTWARE LIFE-CYCLES Beyond the Waterfall.
Valuing our place in the world
REQUIREMENTS Project management tools
Presentation transcript:

22 September 2010

Fundamental Steps STEPS  Requirements  Design  Implementation  Integration  Test  Deployment  Maintenance MODELS Waterfall Spiral Iterative DIFFERENCES How often Overhead

Historical Perspective  Waterfall: 1970, built on 1950’s stage- wise processes Recognized need for feedback  Iterative (agile): late 70s,modeled on evolutionary model Didn’t work well for large products  Spiral: 1988, risk-based

Unified Process  Variant of Spiral  Identifies that iterations differ  Also known as Rational Unified Process (Rational products) Rational Unified Process

Personas and User StoriesTypes and Use CasesRequirements

User Requirements - Persona  Microsoft Microsoft  Persona Power Persona Power

Persona excerpt (hotel reservation)

Sources of requirements  People Stakeholders ○ Who are the stakeholders? Issues: ○ Conflicting requirements ○ Wants vs. needs Helping the customer articulate the requirements ○ Use cases  Hardware constraints Laws of physics and nature  Social responsibility

Social responsibility  Privacy  Security  How it will (can) be used Does it have the potential for misuse? Can it be used to harm people?

Sources of Requirements: People vs. Other (Brackett, CMU) % of requirements gathered from people Type of application highly constrained unconstrained missile guidance system flight control system for airliner enhancement to corporate accounting system manufacturing control system corporate accounting system video game decision support system for military tactics relatively lowrelatively high