Docstoc

Vision

Document Sample
Vision Powered By Docstoc
					   <Company Name>




Vision
Document

HOPE System


iNiTech


November 2010
<Project Name>                                                          Version:    <1.0>
Vision                                                                  Date: <dd/mmm/yy>
<document identifier>




                                   Revision History
 Release No.      Date         Revision Description
 Rev. 0           10/01/2010   Manual Template and Checklist
 Rev. 1           10/10/2010   Initial Work
 Rev. 2           10/20/2010   Revision 1: To Reflect Prototype 1.0
 Rev. 3           11/1/2010    Revision 2: Change to Vision Documentation
 Rev. 4           11/8/2010    Revision 3: Change to new template.
 Rev. 5           11/10/2010   Integrated Cliff’s work.
 Rev. 6           11/10/2010   Integrated Tom’s work
 Rev. 7           11/11/2010   Current Document v3
 Rev. 8           11/28/2010   Minor revisions to statements
 Rev. 9           11/30/2010   Phase II revision




Confidential                          <Company Name>, 2011                                 Page 2
<Project Name>                                                                Version:    <1.0>
Vision                                                                        Date: <dd/mmm/yy>
<document identifier>




                                                        Authorization Memorandum


I have carefully assessed the User’s Manual for the (System Name). This document has been completed in
accordance with the requirements of the System Development Methodology.


MANAGEMENT CERTIFICATION - Please check the appropriate statement.


______ The document is accepted.


______ The document is accepted pending the changes noted.


______ The document is not accepted.


We fully accept the changes as needed improvements and authorize initiation of work to proceed. Based on our
authority and judgment, the continued operation of this system is authorized.

_______________________________                                               _____________________
NAME                                                                          DATE
Project Leader

_______________________________                                               _____________________
NAME                                                                          DATE
Operations Division Director

_______________________________                                               _____________________
NAME                                                                          DATE
Program Area/Sponsor Representative

_______________________________                                               _____________________
NAME                                                                          DATE
Program Area/Sponsor Director




Confidential                              <Company Name>, 2011                                          Page 3
<Project Name>                                                      Version:    <1.0>
Vision                                                              Date: <dd/mmm/yy>
<document identifier>


                                        Table of Contents
1.   Introduction                                                                               6
     1.1       Purpose                                                                          6
     1.2       Scope                                                                            6
     1.3       Definitions, Acronyms, and Abbreviations                                         6
     1.4       References                                                                       6
     1.5       Overview                                                                         6

2.   Positioning                                                                                7
     2.1       Business Opportunity                                                             7
     2.2       Problem Statement                                                                7
     2.3       Product Position Statement                                                       8

3.   Stakeholder and User Descriptions                                                          9
     3.1   Market Demographics                                                                   9
     3.2   Stakeholder Summary                                                                   9
     3.3   User Summary                                                                          9
     3.4   User Environment                                                                     10
     3.5   Stakeholder Profiles                                                                 10
         3.5.1 Stakeholders                                          Error! Bookmark not defined.8
     3.6   User Profiles                                                                        13
         3.6.1 Users                                                 Error! Bookmark not defined.9
     3.7   Key Stakeholder or User Needs                                                        14
     3.8   Alternatives and Competition                                                         16
         3.8.1 Competitors                                          Error! Bookmark not defined.10
         3.8.2 Competitors                                          Error! Bookmark not defined.10

4.   Product Overview                                                                          17
     4.1       Product Perspective                                                             17
     4.2       Summary of Capabilities                                                         17
     4.3       Assumptions and Dependencies                                                    18
     4.4       Cost and Pricing                                                                18
     4.5       Licensing and Installation                                                      18

5.   Product Features                                                                          18
     5.1       Ext. Features                                                                    18
     5.2       Int. Feature                                         Error! Bookmark not defined.10

6.   Constraints                                                                               19

7.   Quality Ranges                                                                            19

8.   Precedence and Priority                                                                   19

9.   Other Product Requirements                                                                19
     9.1       Applicable Standards                                                             19
     9.2       System Requirements                                  Error! Bookmark not defined.10
     9.3       Performance Requirements                             Error! Bookmark not defined.10
     9.4       Environmental Requirements                           Error! Bookmark not defined.10

Confidential                                <Company Name>, 2011                          Page 4
<Project Name>                                                          Version:    <1.0>
Vision                                                                  Date: <dd/mmm/yy>
<document identifier>

10.          Documentation Requirements                                                            19
      10.1       User Manual                                                                        19
      10.2       Online Help                                                                        19
      10.3       Installation Guides, Configuration, and Read Me File                               20
      10.4       Labeling and Packaging                                 Error! Bookmark not defined.10

A      Feature Attributes                                                                          20
      A.1      Status                                                   Error! Bookmark not defined.10
      A.2      Benefit                                                  Error! Bookmark not defined.10
      A.3      Effort                                                   Error! Bookmark not defined.10
      A.4      Risk                                                     Error! Bookmark not defined.10
      A.5      Stability                                                Error! Bookmark not defined.10
      A.6      Target Release                                           Error! Bookmark not defined.10
      A.7      Assigned To                                              Error! Bookmark not defined.10
      A.8      Reason                                                   Error! Bookmark not defined.10




Confidential                                 <Company Name>, 2011                             Page 5
<Project Name>                                                                    Version:    <1.0>
Vision                                                                            Date: <dd/mmm/yy>
<document identifier>


                                                    Vision
1.       Introduction
The purpose of this document is to collect, analyze, and define high-level needs and features of iNiTech’s System .
It focuses on the capabilities needed by the stakeholders and the target users, and why these needs exist. The details
of how iNiTech’s System fulfills these needs are detailed in the use-case and supplementary specifications


1.1 Purpose
The purpose of this document is to collect, analyze, and define high-level needs and features of the Meeting
Scheduling System. Focusing on the capabilities and needs of the stakeholders, and the target users, and why these
needs exist. The details of how the Meeting Scheduling System’s achieves these requirements are detailed in the use
case and supplementary detailed specifications. It also focuses on the capabilities of the stakeholders and the users
targeted.



1.2 Scope
This document will address the iNiTech currently experiences with management of software problem reports and
software changes and address the solution that system will provide. It will detail the project stakeholders and
describe the ways in which they will be affected by the implementation of the system. It will also document high-
level requirements for the system and the basic architecture that will be utilized.




1.3 Definitions, Acronyms, and Abbreviations
This subsection provides the definitions of all terms, acronyms, and abbreviations required to properly interpret the
Vision document. This information may be provided by reference to the project’s Glossary.


         App:     Application
         MS:      Microsoft
         MSDN:    Microsoft Developer Network
         Wiki:    Wikipedia
         WP7:     Windows 7 SmartPhone Platform



1.4 References
       http://msdn05.e-academy.com/utd_cs
       http://create.msdn.com/en-us/home/getting_started
       http://windowsteamblog.com/windows_phone
       http://www.microsoft.com/windowsphone/en-us/howto/wp7/default.aspx
       http://social.msdn.microsoft.com/Forums/en-US/windowsphone7series
       http://channel9.msdn.com/Learn/Courses/WP7TrainingKit/WP7GettingStarted
       http://en.wikipedia.org/wiki/WP7




Confidential                                 <Company Name>, 2011                                             Page 6
<Project Name>                                                                    Version:    <1.0>
Vision                                                                            Date: <dd/mmm/yy>
<document identifier>

1.5 Overview
        Planning Documents

              Software Development Plan (this document)
              Vision and Scope Document
              Software Requirements Specification
              User Interface Design and Prototype
              Software Architecture Document
              Systems Manual which outlines build procedures and other development-related processes.
              Example hand calculations for the complete analysis of one 3-span precast girder bridge.


        Software and Related Products

              Source Code
              Executable Code
              End User Documentation including Tutorial, User's Guide and Theoretical Manual
              Web-site for on-line resources, FAQ's, and latest product information




2.      Positioning


2.1 Business Opportunity

        An intelligent aid for impaired individuals:

                  A software system based on the Windows 7 SmartPhone Platform.
                  Graphical Scheduler system for notification
                  User Medical Referencing System



2.2 Problem Statement




Confidential                                 <Company Name>, 2011                                        Page 7
<Project Name>                                                                 Version:    <1.0>
Vision                                                                         Date: <dd/mmm/yy>
<document identifier>

          The problem of                     Scheduling meetings with minimal interactions and resolution
                                             of conflicts regarding date and time


          affects                            Employees of iNiTech


          the impact of which is             Delay and ultimately improper resource utilization


          a successful solution would be     An accessible, cost-effective meeting scheduler which can be
                                             used by the employees to initiate and schedule meetings. The
                                             product would also address issues related to conflict in dates
                                             and provide an efficient method to solve any such problems




2.3 Product Position Statement




          For                              Impaired Individuals


          Who                              Need additional memory aid


          The (product name)                iNiTech’s Hope System


          That                             Provides a intelligent aid system to keep track of medical needs
                                           and scheduler and location system.


          Unlike                           Other meeting schedulers in the market which do not provide
                                           conflict resolution and are not web-based.


          Our product                      The market which needs a distributed application and
                                           provides security features needed by such a system. It is suitable
                                           for both large and small organizations because it addresses
                                           features ranging from cost-effectiveness to scalability




Confidential                               <Company Name>, 2011                                              Page 8
<Project Name>                                                                     Version:    <1.0>
Vision                                                                             Date: <dd/mmm/yy>
<document identifier>

3.       Stakeholder and User Descriptions
To effectively provide products and services that meet your stakeholders’ and users' real needs, it is necessary to
identify and involve all of the stakeholders as part of the Requirements Modeling process. You must also identify the
users of the system and ensure that the stakeholder community adequately represents them. This section provides a
profile of the stakeholders and users involved in the project, and the key problems that they perceive to be addressed
by the proposed solution. It does not describe their specific requests or requirements as these are captured in a
separate stakeholder requests artifact. Instead, it provides the background and justification for why the
requirements are needed.




3.1 Market Demographics

      The target market of the system is any individual needing assistant in medical medication tracking with
scheduling and reminding services. The system also provides a real-time assessment on location aids and needs. The
primary focus is the care providers for the intended person using the phone.




3.2 Stakeholder Summary
There are a number of stakeholders with an interest in the development and not all of them are end users. Present a
summary list of these non-user stakeholders. (The users are summarized in section 3.3.)


          Name                     Description                      Responsibilities
          Project Manager          The main administrator of the    Creates projects, assigns roles within the
                                   system, the project manager      project, assigns tasks and due dates, views the
                                   will also receive the most       timeline, and generates reports from the
                                   benefit in terms of time saved   timeline.
                                   from implementing the RMT
                                   system.
          Systems Analyst          The SA does a lot of visual      Inputs any or all of the following: use cases,
                                   modeling. He or she usually      system designs
                                   creates the first level of the
                                   use case realization.
          Developer                The developer is involved in     View system diagrams, upload source code.
                                   some system design and a lot
                                   of coding.



3.3 User Summary
Present a summary list of all identified users.


          Name                     Description                      Responsibilities




Confidential                                 <Company Name>, 2011                                              Page 9
<Project Name>                                                                   Version:    <1.0>
Vision                                                                           Date: <dd/mmm/yy>
<document identifier>

          Phone User             The person who uses the          Uses the phone
                                 phone who is impaired


          Care Provider          The individuals who takes        Enters the necessary information and/or data
          and/or Family          care of or is responsible for    for the application to function.
          member                 the welfare of the impaired
                                 individual.




3.4 User Environment
Detail the working environment of the target user:


        A software system based on the Windows 7 SmartPhone Platform.
        Graphical Scheduler system for notification
        User Medical Referencing System
        GPS / Electronic Compass Location
        System name or title: HOPE
        System code: WP7
        System category:
        Major application: performs clearly defined functions for which there is a readily identifiable security
        consideration and need
        General support system: provides general ADP or network support for a variety of users and applications

This is where extracts from the Business Model could be included to outline the task and roles involved and so on.




3.5 Stakeholder Profiles
Each stakeholder in the system here by filling in the following table for each stakeholder. Remember that
stakeholder types can be as divergent as users, departments, and technical developers. A thorough profile would
cover the following topics for each type of stakeholder.


3.5.1   Project Manager
         Representative         Non Disclosure


         Description            The main administrator of the system, the project manager will also receive the
                                most benefit in terms of time saved from implementing the RMT system.


         Type                   Business


         Responsibilities       Creates projects, assigns roles within the project, assigns tasks and due dates,

Confidential                                <Company Name>, 2011                                           Page 10
<Project Name>                                                               Version:    <1.0>
Vision                                                                       Date: <dd/mmm/yy>
<document identifier>

                            views the timeline, and generates reports from the timeline.


        Success Criteria    Defined separately


        Involvement         Business Modeling and Project Management.


        Deliverables        Project deliverables or outputs from the system under development


        Comments / Issues   Project Driven




3.5.2   Business Analyst
        Representative      Non Disclosure


        Description         The BA will input the requirements which are the primary driving force of the
                            system.


        Type                Business


        Responsibilities    Inputs feature lists, business requirements, system requirements, other
                            requirements, and business rules.


        Success Criteria    Defined separately


        Involvement         Requirements Analysis and Design.


        Deliverables        Requirement use cases.


        Comments / Issues   Project deliverables or outputs from the system under development




3.5.3   System Analyst
        Representative      Non Disclosure


        Description         The SA does a lot of visual modeling. He or she usually creates the first level of the



Confidential                           <Company Name>, 2011                                             Page 11
<Project Name>                                                               Version:    <1.0>
Vision                                                                       Date: <dd/mmm/yy>
<document identifier>

                            use case realization.


        Type                Business and casual technical skills


        Responsibilities    Develops use cases and creates system designs.


        Success Criteria    Defined separately


        Involvement         Requirements analysis, upper level implementation design.


        Deliverables        Requirement use cases


        Comments / Issues   Project deliverables or outputs from the system under development




3.5.4   Developer
        Representative      Non Disclosure


        Description         The developer is involved in some system design and a lot of coding.


        Type                Technology Expert


        Responsibilities    View system diagrams, upload source code.


        Success Criteria    Defined separately


        Involvement         Implementation design and testing


        Deliverables        Software Specification


        Comments / Issues   Project deliverables or outputs from the system under development




Confidential                           <Company Name>, 2011                                       Page 12
<Project Name>                                                                    Version:    <1.0>
Vision                                                                            Date: <dd/mmm/yy>
<document identifier>



3.5.5   QA Tester
         Representative         Non Disclosure


         Description            The QA tester tests releases of the project.


         Type                   Experienced user / Technolog y Expert


         Responsibilities       View artifacts, fill out test case forms, and submit test case forms.


         Success Criteria       Defined separately


         Involvement            Testing


         Deliverables           Software Release Candidates


         Comments / Issues      Project deliverables or outputs from the system under development




3.6 User Profiles
Describe each unique user of the system here by filling in the following table for each user type. Remember user
types can be as divergent as gurus and novices. For example, a guru might need a sophisticated, flexible tool with
cross-platform support, while a novice might need a tool that is easy to use and user-friendly. A thorough profile
needs to cover the following topics for each type of user.


3.6.1   Impaired Phone User

         Representative


         Description            The person who uses the phone who is impaired


         Type                   Inexperienced user


         Responsibilities       Provides feedback to requirements.




Confidential                                <Company Name>, 2011                                          Page 13
<Project Name>                                                                    Version:    <1.0>
Vision                                                                            Date: <dd/mmm/yy>
<document identifier>

         Success Criteria        User desires a simple system, reminders that are valuable to their life.


         Involvement             Requirements, Deployment


         Deliverables            System Specification and the finished system


         Comments / Issues       Problems that interfere with success and any other relevant information go here.
                                 These would include trends that make the user’s job easier or harder.




3.6.2    Care Provider

         Representative


         Description             The individuals who takes care of or is responsible for the welfare of the impaired
                                 individual.


         Type                    Casual or experienced user


         Responsibilities        Provides feedback to requirements, configures system.


         Success Criteria        Provider desires a simple and quick method to configure the system.


         Involvement             Requirements, Deployment


         Deliverables            System Specification and the finished system


         Comments / Issues       Problems that interfere with success and any other relevant information go here.
                                 These would include trends that make the user’s job easier or harder.




3.7 Key Stakeholder or User Needs
Key problems with existing solutions as perceived by the stakeholder or user. Clarify the following issues for each
problem:




Confidential                                <Company Name>, 2011                                           Page 14
<Project Name>                                                               Version:    <1.0>
Vision                                                                       Date: <dd/mmm/yy>
<document identifier>

See additional functional and non-functional requirements in the SRS document.




Confidential                              <Company Name>, 2011                                  Page 15
<Project Name>                                                                 Version:    <1.0>
Vision                                                                         Date: <dd/mmm/yy>
<document identifier>




3.8 Alternatives and Competition
Alternatives the stakeholder perceives as available. These can include buying a competitor’s product, building a
homegrown solution or simply maintaining the status quo. List any known competitive choices that exist or may
become available. Include the major strengths and weaknesses of each competitor as perceived by the stakeholder
or end user.


3.8.1   Google Applications: Google Groups, Calendar, ect…
3.8.2   Microsoft Office Applications: Project, SharePoint, ect…




Confidential                               <Company Name>, 2011                                         Page 16
<Project Name>                                                                    Version:    <1.0>
Vision                                                                            Date: <dd/mmm/yy>
<document identifier>




4.       Product Overview
This section provides a high level view of the product capabilities, interfaces to other applications, and system
configurations. This section usually consists of three subsections, as follows:




4.1 Product Perspective
 SharePoint provides functionality enabling tight collaboration between and within research teams via document
sharing and portal development. When used in a CTMS environment combined with investigator portals,
biopharmaceutical companies can experience quantum leaps in operational productivity.


4.2 Summary of Capabilities
The list is understandable to the customer or to anyone else reading the document for the first time. A simple table
listing the key benefits and their supporting features might suffice.




Confidential                                 <Company Name>, 2011                                            Page 17
<Project Name>                                                                   Version:    <1.0>
Vision                                                                           Date: <dd/mmm/yy>
<document identifier>

         Customer Benefit                              Supporting Features
         Accessibility                                 System is web based and can be accessed from any web-
                                                       capable device.
         Ease of use.                                  System layout is designed to be intuitive so that users can
                                                       easily navigate and use its tools.
         Better planned meeting times and              Users can input their preferences for a meeting, and
         locations.                                    conflict resolution is available.
         Accurately models site location.              Administrators enter in data such as available resources
                                                       and rooms to make sure the work building is properly
                                                       represented.
         Information about meetings is secure.         Only people who are a part of a meeting can see status
                                                       updates on that meeting.



4.3 Assumptions and Dependencies

        Content is managed and must be approved
        An editorial team sets the structure, standards, and schedule for content and approves content before it is
        published.

        Content deployment is not required
        This solution has a combined authoring and publishing environment and does not need content deployment.

        Collaboration sites are not included
        Collaboration sites have a different content structure and permission model. Search is used to index and
        expose content from related collaboration sites.




4.4 Cost and Pricing
     TBD


4.5 Licensing and Installation
     TBD


5.      Product Features
To effectively manage application complexity, we recommend for any new system, or an increment to an existing
system, capabilities are abstracted to a high enough level so 25-99 features result. These features provide the
fundamental basis for product definition, scope management, and project management. Each feature will be
expanded in greater detail in the use-case model.


5.1 WebSites
SharePoint 2010 Sites provides a single infrastructure for all your business Web sites. Share documents with
colleagues, manage projects with partners, and publish information to customers.


Confidential                                <Company Name>, 2011                                            Page 18
<Project Name>                                                                  Version:    <1.0>
Vision                                                                          Date: <dd/mmm/yy>
<document identifier>



5.2 Composites
SharePoint 2010 Composites offers tools and components for creating do-it-yourself business solutions. Build no-
code solutions to rapidly respond to business needs.


5.3 Communities
SharePoint 2010 Communities delivers great collaboration tools—and a single platform to manage them. Make it
easy for people to share ideas and work together the way they want.


5.4 Content Management
SharePoint 2010 Content makes content management easy. Set up compliance measures ”behind the scenes”—with
features like document types, retention polices, and automatic content sorting—and then let people work naturally in
Microsoft Office.




6.      Constraints
      Note: See MSDN for constraints


7.      Quality Ranges
      See functional and non-functional requirements in the SRS document.


8.      Precedence and Priority
      See functional and non-functional requirements in the SRS document.


9.      Other Product Requirements
      See functional and non-functional requirements in the SRS document.




10.     Documentation Requirements
This section describes the documentation that must be developed to support successful application deployment.


10.1 User Manual
     A iNiTech User manual is available.


10.2 Online Help
     A iNiTech online help is available.




Confidential                                <Company Name>, 2011                                          Page 19
<Project Name>                                                                    Version:    <1.0>
Vision                                                                            Date: <dd/mmm/yy>
<document identifier>

10.3 Installation Guides, Configuration, and Read Me File
     A iNiTech Technical manual is available.


A        Feature Attributes
Features are given attributes that can be used to evaluate, track, prioritize, and manage the product items proposed
for implementation. All requirement types and attributes need to be outlined in the Requirements Management Plan,
however, you may wish to list and briefly describe the attributes for features that have been chosen. The following
subsections represent a set of suggested feature attributes.


       Feature                                                     Description
Centralize                 Forefront Protection 2010 for SharePoint includes a built-in console that allows
management                 administrators to configure settings, create filter rules, schedule updates, monitor health
                           status, and manage incidents and quarantine.

View collaboration         Forefront Protection 2010 for SharePoint includes a dashboard view into real-time
security dashboard         detection statistics and the health of your collaboration security environment.


Automate download          Through its Rapid Update Process, Microsoft monitors all scan-engine vendor Web sites
and distribution of        for updates. It downloads and validates new engine versions and signatures as they
signature updates          become available, and then posts them online for Forefront Protection 2010 for
                           SharePoint to download and install automatically. Once properly configured, no
                           administrator involvement is needed to keep all engines and signatures current.

Extend manageability       The PowerShell interface in Forefront Protection 2010 for SharePoint gives
                           administrators the flexibility to create new scripts to manage and configure the product.

Monitor collaboration      A management pack for Microsoft Systems Center Operations Manager enables the IT
security health            administrator to monitor the health of Forefront Protection 2010 for SharePoint as part
                           of corporate operational management practices.




Confidential                                <Company Name>, 2011                                            Page 20

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:3
posted:12/4/2011
language:English
pages:20
liamei12345 liamei12345 http://
About