Partial order semantics for use case and task models

Sinnig, Daniel; Khendek, Ferhat; Chalin, Patrice

doi:10.1007/s00165-010-0158-z

Cited by 7 publications

(6 citation statements)

References 39 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The "Order Product" use case and the corresponding task model are given in Figure 16 and Figure 17, respectively. We note that both these use case and task models were used in simplified form as motivating examples in Sinnig et al [2011] but in the latter, we did not allow the user to recover from payment errors. For this case study, this simplification does not apply and users may reattempt to pay for the product after a payment failure.…”

Section: Case Studymentioning

confidence: 99%

“…Both were originally proposed in Sinnig et al [2011] and are required for the rewriting of the ECTT operators disabling and suspend/resume, respectively.…”

Section: Appendix-ectt Rewriting Rulesmentioning

confidence: 99%

“…In Sinnig et al [2011] we proposed a partial-order semantics for use case and task models. The semantic mapping is performed in two steps: first the source models are mapped to respective intermediate semantic domains, followed by mappings to the common semantic domain of sets of partially ordered sets (sets of posets).…”

Section: Related Formal Approaches For Interactive Systemsmentioning

confidence: 99%

“…In our previous work [Sinnig et al 2011], we presented a common semantic domain for use case and task models based on partially ordered sets (posets). While posets support a true (noninterleaving) form of concurrency and have interesting theoretical properties, they are difficult to operationalize (due to potentially infinite cardinalities of the involved posets) and do not support nondeterminism.…”

Section: Formal Foundationmentioning

confidence: 99%

See 3 more Smart Citations

Use case and task models

Sinnig

Chalin

Khendek

2013

ACM Trans. Softw. Eng. Methodol.

Self Cite

View full text Add to dashboard Cite

User Interface (UI) development methods are poorly integrated with standard software engineering practice. The differences in terms of artifacts involved, development philosophies, and lifecycles can often result in inconsistent system and UI specifications leading to duplication of effort and increased maintenance costs. To address such shortcomings, we propose an integrated development methodology for use case and task models. Use cases are generally used to capture functional requirements whereas task models specify the detailed user interactions with the UI. Our methodology can assist practitioners in developing software processes which allow these two kinds of artifacts to be developed in a codependent and integrated manner. We present our methodology, describe its semantic foundations along with a set of formal conformance relations, and introduce an automated verification tool.

show abstract

Section: Case Studymentioning

confidence: 99%

“…Both were originally proposed in Sinnig et al [2011] and are required for the rewriting of the ECTT operators disabling and suspend/resume, respectively.…”

Section: Appendix-ectt Rewriting Rulesmentioning

confidence: 99%

Section: Related Formal Approaches For Interactive Systemsmentioning

confidence: 99%

Section: Formal Foundationmentioning

confidence: 99%

See 2 more Smart Citations

Use case and task models

Sinnig

Chalin

Khendek

2013

ACM Trans. Softw. Eng. Methodol.

Self Cite

View full text Add to dashboard Cite

show abstract

“…All of the checks are focused on global properties of UCMs. The same authors also wrote a number of papers about mapping use-cases into different formalismspartially ordered sets (POSETs) [34], finite state machines [35] and LTS + POSETs [36]. As opposed to FOAM, the properties to be verified are predefined and branching scenarios are not considered.…”

Section: Formal Semantics For Use-casesmentioning

confidence: 99%

Formal Verification of Annotated Textual Use-Cases

Šimko

Hauzar

Hnětynka

et al. 2014

The Computer Journal

View full text Add to dashboard Cite

Textual use-cases have been traditionally used in the initial stages of the software development process to describe software functionality from the user's perspective. Their advantage is that they can be easily understood by stakeholders and domain experts. However, since use-cases typically rely on natural language, they cannot be directly subject to a formal verification. In this article, we present a method (called Formal Verification of Annotated Use-Case Models, FOAM) for formal verification of use-cases. This method features simple user-definable annotations, which are inserted into a use-case to make its semantics more suitable for verification. Subsequently, a model-checking tool is employed to verify temporal invariants associated with the annotations. This way, FOAM allows harnessing the benefits of model checking while still keeping the use-cases understandable for non-experts.

show abstract

Developing GUI Applications in a Verified Setting

Adelsberger

Setzer

Walkingshaw

2018

Dependable Software Engineering. Theories, Tools, and Applications

View full text Add to dashboard Cite

Although there have been major achievements in verified software, work on verifying graphical user interfaces (GUI) applications is underdeveloped relative to their ubiquity and societal importance. In this paper, we present a library for the development of verified, statedependent GUI applications in the dependently typed programming language Agda. The library uses Agda's expressive type system to ensure that the GUI, its controller, and the underlying model are all consistent, significantly reducing the scope for GUI-related bugs. We provide a way to specify and prove correctness properties of GUI applications in terms of user interactions and state transitions. Critically, GUI applications and correctness properties are not restricted to finite state machines and may involve the execution of arbitrary interactive programs. Additionally, the library connects to a standard, imperative GUI framework, enabling the development of native GUI applications with expected features, such as concurrency. We present applications of our library to building GUI applications to manage healthcare processes. The correctness properties we consider are the following: (1) That a state can only be reached by passing through a particular intermediate state, for example, that a particular treatment can only be reached after having conducted an X-Ray. (2) That one eventually reaches a particular state, for example, that one eventually decides on a treatment. The specification of such properties is defined in terms of a GUI application simulator, which simulates all possible sequences of interactions carried out by the user.

show abstract

Partial order semantics for use case and task models

Cited by 7 publications

References 39 publications

Use case and task models

Use case and task models

Formal Verification of Annotated Textual Use-Cases

Developing GUI Applications in a Verified Setting

Contact Info

Product

Resources

About