U.S. Department of Health and Human Services
Indian Health Service: The Federal Health Program for American Indians and Alaska Natives
A - Z Index:
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
T
U
V
W
X
Y
Z
#
Web Services  

Development Process

Static Website Request Process

  1. The Content Manager and/or Project Sponsor reviews the instructions listed on the Web Services Website Requests page and fills out the online Web Services Request form (WSRF) and other forms required to get the process started.
  2. The Web Services Manager reviews the submitted WSRF. If approved, the request is prioritized and added to the pending static queue.
  3. The Web Services Manager will contact the Content Manager and/or Project Sponsor to verify that the site content is complete and they are ready to work with the Content Specialist and Designer.
    Note: The project request remains in the queue until a Designer becomes available. To check for prioritization and order, view the Web Services queue.
  4. When a Designer is available, the Project Manager assigns the project. The Web Services Manager will contact the Content Manager and/or Project Sponsor to reconfirm that the project is ready to go and the content is ready.
  5. The Designer will set up a kick-off meeting with the Content Manager and/or Project Sponsor, Web Services Manager and the Content Specialist to:
    • Introduce the Web Team members
    • Explain objectives, roles and responsibilities
    • Set expectations for the new or redesigned web site.
    • Review the content and plan for additional content.
    • Explain the status of approval, if required, of the new or revised content.
  6. The Content Specialist receives the draft content from the Content Manager and/or Project Sponsor and reviews it for 508 compliance and Plain Language Guidelines. The Content Specialist will:
    • Make recommendations and collaborate with the Content Manager and/or Project Sponsor regarding content
    • Forward the finalized content to the Designer
    • Collaborate with the Designer
  7. The Designer develops, tests the site and submits it to the Web Services Manager for review and approval.
  8. The Web Services Manager reviews the site for compliance with Federal, HHS and IHS Web standards, usability standards and Section 508 requirements.
  9. Once the Web Services Manager gives the final approval, the web site is ready to go live.

Web Application Request Process

  1. The Content Manager and/or Project Sponsor reviews the instructions listed on the Web Services Website Requests page and fills out the online Web Services Request form (WSRF) and other forms required to get the process started.
    Note: Depending on the circumstances, additional forms may be needed. These forms can be found on the Website Requests page.
  2. The Web Services Manager reviews the submitted WSRF. If approved, the request is prioritized and added to the pending Application queue.
    Note: The project request remains in the queue until a Developer becomes available. To check for prioritization and order, view the Web Services queue.
  3. The Business Needs Statement (BNS) will be routed through the approval process by the CPIC Web Application. The sponsor/requestor will be automatically notified once approved.
    Note: If the project is estimated to cost more than $100,000, it will also require submission of a Business Case.
  4. When a Developer is close to being available to work on the project, the Project Manager will assign the project.
  5. The Project Manager prepares the Project Charter, Project Management Plan, Project Process Agreement, and Project Schedule with input and approval from the Project Sponsor and Web Services Manager. Once approved, the Project Manager assigns the project to the Business Analyst.
  6. The Business Analyst works with the Content Manager and/or Project Sponsor and writes the Software Requirements Specifications (SRS), documenting the requirements of the application.
  7. When the SRS is fully approved, a Developer is assigned to the project and provided a copy of the SRS to work from.
  8. The Developer:
    • Documents data and database design into a Data Document
    • Writes the User Acceptance Test (UAT) Plan and the Deployment Checklist
    • Creates a prototype
    • Codes and tests the application
    • Has the Content Manager and/or Project Sponsor and designated testers perform the UAT
    • Submits the completed Web application to the Web Services Manager for review
  9. The Web Services Manager reviews the site for compliance with Federal, HHS and IHS Web standards, usability standards and Section 508 requirements.
  10. Once the Web Services Manager gives the final approval, the application is ready to go live following the steps laid out in the Deployment Checklist.