Dashboard > Spider [en_US] > ... > Motivation for use > Abstract complexity
Log In View a printable version of the current page. Portuguese English
Abstract complexity
Added by Bruno Braga , last edited by Bruno Braga on May 24, 2008  (view change)
Labels: 
(None)


The complexity is one of the major problems of software development. Raise the level of abstraction helps reduce this problem.
We want the developer have more focus on technological decisions and business rules of project and not spend so much time solving problems created by the complexity of software development.

Take a classic example that illustrates the importance of abstraction:
The final code of a computer program (compiled) is very complex to be written by human beings. The compilation came along with the first programming languages such as Assembler. The programming languages are nothing more than abstractions to make life easier for developers, and for years and years languages appeared increasingly powerful and with a higher level of abstraction that facilitate the lives of developers.

But the key point of this topic is to have the maximum of abstraction without losing control and power than we are doing. This is one of the factors that separate languages successful, unsuccessful. The same concept can be used for a generate code tool. Our focus is to raise the level of abstraction without masking the code behind visual interfaces, ie: you have total control over all code generated by the tool and not be dependent on J2EE Spider.
This tool is based on templates, and you can customize it so you can reuse assets, components and standards used by his team. All this allows raise the level of abstraction without losing control and power.

Focus more on business is one of the concepts of Business-driven development.

I'd rather have my team know what they are doing than being dependent on a tool that, instead of giving the "abstraction" makes life harder... Why another tool for abstraction? OOP abstracts the real world already...

Posted by Anonymous at May 27, 2008 11:57 | Reply To This

His team has to know what you're doing. That is correct!

But his team can make a template with artifacts that support the projects (not related to business), and use a tool to create, customize and set-up then in all projects, saving time.

So you abstract complexity of settings and repetitive tasks. But you will remain owner of source code of your project to provide maintenance! Then you have to know what was done.

The dependence of the code with this tool doesn't exist. This is a great advantage.
This tool is only a support for your team. Not a black box.

Powered by a free Atlassian Confluence Open Source Project License granted to J2EE Spider. Evaluate Confluence today.
Powered by Atlassian Confluence 2.7.1, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators