High-priority functions needed for year-end business functions went into the first release. Low-priority functions followed later in the third release. The customer paid for all the additional functionality and the team received very favorable comments for the project sponsor at the end of the project.
The deliverable evaluation is a final QA checkpoint at major milestones and before project closeout. This evaluation provides an objective assessment to verify the major deliverables satisfy the customer's requirements as defined by the contract. Techniques used during the deliverable evaluation include:. It is sometimes valuable to perform a detailed readiness review of a deliverable.
Consider this technique when:. The readiness review is a quality gate. It occurs before the team submits the deliverable into the acceptance process. The purpose of the readiness review is to confirm the deliverable meets the customer's requirements and the SOW specifications.
Here are some guidelines for the readiness review:. An independent, senior resource who is experienced with the technology should conduct the review. All action items from the review must be documented and resolved before the deliverable is considered complete. If required, verify that adequate plans are in place to measure the quality of the deliverable. Readiness reviews provide excellent education and mentoring opportunities for junior team members.
Take advantage of the review to build the capability of the project team. Like the monthly delivery reviews, readiness reviews are an important part of the program's quality management plan.
A learn review should be held at the end of all large projects. Learn reviews are an important technique to avoid repeating mistakes on the same program or with similar types of projects, and to understand root causes of troubled projects. The participants include members of the project team and may include the customer.
Capturing the lessons learned is important final step for the project team:. Encourage your project managers to schedule a learn review and publish the results as part of their project closeout activities. This paper described proven techniques that you can use to improve the quality of your own projects.
It is important to emphasize the personal side of Quality Management along with the basic project management processes. Throughout the Quality Management process and all the evaluations, the Quality Assurance team uses their experience to advise the project team and to make recommendations to address risks and issues.
The goal is to provide advice and counsel to the project. Large multiyear programs offer excellent mentoring opportunities since many of the project team members will likely move on to new projects within the same program.
The ultimate success is creating a positive environment where project teams are eager to share their best practices and the details of their work. Project Management Institute. Vliet, J. Software Engineering: Principles and Practice. Article Quality Management 1 November By Wilkinson, Amy Life-or-death decisions sometimes hang on whether doctors and nurses have safe, secure and swift access to patient records. Article Quality Management , Telecommunications 1 November By Wilkinson, Amy High-speed internet access can be a game-changer for developing countries.
And in Sri Lanka, the need was critical. Decades of bitter civil war left the island nation lagging far behind other parts…. After measuring three…. Release Review Report b. Process Improvement Proposal c. Project Plan d. Check out, make modification on server side and check in b. Check in, make modification on your local copy and check out c. Check out, make modification on your local copy and check in d. Check in, make modification on server side and check out Show Answer Answer : Check out, make modification on your local copy and check in 66 Defining rights of individuals for accessing the project repository is defined at which of the following stage of SCM: a.
SCM Audit b. SCM Planning c. SCM Control d. Fill in the blank from respective comma separated words a. Project, Pinning b. Keyword, Pinning c. Baseline, Label d. Branch, Trigger Show Answer Answer : Baseline, Label 68 In check-in, check-out model, version branching and merging are represented by a structure known as a.
Structure Chart b. Version Graph c. History Graph d. Experimental development b. Concurrent changes c. Independent path of development d. Labelling b. Baselining d. None of the above Show Answer Answer : Baselining 73 Your project is in the User Acceptance Testing phase and the customer comes back with a new requirement. What is correct sequence of activities in handling this change request: a. A workspace can originate from a preserved configuration of another workspace b.
A workspace can originate from a repository c. A workspace originates from a bound configuration in the repository d. Maintaining a file system as work area is more space efficient than using a workspace Show Answer Answer : Maintaining a file system as work area is more space efficient than using a workspace 75 SCM does not help in meeting which of the following ISO requirement a.
Identification and Traceability b. Control of records c. Design and Development outputs d. Audit Report b. Configuration report c. Build customized versions of project for different clients b. Merging two versions of the same file c. None of the above Show Answer Answer : Build customized versions of project for different clients 78 If a SCM break downs, which of the following is of the most help: a. The last complete backup of SCM repository b. Which of the following activity is not involved in it: a.
Baselining CI s b. Identification of CI s c. Analysis of historic Information d. What is the primary information maintained within history? Audit status of version b. Name and versions of artifacts c. Label associated with versions d. Difference between two versions of binary files b. Difference between two versions of files irrespective of their file types c. None of the above Show Answer Answer : Difference between two versions of ASCII files 82 In a parallel maintenance and enhancement project scenario if one of the bug fixes from maintenance project line is also need to be fixed for the enhancement project line then which of the following option is the most optimum?
Suggesting developer of enhancement line to perform the bug fix changes b. Performing merge from identified baseline of maintenance bug fix to enhancement line c. Setting up trigger for automatic bug fix notification d. Inform testing team about the bug fix in enhancement line Show Answer Answer : Performing merge from identified baseline of maintenance bug fix to enhancement line 83 To ensure change control, Veloci-Q procedures says: a.
The request of change should be recorded in Change Control Register b. Change should be tracked till it is PM approves it d. Risk assessment should be done in the end Show Answer Answer : The request of change should be recorded in Change Control Register 84 Configuration Status Accounting provides reports for senior management to access the health of project at any given point in time.
Which of the following report is derived from Configuration Status Accounting: a. System Performance Report b. Traceability metrics Report d. Review b. Approve c. Incorporate changes d. Labeling c. Status of change request and defect reports b. Version status of various configuration items CIs c.
Status of configuration items in various project baselines d. SCM b. Change request c. Control of documents b. Identification and traceability c. Control of non-conforming product d. Changes in code c. Configuration management of the software tools used in the development process d.
Initial b. Repeatable c. Optimized d. Configuration Management b. Control of documents c. Baseline Record BR b. Control, Management, control, quality b. Document control c. Tools usage d. None of the above Show Answer Answer : Control, Management, control, quality 96 Standardized, measurable process for change management are inherent of a. SCM processes b. SCM tools c. SCM plan d. Check-in c.
Check-out Show Answer Answer : Check-out 98 A report that shows the differences between two or more files or versions of a file are a. Audit report b. Difference report c. Configuration report d. Check-in b.
Check-in and check-out b. Merging ascii file and merging non-ascii files c. Merging of actual content; reflecting the merge in version history d. None of the above Show Answer Answer : Merging of actual content; reflecting the merge in version history. Data Item b. Configuration Item c. Building Block d. Approach for frequency and mode of version control b.
Branching Approach c. Merging Approach d. Change Control c. None of the above Show Answer Answer : Change Control Some of the parameters considered for change evaluation are a. Impact on existing system b. Complexity of Change c. Cost d. OS Support b. Development Environment c. Hardware Requirements d. You want to know all your responsibilities as defined by veloci-Q for your role. Where would you go?
Treasure House b. Navigator c. PDB d. PIP DB b. Project data bank d. Treasure house Show Answer Answer : Project data bank 4 As per veloci-Q, in a project following V process model — the activity to define acceptance Test Plan is recommended as part of a. Project Planning phase b. RS phase c. Design Phase d. PMR b. PIP board meeting c. MRM d. BS b. The Project Manager c. CMMI d. Past project data b. Risk Identification checklist c.
Stake holder inputs d. Projected effort and planned effort c. Actually consumed effort only d. Work Plans b. PMR c. PDMR d. International Organization for Standardization b. International Systems Organization c. International Systems Orientation d. TRUE b. Use of checklists and templates b.
Ability of the product to meet stated or implicit needs of customers c. Set of process and procedures d. All of the above Show Answer Answer : Ability of the product to meet stated or implicit needs of customers 13 An assessment consists of a. Interview of customers b. Questionnaire, Documents review and Interviews c. Review of quality System d. All of the above Show Answer Answer : Questionnaire, Documents review and Interviews 14 Triggers for root cause analysis are documented in a.
Quality Plan b. Master list of documents c. Project Dashboard d. Quality Improvement Council b. Management Review Meeting c. Quality Review Meeting d. Veloci-Q b. Project Plan c. Master List of Process d. Regression Testing b. Unit Testing c. Quality Assurance d. Meet the needs and expectations of customers b. Achieve customer satisfaction by providing defect free products and services on time.
Attain CMMi Level 5 compliance d. None of the above Show Answer Answer : Achieve customer satisfaction by providing defect free products and services on time.
SQA b. SEPG c. Tools group d. All of the above Show Answer Answer : Tools group 20 Configuration audits are verification mechanisms used to ensure that deliverables are: a. On schedule b. Defect free c. Consistent with requirements d. The methodology is aimed at providing the organization a long-term solution and the maturity to learn from mistakes. Most of the activities of the defect prevention methodology require a facilitator.
The facilitator can be the software development project leader wearing another hat of responsibility or any member of the team. Source: Computer Finance Magazine.
Errors in software requirements and software design documents are more frequent than errors in the source code itself, according to Computer Finance Magazine. Defects introduced during the requirements and design phase are not only more probable but also are more severe and more difficult to remove. Front-end errors in requirements and design cannot be found and removed via testing, but instead need pre-test reviews and inspections.
Table 1 shows the defects introduced during different phases of the software development life cycle. From the studies made by various software development communities, it is evident that most failures in software products are due to errors in the requirements and design phases — as high as 64 percent of total defect costs Figure 3 , according to Crosstalk, the Journal of Defense Software Engineering.
Hence, it is important to have a proper process of analyzing the requirements in place to ensure that the customer needs are correctly translated into product specifications. Perhaps two or three iteration of interactive sessions with the customer can be of great help in verifying the understanding of the developer about actual requirements.
Self-review is one of the most effective activites in uncovering the defects which may later be discovered by a testing team or directly by a customer. Often, a self-review of the code helps reduce the defects related to algorithm implementations, incorrect logic or certain missing conditions.
Once the developer feels they are ready with the module code, a glance through the code and understanding what it does compared to what it is supposed to do, would complete the self-review.
Peer review is similar to self-review in terms of the objective — the only difference is that it is a peer someone who understands the functionality of the code very well who reviews the code. Effective defect tracking begins with a systematic process. A structured tracking process begins with initially logging the defects, investigating the defects, then providing the structure to resolve them. Defect analysis and reporting offer a powerful means to manage defects and defect depletion trends, hence, costs.
A defect logging tool should document certain vital information regarding the defect such as:. After defects are logged and documented, the next step is to analyze them. Generally the designated defect prevention coordinator or development project leader facilitates a meeting to explore root causes. The root cause analysis of a defect is driven by three key principles:. With these guidelines, defects are analyzed to determine their origins.
This way, you will be able to understand them better. In the most basic definition, functional testing determines what the product does, while non-functional testing determines how it does it. Functional tests are based on business assumptions — so their main goal is to check it all the features work correctly and deliver results that might be expected by the users. Non-functional tests, on the other hand, verifies the performance of the software and tries to look for improvements in that matter.
Manual tests are performed by humans — quality assurance experts hired to do just that. Some of them write software tools used for different types of testing that require more computing power or atypical conditions.
While manual tests are often claimed to be less reliable as they introduce the human factor, that is not necessarily a bad thing. Software engineering can be a process that frequently forgets that people have various ways of acting, so it should be more human-like. With manual tests, the final product or service will be the subject in different scenarios that will check if using it is intuitive, logical and straightforward. If we need fast, repetitive tests without human insight — automated are the way to go.
They take less time when performed, but require more extended periods to be prepared. Software quality assurance is used to test each process. In organizations like software houses, we hire whole quality assurance departments to have a range of specialists in different types of testing.
Here are a couple of tests we run with our web and mobile apps:. The smallest part of the coded program is the unit. In this type of testing, every module is reviewed separately. Tests are performed to find out if all the functionalities work as they supposed to.
After unit testing, modules are combined into bigger groups and elements to see how they cooperate. The reason is to do that is to see how data flows between units. After integrating all the components, the whole system is tested.
At this stage, we need to see how the product works in terms of performance and security. Functional and non-functional tests are involved to give the product a whole rundown.
0コメント