| |
| |
 |
| We are a client-centric organization, and our highly skilled development team provides you with tailored solutions that best fit your business and technology needs. It is our goal to help you and your organization to relezie your vision. |
|
|
|
| |
|
|
| How we do it |
| |
| MCT's services are delivered through a highly disciplined, repeatable process, allowing us to meet the quality and schedule requirements of the most demanding customers. Over the last five years, we have evolved MCT's own software development methodology, by bringing together the best aspects of leading software methodologies, including the Rational Unified Process (RUP) and the Capability Maturity Model (CMM), optimized for application development. Our methodology encompasses the complete software development life cycle including Scope, Design, Development, QA, Release, and Rollout. |
| |
Scope & Design  |
| |
 |
For each MCT engagement, a Marketing Requirement Document (MRD) is required. The MRD defines the business and application goals and strategic buy-in from Management, Development and Product Marketing and adequate resource allocation. The MRD includes quality and performance goals, site maps, screen lists, UI design specification with feature flows, high-level use case, style guidelines, and most importantly high-level timelines with estimated activity and release dates.
When enhancements are necessary, the Development Change Process (DCP) ensures that development stays on-time and on-budget. Each functionality enhancement must meet business as well as target date objectives and each change has detailed cost estimates to help our clients to budget and prioritize accordingly. |
|
| |
| Pre-Development |
| |
 |
From the high-level scoping documents, MCT’s project lead works closely with the clients to produce detailed business requirements and application design. Documents include application release, development project and QA test plans. MCT documents development sizing for Engineering, Application Management and Services and obtains client sign-off on development requirements before moving forward. Ultimately, the first HTML screen decks are produced at the end of pre-development phase. |
|
| |
| Development & QA |
| |
 |
Once coding begins, MCT’s development project lead provides weekly development updates on builds from engineering department. A MCT QA manager produces a master test plan and test cases and provides weekly defect resolution updates. Test plan and processes are followed for regression, performance and load/scaling testing. |
|
| |
| Release and Rollout |
| |
 |
Once an application is ready to exit the QA process, an application build is formally created and installation begins. Once build, installation and functionality verification are performed by MCT’s application manager, the application enters a long-term life-cycle management process. |
|
| |
|
|
| |
|
|
|
|
|
|
|
Software Development
