CP317 | Week 7 | Deployment

Review of Week 6-2

• Software testing involves a concept and a plan.
• A test case procedure and test coverage are part of the software testing plan.
• Levels of software testing include unit testing, integration testing (top down vs. bottom up), system testing, and acceptance testing.
• Black-box testing and white-box testing are testing techniques.
• Test Driven Development (TDD) is another testing technique.

Introduction to Software Deployment

• From an occupation point of view, roles include deployment engineers/analysts and release engineers, Release Engineer Skills and Qualifications are an example.
• Manual deployment is different from automatic deployment.
• Manual deployment may involve software products in cars and airplanes.
• Automatic deployment involves devices connected to the Internet.
• As the Internet of Things grows, the demand for software developers increases.

Deployment

• Software deployment covers all activities to make a new or updated software system available for use, including new software for new systems and new versions for existing ones.
• Software deployment fits into software engineering models.
• Deployment involves a deployment plan, new software versions, user training, support (on-site), and bug fixes.

Deployment Tasks

• Tasks include planning the deployment, testing the software product in a simulated environment, and determining deployment strategies like cutover, stage deployment, gradual cutover, incremental, and parallel.
• Documentation includes creating training materials, user manuals, help guides, and contact information.
• Training is also a key deployment task.

Software Deployment Plan

• It defines the scope, approach, and execution of software deployment.
• Elements include the deployment method (cutover, gradual cutover, parallel, incremental, staged), deployment procedure, training, timelines, incident response, and rollback.
• A Gantt chart can be used to illustrate the deployment plan.
• Sample phase I deployment plan includes:
  • Kickoff of the project
  • Configuration details on units, shifts, and preferences
  • Implementation on one set of devices and modification if needed
  • Implementation of remaining devices.
  • Training customization
  • Training for service providers
  • Installation using nurse station homes, and making use of power and WIFI
  • Walk-through/test
  • Patient and Provider Use of Eloquence ACS
  • On-site patient, tech and nurse support
  • Feedback from users and patient and IT requirements for further deployment -Collation of metrics, feedback from users and reporting

Deployment Strategies/Methods

• A software deployment strategy is a way to change or upgrade software.
• The goal is to make the change without downtime, so users barely notice any improvements.
• Common strategies include cutover, staged deployment, gradual cutover, incremental deployment, and parallel deployment.

Cutover Strategy

• It involves deploying new software to all devices simultaneously.
• It is easy to set up and renews the software state.
• High risks, high impact on customers as well as expected downtime and system reboot are cons.

Staged Deployment

• It has functional production environments for practicing deployment.
• Low risks and renewed software states are pros.
• It is expensive, and expects downtime and system reboot

Gradual Cutover

• New software is installed into some users' machines while others continue using the existing software.
• One pro is the low risks, but it is difficult to configure
• Online deployments are an example

Parallel Deployment

• A new software system gradually takes over the roles of the older one while both systems operate simultaneously.
• Different versions run in parallel, and there is almost zero down-time release
• It may be difficult to configure for online releases

Incremental Deployment

• New features of software are gradually released to the end users.
• There are low risks
• The rollout can be slow, monolithic software will not work, and it is still being developed.

Alternative Names

• Direct cutover is also know as Recreate
• Parallel Operations - Blue/Green
• Pilot Operations - Gradual Cutover
• Phased Operation - Incremental

Deployment Mistakes

• Common deployment mistakes include assuming everything will work out well, using cutover deployment, having no rollback plan, and allowing insufficient time.
• Skipping staging, especially with complicated or safety-critical deployments, is a mistake.
• Installing many updates all at once and using an unstable environment are also mistakes.

Summary

• Key elements include deployment (with concepts and types), deployment tasks (planning, testing, documenting, and training), deployment plans, deployment strategies (such as cutover, staged, gradual, parallel, and incremental), and avoiding common deployment mistakes.

Announcement

• Group project requires completing the SDD first and implementing the software code based on it.
• Prepare a presentation, save it as PPT, and be able to deliver via myls
• Ensure to record as well to deliver to myls
• The content must follow half-time theory and half-time demonstration.