Related QAs: usability, portability, integration Constituent: UI framework
Stakeholder: primary users
Description: The system must support a consistent look and feel between different in-terfaces and applications of the different constituents.
Related QAs: usability, portability, integration Constituent: HIC system
Stakeholder: primary users
Description: The system must use consistent colours, shapes and symbols together with natural language and vocabulary familiar to the user.
QM4AAL: Quality Model for AAL Systems
Related QAs: usability, portability, integration Constituent: UI framework
Stakeholder: primary users
Description: The system must use specific usability standards for the appropriate focus group (assisted persons).
71 71 71
Chapter 7
Final Considerations
The development of quality AAL systems carries significant challenges because the hetero-geneity of their constituent systems, their adaptive properties, and the variety of stakeholders involved in their creation. In this perspective, the QM4AAL offers a repository of QAs re-quirements for both AAL systems and their constituents systems.
Moreover, the three-dimensional structure of the QM4AAL allows to represent QAs requirements for AAL systems’ constituents in a way that such representation be a QM specific of the constituent system. Hence, such QM permits the definition of adaptive prop-erties, stakeholders, and related QAs for each constituent systems. As an example, figure 7.1 illustrates the structure of a QM for a health status monitoring system. In this con-text, the QM4AAL can be used to define and assess both AAL systems as a whole, as their constituent systems as independent systems.
Figure 7.1: QM for the AAL system’s constituent: health status monitoring system.
73
Future work
We are aware that the QM4AAL needs important improvements that will be carried out as future work. In the QM4AAL next versions more constituent systems will be considered, e.g., tele-medicine, nutritional, and rehabilitation systems. Moreover, the QM4AAL will be under experts assessment of both ITC and medical area, in order to prioritize QAs. Fi-nally, the QM4AAL will be used to create a reference architecture and software systems to evaluate its correctness.
Acknowledgment
This work is supported by the Brazilian funding agency FAPESP (Grants N.: 2015/19192-2, 2014/02244-7 and 2013/20317-9).
Appendix A
Quality attributes definitions
In this appendix we present the definitions for quality attributes. Such definitions were extracted from the standard ISO/IEC 25010 [11]. Moreover, we define those QAs that are not comprised by the standard.
75
ISO/IEC 25010 QUALITY ATTRIBUTES DEFINITIONS Functional suitability Functional completenessdegree to which the set of functions covers all the specified tasks and user objectives Functional correctnessdegree to which a product or system provides the correct results with the needed degree of precision Functional appropriatenessdegree to which the functions facilitate the accomplishment of specified tasks and objectives RELIABILITY
Reliability Maturitydegree to which a system meets needs for reliability under normal operation Availabilitydegree to which a system, product or component is operational and accessible when required for use Fault tolerance Recoverability Performance efficiencyperformance relative to the amount of resources used under stated conditions Time behaviour Resource utilization Capacitydegree to which the maximum limits of a product or system parameter meet requirements USABILITY
Usability Appropriateness recognisabilitydegree to which users can recognize whether a product or system is appropriate for their needs Learnability Operabilitydegree to which a product or system has attributes that make it easy to operate and control User error protectiondegree to which a system protects users against making errors User interface aestheticsdegree to which a user interface enables pleasing and satisfying interaction for the user Accessibility
PRODUCT QUALITY FUNCTIONAL SUITABILITY
degree to which a product or system provides functions that meet stated and implied needs when used under specified conditions degree to which a system, product or component performs specified functions under specified conditions for a specified period of time. degree to which a system, product or component operates as intended despite the presence of hardware or software faults degree to which, in the event of an interruption or a failure, a product or system can recover the data directly affected and re-establish the desired state of the system PERFORMANCE EFFICIENCY
degree to which the response and processing times and throughput rates of a product or system, when performing its functions, meet requirements degree to which the amounts and types of resources used by a product or system when performing its functions meet requirements degree to which a product or system can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use degree to which a product or system can be used by specified users to achieve specified goals of learning to use the product or system with effectiveness, efficiency, freedom from risk and satisfaction in a specified context of use degree to which a product or system can be used by people with the widest range of characteristics and capabilities to achieve a specified goal in a specified context of use
QM4AAL: Quality Model for AAL Systems
ISO/IEC 25010 QUALITY ATTRIBUTES DEFINITIONS MAINTAINA- BILITY
Maintainabilitydegree of effectiveness and efficiency with which a product or system can be modified by the intended maintainers Modularity Reusabilitydegree to which an asset can be used in more than one system, or in building other assets Analysability Modifiability Testability SECURITY
Security Confidentialitydegree to which a product or system ensures that data are accessible only to those authorized to have access Integrity Non-repudiation Accountabilitydegree to which the actions of an entity can be traced uniquely to the entity Authenticitydegree to which the identity of a subject or resource can be proved to be the one claimed COMPATIBILITY
Compatibility Co-existence Interoperability
PRODUCT QUALITY
degree to which a system or computer program is composed of discrete components such that a change to one component has minimal impact on other components degree of effectiveness and efficiency with which it is possible to assess the impact on a product or system of an intended change to one or more of its parts, or to diagnose a product for deficiencies or causes of failures, or to identify parts to be modified degree to which a product or system can be effectively and efficiently modified without introducing defects or degrading existing product quality degree of effectiveness and efficiency with which test criteria can be established for a system, product or component and tests can be performed to determine whether those criteria have been met degree to which a product or system protects information and data so that persons or other products or systems have the degree of data access appropriate to their types and levels of authorization degree to which a system, product or component prevents unauthorized access to, or modification of, computer programs or data degree to which actions or events can be proven to have taken place, so that the events or actions cannot be repudiated later degreetowhicha product, systemor component can exchange information withother products, systems or components, and/or perform its required functions, while sharing the same hardware or software environment degree to which a product can perform its required functions efficiently while sharing a common environment and resources with other products, without detrimental impact on any other product degree to which two or more systems, products or components can exchange information and use the information that has been exchanged
77 77 77
ISO/IEC 25010 QUALITY ATTRIBUTES DEFINITIONS PORTABILITY
Portability Adaptability Installability Replaceability SATISFACTION
Satisfactiondegree to which user needs are satisfied when a product or system is used in a specified context of use Usefulness Trustdegree to which a user or other stakeholder has confidence that a product or system will behave as intended Pleasuredegree to which a user obtains pleasure from fulfilling their personal needs Comfortdegree to which the user is satisfied with physical comfort EFFECTIVENESSEffectivenessaccuracy and completeness with which users achieve specified goals Freedom for risk Economic risk mitigation Health and safety risk mitigationdegree to which a product or system mitigates the potential risk to people in the intended contexts of use Environmental risk mitigation EFFICIENCYEfficiencyresources expended in relation to the accuracy and completeness with which users achieve goals Context coverage Context completeness Flexibility
PRODUCT QUALITY
degree of effectiveness and efficiency with which a system, product or component can be transferred from one hardware, software or other operational or usage environment to another degree to which a product or system can effectively and efficiently be adapted for different or evolving hardware, software or other operational or usage environments degreeof effectiveness andefficiency withwhichaproductor systemcanbesuccessfully installed and/or uninstalled in a specified environment degree to which a product can be replaced by another specified software product for the same purpose in the same environment QUALITYIN USE degree to which a user is satisfied with their perceived achievement of pragmatic goals, including the results of use and the consequences of use FREEDOMFOR RISK
degree to which a product or system mitigates the potential risk to economic status, human life, health, or the environment degree to which a product or system mitigates the potential risk to financial status, efficient operation, commercial property, reputation or other resources in the intended contexts of use degree to which a product or system mitigates the potential risk to property or the environment in the intended contexts of use CONTEXT COVERAGE degree to which a product or system can be used with effectiveness, efficiency, freedom from risk and satisfaction in both specified contexts of use and in contexts beyond those initially explicitly identified degree to which a product or system can be used with effectiveness, efficiency, freedom from risk and satisfaction in all the specified contexts of use degree to which a product or system can be used with effectiveness, efficiency, freedom from risk and satisfaction in contexts beyond those initially specified in the requirements
QM4AAL: Quality Model for AAL Systems
OTHERS QUALITY ATTRIBUTES DEFINITIONS Adaptivity Cooperationdegree to which a product or system can exchange requests among classes and instances in order to achieve some goal. Deployabilityaddresses how reliably and easily software can be deployed from development into the production environment. Scalabilityability to handle increased workload by repeatedly applying a cost-effective strategy for extending a system’s capacity. Dependability ConfigurabilityAddresses how hardware and software of an information processing system are organized and interconnected.
degree to which a product or system can effectively and efficiently be adapted in run-time for different or evolving hardware, software or other operational or usage environments Measure of the degree to which an item is operable and capable of performing its required function at any (random) time during a specified mission profile, given item availability at the start of the mission. Reliability, availability, and maintainability are aspects of dependability.
79 79 79
Appendix B
List of quality attributes from AAL software systems
Table B.1 lists the 97 quality attributes that were found at conducting the systematic review about quality attributes and quality models for AAL software systems [14]. Columns from S1 to S17 represent the primary studies analyzed to extract the information on QAs for AAL systems. For more information on studies please referred to [14].
81
TableB.1:Listofqualityattributes IDAttributesS1S2S3S4S5S6S7S8S9S10S11S12S13S14S15S16S17(#)(%) 1Safety1111111111952,9 2Security111111111952,9 3Usability111111111952,9 4Availability11111111847,1 5Efficiency1111111741,2 6Reliability1111111741,2 7Accuracy111111635,3 8Robustness111111635,3 9Maintainability11111529,4 10Accessibility1111423,5 11Adaptivity1111423,5 12Confidentiality1111423,5 13Integrity1111423,5 14Resourceconsumption1111423,5 15Timeliness1111423,5 16Effectiveness111317,6 17Extensibility111317,6 18Installability111317,6 19Natural,anticipatoryHCI1111317,6 20Performance111317,6 21Usefulness111317,6 22Useracceptance111317,6 23Acceptability11211,8 24Adaptability11211,8 25Adequacyforsmalldevices11211,8 26Certainty11211,8 27Changeability11211,8 28Communicationoverhead11211,8 29Easeofuse11211,8 30Encryption11211,8 31Flexibility11211,8 32Heterogeneity11211,8 33Integrability11211,8 Continuedonnextpage 1 HumanComputerInteraction
QM4AAL: Quality Model for AAL Systems
TableB.1–Continuedfrompreviouspage IDAttributesS1S2S3S4S5S6S7S8S9S10S11S12S13S14S15S16S17(#)(%) 34Interoperability11211,8 35Learnability11211,8 36Portability11211,8 37PresenceofSPoF211211,8 38Privacy11211,8 39Productivity11211,8 40Profiledefinition11211,8 41Recoverability11211,8 42Safetypatternusage11211,8 43Satisfaction11211,8 44Suitability11211,8 45Userrole11211,8 46Analysability115,9 47Authentication115,9 48Awareness115,9 49Compatibilitywithstandards115,9 50Completeness115,9 51Conformity115,9 52Contextconsistency115,9 53Contextcorrectness115,9 54Contextualknowledge115,9 55Datavolume115,9 56Delaytime115,9 57Dependability115,9 58Developmenttimeandcost115,9 59Easeofmaintenance115,9 60Evolvability115,9 61Extrapolation115,9 62Feasibility115,9 63Fulfilment115,9 64Functionality115,9 65Generality115,9 66Identification115,9 Continuedonnextpage 2 SinglePointofFailure
83 83 83
TableB.1–Continuedfrompreviouspage IDAttributesS1S2S3S4S5S6S7S8S9S10S11S12S13S14S15S16S17(#)(%) 67Informationprocessing115,9 68Interfacecompatibility115,9 69Invisibility115,9 70Manageability115,9 71Modifiability115,9 72Multiuser115,9 73Obtrusivenessorintegration115,9 74Personalization115,9 75Precision115,9 76Proceedingspeed115,9 77Qualityofdata115,9 78Relevance115,9 79Replicability115,9 80Responsiveness115,9 81Reusability115,9 82Run-timebehavior115,9 83Scalability115,9 84Self-configuration115,9 85Self-maintenance115,9 86Self-optimization115,9 87Stability115,9 88Sustainability115,9 89Testability115,9 90Timeaccuracy115,9 91Trustfulness115,9 92Universalaccess115,9 93Universality115,9 94Unobstrusiveness115,9 95Upgradability115,9 96Usercentric115,9 97User’sautonomy115,9 Totalbystudy131010131016471113914103162228
Appendix C
List of quality attributes from Reference Architectures for AAL systems
85
QA IDQAPSCIAmIRAFeelGoodOASISContinuaPersonaButlersUniversAAL( # ) QARA001Ability of easy integration11 QARA002Accessibility1113 QARA003Accountability11 QARA004Accuracy11 QARA005Adaptability112 QARA006Adaptation112 QARA007Adaptivity1113 QARA008Adequacy for small devices11 QARA009Assurance11 QARA010Authentication11 QARA011Authorization112 QARA012Availability112 QARA013Awareness11 QARA014Changeability11 QARA015Compliance to standards11 QARA016Composability11 QARA017Confidentiality11 QARA018Confidentiality in the infor.112 QARA019Configurability11 QARA020Context awareness1113 QARA021Cooperation11 QARA022Data authenticity11 QARA023Data quality11 QARA024Dependability11 QARA025Deployability11 QARA026Device authenticity11 QARA027Disaster recovery11 QARA028Easy development11 QARA029Easy interaction11 QARA030Efficiency11 QARA031Encryption mechanism11 QARA032Extendibility112 QARA033Fault tolerance11
QM4AAL: Quality Model for AAL Systems
QA IDQAPSCIAmIRAFeelGoodOASISContinuaPersonaButlersUniversAAL( # ) QARA034Flexibiity1113 QARA035Heterogenity11 QARA036Identification11 QARA037Installability112 QARA038Integration11114 QARA039Integrity112 QARA040Intelligent11 QARA041Interaction11 QARA042Interoperability111111118 QARA043Learnability11 QARA044Maintainability1113 QARA045Modifiability11 QARA046Modularity11 QARA047Natural interaction11 QARA048Non-repudiation112 QARA049Operability11 QARA050Patient safety11 QARA051Performance1113 QARA052Personalization11 QARA053Portability112 QARA054Privacy11114 QARA055Quality of service11 QARA056Relevance11 QARA057Reliability1113 QARA058Reliable authentication11 QARA059Resource management11 QARA060Reusability11 QARA061Richness11 QARA062Robustness112 QARA063Safety11 QARA064Satisfaction11 QARA065Scalability1111116 QARA066Seamless connectivity11
87 87 87
QA IDQAPSCIAmIRAFeelGoodOASISContinuaPersonaButlersUniversAAL( # ) QARA067Seamlessly11 QARA068Security11114 QARA069Security profile definition11 QARA070Self-adaptive11 QARA071Self-configuration11 QARA072Simplicity112 QARA073Testability11 QARA074Trustability1113 QARA075Trustworthy11 QARA076Ui aesthetics11 QARA077Unauthorized modifications11 QARA078Understandability11 QARA079Usability11114 QARA080Usefulness11 QARA081User authenticity11 QARA082User error protection11 QARA083User interaction11 Total by study71981219141541
Bibliography
[1] Aguiar, A., Filho, S.J., Magalhães, S.J., Casagrande, T.D., & Hessel, F. Hellfire: A design framework for critical embedded systems’ applications. In ISQED ’10: 11th International Symposium on Quality Electronic Design, pp. 730–737 (2010).
[2] Antonino, P.O., Schneider, D., Hofmann, C., Nakagawa, E.Y.: Evaluation of AAL platforms according to architecture-based quality attributes. Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics), 7040 LNCS, pp. 264–274 (2011).
[3] Broek, G.V.D., Cavallo, F., Wehrmann, C.: AALIANCE Ambient Assisted Living Roadmap. IOS Press, Amsterdam, The Netherlands (2010).
[4] Buchmayr, M., Kurschl, W.: A survey on situation-aware ambient intelligence systems.
Journal of Ambient Intelligence and Humanized Computing, 2(3),175–183 (2011).
[5] Cloutier, R., Muller, G., Verma, D., Nilchiani, R., Hole, E., Bone, M.: The Concept of Reference Architectures. Syst. Eng.. 13(1),14?27 (2010).
[6] Deissenboeck, F., Juergens, E., Lochmann, K., & Wagner, S. (2009). Software quality models: Purposes, usage scenarios and requirements. In ICSE ’09: 7th International Conference on Software Engineering(pp. 9–14).
[7] International standard ISO/IEC/IEEE 24765 (2010). Systems and software engineering – Vocabulary (First edition).
[8] McCall, J.A., Richards, P.K., & Walters, G.F. (1977). Factors in Software Quality.
Technical report, General Electric Co, Sunnyvale, CA.
[9] Boehm,B.W., Brown, J.R., & Lipow, M. (1976). Quantitative evaluation of software quality. In2nd International Conference on Software Engineering(pp. 592–605).
[10] ISO/IEC 9126-1 (2001). Software engineering – Product quality. http:
//www.iso.org/iso/catalogue\_detail.htm?csnumber=22749. Ac-cessed 18th July 2014.
89
[11] ISO/IEC 25010 (2011). Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) - System and software quality models.
[12] ISO/IEC 25012 (2008). Software engineering – Software product Quality Require-ments and Evaluation (SQuaRE) – Data quality model https://http://www.
iso.org/iso/catalogue_detail.htm?csnumber=35736. Accessed 20th August 2015.
[13] Garcés, L., Ampatzaglou, A., Avgeriou, P., and Nakagawa, E.Y.: A Comparative Anal-ysis of Reference Architectures for Healthcare in the Ambient Assisted Living Domain.
In Proceedings of the 28th International Symposium on Computer-Based Medical Sys-tems, CBMS, São Carlos, Brazil. (2015).
[14] Garcés, L., Ampatzaglou, A., Avgeriou, P., and Nakagawa, E.Y. Quality attributes and quality models for ambient assisted living software system: A systematic mapping study.
[15] Huch, M. D2: Identification and characterisation of the main stakeholder groups for “ICT for Ageing” solutions. Version 5. BRAID project. pp. 46. http://www.
supras.biz/pdf/Huch-M_2010_StakeholderAnalysis-ICT-Aging.
pdf. Accessed 2nd February, 2016.
[16] Kitchenham, B.A., Charters, S.: Guidelines for performing systematic literature re-views in software engineering. Technical report, Keele University and Durham Univer-sity, UK (2007).
[17] Memon, M., Wagner, S.R., Pedersen, C.F., Beevi, F.H.A., Hansen, F.O.: Ambient assisted living healthcare frameworks, platforms, standards, and quality attributes. Sen-sors, 14, 4312–4341 (2014).
[18] Omerovic, A., Kofod-petersen, A., Solhaug, B., & Svagaard, I. (2013). Elicitation of Quality Characteristics for AAL Systems and Services.Advances in Intelligent Systems and Computing, 219,95–104.
[19] Mairiza, D., Zowghi, D., & Nurmuliani, N. (2010). An investigation into the notion of non-functional requirements. InSAC ’10: 25th Symposium on Applied Computing.(pp.
311–317).
[20] Wangenheim, C., Hauck, J., & Buglione, L. (2013). Tailoring software process capa-bility/maturity models for the health domain. Health and Technology, 3(1),11–28.
[21] Domínguez-Mayo, F. J., Escalona, M. J., Mejías, M., Aragón, G., García-García, J.
A., Torres, J., & Enríquez, P. (2015). A Strategic Study about Quality Characteristics
QM4AAL: Quality Model for AAL Systems
in e-Health Systems Based on a Systematic Literature Review. The Scientific World Journal, 2015,(863591),1–11.
[22] Aghazadeh, S., Pirnejad, H., Aliev, A., & Moradkhani, A. (2015). Evaluating the Effect of Software Quality Characteristics on Health Care Quality Indicators. Journal of Health Management & Informatics, 2,(3),67–73.
[23] Akter, S., D’ Ambra, J., & Ray, P. (2010). Service quality of mHealth platforms:
development and validation of a hierarchical model using PLS. Electronic Markets, 20 (3-4),209–227.
[24] Bitelli, C., Desideri, L., Malavasi, M. A Quality Model for Service Delivery in AAL and AT Provision. In: Andò, B. et al. (eds). Ambient Assisted Living: Italian Forum 2014. pp. 3–10. Springer International Publishing (2015).
[25] Roussos, G., and Marsh, A.: A blueprint for pervasive self-care infrastructures. In Fourth Annual IEEE International Conference on Pervasive Computing and Communi-cations Workshops, pp. 1–6 (2006).
[26] Berger, M., Fuchs, E., Pirker, M.: Ambient intelligence –from personal assistance to intelligent megacities. In: Conference on Advances in Ambient Intelligence, pp. 21–35.
IOS Press, Amsterdam, The Netherlands (2007).
[27] Hietala, H., Ikonen, V., Korhonen, I., Lahteenmaki, K., Maksimainen, A., Pakari-nen, V., Parkka, J., Saranummi,N.: Feelgood - ecosystem of PHR based products and services. Research report VTT-R-07000-09, VTT Technical Research Centre of Fin-land.,Tampere, Finland (2009).
[28] Wartena, F., Muskens, J., Schmitt, L., Petkovic, M.: Continua: The reference archi-tecture of a personal telehealth ecosystem. In: 12th IEEE International Conference on e-Health Networking Applications and Services (Healthcom), pp. 1–6 (2010).
[29] Kehagias, D.D., Tzovaras, D., Mavridou, E., Kalogirou, K., Becker, M.: Implementing an open reference architecture based on web service mining for the integration of dis-tributed applications and multi-agent systems. In: Cao, L. et al. (eds.) Agents and Data Mining Interaction. LNCS, vol. 5980, pp. 162–177. Springer Berlin Heidelberg (2010).
[30] Tazari, S., Valero, A.F., Dommarco, R., Ramos, J.P.L., Furfari, F.: PERSONA PER-ceptive Spaces prOmoting iNdependent Aging. Final reference architecture model for AAL and recommendations for future activities on the Open AAL Platform. Technical Report D3.1.3, Fraunhofer IGD, ITACA UPV, and CNR-ISTI (2010).
91 91 91