Cannonbose Sales Process
Cannonbose projects are successful because we plan for success before software coding begins.
- Interview for Requirements Gathering
- Project Objectives
- Content and Site Management
- Audience
- Present Proposal
- Tentative cost, schedule, deliverables, and resources used
- Legally binding agreement
- Collect Project Deposit
- Write Project Plan
- Controlling document for managing a software project.
- Research and Write System Requirements Specification
- Tool for capturing project requirements; epitome of “plain language needs”.
- Research and Write System Design Specification
- Designs for software systems customized for building the system.
- Research and Write Testing Plan
- Plan for execution and tracking of test activities, including test coverage.
- Additional Documentation, as needed
- Write Quality Assurance Plan
- Planning, tracking, and control for ensuring project meets quality goals. Includes technical process specific to quality assurance.
- Write Deployment Plan
- Significant deployment issues.
- Write Acceptance and Release Plans
- Significant customer acceptance activities that cannot be handled as part of the project or test plan.
- Write Final Proposal
- Needed if costs, schedule, deliverables, or resources have changed
- Final cost, schedule, deliverables, and resources used
- Begin Development
Thank you for your excellent work on the redesign of PSoCDeveloper. I'm very happy with the new site as are my users. I have received many positive comments from users though the forums, in emails, and face to face. I would not hesitate to work with each of you in the future.
Eric Blom, Site Administrator, PSoCDeveloper