Success Protocols

MATRIX: Project Management Protocol

qdPM: Project Management Tool which helps the project team to be in synchronization. It helps keep track of project status, discussions, meetings, documentations and deliver timely deliveries as planned.
SharePoint: Common Portal shared between the Client and UMANG team, so as to maintain the transparency in work flow. Clients can take advantage of this tool to monitor the project progress.
SVN~ Code Subversion: This tool helps you maintain project source code and documents, also importantly the version control when more than one team member share the project resources.
Delivery Checklist: This List is a final checklist at the time of delivery, which is updated and maintained by teams involved at all stages of the software development, from Development to Documentation, and from Testing to Delivery.

CHRONICLE: Documentations Protocol

Analysis Documents: Documentations involved during the Analysis phase are Initial Understanding document, Low Level Design, High Level Design Document, Prototype designs
Doc-O-Matic: This tool helps in creating and maintaining the software source code technical documentation of different technologies and languages.
Minutes of Meeting(MOM): Upon end of every meeting between the client and UMANG team, a MOM is shared with the client which contains the list of attendees, points discussed, highlights of the meeting, plan of action and more.
Help Menus: Guides to help the users traverse through the software is an integral part of the development. HelpMenus are produced upon request by clients.

ALPHA-BETA: Quality Testing Protocol

MantisBT: Bug Tracking Tool which helps the testing team to report minor and major bugs; and the development team can get notifications and resolve the accordingly. The bugs can be monitored by the entire project team and can generate project reports.
SourceGuard UMLD: For Delphi Project, We use this inhouse developed component which helps in memory leak detection and bug reporting.
Test Case List: Set of conditions or variables under which a tester will determine whether an application, software system or one of its features is working as it was originally established for it to do. The mechanism for determining whether a software program or system has passed or failed such a test is known as a test oracle.