Scribd
Upload
59 views2 pages

Project Planning Phase Overview

The project planning phase involves orienting yourself to the chosen project context by researching existing similar products and feasibility. The deliverable is a project planning document describing the background research, problem statement, goals, skills, and feasibility assessment. The user requirements phase captures requirements from the user's perspective through meetings without focusing on solutions. The goal is to build on ideas from the project planning document by interacting with end users. The deliverable is a user requirements document describing the purpose, general capabilities, constraints, user characteristics, and specific functional and non-functional requirements.

Uploaded by

rashed44
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
59 views2 pages

Project Planning Phase Overview

The project planning phase involves orienting yourself to the chosen project context by researching existing similar products and feasibility. The deliverable is a project planning document describing the background research, problem statement, goals, skills, and feasibility assessment. The user requirements phase captures requirements from the user's perspective through meetings without focusing on solutions. The goal is to build on ideas from the project planning document by interacting with end users. The deliverable is a user requirements document describing the purpose, general capabilities, constraints, user characteristics, and specific functional and non-functional requirements.

Uploaded by

rashed44
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Project Planning Phase Overview: The project planning phase is meant to give you some breathing room right

at the start in order to (i) orientate yourselves about your chosen project and its context and (ii) think critically about how your final product might look by surveying existing products which are similar. Deliverables Project planning document: (PPD) The PPD describes your initial project management decisions. It summarizes your background research into the problem, culminating in a feasibility assessment. It also identifies any learning objectives necessary to carry out the project. Project planning document will include: 1. Title: 2. Statement of the problem 2.1 Detailed Statement of the Problem 2.2 Motivation 2.3 Goals 2.4 Skills Baseline 3. Background to the Problem 3.1 Commercial background 3.2 Scientific background 3.3 Technical Background 4. Conclusion: Feasibility Assessment 5. References: including URLs, books, journals, conferences, newspapers etc.

User Requirement Phase Overview The user requirements phase concerns the capture and analysis of user requirements. These are a description of the functional and non-functional behavior of the application from the users perspective. At this stage we attempt to describe the problem but not yet the solution. However, necessary solution constraints may be taken into account such as hardware platforms, operating systems, programming languages, etc. Goal Your goal is to build on the initial exploration of product ideas that you carried out in your PPD (either by exploring related commercial products or by studying research tools). You will have to interact intensively with your end users (normally found within your project provider company, but possibly also including customers to that company itself). You will need to hold several meeting in which your record details of user requirements. After each such meeting you should (1) review the output of the meeting, (2) write up the requirements carefully and discuss them, and (3) take the output of these discussions back to the company to confirm that your recorded requirements are complete and correct. Deliverables User Requirement Document (URD) 1. Title Introduction 1.1 Purpose 1.2 Scope of the software 2. General description 2.1 Product perspective 2.2 General Capabilities 2.3 General constraint 2.4 User Characteristic 2.5 Operational environment 3. Specific requirement 4,1 capability requirement 4.2 constraint requirement 4.3 Individual requirement

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy