whiteboard_checklist

Document Sample
whiteboard_checklist Powered By Docstoc
					                                Whiteboard Checklist

The purpose of a whiteboard session is to determine the best approach and best
practices to address a business need using information technology. During the session,
the business need is described. Topics covered during these sessions include technology, data,
warehousing, and security requirements, and Ministry standards. Opportunities for system and
data integration with other applications are also discussed.



Application Name:

Application Acronym:

Business Analyst:                                                   Phone No.

Application Administrator:                                          Phone No.

Vendor Project Manager:                                             Phone No.

Data Custodian:                                                     Phone No.




Version 3.2                            Page 1
       Whiteboard Participants

              Participants                                            Date
                                                                    __/__/__
              ___________________________________________________
              ___________________________________________________
              ___________________________________________________
              ___________________________________________________
              ___________________________________________________
              ___________________________________________________
              ___________________________________________________
              ___________________________________________________
              ___________________________________________________
              ___________________________________________________
              ___________________________________________________



       Purpose




Version 3.2                                                            Page 2
Feasibility Whiteboard Session
[Only populate this section when a feasibility whiteboard is being conducted to determine the methodology and
development framework to be used to resolve the identified business problem.
Go through the items used to define Mainstream versus Lightweight development]
    Proposed Technology                                                             Responsibilityi      Date
 Record information on the proposed technologies to be used for this                AA/DA/DBA/        __/__/__
      project:                                                                      DEL/INF/
                                                                                    Helpdesk
              MainStream Development
                 Java Application
                 Data Warehouse
                 Operational Database

                 Oracle Database
                 SDE
                 Oracle Locator

                 Oracle Reports
                 Oracle Discoverer

                   ArcIMS
                   IMF
                   OGC IMF
                   OGC Web Map Service

                 Web static pages
                 ESF

                 Public Facing
                 Private/Internal to Government
                 Uptime/Support Expectations

              Lightweight Development
                  MS Access
                  InfoPath
                  Other [Identify the software to be used]

              Configuration
                 COTS
                 Sharepoint




Version 3.2                                                                                   Page 3
Technical Whiteboard Session
[This type of whiteboard is to be conducted for Mainstream applications either for new applications or
enhancements to the application that may result in new functionality or a change to the technology used.]
     Technology Information                                                         Responsibility1        Date
 Record Information on the technologies to be used for this project:                AA/DA/DBA/          __/__/__
                                                                                     DEL/INF/
              MainStream Development                                                 Helpdesk
                 Java Application
                 Oracle Web Forms Application
                 PL/SQL Cartridge App
                 WEBDB
                 Data Warehouse
                 Operational Database

                   Oracle Database
                   SDE
                   Oracle Locator
                   File System Storage (images, documents, scripts)
                   Oracle Reports
                   Oracle Discoverer

                 Solaris file, email, CRON Services
                 ATS

                   ArcIMS
                   IMF
                   OGC IMF
                   OGC Web Map Service

                 Web static pages
                 ESF

                 Authentication
                 Authorization

              Lightweight Development
                  MS Access
                  InfoPath
                  Other [Identify the software to be used]

              Configuration
                 COTS
                 Sharepoint

      Security Information                                                        Responsibility1          Date
     Record information on security requirements (select all that apply):             AA/DA             __/__/__
              Public Access (No authentication required)
              IDIR authentication
              BCeID authentication
              Data Access Restrictions
              SDE/Oracle access
Version 3.2                                                                                     Page 4
              Oracle only access
              WebADE
              Solaris LDAP
              IDIR groups

      Other Information                                                        Responsibility1        Date
     Check for other project dependencies that may affect the project             AA/BA            __/__/__
     Licensing                                                                Responsibility1        Date
     Record information on the potential number of concurrent Users           DBA/Vendor/          __/__/__
                                                                                 DataBC
          Oracle Database
          Oracle Application Server
          ArcView
          SDE
          ArcInfo
          FME
     File Cleanup / Retention                                                 Responsibility1        Date
Identify need for file cleanup (app generated output, temp files, reports,   AA/BA/Vendor         __/__/__
      etc.)
 Development & Delivery Standards                                             Responsibility1        Date
 Discuss Development Standards                                                     BA             __/__/__
 Discuss Delivery Standards                                                        BA             __/__/__
 Have Vendor Prepare Standards Deviation Documentation                             BA             __/__/__




Version 3.2                                                                                Page 5
Operational Data / Data Warehousing Whiteboard Session
[This is a joint session with resources from GEOBC.]
     Dataset Information                               Responsibility1                                     Date
 Record Information About Data Ownership                 BA/DA                                          __/__/__
          Who is the data custodian?
          Is there a steward / data manager?

 Record information about the data:                                                 DC/BA/DA           __/__/__
      Dataset Name
      Data Classification Hierarchy – Level 1
      Data Classification Hierarchy – Level 2
      Data contents – Briefly describe the content of information that
                the dataset contains.
              Is this spatial data, attribute data or both?
              How is the Data maintained?
              Complexity – Is the dataset simple or complex?

      Record information about transformation
         Data Warehouse logical model (operational subsets, views) 
         What type of replication is required?
         Load frequency – How often should the dataset be replicated?
         Is data conversion required?
         Is data manipulation required (e.g. converting shape files to
              SDE layers)

              Is metadata information recorded in MetaStar?
              Inform data custodian / manager that they are responsible for
                  metadata.

      Security Information                                                          Responsibility1        Date
 What type of warehouse security is required? Direct connect to Oracle,           AA/DA/DataBC         __/__/__
      through an application, iMapBC, or via Distribution Service
 Record information about the security:                                               AA/DA            __/__/__
       Who are the data users?
       Is this data freely viewable to the public?
       Is there sensitive data that must be restricted to certain
                 audiences?
              Are there copyright restrictions?
              Are there data sharing restrictions?
              Is there a requirement for users to sign a data sharing
                 agreement?
              Are there Protection of Privacy concerns?
              Is this data, or part thereof priced data?
              If the data is not freely viewable or downloadable to the public,
                 may the public view or download part of it? Please specify
                 (e.g. raster only viewing and/or limit on number of displayed
                 records).
              Are the Data Sensitivities limited to some attributes or records
                 types such that appropriate filtering would allow the remaining
                 data to be exposed to a wider audience?
              Where data is not public (un-restricted or view only), is it open
                 to internal government staff? If not specify what data is not
                 and to whom it is open.
Version 3.2                                                                                     Page 6
              Are there any data exchange partners that require special
                 access considerations?
              Are there other data access considerations that need to be
                 applied to the dataset or a given component of the dataset?

 Specific Data Requirements                                                   Responsibility1        Date
 Record information about data modeling requirements                               DA             __/__/__
       Logical Data Model required
       Business views – Are they required? How many? Have
                   custodian provide detail.
              Confirm the attributes in new ArcSDE layer.
              Current feature count.

     Record information about data capacity requirements                       AA/BA/DA/           __/__/__
      Data volume in Gigabytes ______ (Initial warehouse database size)           Vendor

      Expected growth rate
      Expected increase for next 3 years:
       1st year: %
       2nd year: %
       3rd year: %


 Common corporate “shareable” tables and codes required                             DA             __/__/__
 Check Urgency or dependent projects (Timing of loading)                          AA/BA            __/__/__
 Development & Delivery Standards                                             Responsibility1        Date
 Discuss Data Related Standards                                                    BA             __/__/__
 Discuss Data Related Delivery Standards                                           BA             __/__/__
 Have Vendor Prepare Standards Deviation Documentation                             BA             __/__/__




Version 3.2                                                                                Page 7
Standards Deviation

 Standards Deviation                                                Responsibility1       Date
 Paste content from Vendor prepared standards deviation into this         BA            __/__/__
      document.


i
 AA – Application Administrator
BA – Business Analyst
DA – Data Architect
DBA – Database Architect
DEL – Application Delivery
INF – Infrastructure
Helpdesk – Helpdesk
TA – Technical Architect
Vendor - Contract Vendor
DC – Data Custodian
DataBC – Resources from DataBC




Version 3.2                                                                      Page 8

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:3
posted:11/18/2012
language:Unknown
pages:8