DePaulinformation services
Technology Contact Center|IS home|IS Forms|Campus Connection|Contact Us




SecuritySystems Data Information & AccessCommunication ServicesComputers on CampusAre you new to DePaul?Resources & ReferencesAbout Information Services
What We Do

How We Do It

How We Are Organized

Our Vision, Purpose & Goals

Who to Call for What


Migrating to Windows 7Recent Changes




TESTEmergency Plan



How we do it
More on How we do it:
Technology Life Cycle
  • Plan
  • Design
  • Build
  • Deploy
  • Support
  • Checkpoints
  • Forms/Artifacts
  • Roles and Responsibility
  • Glossary

  • News & Updates

    Technology Life Cycle

    Build Phase

    Technology Life Cycle - Build Phase

    Click on image for larger view


    What happens during the Build Phase?

    Construction is an exciting time, during which the development team brings the software/project/system to life. The project manager will work closely with the team members to keep the project on track and ensure that issues are resolved. Depending on the phase of testing and the size of the project, issues may be tracked in a simple spreadsheet (see artifacts list below) or may be entered into the TCC ticketing system. Throughout the Build Phase, the Project Requirements and Test Plan documents will guide the team activities. Changes in requirements must be agreed to by both functional and technical leads and will require adjustments to the project plan. Changes in requirements can affect target dates; the need for the change must be balanced with the effect on the project timeline and deliverables.

    While building and testing are going on, an Implementation Plan will be developed. For a small project, this may be no more than an agreement on a turnover date. For a large or complicated project, this may include pilot groups and multiple go-live phases.

    Both the functional and technical teams will test the solution. The technical team will focus on the technical correctness of each item; the functional team will focus on the functionality of each item. If needed, a usability team may be involved to focus on the usability of the solution. The Functional Lead is responsible for ensuring that resources are available for testing and the functionality is adequately tested. The Technical Lead is responsible for ensuring that the solution is technically sound. Formal signoff by the Functional Lead is required prior to production turnover. This signoff is generally in the form of an email. It indicates that the system has been fully tested and every requirement has been met. If the project involves changes that require governance board approval, the project results will be reviewed by the applicable board. At this time, projects which make changes to the portal or the data warehouse require additional approvals.

    Build Phase Artifacts/Templates

    How do you know when the Build phase is complete?

    If you have a fully functional system developed, tested and signed off by both the Functional Lead and the Technical Lead and the Implementation plan has been developed, the Build phase is complete and the system is ready for production turnover.



    © 2001-2004 | DePaul University | Disclaimer | Webmaster
    1 E. Jackson Chicago IL 60604 | 312-362-8000