80 likes | 241 Views
Team Assignment 3. 2. Goal . Question . Metric. 3. Description. 4. GQM chart. Team 7. Contents. 1. About GQM. 1. About GQM. What is GQM process?
E N D
2. Goal . Question . Metric 3. Description 4. GQM chart Team 7 Contents 1. About GQM
1. About GQM What is GQM process? • GQM process is a goal-driver method for developing and maintaining a meaningful metrics program that is base on three levels, Goal-Question-Metric. The Approach uses metric to improve the software development process while maintaining alignment with organization business and technical goals. Why we should use GQM process? • Use GQM to establish meaningful metrics .When we had meaningful metrics we could collect meaningful data and directly aligned with metrics. • Use GQM to choose right metrics to don’t cause unnecessary effort and cost. • Use GQM to collect dependent data of metrics. How will we use GQM process? • GQM process is top - down approach to establish a goal-driver measurement system for software development.Start with Organizational goal, define measurement goals .After that, poses question to address goals. Final, identifies metric to provide the answers for questions
Team 7 2.Goal . Question . Metric
3. Description • Does product work correctly? Yes, it does. Because we control defect in product and know status of defect in product • How to release product on-time in schedule? We need control time delivery product to control and monitor status working of team • How to ensure the project cost not over-run? Reducing the cost of the project from which we can reduce the amount that customers must pay. In order to create customer satisfaction and create good relationships with customers • How to define issue density impact to the product? Issues crop up during project execution mainly because of unclear specifications or a lack of understanding the specs. Issues may also occur because of a conflict or an error in the requirements. The customer’s satisfaction does become affected if project team clear requirement. www.themegallery.com
3. Description • How many change requests are met? • Most projects would not be complete without a few change requests from the customer software maintenance projects run on these. Of course, the customer is happy when change requests are accepted without impacting the price or the delivery schedule. • How to define defect density to the product? • No project is ever perfect, and most times, defects may not be detectable immediately upon delivery. If defects are detected during the warranty period, the customer is happy. However, what is important is whether the defects fall into an acceptable range. Usually, the customer’s expectation is “zero defects,” but all professionals on quality know that “zero defects” is rarely achieved. Sometimes, customers specify defect density that they can accept (number of defects per number of opportunities for error). www.themegallery.com
4. GQM Chart www.themegallery.com
Thank You ! Have a nice day ! ^^