A Embedded software component quality verification framework

A Embedded software component quality verification framework
Fernando Ferreira de Carvalho Advisor: Silvio Romero de Lemos Meira Informatics Center - Federal University of Pernambuco Recife, 23 de Dezembro 2008

1 - Introduction / Motivation / Problem
Embedded system is at the heart of many systems Needs of embedded system industry, Low production cost Short time to market High Quality, and others to be more efficient and competitive (Brown, 2000) The CBD with reuse technique had been a nice direction to reach this objectives… The Robust framework for Software Reuse [Almeilda et al., 2004] is good way to support CDB approach and component reuse for embedded systems. But, Component reuse without quality assurance give catastrophic results [Jezequel et al., 1997]. So, components quality assurance is crucial before stored in a Repository System. 13/11/2018 Fernando Carvalho

Fernando Carvalho (ffc@cin.ufpe.br)
Proposed solution An Embedded Software Component Quality Verification Framework It is composed of four inter-relation module:, based on a set of activities, metrics and guidelines. Embedded software component Quality Model (EQM) Maturity Level evaluation Techniques Metrics Approach Component Certification based on a set of activities, metrics and guidelines. 13/11/2018 Fernando Carvalho

This two standards converged to:
Proposed solution This Framework is based in the standards ISO/IEC 9126, Quality Model for Software Product ISO/IEC 14598, Software Product Evaluation Process This two standards converged to: ISO/IEC 25010, Software product quality - requirements and evaluation The Framework adapted the quality model and evaluation to component context and embedded domain. 13/11/2018 Fernando Carvalho

Out of scope This Framework is part of broad context, some aspects were expected since initial definition. Nevertheless, other process can be added in the future. Cost Model Formal Proof Prediction of the component assembly 13/11/2018 Fernando Carvalho

2 – Embedded System Design
Embedded system design comprise: Ultra-small device x simple functionality Small system x sophisticated functions Large systems and distributed systems Systems produced in large quantities x low production cost Systems produced in low volume x important features 13/11/2018 Fernando Carvalho

The different requirements of embedded systems have a impact on feasibility, on use of CBD for it. A common characteristic in different area of embedded domain is increasing importance of software [Crnkovic, 2003]. Example, the software cost in embedded systems: in industrial robots constitute about 75% of total cots in car industry it is about 30% Fifteen year ago: 25% of total cots in industrial robots Negligible for cars 13/11/2018 Fernando Carvalho

Properties that involves embedded software component is divided in: Functional property (component interface) Non-functional or Extra-functional property, so called Quality attributes, fox example: Timing Performance Consumption Resource Behavior, and others. This properties can be classified in run-time and life-cycle. 13/11/2018 Fernando Carvalho

2 – Specific Requirements for Embedded System
In the most of case, embedded system is real-time with limited resource. So, it has specifics characteristics which depends on domain application, but it have strong implication on requirements. The REQUIREMENTS are related Extra-functional property or Quality attributes, and its priority depends on the domain application. 13/11/2018 Fernando Carvalho

2 – Specific Requirements for Embedded System
There has been developed a research in order to find the most important characteristics in different areas in embedded domain. Industrial Automation Automotive Medical Electronic consumer Other domain 13/11/2018 Fernando Carvalho

2 – Specific Requirements for Embedded System – Industrial Automation
Industrial Automation was classified by research’s Larsson, [Larsson, 2002] The most important characteristics, following the research: At low level: Availability Timeliness Reliability At high level: Performance Usability Integrability 13/11/2018 Fernando Carvalho

2 – Specific Requirements for Embedded System - Automotive
Akerholm [Akerholm, 2005] executed a research in vehicle industry. The resulting list of characteristics is presented below Safety Reliability Predictability Usability Extendibility Maintainability Efficiency Testability Security Flexibility 13/11/2018 Fernando Carvalho

2 – Specific Requirements for Embedded System - Medical
Wijnstra [Wijnstra, 2001] describe their experience with characteristics in the development of medical imaging family. The resulting list of characteristics is presented below Reliability Safety Functionality Portability Modifiability Configurability Extensibility and Evolvability Security Serviceability 13/11/2018 Fernando Carvalho

2 – Specific Requirements for Embedded System – Others Domain
Characteristics Sub-characteristics Real-time properties Response time or latency execution time worst case execution time Deadline Dependability Reliability Availability integrity confidentiality safety Resource consumption Power consumption computation (CPU) power memory Consumption execution (CPU) time, Life cycle properties maintainability Crnkovic [Crnkovic, 2003] summarized the main characteristics and sub-characteristics in the CBD approach apply to embedded system in his research. The table show the results. 13/11/2018 Fernando Carvalho

2 – Embedded System Design – Software component quality
So, embedded software component quality verification must be different that general propose component, because the component evaluation is realized focused in specifics requirements We divided the quality verification in two groups: General propose software component quality process desktops, servers, x86 architecture Specific propose software component quality process embedded systems 13/11/2018 Fernando Carvalho

3 – Embedded Software Component Quality and Certification: A Survey
The relevant research explore the theory of component quality and certification in academic scenarios, but not rich in reports in practical experience. The pioneering works focus in mathematical and test model, while recent researchers have focused in techniques and model based on predicting quality requirements. 13/11/2018 Fernando Carvalho

Timeline of research in the embedded software component quality and certification area proposed standard X fail → a work was extended by another 13/11/2018 Fernando Carvalho

In 1993, Poore [Poore et al., 1993] develop an approach based on three mathematical model (sampling, component and certification models), using test cases to report the failures to achieve a reliability index Poore estimated the reliability of a complete system, and not of individual software units, although, they did consider how each component affected the system’s reliability. 13/11/2018 Fernando Carvalho

Wohlin [Wohlin et al., 1994] presented the first method of component certification using modeling techniques, making it possible not only to certify components but to certify the system. It is composed of the usage model and the usage profile. The failure statistics from the usage test form the input of a certification model. An interesting point of this approach is that the usage and profile models can be reused in subsequent certifications However, even reusing those models, the considerable amount of effort and time that is needed makes the certification process a hard task. 13/11/2018 Fernando Carvalho

In 1994, Merrit (Merrit, 1994) presented an interesting suggestion: the use of components certification levels. These levels depend on the nature, frequency, reuse and importance, as follows: • Level 1: No tests are performed; the degree of completeness is unknown; • Level 2: A source code component must be compiled and metrics are determined; • Level 3: Testing, test data, and test results are added; and • Level 4: A reuse manual is added. These levels represent an initial component maturity model. However, this is just a suggestion of certification levels and no practical work was actually done to evaluate it. 13/11/2018 Fernando Carvalho

In 1996, Rohde (Rohde et al., 1996) provided a reuse and certification of embedded software components at Rome Laboratory of the US Air Force, a Certification Framework (CF), that included: • To define the elements of the reuse context that to certification; • To define the underlying models and methods of certification; and, • To define a decision-support technique to construct a context-sensitive process for selecting and applying the techniques and tools to certify components. 13/11/2018 Fernando Carvalho

• A Cost/Benefit plan that describes a systematic approach of evaluating the costs and benefits. Rohde et al. considered only the test techniques to obtain the defects result in order to certify software components. This is only one of the important techniques that should be applied to component certification. 13/11/2018 Fernando Carvalho

Voas [Voas, 1998] defined a certification methodology using automated technologies, such as black-box testing and fault injection to determine if a component fits into a specific scenario. This methodology uses three quality assessment techniques: (i) Black-box component testing determine if the component quality is high enough; (ii) System-level fault injection determine how well a system will tolerate a faulty component; (iii) Operational system testing determine how well the system will tolerate a properly functioning component 13/11/2018 Fernando Carvalho

According to Voas, this approach is not foolproof and perhaps not well suited to all situations. The methodology does not certify that a component can be used in all systems. This approach certify a component within a specific system and environment. 13/11/2018 Fernando Carvalho

Wohlin and Regnell [Wohlin and Regnell, 1998] extended their previous research (Wohlin et al., 1994), now, focusing on techniques for certifying both components and systems. Thus, the certification process includes : usage specification (consisting of a usage model and profiles), and (ii) certification procedure, using a reliability model. 13/11/2018 Fernando Carvalho

The main contribution of that work is the division of components into classes for certification and the identification of three different ways of certifying software systems: i. Certification process, the functional requirements are validated during usage-based testing; ii. Reliability certification of component and systems, the component models that were built are revised and integrated to certify the system that they form; and, iii. Certify or derive system reliability, where the focus is on reusing the models that were built to certify new components or systems. 13/11/2018 Fernando Carvalho

However, the proposed methods are theoretical without experimental study. According to Wohlin et al., “both experiments in a laboratory environment and industrial case studies are needed to facilitate the understanding of component reliability, its relationship to system reliability and to validate the methods that were used only in laboratory case studies” (pp. 09). Until now, no progress in those directions was achieved. 13/11/2018 Fernando Carvalho

In 2000, Jahnke, Niere and Wadsack [Jahnke, Niere and Wadsack, 2000] developed a methodology for semi-automatic analysis of embedded software component quality. This approach evaluates data memory (RAM) utilization in Java technology by the component. The work is restricted because: - Verifies the component quality from only one point of view, use of data memory in a specific language, - Java is widely used for the development of desktops systems not useful for embedded development. 13/11/2018 Fernando Carvalho

Stafford (Stafford et al., 2001) developed a model for the component marketplaces that supports prediction of system properties prior to component selection. The model use functional verification and quality-related values associated with a component, called credentials. This work introduced notable changes in this area. It use a specific notation such as <property,value,credibility>. Through credentials, the developer chooses the best components to use in the application development based on the “credibility” level. 13/11/2018 Fernando Carvalho

Stafford introduced the notion of active component dossier, its is an abstract component that defines credentials. Stafford et al. finalized their work with some open questions, such as: how to certify measurement techniques? What level of trust is required under different circumstances? Are there other mechanisms that might be used to support trust? 13/11/2018 Fernando Carvalho

In 2002, Comella-Dorda et al. (Comella-Dorda et al., 2002) proposed a COTS software product evaluation process. The process contains four activities, as follows: Planning the evaluation -> evaluation team, stakeholders, required resources, basic characteristics of the evaluation Establishing the criteria -> evaluation requirements , evaluation criteria; Collecting the data -> component data are collected, the evaluations plan is done and the evaluation is executed; and Analyzing the data -> the results of the evaluation are analyzed and some recommendations are given. The proposed process is an ongoing work and, no real case study was accomplished, becoming unknown the real efficiency. 13/11/2018 Fernando Carvalho

In 2003, Beus-Dukic (Beus-Dukic et al., 2003) proposed a method to measure quality characteristics of COTS components, based on the international standards for software product quality (ISO/IEC 9126, ISO/IEC and ISO/IEC 14598). The method is composed of four steps: Establish evaluation requirements, specifying the purpose and scope of the evaluation, specifying evaluation requirements; Specify the evaluation, selecting the metrics and the evaluation methods; Design the evaluation, considers the component documentation, development tools, evaluation costs and expertise required in order to make the evaluation plan; Execute the evaluation, the execution of the evaluation methods and the analysis of the results. However, the method proposed was not evaluated in a real case study 13/11/2018 Fernando Carvalho

In 2003, Hissam (Hissam et al., 2003) introduced Prediction- Enabled Component Technology (PECT) as a means of packaging predictable assembly. This work, which is an evolution of Stafford et al.’s work (Stafford et al., 2001), attempts to validate the PECT and its components, giving credibility to the model 13/11/2018 Fernando Carvalho

During 2003, a CMU/SEI’s report, Wallnau extended Hissam work (Hissam et al., 2003), in order to achieve Predictable Assembly from Certifiable Components (PACC). This novel model requires a better maturation by the software engineering community in order to achieve trust in it 13/11/2018 Fernando Carvalho

Magnus Larsson, in 2004 (Larsson, 2004), define A predictability approach of the quality attributes, where one of the main objectives is to enable integration of components as black boxes. According to composition principles, results types of attributes: Directly compassable attributes. is a function of only the same attribute. Architecture-related attributes. is a function of the same attribute and of the software architecture. Derived attributes. depends on several different attributes Usage-depended attributes. is determined by its usage profile. This work is very useful, but before the component quality must be known. 13/11/2018 Fernando Carvalho

Finally, in 2006 Daniel Karlson (Karlson et al., 2006) presented the verification of component-based embedded system designs. These techniques is Formal Methods based modeling approach(Petri net), called PRES+. Two problems are addressed: component verification and Integration verification. This approach verifies the component from only one perspective: functionality. Formal verification, it is used only in few cases when it is mandatory, because much time and financial effort are employed. 13/11/2018 Fernando Carvalho

Failures in Software Component Certification Two failure cases that can be found in the literature . First failure occurred in the US government, when trying to establish criteria for certificating components (NIAP). Thus, from 1993 until 1996, NSA and the NIST used the Trusted Computer Security Evaluation Criteria (TCSEC), “Orange Book”. It had defined no means of features across classes of components, but only for a restricted set of behavioral assembly properties (Hissam et al., 2003). 13/11/2018 Fernando Carvalho

Failures in Software Component Certification The second failure happened with an IEEE committee, in an attempt to obtain a component certification standard. The initiative was suspended, in this same year. The committee came to a consensus that they were still far from getting to the point where the document would be a strong candidate for a standard. (Goulao et al., 2002a). 13/11/2018 Fernando Carvalho

3 – Embedded Software Component Quality and Certification: Standardization One of the main objectives of software engineering Improve the quality of software products, Establishing methods and technologies to build software products. The quality area could be basically divided into two main topics (Pressman, 2005): Software Product Quality: aiming to assure the quality of the generated product; and Software Processes Quality: looking for the definition, evaluation and improvement of software development processes. 13/11/2018 Fernando Carvalho

3 – Embedded Software Component Quality and Certification: Standardization Software Product Quality: ISO/IEC 9126 (ISO/IEC 9126, 2001), ISO/IEC (ISO/IEC 12119, 1994), ISO/IEC (ISO/IEC 14598, 1998), SQuaRE project (ISO/IEC 25000, 2005) (McCall et al., 1977), (Boehm et al., 1978), among others Software Processes Quality: Capability Maturity Model (CMM) (Paulk et al., 1993), Capability Maturity Model Integrated (CMMI) (CMMI, 2000), Software Process Improvement and Capability dEtermination (SPICE) (Drouin, 1995), among others 13/11/2018 Fernando Carvalho

3 – Embedded Software Component Quality and Certification: Standardization Standards Overview ISO/IEC 61131 component-based approach for industrial systems RTCA DO 178B guidelines for development of aviation software ISO/IEC 61508 Security Life cycle for industrial software ISO/IEC 9126 Software Products Quality Characteristics ISO/IEC 14598 Guides to evaluate software product, based on practical usage of the ISO 9156 standard ISO/IEC 12119 Quality Requirements and Testing for Software Packages SQuaRE project (ISO/IEC 25000) Software Product Quality Requirements and Evaluation IEEE P1061 Standard for Software Quality Metrics Methodology ISO/IEC 12207 Software Life Cycle Process. NBR ISO 8402 Quality Management and Assurance. NBR ISO Model for quality assurance in Design, Development, Test, Installation and Servicing NBR ISO Quality Management and Assurance. Application of the ISO 9000 standard to the software development process (evolution of the NBR ISO 8402). CMMI (Capability Maturity Model Integration) SEI’s model for judging the maturity of the software processes of an organization and for identifying the key practices that are required to increase the maturity of these processes. ISO 15504 It is a framework for the assessment of software processes. Many institutions are creating standards to properly evaluate the quality and development processes of the software product, in different domain. The Table shows a set of national and international standards. 13/11/2018 Fernando Carvalho

3 – Embedded Software Component Quality and Certification: Standardization ISO/IEC 25000, 2005 / SQuaRE project - Software Product Quality Requirements and Evaluation has been created specifically to make two standards converge: ISO/IEC 14598, define a software product evaluation process, based on the ISO/IEC 9126. ISO/IEC 9126, define a quality model for software product Trying to eliminate the gaps, conflicts, and ambiguities that they present. 13/11/2018 Fernando Carvalho

3 – Embedded Software Component Quality and Certification: Standardization ISO/IEC 25000, 2005 / SQuaRE project The objective is : To respond to the evolving needs of users through an improved, and Unified set of normative documents covering three complementary quality processes: Requirements specification, Measurement and Evaluation. The motivation is to supply for developing and acquiring software products with quality engineering instruments supporting both the specification and evaluation of quality requirements. 13/11/2018 Fernando Carvalho

3 – Embedded Software Component Quality and Certification: Standardization SQuaRE include: Criteria for the specification of quality requirements Evaluation of quality requirements, Recommended measures of software product quality attributes. which can be used by: Developers, Acquirers, and Evaluators. 13/11/2018 Fernando Carvalho

3 – Embedded Software Component Quality and Certification: Standardization Quality Requirements Division (ISO/IEC 2503n) ISO/IEC , standard for supporting the specification of quality requirements, either during software product quality requirement elicitation or as an input for an evaluation process: Quality requirements and guide: to enable software product quality to be specified in terms of quality requirements; 13/11/2018 Fernando Carvalho

3 – Embedded Software Component Quality and Certification: Standardization Quality Model Division (ISO/IEC 2501n) ISO/IEC – 2005, contains the detailed quality model and its specific characteristics and sub-characteristics for internal quality, external quality and quality in use. This division includes: Quality model and guide: to describe the model for software product internal and external quality, and quality in use. The document present the characteristics and sub-characteristics for internal and external quality and characteristics for quality in use. 13/11/2018 Fernando Carvalho

3 – Embedded Software Component Quality and Certification: Standardization Product Quality General Division (ISO/IEC 2500n) ISO/IEC – 2005 contains the unit standards defining all common models, terms and definitions referred to by all other standards in the SQuaRE series. This division includes two unit standards: Guide to SQuaRE: to provide the SQuaRE structure, terminology, document overview, intended users and associated parts of the series, as well as reference models; Planning and management: to provide the requirements and guidance for planning and management support functions for software product evaluation. 13/11/2018 Fernando Carvalho

3 – Embedded Software Component Quality and Certification: Standardization Quality Measures Division (ISO/IEC 2502n) ISO/IEC were derived from ISO/IEC 9126 and ISO/IEC This division covers the mathematical definitions and guidance for practical measurements of internal quality, external quality and quality in use. It will include the definitions for the measurement primitives and the Evaluation Module to support the documentation of measurements. 13/11/2018 Fernando Carvalho

3 – Embedded Software Component Quality and Certification: Standardization Quality Measures Division (ISO/IEC 2502n) Measurement reference model and guide Measurement primitives Measures for internal quality Measures for external quality Measures for quality in use 13/11/2018 Fernando Carvalho

3 – Embedded Software Component Quality and Certification: Standardization Quality Evaluation Division (ISO/IEC 2504n) ISO/IEC contains the standards for providing requirements, recommendations and guidelines for software product evaluation, whether performed by evaluators, acquirers or developers: Quality evaluation overview and guide Process for developers Process for acquirers Process for evaluators Documentation for the evaluation module 13/11/2018 Fernando Carvalho

ISO/IEC 2501n (Quality Model Division)
3 – Embedded Software Component Quality and Certification: Standardization ISO/IEC 2501n (Quality Model Division) ISO/IEC 2501n is composed of the ISO/IEC standard, which provides a Quality Model for software product. At the present time, this division contains only one standard: – Quality Model and guide. This is an ongoing standard in development. Quality Model Division does not prescribe specific quality requirements for software, but rather defines a generic quality model, which can be applied to every kind of software. 13/11/2018 Fernando Carvalho

3 – Embedded Software Component Quality and Certification: Standardization
Characteristics Sub-Characteristics Functionality Suitability Accuracy Interoperability Security Functionality Compliance Reliability Maturity Fault Tolerance Recoverability Reliability Compliance Usability Understandability Learnability Operability Attractiveness Usability Compliance Efficiency Time Behavior Resource Utilization Efficiency Compliance Maintainability Analyzability Changeability Stability Testability Maintainability Compliance Portability Adaptability Installability Replaceability Coexistence Portability Compliance ISO/IEC 2501n (Quality Model Division) Characteristics and Sub-Characteristics in SQuaRE project The ISO/IEC defines a quality model that comprises six characteristics and 27 sub-characteristics: 13/11/2018 Fernando Carvalho

3 – Embedded Software Component Quality and Certification: Standardization Quality in Use characteristics and are modeled with four characteristics: effectiveness, productivity, security and satisfaction The main drawback of the ISO/IEC 25010, is that they provide very generic quality models and guidelines, which are very difficult to apply to specific domains such as embedded components and CBSD. 13/11/2018 Fernando Carvalho

ISO/IEC 2504n (Quality Evaluation Division) The ISO/IEC 2502n is composed of the ISO/IEC standard, which provides a generic model of an evaluation process, supported by the quality measurements from ISO/IEC This process is specified in four major sets of activities for an evaluation: 13/11/2018 Fernando Carvalho

ISO/IEC 2504n (Quality Evaluation Division) The ISO/IEC 2504n is divided in five standards: ISO/IEC – Evaluation reference model and guide; ISO/IEC – Evaluation modules; ISO/IEC – Evaluation process for developers; ISO/IEC – Evaluation process for acquirers; and ISO/IEC – Evaluation process for evaluators. 13/11/2018 Fernando Carvalho

ISO/IEC 2502n (Quality Measurement Division) The ISO/IEC 2502n improve the quality measurements provided by ISO/IEC /3/4 (external metrics), (internal metrics) and (quality in use metrics) The most significantly is the adoption of the Goal-Question- Metrics (GQM) paradigm (Basili et al., 1994), thus, the metrics definition becomes more flexible and adaptable to the software product evaluation context. 13/11/2018 Fernando Carvalho

ISO/IEC 2502n (Quality Measurement Division) The ISO/IEC 2502n is divided in five standards: ISO/IEC Measurement reference model and guide; ISO/IEC – Measurement primitives; ISO/IEC – Measurement of internal quality; ISO/IEC – Measurement of external quality; and ISO/IEC – Measurement of quality in use. These standards contain some examples in how to define metrics for different kinds of perspectives, such as internal, external and quality in use. 13/11/2018 Fernando Carvalho

3 – Embedded Software Component Quality and Certification: Certification “certification, in general, is the process of verifying a property value associated with something, and providing a certificate to be used as proof of validity”. (Stafford et al., 2001) “Third-party certification is a method to ensure that software components conform to well-defined standards; based on this certification, trusted assemblies of components can be constructed.” (Councill, 2001) 13/11/2018 Fernando Carvalho

3 – Embedded Software Component Quality and Certification: Certification Third party certification is often viewed as a good way of bringing trust in software components. Components can be obtained from existing systems through reengineering, designed and built from scratch, or purchased. After that, the components are certified, in order to achieve some trust level, and stored into a repository system 13/11/2018 Fernando Carvalho

3 – Embedded Software Component Quality and Certification: Certification The CBSE community is still far from reaching a consensus: how it should be carried out, what are its requirements and who should perform it. Some difficulties, was found due to the relative novelty of this area (Goulao et al., 2002a). 13/11/2018 Fernando Carvalho

4 - Embedded software Component Quality Verification Framework
In a survey of the state-of-the-art was noted that there is a lack of processes, methods, techniques and tools available for evaluating component quality, specifically for embedded is much more scarce. This necessity is pointed out by different researchers (Voas, 1998), (Morris et al., 2001), (Wallnau, 2003), (Alvaro et al., 2005), (Bass et al., 2003), (Softex, 2007) and (Lucrédio et al., 2007). Most researchers agree that component quality is an essential aspect of the CBSE adoption and software reuse success. 13/11/2018 Fernando Carvalho

4 - Embedded software Component Quality Verification Framework
Its idea is to improve the lack of consistency between the available standards for software product quality (ISO/IEC 9126), (ISO/IEC 14598), (ISO/IEC 25000), also including the software component quality context and extend it to the embedded domain. These standards provide a high-level definition of characteristics and metrics for software products but do not provide ways to be used in an effective way, becoming very difficult to apply them without acquiring more knowledge from supplementary sources. 13/11/2018 Fernando Carvalho

4.1 - Embedded software Component Quality Verification Framework: Overview
robust framework for software reuse context 13/11/2018 Fernando Carvalho

4.1 - Embedded software Component Quality Verification Framework: Overview The framework will allow that the embedded components produced in a Software Reuse Environment are certified before being stored in a Repository System. The Embedded Software Component Quality Verification Framework is composed of four modules: an Embedded software component Quality Model, a Maturity Level Evaluation Techniques, a Metrics Approach, and a Component Certification Process. 13/11/2018 Fernando Carvalho

4.1 - Embedded software Component Quality Verification Framework: Overview The framework cover two perspectives of the three considered in SQuaRE project : acquirers and evaluators. acquirer’s perspectives is used to define which component best fits the customer’s needs and application/domain context. evaluator’s perspectives should be considered for evaluation required by companies in order to achieve trust in its components. developer’s perspectives is not contemplate, because it very hard for only one developer to execute all activities, independent of his knowledge 13/11/2018 Fernando Carvalho

4.2 - Embedded software component Quality Model (EQM)
The evaluation occurs through models that measure quality These models describe and organize the quality characteristics that will be considered during the evaluation To measure the quality it is necessary to develop a Quality Model The EQM proposed is based on SQuaRE project (ISO/IEC 25000, 2005), with adaptations for components and in embedded domain 13/11/2018 Fernando Carvalho

Some definitions: Quality characteristic is a set of properties by which its quality can be described and evaluated, and refined into sub-characteristics. Attribute is a quality property to which a metric can be assigned. Metric is a procedure for examining a component. Quality model is the set of characteristics and sub-characteristics, that provide the basis for specifying quality requirements and for evaluating quality (Bertoa et al., 2002). 13/11/2018 Fernando Carvalho

Identifying important quality characteristics, classified in different criteria: Local or Global characteristics individual components (local characteristics ) software architecture level (global characteristics). Moment in which it can be measured (Preiss et al.,2001): characteristics at runtime (e. g. Performance) characteristics at cycle-life (e. g. Maintainability). Application Metrics internal metrics (white-box) external metrics (black-box) Marketing characteristics 13/11/2018 Fernando Carvalho

Characteristics Sub-Characteristics Run-time Life cycle Functionality Real-time Accuracy Security Suitability Interoperability Compliance Self-contained Reliability Recoverability Fault Tolerance Safety Maturity Usability Configurability Understandability Learnability Operability Efficiency Time Behavior Resource behavior Scalability Energy consumption Memory utilization Maintainability Analyzability Stability Changeability Testability Portability Deployability Replaceability Flexibility Reusability Marketability Development time Compatibles architectures Cost Time to market Targeted market Affordability Licensing The EQM follow the ISO/IEC 25010, some changes were made to adequate for software components in embedded context. The characteristics : Relevant were maintained; Not interesting was eliminated; The name was changed to adequate it to new context; New important characteristics was added 13/11/2018 Fernando Carvalho

The use of attributes and metrics is used to determine whether a component fulfills in the characteristics and sub-characteristics . The EQM consists of four elements: Characteristics, Sub-characteristics, Attributes and Metrics. A quality characteristic is a set of properties through which its quality can be described and evaluated An attribute is a measurable physical or abstract property of an entity. A metric defines the measurement method and the measurement scale. 13/11/2018 Fernando Carvalho

4.2 - Embedded software component Quality Model (EQM) - Quality Attributes Quality Attributes are observable at runtime and life-cycle. Characteristics Sub- (Runtime) (Life-cycle) Attributes Functionality Real-time Response time (Latency) Throughput (“out”) Processing Capacity (“in”) Execution time Worst case execution time Dead line Accuracy Correctness Security Data Encryption Controllability Auditability Compliance Standardization Certification Self-contained Dependability The table groups the attributes by characteristics and sub-characteristics, and indicates the metrics used for evaluating each attribute. 13/11/2018 Fernando Carvalho

4.2 - Embedded software component Quality Model (EQM) - Quality Attributes Characteristics Sub- (Runtime) (Life-cycle) Attributes Reliability Recoverability Error Handling Fault Tolerance Mechanism availability Mechanism efficiency Safety Environment analyze Integrity Usability Configurability Effort to configure Understandability Efficiency Resource behavior peripheral utilization Energy consumption Data Memory utilization Program Memory utilization 13/11/2018 Fernando Carvalho

4. 2 - Embedded software component Quality
4.2 - Embedded software component Quality Model (EQM) - Quality Attributes Characteristics Sub- (Runtime) (Life-cycle) Attributes Maintainability Stability Modifiability Changeability Extensibility Customizability Modularity Testability Test suite provided Extensive component test cases Component tests in a specific environment Proofs the components tests Portability Deployability Complexity level Replaceability Backward Compatibility Flexibility Mobility Configuration capacity Reusability Domain abstraction level Architecture compatibility Cohesion Coupling Simplicity 13/11/2018

4.2 - Embedded software component Quality Model (EQM) - Quality in Use characteristics The model is complemented with Quality in Use characteristics (ISO/IEC 25000, 2005) are composed of: Productivity, Satisfaction, Security, and Effectiveness. Quality in Use characteristics are useful to show the component’s behavior in different environments, it is measured through the customer’s feedback Bring relevant information for new customers, This is the user’s view of the component, Obtained when the component in an execution environment, and Analyze the results according to their expectations. 13/11/2018 Fernando Carvalho

Relevant Component Information
4.2 - Embedded software component Quality Model (EQM) - Additional Information Relevant Component Information The Additional Information characteristics complement the model and are composed of: Technical Information is important for developers to analyze the actual state of the component , Organization Information is important to know who is the responsible for that component. Additional Information Technical Information Component Version Programming Language Patterns Usage Architecture compatible Program Memory used Technical Support Organization Information CMMi Level Organization’s Reputation 13/11/2018 Fernando Carvalho

4.3 - Maturity Level Evaluation Techniques
The quality characteristics proposed not need to be evaluated with the same degree of details and depth for all types of application. (E. g. evaluation of a component used in railway system and game). Different evaluation levels must be used in order to provide degree of confidence for different domains and risk-levels. 13/11/2018 Fernando Carvalho

Embedded software component Maturity Model (EMM) The Details of an evaluation is a reflex of the evaluation techniques used. So, an Embedded software component Maturity Model (EMM) was defined. It is based on CMMI (CMMI, 2000) and model for general propose component (Alvaro et al., 2007a). 13/11/2018 Fernando Carvalho

The EMM is constituted of five hierarchical levels of quality characteristics where the components can be evaluated in different the depth of the evaluation gives different degrees of confidence. Each company/customer decides which level is better for evaluating its components, analyzing the cost/benefits of each level. The evaluation levels can be chosen independently for each characteristic (e.g. functionality → EMM I, reliability → EMM III, usability → EMM IV). 13/11/2018 Fernando Carvalho

Guidelines for selecting evaluation level Level Environment Safety/Security Economic Domain EMM I No damage Few material damage; No specific risk Negligible economic loss Entertainment, EMM II Small/Medium damage properly Few people disabled Few economic loss household EMM III Damage properly Large number of people disabled Significant economic loss Security, Control systems EMM IV Recoverable environment damage Threat to human lives Large economic gross Medical, Financial EMM V Unrecoverable environmental damage Many people killed Financial disaster Transportation, Nuclear systems 13/11/2018 Fernando Carvalho

The levels and the evaluation techniques selection of EMM must be appropriated to evaluate the quality attributes proposed on the EQM A relation EQM - Quality Attributes X Evaluation Technique - EMM is necessary. The objectve is not to propose a large amount of isolated techniques, but to propose a set of techniques that are essential for measuring each quality attribute, complementing each other and, thus, becoming useful to compose the Maturity Level Evaluation Techniques. 13/11/2018 Fernando Carvalho

Characteristics EMM I EMM II EMM III EMM IV EMM V Functionality Time constraint analysis Requirements and Documentation Analysis Accuracy analysis Evaluation measurement (Time analysis) Functional Testing (black box), Unit Test, Regression Test (if possible) System Test Documents Inspection (check list) Code Inspection Functional Tests (white-box) with coverage criteria and code inspection Formal Proof Reliability Dependability analysis Suitability analysis Programming Language Facilities (Best Practices) Error Manipulation analysis Fault tolerance analysis Error Injection analysis Error recover Reliability growth model Usability Effort to Configure analysis Documentation analysis (Use Guide, architectural analysis, etc) Interfaces inspection provided and required Code and component’s interface inspection correctness and completeness) Analysis of the pre and post-conditions of the component User mental model Efficiency Constraint analyses Evaluation measurement (memory, power and resource) Memory Analysis Power consumption Analysis Resource Analysis Tests of performance(memory, power and resource) Algorithmic complexity Performance optimization (memory, power and resource) Performance profiling analysis Maintainability Customizability analysis Extensibility analysis Inspection of Documents Analysis of the provided test suite (if exists) Code metrics and programming rules Static Analysis Analysis of the component development process Traceability evaluation Component Test Formal Proof Portability Component execution in specific environment and architectural analysis Cohesion, Coupling, Modularity and Simplicity analyses Cohesion of the documentation with the source code analysis Deployment analysis Backward compatibility Mobility analysis Configurable analysis Hardware/Software analysis Conformity to programming rules Environment and architectural constraints evaluation Domain abstraction analysis Analysis of the component’s architecture 13/11/2018 Fernando Carvalho

Charac- teristic Sub- Characteristics Quality Attributes Evaluation Techniques Functionality Real-Time Response time (Latency) Throughput (“out”) Processing Capacity (“in”) • Evaluation measurement (Time analysis) • Time constraint analysis • Formal Proof Execution time • Evaluation measurement Worst case execution time • System Test Dead line Accuracy Correctness • Requirements and Documentation Analysis • Accuracy analysis • Functional Testing (black box),Unit Test, Regression Test (if possible) • Functional Tests (white-box) with coverage criteria Security Data Encryption • Code Inspection Controllability Auditability Compliance Standardization • Inspection of Documents Certification Self-contained Dependability • Documents Inspection 13/11/2018 Fernando Carvalho

Charac- teristic Sub- Characteristics Quality Attributes Evaluation Techniques Reliability Recoverability Error Handling • Programming Language Facilities (Best Practices) • Error Manipulation analysis • Error Injection analysis • Error recover • Reliability growth model • Formal Proof Fault Tolerance Mechanism available • Suitability analysis • Dependability analysis Mechanism efficiency • Error injection analysis • Fault tolerance analysis Safety Environment analyze • Environment analyses • System analyses Integrity 13/11/2018 Fernando Carvalho

Charac- teristic Sub- Characteristics Quality Attributes Evaluation Techniques Usability Configurability Effort for configure • Effort to Configure analysis • Interfaces inspection provided and required • Code and component’s interface inspection correctness and completeness) • Analysis of the pre and post-conditions of the component • User mental model Understandability Documentation analysis (Use Guide, architectural analysis, etc) 13/11/2018 Fernando Carvalho

Charac- teristic Sub- Characteristics Quality Attributes Evaluation Techniques Efficiency Resource Behavior peripheral utilization • Constraint analyses • Evaluation measurement • Resource Analysis • Tests of performance • Performance optimization • Performance profiling analysis • Formal Proof Energy consumption Mechanism available • Power consumption analysis Data Memory Utilization • Memory analysis Program Memory Utilization 13/11/2018 Fernando Carvalho

Charac- teristic Sub- Characteristics Quality Attributes Evaluation Techniques Maintainability Stability Modifiability • Code metrics and programming rules • Inspection of Documents • Static Analysis Changeability Extensibility • Effort for operating • Extensibility analysis Customizability • Customizability analysis Modularity • Code metrics and programming rule Testability Test suit provided • Analysis of the test-suite provided (if exists) Extensive component test cases • Analysis of the component development process Component tests in a specific environment • Traceability evaluation Proofs the components test • Component Test Formal Proof 13/11/2018 Fernando Carvalho

Charac- teristic Sub- Characteristics Quality Attributes Evaluation Techniques Portability Deployability Complexity level • Component execution in specific environments and architectural analysis • Deployment analyses • Environment and architectural constraints evaluation Replaceability Backward Compatibility • Backward compatibility analysis Flexility Mobility • Mobility analyses Configuration capacity • Configuration analyses Reusability Domain abstraction level • Cohesion of the documentation with the source code analysis • Domain abstraction analysis Architecture compatibility • Conformity to programming rules • Analysis of the component’s architecture • Hardware/Software analysis Modularity • Modularity analyses Cohesion • Cohesion analyses Coupling • Coupling analyses Simplicity • Simplicity analyses 13/11/2018 Fernando Carvalho

4.4 - Metrics Approach As with any engineering, software development requires a measurement mechanism for feedback, evaluation, creating a corporate memory and improve of software process (Basili et al., 1994). Measurement Objectives: to assess a project progress, to take corrective action based on this assessment, and to evaluate the impact of such action Helps of Measurement Helps support project planning Allow to determine the strengths and weaknesses of processes/products Provides a rationale for adopting/refining techniques Allows to evaluate the quality of specific processes/products 13/11/2018 Fernando Carvalho

4.4 - Metrics Approach There are a variety of mechanisms for measurable goals in the literature: The Quality Function Deployment approach (Kogure & Akao, 1983), The Goal Question Metric approach (Basili et al., 1994), (Basili, 1992), (Basili & Rombach, 1988), (Basili & Selby, 1984), (Basili & Weiss, 1984), and The Software Quality Metrics approach (Boehm et al., 1976), (McCall et al., 1977). In this Framework the Goal-Question-Metric (GQM) approach was adopted, which was the same technique proposed to use in ISO/IEC looking for track the software product properties. 13/11/2018 Fernando Carvalho

4.4 - Metrics Approach The Goal Question Metric (GQM) approach is based upon the assumption that for to measure in a purposeful way it must : Specify the goals for itself and its projects, Must trace those goals to the data that are intended to define those goals operationally, and Provide a framework for interpreting the data with respect to the goals. 13/11/2018 Fernando Carvalho

4.4 - Metrics Approach The resulting measurement model has three levels: Conceptual level - GOAL: A goal is defined for an object(product, process, resource) Operational level - QUESTION: A set of questions is used to characterize the way the assessment/achievement of a specific goal Quantitative level - METRIC: A set of data is associated with every question in order to answer it in a quantitative way (Objective/Subjective) Summarized, A GQM model is starting with a goal. The goal is refined into several questions. Each question is then refined into metrics, some of them objective, some of them subjective. 13/11/2018 Fernando Carvalho

4.4 - Metrics Approach The GQM approach allow metrics to track the properties of: Quality attributes of EQM, Evaluation techniques of EMM, and Certification process (i)Metrics to track the EQM Properties Objective Metric Functionality Sub-Characteristic Accuracy Quality Attribute Correctness Goal Evaluates the percentage of the results that were obtained with precision Question Based on the amount of tests executed, how much test results return with precision? Metric Precision on results / Amount of tests Interpretation 0 <= x <= 1; which closer to 1 is better Usability Sub-Characteristic Configurability Quality Attribute Effort to Configure Goal Evaluates the time necessary to configure the component. Question How much time is needed to configure the component in order to work correctly in a system? Metric Time spent to configure correctly Interpretation The faster it is to configure the component the better, but it depends of the component and environment complexity. Subjective 13/11/2018 Fernando Carvalho

4.4 - Metrics Approach (ii) Metrics to track the EMM Properties
Portability Quality Attribute Coupling, Cohesion, Simplicity, Reusability and Modularity analyzes EMM level I Technique Coupling, Cohesion, Simplicity, Reusability, Modularity analyzes using Checkstyle tool[2] Goal Evaluates the internal source code of the component Question Is the Checkstyle tool efficient enough to measure those attributes? Metric Analysis of the results and coverage of the Tool Interpretation If the tool can mine these kinds of information from the source code and present them to be analyzed, it is good to evaluate the component. On the other hand, if it is not enough to evaluate some kind of attributes, other tool should be use to complement or to substitute this one. If this tool is good to evaluate the component, an analysis of the metrics collected in the tool can be used to define those attributes from the component. The idea is that the component should have: less coupling, high cohesion, high modularity, ways to perform the function in a simple way and high reusability. Each technique can be measured in different ways and complexity, using different tools, techniques, methods and processes. [2] Checkstyle – 13/11/2018 Fernando Carvalho

Component Certification Process Component Certification Process
4.4 - Metrics Approach (iii) Metrics to track the Certification Process Properties Component Certification Process Goal Adequately evaluate the software component embedded Question Could the evaluation team evaluate everything they planned to execute using the documents developed during the process activities? Metric Total documented functionalities / Total component functionalities (or Total measurement accomplished) Interpretation 0 <= x <= 1; which closer to 1 is better The idea is to obtain feedback from those metrics in order to improve the activities and steps to assure the efficiency and efficacy of the process Component Certification Process Goal Analyze the usability of the templates provided Question Has the template helped during the certification development? Metric Evaluation team feedback Interpretation If the template helped during the certification development it is good, if not it should be adapted to improve the time of the component certification process. The evaluation team should define metrics as much as they think interesting in order to measure the process capacity 13/11/2018 Fernando Carvalho

4.5 - Component Certification Process
The Component Certification Process is the default process adopted for embedded component certification in robust framework for software reuse (Almeida et al., 2004). It define a set of activities in order to guide the evaluation team during the component evaluation, and It could be repeatable and reproducible, each activity contains a well-detailed description: inputs and outputs, mechanisms to execute, and to control. 13/11/2018 Fernando Carvalho

The process is based on SQuaRE project, which provides guidance and requirements for the software product evaluation. A set of works from literature which includes processes for software product evaluation and processes for software component assessment aid during the definition of this process (McCall et al., 1977) , (Boegh et al., 1993), (Beus-Dukic et al., 2003), (Comella-Dorda et al., 2002) 13/11/2018 Fernando Carvalho

A set of activities to guide the evaluation team during the evaluation were proposed, which is presented using SADT notation (Ross, 1997). 13/11/2018 Fernando Carvalho

Establish Evaluation Requirements activity 13/11/2018 Fernando Carvalho

Specify the Evaluation activity 13/11/2018 Fernando Carvalho

Design the Evaluation 13/11/2018 Fernando Carvalho

Execute the Evaluation 13/11/2018 Fernando Carvalho

4. 5 - Component Certification Process
The evaluation team can describe a set of suggestions in order to improve the quality of the component. This information is important in the case that the component is approved and, much more interesting if the component is rejected. The evaluation team is the main responsible for executing this process and should be carefully defined in order to assure that the certification will be efficiently developed. 13/11/2018 Fernando Carvalho

5 - Conclusion The demands that industries in embedded system includes: low production costs, short time to market, and high quality. Assessment and evaluation of software components has become a compulsory and crucial part of any CBSD Assessment and evaluation of software components lifecycle. addressed by CBD approach Para Permitir a correta Avaliação de comp de sw emb To properly enable the evaluation of embedded software components, supplying the real necessities of the embedded system design of building system fast, cheap and high quality systems, an Embedded software Component Quality Verification Framework is mandatory. 13/11/2018 Fernando Carvalho

4.6 – Experimental Study An experimental process can be divided into the following main activities (Wohlin et al., 2000): Definition (problem, objective and goals), Planning (design, instrumentation and threats), Operation (measurements are collected) , Analysis and Interpretation (data are analyzed and evaluated), Presented and Packaged (results are presented and packged) Definition, Planning activities will be presented. The complete experiment study will be accomplished and described in next year. Para Permitir a correta Avaliação de comp de sw emb 13/11/2018 Fernando Carvalho

4.6 – Experimental Study - Definition
According to GQM Paradigm(Basili et al., 1986), the main objective of experimental study is to: Analyze the capacity to evaluate the quality of embedded software component for the propose of evaluating embedded software component quality verification framework with respect to the efficiency of the framework from the point of view of the researchers, software and quality engineers (customers, evaluators) in the context of the embedded software component quality area. Para Permitir a correta Avaliação de comp de sw emb 13/11/2018 Fernando Carvalho

4.6 – Experimental Study - Planning
Context – To evaluate the efficiency of framework based a set of embedded component (project between industry and university). Training - The training of the subjects using the process will be conducted in a classroom at the university Pilot Project - Before the study, a pilot project will be conducted, aiming to detect problems and improve the planned material. Selection of Subjects - Ten students of pos-graduation at UFPE were selected by convenience sampling. Subjects - According to its skills and technical knowledge to evaluate the embedded software components. Instrumentation - the subjects will receive a questionnaires about his/her education, experience and satisfaction using the framework, and chapters 4 of this Thesis. Para Permitir a correta Avaliação de comp de sw emb 13/11/2018 Fernando Carvalho

Criteria - evaluate quantitatively the real efficiency of the framework and the difficulty of the framework usage. (i) coverage of the EQM, (ii) EMM; and (iii) subjects difficulty to use the framework). Hypothesis is to know and to formally state what is going to be evaluated - Null hypotheses, H0: determine that the framework is not efficient and it is very difficulty to use: Ho’: coverage of the component quality attributes proposed in the CQM X the quality attributes used during the component evaluation < 90% Ho’’: coverage of the evaluation techniques proposed on the SCMM for the quality attributes defined during the component evaluation < 90% Ho’’’: %Subjects that had difficulty to understand, follow and use the Software Component Quality Framework > 20% Alternative hypotheses: determine that the framework is efficient and it is easy to use: Ho’: coverage of the component quality attributes proposed in the CQM X the quality attributes used during the component evaluation >= 90% Ho’’: coverage of the evaluation techniques proposed on the SCMM for the quality attributes defined during the component evaluation >= 90% Ho’’’: %Subjects that had difficulty to understand, follow and use the Software Component Quality Framework <= 20% Para Permitir a correta Avaliação de comp de sw emb 13/11/2018 Fernando Carvalho

Independent Variables -the education and the experience of the subjects, Dependent Variable - the quality of the EQM and EMM developed and the usability of the framework Qualitative Analysis - aims to evaluate the difficulty of the application of the framework and the quality of the material used in the study Randomization - This technique can be used in the selection of the subjects, however, the subjects were selected by convenience sampling Blocking - not identified the necessity of dividing the subjects into blocks Balancing - it is not necessary to divide the subjects, since there is only one group Internal Validity - this study is supposed to have at least between four to eight subjects to guarantee a good internal validity. Para Permitir a correta Avaliação de comp de sw emb 13/11/2018 Fernando Carvalho

External Validity - is considered sufficient, since it aims to evaluate the viability of the application of proposed framework. Construct Validity - A relative well-know project will be used (i.e. the experimenter have about three years of experience). This choice avoids previous experience of making a wrong interpretation of the impact of the proposed framework. Validity of the Conclusion of the Study - This conclusion will be drawn by the use of descriptive statistic. Para Permitir a correta Avaliação de comp de sw emb The project used in the experimental study was the embedded software components used in cars tracking system developed in a partnership between industry, academy and a research institute. 13/11/2018 Fernando Carvalho

5 - Conclusion Contributions To demonstrate that component certification is: Possible, Practically viable, and Applicable in the embedded system industry. To show the challenge and specific requirements of the use CBD approach for embedded systems in different domain; the realization of a survey related to the state-of-the-art in embedded software component quality and certification research; To enable the quality component verification and certification for a Robust Software Framework Reuse (Almeida et al.2004), and To Assess and To evaluate quality of embedded software components Para Permitir a correta Avaliação de comp de sw emb 13/11/2018 Fernando Carvalho

5 - Conclusion To demonstrate that component certification is: Possible, Practically viable, and Applicable in the embedded system industry. To show the challenge and specific requirements of the use CBD approach for embedded systems in different domain; the realization of a survey related to the state-of-the-art in embedded software component quality and certification research; To enable the quality component verification and certification for a Robust Software Framework Reuse (Almeida et al.2004), and To Assess and To evaluate quality of embedded software components Para Permitir a correta Avaliação de comp de sw emb 13/11/2018 Fernando Carvalho

5 - Future works During the research it was perceived that there are needs for a number of improvements. Some of them are the following: Component Certification Center - component certification standard for Software Factories Tool Support - it is needed a tool support in order to aid the usage of the proposed processes, methods, techniques, etc Risk and Cost/Benefit Management Model the risk and cost/benefit Model analyze if the costs are acceptable and viable or not. Para Permitir a correta Avaliação de comp de sw emb 13/11/2018 Fernando Carvalho

5 - Chronogram The research work to perform up until the defense of the thesis can be divided into five distinct activity Activity Deadline Deliverable Suggest and review metrics for remaining quality attributes Jan 16 - Jan Define a document/form model for register embedded component evaluation 30 - Jan Finalization of case of study for proposed framework evaluation 13 - Feb Completion of doctoral thesis 1 - Mar Doctoral thesis defense 27 - Mar Para Permitir a correta Avaliação de comp de sw emb 13/11/2018 Fernando Carvalho

Fernando F. de Carvalho ffc@cin.ufpe.br
Thank you ! Questions ? Fernando F. de Carvalho 13/11/2018 Fernando Carvalho

A Embedded software component quality verification framework

Similar presentations

Presentation on theme: "A Embedded software component quality verification framework"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

A Embedded software component quality verification framework

Similar presentations

Presentation on theme: "A Embedded software component quality verification framework"— Presentation transcript:

Similar presentations

About project

Feedback