1. What are the elements of a QC plan?
The answer to this question depends on industry, company and/or project. In our software company, the closest thing to a Quality Control plan are our Test Standards and Test Plans.
The elements of our Test Plans are:
1) Introduction
- Purpose
- Product description
- System architecture
2) Scope
- Test coverage
- Features to be tested (in scope)
- Features not to be tested (out of scope)
- Compatibility matrix
3) Test strategy
- Test objectives
- Test approach
- Test environment
- System dependencies
- Test tools
- Assumptions
- Risks
4) Process
- Test process and guidelines
- Priority and Severity defined
- Pass/fail criteria
- Test entry/exit criteria
- Test resources
- Deliverables required for testing
- Roles and responsibilities
- Approvals and sign off
2. Can you please explain the difference between I.S.O and C.M.M levels?
The CMM is a way to communicate capabilities.
The ISO is a way to communicate the process.
3. How yuo can track bug and report through Quality Control dept?
According to me i track bug by defect tracking tool and i report it through defect life cycle. i i was wrong please correct me.
Noise variable factors either cannot be controlled or are difficult and or expensive to control during the design or actual production stage.
5. What is meant by risk? how you can avoid the risks?
Risk can be anything that leads to failure / defect / error in the apllication or process.
We can avoid risk by applying proper risk matrix in the process.Risk Matrix shows the controls within application systems used to reduce the identified risk, and in what segment of the application those risks exist.
Consider,Team members are leaving from the organization in the middle of the project is the risk for the Manager.For that he can take the preventive action by ask for the bond from the employee or can have the countable backups in the project.
Control charts are suitable for tracking items such as:
Production failures
Defects by life cycle phase
Complaint/failures by application/software
Response time to change request
Cycle times/delivery times
Mean time to failure
7. What are the activities that are involved in Software Quality Control?
The activities that are involved in Software Quality Control are Reviews and Testing.
Reviews:
a. Review of requirement.
b. Review of design.
c. Review of code.
d. Review of deployment plan .
e. Review of test plan.
f. Review of test cases.
Testing:
a. Unit Testing
b. Integration Testing
c. System Testing
d. Acceptance Testing
8. Described Software Quality Control Testing?
a. Unit Testing
b. Integration Testing
c. System Testing
d. Acceptance Testing
9. Described Software Quality Control Reviews?
Review of requirement.
b. Review of design.
c. Review of code.
d. Review of deployment plan .
e. Review of test plan.
f. Review of test cases
10. What are the Project Control Activities?
The following are the activities of project control:
- Verify the integrity of the database files.
- Check the transcription errors while inputting and referencing the data.
- Verify the data consistency.
- Perform the internal review of documents.
- Perform the completeness check.
- Compare the existing results with previous results.
11. List the benefits of Software Quality Control?
Following are the benefits of SQC:
- Increased productivity of the development team.
- Improved Product Quality: Test statistics and defect tracking are more precise and up to date.
- Decreased re-work costs as the detection of defects are found earlier in the software project development lifecycle in every stage.
- Increased confidence levels in existing product management and future product development.
- Increased credibility as the software produced will be highly qualitative.
12. Explain software control views?
Transcendental View : Quality can be recognized and not defined.
User View: Quality as suitable for the needs.
Product View : Quality as related to the inherent characteristics of the product.
Value-based View: Quality is dependent on the number of customers those who are willing to pay for the software product.
Development View : Quality that is in conformance to specification.
13. What are the changes in a company when it receives ISO 9001 certification?
Quality being part of every day operations, is the internal impact.
- Quality becomes as a part of setting and managing the objectives, practices.
- The open up of operations to customer audits, is the external impact.
- Procedures and record-keeping improve dramatically.
- The implementation of this standards will obviously takes the work to keep audits and the appropriate follow-ups fluent.
14. What is the process of Software Quality Measurement?
Quantifying the dimensions of the software product, to what extent the rate of the product is met.
- Qualitative and quantitative approaches provide the aggregate view of the product.
- Linear continuum need to be supplemented by the identification of the critical programming bugs.
- Consequences that might lead to catastrophic outages need to be properly identified.
- The critical application characteristics measurement involves the structural attribute measurement of the application architecture, coding, in-line documentation.
15. Who are involved in Software Quality Control?
Project Manager - Controls the software engineering work performed during the software development.
- Designer - Assists the team to complete the overall design of the software project implementation.
- Technical Advisors - Supports to implement all technical aspects and imposes the quality practices.
- Checkers/Testers - Performs the complete testing of the software project at various levels.
- Quality Assurance Manager - Conforms the software product is as per the expected result with proper guidance and co-ordination with the development team.
16. Explain Software Functional Quality?
SFQ is pertaining to conformance to the functional requirements.
- The SFQ is measured by the level of end user satisfaction.
- The usability and the intuitiveness and responsiveness of the use cases are referred, so as to determine the simplicity / complexity of the operations.
- SFQ compliances with the original design, and desired testability.
- Example: Voice of the Customer can be compared with the level of intuitiveness and responsiveness to measure the quality.
17. What are the software size requirements in Software Quality Control?
There are two types of software sizes:
Technical Size:
- The most technical sizing method is measured in terms of Line of Code per technology.
- The number of lines include in functions, files, classes and tables.
- These are computed with backfiring the Function Points.
Functional Size:
- The very common function size is Function Point Analysis.
- FPA is all about measuring the software deliverables.
- FPA is based on the requirements of the user and presents accurate representation of developer and estimator.
- FPA reflects the functionality that is delivered to the client.
- FPA involves in identifying and weighting of inputs, outputs and data storage.
18. Explain Software Functional Size?
The very common function size is Function Point Analysis.
- FPA is all about measuring the software deliverables.
- FPA is based on the requirements of the user and presents accurate representation of developer and estimator.
- FPA reflects the functionality that is delivered to the client.
- FPA involves in identifying and weighting of inputs, outputs and data storage.
19. Explain Software Technical Size?
The most technical sizing method is measured in terms of Line of Code per technology.
- The number of lines include in functions, files, classes and tables.
- These are computed with backfiring the Function Points.
20. What are best practices for assessing performance efficiency of a software product?
Practices of implementing Application Architecture.
- Interactions with remote resources should be appropriate.
- Proper management of memory, network and disk space.
- Best coding practices.
- Proper and appropriate data access performance and management.
- Appropriate compliance with Object Oriented and Structured Programming practices.
- Appropriate compliance with SQL Programming best practices.
21. What are the best practices for assessing security a software product?
Implementing proper Application Architecture Practices.
- Design compliance of multi-layer components and their functionality.
- Input validation, Cross Site Scripting best practices
- Proper handling of error and exceptions.
- Proper access controls to the program and system functions.
The following are the SE Practices and attributes:
- Coding practices / standards.
- Practices of Application Architecture.
- Determining the complexity of the algorithms.
- Determining the multi-layer design compliance.
- Ratio of component and pattern usability.
- Determining the software to avoid the patterns which would lead to unexpected results / behaviors.
- Determination of data integrity and consistency
23. Explain about Quality Control?
Includes the activities that are designed to determine the level of quality.
- QC is a reactive means which measures and monitors the quality
- Includes operational activities and techniques to meet the quality needs.
- QC involves in verifying the desired quality levels.
24. Can you please explain the difference between Quality Control and Quality Assurance?
Quality Assurance:
- Focused on planning, documentation and agreeing certain guidelines that ensures quality.
- The outcomes of Quality Assurance are quality plans, inspection plan, test plan.
- QA is to prevent defects from entering into solutions.
Quality Control:
- Includes the activities that are designed to determine the level of quality.
- QC is a reactive means which measures and monitors the quality
- Includes operational activities and techniques to meet the quality needs.
- QC involves in verifying the desired quality levels.
25. Define about Quality Assurance?
Focused on planning, documentation and agreeing certain guidelines that ensures quality.
- The outcomes of Quality Assurance are quality plans, inspection plan, test plan.
- QA is to prevent defects from entering into solutions.
26. Lis the Software Control Methods?
A paradigm that is Goal Question centric.
- A method that control the overall risk.
- Quality Control that involves Plan, Perform, Check, Action Model.
- Complete Software Quality Control.
- Software Development Method that involve the Spiral Model.
27. What are the factors that influence software quality?
Clear purpose of the product. All documentation must be clearly written.
- Completeness to the fullest development of the product.
- Only needed information and minimum lines of code should present. It is important as the memory is limited.
- The software product should be portable, so that computers of various configurations would support the execution of the product.
- Product should be maintainable, so that the updating activity can be continued throughout the life time of the software product.
28. What are the quality characteristics of ISO 9126?
Functionality : Functions that satisfies the specified requirements.
- Reliability : A set of attributes that are capable of software maintenance under specified conditions.
- Usability : A set of attributes that is capable of effort bearing on individual's performance.
- Efficiency: A set of attributes that are capable of balancing the relationship between performance of software and the resources used.
- Maintainability: A set of attributes that are capable of bearing the effort required for specific modifications.
- Portability: A set of attributes those are capable to bear on the ability of the software to be transferred on another environment.
29. What are Software Quality Control factors?
Functionality - To determine the required functionality in the software
- Usability - To determine the ease of the software is to use.
- Maintainability - To determine whether the modifications of the software can be made.
- Efficiency - To determine whether the software is efficient.
- Portability - To determine whether the software can be transferred to another environment.
- Reliability - To determine the reliability of the software as per the client's needs.
30. Which Software Quality Control Nomenclature is implemented for a software product?
Software Quality Control Nomenclature:
- Verifying: comparing the code predictions
- Validating: Comparing the prediction of code with test data
- Version Testing: Comparing output of the current version with output of the previous version
- Installation Testing: Comparing the result with newly installed code to the sample result code
- Development Code: Code tested only by the software developer.
- Alpha Code: Testing of the software product internally by selected users.
- Beta Code: Code testing internally by a large numbers of users.
- Released Code: Well tested and documented code that is officially distributed.
31. Explain Software Quality Control?
A set of activities for ensuring the quality of the software product is known as Software Quality Control.
The focus is on identifying the defects in the original products produced.
It is limited only for Testing phase of SDLC.
Software Quality Control is governed by Software Quality Assurance.
Software Quality Control is detection oriented.
The scope relates to specific product.
Agile communication is quicker than traditional software development communication in the following ways:
First, the project teams are "co-located" so that any questions are immediately answered instead of using phones,
email, etc to ask coworkers for ideas, thoughts or answers. Every day an Agile team meets for a quick 15 minute meeting
(sometimes called a daily scrum) to refine what tasks were completed the previous day, what will be done by the team
today and what impediments are prohibiting the team from getting the work done.
Agile teams are constantly refining scope based on empirical data from previous releases, test results and discoveries
where traditional projects design and code up to the delivery date only to discover problems when it's very expensive to correct.
33. When we write Test cases? & Why will write Testing?
Test Case is a document which acts as refrence or record. Test case includes not only test input and expected behavior
but also test step and description and pass fail criteria. It is a good practice if we write a test case before we
execute it. It will give a brief idea that what we have to test. In addition to this it acts as record which can be
used by new tester to understand and then test.
When putting a system together, the different components interacting may show unexpected behaviors. It is hard to be
able to predict these completely.
A typical example happens in power plants when running steam boilers or power generators in parallel. The load is not
distributed evenly, as would happen on a stand alone unit,but needs to be constantly tweaked.
In addition, there are unexpected configurations resulting from the installation itself, which create unstable modes
due to interaction. These must be addressed and proper compensation through the control system be applied.
Cleanroom development uses an iterative approach, in which the product is developed in increments that gradually
increase the implemented functionality. The quality of each increment is measured against pre-established standards to
verify that the development process is proceeding acceptably. A failure to meet quality standards results in
the cessation of testing for the current increment, and a return to the design phase.
