[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-244714-105":53,"doc-detail-244714-en":127},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":120,"head_meta":122,"extra_data":124,"updated_unix":126},105,"en","improvement-of-requirements-engineering-course-medical-software-case-study","Improvement of Requirements Engineering Course - Medical Software Case Study","","Requirements engineering is a critical phase in software development, and for complex medical systems it requires careful elicitation and specification of requirements in a form that supports effective communication between developers and users. Focusing on healthcare and medical software, the paper discusses key elements and characteristics of requirement documentation templates and highlights lessons for collecting requirements in this domain. It also proposes practical steps to improve a requirements engineering course delivered for more than 10 years at the University of Novi Sad.",{"@graph":63,"@context":119},[64,80,102],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/improvement-of-requirements-engineering-course-medical-software-case-study/244714/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/improvement-of-requirements-engineering-course-medical-software-case-study/244714.png","ImageObject",442,249,{"name":88,"@type":89},"Franzy","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-20","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",13,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"Why is requirements engineering important for medical software development?","Question",{"text":109,"@type":110},"Because complex medical software requires requirements elicitation and specification in a form that enables clear communication between developers and users.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"What characteristics distinguish medical software in this paper?",{"text":114,"@type":110},"Medical software may be standalone for diagnostic or therapeutic purposes, embedded in medical devices, act as an accessory, or support design and testing and quality control for medical devices.",{"name":116,"@type":107,"acceptedAnswer":117},"How do regulatory issues affect requirements engineering for medical software?",{"text":118,"@type":110},"Regulatory requirements tied to privacy, patient data protection, and medical device standards influence how slowly healthcare adapts to new technologies and make complete, consistent requirement specifications especially necessary.","https://schema.org",{"og:url":78,"og:type":121,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":123,"canonical":78},"index,follow",{"doc_id":125,"site_id":56},244714,1791731463,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":136,"language":137,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":138,"faqs":139,"seo_title":140,"seo_description":61,"update_tm":141,"read_time":76},2336478945519,"https://ap-avatar.wpscdn.com/davatar_085a072bc5b1113ac321206ff7593b45","4  \nImprovement of Requirements Engineering Course – Medical Software Case Study  \nMIRJANA IVANOVI´C, University of Novi Sad, Faculty of Sciences, Department of Mathematics and Informatics  \nAMELIA BADICA, Faculty of Economics and Business Administration, University of Craiova MARIA GANZHA, Systems Research Institute Polish Academy of Sciences and Warsaw University of Technology  \nCOSTIN BADICA, Department of Computers and Information technology, University of Craiova MARCIN PAPRZYCKI, Systems Research Institute Polish Academy of Sciences and Warsaw Management Academy  \n\n| Requirements engineering is one of crucial phases in developing any kind of software. For complex and demanding software it is necessary, before starting actual development, to elicit and specify requirements in form of appropriate document that will facilitate communication between developers and users. Requirement Engineering (RE) is, usually, one of master courses during ICT studies. Nowadays, society is confronted with a global aging population, and signi􀀌cant e􀀋orts are dedicated to the development of complex healthcare and medical software. In this paper we will discuss some important elements and characteristics of requirement document template and also critical and important lessons for collecting requirements for healthcare and medical software. We also propose some steps for improving RE course that has been delivering for more than 10 years at the University of Novi Sad.\u003Cbr>Categories and Subject Descriptors: D.2.1 [Requirements/Specifications] ; D.2.9 [Software quality assurance-SQA]:—Management; J.3 [Medical information systems]:—Life and medical sciences; K.3.2 [Curriculum]:—Computer and Information Science Education |\n| --- |\n| 1. INTRODUCTION\u003Cbr>Remarkable gains in life expectancy have influence on society, as they result in global aging population. Wide range of stakeholders invests serious efforts to develop different kinds of healthcare and medical software, in order to support, on the one hand, independent living of old population and, on the other hand, unhealthy and disabled population. Majority of medical devices, available today, could not function without appropriate software. So-called medical software is a special kind of software, used within medical context, which possess the following characteristics:\u003Cbr>(1) standalone software used for diagnostic/therapeutic aim,\u003Cbr>(2) ”medical device software” – embedded in specific medical (smart) devices, |\n\nAuthors address: Mirjana Ivanovi, Trg Dositeja Obradovica 4, 21000 Novi Sad, Serbia; [e-mail: mira@dmi.uns.ac.rs](e-mail: mira@dmi.uns.ac.rs); Amelia Badica, 13, A.I. Cuza Street, Craiova, 200585, Romania; e-mail: [ameliabd@yahoo.com](ameliabd@yahoo.com); Maria Ganzha, ul. Newelska 6, 01-447 Warsaw, Poland; [e-mail: maria.ganzha@ibspan.waw.pl](e-mail: maria.ganzha@ibspan.waw.pl); Costin Badica, Blvd. Decebal nr. 107, RO-200440, Craiova, Romania;  \ne-mail: [cbadica@software.ucv.ro](cbadica@software.ucv.ro); Marcin Paprzycki, ul. Newelska 6, 01-447 Warsaw, Poland; [e-mail: paprzyck@ibspan.waw.pl](e-mail: paprzyck@ibspan.waw.pl);  \nCopyright 􀀍c by the paper's authors. Copying permitted only for private and academic purposes.  \nIn: Z. Budimac (ed.): Proceedings of the SQAMIA 2017: 6th Workshop of Software Quality, Analysis, Monitoring, Improvement, and Applications, Belgrade, Serbia, 11-13.9.2017, Also published online by CEUR Workshop Proceedings ([http://ceur-ws.org](http://ceur-ws.org), ISSN 1613-0073)  \n4:2 􀀏 Mirjana Ivanovi et al  \n(3) software that drives medical devices or acts as an accessory to medical devices,  \n(4) software that supports the design, realization, and testing of medical devices; or provides quality control management for such devices.  \nHealthcare and medicine domains, nowadays, are facing a number of exclusive challenges in technology adoption. Very important aspect is strict connection to the regulatory issues, dealing with privacy and protection of patient data, th","cbCaioUx8WbZ3u9j","https://ap.wps.com/l/cbCaioUx8WbZ3u9j","pdf",166144,9,"English","# Introduction\n## Requirements engineering for software development\n## Characteristics of medical software\n## Regulatory challenges and patient data protection\n## Medical device software and safety requirements\n## Need for structured requirement documentation\n# Proposed course improvement approach\n## Lessons learned from healthcare requirements collection\n## Steps to enhance the requirements engineering course","[{\"question\":\"Why is requirements engineering important for medical software development?\",\"answer\":\"Because complex medical software requires requirements elicitation and specification in a form that enables clear communication between developers and users.\"},{\"question\":\"What characteristics distinguish medical software in this paper?\",\"answer\":\"Medical software may be standalone for diagnostic or therapeutic purposes, embedded in medical devices, act as an accessory, or support design and testing and quality control for medical devices.\"},{\"question\":\"How do regulatory issues affect requirements engineering for medical software?\",\"answer\":\"Regulatory requirements tied to privacy, patient data protection, and medical device standards influence how slowly healthcare adapts to new technologies and make complete, consistent requirement specifications especially necessary.\"}]","Improvement of Requirements Engineering Course - Medical Software Case Study | PDF",1789221026]