Statement of Work by bdy52T3r

VIEWS: 14 PAGES: 15

									   Statement of Work




             for

.NET Phase III- Survey Tool




         Between: Montana Department of Commerce/
         Montana Office of Tourism

            and:              [Contractor name]


         Prepared by: Corrie Hahn

         Effective Date: _________________________

         Under Contract #: __SPB 06-1263B___________

         Under Contract Name: __Master Contract for IT
         Services__

                              ______________________
Table of Contents
1.0 Introduction.................................................................................................................... 3
   1.1     .NET Phase III- Survey Tool ............................................................................................. 3
   1.2     Background ..................................................................................................................... 3
   1.3     Objectives........................................................................................................................ 3
   1.4 Reference to other applicable documents ........................................................................... 3
2.0 Staffing Roles and Responsibilities .................................................................................. 3
   2.1 Staffing .................................................................................................................................. 3
   2.2 Roles and Responsibilities Matrix ......................................................................................... 4
2.2.1 Contractor Staff, Roles and Responsibilities (Please identify your project team and
provide resumes as appendices.) ........................................................................................... 4
2.2.2 Agency Staff, Roles and Responsibilities MTOT will prepare a Project Charter outlining
all project roles and responsibilities. ...................................................................................... 4
3.0 Key Assumptions- ........................................................................................................... 5
3.0.1 Software and Coding- Integrated third party components are acceptable to the State. All
custom coding must adhere to the programming assumptions below. It is expected the
contractor must have documented programming skills in the following areas: ....................... 5
4.0 Risks ............................................................................................................................... 6
5.0 Scope of Work ................................................................................................................ 6
   5.2 Inclusions .............................................................................................................................. 6
   5.3 Exclusions .............................................................................................................................. 7
   5.4 Deliverables........................................................................................................................... 7
6.0 Work Approach.............................................................................................................. 12
7.0 Completion Criteria and Final Acceptance Criteria .......................................................... 13
   7.1 Completion Criteria ............................................................................................................. 13
8.0 Schedule—Vendor to complete ..................................................................................... 13
9.0 Project Management .................................................................................................... 13
10.0 State Policies Standards and Computing Environment .................................................. 13
11.0 Timeline and Period of Performance ........................................................................... 13
12.0 Compensation and Payment Schedule ......................................................................... 13
14.0 Appendices .................................................................................................................. 14
                                          Statement of Work

1.0 Introduction

1.1 .NET Phase III- Survey Tool

This work is being performed under the Master Contract for IT Services. The Montana Office of
Tourism, also referred to as MTOT, plans to convert our current survey tool to .NET. The application
will be a secure Web based (thin client) application. It will also allow our businesses and property
managers to update portions of their record on visitmt.com. The data will reside in our Oracle
database. That data is used to build the dynamic pages of our Web applications.

This Statement of Work (SOW) is made and entered by and between Montana Department of
Commerce/Montana Office of Tourism and [Contractor]. This SOW incorporates by reference the
terms and conditions of Contract Number SPB06-1263B in effect between the State and [Contractor].
In case of any conflict between this SOW and the Contract, the Contract shall prevail. The Agency and
Contractor agree as follows:

1.2 Background

The current Montana site, service and event survey system was developed in 1999 and then rewritten
in 2007 to keep the application functional while our entire Web infrastructure was converted to .NET.
That conversion is now complete and it is time to rewrite our survey tool in .NET. The new system will
provide similar functionality as the current system. That is gathering customer information to be stored
in the Oracle database (This database is commonly referred to as “Tourism”.) that supports our
consumer Web sites, mobile sites and XML/JSON feeds. However, we will be identifying some
enhancements to the system. Those enhancements center on creating a public/customer interface to
allow record holders the ability to update their own records. The tourism database has approximately
10,000 records of tourism related sites, services and events.

1.3 Objectives

1.3.1 Convert existing surveys to .NET
1.3.2 Add functionality to allow customers to edit fields remotely
1.3.3 Give the MTOT an administrative function to allow or restrict access to survey fields

1.4 Reference to other applicable documents
TBD- List any pertinent documents or supporting materials pertaining to this SOW

2.0 Staffing Roles and Responsibilities

2.1 Staffing

Project Manager – Contractor


MTOT .NET Phase III- Survey Tool                                              Page 3 of 15
Name:
Address:
City:
State & Zip:
Phone:
Cell:
Fax:
Email:

Project Manager – Agency
Name: Corrie Hahn
Address: 301 S Park Ave
City: Helena
State & Zip: MT 59620
Phone: 406-841-2884
Cell: 406-465-7067
Fax: 406-841-2811
Email: cohahn@mt.gov

2.2 Roles and Responsibilities Matrix

   2.2.1 Contractor Staff, Roles and Responsibilities (Please identify your project team and provide
   resumes as appendices.)
        Contractor staff that will be involved
        Individuals key to the project
        Detail roles and responsibilities matrix the contractor tasks, staff, hours, rates, cost.
              - Include staff function corresponding to the Org Chart

   2.2.2 Agency Staff, Roles and Responsibilities MTOT will prepare a Project Charter outlining all
   project roles and responsibilities.
      2.2.2.1 Project Executive Members: Jeri Duran- MTOT Administrator, Anna Marie Moe- MTOT
      Manager- Operations

      2.2.2.2 MTOT Project Manager- Corrie Hahn

      2.2.2.3 Business Analysts- Thurston Elfstrom, Norm Dwyer, Jan Wirak, Deb Knudsen

      2.2.2.4 The Project Manager will have the authority to sign off on scope changes and contractor
      team member changes. Note: Any scope changes resulting in budget changes will also require
      a contract amendment.

      2.2.2.5 MTOT’s Project Manager will work directly with the Contractor’s Project Manager to
      assure all data and information is presented to the Contractor in a timely manner.


MTOT .NET Phase III- Survey Tool                                              Page 4 of 15
3.0 Key Assumptions-
   3.0.1 Software and Coding- Integrated third party components are acceptable to the State. All
   custom coding must adhere to the programming assumptions below. It is expected the contractor
   must have documented programming skills in the following areas:
       A. ASP & VBScript- ASP is a server-side script processor developed by Microsoft. VBScript is
          the programming language most often used to power it.
       B. XML, HTML & XHTML- basic markup languages.
       C. C# or VB.Net- C# and VB.Net are general-purpose programming languages. Both have been
          developed by Microsoft as part of its .Net initiative.
       D. .NET Framework 4- The Microsoft .NET Framework is a software framework that can be
          installed on computers running Microsoft Windows operating systems. It includes a large
          library of coded solutions to common programming problems and a virtual machine that
          manages the execution of programs written specifically for the framework. The .NET
          Framework is a Microsoft offering and is intended to be used by most new applications
          created for the Windows platform.
       E. Java- Java is a widely portable programming language that can be used for both client-side
          and server-side web applications.
       F. JavaScript & AJAX- JavaScript is a popular client-side scripting language. AJAX is a web
          development technique that combines Asynchronous JavaScript and XML.
       G. Structured Query Language- SQL is a language used to interact with relational databases.
       H. Cascading Style Sheets (CSS) is a style sheet language used to describe the presentation
          semantics (that is, the look and formatting) of a document written in a markup language.
          It’s most common application is to style web pages written in HTML and XHTML, but the
          language can be applied to any kind of XML document, including SVG and XUL.

   3.0.2 Development Environment- The MTOT uses Windows Server 2008 as its hosting
   environment. The server environment resides on a virtual server located at STISD’s (State of
   Montana) data center in Helena, MT. RAM and storage space can be increased or decreased as
   needed.

      3.0.2.1 The MTOT will provide a test Windows environment and a test Oracle “Tourism”
      database.

      3.0.2.2 Our database environment is Oracle 11G.

      3.0.2.2 The contractor will be provided remote access in to our test environment.

      3.0.2.3 The MTOT will provide one “on site” desk including a phone and LAN access.

      3.0.2.4 The MTOT will move all code from the test environment to the production environment.

      3.0.2.5 The contractor may work remotely with onsite visits as needed.



MTOT .NET Phase III- Survey Tool                                             Page 5 of 15
      3.0.2.6 The contractor a test environment will be identical to the production
      environment.

4.0 Risks
   4.0.1 In an effort to mitigate all risks to the project the attached risk assessment plan will be
   completed within 5 days of the project start date and reviewed monthly.

   4.0.2 See appendix- A1_Risk Assessment and Mitigation Plan

5.0 Scope of Work

5.1 Coding Standards
       5.1.1 For the .NET conversion MTOT is requiring the vendor to adhere to a set of
       coding standards to be used for the conversion (such standards need to include not
       only application coding standards, but also web design st andards.)

       5.1.2 CSharp Coding Standards- See Appendix- A2_CSharp Coding Standards.

       5.1.3 MTOT will conduct random sample code reviews to test that coding standards
       are being upheld.

       5.1.4 To reduce the risk of multiple standards, all new coding made necessary by the
       requirements of this CEP and not covered in the established standards must be
       reviewed and approved by MTOT prior to any development.

       5.1.5 Vendor’s code will be required to pass the State’s Information Technology
       Service Division vulnerability scan prior to being placed into production.

5.2 Inclusions

   5.2.1 Maintain full screen functionality including fully functional .NET controls on all
   surveys. These are controls and features that will appear on all surveys that allow the
   user to search and navigate among records; search by date; completion indicator; create,
   update and delete records; print; tools and survey type indicator.
             5.2.1.1 Comments
             5.2.1.2 Date Range Search Box
             5.2.1.3 Sent Completed Indicator
             5.2.1.4 Tools sidebar- top
             5.2.1.5 Tools sidebar- bottom
             5.2.1.6 Vacation Planner Type Indicators currently the- Printed Guide Type
             Indicator




MTOT .NET Phase III- Survey Tool                                                 Page 6 of 15
   5.2.2 All users shall access the applications via any standard Web browser (Microsoft Internet
   Explorer, Mozilla Firefox, Google Chrome, Apple Safari) on either a Windows or Mac OSX platform
   as well as Apple Mobile Safari for iPad and Chrome browser for Android tablets.

  5.2.3 Surveys will be in compliance with state standards including 508 accessibility.

5.3 Exclusions
       5.3.1 Remove from toolbar- Internet link and Internet Iink Effective Date (option) from the Date
       Range Search Box and Date Range Search control.

       5.3.2 Places of Worship survey (need to remove from the website, city pages)

5.4 Deliverables
       5.4.1 Convert and replace current surveys with fully functional .NET versions- The system will
       allow authenticated users to create, update, delete and print surveys. The MTOT must print
       sets of surveys based on selected criteria (for example “site type=hotel”). All current database
       and control relationships must be maintained.

       Existing .asp survey code is available upon request.

               5.4.1.1 ART_CULTURE_HISTORY
               5.4.1.2 ATTRACTIONS_INFORMATION
               5.4.1.3 BED_AND_BREAKFAST_SURVEY
               5.4.1.4 CAMPGROUND_INFORMATION
               5.4.1.5 DINING_INFORMATION
               5.4.1.6 EVENTS_CALENDAR
               5.4.1.7 GOLF_COURSE_AND_RESORT_INFORMATION
               5.4.1.8 GUIDED_RECREATIONAL_SERVICES_SURVEY
               5.4.1.9 HOSTELS_HOTSPRINGS_LODGES_RANCHES_AN
               5.4.1.10 HOSTELS_HOTSPRINGS_LODGES_RANCHES_AND
               5.4.1.11 HOTEL_MOTEL_SURVEY
               5.4.1.12 INFORMATION_VACATION_PLANNING_ASSIST
               5.4.1.13 MASTERFORM
               5.4.1.14 PHOTO_RELEASE
               5.4.1.15 PRIVATE_CAMPGROUND_RV_PARK_SURVEY
               5.4.1.16 PUBLIC_FACILITIES_INFORMATION
               5.4.1.17 SERVICE_BUSINESS_SURVEY
               5.4.1.18 SHOPPING_INFORMATION
               5.4.1.19 SPECIAL_INTEREST_RECREATION_AND_ADVE
               5.4.1.20 VACATION_HOMES_CONDOS_CABINS_SURVEY


MTOT .NET Phase III- Survey Tool                                               Page 7 of 15
               5.4.21 WAGON_TRAIN_CATTLE_DRIVE_SURVEY
               5.4.1.22 WINTER_RECREATION_INFORMATION
               See Current Survey Forms- Appendices A4 through A25 get updated pdfs

       5.4.2 Based on zip code the system will auto fill City, State, Indian Reservation, Tourism
             Region with an option to override suggested information; replicating current
             functionality of survey tool in current application. A zip code table currently exists in
             our Oracle database.

       5.4.3 Based on selection of Agency system will provide a drop down box of related Sub
             Agencies to be selected; replicating current functionality of survey tool in asp (For
             example National Forest and Flathead National Forest.)

       5.4.4 System will provide a list of related business based on Relationship Table in the
             database; replicating current functionality of survey tool in asp.

       5.4.5 System will produce the correct survey form based on selection of Survey in Survey
             Table, replicating functionality of survey tool in asp. For example if you enter a site ID or
             business name the system will generate the correct survey form.

       5.4.6 System will trigger membership to Montana Groups Website replicating current
             functionality of survey tool in asp

       5.3.7 Survey tool should assign a unique Site_id # to new listings

       5.4.8 When printing the survey form the unique Site_id # must appear on the printed survey
             form replicating current functionality of survey tool in asp

       5.4.9 System shall monitor when the survey was sent, received or last updated and by whom;
              replicating current functionality of survey tool in asp

       5.4.10 System shall provide the ability to search Events by date ranges.

       5.3.11 System should include the ability edit the survey form for addition or removal of
              keywords from a particular survey replicating current functionality of survey tool.

       5.3.12 The system shall have three levels of security with specific rights and roles. Security
              levels will include- Administrator, User and Web User.



MTOT .NET Phase III- Survey Tool                                                Page 8 of 15
5.5 New Functionality

   5.5.1 Mapping:

       5.5.1.1 System should input Latitude/Longitude based on Street Address, defaulting to Service
       City if no street address and readjusting to new data.

       5.5.1.2 System should include ability to adjust Latitude/Longitude and Zoom perspective. This
       will allow us to adjust zoom setting according to businesses requirements.

   5.6.2 Administrative:
       5.6.2.1 Based on login rights the system must have the ability to administrate the following:
           5.6.2.1.1 Input Electronic notes (Historic and Inactive Comments) and provide the ability to
           search notes by date parameters.
               A. Assign Printed Guides Business Type Indicator to records (formerly the Vacation
                   Planner indicator) Note- the MTOT no longer prints a vacation planner. We used to
                   track businesses by VP Indicator. This is being replaced with Printed Guides Business
                   Type Indicator.
               B. Assign Media Calendar indicator
               C. Assign Special Promotion indicator
               D. System should include ability to email and attach the survey form to that email from
                   the survey tool
               E. System should include ability to print all related surveys replicating current
                   functionality of survey tool in asp AND the MTOT should have the ability to able to
                   turn it off. For example if two different surveys are associated with a record you can
                   choose to print just one.
               F. System should include process by which remote record (business) updates remain
                   inactive until reviewed by the MTOT and changes should be marked in red,
                   differentiating them from items not updated.

   5.6.3 Printing:
       5.4.3.1 System should include ability to print an Envelope, groups of envelopes or Label, group
       of labels.

   5.6.4 Sorting:
       5.4.4.1 System should include ability to sort by Email, Site Types, Contact Address as well as
       using the existing sort options, replicating current functionality (controls) of survey tool in old
       asp.




MTOT .NET Phase III- Survey Tool                                                  Page 9 of 15
       5.4.4.2 The System should create a search result page replicating current functionality of the
       survey tool in current application and it should have an option to for records to be exported
       into an Excel document.

   5.6.5 Creating New Record:
       5.6.5.1 System should include a warning dialogue box when the input of a phone number or
       mailing address duplicates information already in the database; that there is a possible need to
       create a relationship with another listing and if the answer is yes, be able to create that
       relationship in the relationship table.

       5.6.5.2 System should have ability deny creation of a new listing without filling in key fields such
       as business name, mailing address or contact address, street address or latitude/longitudes,
       description, outfitter license number if an outfitter, a Lodging Facility Tax number if
       accommodations.

       5.6.5.3 System will include a new survey for Winter Ski Resorts with all the information
       displayed on the ski resort section of Wintermt.com accessible through the survey.
               5.4.5.3.1 System will include ski resort maps and ability to update those maps.

       5.6.5.4 System will include Book Now/ Book Inquiry button information i.e. URL to their
       Reservation Page.

       5.6.5.6 System will include collection of Specials/Packages. They will be stored as text only in a
       text box.

       5.6.5.7 System will ensure that the collections boxes are large enough to see all collected
       information.

   5.6.6 Inclusion of Images- the system will associate images with records.
       5.4.6.1 The system must provide the ability to view the images associated with the listing and
       ability to add, delete and replace with a limit of six (a number we could adjust to future
       requirements) and indicate order of images, photo credit, brief description. Images must be in
       .jpg format.

   5.6.7 Remote Record Update (for Montana businesses):
       5.6.8.1 Add functionality that will allow customers to edit fields remotely.




MTOT .NET Phase III- Survey Tool                                               Page 10 of 15
       5.6.8.2 The system will give the MTOT an administrative function to allow or restrict access to
       the survey fields our customers can update.

       5.6.8.3 The remote update must have a secure log-in using the State of Montana’s ePass or
       similar functionality approved by the state.

       5.6.8.4 The system will notify the administrator when records have been updated.

       5.6.8.5 The remotely entered information will go into an audit table. The new information will
       appear in red text in the tool once approve there will be an activate button to move the newly
       entered data intro the production tables.

   5.6.8 Reporting- The system must provide the ability to generate custom reports. This must be
   functionality found in a product like Crystal Reports. For example we may need to determine the
   number of hotels in each region. Brian examples

   5.6.9 Data Exports- the system shall have built in exports (SQL) to export data in tab or comma
   delimitated format. This will allow the administrator to export records based on selected criteria.
   For example MTOT can export all records in Glacier Country. (This will be used to send regions
   exports for their printed travel planners.) This is intended for a nontechnical user. Integration with
   a third party tool will be acceptable. The MTOT has many commonly used prewritten SQL
   statements. These are available upon request.

       5.6.9.1 An administrative interface will be built to allow the system administrator to set the
       criteria for exports. Parameters may vary according to the requirements of the request. For
       example Regions may want all records from their region or just hotels from their region.
       Newspapers may request all events in a time parameter and specific region.

       5.6.9.2 Exports should be archived in the system.

  5.6.10 Data Imports- The system shall have the ability to import bulk records such as RV Dump Sites
  and Rest Areas. Imports will be in text format (tab or comma delimited). An interface shall be
  provided to match imported fields to the existing database fields.

  5.6.11 Relationships- The system shall allow the user to create relationships between records. For
  example a Guest Ranch that is also an Outfitter can be linked. An event can be linked to a chamber
  of commerce. Related records will show up in a text box in the side toolbar. Those related records
  will be click able links. This will allow the administrator to know when one record changes their


MTOT .NET Phase III- Survey Tool                                               Page 11 of 15
  phone number it must also be done for the related records. This will be stored in the relationship
  table in our database. Examples include; record to record, record to property manager, event to
  chamber.

6.0 Work Approach
    A. This project will be performed according to established Software Development Lifecycle
       http://en.wikipedia.org/wiki/Software_development_process .

   B. Requirements Gathering- Based on discussions with MTOT or specific service request perform
      analysis of the current code and determine the best solution.

   C. Task/Project Plan/Design- Contractor will define task/project details and timeline.

   D. Approval To Proceed – MTOT Project Manager will approve in writing (email notification is
      acceptable) the solution and solution estimate prepared by the contractor prior actual work
      being performed.

   E. Code Generation- Contractor will write supporting code to accomplish the task/project and all
      code will be commented throughout.

   F. Testing- Contractor will test and check the code, in the test environment, to ensure it satisfies
      the established criterion and does not affect current functionality. The MTOT will then test the
      code in the test environment and alert the contractor of any defects.

   G. Deployment- If all defects are fixed the MTOT will move the code into the production
      environment and inform the contractor of its production status.

   H. Acceptance- MTOT will review, test and accept the task/project in the production environment.

   I. Final Acceptance Testing- Once MTOT Project Manager is informed in writing (email is
      acceptable) by the Contractor that work is complete; MTOT will perform and complete final
      acceptance testing within 10 business days.

   J. Upon completion of the acceptance testing, MTOT Project Manager will return in writing (email
      is acceptable) acceptance of the work product, or a definition of the deficiencies.

   K. All components require end-user documentation.




MTOT .NET Phase III- Survey Tool                                             Page 12 of 15
7.0 Completion Criteria and Final Acceptance Criteria

 7.1 Completion Criteria
       7.1.1 Completion Criteria
       Upon completion and testing of the deliverables the Contractor will deliver the work product
       and notify the MTOT Project Manager (notification and delivery of work products in an
       electronic format is preferred). The Project Manager will review the work product and provide a
       statement of acceptance or a statement of product deficiency within 10 days. Contractor will be
       expected to fix any deficiency within 10 days.

       7.1.2 Final Acceptance
       Final acceptance will occur when all deficiencies are resolved. The MTOT Project Manager will
       provide written acceptance. A 45 day warranty period will follow to resolve any bugs and
       errors.

8.0 Schedule—Vendor to complete
   1. TBD-- Dates of the seller’s key tasks or completion of the major elements of the project.

   2. Identify interim quality gate milestones-these are decision points where the project can be
      stopped or approved to go forward.

9.0 Project Management
   1. The MTOT will appoint and assign a project manager.
   2. The Contractor will appoint and assign a project manager.
   3. The contractor will provide the MTOT Project Manager with weekly status reports.

10.0 State Policies Standards and Computing Environment
State Policies, Standards and Computing Environment can be found on the state Web site at:
Environment - http://itsd.mt.gov/techmt/compenviron.mcpx
Policies - http://itsd.mt.gov/policy/default.mcpx
Supported Software- http://itsd.mt.gov/policy/software/default.mcpx

11.0 Timeline and Period of Performance
Outline the dates of contractor’s key tasks or submission of product or service.
The period of performance for this project will start on [start date] and the work tasks are estimated to
continue through [end date]. The MTOT expects this will be on or near October 1st, 2012. The State has
the right to extend or terminate this SOW at its sole discretion.

12.0 Compensation and Payment Schedule

       12.1 Fixed Price This is a fixed price engagement. MTOT shall pay Contractor an amount not to
       exceed ($___) for the performance of all activities necessary or incidental to the performance of
       work as set forth in this SOW. Payments to the contractor will be based on completion and


MTOT .NET Phase III- Survey Tool                                              Page 13 of 15
       acceptance of project milestones plus the final holdback payments. Milestones will be prorated
       based on time, resources required and complexity relative to the overall project.

       12.2 Milestone Holdback: A 2% holdback will be withheld from each milestone payment. The
       total amount withheld will be paid to the contractor at the completion and acceptance of the
       project.

       12.3 Performance Security Hold Back: An additional amount of 10% of the overall project will
       be withheld pending completion and final acceptance of the project.

       The total amount withheld (milestone and security) will be paid to the contractor at the
       completion and acceptance of the project.

13.0 Miscellaneous: The MTOT shall not reimburse the Contractor for travel and other expenses as
identified in this SOW unless authorized in writing, in advance by Agency. No payment of travel
expenses will be made to Contractor for routine travel to and from Agency’s location. Contractor shall
provide a detailed itemization of expenses as requested by Agency. The amount reimbursed to
Contractor is included in calculating the “not to exceed” amount specified above. Additionally:

   A. Support personnel- shall be the responsibility of the contractor.

   B. Shipping, handling and packaging- shall be the responsibility of the contractor.

   C. Conflict resolution agreement- will be defined in the Project Charter.

14.0 Appendices
Appendices are referenced individually in the SOW.

15.0 Execution/Signature Block
In Witness Whereof, the parties hereto, having read this SOW, Montana Office of Tourism - .NET
Phase III Survey Tool to Contract Number SPB 06-1263B in its entirety, do agree thereto in each and
every particular.

Approved                                           Approved

 DOC, Montana Office of Tourism
 301 S Park Ave
 Helena, MT 59620
                                                     FEDERAL ID #


Dorie Schwinden                                    Contractor Name




MTOT .NET Phase III- Survey Tool                                               Page 14 of 15
Print or Type Name                                          Print or Type Name

Title                                                       Title

Date                                                        Date




Legal                                                       Date


The Contractor is notified that pursuant to 2-17-514, MCA, the Department of Administration retains
the right to cancel or modify any contract, project or activity that is not in compliance with the
Agency’s Plan for Information Technology, the State Strategic Plan for Information Technology, or any
statewide IT policy or standard.

Reviewed and Approved by:
Information Technology Services Division
Montana Department of Administration,
per MCA 2-17-512:

_____________________________________                       Date:
State CIO (or Agency Designee for Delegated IT Authority)




MTOT .NET Phase III- Survey Tool                                                 Page 15 of 15

								
To top