:: Celcius Technologies :: ............. Our Vision : Your Revolution

Celcius recognizes Quality to be an ever-extending process. As a solutions and service provider in the international market, we are committed to offer the highest quality customer service and support.

Celcius reviews all its processes periodically and enhances them regularly to meet the expectations of our customers.

We are highly focused on delivery of quality, enterprise level solutions, on time and within budget. Our products and services are among the finest available and can help your organization save time and money.

Experienced quality professionals support our quality management process.

*A brief phase wise overview of the process followed by Celcius to ensure end-to-end Quality control

Proposal Submission Phase
	Initial Study of the system
	Preparation of Proposal on the Scope, Proposed Architecture, Timelines and the Cost of the Overall projects
	Acceptance of Proposal
	Signing of NDA
	Issuing of signed Work Order or Purchase Order

Project Initiation Phase
Activities
	Project kickoff meeting
	Identify the contact persons and channel of communications
	Planning for project resources and services.

Planning Phase
Activities
	Identifying roles and responsibility of each member
	Identifying training needs.
	Identifying H/W and S/W resources needed for the project
	Define Change Request Management for the project
	Preparing Software Project Plan using QMS specified template and also having it reviewed
	Creating work breakdown structure with the project team and completing initial estimation using estimation processes
	Identifying deliverables for the project
	Preparing the Risk management plan
	Preparing a schedule (MS project) for the project and track the activities of the project by using the same
	Preparing software configuration management plan for the project
	Identifying defect prevention plan
	Putting SPP under software configuration management

Requirements Gathering Phase
Activities
	Collection of requirements, through emails, documents or telephone
	Analyzing requirements and preparing the Business Requirements Document. This document will essentially identify all the requirements and the functional scope the full system
	Base-lining and freezing of requirements though customer review and approval
	Preparing of User Acceptance Criterion through preparation of functional and system test plan
	Base-lining of User Acceptance Criterion through customer review and approval
	Sign-off on the Business Requirement Document and the Functional and System test plans
	Getting everything under software configuration management

Design Phase
Activities
	Completing *HLD*
	Generating / updating *test plans and test cases* and reviewing them
	Acquiring / generating / updating test data and reviewing them
	Developing prototypes, if required
	Defining data model and creating Data Flow Diagrams
	Defining use cases and creating Domain Model
	Completing *LLD*
	Completing design review by a peer reviewer and updating HLD
	Initiate Change Requests and approval, during the process of user approval and base lining of HLD and LLD

Coding Phase
	Generating code from domain model using UML tools (on requirement basis)
	Coding as per the design specification
	Following defined/recommended naming conventions and coding standards performing unit testing in accordance with the test plan / test cases and test data and review it
	Log all the defects in a defect tracking system
	Perform code reviews / walkthroughs if planned and update the code with the review comments closed
	Put the code under software configuration management
	Update and Review the analysis / design documents after approval
	Update and Review test plans / test cases /test data after approval
	Update prototypes, if required

Testing Phase
Test entry and exit criteria should be established for each type of testing and should be documented in the corresponding test plans. For example
	Code review, unit testing and closing the defects found during the unit testing should be complete before entering to integration testing
	Integration testing and losing the defects found during the integration testing should be complete before entering the Functional testing phase
	Functional testing should be complete before system testing
	Test readiness review before the software enters alpha/beta testing
	Performing integration testing as per the reviewed integration test plan
	Performing functional testing as per the reviewed functional test plan
	Performing System testing as per the reviewed System test plan
	Performing Alpha/Beta testing as per the reviewed test plan
	Documenting the test results for all the above testing and perform as many iterations needed to meet the exit criteria
	Updating and Reviewing analysis / design documents and Test Plans/ Test Cases /Test
	Data if required
	Updating and Reviewing prototypes, if required
	Updating and Reviewing code, if required
	Maintaining and following bug/enhancement life cycle

Project Execution and Tracking
Activities
	Tracking the progress of the project through SPP
	Maintenance of versioning, bug tracking , and release notes
	Mitigating and handling Risks
	Revisiting Project estimates when necessary
	Maintaining up to date Project Management Plan
	Project Status Reporting
	Conducting Project Review meetings
	Milestone Reviews
	Conducting Project Co-ordination meeting with support groups

Project Delivery
Activities
	Product delivery takes place only after all known defects are closed

*Above-mentioned activities can differ from project to project depending on requirements costing and project duration