Quality Measurement Model

Software Quality is composed of a series of quality elements, each of which is composed of some measurement criteria.
The standards are quantified by some measurement standards. Quality Measurement runs through the whole process of software engineering and Software Delivery
Before Software Delivery, measurements (internal attributes) mainly include Program Complexity, module effectiveness, and overall program rules.
Module. The measurement (external attribute) after Software Delivery mainly includes the number of residual defects and the maintainability of the system.
ISO 9126 is referred to as "software product evaluation: Quality Characteristics and User Guide ". In this standard, set the software quality
It refers to the sum of features and features related to the ability of software products to meet declared or implied requirements. It can be divided into six
Features: functionality, reliability, efficiency, usability, maintainability, and portability. These six features, each
Features include a series of sub-features. The meanings of quality features and Quality Sub-features are as follows:
Features
Functionality: A group of functions
It is related to the existence of its specified nature.
. Function refers to
Some features.
Suitability: whether a set of functions can be provided for a specified task
And whether this set of features are suitable for relevant software attributes.
Accuracy (accurateness): results that are correct or consistent
Or effect-related software attributes.
Interoperability: interoperability with other specified Systems
Software attributes related to interoperability capabilities.
Compliance (compli ance): Make the software comply with relevant standards, conventions,
Regulations and similar software attributes.
Security: avoid unauthorized access to programs and data.
Or software attributes related to the ability to access unexpectedly.
2 Reliability: Same
Software maintenance within a period of time and under specified conditions
Performance.
Maturity: The frequency of effectiveness caused by software faults
Software attributes.
Fauit tolerance
Software owner related to the ability to maintain a specified performance level in the case of a port
.
Recoverability
Establish its performance level and restore the capacity of directly affected data to achieve
Software attributes related to effort and time required for this purpose.
3. Usability: required for use
And by a set of defined or hidden user
A set of attributes related to such individual evaluations.
Understandability: Understanding logical concepts with users
Software attributes related to the labor paid by the application.
1 earnability
Control, input, and output) software attributes related to the effort.
Operability
Software attributes related to the effort.
4 efficiency: under the specified conditions,
Between the performance level of the software and the amount of resources used
Link software Property
Resource behavior: when the software executes its functions,
Software related to the amount of resources used and the duration of resource use
.
5. maintainability
(Maintaina bility ):
Modifies a set of attributes related to the required effort.
Analyzability: similar
Determine the software attributes related to the effort required for the part to be modified.
Changeability
Software attributes related to effort required for environment change.
Stability (STA, bility): Risk of unexpected effects caused by modifications
.
Testability: efforts required to confirm the modified Software
.
6 Portability: with the software available from
The ability to move a slow building to another environment is related
.
Adaptability: unlike a software
The processing or means of software preparation can adapt to different prescribed environments.
Software attributes.
Installability: Install software in a specified environment
Software attributes related to the effort required.
Conformance: make the software compliant with portability-related labels
Quasi or agreed software attributes.
Replaceability: with a software in this software environment
Used to replace specified Other Software

By extending the software quality measurement to the architecture design, the architecture quality attribute and implementation problems are derived. We
You can use the following checklist to describe and construct your own quality measurement model.
Quality Attributes of software architecture
Editing
No.
Name content
1. Performance what is the expected response time for each case.
Average/slowest/fastest expected response time.
Resources (CPU, lan, etc.) to be used ).
How many resources are consumed.
Resource allocation policy.
The expected number of parallel processes.
Is there a particularly time-consuming computing process.
Whether the server is single-threaded or multi-threaded.
Is there a problem that multiple threads access Shared resources at the same time? If so, how to manage them.
To what extent does poor performance affect ease of use.
The response time is synchronous or asynchronous.
What is the change in system performance in one day, one week, or one month.
What is the expected increase in system load.
2. What is the impact of availability system faults.
How to identify hardware faults or software faults.
After a system failure occurs, the system can be restored quickly.
In case of a fault, is there any backup system that can take over.
How can we know that all key functions have been copied.
How long does it take to back up, back up, and recover the system.
The expected normal working hours are several hours.
The expected normal working hours per month.
3. What is the impact of reliability software or hardware faults.
Will poor Software Performance affect reliability.
How much does unreliable performance affect your business.
Is Data Integrity affected.
4. Does the function system meet all functional requirements raised by users.
How the system handles and adapts to unexpected requirements.
5 is the user interface easy to understand for ease of use.
Does the interface need to meet the needs of the disabled.
Do developers think that the tools used for development are easy to use and easy to understand.
6. Is it more advantageous to use a dedicated development platform than to use it for portability.
Is it worthwhile to establish an independent level of overhead.
What level should the system provide for portability (application, application server, and Operation )?
System or hardware level ).

7. reusability: Is this system the beginning of a series of product lines.
How many other systems are related to the existing systems? If so, can other systems be reused.
Which existing components can be reused.
Can the existing framework and other code be reused.
Can other applications use the infrastructure of this system.
Build reusable components. What are the costs, risks, and benefits.
8 is the integration technology based on current standards for communication with other systems.
Is the Component Interface consistent and easy to understand.
Is there a process for interpreting component interfaces.
9 Can I test the tools, processes, and technologies of languages, components, and services.
Is there any interface for unit testing in the framework.
Is there an automatic testing tool available.
Can the system run in the tester.
10 is the factorization system modular.
Is there an ordered multi-dependency relationship between systems.
Will modifications to one module affect other modules.
11. conceptual integrity do people understand this architecture. Is there a lot of basic questions.
Are there any conflicting decisions in the architecture.
Is it easy to add new requirements to the architecture.
12. Is there sufficient time, money, and resources to establish the architecture benchmark and the entire project for completeness.
Is the architecture too complex.
Is the architecture modular enough to support parallel development.
Is there too many technical risks.