[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-240887-105":3,"detail-sidebar-cat-1-en-105":81,"doc-detail-240887-en":127},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":74,"head_meta":76,"extra_data":78,"updated_unix":80},105,"en","usability-promotion-in-a-technical-project-with-sparse-resources-a-case-study-implementation-plan","Usability Promotion in a Technical Project with Sparse Resources - A Case Study - Implementation plan","","The paper explains how software usability for security-related functionalities is promoted and evaluated during the design phase of a software project built on middleware. It presents ongoing work in the GEMOM project, outlines early-stage challenges, and describes a planned approach to address them. The focus is on establishing an actionable usability implementation plan despite the lack of direct end users and limited resources for human factors studies.",{"@graph":14,"@context":73},[15,34,56],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/template/","Template",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/template/presentations/","Presentations",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/template/usability-promotion-in-a-technical-project-with-sparse-resources-a-case-study-implementation-plan/240887/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/usability-promotion-in-a-technical-project-with-sparse-resources-a-case-study-implementation-plan/240887.png","ImageObject",442,249,{"name":42,"@type":43},"River Wang","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-10-30","2026-09-11",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",7,{"@type":57,"mainEntity":58},"FAQPage",[59,65,69],{"name":60,"@type":61,"acceptedAnswer":62},"How does the paper promote and evaluate usability during the design phase?","Question",{"text":63,"@type":64},"It describes promoting usability of software functionalities while still in the design phase and establishing evaluation activities aligned with the project’s usability implementation plan.","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"What challenges did GEMOM face at the beginning regarding usability?",{"text":68,"@type":64},"Challenges included promoting usability in a deeply technical project, lack of a clearly defined usability task, absence of direct end users for middleware, and very limited person-months allocated to human factors studies.",{"name":70,"@type":61,"acceptedAnswer":71},"Why is usability harder to address in middleware systems than in applications with direct users?",{"text":72,"@type":64},"Middleware typically has no direct human users and is mainly used by other applications, so usability perspective can be neglected compared with systems that explicitly present interfaces to people.","https://schema.org",{"og:url":32,"og:type":75,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":77,"canonical":32},"index,follow",{"doc_id":79,"site_id":7},240887,1791701367,{"code":4,"msg":82,"data":83},"success",[84,88,93,98,103,108,113,118,123],{"id":85,"doc_module":22,"doc_module_name":25,"category_name":29,"show_sort_weight":86,"slug":87},11,90,"presentations",{"id":89,"doc_module":22,"doc_module_name":25,"category_name":90,"show_sort_weight":91,"slug":92},12,"Resumes",80,"resumes",{"id":94,"doc_module":22,"doc_module_name":25,"category_name":95,"show_sort_weight":96,"slug":97},14,"Invoices",70,"invoices",{"id":99,"doc_module":22,"doc_module_name":25,"category_name":100,"show_sort_weight":101,"slug":102},15,"Posters",60,"posters",{"id":104,"doc_module":22,"doc_module_name":25,"category_name":105,"show_sort_weight":106,"slug":107},16,"Social Media",50,"social-media",{"id":109,"doc_module":22,"doc_module_name":25,"category_name":110,"show_sort_weight":111,"slug":112},17,"Forms",40,"forms",{"id":114,"doc_module":22,"doc_module_name":25,"category_name":115,"show_sort_weight":116,"slug":117},18,"Letters",30,"letters",{"id":119,"doc_module":22,"doc_module_name":25,"category_name":120,"show_sort_weight":121,"slug":122},21,"Paper Templates",5,"papers-templates",{"id":124,"doc_module":22,"doc_module_name":25,"category_name":125,"show_sort_weight":4,"slug":126},158,"General","general-158",{"code":4,"msg":82,"data":128},{"doc_id":79,"user_id":129,"nickname":42,"user_avatar":130,"doc_module":22,"category_id":85,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":55,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":26,"language":136,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":12,"update_tm":140,"read_time":22},1099514067438,"https://ap-avatar.wpscdn.com/avatar/100002539ee87300030?x-image-process=image/resize,m_fixed,w_180,h_180&k=1780474512215547542","Usability Promotion in a Technical Project with Sparse Resources – a Case Study  \nKaarina Karppinen  \nVTT Technical Research Centre of Finland Kaitoväylä 1, PO Box 1100 FI-90571 Oulu, Finland +358 40 5487 058  \n[kaarina.karppinen@vtt.fi](kaarina.karppinen@vtt.fi)  \nMarja Liinasuo  \nVTT Technical Research Centre of Finland Vuorimiehentie 3, Espoo, P.O. Box 1000 FI-02044 VTT, Finland +358 400 912711  \n[marja.liinasuo@vtt.fi](marja.liinasuo@vtt.fi)  \nABSTRACT  \nIn this paper, we describe how the usability of software functionalities are promoted and evaluated during the design phase of a software project developing security-related functionalities in amiddleware. The paper describes our work-in-progress in GEMOM project, challenges faced in the beginning of the project, and our planto overcome those challenges with a clearly defined usability implementation plan.  \nCategories and Subject Descriptors  \nD.2.9 [Software Engineering]: Management – Software quality assurance (SQA).  \nGeneral Terms  \nDesign, Human Factors  \nKeywords  \nsoftware design, usability, scenarios, acceptability  \n1. INTRODUCTION  \nThe usability of a software product is becoming a widely recognised quality attribute in software development [1] . However, the conception of usability realised in projects is often quite narrow and, pertaining software design, restricted to attributes that are conceived as becoming topical to produce only in the later phases of software development. Anyhow, no effective product can be designed without taking into account also the “soft” human and context-related complexities, broadly speaking human factors, already in the beginning of the system development.  \nFurthermore, in the Human-Computer Interaction (HCI) community, software usability has primarily been concerned with the presentation of information, more precisely with user interface [2] . User interface can denote the visible part of the system and, less frequently, the interaction part of the system, i.e., the coordination of the information exchange between the end user and the system in  \nPermission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee.  \nI-USED’08, September 24, 2008, Pisa, Italy  \nboth directions [3] . Either way, the easily neglected fact is that the usability of the tool is not only about the interface but also depends on other attributes rooted deeper in the character of the tool, e.g. the tasks it performs,.  \nMiddleware is a specific type of computer software that connects various software components or applications together. Typically other applications are conceived as users of amiddleware, and it has no direct human users, except for systems specialists or the like who usually install and maintain complex IT systems. Hence, usability in a middleware system development is harder to promote than of applications which have a direct interface towards a human user. As a consequence, the lack of “proper” users and the tradition of software development methodologies, which may see a user only as a means to elicit requirements, easily results in software development without any usability perspective. In the ongoing GEMOM project these obstacles are planned to be prevailed and one of the project’s aims is better usability of the end product without risking the security of it; a task that is proved to be hard to perform [4] .  \n2. OVERCOMING THE CHALLENGES FOR USABILITY  \nGEMOM (Genetic Message Oriented Secure Middleware) is a recently launched research project, lasting for 2½ years, that is co-funded by the European Commission and involves ten industry and research partners across Europe [5] . GEMOM is developing ","cbCaif1sXPhgKaDP","https://ap.wps.com/l/cbCaif1sXPhgKaDP","pdf",34161,"English","# Abstract\n# 1. Introduction\n## Software usability as a quality attribute\n## Challenges specific to middleware\n# 2. Overcoming the Challenges for Usability\n## GEMOM project overview\n## Defining the challenges\n## Creating motivation","[{\"question\":\"How does the paper promote and evaluate usability during the design phase?\",\"answer\":\"It describes promoting usability of software functionalities while still in the design phase and establishing evaluation activities aligned with the project’s usability implementation plan.\"},{\"question\":\"What challenges did GEMOM face at the beginning regarding usability?\",\"answer\":\"Challenges included promoting usability in a deeply technical project, lack of a clearly defined usability task, absence of direct end users for middleware, and very limited person-months allocated to human factors studies.\"},{\"question\":\"Why is usability harder to address in middleware systems than in applications with direct users?\",\"answer\":\"Middleware typically has no direct human users and is mainly used by other applications, so usability perspective can be neglected compared with systems that explicitly present interfaces to people.\"}]","Usability Promotion in a Technical Project with Sparse Resources - A Case Study - Implementation plan | PDF",1789167211]