Overview

Paradux has fused traditional software development methods with modern web development techniques to form a unique application construction process. Central to our methodology is building three-tiered applications, with user interface, business logic, and data layers clearly separate. This approach ensures that the end product is flexible, reliable, scalable.

Below is our project planning and development process. If you have any questions, please feel free to contact us and we can provide a one-on-one explanation.

Process

Project Planning and Preparation   This is the first phase in our development cycle. Usually initiated with a face-to-face meeting between Paradux and the client, this is the time for the client to communicate their needs to Paradux and for Paradux to better understand the goals and objectives of the relationship and resulting web site.

The Requirements Document is created during this phase. It includes a finalized list of goals and objectives of the site, measures of success, areas and features, a basic site map, a master schedule, and a definition of project roles at both companies with contact information.

During this period our design team examines the client's logo, color schemes, and sample material (especially web sites that the client likes) to begin to create a design direction.

Specification   After the architecture planning phase, the specification writing begins. The specification is a blue print for the entire project. Its two major parts, the flow chart and functional specification, are created sequentially. The flow chart is a site map with user experience flows, while the functional specification describes every feature on every page, as well as back-end functionality that is not tied to a user screen. The specification also includes testing criteria and performance benchmarks.

If during the specification process Paradux finds that the desired application differs significantly from that which was previously assumed, a revised cost estimate will be provided. The master schedule may be revised as well.

Design Finalized  Once the site map is created, the design team begins working on the design direction. They create up to three mock-ups that present the proposed look and feel of the site. The client either chooses one of the designs, or provides feedback to create the best look-and-feel possible.

Development   With the specification signed off on by the client and design templates complete, Paradux begins the development phase. During this phase all of the main design, HTML, and programming work takes place. The design team hands off the designs to the HTML team for HTML build-out. All pages are created in HTML and presented to the client for approval (this is a wireframe; no features are in place). This allows the client to see exactly how the site will feel and function before the programming begins. Once the wireframe is approved, the programming team starts coding. As each area is created, the pages are unit tested and sent to the client for review and approval.

Quality Assurance   As part of the development process, Paradux continually tests and debugs the web site and underlying application. Although QA is an on-going effort, specific rigorous QA sessions for each release will be conducted in tandem with the client's staff. This is done in accordance with the testing and benchmark guidelines outlined in the specification.

Deployment  Once the application is fully tested and ready to go, we deploy it on the end system (in this case on the client's server).

Maintenance and Management    Just because the program has been completed as specified doesn't mean our work is done. First, we stand by ready to handle any defects that may arise during the warranty period. Second, we maintain the system with necessary patches and upgrades. Finally, we begin to look at plans for subsequent project phases.