|
Mind Curve Technology has the extensive expertise,
experience and resources to develop custom Software applications that
best suit your needs, budget, schedule and existing infrastructure. We
strive to focus on the customer and deliver solutions designed around
their requirements. |
|||||||||||||||||||||||||||
| Our Expertise | |||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
| Software Development Phases | |||||||||||||||||||||||||||
| Phase 1 Planning |
![]() |
||||||||||||||||||||||||||
| Planning is the first phase of software development. In this phase the client give the details and concepts of his/her software and we plan the requirement of resources, time & budget of the proposed development. | |||||||||||||||||||||||||||
| Phase 2 - Requirements Analysis | |||||||||||||||||||||||||||
| The requirements analysis phase is concerned with capturing the requirements of the package. The requirements review is a meeting with the aim of discussing these requirements. The final output of this phase is a formal requirements document (Software Requirement Specification), which aims to freeze the requirements at this point and will serve as input to the design phase. | |||||||||||||||||||||||||||
| Phase 3 - Design & Development | |||||||||||||||||||||||||||
| The design phase is concerned with design of the software. Things to keep in mind are things like quality, flexibility (code reuse, future addition of features/functionality) etc. The final output of this phase is a formal design document (Software Design Document), which aims to freeze the design at this point and will serve as input to the coding phase. It serves as secondary function as a reference document for the code and can be particularly useful for developers that should work on the code in the future. | |||||||||||||||||||||||||||
| Phase 4 - Implementation | |||||||||||||||||||||||||||
|
The implementation phase involves the actual coding/programming of the software.
The output of this phase is typically the library, executables and User Manuals and additional software documentation
|
|||||||||||||||||||||||||||
| Phase 5 - Testing and Integration | |||||||||||||||||||||||||||
| The testing phase is concerned with the validation and verification of the software Unit testing is done on units and integration testing is done by including this package/unit together with other packages/units and testing them all together. | |||||||||||||||||||||||||||
| Phase 6 - Evaluation | |||||||||||||||||||||||||||
| Release the pilot of the product and client evaluates the product. If he /she require modification in the product he suggest it and we do it within a very short span of time. | |||||||||||||||||||||||||||
|
Phase 7 - Release
|
|||||||||||||||||||||||||||
| The Release phase involves the packaging of all sub-packages, together with all relevant documentation in a suitable format for distribution. | |||||||||||||||||||||||||||
| Phase 8 - Recycle | |||||||||||||||||||||||||||
| In case of log term projects, the release phase is the staring point of recycling of the project, but in short term projects release phase is the point of sign off too. | |||||||||||||||||||||||||||
| Technology Skills | |||||||||||||||||||||||||||
| Internet Programming Languages | |||||||||||||||||||||||||||
| PHP, Java, ASP.Net, JavaScript, VB Script, Action Script (Flash) | |||||||||||||||||||||||||||
| Programming Languages | |||||||||||||||||||||||||||
| C#, VB.Net, Java | |||||||||||||||||||||||||||
| Databases | |||||||||||||||||||||||||||
| MySQL, Microsoft SQL , Oracle, Sybase | |||||||||||||||||||||||||||
| Web Servers | |||||||||||||||||||||||||||
| MS Internet Information Server (MS IIS), Apache, WebSphere, Tomcat Apache | |||||||||||||||||||||||||||
| Operating Systems | |||||||||||||||||||||||||||
| MS DOS, MS Windows 95/98/ME, Windows NT/2000/2003/2008, Windows XP, Unix/Linux. | |||||||||||||||||||||||||||
