CIPL_Application development process.pptx

7/30/2019 CIPL_Application development process.pptx

http://slidepdf.com/reader/full/ciplapplication-development-processpptx 1/8



Development Process

Define

Plan

&

SRS

DebugDeployment

Prototype &

Design

Application

Development

Test



Development Process: Brief Define: - First is to define detailed scope of the requirements. This is done through a detailed

study by the project manager to know the requirements. This process starts even before theproject is awarded to us as our estimates are based on the amount of work involved andtechnological challenges. To estimate these we keenly study the project and the applicationscenario in real world before giving a quote

Plan and design: - Once the project is awarded to us, a SRS (Software Requirementsspecifications), Prototype with supporting High Level Designs (HLD), User Interface, Class

Diagram and Database Diagrams are prepared. These design documents and prototype are sentto clients for approval.

Develop: - Upon approval, we start coding. All our codes are well commented and follow namingconventions. We have a well defined multi-tier architecture and each developer adheres to it.

Test: - Testing phase begins with the planning. As soon as HLD is frozen, we prepare test plansand cases. Application is tested parallel to development making sure that there are no errors.Once the development is completed, the application is tested from scratch to make sure all

modules are well integrated. Debug: - The testing results are then converted in actions for debugging and solving the bugs.

Once all the bugs are fixed by the developers Quality team verifies the bugs and reports anyreproduced bugs. This process continues till all bugs are fixed.

Deployment: - Project leader reviews the application and makes sure that the application fulfils theService Level Agreement (SLA) and is in line with other functional and non functional requirements.Upon approval application is deployed to the production server.



Features of Development Lifecycle



Features of Development Lifecycle: Brief Prototyping: - Documents are always necessary in a well defined process but it is very difficult for

customers to figure out upfront what they will get for their money. Prototypes help the clients to have a clueof what will be delivered after coding.

Module releases: - Every project is divided into multiple modules. As soon as a module is completed we

send the demonstration version to the customer. This enables customers to track progress and notify us with

any change in flow

Periodic review and update to the client: - Project is reviewed by the project leader every week and

update is provided to the client about the schedule, completed targets and planned targets for the next week.

Checklist method: - From planning to deployment, we follow checklist method, dramatically reducing thecommonly made mistakes made by the developers while coding, releasing and deploying.

Well defined architecture: - We have developed a well-defined architecture. This helps us to train newly

recruited developers and leaders quickly. Since same architecture is followed in all the projects, it enables us

to manage manpower resources efficiently as everyone is familiar with the architecture and can be deployed

on any project in no time.

Common Libraries: - We have coded a set of libraries which the developers uses while coding the

application. These are common functions required while coding of any project. This helps expediting thedevelopment and virtually eliminating bugs as these libraries are well tested and optimized.

Knowledge management: - Common functions and solutions to challenges and issues are added in our

Knowledge management application. We believe in solving a problem or coding commonly used function

once. This also helps us reduce the development time.



Features of Development Lifecycle: Brief Task and bug tracking system: - Tasks while development and bugs while debugging are the

most important aspects of the projects.. Generally it becomes very difficult to manage bugs wheremultiple Quality Engineers and developers are working on an application. For this, we have a

project management application to manage/track both bugs and tasks .Use of above referred

application with advanced reporting, tracking and auditing features not only makes it easy to

manage but also enables improvements in each project.

Source code and version control system: -Developing an application without source code and

version control is a big risk. We use Visual Source Safe for Microsoft Technologies and SVN for

other technologies. Frequent review of SLA and planning documents by Project Leader: - Project leader is

responsible for meeting all requirements. Therefore project leader has to review the development

and SLA documents regularly to make sure project is on track. The reports are submitted to

management in every 15 days.



Quality Control Process

Planning

QA testplans

QA testcases

Bug tracking

tool set up

Executionof test

cases



Quality Control Process: Brief Quality is the most important part of the development process. We have a dedicated Software

Quality Assurance team. The team is responsible for the quality of the applications used in thedevelopment process. Each application goes through the process of testing as per well developed

checklists.

Once project planning and documentation is completed, the QA team prepares test plans and test

cases. These are executed by Quality Testing Engineers.

The application goes through various types of testing like Validation testing, functional testing,

performance testing, load testing, stress testing, usability testing and more. Once the bugs are

removed, optimization issues and other quality concerns are fixed by the developers. Theapplication is tested by the Quality team again to make sure each and every issue is fixed.

This type of testing is known as regression testing. Any reproduced issue is sent to the developers

again for fixing. This process continues till all issues are closed successfully.

To manage this process, we have a comprehensive quality and bug management system. Bugs

are tracked closely and developers are answerable if any bug is reproduced two times.

The quality process does not end with deployment of the application. Once the application iscompleted, Quality Manager is responsible for generating report for each developer comparing

improvement from the previous project. Developers are answerable for repeated mistakes. This

ensures continuous improvement.

To conclude Quality is a priority at Classic Informatics Private Limited

CIPL_Application development process.pptx

Documents

Transcript of CIPL_Application development process.pptx