Business Intelligence
Management Systems

Contact Us
C. R. Hext (Director, Risk Management from Seaspan International): We have found the programs to be extremely user friendly and exceedingly meet our requirements to extract data from the system / Chris Chung (General Manager from BISCO Canada Inc): Their incredibly affordable solution has proved to be an excellent customer service and management tool that is efficient and very easy to use and manage. They were a great group to deal with. / Bianca Laurencin (Office Manager from C.A.S.T.): The customer support is great. When challenging situations arise, we call and usually the problem is resolved within a day / Hamid Zamanisadr (Comptroller from Yellow Cab Company): The professionalism, the code of conduct and the patience which you demonstrate is brilliant and admirable. I always look forward to working with you / Laura Hansen (President from Image Group Inc): The system that ProInfo has built for us has resulted in more accuracy in our written orders and more clarity and consistency in our instructions to our suppliers. We can always modify as changes occur with ProInfos expertise and support
Home Company Applications Technology Clients
Web Development Methodology

When it comes to producing applications, having a definable and consistent process is tremendously important - without it, the quality of the results are unpredictable. These processes are part of what sets ProInfo Solutions apart from the competition.
As important as process is, it must be flexible in this dynamic field. ProInfo Solutions tailors its processes to each specific assignment to provide guidelines and structure.
Whether the development process spans only a few days, or several months, the following are the typical phases:

Phases of the PROINFO Development Process:
Phase 1: Planning
Phase 2: Preparation
Phase 3: Software Design
Phase 4: Programming and Integration
Phase 5: System Testing
Phase 6: Data Conversion and Acceptance

Phase 1: Planning

  • Proposal
  • Contracts
  • Collect background information
  • Competitive review
  • Project profiler surveys
  • Project goals and mission
  • Target audience needs and wants
  • Define standards for success
  • Establish what resources are available
  • Initial Schedules
  • Establish communication mechanisms
  • Project Plan
  • Work breakdown structure
  • Quality Assurance Plan

    Phase 2: Preparation
  • Define how the assignment will be approached
  • Brainstorming and problem solving
  • Observing other web sites that "do it well"
  • Define content scope
  • Organize content
  • Strategic Brief
  • Creative Brief
  • Technical Brief
  • Basic Content Plan and Site Map
  • Select Development Environment
  • Functional Requirements

    Phase 3: Software Design
  • Rough plan of how the site will work
  • How will information be organized
  • Revised site map plans
  • Content development
  • Content scheduling
  • Mock ups and basic working models
  • Final production and technical plans
  • Design Entities/Dependencies
  • Logical Model
  • Table Structures
  • Database Schema
  • Functional Design Document
  • Screen Designs & Demonstration
  • Cross Reference Matrix
  • Web Security Plan
  • Training Plan
  • System Test/Acceptance Plan
  • Conversion Plan
  • Programming Specifications

    Phase 4: Programming and Integration
  • Content freeze
  • Final preparation and editing of content
  • Final interface design
  • Integration with back-end systems
  • Hosting issues, statistics
  • Site indexing and submission
  • Problem resolution
  • Acquisition and Installation Plan
  • Mappings
  • Software
  • System Documentation (Draft)

    Phase 5: System Testing and Beta
  • Internal launch date established
  • Testing and Quality Assurance
  • Usability tests
  • Stability tests
  • Volume/stress tests
  • Compatibility tests
  • Unit Testing
  • System Testing
  • Validation Testing
  • Determine date for external launch
  • Ongoing search engine placement issues
  • Site Installation Plan
  • Test Results

    Phase 6: Data Conversion and Acceptance
  • Update, revise, reinvent
  • Review server logs
  • Link checking
  • Ongoing QA testing
  • Who will be responsible?
  • Final required documentation
  • When do you redesign?
  • Beta Results Analysis
  • Operational System - Training
  • System Documentation