Scribd
Upload
37 views2 pages

The Following Are The Changes Which Need To Be Made To The Old Document

The document outlines changes needed to an old document, including adding a project initiation document defining the project context, objectives, and resources. It also recommends defining the project scope using SMART strategies, purpose, description and constraints. Additional changes are specifying frequency of use, actor descriptions, triggers, pre-conditions, success conditions, main steps, and alternative courses of action.

Uploaded by

krishnaparimalreddy
Copyright
© © All Rights Reserved
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
37 views2 pages

The Following Are The Changes Which Need To Be Made To The Old Document

The document outlines changes needed to an old document, including adding a project initiation document defining the project context, objectives, and resources. It also recommends defining the project scope using SMART strategies, purpose, description and constraints. Additional changes are specifying frequency of use, actor descriptions, triggers, pre-conditions, success conditions, main steps, and alternative courses of action.

Uploaded by

krishnaparimalreddy
Copyright
© © All Rights Reserved
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

The following are the changes which need to be made to the old document:

1. Inclusion of PID (Project Initiation Document) which defines the business context for
a project, clarifies about the objectives, scope, deliverables, timescale of the project,
budget, authority, available resources etc.
2. SCOPE of the project which should include SMART strategy i.e., scope should be
Specific, Measurable, Achievable, Relevant, Time-framed.
3. Purpose of the project.
4. Description and Constraints to be defined.
5. Frequency of use has to be defined i.e., how many times this use case be executed?
6. Actors should be defined (Descriptions)
7. Triggers (What event causes this use case to happen?)
8. Pre-conditions
9. Success end conditions
10. Main steps involved
11. Alternative courses of action

Attribute

Type

Format

Length

Range

Dependency

This section describes the purpose of the Business Requirements.

Business requirements for major enhancements to an existing application.

Business requirements for new application development.

Business requirements for replacement application development.

Business requirements for a request for proposals (RFP).

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