Automated events identification in use cases

Jurkiewicz, J.; Nawrocki, Jerzy

doi:10.1016/j.infsof.2014.09.011

Cited by 6 publications

(4 citation statements)

References 19 publications

(28 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…According to the Bhuiyan et al, [103], a use case is "the specification of a set of actions performed by a system, which yields an observable result that is typically, of value for one or more actors or other stakeholders of the system". The Use Case diagram provides a visual view of sequence of steps to achieve a task and describes the use of a system by the actors related to it [21,22,25,26,31,104]. These actors are any external elements that interact with the system.…”

Section: Use Case Diagrammentioning

confidence: 99%

Developing and Implementing A System for Shipping Companies Comparison

Al-Theeb

Al-Tami

Al-Johani

et al. 2019

IJSRST

View full text Add to dashboard Cite

Information-intensive Web services such as shipping comparison sites have recently been gaining popularity. However, most users including novice shoppers have difficulty in browsing such sites because of the massive amount of information gathered and the uncertainty surrounding Web environments. The aim of this research is to design a system which is called Shohnati to perform all procedures related to the order of shipment, and to store and process all information relating to customers or shipping companies in a database. Through this research, the customers will be able to order the shipment more easily by providing a complete comparison between the shipping companies, request the shipment from the preferred company's site, follow the shipment, and follow the latest offers of companies on our site. The proposed system was developed using the Unified Modeling Language (UML) and Visual Studio-ASP.NET programming language.

show abstract

Section: Use Case Diagrammentioning

confidence: 99%

Developing and Implementing A System for Shipping Companies Comparison

Al-Theeb

Al-Tami

Al-Johani

et al. 2019

IJSRST

View full text Add to dashboard Cite

show abstract

“…Each one of these represents a set of Use Cases, actors and their relationship]. This scenario based techniques has become very popular and easy to understand, model and validate user and system requirements [10], [14]. However, specifying scenarios via Use Cases may not be sufficient for requirements specifications due to the usage of natural language.…”

Section: Use Case Diagramsmentioning

confidence: 99%

“…According to the UML 2.0, a use case is "the specification of a set of actions performed by a system, which yields an observable result that is typically, of value for one or more actors or other stakeholders of the system". The Use Case diagram provides a visual view of sequence steps to achieve a task and describes the use of a system by the actors related to it [10]. These actors are any external elements that interact with the system.…”

Section: Use Case Diagramsmentioning

confidence: 99%

“…In the current instance, we examine how this might be done with formal Unified Modelling Languages (UML) specifically through Use Cases [9]. Use cases describes the interaction among uses and systems in natural language [10]. Our aim, then, is to support the modelling of organizational contexts, intentions and rationale in i*, while traditional specifications of functionality and design proceeds in the formal Use Case [9] notation of UML.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Integration of Organisational Models and UML Use Case

Bhuiyan¹

2018

JCP

View full text Add to dashboard Cite

The fundamental step in systems implementation is requirements gathering. This step is categorized into early phase requirements elicitation and systems modelling. Requirement elicitation involves gathering stakeholders' intentions, goals, rationale and organizational context that can be modelled with agent-oriented conceptual modelling such as i*. On the other hand, systems' modelling is portraying abstract version of interaction among interrelated components within a whole system via UML languages such as Use Case diagrams. The co-evolution of Agent-Oriented conceptual model such as i* and Use Case Diagrams aims to close the gap of capturing organizational requirements and system requirements. However, changes made in i* must be reflected in the Use Case diagram to ensure consistency in requirements. Therefore, this paper proposes a methodology supporting the co-evolution of these two otherwise disparate approaches in a synergistic fashion.

show abstract