Principles of software engineering management
Principles of software engineering management
Software testing techniques (2nd ed.)
Software testing techniques (2nd ed.)
Targeting safety-related errors during software requirements analysis
SIGSOFT '93 Proceedings of the 1st ACM SIGSOFT symposium on Foundations of software engineering
A Hierarchy of Communication Models for Message Sequence Charts
FORTE X / PSTV XVII '97 Proceedings of the IFIP TC6 WG6.1 Joint International Conference on Formal Description Techniques for Distributed Systems and Communication Protocols (FORTE X) and Protocol Specification, Testing and Verification (PSTV XVII)
MESA: Support for Scenario-Based Design of Concurrent Systems
TACAS '98 Proceedings of the 4th International Conference on Tools and Algorithms for Construction and Analysis of Systems
An Analyser for Mesage Sequence Charts
TACAs '96 Proceedings of the Second International Workshop on Tools and Algorithms for Construction and Analysis of Systems
Applying Design Metrics to a Large-Scale Software System
ISSRE '98 Proceedings of the The Ninth International Symposium on Software Reliability Engineering
Automatic generation of conformance tests from message sequence charts
SAM'02 Proceedings of the 3rd international conference on Telecommunications and beyond: the broader applicability of SDL and MSC
Research Directions in Requirements Engineering
FOSE '07 2007 Future of Software Engineering
Models and Testing --- A Recipe for Improved Effectiveness?
TestCom '08 / FATES '08 Proceedings of the 20th IFIP TC 6/WG 6.1 international conference on Testing of Software and Communicating Systems: 8th International Workshop
A Multi-level Methodology for Developing UML Sequence Diagrams
ER '08 Proceedings of the 27th International Conference on Conceptual Modeling
A Formal Model of Business Application Integration from Web Services (Position Paper)
SOFSEM '09 Proceedings of the 35th Conference on Current Trends in Theory and Practice of Computer Science
Verifying Action Semantics Specifications in UML Behavioral Models
CAiSE '09 Proceedings of the 21st International Conference on Advanced Information Systems Engineering
Implementing MSC Tests with Quiescence Observation
TESTCOM '09/FATES '09 Proceedings of the 21st IFIP WG 6.1 International Conference on Testing of Software and Communication Systems and 9th International FATES Workshop
An approach to identifying causes of implied scenarios using unenforceable orders
Information and Software Technology
Lightweight verification of executable models
ER'11 Proceedings of the 30th international conference on Conceptual modeling
Analyzing realizability of choreographies using initiating and responding flows
Proceedings of the 8th International Workshop on Model-Driven Engineering, Verification and Validation
Model-Driven engineering in a large industrial context — motorola case study
MoDELS'05 Proceedings of the 8th international conference on Model Driven Engineering Languages and Systems
A framework for pathologies of message sequence charts
Information and Software Technology
On the realizability of collaborative services
Software and Systems Modeling (SoSyM)
| Hi-index | 0.00 |
Scenario based requirements specifications are the industry norm for defining communicating systems. These scenarios are often captured in the form of UML/MSC sequence diagrams. Errors are often introduced at this stage of the development process, which are costly to resolve if they are not detected early. This paper is concerned with the automatic detection and resolution of semantic errors that can occur in such scenarios.The paper discusses a semantic interpretation of scenario-based requirements and various types of defects (or pathologies) that can be detected. The paper defines the semantics and defects within a partial order theoretic framework. We introduce a UML 2.0 profile that captures various domain specific communication semantics, which can be used to determine the relevance of detected pathologies when different underlying implementation assumptions are made. The paper also discusses how to automatically resolve pathologies by using this profile to adapt the communication architecture in the requirements model.