Request for Proposal (RFP) In response to the RFP – the first step is to prepare a proposal 1. Review Customer Requirements and come up with candidate.

Slides:



Advertisements
Similar presentations
Project Management.
Advertisements

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.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
1 Chapter 2: Product Development Process and Organization Introduction Importance of human resources: Most companies have similar technology resources.
CSE 308 Project Management. SWE Communication Skills Management: Run a team meeting Presentation: Present aspects of your project during its development.
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.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Project Plans CSCI102 - Systems ITCS905 - Systems MCS Systems.
Final Report Document. Format Title Page Executive Summary Table of Contents Introduction Mission Statement Main PDS items Brief justification of the.
Chapter 14 INTRODUCTION TO SYSTEMS DEVELOPMENT. Systems Development Methodology Important issues in systems development: Must be aligned to business strategy.
What is a project? Project Management Institute definition
The Proposal. Project Proposals Genesis of Proposals: They can result for formal requests (e.g. Request For Proposal, RFP) They can be unsolicited (e.g.
Information Systems Development Lecture 2: the idea of the Life Cycle.
Chapter 3: The Project Management Process Groups
Project Tracking and Scheduling Infsy 570 Dr. R. Ocker.
Project Management and Scheduling
Effective Methods for Software and Systems Integration
© 2005 Prentice Hall14-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Chapter 2: Overview of Essentials ISE 443 / ETM 543 Fall 2013.
Copyright 2002 Prentice-Hall, Inc. Managing the Information Systems Project 3.1 Chapter 3.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Computer System Analysis
 A project is “a unique endeavor to produce a set of deliverables within clearly specified time, cost and quality constraints”
S/W Project Management
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Recap from last week Understand organizations, including the four frames, organizational structures. Explain why stakeholder management and top management.
IT 499 Bachelor Capstone Week 8. Adgenda Administrative Review UNIT Seven UNIT Eight Project UNIT Nine Preview Project Status Summary.
Requirements Engineering CSE-305 Requirements Engineering Process Tasks Lecture-5.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
Software Engineering Management Lecture 1 The Software Process.
Software Project Management Lecture # 7. What are we studying today? Chapter 24 - Project Scheduling  Effort distribution  Defining task set for the.
Rev. 0 CONFIDENTIAL Mod.19 02/00 Rev.2 Mobile Terminals S.p.A. Trieste Author: M.Fragiacomo, D.Protti, M.Torelli 31 Project Idea Feasibility.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Software Project Management By Deepika Chaudhary.
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
University of Southern California Center for Systems and Software Engineering Barry Boehm, USC CS 510 Software Planning Guidelines.
Design Proposal A document prepared to (a) justify the need for the project, (b) describe the engineering process to be taken, (c) outline the expected.
IS Analysis and Design. SDLC Systems Development Life Cycle Break problems into management review stages Control cost and time Works best with well understood.
Request for Proposal (RFP)
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design.
Requirement Engineering. Recap Elaboration Behavioral Modeling State Diagram Sequence Diagram Negotiation.
Information Systems System Analysis 421 Chapter 3 Managing the Information Systems Project.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Team-Based Development ISYS321 Managing the Information Systems Project.
1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.
By: Wilmer Arellano.  1. Form a team  2. Find a Team Leader  3. Find Three Potential Topics  4. Find a Mentor  5. Select a Topic.
Chapter 2- Software Development Process  Product Components  Software Project Staff  Software Development Lifecycle Models.
HNDIT23082 Lecture 10:Software Project Management
Project Management PTM721S
Software Engineering Management
Supporting quality devices
Project Management PTM721S
Chapter 6: Database Project Management
Software Planning Guidelines
Software Life Cycle “What happens in the ‘life’ of software”
Class 7 – Inception Phase: Steps & techniques
BSA 376 Competitive Success/snaptutorial.com
BSA 376 Education for Service/snaptutorial.com
BSA 376 Teaching Effectively-- snaptutorial.com
Request for Proposal (RFP)
Project Management Process Groups
Project management Learning Unit 5.
DOD’S PHASED SYSTEM DEVELOPMENT PROCESS
PSS verification and validation
Presentation transcript:

Request for Proposal (RFP) In response to the RFP – the first step is to prepare a proposal 1. Review Customer Requirements and come up with candidate designs 2. Review advantages and risks of design, decide development tools ( hardware and software) 3. Life-cycle model for the project – systematic breakdown of project phases, etc.

Step 1 Understand needs of end user – Design constraints – Criteria for evaluating/ranking designs – Feasible designs – ranking and trade-offs Assess and Manage Risks Develop models for systems, sensors, interfaces - subsystems – sequential or parallel interconnected systems Validation of models (input-output)

Step 2 Decide development strategy – Top down, bottom up, combination Development tools – Software components,(compilers, libraries, support s/w)

Step 3 Project phases (concept, overall design, detailed design, coding development/ build and test) – Project demos – Identify deliverables – Determine specification list and evaluate against original design specs ( iteratively develop a proposal that meets the customer needs)

Technical Section – Identify customer needs (VOC Lecture) Understand the objectives, Meet with customer and Ask questions – Constraints Generic - Standards, delivery date, quantity, safety, emi, Non-generic - environmental conditions, aesthetics, packaging, etc. – Background Prior work and their shortcomings – Design Specifications (meet with your customer/sponsor) – Design parameters – Translate customer needs to design parameters Relevance of each parameter to design criteria that must be satisfied Candidate Designs (more than 1 design) – Evaluate/rank designs ( feasibility and decision matrices) – Expected Outcomes – Test plan – to demonstrate specs have been met

Project Management Personnel Tasks Contribution of each team member Resources needed/ procurement Timeline – Tasks, integration, reports, presentations, demonstrations Gantt Charts – (rough draft for pre-proposal)

Full Proposal – Due Week 6

Proposal Format No more than 15 typed pages – Cover page Title, design team #, facilitator, Document type Design team members, date – Executive summary – TOC – Introduction – Background – Objectives – FAST Diagram – Conceptual Designs, Ranking – Proposed design – Risk Analysis – Project Management – Budget – References (plagiarism) – Appendix

Questions

Technical Communications Reports- Pre-proposal Full Proposal Design Issues Interim Progress Reports - Status of project Final Report - Informs management/client of the final result, operating manual (use and trouble shooting) Application Notes- detailed description of the use of the product Professional Self-Assessment Oral Presentations

Formal Report Structure