[PDF] Project Definition Document (PDD)



Previous PDF Next PDF







Project Design & Proposal Writing

Feb 02, 2003 · PROJECT DESIGN CYCLE2 Basic project design can be broken into two main parts: understanding problems and designing solutions Underlying these two components is a cycle that consists of the following steps: • Situation analysis: needs assessment, stakeholder analysis and problem analysis • Assessment of organizational capacity



Developing the Project Design Document

CHAPTER 3: DEVELOPING THE PROJECT DESIGN DOCUMENT 37 BOX 3 1: DESCRIPTION OF THE GEMINA PROJECT (PDD EXAMPLE) Title of the project activity: Gemina Rice Husk Project in Nicaragua List of project participants: The Gemina Rice Husk Project is being developed by a joint company, Gemina Generator s created by Grupo Gemina, a



Designing Education Projects - ERIC

who design education projects take the development process to a new level of excellence The manual walks through the basics of needs assessment, project planning and implementation, and evaluation This information is intended to answer questions about the project development process and to be used as an overall project improvement tool



BASICS OF PROJECT PLANNING - Zilicus Online Project

The project schedule may change as project progress; this change can be attributed to change in scope, deliverables, quality and risk aspects of the project It is the people who make the project work hence it is critical to plan for project team



Project Definition Document (PDD)

The Project Definition Document (PDD) forms the technical foundation for a design project Its purpose isto clearlydefine the design problem that will be solved, and to ensure the design team has the requisite resources and capabilities The design problem definition consists of an articulation ofthe need being served, specific objectives



ARCHITECTURAL DESIGN NARRATIVE

ARCHITECTURAL DESIGN NARRATIVE BACKGROUND The Haines Assisted Living Facility is a two-phase project located on a site that offers tremendous southern exposure of the majestic Chilkat Mountains The floor plan is organized around an interior central garden and glazed two-story



Chapter 10: Monitoring and Evaluation (M&E)

TABLE 10 1 Key Elements of Project Design That underpin High-Quality Project M & E KEy PROjECT DESiGn ELEMEnTS DESCRiPTiOn Developing a project ideas (or concept) note A brief, structured description of a set of preliminary ideas and an outline of a proposed project This is written before you commit to detailed project design and proposal



WIND TURBINE DESIGN AND IMPLEMENTATION

project considered the American Association of Civil Engineers (ASCE) Commentary on “Engineering Design ” Economic One of the more important constraints on large‐scale civil engineering projects is economic feasibility The design of the project considered the cost of construction and the materials used

[PDF] methodologie design produit

[PDF] les étapes du design produit

[PDF] démarche design definition

[PDF] cycle de conception pei

[PDF] projet design pei

[PDF] cahier des charges design graphique

[PDF] comment faire un cahier de remédiation

[PDF] test d'entrée en première s

[PDF] cahier de vacances 4eme vers 3eme pdf

[PDF] cahier de vacances 6ème

[PDF] cahier de vacances college pdf

[PDF] weballemand cahier de vacances

[PDF] allemand 6ème pdf

[PDF] exercice allemand 6eme gratuit

[PDF] mise en page planche art appliqué

ASEN 4018 2014/2015

Project Definition Document (PDD)

Document Scope

This document provides guidance for developing the Project Definition Document (PDD) for ASEN 4018, as well as

an annotated template for the assignment.

Purpose

The Project Definition Document (PDD) forms the technical foundation for a design project. Its purpose is to

clearly define the design problem that will be solved, and to ensure the design team has the requisite resources and

capabilities. The design problem definition consists of an articulation of the need being served, specific objectives

and levels of success for the design to satisfy this need in the context of the design course, and specific functional

requirements the design must provide to satisfy those objectives. Team capabilities and resources are assessed

relative to an initial analysis of the critical project elements ("tall poles") that must be addressed for a successful

design solution. This assignment should be approached in the order given, i.e. define the problem and research

related work before the specific objectives are identified. The PDD is developed in cooperation with the project customer, and represents a common understanding

of the project focus, functional requirements, scope, and deliverables. Customer approval is due at the time of PDD

submission. Deviations from the set of objectives provided here will not be permitted without customer and advisor

approval in the form of a revised PDD.

The Projects Advisory Board (PAB) will review the PDD for clarity of purpose and credibility of the critical

project elements, together with the corresponding team capabilities and resources. The PAB will issue a judgment of

"acceptable" or "not acceptable" for readiness to begin the conceptual design phase, along with specific feedback on

weak PDD components. Only teams with an "acceptable" PDD will be permitted to continue with the design

process leading toward the Preliminary Design Review (PDR). Others must revise the PDD until an "acceptable"

project definition is obtained.

Format

The following pages provide a template for your Project Definition Document. Details about what should be

included for each section are provided in the template. The PDD (Sections 1 through 7) shall not exceed 5 pages

including figures, so you must be concise. About ½ page is suggested for each section, except for Section 4 that

contains diagrams that typically make it longer. Students are encouraged to view past project"s work at

orrs566fffOtnjnFvenOpe 6vpFnusvtp6upPcnF7epucAPOmlnFmpEvSsjpumnl CMMmtnSsnPpPruOm8ppsmcPmScPemrovrmusptclctm

Fp5 cFpSpPrumlnFmropmCMMmovapmtovPApemnapFmropmRpvFu3mvPemsvurmfnF(mSvRmPnrml jjRmveeFpuumropmcrpSumcPmrocum

vuucAPSpPrOm

Due Date

Your PDD will be submitted to D2L by 6:00 pm, Monday, 9/15. Customers must sign off on your document before

submission. PDD

8/29/2014

Project Definition Document ASEN 4018

University of Colorado

Department of Aerospace Engineering Sciences

ASEN 4018

Project Definition Document (PDD)

PROJECT NAME HERE

Approvals

Name .llcjcvrcnPm.ssFnapemMvrpm

) urnSpFm )n Fupm )nnFecPvrnFmMvjpm;vfFpPtpm)?6.N0m

Project Customers

NAME d.=Nm

.MM8N00m.MM8N00m

ConPp5mConPp5m

NSvcj5mNSvcj5m

Team Members

NAME Contact info (email, phone, etc.) d.=Nm)nPrvtrmcPlnmbpSvcj3msonPp3mprtO1m d.=Nm d.=Nm )nPrvtrmcPlnmbpSvcj3msonPp3mprtO1m d.=Nm )nPrvtrmcPlnmbpSvcj3msonPp3mprtO1m d.=Nm )nPrvtrmcPlnmbpSvcj3msonPp3mprtO1m d.=Nm )nPrvtrmcPlnmbpSvcj3msonPp3mprtO1m

8/29/2014 2

Project Definition Document ASEN 4018

NAME d.=Nm

1.0 Problem or Need

Describe the field of application, the problem addressed, and the predicted benefits of a successful project.

Pictures or diagrams are encouraged, provided they are annotated or explained clearly.

2.0 Previous Work

Place the problem in context with other work. If this is a continuation of a previous project, clearly identify

what is novel about your project. Cite references to the engineering literature, popular press, or web sites as

appropriate. Do not cite any proprietary documents or personal communication that is not available in the

public domain.

3.0 Specific Objectives

Describe specifically what the project must accomplish to satisfy the design problem or need. Define what

"success" means for yourproject, using levels ranging from the absolute minimum that must be accomplished

for the project to be considered a success (Level 1) up to the most that the project will plan to accomplish

(Level N). Generally, three to four levels are adequate. Do not use "stretch goals" that will be attempted if

time permits. Provide an explicit description of the project deliverables to the course and to the customer,

including how the system will be tested.

4.0 Functional Requirements

Provide a functional block diagram (FBD) here, along with its explanation. It should include the major

functional elements of the system, and how they must interact to solve the problem. It should also show

which elements or aspects will be designed by the team and which elements will be acquired. In many cases,

the senior project will address only a portion of a larger system or problem; the FBD should clearly distinguish the project elements from others in a larger system.

Provide a Concept of Operations (CONOPS) diagram, showing how the system would be eventually operated

in the intended application. Provide a CONOPS specific to yourproject, showing how it will be tested and

operated in this course. (Often, a project addresses only a portion of a larger problem or mission, in which

case these two CONOPS will be different).

5.0 Critical Project Elements

Identify those aspects of the project that are critical to the success defined above, and briefly explain your

reasoning. Include technical, logistic, and financial aspects.

6.0 Team Skills and Interests

Describe the areas of expertise and/or interests of the team members on your project, and relate them to the

critical project elements identified above. Critical Project Elements Team member(s) and associated skills/interests

8/29/2014 3

Project Definition Document ASEN 4018

7.0 Resources

Describe resources beyond team interest/skills needed to address the critical project elements defined above,

and identify the source for each. These include specialized equipment, software, facilities, or outside

expertise, and any additional financial support needed beyond the $5,000 project funds.

Critical Project Elements Resource/Source

8.0 References

Include at least five references.

8/29/2014 4

quotesdbs_dbs20.pdfusesText_26