TinyModeler is a domain modeling web application made for programmers and application designers. Below, you'll find some screenshots of the application and a list of frequently asked questions.
Frequently Asked Questions
ContentsWhat is Domain Modeling? Why TinyModeler? Who makes TinyModeler? What are the browser requirements to use TinyModeler? The models look like UML (Unified Modeling Language) class diagrams or Entity Relationship Diagrams, what's the difference? What languages do you support for code generation? But, TinyModeler doesn't have feature X! Will TinyModeler always have a free option? If I sign up for an account, will you spam me or sell my information?
What is Domain Modeling?
According to Wikipedia, Domain Modeling is: A conceptual model of a domain of interest (often referred to as a problem domain) which describes the various entities, their attributes and relationships, plus the constraints that govern the integrity of the model elements comprising that problem domain.You could also call it data modeling or class diagraming. It's basically a way for software architects and designers to model the data and interactions for a particular problem domain in a succinct and descriptive diagram.
TinyModeler isn't the first domain modeling tool on the market. It's also not the one with the most features. We designed it from the ground up to be intuitive and useful.
Who makes TinyModeler?
TinyModeler is developed by Tiny Mission, a web and mobile software development company in Minnesota. We wrote it as a way to scratch a particular itch we have while designing software for our clients. We needed a fast and easy way to develop domain models that could effectively communicate and application's design. Not happy with the tools currently on the market, we decided to write our own.
What are the browser requirements to use TinyModeler?
The models look like UML (Unified Modeling Language) class diagrams or Entity Relationship Diagrams, what's the difference?
The model diagrams created with TinyModeler incorporate aspects of traditional entity relationship diagrams and UML class diagrams. These two tools are often taught separately and treated independently. However, they are meant to accomplish similar tasks.
On very large projects, the data modeling for the database might be done by a totally separate team from the business logic class designers. However, for most applications of reasonable size and complexity, these tasks are done by the same people. Having one tool for data modeling and class designing is a pragmatic approach to software design.
What languages do you support for code generation?
We currently support generating SQL schemas, Ruby on Rails models and migrations, and C# classes. We plan to add support for at least Java, Python, and Objective-C in the future.
But, TinyModeler doesn't have feature X!
While we're still in beta and there are some more features that will make it out in the final release, the feature list for TinyModeler was specifically chosen to keep it simple to understand and easy to use. We kept what we need to get the job done, and threw out the rest. If you want something that implements the entire UML 2.x Class Diagram specification, you'll have to go somewhere else.
Will TinyModeler always have a free option?
Yes, we will always offer a free account option that allows you to use the system for some fixed number of models.
If I sign up for an account, will you spam me or sell my information?
No. Account holders may receive periodic notifications of new features or expected server down time, but we won't send unsolicited advertisements or bug you in any other way. Your e-mail address will only be used for said anouncements and won't be sold to third parties.