ComputerScienceExpert
$18/per page/
The retail store has hired you to assist in resolving the recent networking problems that have been occurring. The new owner needs you to address the issues so that his company can accomplish its mission and goals. He thinks that the network needs to expand (or at least be fixed), but at this point, he has no idea what the current network has or what it needs. The owner needs you to assess the current network, come up with some conclusions about next steps, and report the results to him. He wants to make sure that you have a good understanding of his goals and objectives as well as the presenting problems.
Examples are provided here to help with this assignment.
Click on this link to view a sample of an Implementation Plan template. When you open the Web site, click on "Templates," and then click on "Implementation Plan."
You have been asked to develop a solution in the form of a Network Design and Implementation Plan for your retail store using the following format:
Each week, you will add a section to this Network Design and Implementation Plan and submit for grading. As a preview, each section will contain the following:
The project deliverables for this week are as follows:
Please submit your assignment.
For assistance with your assignment, please use your text, Web resources, and all course materials.
<PROJECT NAME>
IMPLEMENTATION PLAN
Version <1.0>
<mm/dd/yyyy> [Insert appropriate disclaimer(s)] <Project Name> VERSION HISTORY
[Provide information on how the development and distribution of the Project Implementation Plan was controlled and tracked. Use the table below to provide the version
number, the author implementing the version, the date of the version, the name of the
person approving the version, the date that particular version was approved, and a brief
description of the reason for creating the revised version.]
Version # Implemented
By Revision
Date 1.0 <Author name> <mm/dd/yy> Approved
By
<name> Approval
Date
<mm/dd/yy> Implementation Plan Template (v1.0) Reason
<reason> Page 2 of 19
[Insert appropriate disclaimer(s)] <Project Name> Notes to the Author
[This document is a template of a Project Implementation Plan document for a project. The template includes instructions to the author, boilerplate text, and fields that should be replaced with the values spe cific to the project.
• Blue italicized text enclosed in square brackets ([text]) provides instructions to the document author, or describes the intent, assumptions and context for content included in this document. • Blue italicized text enclosed in angle brackets (<text>) indicates a field that should be replaced
with information specific to a particular project. • Text and tables in black are provided as boilerplate examples of wording and formats that may be
used or modified as appropriate to a specific project. These are offered only as suggestions to
assist in developing project documents; they are not mandatory formats. When using this template, the following steps are recommended:
1. Replace all text enclosed in angle brackets (e.g., <Project Name>) with the correct field document values. These angle brackets appear in both the body of the document and in headers and
footers. To customize fields in Microsoft Word (which display a gray background when selected)
select File->Properties->Summary and fill in the appropriate fields within the Summary and Custom tabs.
After clicking OK to close the dialog box, update all fields throughout the document selecting
Edit>Select All (or Ctrl-A) and pressing F9. Or you can update each field individually by clicking
on it and pressing F9.
These actions must be done separately for any fields contained with the document’s Header and
Footer.
2. Modify boilerplate text as appropriate for the specific project.
3. To add any new sections to the document, ensure that the appropriate header and body text
styles are maintained. Styles used for the Section Headings are Heading 1, Heading 2 and Head ing 3. Style used for boilerplate text is Body Text.
4. To update the Table of Contents, right-click on it and select “Update field” and choose the option “Update entire table”.
5. Before submission of the first draft of this document, delete this instruction section “Notes to the
Author” and all instructions to the author throughout the entire document. Implementation Plan Template (v1.0) Page 3 of 19
[Insert appropriate disclaimer(s)] <Project Name> Table of Contents 1. Introduction..............................................................................................................................7
1.1 PURPOSE.....................................................................................................................7
1.2 SYSTEM OVERVIEW......................................................................................................7
1.2.1 System Description.........................................................................................................7
1.2.2 Assumptions and Constraints .........................................................................................7
1.2.3 System Organization.......................................................................................................7
1.3 GLOSSARY...................................................................................................................7
2 Management Overview..............................................................................................................7
2.1 DESCRIPTION OF IMPLEMENTATION................................................................................7
2.2 POINTS-OF-CONTACT................................................................................................... 8
2.3 MAJOR TASKS..............................................................................................................8
2.4 IMPLEMENTATION SCHEDULE.........................................................................................9
2.5 SECURITY AND PRIVACY...............................................................................................9
2.5.1 System Security Features..............................................................................................10
2.5.2 Security Set Up During Implementation......................................................................10
3 Implementation Support..........................................................................................................10
3.1 HARDWARE, SOFTWARE, FACILITIES, AND MATERIALS..................................................10
3.1.1 Hardware.......................................................................................................................10
3.1.2 Software........................................................................................................................11
3.1.3 Facilities........................................................................................................................11
3.1.4 Materials.......................................................................................................................11
3.2 DOCUMENTATION........................................................................................................11
3.3 PERSONNEL...............................................................................................................12
3.3.1 Staffing Requirements .................................................................................................12
3.3.2 Training of Implementation Staff.................................................................................12
3.4 OUTSTANDING ISSUES................................................................................................ 12
3.5 IMPLEMENTATION IMPACT............................................................................................13
3.6 PERFORMANCE MONITORING......................................................................................13
3.7 CONFIGURATION MANAGEMENT INTERFACE.................................................................13
4 Implementation Requirements by Site...................................................................................13
4.1 SITE NAME OR IDENTIFICATION FOR SITE X.................................................................13
4.1.1 Site Requirements.........................................................................................................13
4.1.2 Site Implementation Details.........................................................................................14
4.1.3 Risks and Contingencies...............................................................................................15
4.1.4 Implementation Verification and Validation ................................................................15
4.2 ACCEPTANCE CRITERIA ..............................................................................................15
APPENDIX A: Project Implementation Plan Approval..........................................................16
Implementation Plan Template (v1.0) Page 4 of 19
[Insert appropriate disclaimer(s)] <Project Name> APPENDIX B: REFERENCES..................................................................................................17
APPENDIX C: KEY TERMS.....................................................................................................18
APPENDIX D: System Hardware Inventory............................................................................19
APPENDIX E: System Software Inventory.............................................................................20 Implementation Plan Template (v1.0) Page 5 of 19
[Insert appropriate disclaimer(s)] <Project Name> 1. Introduction
1.1 Purpose
[This subsection of the Project Implementation Plan describes the purpose of the plan
and identifies the system to be implemented.]
1.2 System Overview
[This subsection of the Project Implementation Plan provides a description of the system to be implemented and its organization.]
1.2.1 System Description
[This subsection of the Project Implementation Plan provides an overview of the processes the system is intended to support. If the system is a database, provide a description of the type of data maintained, sources and uses of that data. Include any
identification numbers, titles, abbreviations, version numbers and release numbers to
describe the system. ]
1.2.2 Assumptions and Constraints
[This subsection of the Project Implementation Plan describes the assumptions made
regarding the development and execution of this document as well as the applicable
constraints. Some items to consider when identifying the assumptions and constraints
are:
o Schedule
o Budget
o Resource availability and skill sets,
o Software and other technology to be reused or purchased,
o Constraints associated with product interfaces ]
1.2.3 System Organization
[This subsection of the Project Implementation Plan provides a description of the system structure and the major system components essential to its implementation. It
should describe both hardware and software, as appropriate. Charts, diagrams, and
graphics may be included as necessary to provide a clear picture of the system.]
1.3 Glossary
[This subsection of the Project Implementation Plan lists all terms and abbreviations
used in this plan. If it is several pages in length, it may be placed in an appendix.] 2 Management Overview
[This section of the Project Implementation Plan provides a description of how the implementation will be managed and identifies the major tasks involved.]
2.1 Description of Implementation
[This subsection of the Project Implementation Plan provides a description of the
planned deployment, installation, and implementation approach. Include whether the
system will be implemented using a phased approach or an “instant-on” approach. ]
Implementation Plan Template (v1.0) Page 6 of 19
[Insert appropriate disclaimer(s)] <Project Name> 2.2 Points-of-Contact
[This subsection of the Project Implementation Plan identifies the System Proponent,
the name of the responsible organization(s), titles, and telephone numbers of the staff
who serve as points of contact for the system implementation. These points-of-contact
should include the Business Sponsor, Program Manager, Project Manager, Quality Assurance Manager, Configuration Management Manager, Security Officer, Database Administrator, or other managers and representatives with responsibilities relating to the
system implementation. The site implementation representative for each field installation or implementation site should also be included, if appropriate.]
Add additional lines as needed to the table. If the applicable team members are listed
in the Project Management Plan, reference the appropriate section within that document.]
Role Name Contact Number Business Sponsor
Project/Program Manager
Government Project Officer
System Developer or System
Maintainer
Quality Assurance Manager
Configuration Management Manager
Security Officer
Database Administrator
Site Implementation Representative
IV&V Representative Table 2.2 – Points-of-Contact
2.3 Major Tasks
[This subsection of the Project Implementation Plan provides descriptions of the major
system implementation tasks. Add as many subsections as necessary to this subsection to describe all the major tasks. The tasks described in this subsection are not sitespecific, but generic or overall project tasks that are required to install hardware, software, and databases, prepare data, and validate the system
If several implementation approaches are being reviewed, then identify the advantages,
Implementation Plan Template (v1.0) Page 7 of 19
[Insert appropriate disclaimer(s)] <Project Name> disadvantages, risks, issues, estimated time frames, and estimated resource requirements for each option considered. These options could include: •
•
•
• Incremental implementation or phased approach
Parallel execution
One-time conversion and switchover
Any combinations of the above. Include the following information for the description of each major task, if appropriate: •
•
•
• What the task will accomplish
Resources required to accomplish the task
Key person(s) responsible for the task
Criteria for successful completion of the task (e.g., “user acceptance”) Examples of major tasks are the following: •
•
•
•
•
•
•
•
•
•
• Provide overall planning and coordination for the implementation
Provide appropriate training for personnel
Ensure that all manuals applicable to the implementation effort are available
when needed
Provide all needed technical assistance
Schedule any special computer processing required for the implementation
Perform site surveys before implementation
Ensure that all prerequisites have been fulfilled before the implementation date
Provide personnel for the implementation team
Acquire special hardware or software
Perform data conversion before loading data into the system
Prepare site facilities for implementation Consider addressing the changes that may be necessary once the system has been implemented. These changes may include, but are not limited to, personnel and technology equipment alignment, and contractor support.]
2.4 Implementation Schedule
[This subsection of the Project Implementation Plan provides a schedule of activities to
be accomplished. Show the required tasks (described in Subsection 2.3, Major Tasks)
in chronological order, with the beginning and end dates of each task. If MS Project is
used to plan the implementation, include the project Gantt chart. Include any milestones
from the projects that are dependent on this project and vice-versa.]
2.5 Security and Privacy
[This subsection of the Project Implementation Plan includes an overview of the system
security and requirements that must be followed during implementation. If the system
contains personal data, describe how Privacy Act concerns will be addressed.]
Implementation Plan Template (v1.0) Page 8 of 19
[Insert appropriate disclaimer(s)] <Project Name> 2.5.1 System Security Features
[This subsection of the Project Implementation Plan provides an overview and discussion of the security features that must be addressed when it is implemented. It should
include the determination of system sensitivity and the actions necessary to ensure that
the system meets all the criteria appropriate to its Certification level. Reference the applicable security guidance documents.]
2.5.2 Security Set Up During Implementation
[This subsection of the Project Implementation Plan addresses security issues specifically related to the implementation effort, if any. For example, if LAN servers or workstations will be installed at a site with sensitive data preloaded on non-removable hard disk
drives, address how security would be provided for the data on these devices during
shipping, transport, and installation because theft of the devices could compromise the
sensitive data.] 3 Implementation Support
[This section of the Project Implementation Plan describes the support hardware, software, facilities, and materials required for the implementation, as well as the documentation, necessary personnel and training requirements, outstanding issues and implementation impacts to the current environment. The information provided in this section
is not site-specific. If there are additional support requirements not covered by the subsequent sections, others may be added as needed.] 3.1 Hardware, Software, Facilities, and Materials
[This subsection of the Project Implementation Plan lists all support hardware, software,
facilities, and materials required for the implementation.]
3.1.1 Hardware
[This subsection of the Project Implementation Plan provides a list of support equipment
and includes all hardware used for installing and testing. This hardware may include
computers, servers, peripheral equipment, simulators, emulators, diagnostic equipment,
other non-computer equipment as well as any network and data communication requirements. The description should include the specific models, versions, configuration
settings, and the equipment owner. Also include information about manufacturer support, licensing, and usage and ownership rights, and maintenance agreement details.
If this information is recorded in another document or system, such as the Configuration
Management Plan or tool, identify that item here. Otherwise, refer to the Hardware Inventory table in Appendix D.
For example, if a web-enabled database is to be implemented, identify the application
and web servers that will provide network access. If the hardware is site-specific, list it
in Section 4, Implementation Requirements by Site.] Implementation Plan Template (v1.0) Page 9 of 19
[Insert appropriate disclaimer(s)] <Project Name> 3.1.2 Software
[This subsection of the Project Implementation Plan provides a list of non-hardware
components (software, databases, and compilers, operating systems, utilities, etc.) required to support the implementation. Identify the component by specific name, code, or
acronym, identification numbers, version numbers, release numbers, and applicable
configuration settings. Also, include information about vendor support, licensing, usage,
and ownership rights, as well as any required service and/or maintenance contract
costs and associated payment responsibility. Identify whether the component is commercial off-the-shelf, custom developed or legacy. Identify any component used to facilitate the implementation process.
If this information is recorded in another document or system, such as the Configuration
Management Plan or tool, identify that item here. Otherwise, refer to the Software Inventory table in Appendix E.
If the component is site-specific, list it in Section 4, Implementation Requirements by
Site.]
3.1.3 Facilities
[This subsection of the Project Implementation Plan identifies the physical facilities, accommodations and their location(s) required during implementation. Examples include
physical workspace for assembling and testing hardware components, desk space for
software installers, floor space for equipment, and classroom space for training the implementation staff. Specify the hours per day needed, number of days, and anticipated
dates.
If the facilities needed are site-specific, provide this information in Section 4, Implementation Requirements by Site.]
3.1.4 Materials
[This subsection of the Project Implementation Plan identifies any other consumables
(i.e. technology, supplies, and materials) required to support the system. Provide the
names, identification numbers, version numbers, release numbers, owners, and any associated maintenance or operational costs.
If the materials needed are site-specific, provide this information in Section 4, Implementation Requirements by Site.] 3.2 Documentation
[This subsection of the Project Implementation Plan lists any additional documentation
needed to support the deliverable system. Include any security or privacy protection
considerations associated with the systems use. If created, make reference to the Software User Documentation Guide for user documentation.] Implementation Plan Template (v1.0) Page 10 of 19
[Insert appropriate disclaimer(s)] <Project Name> 3.3 Personnel
[This subsection of the Project Implementation Plan describes committed and proposed
staffing requirements. Describe the training, if any, to be provided for the implementation staff.]
3.3.1 Staffing Requirements
[This subsection of the Project Implementation Plan describes the number of personnel,
length of time needed, types of skills, skill levels, expertise, and any necessary security
clearances for the staff required during the implementation period. If particular staff
members have been selected or proposed for the implementation, identify their roles
and responsibilities.]
3.3.2 Training of Implementation Staff
[This subsection of the Project Implementation Plan addresses the training, if any, necessary to prepare staff for implementing the system; it does not address user training,
which is the subject of the Software Training Plan.
Describe the type and amount of training required for each of the following areas, if appropriate, for the system: •
•
• System hardware/software installation
System support
System maintenance and modification List the courses that will be provided, a course sequence, and a proposed schedule. If
appropriate, identify which courses particular types of staff should attend by job position
description.
If one or more commercial vendors will provide training, identify them, the course
name(s), and a description of the course content.
If Center staff will provide the training, provide the course name(s) and an outline of the
content of each course. Identify the resources, support materials, and proposed instructors required to teach the course(s).] 3.4 Outstanding Issues
[This subsection of the Project Implementation Plan states any known issues or problems relevant to implementation planning. This section answers the question, “Are there
any specific issues, restrictions, or limitations that must be considered as a part of the
deployment?”
If issues are site-specific, provide this information in Section 4, Implementation Requirements by Site.] Implementation Plan Template (v1.0) Page 11 of 19
[Insert appropriate disclaimer(s)] <Project Name> 3.5 Implementation Impact
[This subsection of the Project Implementation Plan describes how the system’s implementation is expected to impact the network infrastructure, support staff, user community, etc. Include any references to Service Level Agreements which describe the performance requirements, availability, security requirements, expected response times, system backups, expected transaction rates, initial storage requirements with expected
growth rate, as well as help desk support requirements.
If impacts are site-specific, provide this information in Section 4, Implementation Requirements by Site.] 3.6 Performance Monitoring
[This subsection of the Project Implementation Plan describes the performance monitoring tool, techniques and how it will be used to help determine if the implementation is
successful.] 3.7 Configuration Management Interface
[This subsection of the Project Implementation Plan describes Configuration Management, such as when versions will be distributed. Reference the Configuration Management Plan.] 4 Implementation Requirements by Site
[This section of the Project Implementation Plan describes site-specific implementation
requirements and procedures. If requirements and procedures differ by site, provide this
information in an appendix and reference it here.
The "X" in the subsection number should be replaced with a sequenced number beginning with 1. Each subsection with the same value of "X" is associated with the same implementation site. If a complete set of subsections will be associated with each implementation site, then "X" is assigned a new value for each site.] 4.1 Site Name or Identification for Site X
[This subsection of the Project Implementation Plan identifies the site by name, location
and ownership.]
4.1.1 Site Requirements
[This subsection of the Project Implementation Plan defines the requirements that must
be met for the orderly implementation of the system and describes the hardware, software, and facilities requirements for this site.
Any site requirements that do not fall into the following three categories and were not
described in Section 3, Implementation Support, may be described in this subsection, or
other subsections may be added following Facilities Requirements below: • Hardware Requirements -- Describe the hardware requirements necessary to
support the implementation (such as, workstations that will run on a LAN). Implementation Plan Template (v1.0) Page 12 of 19
[Insert appropriate disclaimer(s)] <Project Name> •
Company Scenario:
Marge’s Health Food Store provides organic and raw foods to the local community. According to
Marge, the organization plays a vital role in connecting the community with the products
produced by local farmers and merchants. She states, “We are here to provide a one-stop
shopping experience for community members seeking to eat healthier and learn about and
engage in sustainable lifestyle practices.” Marge wants to be able to offer as many foods and
organic products to the local community as possible. Customers appreciate having variety and
options when shopping for products. She also wants the customer to learn more about the local
farming community and to understand more about the health benefits of the products that she
sells. In the coming year, she wants to offer workshops for community members to attend so
that she can introduce them to different foods, cooking techniques and natural homeopathic
remedies. Ideally, she wants to be able to provide as much information as possible on her Web
site. She also wants to be able to print recipes and health and product information in the store at
the customer’s request. Marge knows that her competition is using technology to meet the
needs of its customers, and she is afraid that she will lose customers to those larger companies.
One of the biggest things that customers emphasize is convenience. They do not want eating
healthy to become difficult to do, especially when it comes to learning more about cooking with
organic foods. Busy lifestyles simply do not permit a significant amount of time to devote to
lifestyle changes.
Marge was told that she must have a database system to manage all of the information that she
needs to keep track of. She was also told that she could use the system to print out literature
and to support her Web site as well. Her financial partner recently broke it down for her and
said, “If you do not improve your sales by at least 5%, I am afraid we will not be able to keep the
store open. If people do not understand your products and related benefits, they will not buy
them. You have got to educate your customers and you need more of them. Even 10% would
work!” Marge knows that she will not be able to improve her bottom line if she cannot manage
her products, customers, and upcoming education workshops. She needs to expand her
inventory of products even more, and she has the opportunity to connect with local producers to
start carrying their products.
Mission Statement: A concise paragraph that details the strategic vision and direction for the
organization
Goal: A list of objective measures used to accomplish the mission of the organization
Critical Success Factors: A list of activities that the organization must be able to engage in to
remain viable as a business or to ensure that a specific project has been successful 1. Determining the mission statement: Why does the organization exist?
Provide a one-stop shopping experience for community members who are seeking to eat healthier and learn about and engage in sustainable lifestyle practices.
2. Determining the goals: What are the objectives of the organization?
a. To increase customer base by 10%
b. To expand product category offerings
c. To make product, health, and recipe information available to customers
d. To increase sales by 5%
3. Determining the critical success factors: What must the organization accomplish to
achieve its mission and goals?
Objective (Goal)
To increase customer base by 10%
To expand product category offerings
To make more product, health, and
recipe information available to customers
To increase sales by 5% Critical Success Factor
To increase customer knowledge about
available products, health, and recipes
Acquire new products from local
suppliers
Acquire a database to support the
information needs of the organization
Attract new customers 4. Determining quantitative and qualitative variables: What will be used to measure the
success of this technology project? Objective (Goal)
To increase customer
base by 10% To expand product
category offerings To make more product,
health, and recipe
information available to
customers Measure Indicator
(Quantitative/Qualitative)
Baseline count of customers
compared to the count of
customers at a specific future
date (Quantitative) Source Customer satisfaction
(Qualitative)
Baseline count of the product
in each category compared to
the count of products in each
category at a specific future
date (Quantitative) Customer satisfaction
survey
Products (Database)
Categories (Database) Customer product satisfaction
(Qualitative)
Baseline count of product,
health, and recipe information
pieces and workshops
available to customers
compared to the count of Customer satisfaction
survey
Recipes (Database)
Articles (Database)
Workshops (Database) Customers (Database) product, health, and recipe
information pieces and
workshops available to
customers at a specific future
date (Quantitative) To increase sales by 5% Customer education
satisfaction (Qualitative)
Baseline sales revenue
compared to sales revenue at
a specific future date
(Quantitative) Customer satisfaction
survey
Orders (Database) 5. Determining the alignment between the solution and the mission and goals: How
will we determine that the technology project solution supports the mission and goals?
Verify that each database source listed above is accounted for and serving its intended
purpose during each phase of the database development life cycle:
a.
b.
c.
d.
e.
f. Establishing Requirements: Do we have stakeholder consensus?
Analysis: Does the system specification represent required system?
Design: How (step-by-step) will the system be constructed?
Implementation: The actual system is constructed as per specification.
Testing: A comparison of actual systems specified in design documents is
made. Discrepancies and errors are thoroughly documented.
Maintenance: Have requirements changed? What added functionality or
solutions do we need?
•
•
• Software Requirements -- Describe any software required to implement the system (such as, software specifically designed for automating the installation
process).
Database Requirements – Describe any databases that a...