|
Q: Who uses Iron Speed Designer?
A: The range of case studies and applications on our website is broad, covering applications from
surgery scheduling to e-commerce. While many of our customers build internally facing applications,
others build externally facing applications and products. You’ll see several software products listed
among our current case studies. Check out our partial customer list and you’ll see corporate IT groups,
manufacturers, financial institutions, consultants and product developers.
Learn more...
Q: How maintainable is the code generated by Iron Speed Designer? How hard is it to update
my applications when you come out with a new release?
A: Most of our customers actively maintain their original applications in the most recent releases
of Iron Speed Designer. For the most part, they install the new release, open the existing
application in Iron Speed Designer, and let Iron Speed Designer “migrate” it for them.
While from time to time there are some aspects of your application that Iron Speed Designer
can't migrate, such as code customizations, these changes occur infrequently.
Q: Iron Speed Designer provides C/R/U/D functionality but doesn’t generate the more challenging
tasks such as business-layer transactions and workflows. Why should I use Iron Speed Designer?
A: Iron Speed Designer does not generate business-layer code and workflows. However, in our
experience, the surrounding create / retrieve / update / delete functionality comprises over
80% of most applications, so Iron Speed Designer provides a significant advantage by eliminating
most of this coding. Why hand-code 100% of an application when you can reduce the work to 20%
hand-coding?
Moreover, Iron Speed Designer generates a class architecture upon which business logic and workflows
can be built, again saving you the time of designing and evolving your own architecture.
Learn more...
Q: I’m worried I won’t be able to sufficiently test applications with code I don’t fully
understand. How difficult is it to test applications generated by Iron Speed Designer?
A: Testing applications and code generated by Iron Speed Designer is no different than testing
your own hand-written custom code. In fact, it is a lot easier.
Code generated by Iron Speed Designer is extremely well tested, simply because is has the benefit of
both Iron Speed’s QA process and thousands of other developers who use and test code generated by
Iron Speed Designer. Using well-tested generated code reduces the overall testing load, so you can
focus on testing the your application's custom code.
Q: Won’t I spend as much time learning Iron Speed Designer as I will save by using it? What’s the
learning curve like?
A: Thousands of our customers have had no difficulty learning how to use Iron Speed Designer.
There are certainly advanced aspects to the tool that require more learning than the basics, but
we don’t hear from many developers who encounter difficulties learning the tool. Even if it takes
a week or two to become proficient with Iron Speed Designer, that still is much shorter than
the amount of time it would take you to generate the 50% to 90% of the application that
Iron Speed Designer can generate.
Q: I use an iterative development process but Iron Speed Designer uses a database-driven
process. What if my database schema is evolving? How will Iron Speed Designer work with my
development style?
A: The advantage of using a code generation approach is that you can regenerate your application each time the database schema changes. Code generation in general, and Iron Speed Designer in particular, are ideal for developing in environments where end-user requirements shift frequently. Applications can be much more easily regenerated with a code generator than they can be changed manually when end-user requirements change.
Iron Speed Designer definitely anticipates database schema changes and includes built-in tools for synchronizing your application with an updated database schema.
|