20.10.2014 Views

National Electronic Disease Surveillance System (NEDSS ...

National Electronic Disease Surveillance System (NEDSS ...

National Electronic Disease Surveillance System (NEDSS ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>NEDSS</strong> Phase II, Deliverables 1 and 2<br />

V. Technical Process Plans<br />

Process Model<br />

The process model for this project is outlined in the project plan attached (see Appendix).<br />

Though not all phase tasks flow in a sequential format, the overall flow is from top to bottom, or<br />

Planning to Requirements to Design to Build to Test to Implement to Review.<br />

Several of the phases have appropriate review and revision tasks, which allow the appropriate<br />

stakeholders to be updated on the project status and allow for minor project adjustments.<br />

Methods, Tools and Techniques<br />

This project will utilize only established engineering methodologies (e.g. IEEE standards) and<br />

tools. The specific programming tools will be determined when the <strong>NEDSS</strong> Base system is<br />

released. All other standards will be determined at the appropriate time after consultation with<br />

CDC and DoTS technical resources for compatibility within the respective environments.<br />

Infrastructure<br />

The technical infrastructure is dependant on the established standards within BOH, DoTS and<br />

those that are required by <strong>NEDSS</strong>. What will need to be determined during the associated<br />

phases (i.e. Build, Test and Implement) are as follows:<br />

• Hardware, operating system, network and software<br />

• Policies, procedures, standards, and facilities<br />

• Workstations, local area networks, software tools for analysis, design implementations,<br />

testing, and project management,<br />

• Desks, office space, etc.<br />

Implementation Acceptance<br />

Once the final system specifications are determined (Requirements Traceability Matrix), the<br />

criteria for both technical and user (stakeholder) deliverable acceptance is established. The<br />

Traceability Matrix will list every key function point of the system and how it is measured.<br />

Once the project sponsors and key stakeholders have signed off this document, the appropriate<br />

standards are in place to determine (measure) the status of the deliverables.<br />

PHRG Page 14 of 35 September 28, 2001

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!