{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,1,11]],"date-time":"2025-01-11T05:21:14Z","timestamp":1736572874768,"version":"3.32.0"},"reference-count":0,"publisher":"Politechnika Wroclawska Oficyna Wydawnicza","issue":"1","content-domain":{"domain":[],"crossmark-restriction":false},"short-container-title":["EISEJ"],"published-print":{"date-parts":[[2020]]},"abstract":"<jats:p><jats:bold>Background:<\/jats:bold> The comprehensive representation of functional requirements is a crucial activity in the analysis phase of the software development life cycle. Representation of a complete set of functional requirements helps in tracing business goals effectively throughout the development life cycle. Use case modelling is one of the most widely-used methods to represent and document functional requirements of the system. Practitioners exploit use case modelling to represent interactive functional requirements of the system while overlooking some of the non-interactive functional requirements. The non-interactive functional requirements are the ones which are performed by the system without an initiation by the user, for instance, notifying something to the user or creating an internal backup.<\/jats:p>\n\t\t\t\t\t<jats:p><jats:bold>Aim:<\/jats:bold> This paper addresses the representation of non-interactive requirements along with interactive ones (use cases) in one model. This paper calls such requirements `operation cases\u2019 and proposes a new set of graphical and textual notations to represent them.<\/jats:p>\n\t\t\t\t\t<jats:p><jats:bold>Method:<\/jats:bold> The proposed notations have been applied on a case study and have also been empirically evaluated to demonstrate the effectiveness of the new notations in capturing non-interactive functional requirements.<\/jats:p>\n\t\t\t\t\t<jats:p><jats:bold>Results and Conclusion:<\/jats:bold> The results of the evaluation indicate that the representation of operation cases helps in documenting a complete set of functional requirements, which ultimately results in a comprehensive translation of requirements into design.<\/jats:p>","DOI":"10.37190\/e-inf200104","type":"journal-article","created":{"date-parts":[[2020,6,17]],"date-time":"2020-06-17T08:30:57Z","timestamp":1592382657000},"source":"Crossref","is-referenced-by-count":4,"title":["Extending UML Use Case Diagrams to Represent Non-Interactive Functional Requirements"],"prefix":"10.37190","volume":"14","author":[{"given":"Saqib","family":"Iqbal","sequence":"first","affiliation":[]},{"given":"Issam","family":"Al-Azzoni","sequence":"additional","affiliation":[]},{"given":"Gary","family":"Allen","sequence":"additional","affiliation":[]},{"given":"Hikmat","family":"Ullah Khan","sequence":"additional","affiliation":[]}],"member":"23140","published-online":{"date-parts":[[2020]]},"container-title":["e-Informatica Software Engineering Journal"],"original-title":[],"language":"en","link":[{"URL":"http:\/\/www.e-informatyka.pl\/attach\/e-Informatica_-_Volume_14\/eInformatica2020Art04.pdf","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,1,10]],"date-time":"2025-01-10T08:48:22Z","timestamp":1736498902000},"score":1,"resource":{"primary":{"URL":"https:\/\/www.e-informatyka.pl\/index.php\/einformatica\/volumes\/volume-2020\/issue-1\/article-4\/"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2020]]},"references-count":0,"journal-issue":{"issue":"1","published-online":{"date-parts":[[2020]]},"published-print":{"date-parts":[[2020]]}},"URL":"https:\/\/doi.org\/10.37190\/e-inf200104","relation":{},"ISSN":["2084-4840"],"issn-type":[{"type":"electronic","value":"2084-4840"}],"subject":[],"published":{"date-parts":[[2020]]}}}