Systems Planning Vision Statement Assignment

.

Vision Document Draft

for

<Project>

Version 1.0 approved

Prepared by <author>

<organization>

<date created>

Vision Document <Project> Page ii

Contents 1. Introduction ………………………………………………………………………………………………………………4

1.1 Purpose ………………………………………………………………………………………………………………………… 4 1.2 Scope …………………………………………………………………………………………………………………………… 4 1.3 Definitions, acronyms and abbreviations ………………………………………………………………………….. 4 1.4 References ……………………………………………………………………………………………………………………. 4 1.5 Overview ……………………………………………………………………………………………………………………… 5

2. Positioning ………………………………………………………………………………………………………………..6 2.1 Business Opportunity …………………………………………………………………………………………………….. 6 2.2 Problem Statement ………………………………………………………………………………………………………… 6 2.3 Product Position Statement …………………………………………………………………………………………….. 6

3. Stakeholder and User Descriptions …………………………………………………………………………….7 3.1 Market demographics …………………………………………………………………………………………………….. 7 3.2 Stakeholder summary …………………………………………………………………………………………………….. 7 3.3 User summary ………………………………………………………………………………………………………………. 8 3.4 User environment ………………………………………………………………………………………………………….. 8 3.5 Stakeholder profiles ………………………………………………………………………………………………………. 8 3.6 User profiles …………………………………………………………………………………………………………………. 9 3.7 Key stakeholder or user needs: ……………………………………………………………………………………… 10 3.8 Alternatives and competition ………………………………………………………………………………………… 10

4. Product overview …………………………………………………………………………………………………….11 4.1 Product perspective ……………………………………………………………………………………………………… 11 4.2 Summary of capabilities……………………………………………………………………………………………….. 11 4.3 Assumptions and dependencies …………………………………………………………………………………….. 12 4.4 Cost and pricing ………………………………………………………………………………………………………….. 12 4.5 Licensing and installation …………………………………………………………………………………………….. 12

5. Product features ………………………………………………………………………………………………………13 5.1 Feature 1…………………………………………………………………………………………………………………….. 13 5.2 Feature 2…………………………………………………………………………………………………………………….. 13

6. Constraints………………………………………………………………………………………………………………14 7. Quality ranges …………………………………………………………………………………………………………15 8. Precedence and priority …………………………………………………………………………………………..16 9: Other product requirements………………………………………………………………………………………17

9.2 System requirements ………………………………………………………………………………………………………… 17 9.3 Performance requirements ………………………………………………………………………………………………… 17

10 Documentation Requirements …………………………………………………………………………………..19 10.1 Release notes, read me file ………………………………………………………………………………………………. 19 10.2 Online help ……………………………………………………………………………………………………………………. 19 10.3 Installation guides: …………………………………………………………………………………………………………. 19 10.4 Labeling and packaging ………………………………………………………………………………………………….. 20

11 Appendix 1 – Feature attributes…………………………………………………………………………………21 11.1 Status ……………………………………………………………………………………………………………………………. 21 11.2 Benefit ………………………………………………………………………………………………………………………….. 21 11.3 Effort ……………………………………………………………………………………………………………………………. 22 11.4 Risk ……………………………………………………………………………………………………………………………… 22 11.5 Stability ………………………………………………………………………………………………………………………… 23 11.6 Target release ………………………………………………………………………………………………………………… 23 11.7 Assigned to ……………………………………………………………………………………………………………………. 23 11.8 Reason ………………………………………………………………………………………………………………………….. 24

Vision Document <Project> Page iii

Revision History

Name Date Reason for Changes Version

Your name MM DD, 202x

Include reason

Vision Document <Project> Page 4

1. Introduction <Describe the contents of this section. Remove these directions after completing the section.>

1.1 Purpose

< State the purpose of this vision document. Remove these directions after completing the section.>

1.2 Scope

< Briefly describe the scope of this vision document, including which programs, projects, applications, and business processes the document is associated with. Include anything else that this document affects or influences. Remove these directions after completing the section.>

1.3 Definitions, acronyms and abbreviations

< Define all terms, acronyms, and abbreviations that are required to interpret the vision correctly. This information might be provided by reference to the project glossary, which can be developed online in the repository. Remove these directions after completing the section.>

1.4 References

< List all documents that the vision document refers to. Identify each document by title, report number (if applicable), date, and publishing organization. Specify the sources from which readers can obtain the references; the sources are ideally available in RM or in other online repositories. This information might be provided by reference to an appendix or to another document. Remove these directions after completing the section.>

Vision Document <Project> Page 5

1.5 Overview

<Discuss the contents of this vision document. Remove these directions after completing the section.>

Vision Document <Project> Page 6

2

2. Positioning

2.1 Business Opportunity

<Discuss the business opportunity that is addressed by the project. Remove these directions after completing the section.>

2.2 Problem Statement

Summarize the problem that this project solves. Use the following statements as a model, providing project details to replace the parenthetical elements: The problem of (describe the problem) affects (the stakeholders affected by the problem). The impact of the problem is (what is the impact of the problem). A successful solution would include (list some key benefits of a successful solution). Remove these directions after completing the section.>

2.3 Product Position Statement

< Provide an overall statement that summarizes at the highest level the unique position the product intends to take in the marketplace. Use the following statements as a model, providing project details to replace the parenthetical elements: For the (target customer), who (statement of the need or opportunity). The (product name) is a (product category) that (statement of key benefit, that is, the compelling reason to buy). Unlike (primary competitive alternative), our product (statement of primary differentiation). A product position statement communicates the intent of the application and the importance of the project to all concerned stakeholders. Remove these directions after completing the section.>

Vision Document <Project> Page 7

3. Stakeholder and User Descriptions <To provide products and services that meet stakeholders' and users' needs, you must identify and involve all stakeholders as part of the requirements- definition process. You must also identify the system users and ensure that the stakeholder community represents them adequately. This section provides a profile of the stakeholders and users who are involved in the project. This section also identifies the key problems that stakeholders and users consider that the proposed solution must address. This section does not describe specific requests or requirements; a separate stakeholder requests artifact captures these items. The key-problem description provides the background and justification for requirements. Remove these directions after completing the section.>

3.1 Market demographics

<Summarize the key market demographics that motivate your product decisions. Describe and position target market segments. Estimate the market size and growth by using the number of potential users. Alternatively, estimate the amount of money that your customers spend trying to meet the needs that your product or enhancement would fulfill. Review major industry trends and technologies. Answer these strategic questions:

• What is the reputation of your organization in these markets? • What would you like the reputation to be? • How does this product or service support your goals?

Remove these directions after completing the section.>

3.2 Stakeholder summary

<List all the identified stakeholders. For each stakeholder type, provide this information:

• Name: Name the stakeholder type. • Represents: Briefly describe which individuals, teams, or organizations

this stakeholder type represents. • Role: Briefly describe the role this stakeholder type plays in the

development effort. Remove these directions after completing the section.>

Vision Document <Project> Page 8

3.3 User summary

<List all the identified user types. For each user type, provide this information:

• Name: Name the user type • Description: Briefly describe the relationship of this type of user to the

system under development. • Stakeholder: List which stakeholder type represents this user type.

Remove these directions after completing the section.>

3.4 User environment

<Detail the working environment of the target user. Here are some suggestions:

• How many people are involved in completing the task? Is this changing?

• How long is a task cycle? How much time do users spend in each activity? Is this changing?

• What unique environmental constraints affect the project? For example, do users require mobile devices, work outdoors, or work during flights?

• Which system platforms are in use today? Are there future platforms planned?

• What other applications are in use? Does your application need to integrate with them?

In this section, you might include extracts from the business model to outline the task and workers who are involved. Remove these directions after completing the section.>

3.5 Stakeholder profiles

<Describe each stakeholder in the project by completing the following table for each stakeholder. Remember: Stakeholder types can be users, strategy departments, legal or compliance departments, technical developers, operations teams, and others. A thorough profile covers the following topics for each stakeholder type:

• Representative: State who represents the stakeholder to the project (This information is optional if it is documented elsewhere.) Enter the representatives' names.

• Description: Briefly describe the stakeholder type. • Type: Qualify the expertise of the stakeholder, such as "guru,"

"business expert," , or "casual user." This designation can suggest technical background and degree of sophistication.

• Responsibilities: List the key responsibilities of the stakeholder on the system under development; list their interests as a stakeholder.

Vision Document <Project> Page 9

• Success criteria: State how the stakeholder defines success. How is the stakeholder rewarded?

• Involvement – Describe how the stakeholder is involved in the project. Where possible, relate the involvement to the process roles; for example, a stakeholder might be a requirements reviewer.

• Deliverables: Identify additional deliverables that the stakeholder requires. These items might be project deliverables or output from the system under development.

• Comments or issues: State problems that interfere with success and any other relevant information.

Remove these directions after completing the section.>

3.6 User profiles

<Describe each user of the system here by completing the following table for each user type. Remember user types can be experts and novices; for example, an expert might need a sophisticated, flexible tool with cross- platform support, while a novice might need a tool that is easy to use. A thorough profile covers these topics for each type of user:

• Representative: State who represents the user to the project. (This information is optional if it is documented elsewhere.) This representative often refers to the stakeholder who represents a set of users; for example, Stakeholder: Stakeholder1.

• Description: Briefly describe the user type. • Type: Qualify the expertise of the user, such as "guru" or "casual

user." This designation can suggest technical background and degree of sophistication.

• Responsibilities: List the key user responsibilities with respect to the system; for example, state who captures customer details, produces reports, and coordinates work, and so on.

• Success criteria: State how the user defines success. How is the user rewarded?

• Involvement: Describe how the user is involved in the project. Where possible, relate the involvement to process roles; for example, a stakeholder might be a requirements reviewer.

• Deliverables: Identify the deliverables that the user produces and for whom.

• Comments or issues: State problems that interfere with success and any other relevant information. Describe trends that make the user's job easier or harder.

Remove these directions after completing the section.>

Vision Document <Project> Page 10

3.7 Key stakeholder or user needs:

<List the key problems with existing solutions as the stakeholder perceives them. Clarify these issues for each problem:

1. What are the reasons for this problem? 2. How is the problem solved now? 3. What solutions does the stakeholder want?

You must understand the relative importance that the stakeholder places on solving each problem. Ranking and cumulative voting techniques help indicate the problems that must be solved versus issues that stakeholders would like to be addressed. Use this table to capture the stakeholder needs. Need Priority Concerns Current solution Proposed solution Table 1. Stakeholder needs Remove these directions after completing the section.>

3.8 Alternatives and competition

<Identify alternatives that the stakeholder perceives as available. These alternatives can include buying a competitor's product, building a homegrown solution or maintaining the status quo. List any known and available competitive choices. Include the major strengths and weaknesses of each competitor as the stakeholder perceives them. Remove these directions after completing the section.>

Vision Document <Project> Page 11

4. Product overview <This section provides a high-level view of the product capabilities, interfaces to other applications, and systems configurations. This section typically consists of three subsections:

• Product perspective • Product functions • Assumptions and dependencies

Remove these directions after completing the section.>

4.1 Product perspective

<Put the product in perspective with regards to other related products and the user's environment. If the product is independent and completely self- contained, state it here. If the product is a component of a larger system, relate how these systems interact and identify the relevant interfaces between the systems. One way to display the major components of the larger system, interconnections, and external interfaces is to use a business process or use-case diagram. Remove these directions after completing the section.>

4.2 Summary of capabilities

<Summarize the major benefits and features that the product will provide. For example, a customer support system might use this part to address problem documentation, routing, and status reporting without elaborating on detail that these functions require. Organize the functions so that the list is understandable to the customer or to anyone else who reads the document for the first time. A simple table that lists the key benefits and their supporting features might suffice, as in the following example. Customer benefit Supporting features New support staff can quickly learn how to use the product.

A knowledge base assists support personnel in quickly identifying known fixes and workarounds.

Customer satisfaction is improved because nothing falls through the cracks.

Problems are uniquely itemized, classified, and tracked throughout the resolution process. Automatic notification occurs for any aging issues.

Management can identify problem areas and gauge staff workload.

Trend and distribution reports enable a high-level review of problem status.

Vision Document <Project> Page 12

Customer benefit Supporting features Distributed support teams can work together to solve problems.

With a replication server, current database information can be shared throughout the enterprise.

Customers can help themselves, lowering support costs and improving response time.

A knowledge base can be made available over the Internet. The knowledge base includes hypertext search capabilities and a graphical query engine.

Table 2. Benefits and features example Remove these directions after completing the section.>

4.3 Assumptions and dependencies

<List each of factor that affects the features that the vision document includes. List assumptions that, if changed, will alter the vision document. For example, an assumption might state that a specific operating system will be available for the designated hardware for the software product. If the operating system is not available, the vision document will require change. Remove these directions after completing the section.>

4.4 Cost and pricing

<Record relevant cost and pricing impacts and constraints. For example, distribution costs (the number of CDs and CD mastering) or other cost-of- goods-sold constraints (manuals and packaging) might be material or irrelevant to project success, depending on the nature of the application. Remove these directions after completing the section.>

4.5 Licensing and installation

<Licensing and installation issues can also directly affect the development effort. For example, the need to support serializing, password security, or network licensing will create additional system requirements that must be considered in the development effort. Installation requirements might also affect coding or create the need for separate installation software. Remove these directions after completing the section.>

Vision Document <Project> Page 13

5. Product features <List and briefly describe the product features. Features are the high-level capabilities of the system that are required to deliver benefits to the users. Each feature is a requested service that typically requires a series of inputs to achieve a satisfactory result. For example, a feature of a problem-tracking system might be the ability to provide trending reports. As the use-case model takes shape, update the description to refer to the use cases. Because the vision document is reviewed by a wide variety of involved personnel, keep the level of detail general enough for everyone to understand. However, offer sufficient detail to provide the team with the information it needs to create a use-case model or other design documents. To manage application complexity, for a new system or an incremental change, list capabilities at such a high level that you include approximately 25-99 features. These features provide the basis for product definition, scope management, and project management. Each feature will be expanded into greater detail in the use-case model. Throughout this section, make each feature relevant to users, operators, or other external systems. Include a description of functions and usability issues that must be addressed. The following guidelines apply:

• Avoid design. Keep feature descriptions at a general level. Focus on required capabilities and why (not how) they should be implemented.

• Designate all features as requirements of a specific feature type for easy reference and tracking.

Remove these directions after completing the section.>

5.1 Feature 1.

5.2 Feature 2.

(add additional features as needed)

Vision Document <Project> Page 14

6. Constraints

<Note any design constraints, external constraints, such as operational or regulatory requirements, or other dependencies. Remove these directions after completing the section.>

Vision Document <Project> Page 15

7. Quality ranges

<Define the quality ranges for performance, robustness, fault tolerance, usability, and similar characteristics that the feature set does not describe. Remove these directions after completing the section.>

Vision Document <Project> Page 16

8. Precedence and priority

<Define the priority of the different system features. Remove these directions after completing the section.>

Vision Document <Project> Page 17

9: Other product requirements <At a high level, list applicable standards, hardware or platform requirements, performance requirements, and environmental requirements. 9.1 Applicable standards: List all standards that the product must comply with. The list can include these standards:

• Legal and regulatory standards (FDA, UCC) • Communications standards (TCP/IP, ISDN) • Platform compliance standards (Windows, UNIX, and so on) • Quality and safety standards (UL, ISO, CMM)

Remove these directions after completing the section.>

9.2 System requirements

<Define the system requirements for the application. These can include the supported host operating systems and network platforms, configurations, memory, peripheral devices, and companion software. Remove these directions after completing the section.>

9.3 Performance requirements

Detail performance requirements. Performance issues can include such items as user-load factors, bandwidth or communication capacity, throughput, accuracy, reliability, or response times under various load conditions. Remove these directions after completing the section.>

9.4 Environmental requirements <Detail environmental requirements as needed. For hardware-based systems, environmental issues can include temperature, shock, humidity, and radiation. For software applications, environmental factors can include

Vision Document <Project> Page 18

use conditions, user environment, resource availability, maintenance issues, error handling, and recovery. Remove these directions after completing the section.>

Vision Document <Project> Page 19

10 Documentation Requirements <This section describes the documentation that you must develop to support successful application deployment. Remove these directions after completing the section.>

10.1 Release notes, read me file

<Release notes or an abbreviated read me file can include a "What's new" section, a discussion of compatibility issues with earlier releases, and installation and upgrade alerts. The document can also contain or link to fixes in the release and any known problems and wo

Collepals.com Plagiarism Free Papers

Are you looking for custom essay writing service or even dissertation writing services? Just request for our write my paper service, and we'll match you with the best essay writer in your subject! With an exceptional team of professional academic experts in a wide range of subjects, we can guarantee you an unrivaled quality of custom-written papers.

Get ZERO PLAGIARISM, HUMAN WRITTEN ESSAYS

Why Hire Collepals.com writers to do your paper?

Quality- We are experienced and have access to ample research materials.

We write plagiarism Free Content

Confidential- We never share or sell your personal information to third parties.

Support-Chat with us today! We are always waiting to answer all your questions.