"Strategic thinkers having business insight combined with technical know-how and committed for creating superior value for all stakeholders."

Lifecycle Processes

Quality Management

The focus of the quality processes at SPSOFT is prevention of loop holes at every stage of planning and management. With target to this objective, we function based on four-tiered quality structure.

• Process Heads / Process Owners (PH/POs) are responsible for ensuring quality at a project / process level.
• Internal Quality Auditors (IQAs) conduct Internal Audits across all processes / groups and all projects within each process / group on a quarterly basis.
• An external accreditation body conducts Surveillance Audits for our ISO 9001:2008 certification once every nine months.
• Quality Management Systems (QMS) team is responsible for defining long-term quality objectives and laying down the quality roadmap.

Quality Planning

Quality planning is done at two levels:

• Quality Assurance: Quality Assurance (QA) activities include defining processes - if not already defined, implementing already defined processes, training of team members, periodic quality audits and implementing serious project management practices.
• Quality Control: Quality Control (QC) activities include expert and management reviews of all the work products once they are released, either through inspections or walkthroughs. Another QC activity is testing (unit, modular and system/integration).

Change Management:

Change management is done at two levels:

• Configuration Management
  A Configuration Analyst is responsible for all the configuration management related activities. A formal documentation procedure is prepared and followed which covers the following information:

• - List of items that will be the baseline (configurable items) along with criteria for baseline
• - Procedures for work products check-in, check-out and releases
• - Change Control Mechanisms
• - Back up procedures
• - Disaster recovery procedures
• - Handling of customer supplied worm products

The Quality Systems Document for Configuration Management contains earlier mentioned procedures along with project specific deviations.

• Change Control
  Whenever change requests are received, the Project Manager reviews it initially and then periodically for progress review. The impact of these changes is analyzed on Requirement Specification, Design, Coding, Testing, Schedule, and Efforts. The Project Manager finally decides upon the change requests. Project Manager can have client representatives review change requests and the impact analysis.

Software Development

Based on the nature of the project, technology, and methodology, the software development activity is divided into a series of 'Milestones'. Each Milestone has inputs, processing steps, outputs (work products), completion criteria, acceptance criteria and so on. It is normally selected from a library of Milestones. Work products are tested for quality before using them as inputs into subsequent Milestone.