|
Step |
Task |
Predecessor |
Resources
|
|
2 |
Identify
Business, Functional, and Technical Requirements |
|
|
|
2.1 |
Business Requirements |
|
|
|
2.2 |
Conduct
risk assessment |
2.3 |
ISB Oversight Risk Assessment and Matrices
Severity
and Risk Matrix |
|
2.3 |
Identify state policies, standards, and guidelines |
|
IT
Portfolio Management Policy, Standards, and Guidelines |
| 2.3a |
Access to information technology for individuals with disabilities, including the public and employees. |
|
WA State Accessibility Guidelines
Accessibility Guide and Resources |
| 2.3b |
State Standards for Internet Markup Language - Extensible HyperText Markup Language (XHTML) 1.0 |
|
XHTML 1.0 Standard |
| 2.3c |
Internet Domain Name Standards |
|
Internet
Domain Name Standards |
| 2.3d |
Web Presentation Guidelines |
|
Web Presentation Guidelines |
2.3e |
Privacy |
|
Privacy
Policy
Model
Privacy Notice |
| 2.3f |
Security Policy |
|
IT Security Policy |
| 2.3g |
Security Standards |
|
IT
Security Standards |
| 2.3h |
E-Commerce Policy |
|
SAAM E-Commerce Policy Chapter 40 |
| 2.3i |
Economic Feasibility Study Information |
|
Economic Feasibility Study Elements and Worksheets |
| 2.3j |
Feasibility Study Elements and Worksheets |
|
Feasibility Study Elements and Worksheets |
| 2.3k |
Core Systems Feasibility Study Tool |
|
Feasibility Study Tool |
2.3l |
ITInvestment Policy |
|
Information Technology Investment Policy |
2.3m |
IT Investment Standards |
|
Information Technology Investment Standards |
2.3n |
Records Retention |
|
Secretary of State - General Records Retention Schedule |
| 2.3o |
IT Standards and Protocol Directions |
|
IT
Standards & Protocol Directions |
| 2.3p |
Review ISB EA Integration Architecture standards and Solution Sets for agency to agency applications |
|
ISB EA Integration Architecture Standards |
| 2.5 |
Conduct business process and data modeling |
|
Example Business Process and Data Modeling |
|
2.6 |
Evaluate other projects and systems for overlap and/or impact |
2.3 |
Agency
IT Portfolio (Intranet) |
| 2.6a |
Identify Communities of Interest |
|
Communities
of Interest |
| 2.6b |
Core Systems Impact Analysis Checklist |
|
Impact Analysis Checklist |
| 2.6c |
Review Section 903 Consultation Process for State IT Products and Services |
|
Section 903 Consultation Process |
| 2.6d |
Identify training needs |
|
IT Training Opportunities Through the Department of Personnel |
|
2.7 |
Complete project planning |
|
Project Management Framework |
| |
Electronic Payments |
|
|
|
2.8 |
If the application contains an electronic transfer of funds, prepare an economic feasibility study to submit to OFM |
2.3, 2.19 |
SAAM E-Commerce Policy Chapter 40 |
| |
|
|
Economic Feasibility Study Elements and Worksheets |
| 2.8a
|
Discuss Banking Arrangements/Credit Card Rates/Options
|
|
Office of the State Treasurer and SAAM Chapter 65 |
| 2.8b |
Internet Check master contract with U.S. Bank is available to state and local governmental organizations and qualifying non-profits.
|
2.8
|
Internet Check Payment Services |
| 2.8c |
Full range of services including a complete dual-server environment for hosting secure, credit card-enabled Web sites.
|
2.8 |
e-Payment Services |
| 2.8d |
Intergovernmental Network (IGN) customers considering implementation of web-based credit card applications.
|
|
IGN e-Pay Guide |
|
2.9 |
With OFM approval, obtain a merchant identification number |
|
Office of the State Treasurer |
| |
SECURITY |
|
|
|
2.10 |
Identify security needs including digital signature/certificates |
|
Information Technology Security Policy
|
|
2.10a |
If the application contains the use of digital signatures, consider Transact WA |
|
DIS Enterprise Security Services Transact
WA admin
|
|
2.10b |
If the application contains the use of anonymous login or user id and password, consider Fortress |
|
Fortress Secure Access Service |
|
2.10c |
If application requires a user ID and password, consider SecureAccess Washington™ |
|
SecureAccess Washington™ Single Sign-on Service |
|
2.11 |
Develop an agency privacy policy statement |
2.3 |
Model Privacy Notice |
|
2.12 |
Identify
help desk options |
|
Web-based Customer Support |
|
|
|
Safeharbor.com |
|
2.13 |
Determine hardware/software capacity, conduct analysis and needs identification |
|
|
|
2.14 |
Conduct system inventory (What HW/SW is available now?) |
|
Review
Agency IT Portfolio (Intranet) |
|
2.15 |
Develop General Design |
|
|
|
2.16 |
Prepare system analysis (What HW/SW do we need?) |
|
|
|
2.17 |
Prepare contingency plan |
|
|
|
2.18 |
Continue risk management |
|
|
|
2.19 |
Conduct IT Feasibility Study if necessary |
|
Feasibility Study Guidelines for Information Technology Investments |
2.20 |
Secure needed funding approvals to proceed to detailed design |
|
Office of Financial Management Budget Instructions |
2.21 |
Prepare quality assurance plan |
|
|
2.22 |
Prepare disaster recovery plan |
|
|
2.23 |
Begin developing test plans |
|
|
2.24 |
Functional Requirements |
|
|
|
2.25 |
Consider impact of Web application on current business processes |
|
Review agency IT Portfolio (Intranet) |
|
2.26 |
Identify technical capacity of the organization and scalability of technical assets |
|
Review agency
IT Portfolio (Intranet) |
2.27 |
Identify technical interface needs |
|
Agency IT Portfolio and other agencies if necessary |
|
2.28 |
Technical Requirements |
|
|
|
2.29 |
Identify e-payment technical options |
2.8 |
DIS e-Payment services |
2.30 |
|
|
|
|
2.31 |
Identify security needs for data, access, hardware, software, network, etc. |
1.8 |
IT
Security Policy |
|
|
|
Information Technology Security Standards |
|
|
|
Agency IT Portfolio (Intranet) |
|
2.32 |
Establish Web hosting environment |
|
DIS Web Hosting |
2.33 |
Obtain Domain name |
|
Obtain Domain or Host Name |
2.34 |
Obtain a D-U-N-S number for commerce |
|
Dun & Bradstreet |
|
2.35 |
If not using DIS e-payment server, obtain verisign certificate for SSL security. |
|
VeriSign SSL Certificates |
2.36 |
Identify what Web content exists and what needs to be developed |
|
Agency internal communications office and agency program area |
2.37 |
Identify graphical design issues |
|
Web Presentation Guidelines for Digital Government |
2.38 |
Define site map and user interface paths |
|
Web Presentation Guidelines for Digital Government |
2.39 |
Identify Access WA portal needs |
|
About Access WA |
2.40 |
Identify Transact WA portal needs |
|
About Transact Washington |
| 2.41 |
Update project scope |
|
|
| 2.41a |
Update To-Be Model and Transition Plan |
|
|
| 2.42 |
Update project workplan, costs, and schedule |
|
|