Epilink: Requirements and Implementation, Coursework Example

Requirements

Building a project plan incorporates all three key areas of a project including, schedule, cost and quality. All three of the constraints play pivotal roles in the successful completion of the project (Dobson 2004). With project management the requirements of the project define the scope, schedule and cost of the project. With the requirements defined the project manager can utilize the tools and techniques of the project management best practices to successfully manage a project and complete it on time, on budget and provide the deliverables the stakeholders required. To understand the specific requirements the scope must be understood and outline the major deliverables. From those deliverables the specific requirements or system specifications can be outlined. The scope of this project implementation includes implementing a web-based system for notifiable diseases state-wide. The system implementation has multiple deliverables but it also includes requirements from outside entities. These requirements will be handled by the specific teams responsible for those requirements and integrations into the system. The implementation plan requires specific project deliverables as well. The larger the project, the more imperative it is to clearly define the scope of the project (Kanaracus, 2012).

The system requirements are as follows:

Implementation of a Scalable Web-Based System for Notifiable Diseases:

• Encompass the entire state
• Provide key data and reporting on notifiable diseases
• Knowledge Management System
  • Searchable
  • Editable
  • Enterprise Wide access
  • Auditing capability for changes to knowledge
  • Accessed by multiple platforms (PC, Smart Phone, Tablet, etc.)
  • Printable
  • Savable (Multiple formats, .doc, .pdf. .xls, .pdf, .vso, etc.)
• Module Implementation
  • Form Designer
  • Enter Module
  • Analysis Module
  • Epi Map
• Rapid Creation of Data
• Multiple Points of Data Analysis
• Approval Management System
• Communication Tools
  • Internal (WebEx, Screen Share, Instant Message)
  • External (WebEx, Screen Share, Instant Message)
• Support
  • System Support
  • Configuration Support
  • Production Support

The requirements outline the basic needed functionality of the system and what is needed by the Health Division to have an up-and-running web-based system to perform the key functions they need to perform their duties. Through the detailing of the project requirements there will be user stories created to fully understand the usage of the system and the people utilizing the tool. There will also be a Gap Analysis conducted on the available tools that support the general requirements to understand the capability of off-the-shelf capabilities or if the system will need to be developed with the expertise of the information technology team of the company.

Implementation

This system is basically an all-inclusive knowledge management system. The primary system of implementation is the Epi Info 7. This tool is used by physicians, nurses, epidemiologists and other public health workers to easily access critical data in an easy and usable process. There are many challenges when developing a knowledge management system. When developing or implementing any new idea or project there are hurdles that the project team will encounter that span outside of the viability and functionality that the project is going to provide There are outside factors that could present themselves as obstacles but understanding those challenges can turn those obstacles into opportunities.

The implementation of the project will take part in a series of implementations divided by regions of the state. The reason for this is the mitigate the risk associated with the waterfall project management methodology incorporated into a big-bang approach and utilize the agile project management methodology for developing the system into a sustainable and repeatable process. The project implementation will follow three distinct implementation cycles. Each region will be designed around geographic separations of the state. This allows for a centralized command and control of the project work. This also alleviates the burden of the number of facilities on the project team and allows a pinpointed focus on key facilities. Once each area rolls onto the new platform the next area will immediately begin the process for implementation. As the project progresses the lessons learned will allow for greater implementation speed and accuracy (Prencipe, Davies, & Hobday, 2007).

The project will follow this implementation schedule:

This process will be repeated by the three iterative roll-outs and will conclude with the last area going live approximately one year after the first go-live event. Each area of the project will revolve around the key functional areas of the Epi Info system including the form designer, enter module, analysis module and Epi Map. Each of these areas will be the become key milestones of the project schedule and become the focal points in the critical path of the project.

References

Dobson, M. (2004). The triple constraints in project management. Vienna, VA: Management Concepts.

Kanaracus, C. (2012). Survey finds erp software project overruns ‘distressingly common’. Retrieved from http://www.cio.com/article/710777/Survey_Finds_ERP_Software_Project_Overruns_39_distressingly_Common_39_?taxonomyId=3009

Prencipe, A., Davies, A., & Hobday, M. (2007). The business of systems integration. Oxford University Press, USA

Project Management Institute, P. M. (2008). A guide to the project management body of knowledge. (4th ed.). Newtown Square: Project Management Inst.