Our Methodology for Custom Projects and Portals
Any process of building a Net solution goes through these clearly identifiable stages.
Phase 1: Pre-development Planning
Based on a high-level understanding of the solution required, Effects Multimedia will submit a Project Plan which will endeavor to list all the modules, tasks and sub-tasks in the project, with an idea of the timeline required for delivery.
This Project Plan will also define points of approval by the client and will be used for planning meetings for approvals and iterations.
This Project Plan is created with certain assumptions, based on Effects Multimedia, experience in delivering similar projects to clients, and is dependent on the assumptions being correct.
On sign-off of the Project Plan, Effects Multimedia, will prepare an appropriate System Requirements Sheet (SRS), which will highlight the overall client requirements in a manner and format
understandable to the client to:
- Convey Effects Multimedia understanding of the overall requirements
- Define the proposed solution
On the completion of a suitable SRS, Effects Multimedia, will prepare a Prototype of the solution required. The Prototype provides a page-by-page rough layout of the proposed solution and will be used to get final sign-offs prior to delivery.
- The Prototype will contain:
- The contents of each page with a large degree of detail
- The database interaction on each page
- The client-side manipulation required in each page
- The input received from the client by the server
- The navigability of the important portions
The Prototype will be handed over to the client for a detailed analysis and sign off, post spot-iterations, if any.
On the basis of the sign off on the Prototype, the deliverables will begin.
Phase 2: Development
Based on the inputs given in the Prototype, Effects Multimedia, will put two teams to work on parallel activities:
- Database design
- User Interface design
Usually, the Database design is retained by Effects Multimedia, unless specifically asked for by the client and is an internal deliverable for the project.
The User Interface design will go through the following stages of delivery:
- Overall User experience definition (Typically the home page of the site)
- Design of the main interfaces of the high-level modules of the solution
- Design of unique, non-standard elements in the site, if any
- Detailed prototype, down to the page level, typically comprising at least two pages at the module level
The User Interface design will go through a series of approvals. Usually, this delivery is dependent upon the previous delivery. Hence, the complete User Interface design will be a sequential activity.
After delivery of the User Interface design, the solution coding begins.
Coding will be subject to daily internal Quality Checks to confirm quality of delivery and adherence to client's requirement. On completion of functionality of each module, client approvals will be sought. This process will continue until all modules are delivered.
After delivery of all modules, integration of all modules into a single entity will happen and a complete quality check is done on the solution.
The integrated solution is deployed at the server location for complete beta testing by a closed user group. This group typically consists of all classes of likely users, including external groups with project buy-ins .
Any deficiencies and minor feature additions are made, based on the beta testing group feedback, and the solution is ready for delivery
Phase 3: Delivery and Maintenance
Once the project is ready for delivery, it is deployed in a production environment and is opened to all user groups. At this stage the solution is closely monitored for efficiency and performance deficiencies, which are fixed online for a period of two weeks.
This is usually treated as final delivery by Effects Multimedia, and the final invoice is raised and payments received.
After the period of close monitoring is complete, Effects Multimedia, will move the solution to a Maintenance Mode, where a skeletal team will be available for minor feature additions and changes based on user feedback. Beyond the first two weeks, charges for the same will be extra and is not a part of this proposal.