No full-text available
To read the full-text of this research,
you can request a copy directly from the authors.
Minimally Adequate Teacher Designs Software
Abstract
this paper avoids undesired results, due to overgeneralization. To achieve thisgoal, the algorithm asks the designer for guidance during the synthesis process,when needed.
... The over-generalization issue is not tackled in the context of this study. However, there are synthesizers which can avoid over-generalization, e.g., through interactive synthesis as implemented in MAS (Minimally Adequate Synthesizer) [39,40]. ...
... MAS (Minimally Adequate Synthesizer) [39,40] is a command line tool developed for synthesizing application traces. MAS infers a state machine diagram from simple message sequences following Angluin's framework of a minimally adequate teacher [3]. ...
... The well-known problem of over-generalization can be handled in various ways. In [39,40], MAS handles this prior to or during the synthesis when run in an interactive mode. The over-generalization problem has been acknowledged (e.g. by Uchitel et al. [67]). ...
Service-oriented architecture (SOA) is a software architectural style, which relies on reusable and composable services. In addition to software-orientation, SOA includes a business viewpoint, so that business requirements can be captured as high level business processes. Business processes can be implemented, for example, as an orchestration of different service components. Individual services participate in the overall execution of business processes by providing elementary service activities. In addition to flexibility and services reuse, bridging of business and information technology (IT) views is one of the claimed benefits of SOA.
Development of service-based systems includes a range of different activities. However, development of service-based systems is still lacking systematic and tool vendor independent practices and development methods. In this thesis, a development process for a service provider, called Service Product Development Process (SPDP), is presented. It consists of several development phases and related activities. The input for SPDP includes high level business process requirements. The result of the process is a new service-based product to be added to the service provider’s product portfolio.
The purpose of this thesis is to study the applicability and the benefits of applying a scenario-driven approach, a type of requirement-driven development, for the development of service-based systems. Scenarios are used to capture functional system requirements as simple message sequences given as UML sequence diagrams. The scenario-driven approach is applied to different phases of SPDP including business process development, service specification, and service realization. The proposed scenario-driven approach is not limited to the SPDP context. It is rather a general purpose framework for development of service-based systems or products, called SceDA.
SceDA includes three independent scenario-based methods, which are targeted to support different development phases of service-based systems. One of the three methods is used for scenario-based business process development. The other two methods are targeted at service development, in particular, service specification and service realization. Service specification is supported by a method for automatically mining and re-documenting the development rules as scenarios. To support service realization, a method for generating source code for individual service and client applications has been developed. Each method includes a description of the developed tool support and a case study.
Case studies are used for constructing and evaluating the three scenario-based methods developed. Each method is applied as a case study in the context of development phases of SPDP. In the first case study, scenario-driven business process development method is applied. Two other case studies concern constructing and using scenarios for application development. One case study utilizes the scenario mining method. In the other case study, the code generation method is applied.
... IJCSNS International Journal of Computer Science and Network Security, VOL.6 No.2B, February 2006 58 3. each message extend the state vextors by propagating variable values throughout the sequence diagrams The objects are assigned state vectors based on OCL information and the algorithm of [5] before or after transferring messages. 4. generate each object's statechart of single sequence diagram based on state vector. ...
Scenarios present system behaviors by specifying collaboration and interaction between objects or components from users' perspectives. Statecharts are precise descriptions of system behaviors. Automatic transformation from scenarios to statechart is the process in which system behavior models are generated automatically from UML requirement models. In this paper we propose an approach to eliciting implied scenarios based on generated statechart from scenarios. This approach presents some rules of constructing state vectors that assist analysts to add semantic information to scenarios expressed by sequence diagrams，identify implied state transition paths by adding the scenarios information based on existing algorithm which supports the design process by generating statechart design automatically from scenarios, and synthesize implied scenarios by implied state transition paths with which analysts or users can further refine their requirements.
... Mäkinen and Systä [18] proposed an interactive approach for synthesizing UML statechart diagrams from sequence diagrams. In this approach, the synthesis algorithm called MAS (Minimally Adequate Synthesizer) [19, 20] consults the user whenever needed to avoid undesired generalizations in the resulting statechart diagram. MAS models the synthesis process as a language inference problem and uses Angluin's [1] framework of minimally adequate teacher to infer the desired statechart diagram with the help of membership and equivalence queries. ...
This report summarizes the Workshop on Scenario-Based Round-Trip Engineering held in Minneapolis, Minnesota, USA, on October 16, 2000, in conjunction with the International Conference on Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA 2000). The workshop consisted of a keynote and seven presentations, which were organized into three sessions: From Interaction Diagrams to State Machines, Forward Engineering, and Reverse Engineering. Altogether nine position papers were accepted. The workshop web page, including the papers, the presentations, and the electronic version of this report, can be found at <http://www.cs.uta.fi/~cstasy/oopsla2000/workshop.html>.
The development of services-based systems starts from defining business requirements to be implemented as high-level business processes. In this paper, we describe a scenario-driven approach for developing business processes specified as WS-BPEL descriptions. We aim for simplicity in the business level notation and leverage example-like modelling principles in order to enable process sketching. The first step in our approach is to identify the essential functional requirements for business processes. The requirements are modelled as simple scenarios, each of them defining a sample run through the process, i.e., required behaviour that the underlying service-based system should allow. The scenarios, specifying sent and received messages among the services, are synthesised into a state machine. The state machine is transformed into an initial process model given in UML activity model notation. To enable mapping into WS-BPEL code, the transformation exploit domain-specific rules, i.e., our target model consists of a subset of UML with WS-BPEL specific constraints and stereotypes. The initial process model can be further refined to enable generation of executable WS-BPEL descriptions. We apply the approach on two cases, a simple process for managing loan requests and an industry case study from a logistics provider are presented.
The development of services-based systems starts from defining goals for business processes to be implemented, e.g., as a Web service orchestrations specified in WS-BPEL. In this paper, we propose a scenario-driven approach for modeling business processes. We aim for simplicity in the notation and leverage example-like modeling principles in order to improve process sketching. The first step in our approach is to identify the essential business requirements and model them using a simple scenario notation. The scenarios, given as UML sequence diagrams, are synthesized into a state machine, which is translated into a WS-BPEL flavored process skeleton given as UML activity diagram. The process skeleton can be further refined into executable process model.
Minimally Adequate Synthesizer (MAS) is an interactive algorithm that synthesizes UML statechart diagrams from sequence diagrams. It follows Angluin's framework of minimally adequate teacher to infer the desired statechart diagram by consulting the user. To minimize the consultations needed, MAS keeps track of the interaction with the user. Together with its general knowledge about sequence diagrams, this allows MAS to operate without user's help in most of the cases. A synthesized statechart diagram is a generalization, which accepts additional behavior to that described in the sequence diagrams given as input. During the synthesis process MAS asks the user if certain generalizations are allowed or not. We sketch the usage of two different kinds of inaccurate answers the user can provide. We allow Probably yes and Probably no answers, i.e. weak Yes and No answers. The information obtained from these answers is considered less significant than that obtained from normal, definite answers. The user can also postpone answering by saying later. 1.
ResearchGate has not been able to resolve any references for this publication.