02341: Model-based Software Engineering (f16)

On this page, you will find some hints on the final submission for the project of the course Model-based Software Enineering (02341) in Spring 2016.

Altogether, the submission should consists of three parts:

• All the source code of your YAWL editor and YAWL simulator:
  the source code should be submitted as exported Eclipse projects from your Eclipse development workbench; make sure that you use the Eclipse export mechanism for that and that this can be successfully imported on a different computer (no absolute path names, ...).

   

• At least two YAWL examples of realistic workflows:
  these examples should be submitted as one or more PNML files, which should be compatible with your YAWL Petri net type definition of your software.

   

• A written report covering the "why", the "what" and the "how" of your software:
  this report should be submitted as a PDF file.

   

  Note that your report needs to include:

  • a motivation;
  • an introduction to YAWL and its graphical notation;
  • an analysis section covering an overview of the GUI and the use of your software;
  • a careful presentation of the domain starting from a discussion of examples, and then discussing the domain model as a continuous text;
  • the scope of the project;
  • a discussion of the more technical EMF diagrams realizing the YAWL type of the ePNK and a discussion of additional constraints, as well as the EMF models for annotations;
  • a discussion of the realization of the graphical features of your YAWL nets;
  • a detailed discussion of your simulator application, its different components, and how they interact with the ePNK using appropriate UML diagrams, which should including the action and presentation handlers;
  • some interesting imlementation details;
  • a concise handbook on how to use your YAWL editor and simulator and a discussion of the YAWL examples that you provided (from a business process modelling perspective); the handbook should cover all features of your YAWL editor and simulator.

   

• Authorship:
  Make sure that in the code all non-generated classes and methods have an @author tag with the name and student number of the students who have implemented the class/method. For each section and subsection of the report, information should be provided who authored it (with name and student number).