Sterlite’s Project Management methodology is based on the Rational Unified Process (RUP). This process is structured along two dimensions – time and process. Both dimensions are required for a project to succeed.

Time: Division of the lifecycle into time based phases and iterations.

Process: Production of a specific set of artifacts with well-defined activities.

The Rational Unified Process describes how to effectively deploy commercially proven approaches to software development for software development teams. These are called "best practices" not so much because you can precisely quantify their value, but rather, because they are observed to be commonly used in industry by successful organizations.

The Rational Unified Process provides each team member with the guidelines, templates and tool mentors necessary for the entire team to take

full advantage of among others the following best practices:

- Develop software iteratively
- Manage requirements
- Use component-based architectures
- Visually model software
- Verify software quality
- Control changes to software

Click on image to enlarge

RUP and similar products -- such as Object-Oriented Software Process (OOSP), and the OPEN Process -- are comprehensive software engineering

tools that combine the procedural aspects of development (such as defined stages, techniques, and practices) with other components of development (such as documents, models, manuals, code, and so on) within a unifying framework.

RUP establishes four phases of development, each of which is organized into a number of separate iterations that must satisfy defined criteria before the next phase is undertaken: in the inception phase, developers define the scope of the project and its business case; in the elaboration phase, developers analyze the project's needs in greater detail and define its architectural foundation; in the construction phase, developers create the application design and source code; and in the transition phase, developers deliver the system to users.

RUP provides a prototype at the completion of each iteration. The product also includes process support for Java 2 Enterprise Edition (J2EE) and BEA (WebLogic) development, and supplies an HTML-based description of the unified process that an organization can customize for its own use.

Inception - specifying the project vision
Elaboration - planning the necessary activities and required resources; specifying the features and designing the architecture.
Construction - building the product as a series of incremental iterations
Transition - supplying the product to the user community


Business Modeling - the identification of desired system capabilities and user needs
Requirements - a narration of the system vision along with a set of functional and non functional requirements
Analysis and Design - a description of how the system will be realized in the implementation phase
Implementation - the production of the code that will result in the executable system
Test - the verification of the entire system
Deployment - the delivery of the system and user training to the customer