|
||||||||||||||||||
|
||||||||||||||||||
 |
||||||||||||||||||
| 1) Understanding the Application Requirement | ||||||||||||||||||
| Each organization follows a unique methodology for processes. Thus when a process is to be automated it requires a customized approach and a customized software. | ||||||||||||||||||
| Our basic function is to understand the objective of the organization for setup of a customized software. | ||||||||||||||||||
If similar software’s are available ready in the market we suggest our customers to opt for a ready to use solution which would save their time and resources. |
||||||||||||||||||
| 2) Understanding the Processes / methodology the Organisation Follows | ||||||||||||||||||
| Most times many processes are integrated together generating the final output. Understanding the processes is the key to understanding the requirements. | ||||||||||||||||||
| Each process needs to be explored to the depth of it and thus is the key to understanding the system requirement. | ||||||||||||||||||
| 3) Understanding the End Users Requirement | ||||||||||||||||||
| The bottom is where the foundation lies. We believe the end user is most important part of a system. The end users requirements need to be integrated as per the processes and methods of functioning of the organization. |
||||||||||||||||||
| The success of any system / software application lies with the satisfaction of the end user. The end user can reject the most technologically advanced system if it does not match to his requirements. | ||||||||||||||||||
| After all he is the one who starts or is at the base of a process. | ||||||||||||||||||
| 4) Understanding the Managements Requirements | ||||||||||||||||||
| The management’s requirements are more towards the overall functioning of the organization or processes. The requirements differ at each level of the management chain. | ||||||||||||||||||
| However a strong MIS (Management Information System) which will allow them to monitor the processes and overall functioning of the organization / process is the base requirement. | ||||||||||||||||||
| 5) Drafting a Basic Sketch of The proposed Solution | ||||||||||||||||||
| Once the requirement is understood, our systems analyst takes over. A basic sketch of the proposed system is drawn as per discussions among our team. | ||||||||||||||||||
| The input and output modules are setup for the programmers to move ahead with the project. | ||||||||||||||||||
| 6) Deciding on Technology | ||||||||||||||||||
| A Simple Approach for a Complex Solution | ||||||||||||||||||
| Most times a simple technology can resolve the most complex problems. | ||||||||||||||||||
| We believe use of technology should be practical. If an application requires simple technology / solution, no need to force a complex solution. | ||||||||||||||||||
| 7) Creating a application skeleton for modules integrated | ||||||||||||||||||
| An application is designed in modules or phases to assist multiple developers coding each individual section of the process. | ||||||||||||||||||
| Once the modules have been defined the software developers / programmers start coding as per specific modules they are responsible for. | ||||||||||||||||||
| Once all the modules are designed and coded, they need to be integrated together. | ||||||||||||||||||
| 8) Getting Feedback from End Users - Making Changes as per users feedback | ||||||||||||||||||
| Once a basic system is created, the system is installed and presented to the end users for approval. Each change is noted carefully and all modifications to match the needs of the users are taken care of. | ||||||||||||||||||
| 9) Creating Basic Reporting as per requirement | ||||||||||||||||||
| Once the Input modules are in place, the reporting or MIS needs to be created as per the management’s requirements. | ||||||||||||||||||
| 10) Getting Feedback from Management - Making Changes as per feedback | ||||||||||||||||||
| Making changes as per managements directions including macro & micro reporting as per each member’s requirements | ||||||||||||||||||
| 11) Setting up application at site on trial basis for demo entries | ||||||||||||||||||
| The application is then put for a test run on site. While the users fill in live data few requirements emerge. The system is tested for compatibility with functioning of the physical processes of the organisation. | ||||||||||||||||||
| 12) Getting Feedback ? Modifications as per feedback | ||||||||||||||||||
| New requirements emerge during the testing process and necessary modifications are taken care of. Flexibility of the application keeping in mind the changes occurring due to change in business / govt. policies are to kept in mind having a long term approach. | ||||||||||||||||||
| 13) Testing for Software Bugs | ||||||||||||||||||
| A customized system is not a standard packaged software. Thorough testing follows, after the software is completed. However, since the software is changed, very often to match your requirements, it is bound to leave a few errors. We try and correct such errors in the course of the development. This is a part of the process. | ||||||||||||||||||
| 14) Making the system Live and operational | ||||||||||||||||||
| Once the system has undergone the test run by the users & tested for bugs, the system is made live at site. | ||||||||||||||||||
| 15) Managing Administration & Security Issues | ||||||||||||||||||
Backup / Restore facilities are by default a part of each system we design. Security features allowing restricted entry to each module based on user profile are integrated into the system as per organizations policies. Tracking features are included for monitoring each entry point and modifications made into the applicaton. |
||||||||||||||||||
| A Software is a Never Ending Process. | ||||||||||||||||||
| We stay by your side during the entire process of Application Development, Maintenance & Upgradation | ||||||||||||||||||
 |
||||||||||||||||||
|
||||||||||||||||||
