Filters

2011 - 20202
Reset filters

Settings

Publication Index: WoSSubject: use cases

Search Results

Now showing 1 - 2 of 2
  • Thumbnail Image
    Conference Object
    Citation - WoS: 1
    Use Cases and Object Modelling Using Argouml
    (Springer-verlag Berlin, 2011) Complak, Wojciech; Wojciechowski, Adam; Mishra, Alok; Mishra, Deepti
    The key factor in the process of good quality software development is using proper techniques for requirements elicitation, representation and modelling providing foundations to build a logical model of the projected system. One of the most popular functional requirements description methods is use cases and scenarios approach introduced by Jacobson in 1993. Use case diagrams and analysis of functionality necessary for future users of the system allows precise definition of object model of target software system. However there are few fully functional free CASE tools supporting system designer at this software development stage. The article describes process of creating guidelines and formal requirements for design of a software system supporting storage and analysis of data concerning regulatory duties of Polish Telecom (Polish name: Telekomunikacja Polska) in the range of RIO framework agreement regarding collocation with the free UML modelling ArgoUML tool.
  • Thumbnail Image
    Article
    Citation - WoS: 5
    Citation - Scopus: 6
    Enhancing Misuse Cases With Risk Assessment for Safety Requirements
    (Ieee-inst Electrical Electronics Engineers inc, 2020) Arogundade, Oluwasefunmi T.; Misra, Sanjay; Abayomi-Alli, Olusola O.; Fernandez-Sanz, Luis
    Risk-driven requirements elicitation represents an approach that allows assignment of appropriate countermeasure for the protection of the Information System (IS) depending on the risk level. Elicitation of safety requirements based on risk analysis is essential for those IS which will run on the open and dynamic Internet platform. Traditionally, misuse cases are used to find the weak points of an IS but cannot differentiate between the weak point that can lead to lenient hazard and/or serious hazard. In this paper, we present an enhanced misuse case approach to support IS safety risk assessment at the early stages of software process. We extensively examined and identified concepts which constitute a modelling technique for IS safety risk assessment and build a conceptual model for achieving IS safety risk assessment during the requirement analysis phase of software process. The risk assessment process follows an approach of consequential analysis based on misuse cases for safety hazard identification and qualitative risk measurement. The safety requirements are elicited according to the results of the risk assessment. A medical IS is used as a case study to validate the proposed model.