This project is my Master's thesis which I carried out under the guidance of Dr.Jon Pearce at San Jose State University. The main idea of the Collaboration Prototyper is to generate near complete prototypes from UML Collaborations (defined next). In the software development process, the 60% of the time, key stakeholders find that the product differs from their initial specification and requirements. The requirements are lost due to a long pipeline of procedures and people in between. If we could take the requirement specification consisting of analysis models and usecases directly, and generate a prototype from it, we could try and reduce this gap between the expectation and delivery of the product.

Class diagrams by themselves lack method implementations. Hence, we combine sequence diagrams with class diagrams to include information about method implementations. Collaborations are nothing but the structure (class diagrams) and behaviour (sequence diagrams) of an application. A collaboration is a collection of classes that work together to implement the services specified in a component's provided interfaces. We use [StarUML] (http://staruml.io/) to draw UML diagrams.

The software architect or modeler prepares a UML collaboration with necessary detail filled in. The Collaboration Prototyper specifies a set of rules the user has to follow so that it can generate code from the collaboration. The UML Collaboration reads in the .mdj file generated from StarUML and generates a prototype.

On importing the project, you have to build the artifact and the cbpro.jar file will be generated. It takes in the input file as the argument.

java -jar cbpro.jar input_file
Example: java -jar cbpro.jar ProxyPattern.mdj