Documents

Documentation of the main sample application The project contains one main sample application that enables much more than the library first expected to be capable of. This document should be the main place and the starting point for further reading and it contains stuff that may be added to the PDF version or is from that. First I will add a table of contents that may be filled from time to time. I wish to discuss the usability of this documentation in the mailing list to probably improve the documentation. There may be issues I do not see, because I am the hacker of my software and documentation is - sorry - the second choice of tasks I do :-) Table of contents: Introduction Concept Quickstart Creating an UML model Package names Creating packages Create a classview Create a class diagram Start modeling Create some classes Relate classes Creating attributes Export the UML model Import UML model The frst prototype You have an existing database The sample Postbooks Setup the ODBC connection to the database Create a new UML model (Quickstart) Export of the model in XMI 1.2 and import Prepare for Reverse engineering Export the application as XMI 2.1 Import the XMI 2.1 model in BoUML Start the XMI inport into BoUML Postbooks application as UML model Postbooks application as prototype Applying bussiness rules What are bussiness rules? Technical implementation of bussiness rules A frst bussiness rule Printing Preparing for printing Dynamic parameters Extend the functionality of the prototype Overview: You will learn how to create a database application prototype very fast by using UML and the main sample application that it self is a prototype. The UML diagram looks like this when you follow the documentation:   The application prototype will then look like this (at the time the field Kreditlimit was not shown in the protptype - on the left dialog):   And new is the ability to add bussiness logic such as validations at the scope of the form and not at field level. This is done with UML activity diagrams:   Several values could be validated with a bunch of decisions and proper error messages could be shown in case of wrong conditions. As of the final software release lbDMF-1.0 you have the ability to print reports. Reports are printed via an 'execution action' you could add to your form. Used as the printing engine is xTuples OpenRPT project. Here you see the forms of the application 'lbDMF Manager':   Now you see the CRM project as generated web application:

Options:

View Article Map