IT331
Network Development
Capstone Project
[Onsite]
Credit hours: 4
Contact hours: 50 (30 Theory, 20 Lab)
Prerequisites: Completion of a minimum of 84 credits earned in the
program of study
Network Development Capstone Project
Appendix A—Capstone
Project
Appendix A—Capstone Project
Project Description
Five doctors decide to form a partnership and to consolidate their businesses to leverage
their investments and to provide better service to their patients. Each of the existing five
offices will remain intact. There is one located in the center of the city, one in the north,
another in the south, and the remaining two on the east and west sides. Each of the lead
doctors would like to be able to see their patients at any of the sites, and access any of
their patients’ information from any of the sites. The doctors’ offices can be open 6 to 14
hours per day (7am - 9pm) depending on when the doctors are in.
Currently, all offices are using quite dated personal computers that are not capable of
accommodating certain modern medical insurance and information applications, nor can
they support the processing demand of specific digital images of medical graphics. Dot
matrix printers with proprietary software that date back to 1986 are still used to manage
the patients’ information. These computer systems (hardware as well as software) will
need to be upgraded and the existing data will need to be transferred into the new
computer system.
The office in the center of the city has a local area network (LAN) in the building,
however it will require upgrades in software and hardware as all the equipment including
the server and personal workstations as well as network devices for the LAN are all very
much dated. The upgrades will ensure the system capability and capacity that can
provide a centralized solution to the data storage and management for the new
partnership among all the five offices as well as meeting the additional information and
communications needs for the distributed nature of the new partnership. Therefore, this
office will be the official central office that handles all the data communications for the
entire business. Patient information and major services such as billing and insurance will
be hosted in this location for access by all sites. Currently a Novell 4.5 server is used to
provide the network services (mainly for files, printing, and backup functions) between
the server and all the existing workstations running Windows 98. Currently the entire
building has two PCs in the front, one in the Nurses’ Office, one in the Supervisor Office
shared by the office supervisor and the billing manager.
©ITT Educational Services, Inc.
79
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
Currently, both the East and West offices also have an identical LAN that interconnects
the PCs in a peer-to-peer mode on each site. As the two doctors used to be in some kind
of partnership, they have been using a shared billing and insurance management software
application installed on a low-end SCO Unix machine located in the West office with
directly attached terminals on its site and a remote terminal in the East office connected
through a legacy point to point dedicated circuit. These machines are outdated and need
to be replaced. Recently some work has been done to fix the network connectivity
problems between the two offices in preparation for replacement of the SCO machine and
terminals. It is believed that this fix would allow the network connection between the two
sites to be capable of the Internet services.
Both the North and South offices are equipped with standalone personal computers of
different ages. No networking capability exists within and between the sites. Each site
has a dedicated computer that handles the billing and insurance using a 56K modem.
Each office keeps the record of the patient information and other related data on several
personal computers scattered in the offices, and all patients’ information are manually
filed with the hardcopy printouts the in the old fashion. Each computer in both offices
has a locally attached low-end printer.
Growth expectations
The doctors’ expectations are to grow. By the end of the project, they expect to have
added four doctors and a proportional number of nurses to the staff (for the entire
partnership), as well as an office manager overseeing all the administrative operations of
all offices. They are also planning to sponsor internships for new doctors and nurses.
They are not sure as to the number of interns per year but current thoughts are to limit it
to one of each per quarter.
The doctors have concerns and are in need of guidance regarding technology,
maintenance, upgrades, and warranties. Some thoughts of the future are the use of
wireless laptops and PDA’s for use of viewing records during a patient visit, Voice over
IP phones among offices and possibly to the external to reduce cost in their telephony,
dictation devices so the patient visits are transcribed. They are also not sure when to
upgrade or what hardware/software warranties to have. They are expecting the winning
technology consulting firm will provide a solution that can address their needs with in
such a way that the merger of the five offices can take place without having to slow down
the current service at any location.
Security, Disaster Recovery, Risk Analysis
The doctors are not sure about the security requirements. However, they know they must
provide physical security in addition to complying with the current HIPAA laws.
Currently, the only machine backed up is Novell server in the central office. A backup to
tape is performed once a week. After the backup is completed, the administrative
©ITT Educational Services, Inc.
80
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
assistant takes the tape home with the thought of returning it if it was required. To this
date, they have had a few instances when some certain data must be restored, which
would cause the office at least half a day to get the lost data back. With the new
partnership, all doctors realize this aspect will have to be more effective and efficient.
Additionally, as the management of patient information is going to be centralized, each
site needs to be able to see patients even if the main network connectivity between the
offices are temporarily lost. That means the doctors would like some redundant
connectivity available. They would like to see a solution that will allow access to a
replicated copy of the patient information hosted in a hot standby server located outside
of the central office (in case of any disaster) on the central site.
Network Infrastructure Scope
The scope is to design an infrastructure that connects each remote office to the central
office that will meet all stated requirements on the integrity, storage and movement of
related data and the applications that process such data, and the networking and
communications infrastructure that supports such applications covering all desired
functions in security, redundancy and operability, etc. The office computers, servers and
all network related equipment need to be upgraded to meet the requirements as well.
Workstations from all sites will need to be connected to the Internet all the time for
research and Web-based applications. The new partnership is also seeking professional
guidance and procedures on whether it makes sense to hire a full-time staff to manage the
networking/telecommunications infrastructure and related services, or if leaving such
services to an external consulting firm will be more effective and efficient.
Each office will have its own local area network (LAN) with an operating speed that will
permit data transfer at high speeds with minimum chance of bottlenecks. The doctors
need to know if it would be best to have the data accessed by all offices be on its own
LAN. As of today, data sharing among workstations is minimal, nor is dedicated high
speed Internet access available at any site.
Office and Building Dimensions
The main part of the new partnership is to upgrade their office building with the same
type of structure and functions. Each office building is 92’ wide x 66’ deep. The height
from floor to false ceiling is 10’. The height from the false ceiling to the roof is another
4’. The passageways are four feet wide. The rooms are equal in width. The length of the
rooms is the same in most cases. In the central office the print room is six feet in length,
storage is 20 feet in length, and the IT/Telecom Room is 16 feet in length.
Each remote office will have the following:
ƒ
ƒ
ƒ
ƒ
One file/print server
Two high speed network printers/copiers/scanners
Fax machine
Voice Messaging with beeping services
©ITT Educational Services, Inc.
81
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
ƒ Ten workstations on each location, with one at the front desk for the receptionist, one
dedicted to the Billing person, one dedicated to the insurance claims staff, one station
for the patient records staff, one station for the doctor, and all the rest are for nurses,
interns and potential growth.
ƒ At any time, at least one doctor and one nurse must be at each location for at least 6
hours (but could be as long as 14 hours). Phone calls into the office to a specific
doctor will be routed to doctors in other offices when the specific office is not open.
Each doctor and nurse will have a separate workstation.
ƒ There must be connections for laptops used by the billing manager and the office
manager when visiting the remote office.
ƒ Network devices that support the LAN and WAN connection – router, firewall, switch
The main office will have the following:
ƒ The same list as each remote office
ƒ An application server hosting the Medical Manager Software installed to track all their
patients, demographics, insurance, and bills
ƒ A separate server that host business management applications such as accounting, HR,
and other assets management tools
ƒ A separate server that provides necessary network services such as Active Directory,
DNS, and DHCP
ƒ A Web server for the business
ƒ Network connection – router, firewall, switch
ƒ Email service is to be provided by an external provider and is accessible via email
client software and/or Web access
ƒ One file/print server
ƒ Three network printers/copiers/scanners
ƒ A separate station for each nurse which is to grow to three
ƒ A separate station for each doctor which is to grow to three
ƒ One station for the office manager
Software per Workstations
ƒ
ƒ
ƒ
ƒ
Microsoft (MS) Office
Email client software
Web browser
Network connectivity to centralized patient information, billing and insurance claim
applications, and the Internet
Deliverables
Your task is to identify the equipment required at each office, the LAN and WAN design
that will provide information and communications services for the new partnership with
all necessary security and disaster planning to meet HIPAA requirements at a reasonable
cost.
©ITT Educational Services, Inc.
82
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
Documentation
o
o
o
o
o
o
o
o
o
Document briefly summarizing the problems and proposed solutions for each of the
problem; Each solution must be backed up with sound justification
Diagrams for all the LAN and WAN solutions
Document detailing all proposed equipment with cost
Document detailing configurations of each equipment
Document detailing all proposed software with cost
Document detailing all require services (from external provider) with cost
Document detailing the planning, implementation and maintenance of the project
(project management)
Document detailing user training information
Document detailing the technical solution to the client
Timeline
o
o
Timeline 1 – project response
Timeline 2 – install, implement, test, and training
Timeline 1
In the timelines, the milestones may differ from the deliverables. The first timeline is
to show the tasks, resources, milestones, and time required for the development of the
project. Items to be included are the requirements analysis, network diagram,
equipment selection, cost analysis, disaster recovery, and the second timeline creation.
This will need to be presented and explained to the doctors, office manager, and
billing manager prior to the implementation of the second timeline.
Timeline 2
The second timeline is to represent the tasks, resources, milestones for the installation,
configuration, implementation, testing, and training in the use of the equipment and
software.
Network diagrams: Existing and Proposed
The network diagram will depict the network and components of each office as well as
the connectivity between the offices and within the offices. Label the components,
include their IP addresses, and identify their uses. Basic floor plans have been
provided showing the rooms, sizes, and the locations.
Equipment selection and cost analysis
Research will need to occur to obtain prices of the equipment and the specifications.
Include connectivity capabilities and the redundancy capabilities. Software suggested
for use is MS Excel. The preparer can list each piece of equipment, quantity, and
value. There are columns for each item. As a suggestion, the equipment can be
grouped via office or equipment type.
©ITT Educational Services, Inc.
83
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
Security, Disaster Recovery, and Risk Analysis
This area will be used to discuss redundancy, disaster recovery, backups, and how
security will exist and be maintained. In addition, in this area risk analysis is to be
discussed. A definition for disaster recovery is: if something breaks a plan exists
outlining how to repair it. For risk analysis, a determination will need to be made
outlining what requires attention first and with how much priority if multiple items are
broken. The thought is to determine which failure would cause the most expense or
damage to the business. Another item to review is the time required to repair.
Regarding security, identify how the data and resources housing the data will be
protected from unauthorized entry.
Presentation to Doctors
Use Microsoft Power point to discuss the various deliverables and highlights of the
project. Utilize the previous deliverables during the presentation if detailed questions
occur and require references.
©ITT Educational Services, Inc.
84
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
Office Floor Plan
Room 1
Room 2
Room 3
Room 4
Room 6
Room 7
Room 8
Restroom
Restroom
Laundry
Nurses
Room 5
Supervisor
Doctor 3
Billing /
Collection
Conference / Break Room
Doctor 2
Fax
Copier
Network Printer
Chart Room
Doctor 1
Storage
Copier
network printer
Financial
Manager
Manager
IT/Telcom
Rack
Reception area
Restroom
Server
Server
Central Office
PROPOSAL EVALUATION
Evaluation Procedures
The class instructor and an evaluation team comprising the school’s advisory board
members will evaluate each proposal.
The evaluators will consider how well each project team's proposed solution meets the
needs of the client. The proposed solutions should be clear and complete to enable the
evaluators to understand all aspects of each proposal. The evaluation process is not
designed to simply award the contract to the lowest cost vendor. The aim is to help the
client select a project team that provides the best combination of attributes, technical
expertise, and pricing, based on the defined evaluation factors.
The evaluation criteria for the capstone project proposal are:
CATEGORY
©ITT Educational Services, Inc.
WEIGHT
85
Date: 11/16/2009
Network Development Capstone Project
Team Project
• Documentation
• Teamwork
• Presentation
• Network Solution
Appendix A—Capstone
Project
20%
10%
10%
45%
Teams will receive a score of zero to 100 for each evaluation criterion. Criteria weights
correspond to points. Refer to the student syllabus for categories and assigned
percentages. For a specific evaluation criterion, the proposal with the highest raw score
receives the maximum points; other scores receive a fraction of the points based on the
ratio of their scores to the highest raw score. Each team’s total score is the sum of the
weighted scores.
The final decision of the panel – the instructor and the participating advisory board
committee members will serve as the client representing the doctors’ group described in
the Capstone Project – based on the scoring process. The other factors that influence the
final decision are customer references, financial stability, and the willingness of the
apparently successful vendor to agree to the client’s contractual requirements.
List of Deliverables:
The deliverables for this course consist of:
1. Project Documentation
Use the information and knowledge gained from flowcharting, GANTT charting, and
project planning to prepare, submit, and present the proposed solution for the client.
Using the project management approach to project planning, prepare a detailed project,
simulating all of the information and tools learned throughout the program. This project
is to be prepared and printed using but not limited to Microsoft Office Project software
and Microsoft Word.
1. The scope document and project charter.
ƒ The definition of the problem or need
ƒ The definition of the project’s goals and objectives—aligning the
IT strategy to the business value
ƒ The project plan
ƒ The definition of the resources needed to complete the project
ƒ A cost analysis matrix that indicates how much the project will
cost
ƒ A payment plan that explains how the client will pay for the
services
2. A prototype of the system design—solution. Create a requirements document to
address the Connectivity Design Recommendations for the proposed LAN/WAN
system.
©ITT Educational Services, Inc.
86
Date: 11/16/2009
Network Development Capstone Project
ƒ
ƒ
ƒ
Appendix A—Capstone
Project
Detailed network drawings utilizing a network diagramming tool
such as Microsoft Visio:
• Physical: List all network devices and endpoints
• Logical: IP network diagram—data flow—per location
(LANs)
Additional drawings to include:
• Cable run table
• Office floor plans
• Equipment power requirements
• Wiring
The Security/Maintenance Plan: The top priorities must include:
• Intruder deterrence
• Theft prevention
• Disaster prevention
• Internal security and confidentiality
3. Test and quality assurance (QA) plans. Provide an outline of the QA/Quality
Control (QC) activities that will be implemented during the installation of the
proposed systems.
4. A change management plan. Ensure that the plan addresses ways to reduce the
risk of project failure by describing how to lessen the impact when there is a
change in technology:
ƒ Redeployment of systems—software and hardware
ƒ Retraining of the organization’s personnel—displaced after the
internal transfer process
ƒ Communication strategy—how changes will be communicated to
the organization’s workforce
5. A Work Breakdown Structure (WBS) for the team.
6. A training plan. This plan can include:
ƒ Introduction
ƒ Training approach
ƒ Schedule
ƒ Evaluation
ƒ Tracking and reporting
ƒ Outcome measurement
ƒ Assumptions
ƒ Risks
7. An implementation plan.
8. A post-implementation plan.
9. A disaster recovery plan.
Preferred Documentation Style
The entire documentation should be printed on an 8.5-by-11-inch, or letter-size, paper
with margins of 1 inch on all sides. The text should be single-spaced. Use the Arial
Narrow font—font size 12 point.
©ITT Educational Services, Inc.
87
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
All references must follow the American Psychological Association (APA) style.
Special note: When editors or teachers ask you to write in the "APA style," they do not
mean the writing style. They refer to the editorial style that many social and behavioral
sciences have adopted to present written material.
©ITT Educational Services, Inc.
88
Date: 11/16/2009
Network Development Capstone Project
2.
Appendix A—Capstone
Project
Network Solution
From a hands-on perspective and an application approach, incorporate the available
LAN/WAN equipment in the network diagram that must be created using network
diagramming tool Microsoft Visio. You may retrieve a copy of the software from your
instructor. In addition to the Physical Simulated Network diagrams along with a
minimum of five hard disk drives from each team, every team must successfully
complete and present the following:
o A site LAN logical topology with an IP Addressing Scheme
o Site WAN and LAN diagrams depicting the conceptual, logical, and physical
views of the proposed systems for each location specified within the RFP
o A systems requirements document detailing the connectivity strategy for LAN
and WAN:
• Protocols
• Hardware
• Software
• Implementation and post-implementation procedures
• WAN diagrams
o Physical topology
o Logical diagram with an IP addressing scheme
o A prototype environment of the following equipment:
ƒ An installed and configured Windows 2003 server with running Active
Directory.
ƒ An installed and configured Web and FTP server (IIS) function
ƒ An installed and configured Red Hat LINUX server
ƒ A minimum of two installed and configured Windows XP
workstations
ƒ An intranet home page, posted on the Web server, that reflects the
client’s products and services.
ƒ A database using Microsoft Access or SQL
Every team will utilize the preconfigured templates to document all network services,
such as routers, switches, servers, and computers. Each team is responsible for creating
its own class of IP addresses along with the appropriate number of subnets. You need to
also create a diagram to complete the Point to Point Protocol (PPP) and simulate the
Integrated Services Digital Network (ISDN) and Frame Relay implementation. Based on
this physical simulated network diagram—not the teams’ theoretical designs from the
RFP—the following WAN/LAN specifications must be successfully completed and are
subject to the instructor’s verification:
o Connectivity to and from any node in the LANs and the WAN, including all
servers
o No TELNET allowed from any nodes in all LANs to the core routers
o No TELNET allowed from any nodes on the networks to any routers
o The ability to transfer a text or document file from any node on the network to
the FTP server
©ITT Educational Services, Inc.
89
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
o The ability to download, from any node on the network, a driver file from the
FTP and Web servers
3.
Class Presentation and Walkthrough
Each team will present the final project in Unit 11. All the team members must
participate in the final presentation. The members should be able to discuss their
solutions with the instructor and the rest of the class before submitting the final project.
A walk-through is a semiformal presentation/evaluation of a product at its appropriate
development stage for the purpose of finding errors in the product.
©ITT Educational Services, Inc.
90
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
Suggested Templates
This section contains sample templates that you may use or modify according to your
project requirements.
©ITT Educational Services, Inc.
91
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
Required Cover Page for the Completed Project Documents
PROJECT TITLE
SUBTITLE (if applicable)
A COMPREHENSIVE NETWORK DEVELOPMENT PROJECT
SUBMITTED TO THE
IT/COMPUTER NETWORK SYSTEMS PROGRAM
IN PARTIAL FULFILLMENT OF THE REQUIREMENTS
FOR THE ASSOCIATE DEGREE
by
STUDENT NAME
STUDENT NAME 2 (if applicable)
STUDENT NAME 3 (if applicable)
STUDENT NAME 4 (if applicable)
STUDENT NAME 5 (if applicable)
ADVISOR — NAME(S) OF THE FACULTY
ITT TECHNICAL INSTITUTE
CITY, STATE
MONTH, YEAR (Format: DECEMBER, 2007)
©ITT Educational Services, Inc.
92
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
Team Meeting Agenda
Meeting Title
Minutes
Meeting Date
Time
Location
TYPE OF
MEETING
FACILITATOR
NOTE TAKER
TIMEKEEPER
ATTENDEES
Agenda Topics
Allotted Time
Agenda Topic
Presenter
DISCUSSION
CONCLUSIONS
PERSON
RESPONSIBLE
ACTION ITEMS
©ITT Educational Services, Inc.
93
DEADLIN
E
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
Scope Document and Project Charter
1. Purpose
Address the “how, when, where, and why” questions that clarify or support a project.
This section summarizes the rationale for the solution. Provide a description of the
situation that leads to the recognition that this solution should be built.
2. Goals and Objectives
Specify clear, reachable steps of action. The objectives must answer the “how, when,
where, and why” questions. Describe the important business objectives of the solution in
a way that is quantitative and measurable.
3. Success Criteria
Specify the desired performance related to a project and the desired outcome. Determine
how success will be defined and measured on this project, and describe the factors that
are likely to have the greatest impact on achieving that success. Include external factors
and factors within the direct control of the organization.
4. Project Context
Describe the project’s alignment with the company goals and mission.
5. Project Deliverables
Explain how dependencies will influence the project.
6. Scope Specifications
Provide a high-level breakdown of the goals and objectives of the project. The project
scope defines the concept and range of the proposed solution.
7. Out-of-Scope Specifications
Mention the tasks or issues not related to the project. It is important to define what will
not be included in the product. Stakeholders establish realistic expectations based on the
scope and limitations.
8. Assumptions
Record any assumptions you make when starting the project and writing the vision and
scope document. Note any major dependencies—such as technologies, development
partners, or other business relationships—that will influence the project’s success.
©ITT Educational Services, Inc.
94
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
9. Constraints
Identify any resources—human and nonhuman—that will prevent the project from
completion.
10. Risks
Summarize any unforeseen events that might derail the project. List the major business
risks associated with developing this product, such as marketplace competition, user
acceptance, or implementation issues. It would be a good idea to estimate the severity of
the risks and identify risk mitigation actions that can be taken.
11. Stakeholders
Mention the organization departments involved in the project process. These departments
are either affected by the outcome of the project or can influence the outcome.
12. Recommended Project Approach
Describe the strategies, methodologies, and technologies to be used to complete the
project.
13. Cost Matrix
It is imperative to incorporate the principle of cost management when implementing a
project. In this section, each team member will create a cost matrix and submit it to the
project manager for approval and inclusion in the budget of the project. The following
table can be used to create the cost matrix.
Description of
the Item
Function of the Location of the
Item to the
Item
Project
©ITT Educational Services, Inc.
95
Quantity
Price
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
Security/Maintenance Plan
1. Introduction and Background
Provide a high-level description of the product or services to be maintained and secured
in the scope of maintenance and security operations activities.
2. Budget
Identify the budget associated with the security and maintenance of operations activities.
3. Roles and Responsibilities
Identify the roles and responsibilities associated with maintenance and security
operations and the skill set needed to perform these roles. The key roles to be identified
include the primary business contact, maintenance and security operations team leads,
key technical staff, customer or help desk support, documentation, training, and other
support staff.
3. Performance Measures and Reporting
Identify the key performance measures for maintenance activities and security operations
for product or service performance. Include information on:
o How measures will be captured and reported
o How security will be monitored and reported
4. Governance and Management/Security Approach
Identify new methodologies or reference the existing ones to establish maintenance and
security priorities and other change management strategies.
5. Customer/Business Owner Management and Security
Describe how the stakeholders and customers will be involved in or informed about
maintenance and security operations activities. Describe the key stakeholders and
methods of communication, where known.
6. Standard Operation and Business Practices
Identify or reference the methodologies, processes, strategies, and tools used for change
control and configuration management, problem report management, customer support,
lifecycle testing, risk identification and mitigation, data sharing, storage, disaster
recovery, and security.
©ITT Educational Services, Inc.
96
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
7. Documentation Strategies
Describe new documentation standards and expectations or reference the existing ones.
Include descriptions of documentation that will be routinely produced such as
product/service documentation; reports; and user, usage, problem, and change
information. Include details on where documentation is stored and how to access it.
8. Training
Describe the ongoing training activities.
9. Security
Describe the ongoing security activities.
10. Acceptance
Define the point at which the project and maintenance staff agrees that implementation
and transition activities are complete and maintenance activities may begin.
©ITT Educational Services, Inc.
97
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
Quality Assurance Plan
This section contains a checklist to conduct the evaluation process for the Quality
Assurance Plan. The checklist assists designated reviewers on the project team in
determining whether the project specifications meet the criteria established in the Project
Plan. The objective of the evaluation is to determine whether the document complies with
the client’s RFP requirements.
Requirement
To be Completed by Team
To be Completed by
Reviewer
Performed
by
Comply
Comments
Y
N
SCHEDULE OF TASKS AND RESPONSIBILITIES
Based on the tasks described in your
Project Plan, provide a schedule of
the QA activities for the duration of
the project. The tasks may include:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Identifying standards and
guidelines
Evaluating software tools
Evaluating facilities
Evaluating the software
products review process
Evaluating project planning,
tracking, and oversight
processes
Evaluating the requirements
analysis process
Evaluating the design process
Evaluating the code and unit
testing process
Evaluating the integration
testing process
Evaluating the acceptance
testing process
Evaluating the release process
Evaluating the corrective
action process
Evaluating the media
certification process
Certifying nondeliverable
software
©ITT Educational Services, Inc.
98
Date: 11/16/2009
Reviewer
Comments
Network Development Capstone Project
Appendix A—Capstone
Project
Requirement
To be Completed by Team
To be Completed by
Reviewer
Performed
by
Comply
Comments
Y
•
•
•
•
•
N
Evaluating the storage and
handling process
Evaluating the configuration
management process
Evaluating software
development
Performing configuration
audits
Evaluating the risk
management process
SYSTEM DOCUMENTATION
Documents by Phase: List and
briefly describe the documentation
expected to be produced during this
project. Depending on the size of
your project, the list may include, but
is not limited to, the documents in the
following subsections:
Initiate Phase:
•
Needs statement
•
Project plan, including WBS
•
Configuration management
plan
•
Quality assurance plan
•
Feasibility study
•
Cost/benefit analysis
©ITT Educational Services, Inc.
99
Date: 11/16/2009
Reviewer
Comments
Network Development Capstone Project
Appendix A—Capstone
Project
Requirement
To be Completed by Team
To be Completed by
Reviewer
Performed
by
Comply
Comments
Y
N
Risk Analysis
Define Phase:
•
System support and
acquisition plan—initial
•
Functional requirements
document
•
Data requirements
document
•
System security and privacy
plan
•
Internal audit plan
•
Project plan—updated
Design Phase:
•
System/subsystem
specifications
•
Database specifications
•
Program specifications
•
System support and
acquisition plan—final
•
Validation, verification, and
testing plan—initial
•
Training plan—initial
•
Project plan—updated
Build Phase:
• Installation and conversion
plan —initial
• Test plan
• User’s manual
• Operations manual
• Maintenance manual
• Validation, verification, and
testing plan—final
• Training plan—final
• Project plan—updated
Evaluate Phase:
• Test results and evaluation
reports
• Installation and conversion
plan —final
©ITT Educational Services, Inc.
100
Date: 11/16/2009
Reviewer
Comments
Network Development Capstone Project
Appendix A—Capstone
Project
Requirement
To be Completed by Team
To be Completed by
Reviewer
Performed
by
Comply
Comments
Y
N
• Project plan—updated
Operate Phase:
• Pilot test results
• Training material
• Project plan—updated
Discipline for Documentation
Standard Practices: Describe the
criteria that will be applied to review
and evaluate all lifecycle documents.
©ITT Educational Services, Inc.
101
Date: 11/16/2009
Reviewer
Comments
Network Development Capstone Project
Appendix A—Capstone
Project
Test Plan
<Project Name>
<Month, Year>
A. Introduction
A.1. Purpose
Describe the purpose of the Test Plan.
A.2. System Overview
Provide a brief system overview description as a point of reference for the remainder of
the document.
B. Test Analysis
Identify the tests being conducted and describe each test in brief.
B.1. Security Considerations
Describe the security requirements built into the system and verified during system
acceptance testing. Identify and describe the security issues or weaknesses discovered
during the testing.
B.2. Test # Test <name>
Provide a test name and identifier (#) for reference in the remainder of the section.
Identify the functions that are tested—later, reports on these tests are prepared. Include
the following information when recording the results of a test:
o
o
o
o
o
o
The name and version number of the application or document tested
The input data used in the test
The hardware and operating systems on which the test was run
The time, date, and location of the test
Names of the team members involved in the test
The output data, with detailed descriptions of any deviations from the expected
results
B.3. Test # Requirements to be Tested
Describe the system and program requirements that will be tested using this particular
test.
©ITT Educational Services, Inc.
102
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
B.4. Test # Expected Outcome
Describe or depict the expected result of each test.
B.5. Test # Functional Capability
Describe the functional capability the way it has been demonstrated. Assess the manner
in which the test environment may be different from the operational environment and the
effect of this difference on the capability.
B.6. Test # Performance
Quantitatively compare the performance characteristics of the system with the
requirements stated in the scope document.
B.7. Test # Data Handling
Describe how you will identify, maintain, and control versions of the test data.
B.8. Test # Constraints
Describe any anticipated limitations imposed on the test because of system or test
conditions such as timing, interfaces, equipment, and personnel.
C. Summary
C.1. Demonstrated Capability
Provide a statement on the capability of the system as demonstrated by the test, compared
with the requirements and security considerations.
C.2. System Deficiencies
Provide an individual statement for each deficiency discovered during the testing.
C.3. Recommended Improvements
Explain any recommendation—following the testing—to improve the system, its
performance, or related procedures. Include any additional functionality seen as a
potential improvement for the user even if the functionality is not specified in the
requirements document.
C.4. System Acceptance
State whether the testing has shown that the system is ready for release testing and
subsequent production operation.
©ITT Educational Services, Inc.
103
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
Training Plan
<Project Name>
<Month, Year>
1. Introduction
1.1. Purpose
Describe the purpose of the Training Plan.
1.2. Scope
Describe the scope of the Training Plan as it relates to the project.
1.3. System Overview
Provide a brief system overview description as a point of reference for the remainder of
the document.
1.4. General Training Prerequisites
Summarize the general training prerequisites for each type of training mentioned in this
plan.
2. Training Approach
2.1. Training Requirements
Describe or list the skills required to support the project lifecycle activities. Match the
requirements to the existing team skill sets to determine the training needed for the
project.
2.2. Roles and Responsibilities
Identify the team members and their responsibilities in developing the training materials.
Identify who will conduct the training.
2.3. Techniques and Tools
Describe the training techniques to be used. These techniques may include computerbased instructions, self-paced written manuals, peer training, hands-on practical sessions,
classroom lectures, or any combination of these techniques.
Identify the tools needed for the training, such as online terminals or PC workstations,
training manuals, classroom facilities, and any computer center resources.
©ITT Educational Services, Inc.
104
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
2.4. Training Prerequisites
Identify any prerequisites for individuals to receive training. Develop a strategy regarding
prerequisite training.
2.5. Schedule
Prepare a training schedule to include information such as identification and development
of course content and materials, training dates, and post-training reporting.
3. Curriculum
Briefly describe the curriculum for each proposed training class or attach the course
description from the vendor.
Course
Audience
Message
Method
When/How
Responsible
Title/Offering
Often
Identify the
Name the
Identify the Identify the Identify the
Identify the
organization’s job roles
type of
product or
date of
person
service.
staff.
that require training,
training and
responsible for
training.
such as
the number of conducting the
hands-on
times the
training
workshops
training will
sessions—
and
take place.
external
seminars.
consultants or inhouse technical
training staff.
4. Evaluation
What method of evaluation is being used to determine the success of the overall plan?
How often will the evaluation occur? Calculate the Return On Investment to determine
whether the client is receiving his or her money for implanting this process within the
project.
5. Tracking and Reporting:
How will the education, training, drills, and exercises included in the plan be tracked and
reported?
©ITT Educational Services, Inc.
105
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
6. Outcome Measurement:
What is the expected overall outcome of the plan?
7. Sustainability:
Describe how the training plan will be sustained. How often will assessments be done
and the plan reviewed and evaluated?
8. Assumptions:
What assumptions have you made in the development of the training plan?
9. Risks:
What risks or barriers exist to the implementation, execution, and sustainability of the
training plan?
©ITT Educational Services, Inc.
106
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
Implementation Plan
A. Introduction
A.1. Purpose
Describe the purpose of the Implementation Plan.
A.2. System Overview
Provide a brief system overview description as a point of reference for the remainder of
the document.
B. Implementation Plan
B.1. Implementation activities
Describe the actions, or outcomes, of the implementation and how these actions will
achieve the objectives.
B.2. Implementation Timetable
The project will commence on [dd/mm/yyyy]. Its duration will be [insert duration].
Recommended
Actions
Identify the
task to be
completed—
server
installation or
server patch.
Technological System Implementation Plan
Specific
Lead
Support
Key
MileAction
Outputs
stones
Actions
Achieved
by
Describe
Identify
Identify Provide the Identify
Identify
how the
the person who
details of
whether
the person
action will or persons will
the
the task
on the
be
on the
continue outcomes
is a
project
performed. project
to
of the task
milestone team
team
support to be
to a
responsible
responsible the
completed
specific
for
for leading process. and the
phase of carrying
this task.
results if
the
out the
the task was project.
task.
successfully
completed.
©ITT Educational Services, Inc.
107
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
B.3. Standards Implementation
Consider all the protocols and Industry Standard committees and practices. Explain how
they are implemented; for example, explain how the Open Systems Interconnection (OSI)
model created by the International Organization for Standardization (ISO) group and
Institute of Electrical and Electronics Engineers (IEEE) org Electronic Industries Alliance
- Telecommunication Industry Association (EIA-TIA) wiring standards was
implemented. In addition, discuss the impact of nonconformance with industry standards
and protocols.
C. Technological Infrastructure
Identify and describe the technology infrastructure and changes that are expected as a
result of the project.
•
What infrastructure is required?
•
How will it be implemented?
•
What architecture is being used?
•
What is the time schedule for implementation?
•
Who will it affect?
Include the physical and logical drawings of LAN and WAN.
©ITT Educational Services, Inc.
108
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
Post-Implementation Plan
A. Executive Summary
Summarize the project.
B. Results
B.1. Schedule
Projected
Note the anticipated start and end dates of the project, as proposed in the project
charter.
Actual
Note the actual start and end dates of the project.
Reasons for Variance
If there is a variance between the projected and actual schedules, describe the key
reasons for the variance.
B.2. Costs
Projected
Note the anticipated project costs, as per the project charter.
Actual
Note the actual project costs.
Reasons for Variance
If there is a variance between the projected costs and the actual costs, describe the
key reasons for the variance.
B.3. Goals and Objectives
Projected
Note the project goals and objectives outlined in the project charter.
Actual
Describe the objectives achieved from the project and progress toward the goals.
©ITT Educational Services, Inc.
109
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
Reasons for Variance
If there is a variance between the projected goals and objectives and the actual
results, describe the key reasons for the variance. Discuss the impact of delayed
measurement or evaluation, mentioned earlier.
B.4. Requirements and Functionality
Projected
Note the functionality proposed in the project planning materials and key
requirements documentation.
Actual
Note how the functionality delivered meets the requirements.
Reasons for Variance
If there is a variance between the projected and actual functionality, describe the
key reasons for the variance. If there is a variance between the documented
requirements and the delivered functionality, describe the key reasons for the
variance.
B.5. Benefits
Projected
Note the benefits anticipated at the beginning of the project.
Actual
Note the benefits realized or projected as a result of the project.
Reasons for Variance
If there is a variance between the anticipated and actual benefits, describe the key
reasons for the variance.
C. Lessons Learned
Provide the information obtained from the Lessons Learned exercise. The following are
the commonly cited lesson categories. You can modify the following list based on the
lessons learned information reported for your project.
Vendor Solicitation and Selection
Contract Negotiation and Management
Technology
Project Management
©ITT Educational Services, Inc.
110
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
Communications Plan
Technical Design Specifications
Data Conversion
Testing
Training
Implementation
Production and Operations
D. Recommendations
Based on the lessons learned from the project, describe the recommendations that the
project team has for future or similar projects.
©ITT Educational Services, Inc.
111
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
Disaster Recovery Plan
Purpose
This document describes how to plan for, record, and recover from a disaster. This plan
will assist you in gathering specific information relevant in the different stages of a
disaster. The plan also outlines the measures that organizations should take to prepare for
a disaster of any magnitude.
1. Operations
Use the following charts and guidelines to identify the technology and personnel required
to keep your operations going in the aftermath of a disaster.
Technology Priorities Assessment
Use the following chart to identify the key applications required to keep your
organization running over the next 24 hours, the next three days, and the next
week.
Office
Division (Such as Development,
Finance)
Application
Workstation/ Server
ID
Finance
PeaceTree
Spica
San Jose
Clinic
Technology Refresh: Key Recovery Staff
Assuming all the staff is available, the following table helps you to identify the
key personnel required to recover your systems and the location from where these
systems will be recovered.
Service Type Assigned Personnel
Location
System Profile
For each system configured, you must complete a comprehensive analysis to
determine how critical the system is to the organization.
Location Division Workstation Critical
Fixed
Manufactu Needed Needed
(Such as
/ Server ID Yes/No
Assets
rer
Within Within
Developm
Yes/No
24
1–3
ent,
Hours
Days
Finance)
©ITT Educational Services, Inc.
112
Date: 11/16/2009
Needed
Within
1
Week
Network Development Capstone Project
Appendix A—Capstone
Project
2. Communications
Use the following forms to keep track of the contacts you will need during
recovery.
Technology Recovery Contacts
Name
Role
(Such as
Network,
Database,
Systems)
Address
Type of Vendor
(Consultant, Firm,
Corporation)
Contact Information
(Phone Number, IM,
Skype, Address)
Internal Escalation Contact List
Name Role During Recovery Location Job Scope Phone Number
3. Business Impact Assessment
Business Process
What are the business processes performed by each of your departments? Name
and briefly describe each business process.
©ITT Educational Services, Inc.
113
Date: 11/16/2009
Network Development Capstone Project
Appendix A—Capstone
Project
Business Unit Information
This chart can be used to record the functions of each business unit in your
organization. You can keep it in a known repository at the recovery site for
reference.
OVERVIEW OF THE BUSINESS UNIT
Location:
Main Constituency (if internal, state “Internal”):
Organizational Focus:
Departmental Function:
Recovery Objectives:
Number of Employees:
Consequences of Not Performing a Function
Under the following headings, indicate your assessment of the business impact of
not performing a function following a major incident or disaster.
Potential Impact
Estimate the potential impact if a function is not performed following a disaster.
Operations Immediacy
(Such as in the next three
days or next week)
©ITT Educational Services, Inc.
114
Potential
Impact
Assumptions and
Justification
Date: 11/16/2009