DICE
Evaluation Plan
DICE will be evaluated comprehensively in order to ensure a complete and robust
product that will be destined for success. The individual phases of the project, as well as
the project as a whole will be evaluated based on specific criteria. The testing and
evaluation periods of the project are outlined in the WBS. Although we have
documented and placed these items on the project timeline, we have recognized the need
to be flexible and “take a step back” to look at the project to ensure we are reasonable and
complete with our efforts. As noted in the WBS, all phases will be considered complete
when the tasks that are associated within the phase are successful and this success is
documented. Below, you will see a conceptual diagram of our evaluation strategy for
DICE.
Technical
Marketing
Hardware
Scope
Software
Customer
Phase 0
Interoperability
Niche
Phase III
Evaluation
Of
DICE
Phase I
Phase II
Management
Cost
Scope
Financial
Personnel
Risks
Administrative
Each phase will be evaluated based on the evaluation checklist for that phase.
Evaluation will occur every 3 months or as deemed necessary by the PM. The evaluation
checklist consists of four identification points. They are as follows:

Marketing: the current target customers, the scope of this market audience and
an updated list of competitors will be validated.

Management: scheduling, task breakdown analysis, application of human
resources, and overall project scope is included in this evaluation identification
point.

Technical: the components of the software, hardware, interfaces and overall
system will be evaluated for completion, testing, and interoperability.

Cost: the scheduled budget for the current phase will be evaluated for cost
efficiency, funding allocation, and mitigation/impacts of potential risks.
Marketing
The identification of customers, market share, and competition helps to mold how
the product will eventually look. In order for user acceptance to occur, the market must
be explored for consistency or for changes in trends.
Success is when the following are obtained:
Customer base is clearly and accurately defined
Documentation is update on competitive threats
Management
The DICE team is driven by upholding professionalism amongst its team
members. The team will strive to become a performing team as quickly as possible, as
well as to maintain this performing status. This will require oversight and insight from
the team leader and constant positive communication amongst the team members.
Viewpoints and ideas are to be respected and discussed with only constructive criticism.
On an aggressive project like DICE, negativity is the breeding ground for failure.
Success is when the following are obtained:
Collaboration is the leading factor in discussions
Open, Honest, and Direct Communication is present
Each members’ contributions are satisfactory
Schedule for meetings clearly articulated
Every meeting is documented
Cost
One of the largest driving factors of all projects is the bottom line (how much will
it cost and how much will I profit from it). Each phase of the project hinges on the
funding and the wise spending of this funding. Truly, the only successful way to migrate
into the next phase of the project and to achieve success of the outlined goals in the WBS
is to be sensitive to the cost. The break even points for the business and its sustainability
must be monitored by all team members. Forecasting, budgeting, and reconciliations will
all prove critical tools in this indication point.
Success is when the following are obtained:
Budget that meets the SBIR funding allocated
Budget broken down by phase and reviewed periodically
Breakeven point is documented and realized
Technical
There are four components in determining the technical success of the project:
hardware, software, interfaces and overall system integration.
Software:
Software will be managed and evaluated under the Capability Maturity Model
Integration (CMMI: http://www.sei.cmu.edu/cmmi/cmmi.html).
Testing will be performed whenever new features are added to ensure
functionality. Integration testing will be performed at every level of development.
Hardware:
The hardware to be used will undergo exhaustive testing (if it performs well under
a heavy load, then other states will be non-issues). The network infrastructure
will be also tested to determine sufficiency of bandwidth.
Interfaces:
The interfaces are the key aspect to creating the community on DICE. With our
first instantiation to be housed at ODU, we must successfully create the tie in to
their SIS, which is Banner. Other schools will have different SISes that will need
to be accounted for. By creating a model for the Banner information pull, these
principles and data elements will be examined and documented for future
implementations.
System:
The system will be tested to ensure that the software and hardware components
work together seamlessly to provide a quality product. Rigorous in-house testing
will be performed on a regular basis and in fact may encapsulate both the
hardware and software testing once both facets of the project are sufficiently
complete.
Success is when the following are obtained:
 Functioning GUI prototype
 Functional interface with Enrollment Database
 Functional hooks to enterprise level databases
 Documentation of interoperability components are published
 Functional integration of hardware and software
 Technical documentation for software and hardware
Testing Defined
The DICE project is going to be taking a unique approach to testing. There are three
identification points that must be evaluated by an expert on the team. These are outline
in the WBS and listed below:

Marketing: Marketing Director

Management: Project Manager and Operations Manager

Cost: Financial Director and Risk Manager
It should be noted that the Technical testing and evaluation are missing from the
above list. This is where the uniqueness of DICE’s evaluation plan comes into being. As
contained in our WBS, DICE is gong to hire 1 testing technician in Phase 1. This
individual will eventually become the lead DICE expert in the technical realm. We will
hire another testing technician in Phase 2 and will continue with the two technician
approach throughout the project. When we have achieved success and are experiencing
the OutYears portion of the project, we will convert the testing technicians to DICE
Experts. These experts will act as second layer support to the DICE system, as well as
becoming intimately involved in the inner workings of DICE. Please refer to the
following diagram:
Phase33
Phase
OutYears
OutYears
1 Testing Technician
Increasing Knowledge of DICE
Phase22
Phase
Phase11
Phase
Phase00
Phase
DICE
Technical Evaluators
From Testers to Experts
2 Testing Technicians
2 Testing Technicians
2 DICE Experts