- Measurements are collected as per their definition at defined points as mentioned in Organization Metrics File
- Data is collected and compiled by using Project Summary, Help Desk, eRMS, Analysis Reports, Peer Review Analysis Reports etc
- Verification of the measurement data is done independently to check completeness, integrity, accuracy by SQA & SEG for the data that they provide to each other
- Once the data is collected will be assessed independently by QE
- Project may consider additional metrics to better manage their project
- Data should be available for use only by appropriate groups and personnel.
Showing posts with label metrics. Show all posts
Showing posts with label metrics. Show all posts
Monday, June 15, 2009
How data is collected for metrics and measurements?
There are some ways for metrics and measurements for data
Labels:
accuracy SQA,
Analysis Reports,
completeness,
eRMS,
helpdesk,
Integrity,
measure,
measurement,
metric,
metrics,
organization metrics files,
peer reviews,
Project Summary,
QE,
SEG,
verification
Sunday, June 14, 2009
What are the business goals of metrics and measurements?
We may say that these are its main goals.
- Continuously enhance the quality of our products & services
- Increase customer satisfaction leading to repeat business
- Attract, develop & retain competent & motivated resource base by ensuring highest level of employee satisfaction
- Be ready to meet market expectations by being proactive and having in-depth understanding of market requirements
- To be the world leader in providing - - - - software solutions
- Become a preferred vendor of - - - - software solutions by strengthening customer base in existing markets and aggressively exploring new markets
- To become a profitable organization
What is the relationship of Metrics and Measurement and Quality?
Here are the points to be noted
So there is relationship. As we have measurement correct we will have solid requirements and on that at the quality will be fine
- Software requirements are the foundation from which quality is measured. Lack of conformance to requirements is lack of quality.
- Specified standards define a set of development criteria that guide the manner in which software is engineered. If the criteria are not followed, lack of quality will almost surely result.
- There is a set of implicit requirements that often goes unmentioned (e.g., the desire for ease of use). If software conforms to its explicit requirements but fails to meet implicit requirements, software quality is suspect.
So there is relationship. As we have measurement correct we will have solid requirements and on that at the quality will be fine
How do ensure that Metrics and mesasurements are correct?
There are two things to do for ensuring that these are correct.
- Establish the objectives of measurement before data collection begins, defining each technical metric in an unambiguous manner.
- Define a few metrics and then use them to gain insight into the quality of a software engineering work product.
What are the main steps of metric and measurement?
Here are the main steps.
- Derive the software measures and metrics that are appropriate for the representation of software.
- Data required to derive the formulated metrics are collected.
- Once computed, appropriate metrics are analyzed on pre-established guidelines and past data.
- The results of the analysis are interpreted to gain insight into the quality of the software, and the results of the interpretation lead to modification of work products arising out of analysis, design, code, or test.
Labels:
analysis,
design,
metric,
metrics,
metrics and measurement,
results,
Software,
Software Engineering Methods,
Source code,
steps,
test
Subscribe to:
Posts (Atom)