Essel Swolutions Logo
Essel SWolutions .
METHODS >Methodology
.

One of our primary goals while setting up a quality system was to bring in all functional and non-functional aspects of the management and development of projects and products. At the same time, we were very cautious in eliminating all possible overheads of having a highly structured process. Based on the nature of work that we undertake, we categorized the work types into different categories, but for all the different categories we have a common four phased development life cycle. The four phases are the Inception Phase, the Elaboration Phase, the Construction Phase and the Transition Phase. But for each of the work categories, the steps that we follow in each phase will be different according to the nature of work, like for an on-going maintenance project, the steps in the inception phase will be different when compared to that of a development project in its entirety. A schematic diagram of the process methodology is given below.

Templates, checklists and guidelines are the other supporting tools that we use extensively to help the organization follow the process. For each of the artifacts that are generated at each step of the process, we have templates that are tailored perfectly to suit our needs. This method helps us to have a systematic approach to deal with each work item and also helps us to have uniformity across documents.

Based on the specific nature of each of the project, our process itself defines flexibility to tailor and fine tune it again to suit that particular project. This is done during the initial phase of the project by a joint team from technical, business development and the QA departments. From the experience that we gained out of over a decade of practice in managing projects in diverse areas, we always try to follow an iterative development methodology to the extend possible. Periodic releases to the clients helps them get a feel of how and where exactly the project or product is heading towards.

We always follow UML for design purposes and Essel as an organization insists on having a detailed design - detailed to the maximum extent possible. For example, it is mandatory that a design must atleast be deep up to the level of specifying the signature of all public functions of all classes when designed in an object oriented fashion. Reviews are mandatory at each milestone to assure that the proposed quality levels are met at all stages. The process defined for Essel SWolutions comprehensively covers all stages of the software development life cycle right from the stage where the company gets a request for proposal to until the closure of the project.

. UML is used for Design Documentation
. Follows Iterative Development
. Easy to manage Change Requirements

. Risk mitigation can be done in early stages

Methodology Chart Methodology Chart
Methodology Chart Methodology Chart


Top



Kerala House Boat
.
. .
.
.
All rights reserved
Copyright © 2015 Essel SWolutions
Valid XHTML 1.0 TransitionalValid CSS!






Site Map Contact UsHome Kerala House Boat