SHOWCASE
In this section you can find descriptions of several example projects from practice. They demonstrate the variety of possible applications realised with the help of ModuleStudio. It ranges from fun and experimental projects to research and business applications. There is also a playground available at our demo site.
Connector
In the course of our work on a modular system for ecommerce applications, the need to import and export different data from different modules in a flexible way arose. An application for just this purpose has been modeled. So, without further ado: the Connector.
In the model, varying tasks are represented by workflows. Beside a name and a description they have a state, for example: waiting, running or error. A workflow serves primarily as a container element to execute a complete process.
The „workflowJob“ entity stores the more interesting parts of a connector. A workflow consists of multiple jobs, each referring to an entity and representing either an import or an export. Different file formats and various settings are supported. The current version supports importing from xml, csv and ASCII files. In addition to those formats, exporting also supports the output of pdf files.
The Connector module is not limited to simple import and export operations, however. The image shows a… >read more
CocktailManager
Who has not run into this problem: you want to mix a drink, and the exact ingredients required are not available in the house. The solution is obvious: wouldn't it be nice to have a cocktail menu that always corresponds to the actual stock on hand? Problem defined... solution modeled!
The CocktailManager allows one to store cocktail recipes and the different ingredients each needs. As with any recipe, the required amount of each ingredient that goes into a particular cocktail will be stored. Each user can then define how much of which ingredients he has on hand at the moment. In addition, a user can input the minimum amounts needed for normal usage, and the minimum amounts needed for parties. This makes it possible for the CocktailManager to, for example, make tequila recipes available only after there are at least two bottles available.
The module creates four dynamic reports: two cocktail menu cards, complete with recipes, but limited to those cocktails for which all ingredients are in stock (one card for normal use and the other for parties), a bartender's cheat sheet for reviewing all of the recipes, and a shopping list containing everything not in stock at the moment.
Since modeling the basic module took, essentially,… >read more
Modular shop system
Many web sites with complex substructures, such as web-based shopping sites, are not implemented using a modular architecture. When such sites require changes or new features to be implemented in one aspect of the system, a chain-reaction often occurs causing unanticipated changes to cascade through the rest of the system. This can often trap a customer into a fragile system that is expensive to enhance or maintain. Small changes in content can result in unforeseen additional costs. After implementing a few shop projects, the costs and effort of maintaining customisations for several individual client projects begins to add up.
For our clients, we have designed a shop system consisting of a several individual modules using ModuleStudio. The modular design helps us avoid some of the pitfalls described earlier. As the picture points out, there are management areas for customers, products and orders, as well as modules for shipping, payment, and sales promotions. The two modules ERP-Sync and Connector allow data to be exchanged between ours and other systems. The pricing module allows one to define different currencies, price lists, and pricing rules, including discounts, extra charges, taxes, and other similar things.
>read more