Application quality and developer productivity keep software
development projects on track and ensure long-term stability.
Disparate development project members and different code languages,
however, can often derail the most organized software development
project. Embarcadero Describe Enterprise solves this problem
by providing a model-driven analysis, design, and development
environment that leverages the Unified Modeling Language™
Describe Enterprise reduces complexity and increases visual
clarity in any type of software development project, ensuring
a sound architecture is established and communicated throughout
the Enterprise. Its rich feature set enables collaboration between
everyone in the enterprise with a stake in the software development
lifecycle, from Business Unit Manager to System Requirements
Architect to Project lead to Application Developers working
in Java, .NET, Visual Basic, C++, C#, and more.
Describe Enterprise provides your development organization with
a “neutral” modeling platform supporting all major
leading code languages including Java/J2EE, Microsoft .NET/C++/C#/Visual
Basic, and others. The result is greater flexibility in new
application development on the best platform to solve the business
problem with no hardware or software vendor lock-in involved.
We realized that, as with software development, web development
required clear documentation. We began to do rigorous documentation
for our projects. I looked at many examples of technical specifications.
I quickly realized that if I was boggled by these technical
specs, our clients would have no hope of understanding them.
We knew we couldn’t write a web site technical specification
like other technical specifications because our clients weren’t
Even when we were working for a technical client, we found
that technical specifications were not an effective form of
communication. While the technology folks do understand the
language of the medium, they are rarely the primary person
responsible for establishing goals and working through the
development process. This is usually left for others, either
upper management, or often the marketing department. In any
case, the project leaders do not often have a strong technical
background. Their technical knowledge was not deep enough
to understand all the technical issues involved in the project.
If you’re not technical, a written technical specification
will make your eyes glaze over. Technical specifications are
not at all effective in communicating to “normal people.”
We had to find a way to document non-technically.
A web site is software. It is written in code, and runs on
a computer. The more dynamic a site (database driven) and
the more functionality it has (integration), the greater the
divide between the clients’ knowledge and the product
they are buying. Not many of the clients we’ve worked
with have had experience purchasing and developing custom
software (which is what a web site ultimately is). This creates
a real barrier to smooth project management. Even if the developer
takes the time to plan and document the specifications for
the project, the client is often unable to understand what
the technical specification is saying. The end result is miscommunication,
missed expectations, project creep, and blown budgets and