Another reason for the fairly small number of papers in the field, besides different and/or non-harmonized notations, is related to the semantic capacity of business models which has not been completely explored yet and should be exploited for the automated CDM design. Inspired by  and some subsequent proposals [4, 31, 37, 7, 6, 5], in this paper we explore the semantic capacity of the business process model represented by the UMLactivitydiagram (AD), and define the formal rules for automated design of the initial CDM represented by the UML class diagram (CD). The proposed approach is based on: (i) automatic extraction of business entities (participants and objects) from the source AD, and (ii) automatic generation of corresponding classes and their associations (participant-object and object-object associations) in the target CD.
Test optimal tool is used to generate test cases from activitydiagram or state diagram of the project. That output generated test cases are stored in EXCEL file in table format or it will be in HTML format. Proposed project extract test case data from activitydiagram of project through this files and store it in database. Than this test cases are further analyze for minimization and optimization with the help of criteria mention in algorithm. Figure 3 Depicts architectural design of the system. We will consider different projects of same domain with activitydiagram and will do analysis of their model driven testing using test-optimal and my dissertation. Manual testing will be done in my dissertation.
UML ialah salah satu alat permodelan yang mendapat penggunaan meluas dalam pembangunan perisian-perisian. Ia mengandungi pelbagai rajah yang membantu pembangun perisian untuk menghasilkan produk yang lebih baik. Satu dari rajah-rajah berkenaan dikenali sebagai Rajah Aktiviti. Ianya bersifat penyampai yang biasanya dihasilkan di dalam fasa analisis bagi sesuatu perisian. Ia mengandungi banyak kelebihan disamping terdapat juga kelemahan. Satu perkara penting yang mana Rajah Aktiviti yang ada sekarang tidak mampu lakukan adalah ia tidak boleh disah dan ditentusahkan. Rajah Aktiviti yang ada kini adalah rajah fungsian dan adalah mustahil mengekstrak parameter-parameter bukan fungsian daripada rajah fungsian, akan tetapi dengan memodelkannya kepada colored Petri net serta menggunakan perumusan colored Petri net kita mampu untuk mengesah dan menentusahkan Rajah Aktiviti.
Abstract: Now-a-days, optimization of test suite using model-based testing techniques are gaining more popularity as they are easy to implement and less costly as compare to code-based testing. Aspect-oriented programming paradigm is relatively a new field of software development. In this paper, a UMLactivitydiagram-based test suite minimization technique has been developed for Aspect-Oriented Software System by using Fuzzy Clustering. This technique will reduce the size of the test suitewithout compromising thespecified coverage criteria.
M. Sarma et al. presented an approach of generating test cases from UML design diagrams. A UML use case diagrams transformed into a graph called use case diagram graph (UDG) and sequence diagram into a graph called the sequence diagram graph (SDG) and then integrating UDG and SDG to form the System Testing Graph (STG). The STG is then traversed to generate test cases for system testing. They have used state-based transition path coverage criteria for test case generation. Having stored all essential information for test generation in the STG, they now traverse the STG to generate test cases. The Test Suite Generation algorithm, traverse the STG at 2 levels. The traversal begins with the UDG. This traversal visits all use cases and generate test cases for detecting initialization faults. At level 1, if a use case initialization faults occur then it was assume faults in its operation and therefore no need to apply test cases corresponding to the operation. At level 2 traversal, starting from a use case node the corresponding SDG was visited and test cases were generated to detect operational faults . Chen et al. proposed a technique in which they use UMLactivity diagrams as design specifications, and consider the automatic approach to test case generation. Instead of deriving test cases from the UMLactivitydiagram directly, they presented an indirect approach which selects the test cases from the set of the randomly generated test case according to a given activitydiagram. In this method, they first randomly generate abundant random test cases. Then, by running the program with these test cases, they will get the corresponding program execution traces. Last, by comparing these traces with the activitydiagram according to the specific coverage criteria, they can prune some redundant test cases and get a reduced test case set which meets the test adequacy criteria.
Software testing is the last phase of the development cycle. The important role in software development is software Testing. In today’s software industry, the design of software tests is mostly based on the tester’s expertise, while test automation tools are limited to execution of preplanned tests only. Testing effort can be classified into three parts, they are test case generation, test execution and test evaluation. This paper presents a novel approach to generate the automated test paths. Due to the delay in the development of software, testing has to be done in a short time. This led to automation of testing because its efficiency and also requires less man power. In this proposed approach, by using one of the most standard Unified Modeling Language (UML) ActivityDiagram, construct the Activity Dependency table(ADT), then generate the Test paths. Then the test path are prioritized by using the Tabu search algorithm. The prioritized test path can be used in system testing, regressing testing and integration testing. Then also form the Cyclomatic diagram to check the efficiency of the test scenario .
activitydiagram. To facilitate the process and make it more transparent, unique mapping between both perspectives was designed and verified. Each agent is mapped into a single partition which is important because agents play decisive roles in those processes. Each event is transformed into a unique frame. The frames are named after events. So the simple checking of transition is that the number of frames has to comply to the number of events. Resources are illustrated in the border lines between two neighboring agents. The activitydiagram also reflects relations between entities in the REA model. Finally, each activitydiagram has its starting point and point of terminations that are also illustrated in the diagram. UML state and sequence diagrams utilize UMLactivitydiagram for describing different views on the problem. Transition described in the paper shows potential for introducting the commitments into the activitydiagram too what could lead to modeling of cycles. But this is a task for further research. Thus, it can be seen that business process modeling based on value chain is possible and advantages of value chains can be used. However, there are still questions open for further research. Firstly, no iterations or cycles were modeled. The production schedule normally consists of more production runs planned what leads to necessary modeling of cyclic operations. Secondly, we used a very simple model leaving other processes like planning, reservations, co- operations of more workers or machines beyond model scope. Thirdly, like majority of REA models, our model was created from the single company perspective which makes it difficult to use it to model networks of collaborating trading parties. These questions represent the next research challenges.
3.2. UMLUML consists of a set of graphs or charts with explanatory comments that can be expressed either in a formal way or in natural language. Each diagram has a specific and precise position in the design process. An activitydiagram is a dynamic diagram that shows the activity and the event that causes the object to be in the particular state. The activity is triggered by one or more events, and it may result in one or more events that may trigger other activities or processes. The biggest disadvantage of activity diagrams is that they do not clearly explain which objects execute which activities, and the way that the contection works between them. However, labeling of each activity with the responsible object can be performed. Often it is useful to draw an activitydiagram early in the modeling of a process, to help understand the overall process .
Linguistic assistant for domain analysis (LIDA)  can also be used as an assistant in the model development process from software requirement. Here the analyst first imports the documents to be analyzed & POS (part-of-speech) tagging of the words. Then noun listing can be done for marking relevant candidate classes & iteratively removing those classes those are not relevant. Next task is identification of attributes of classes by adjective listing. Proceeding activitydiagram the analyst then moves to Verb analysis for identifying methods & roles. Following this identification process, the analyst then proceeds to LIDA Modeler to graphically associate attributes, method, roles with appropriate classes. But problem with this approach is that LIDA needs more user interactions while generating diagrams. LIDA identifies just list of nouns, adjectives, verbs & developer and user has to decide which word goes in classes or attributes or operations. So LIDA depends on knowledge of problem domain to the Experts and those are familiar to these requirement document and LIDA system. If developer is having less knowledge then this tool may ignore some important functionality of system.
Our proposed technique, first translates the activity and sequence diagrams into their respective graphs which is called as activitydiagram graph (ADG) and sequence diagram graph (SDG). The subsequently, System Testing Graph (STG) will be made by integrating both activity and sequence graph. Then STG is traversed using BFS and DFS algorithm separately and resultant test cases are stored. The case study of an ATM system is presented by using this approach. .Subsequently the generated test cases are compared according to their success and failure rate. A. T RANSFORMATION OF AD TO ADG
There are many researchers involved in doing research on managing syntactical and horizontal inconsistency between UML diagrams. However, limitations such as huge complexity of the UML that contains different notations, different types of diagram for different view of a system and lack of UML syntax and semantics are some of the sources of inconsistencies problem in a UML model. Therefore, in order to improve the validating consistency of the UML model requires constant improvements. Numerous approaches related to consistency specification and inconsistency detection has been carried out. However, current solutions using simplified version of the UML result in poor integration between the consistency management with CASE tool environment. Therefore, improvement on consistency rules specification requires the rules to be specified over standard UML elements that adhered to the UML models. Thus, in overcoming the drawbacks as mentioned before, this research focuses on formalizing syntactical rules for part of the UML elements adhering to four (4) UML diagrams; use case diagram, activitydiagram, sequence diagram and class diagram, into logical specification. Syntactical rules for each of the UML elements are defined in logical specification to give more precise description to their natural language descriptions. The UML elements are then used to formalize twelve (12) horizontal consistency rules that will be used in detecting inconsistencies between those four (4) UML diagrams. The consistency rules are integrated into UML Checker and are used to validate the UML model. The next chapter discusses the literature on the existing approaches related to consistency management.
servations that agree pairwise, it is called a sheaf [MM92]. The topological space need not be discrete, so continuous phenomena can be modelled in this scheme. Inheritance is captured by homomorphisms between objects, and possible interac- tions between objects are defined by them both inheriting from a third, interaction object. Thus a system is specified as a category theoretic diagram showing the objects and their inheritance relationships. The category theoretic limit over this diagram yields an object (sheaf) whose behavior is the combined behavior of the system. Systems of systems may be composed as diagrams of diagrams, and the combined behavior in this case is a colimit. Examples are given of semantics for a concurrent programming language, deadlock analysis and security in terms of “non-interference”. What Goguen proposes is a scheme of modelling using cat- egory theory, a competitor for UML rather than a foundation for it. There is no modelling language, other than the diagrams and mathematical symbols of the cat- egory theorists. No specific suggestions are made about the use to be made of the models in the development process, or tools to analyse them. The notion of sys- tem developed is elegant and extremely general. It seems likely that using such neat and powerful concepts could lead to better quality designs. But mathematical ideas have never been popular among software developers. In practice, a clarified form of UML has much more chance of improving software quality than an attempt to introduce category theory.
Abstract — The unreasonable interference of concurrent threads makes the testing activity for concurrent systems a difficult task. Test case explosion is the major problem in concurrency testing and make an interruption in systematic testing of concurrent systems. In this paper we propose an approach of generating test cases from combinational UML models. In our approach ActivityDiagram (AD) and Sequence Diagram (SD) are used to model a system. The AD has converted into a graph called Activity Graph (AG) and SD into a graph called Sequence Graph (SG). Finally AG and SG are combined to form a graph called Activity Sequence Graph (ASG). The ASG is traversed using a traversing algorithm to generate the test cases. After comparing the test cases generated from ASG with the test cases generated from AG and SG, it is found that the test cases generated from ASG gives a better coverage when compared with the test cases from single modelling graph. The test cases are generated by controlling the test case explosion and are useful for controlling synchronization fault, loop fault, as well as scenario faults and interaction faults.
Several research attempts have been proposed for test case generation under various circumstances, mainly scenario based, path oriented, model based, goal oriented approaches. Scenario-based test case based on concurrent approach with concurrence coverage criteria. Path-oriented testing based on static and also dynamic flow of the software. Static path testing is based on symbolic execution, and dynamic path testing done by evaluation of running time of executing program. Model based technique is deal with different UML models such as state-chart, sequence diagram, object diagram, activity etc. Goal oriented technique identify test case which covers a selected goal such as a branch or statement. Many researches have been going to generate test case based on the specifications.
In the paper  use higher order logic (HOL) as implemented in the generic interactive theorem prover Isabelle. The paper  uses first order logic. OCL 2.0 has a third truth value “undefined” and allows collections of collections, so first order logic will probably not suﬃce to formally define it. Neither group make use of the OCL metamodel in their translations. It oﬀers diﬀerent, equivalent translations optimised for readability or for automated theorem proving respectively. With a foundation as suggested in these works, OCL itself could be the target formal language for a model transformation defining the semantics of UML. This would probably require additions to the current limited temporal operators of OCL though.
RDF (Resource Description Framework) and RDF Schema (collectively called RDF(S)) are the norma- tive language to describe the Web resource information. How to construct RDF(S) from the existing data sources is becoming an important research issue. In particular, UML (Unified Modeling Language) is being widely applied to data modeling in many application domains, and how to construct RDF(S) from the existing UML models becomes an important issue to be solved in the context of Semantic Web. By comparing and analyzing the characteristics of UML and RDF ( S ) , this paper pro- poses an approach for constructing RDF ( S ) from UML and implements a prototype construction tool. First, we give the formal definitions of UML and RDF ( S ) . After that, a construction approach from UML to RDF ( S ) is proposed, a construction example is provided, and the analyses and discussions about the approach are done. Further, based on the proposed approach, a prototype construction tool is implemented, and the experiment shows that the approach and the tool are feasible.
In the recent year, distributed computing systems have become very popular approach of computing in comparison of old centralized computing systems due to high performance computing in a very low cost. Topological design for static interconnection of computer systems under distributed environment plays a very vital role to achieve the desired accuracy in a low cost. For the topological design, the concept of graph theory is used by the various researchers from time to time. The present work is an attempt to propose a new octagonal topological design for static interconnection of computer systems under distributed environment. All interconnected nodes are placed at equidistant and Unified Modeling Language (UML) approach is used to model the proposed network topology. UML class and sequence diagrams are designed for effective execution of incoming process inside a Process Execution Controller (PEC).