note: this template is shareware downloaded from www.processimpact.com. all shareware payments are donated to the norm kerth benefit fund to

NOTE: This template is shareware downloaded from www.processimpact.com.
All shareware payments are donated to the Norm Kerth Benefit Fund to
help a consultant who is disabled with a brain injury. Please visit
http://www.processimpact.com/norm_kerth.html to make a shareware
payment ($10 suggested). Thank you!
eLearning versions of several popular Process Impact training seminars
are available at www.processimpact.com/elearning.shtml, including “In
Search of Excellent Requirements,” “Exploring User Requirements with
Use Cases,” and “Writing High-Quality Requirements.” Single-user and
corporate-wide site licenses are both available.
Vision and Scope Document
for

Version 1.0 approved
Prepared by


Table of Contents
1. Business Requirements 1
2. Vision of the Solution 2
3. Scope and Limitations 2
4. Business Context 3
Revision History
Name
Date
Reason For Changes
Version
1.Business Requirements
=======================
all detailed requirements development. You may gather business
requirements from the customer or development organization’s senior
management, an executive sponsor, a project visionary, product
management, the marketing department, or other individuals who have a
clear sense of why the project is being undertaken and the ultimate
value it will provide, both to the business and to customers.>
1.1.Background
--------------
general description of the history or situation that leads to the
recognition that this product should be built.>
1.2.Business Opportunity
------------------------
that is being solved. Describe the market in which a commercial
product will be competing or the environment in which an information
system will be used. This may include a brief comparative evaluation
of existing products and potential solutions, indicating why the
proposed product is attractive. Identify the problems that cannot
currently be solved without the product, and how the product fits in
with market trends or corporate strategic directions.>
1.3.Business Objectives and Success Criteria
--------------------------------------------
that is quantitative and measurable. The value provided to customers
is described in section 1.4, so this section should focus on the value
provided to the business. This could include estimates of revenue or
cost savings, return on investment analysis, or target release dates.
Determine how success will be defined and measured on this project,
and describe the factors that are likely to have the greatest impact
on achieving that success. Include things within the direct control of
the organization, as well as external factors. Establish measurable
criteria to assess whether the business objectives have been met.>
1.4.Customer or Market Needs
----------------------------
needs that are not yet met by the marketplace or by existing systems.
You may wish to describe problems customers currently encounter that
the new product will (or will not) address and how the product would
be used by customers. Identify the customer hardware and software
environment in which the product must operate. Define at a high level
any known critical interface or performance requirements. Avoid
including any design or implementation details. Present the
requirements in a numbered list so that more detailed user or
functional requirements can be traced to them.>
1.5.Business Risks
------------------
product, such as marketplace competition, timing issues, user
acceptance, implementation issues, or possible negative impacts on the
business. Estimate the severity of the risks and identify any risk
mitigation actions that could be taken.>
2.Vision of the Solution
========================
built to address the business objectives. This vision will provide the
context for making decisions throughout the course of the product
development life cycle. The vision should not include detailed
functional requirements or project planning information.>
2.1.Vision Statement
--------------------
intent of the new product and describes what the world will be like
when it includes the product. The vision statement should reflect a
balanced view that will satisfy the needs of diverse customers as well
as those of the developing organization. It may be somewhat
idealistic, but it should be grounded in the realities of existing or
anticipated customer markets, enterprise architectures, organizational
strategic directions, and cost and resource limitations.>
2.2.Major Features
------------------
emphasizing those features that distinguish it from previous or
competing products. Specific user requirements and functional
requirements may be traced back to these features.>
2.3.Assumptions and Dependencies
--------------------------------
writing this vision and scope document. Note any major dependencies
the project must rely upon for success, such as specific technologies,
third-party vendors, development partners, or other business
relationships.>
3.Scope and Limitations
=======================
solution. It’s also important to define what will not be included in
the product. Clarifying the scope and limitations helps to establish
realistic expectations of the many stakeholders. It also provides a
reference frame against which proposed features and requirements
changes can be evaluated. Proposed requirements that are out of scope
for the envisioned product must be rejected, unless they are so
beneficial that the scope should be enlarged to accommodate them (with
accompanying changes in budget, schedule, and/or resources).>
3.1.Scope of Initial Release
----------------------------
initial release of the product. Consider the benefits the product is
intended to bring to the various customer communities, and generally
describe the product features and quality characteristics that will
enable it to provide those benefits. Avoid the temptation to include
every possible feature that any potential customer category might
conceivably want some day. Focus on those features and product
characteristics that will provide the most value, at the most
acceptable development cost, to the broadest community.>
3.2.Scope of Subsequent Releases
--------------------------------
indicate which major features will be deferred to later releases.>
3.3.Limitations and Exclusions
------------------------------
might anticipate, but which are not planned to be included in the new
product.>
4.Business Context
==================
project, including profiles of major customer categories, assumptions
that went into the project concept, and the management priorities for
the project.>
4.1.Stakeholder Profiles
------------------------
actively involved in a project, are affected by its outcome, or can
influence its outcome. The stakeholder profiles identify the customers
for this product and other stakeholders, and states their major
interests in the product. Characterize business-level customers,
target market segments, and different user classes, to reduce the
likelihood of unexpected requirements surfacing later that cannot be
accommodated because of schedule or scope constraints. For each
stakeholder category, the profile includes the major value or benefits
they will receive from the product, their likely attitudes toward the
product, major features and characteristics of interest, and any known
constraints that must be accommodated. Examples of stakeholder value
include:
*
improved productivity
*
reduced rework
*
cost savings
*
streamlined business processes
*
automation of previously manual tasks
*
ability to perform entirely new tasks or functions
*
conformance to current standards or regulations
*
improved usability or reduced frustration level compared to
current applications
Example:>
Stakeholder
Major Value
Attitudes
Major Interests
Constraints
executives
increased revenue
see product as avenue to 25% increase in market share
richer feature set than competitors; time to market
maximum budget = $1.4M
editors
fewer errors in work
highly receptive, but expect high usability
automatic error correction; ease of use; high reliability
must run on low-end workstations
legal aides
quick access to data
resistant unless product is keystroke-compatible with current system
ability to handle much larger database than current system; easy to
learn
no budget for retraining
4.2.Project Priorities
----------------------
and budget. The table below may be helpful in identifying the
parameters around the project’s key drivers (top priority objectives),
constraints to work within, and dimensions that can be balanced
against each other to achieve the drivers within the known
constraints. For more information, see chapter 2 of Creating a
Software Engineering Culture by Karl E. Wiegers (Dorset House, 1996).
Examples:>
Dimension
Driver
(state objective)
Constraint
(state limits)
Degree of Freedom
(state allowable range)
Schedule
release 1.0 to be available by 10/1, release 1.1 by 12/1
Features
70-80% of high priority features must be included in release 1.0
Quality
90-95% of user acceptance tests must pass for release 1.0, 95-98% for
release 1.1
Staff
maximum team size is 6 developers + 4 testers
Cost
budget overrun up to 15% acceptable without executive review
4.3.Operating Environment
-------------------------
the major availability, reliability, performance, and integrity
requirements. This information will significantly influence the
definition of the system’s architecture. Consider questions such as:
*
Are the users widely distributed geographically or located close
to each other? How many time zones are they in?
*
When do the users in various locations need to access the system?
*
Where is the data generated and used? How far apart are these
locations? Does the data from multiple locations need to be
combined?
*
Are specific maximum response times known for accessing data that
might be stored remotely?
*
Can the users tolerate service interruptions or is continuous
access to the system critical for the operation of their business?
*
What access security controls and data protection requirements are
needed?>

  • INSTYTUT MIKROELEKTRONIKI I OPTOELEKTRONIKI WYDZIAŁ ELEKTRONIKI I TECHNIK INFORMACYJNYCH
  • ŽÁDOST ČÍSLO   ŽÁDOST O POSKYTNUTÍ NADAČNÍHO PŘÍSPĚVKU
  • 65625 CHAPTER 1 PAGE 12 65 PUBLIC UTILITY COMMISSION
  • TEXAS DEPARTMENT OF STATE HEALTH SERVICES SCHOOL HEALTH PROGRAM
  • A VERWALTUNGSGEMEINSCHAFT SCHÖNBERG –PASSAMT – 94513 SCHÖNBERG USWEISPASSINHABERIN NAME
  • QUADERN DE LA UNITAT DE PRODUCCIÓ RAMADERA AVÍCOLA CONTROL
  • W ESTERN AUSTRALIA ROYAL AGRICULTURAL SOCIETY ACT 1926 ROYAL
  • PISNI IZPIT IZ IM 14JUNIJ2005 1 SKOZI MEŠALNO CELICO
  • KONSEKWENJCA LOGICZNA FORMUŁ DEFINICJA FORMUŁĘ NAZYWAMY KONSEKWENCJĄ LOGICZNĄ FORMUŁ
  • „ZELENA BRAZDA“ – NATJEČAJ NAMIJENJEN POTICANJU RAZVOJA POSEBNIH OBLIKA
  • TENTAMEN ATT RÄKNA VID SISTA FÖRELÄSNINGEN UPPGIFT 1 DNARNA
  • N° 14 PERFIL PACIENTES CON HEMOFILIA A SERVICIO DE
  • ÖZEL OLIMPOS HASTANESININ ÜYELERINIZE UYGULADIĞI FIYATLAR AŞAĞIDA BILGILERINIZE SUNULMUŞ
  • FILED 91902 CERTIFIED FOR PUBLICATION IN THE COURT OF
  • SEVERE WEATHER PROCEDURE AIM TO MAINTAIN A SAFE SITE
  • INSTRUCTIVO PARA TRAMITAR VISA DE INGRESO A CHINA I
  • 20122013 ÖĞRETİM YILI GÜZ YARIYILI YURT İÇİ YATAY GEÇİŞ
  • ORDENADOR O COMPUTADORA DISPOSITIVO ELECTRÓNICO CAPAZ DE RECIBIR UN
  • DS 533 FALL 2003 EXAM 2 NAME
  • RAVENSWOOD SURGERY PPG MEETING – 25 MAY 2017 ATTENDEES
  • !DOCTYPE HTML HTML LANGEN HEAD META CHARSETISO88591 TITLEST THOMAS
  • POWERPLUSWATERMARKOBJECT357831064 GRADE 8 MODEL SCIENCE UNIT 3 STABILITY AND
  • COUNTING NUMBERS ENGLISH SAMOA TUVALU TONGA ONE TASI
  • NOTE ASSIGNMENT NOT ACCEPTED ON THIS CLAIM PLEASE DO
  • VŠĮ TAUTINIŲ BENDRIJŲ NAMAI 2010 M VIEŠŲJŲ PIRKIMŲ PLANAS
  • USUALLY AND USED TO DOS EXPLICACIONES CON AUDIO HTTPWWWCURSOINGLESCOMGRAMATICAINGLESAUSEDTOPHP
  • AJUNTAMENT DE SANT FELIU DE GUÍXOLS EXPNÚM 16222009000002 DECRET
  • 12 SUNKEL GUILLERMO UNA MIRADA OTRA LA CULTURA DESDE
  • THE ORGAN DONATION CRISIS DEE DEE CHEN LILIANA KIM
  • F RESH NORTH QUEENSLAND MANGOES DIRECT FROM THE FARM