CoursEval Software Development Life-Cycle

kettleproduceSoftware and s/w Development

Dec 2, 2013 (4 years and 7 months ago)


CONFIDENTIALITY: This document may contain confidential,
proprietary and privileged information, and unauthorized disclosure or use is prohibited.



CoursEval Software Development Life


The CoursEval SDLC has evolved over the past 4 years to incorporate best practices to ensure we can
deliver high quality changes that our customers want in a timely manner.

The SDLC process is a hybrid of agile development and waterfall methodologies. The support and
development teams take on many different roles throughout the process and will be involved in
business analysis, quality assurance, technical trouble shooting,
and customer service within the


Phase 1

Define the release

Identify problem areas by reviewing tickets submitted from:


Customer reported issues


Customer requests


CoursEval submitted enhancements

Identify Strategic areas for enhancements by

talking to customers and reviewing tickets.

Organize tickets into a release version to fit the release schedule. The release schedule seems
most appealing to the CoursEval customer base when the new application is delivered before
peak evaluation times wh
ich are traditionally October/November and April/May. Tentative
targets are end of September, end of January, and end of June.

Phase 2

Development process

Create technical specifications when required. Larger, more in
depth enhancements require
some lev
el of technical specifications to communicate the changes through the SDLC.

Development works directly with the support team to develop new features. New tickets are
added during this process if the original tickets are too broad. The tickets are used to t
rack the
features through development and testing. They are also used to develop release notes and a
test plan for Beta sites.

Tickets are updated with notes for the QA process including: functionality changes, testing
notes, scripts for testing, etc.

ckets are marked as ready to be tested once the development is completed

Tickets are marked as completed as features and changes pass the QA process.

Phase 3

Quality Assurance

The ticketing system organizes tickets to be completed, tickets in the testing

cycle, and
completed tickets.

Beta sites are identified well in advance o f the release. The goal is to have 3
4 weeks for Beta
sites to test. Beta sites have the option of using CoursEval provided test plans and the freedom
to test the features that are

important to them.

Release notes are developed in time for the Beta sites to begin testing. Release notes take on
the appearance of a newsletter and will include screen shots as well as text describing each

CONFIDENTIALITY: This document may contain confidential,
proprietary and privileged information, and unauthorized disclosure or use is prohibited.



CoursEval Software Development Life


A complete test plan is developed for
Beta sites in time for Beta sites to begin testing. The test
plan breaks the changes to the application down into feature areas. This makes it easier for
Beta customers to find the features that they are most interested in and provides a systematic
way to
go through each feature if the customer so desires.

Phase 4

Release preparation and installations

Release notes are distributed in introductory emails to existing customers.

Webinars are setup to demonstrate the new features in the release and to solici
t feedback.

Product documentation is updated 1
2 weeks prior to release and may lag the release if the
changes are complex. It is difficult to move this task up since changes are rapid and may
change during the testing cycle causing re
work to the document

Installations are first performed on the hosted environment giving 1
2weeks of a controllable
release prior to distributing CoursEval.

The hosted servers are typically updated 1 or 2 per day over the course of a week. Staggering
the release in this

way enables the CoursEval team to respond quickly to issues without having
to re
install across the farm.

The hosted server installations do not require the service pack or windows Installer deliverables
to be updated.

Customer site installations are sch
eduled based on customer preferences. There are two types
of installations:


installers download the service pack (zip file) from the CoursEval support website
and follow a procedure to shutdown CoursEval, unzip the service pack, then re


The majority of the installations are done by the Support team. A support portal built into
the CoursEval Manager Portal enables file uploads, script executions, and database
queries. A procedure is in place to load and check the updates and usually
takes 2
minutes per server to complete.

Data updates for releases are incorporated into the CoursEval code base and run automatically
when the version is updated. This technique enables updates from any version to provide
customers with flexible upgrad
e paths when it is convenient for them.

Phase 5


Transaction, Error, and Activity logs are monitored for issues.

Tickets are entered for reported issues.

If a patch is necessary, the SDLC process is repeated including analysis for any data
fixes that
could result from an issue. If necessary, communication to customers is sent out and re
are performed.