Subproject Overview

Mission and Scope

The mission of the Phoenix Project is to make an ambulatory blood monitor that is inexpensive, unobtrusive, and easy to use, and that collects a week of blood pressure measurements.

The purpose of this subproject is to:

  • Document how to develop the Phoenix Ambulatory Blood Pressure System
  • Build out the project's infrastructure

The Phoenix Project faces some interesting process challenges:

  • The product is complex. It is a system:
    An interacting combination of elements to accomplish a defined objective. These include:

    • Hardware (the monitor)
    • Software (analysis applications)
    • Firmware (monitor OS, monitor applications)
    • People (clinical and laboratory roles)
    • Information
    • Techniques (clinical protocols)
    • Facilities (the Halberg Chronobiology Center)
    • Services
    • Other support elements

    (International Council on System Engineering, System Engineering Handbook)

  • The product is free and open-source. It is the work of a virtual team whose composition varies over time and is separated by distance and timezones.
  • The product is a medical device. Its development process must be guided by a an auditable quality system.

Status

Subproject Documents

  • Process descriptions
    • Phoenix Process Framework PDF (25 pages, 307 KB)
    • Describes a process framework - a library of process components that are used to construct endeavor-specific processes, where process components include things such as work products, roles, and activities. The framework is not a process but the concepts with which processes are built. Thus far, the main benefit of the framework is its clues about project infrastructure.

      This is a work in progress. Any feedback is welcome.

    • Systems Engineering Process
    • Software Enginnering Process
    • ...
  • Tools
    • FTP (file transfer) clients — recommendations
    • For Microsoft Windows FileZilla
      For Mac OS X CyberDuck

      To access the Phoenix Project site, run the FTP client in active mode. This is the default for FileZilla, but the default for CyberDuck is passive mode.

    • Communications
    • Product data and configuration management
    • Testing and quality assurance
    • ...

This page is maintained by Christopher J. Adams. It was last updated on 15 May 2005.

Copyright (c) 2005 Christopher J. Adams
Copying and distribution of this page is permitted in any medium, provided this notice is preserved.