Problem frame semantics for software development

Hall, Jon G.; Rapanotti, Lucia; Jackson, Michael

doi:10.1007/s10270-004-0062-1

Cited by 51 publications

(31 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Proceeding this way has the advantage that the specification obtained satisfies the S, W R relation by construction, making a proof unnecessary. It also matches the PF semantics [5] in that S is determined by W and R.…”

Section: Discussion and Future Worksupporting

confidence: 57%

Using the event calculus to reason about problem diagrams

Classen

Laney

Tun

et al. 2008

Proceedings of the 3rd International Workshop on Applications and Advances of Problem Frames

View full text Add to dashboard Cite

Central to the problem frames approach is the distinction of three different descriptions: requirements R, domain assumptions W and specifications S, tied together with the socalled frame concern, a proof obligation that has to hold between them if a problem diagram is to be correct: S, W R. The form this proof should take is not fixed a priori. It might, however, be desirable to automate it in order to allow for an efficient analysis of large diagrams. To make this possible, we follow some earlier suggestions to use the Event Calculus as a suitable formalism for these descriptions. The main contribution of the present paper is a set of consistency rules as well as guidelines for passing from a problem diagram to its formal description.

show abstract

Section: Discussion and Future Worksupporting

confidence: 57%

Using the event calculus to reason about problem diagrams

Classen

Laney

Tun

et al. 2008

Proceedings of the 3rd International Workshop on Applications and Advances of Problem Frames

View full text Add to dashboard Cite

show abstract

“…Building the one-to-one mapping between atomic business and system uses case or system use case scene, and then building system model to get system requirements, which achieves e the transition from business model to system model [6].…”

Section: System Modelingmentioning

confidence: 99%

The Commercial Bank Card System Based on SOA

Zhang

2012

AEF

View full text Add to dashboard Cite

Abstract. SOA has been the effective technical solution to enterprise application integration and business process rebuilding. The paper presents a reference implementation scheme of Commercial Bank Card System based on SOA. In requirement tier, the implementation plan first establishes the full concept model and logical model of Commercial Bank Card System from business request(business use case-business step-atomic business) to system request (system use case-system step-atomic component), then in semantics tier, we give out full description of the model through the combination of OWL and BPEL. At last a SOA's three-tier framework of "requirement-semantics-service" has been built for the Commercial Band Card System.

show abstract

“…In problem frames, the machine S is a physical domain which cannot be specified without the specifications of other physical domains in W. Meanwhile, R must be expressed as constraints in terms of the properties of W [13]. Also, the machine S in a solved sub-problem becomes part of the context domain W in the parent problem.…”

Section: Problem Framesmentioning

confidence: 99%