musalasoft quality process overview damyan kasapov, qa engineer tsvetelina kovacheva, qa engineer...
TRANSCRIPT
MusalaSoft
Quality Process Overview
Damyan Kasapov, QA EngineerTsvetelina Kovacheva, QA Engineer
March 15, 2005
MusalaSoft
• Musala Soft is a software engineering services company focused on e-Business solutions, information systems reengineering and integration.
Software Development
Process
MusalaSoft–Software ProcessCustomer
RequirementsSpecification and Change Request
Musala Soft
input
Quality Assurance
SolutionSatisfaction
QMS Improvement
Continual Improvement
Resources
Management Review
Customer Feedback
Internal Audit Post-mortem Analysis
Quality Process
• Internal Standards
• Audits
• Impact Analysis
• Risk Management
• Configuration Management
• Static and Dynamic Testing
• Documentation Testing
QA Team
• Separated QA Team at Company Level
• Assign one or more QAE to each Project Team
• QM control QA Team and enforce Company Quality Policy
QA Team QM
QAE QAE QAE…
Company Level
Project Level Assign QA Engineer
Project Team
PM
QAETeam Members
QAE
Software Development
Process
MusalaSoft–Software ProcessCustomer
RequirementsSpecification and Change Request
Musala Soft
input
Quality Assurance
SolutionSatisfaction
QMS Improvement
Continual Improvement
Resources
Management Review
Customer Feedback
Internal Audit Post-mortem Analysis
Quality Process
• QA activities are extended through all phases of Software Development Process
- Starts from Requirements Analysis - Ends with Customer Satisfaction
• Covers Static and Dynamic Testing – reviews, audits, analysis, test planning and execution
• Requires wide knowledge for many technologies
Quality Assurance
Plan
Specify
Execute
Quality Control• Process Reviews
• Audits
Analyse
Improve
Estimate
Improve
Report
Fix
Re-Test
Quality Assurance
• Risk Management
• Test Estimation
QA Activities
• Test Planning• Test Specification Development• Test Execution• Reporting, Re-Testing• Analyse and Check• On-going – Reviews and Audits
QA Methodology
• The Testing Scope and Coverage depending on Project size and technologies: - Functional Testing – Component, Integration, System, etc. - Non-Functional Testing - Load, Performance, Security, Recovery, etc.
• Unit Testing is controlled from QA Engineers, but is performed from Developers
• QA Team mainly using Black-Box techniques to build test cases and test data
Challenges
• High dynamics between Teams – QA commitment in different Teams and Projects
• Innovations, unknown technologies and short time for training and knowledge
• Customer Standards enforcement – conflict with Company Standards
Questions
Thanks for your attention.
Questions?