Our Process model will be described using the chart:

PHASE 1- Requirements Gathering and Analysis

Gathering requirement through sessions and interviews with the client to describe what the system should do and allows the developers and the customer to agree on that description Describing the system in the form of Use Cases diagram as per the UML The information recorded is: - Functional requirements - Rules - constraints - Changes that are likely to occur - Personal Preferences Prototype storyboards or screen layouts are used for role-playing. Delivers: - Use case model, consisting of a set of use case diagrams. - Requirements document listing operational constraints, nature of changes likely

PHASE 2 – Analysis & Design

Prepare an Analysis model, comprising of Structural and Dynamic Models of the system by analyzing the requirements. Convert Analysis model to Design model Identify Core domain classes and static associations between these classes (based on analysis of requirements and the domain). Involve the client while Designing model with respect to architectural approaches and technology solutions for project implementation. Delivers: - Class diagrams - Sequence diagrams - State diagrams - Activity diagrams - Functional Specs.

PHASE 3 – Development Planning

Plan for iterative and incremental development of the software. Analyze the architecture to identify candidates for increments. Identify independent and infrastructure increments. Such increments create the infrastructure for the rest of the software. Identify dependent and use-case increments. Dependent increments rely on the infrastructure created by the independent increments. Identify integration points. This is based on the dependencies. Decide milestones, and teaming. This is driven by the technical requirements and size of each increment. Delivers: - Detailed project schedule with activities, teaming, milestones for various, and integration points. - Integration test planning (integration points, test cases, etc).

PHASE 4 –Implementation

This is the stage where the project is actually off the ground. TIPL builds the application in progressive phases or increments. Incremental delivery permits experimentation of complex solutions during the course of development. This approach facilitates modifications through hands-on exposure to the delivered increment. Construct the increments (over multiple iterations if necessary). Implementation and preparation of unit test cases Perform integrations and integration testing at the integration points. Delivers: - Constructed and tested subsystems or components

PHASE 5 –Delivery

Conduct acceptance testing and deliver the software End-users training to use the application effectively. Follow-up action in terms of close monitoring of the system and applications ensuring immediate response to issues