Request a Quote

Featured Client

.Net Project for a Danish Company

Option Matrix has been working over last 2 years for an IT solutions firm in Denmark that provides portal solutions to sports clubs

Project Methodology

Option Matrix uses incremental and iterative prototyping methodology adapted from Rational Unified Process. Option Matrix process steps are aligned to SEI CMM Level 3 standards. Option Matrix gives a lot of importance to detailed representation of use cases in the scope section of the proposal.

Analysis & Design Phase Home Page Template

The Project Manager talks to client and asks for any examples of web designs they like or the elements that they would like to see in the header navigation, primary navigation, Web Designing Indialeft navigation, center navigation, right navigation and footer navigation on the home page. Another question is the desired layout of inside templates. Based on this input, the Business Analyst works with a group of web designers who make a few designs and client inputs are taken iteratively a few times before the home page look is final.

Prototype

Project Manager draws the screen layouts to guide web designers for making a HTML layout of every single feature and use case in the project. Home page design is incorporated into this layout as soon as it is ready. This step requires extensive client interaction and is iterative.

Design Certification

Project Manager writes a formal mail to client that he is satisfied with the way the team has made the layout and requests for a discussion. The Business Analyst takes the client through each screen and feature using an online URL on the browser. This URL is created in Design URL and will stay intact till end of project. Client inputs are duly incorporated and the client is then asked to give a formal design phase sign-off. The Project Manager call the client and tell clearly that all changes and inputs must be given at this stage and no further changes can be incorporated without extra budget after this point. It is critical to stay within the boundaries of the pre-decided scope of work at this point and both the client and project team must diligently apply themselves to accurately represent the required design. Anything that cannot be represented on the screen can be put like a callout or comment on the screen but it must be very comprehensive. This step is the nucleus of the project and we demand and insist that the client should provide a formal sign-off mail stating that they are satisfied with the design and accept that no further changes will be possible beyond this point. There is typically an invoice that is raised when this step is done and the invoice e-mail has a scanned image of both the project manager certification as well as client sign-off. Programmers are strictly advised not to start coding until a design sign-off is done.

DB Design and Code Structure

At this stage a Technical Architect takes over and works jointly with the Business Analyst to make a database design for the project. Third level normalization must be ensured so that future enhancements and feature addition is easy and do not pose insertion / deletion anomalies. Next a code structure is made where the individual PHP or INC or JS or other script files and folders required in the project are created as blank empty files. This is like creating a skeleton for the project. Sample code from the function library as relevant is inserted in each of the script files, so that the programmer does not have to start from ground zero. The technical architect makes an excel sheet where all the files and folders are listed and there is a 2-3 line description in front of each line item stating the purpose and any guidelines. A work breakdown structure is also made at this point, which states in XLS format, the definition of each module and which features are included in each module. This marks the end of design phase and the Business Analyst must send the definition of modules to client and explain over SKYPE what is covered in each module and what to expect in the remaining part of the project. Since, everything is well defined by now; it is also possible to give an accurate picture of delivery deadlines for each module completion.

Modular Coding

This stage has steps 6 sub-steps that must be carried out for each module.

Modular Coding

First we start with Module 1 and do the coding as per the code structure.

Unit Testing

The programmers are asked to unit test their work, so that there is no excuse about gross human error.

Code Certification

Once, the programmers are satisfied with their work, the Technical Architect does a code walkthrough and certifies that the coding has been done as per the specified guidelines of the company. Programmers may need to make some changes to fully satisfy the technical architect and the later is advised to stay involved and correct guide programmers rather than throw up surprises in module certification. The technical architect must write a formal certification mail to project manager with copy to client and business analyst.

Black Box Testing

The project manager directs the QA Analyst to test the features included in the specific module as well as check for regression to ensure that new programming does not disturb the old modules. QA Analyst submits an error report and must give his approval before things can move forward. QA Analyst sends a formal mail to client, project manager and business analyst certifying that he is satisfied with the features.

Module Approval

Business Analyst makes a presentation to Project Manager demonstrating the features on a live URL and when the Project Manager is satisfied (maybe with some changes), the project manager writes a mail to client with copy to business analyst, technical architect, QA Analyst and BDM that the module is now ready for client validation.

Client Validation

Business Analyst makes a presentation to Project Manager demonstrating the features on a live URL and when the Project Manager is satisfied (maybe with some changes), the project manager writes a mail to client with copy to business analyst, technical architect, QA Analyst and BDM that the module is now ready for client validation.

Testing and Go Live
System Testing

Once all modules are done, the QA Analyst does a comprehensive testing and submits his report. Once the QA Analyst is satisfied, the Business Analyst makes a comprehensive demonstration of all project features to the Project Manager. Once the Project manager is satisfied, he writes a formal mail to client that the project is ready for final demonstration. Business Analyst makes a demonstration to client and gets approval with any changes within scope and design boundaries. Client sends an approval mail asking the company to transfer project to their live server.

Beta Testing

Project source code is transferred to live server of client and there is a beta testing phase of 2 months, where the client is advised to ask mock clients to use the application and report bugs. Bugs within project scope are corrected free of cost. At this point, definition of bug is anything that does not work as per design sign-off. The purpose of beta testing is to make the application fully error free and robust to the extent feasible. End of beta testing marks the end of project and any further work is paid work that must be scoped separately.

zzz