How do the Process Model, WBS, SPMP, Goal Statement,

Slides:



Advertisements
Similar presentations
© 2007 AT&T Knowledge Ventures. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Knowledge Ventures. Interactive Solutions & Design Group.
Advertisements

1 Software Processes A Software process is a set of activities and associated results which lead to the production of a software product. Activities Common.
Object-Oriented Analysis and Design LECTURE 2: INCEPTION PHASE.
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
IS Theories & Practices Systems Architecture & Infrastructure IS 655: Supplementary Note 1 CSUN Information Systems.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Project Management.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Acquiring Information Systems and Applications
Acquiring Information Systems and Applications
Acquiring Information Systems and Applications
Systems Development Life Cycle:
Noor Fouad Al-Emadi IEEE 1074 Standard for Developing Life Cycle Processes.
What is a project? Project Management Institute definition
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Software Test Plan Why do you need a test plan? –Provides a road map –Provides a feasibility check of: Resources/Cost Schedule Goal What is a test plan?
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
Effective Methods for Software and Systems Integration
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Copyright 2002 Prentice-Hall, Inc. Managing the Information Systems Project 3.1 Chapter 3.
Computer System Analysis
Goal and Scope Where are we going and what path will we be taking?
S/W Project Management
RUP Fundamentals - Instructor Notes
Software Development *Life-Cycle Phases* Compiled by: Dharya Dharya Daisy Daisy
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Software Project Failure Software Project Failure Night Two, Part One CSCI 521 Software Project Management.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
Project Life cycles BTEC National.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Common Activities Activities and Tasks in the WBS.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 1: Introduction to Systems Analysis and Design Alan.
Software Life Cycle The software life cycle is the sequence of activities that occur during software development and maintenance.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design.
Information Systems System Analysis 421 Chapter 3 Managing the Information Systems Project.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
Chapter 2 Project Management Methodologies. A project life cycle PlanDesignDevelop Integrate (including test) DeployMaintain They can be iterative and.
Global Rectifier Diode Industry Product, Trends, Growth Research Report 2015 Published: Sep 2015 Single User License: US$ 2800 Corporate User License:
ITS PMO Framework Enhancing Stakeholder Engagement & Cross Functional Transparency Jimmy Goyal June
Systems Analysis and Design in a Changing World, Fifth Edition
Chapter Five Project Planning.
Chapter 3 Managing the Information Systems Project
Lecture 3 Prescriptive Process Models
Chapter 6: Database Project Management
WORK BREAKDOWN STRUCTURE
Operations an exploration of basic manufacturing operations, forecasting, budgeting and control.
IEEE Std 1074: Standard for Software Lifecycle
Systems Analysis – ITEC 3155 Evaluating Alternatives for Requirements, Environment, and Implementation.
Software Process Models
Accounting Information Systems: A Business Process Approach
Defining the Activities
INF 342 Enthusiastic Study/snaptutorial.com
Module C: Presentation The Engineering / Design Process
Chapter 3 Managing the Information Systems Project
Chapter 1 (pages 4-9); Overview of SDLC
Created by Katy Koenen © Microsoft Corporation
Chapter 3 Managing the Information Systems Project
By Mr. BZ Engineering and Design Fall 2011
Design Process.
Executive Project Kickoff
Chapter 2 Managing the Information Systems Project
System Analysis and Design:
Project Management II The Project Value Creation Process
Presentation transcript:

How do the Process Model, WBS, SPMP, Goal Statement, Example How do the Process Model, WBS, SPMP, Goal Statement, etc. etc. etc. all fit together?

The Problem We manufacture widgets. Sometimes our stock of raw materials runs too low, and production must slow down / stop. Hence, we need software that will automatically forecast raw materials needs for purchasing based on analysis of various data sets (production equipment, sales orders, etc.)

Possible Solutions Plan A: Plan B: buy it off-the-shelf build it ourselves

Approach Build it a piece at a time start with easy decision feasibility of getting the needed data, determine algorithms, etc. second version will address overall look and feel third version will implement most important decision create something that concretely shows project's value repeat until done

Step One - getting organized create a goal statement identify the key players keepers of data champions of the project final decision makers etc

Statement of Work Contents: Step Two - Write the SOW Statement of Work Contents: Goal Scope Deliverables Criteria for Success etc

Step Three - Process Model Selection Spiral Life Cycle Gather Requirements Design Code Test Repeat

Step Four - Plan Activities How do we decide what all we need to do? Based on Past WBSs Based on Brainstorming about Tasks Based on IEEE 1074 ?

Step Four - Using 1074 to select activities 6. Plan Project Management 7. Analyze Risks 9. Manage the Project 10. Retain Records 11. Implement Problem Reporting 15. Identify Quality Improvement Needs 16. Identify ideas and needs 17. Formulate Potential Approaches 25. Define Interface Requirements 28. Define Database 29. Design Interfaces 30. Develop Algorithms 32. Create Test Data 33. Create Source Code 37. Perform Integration 50. Execute V&V Tasks 54. Execute the Tests

Step Five - Build the Work Breakdown Major Activities in the WBS: 1. Project Functions 2. Conduct Feasibility Study 3. Design Interface Architecture 4. Most Important Problem 5. Next Problem 6. Re-Evaluation of Project 7. Development Continuation 8. Deployment

Step Five - Build WBS 1. Project Functions 1.1 Retain Records (10) 1.2 Plan Configuration Management (55) 1.3 Perform Configuration Control (57) 1.4 Collect and Analyze Metric Data (51) 1.5 Produce Internal Documentation (61)

Step Five - Build WBS 2. Feasibility 2.1 Analysis 2.1.1 Identify Major Needs (16) 2.1.2 Formulate Potential Approaches(17) 2.1.3 Decide what is easiest to do. 2.2 Design 2.2.1 Design Database (28) 2.2.2 Design Interfaces (29) 2.2.3 Develop Algorithm (30) 2.3 Code 2.3.1 Create Test Data (32) 2.3.2 Create Source Code (33) 2.4 Test 2.4.1 Execute Tests (54) 2.4.2 Execute V&V (50) 2.4.2.1 Is this Worthwhile? 2.4.2.2 Determine key problem for next phase 2.4.2.3 Decide if to go forward

Step Six - Estimate Size and Duration Step Seven - Estimate Cost Step Eight - Use WBS and size estimates to create project plan Step Nine - Begin Activities 1 and 2