Our Methodology

Developing and delivering software systems on time and within budget requires a disciplined, engineering approach to software development.

At Methodologic we have developed an approach following proven Software Engineering Methodologies, which allows us to build distributed systems using documented, repeatable processes to deliver high quality solutions to our clients. Each phase of the methodology includes a deliverable to the client, in essence providing insight into the product as it is being developed.

Fundamental Principles

Our methodology is based on six fundamental principles that we believe are of preeminent importance in developing quality software systems. These principles are reflected in all of our documented processes and permeate our approach to software engineering.

1. Business Solutions

   To deliver necessary returns on investment, solutions must be strategically aligned with business objectives. Therefore, our first underlying principle is an emphasis on the business value of a solution. We work closely with our clients to explore the implications of system alternatives and to pursue those solutions which solve business problems. Essential to this process is a facilitated workshop which includes key business executives, IT professionals, and designated end users to develop consensus on the business reasons for the application, the core functionality, and the development and delivery processes.

2. Client Interaction

   A second fundamental principle is that client interaction must occur at every phase of the development lifecycle. Client representatives participate intensively in the analysis and specification phases. After the system requirements have been determined, interface prototypes are developed and reviewed by the client. Once these prototypes have been accepted, a software requirements specification document is prepared which then acts as a contract specifying the functionality of the system. This document is formally reviewed and accepted by the client. Thereafter, at each main phase of the project, a deliverable is produced and formally accepted by the client.

3. Fixed Price/Fixed Time

   The third fundamental principle is fixed price/fixed time for system implementation, testing, and integration. In essence, we assume part of the project risk. This practice enables our clients to achieve expected strategic returns and to budget effectively for project activities.

4. Component Reuse

   With the rate of change of global business activities, systems must be deployed quickly if they are to have strategic impact. Methodologic leverages components such as software objects, application frameworks, and off-the-shelf packages to deliver systems quickly and efficiently.

5. Knowledge Transfer

   Through participation in design walkthroughs and other project activities as well as through formal training sessions, we work closely with IT professionals and end users to ensure that system maintenance and enhancements can be performed without Methodologic.

6. Flexibility

   Finally, no one methodology can be used for every software project. At Methodologic, we emphasize maintaining the flexibility and agility to adapt our practices to the needs of our clients. Depending on the nature of the application, project phases may be lengthened or condensed, modified, or even omitted.