Rapid Programming Cycles with InstantView®

At all stages, working with InstantView® is faster than any conventional application development. Above all, costs will be reduced due to reusable application elements and a highly flexible and intelligent business model.

Conventional InstantView®

traditional architecture

InstantView architecture
Conventional Design
  • No domain restriction
  • Use case can be taken as is
  • ER model expansion to fit the use case
  • Use case can be an isolated application
  • Top down design
  • Use case design is a matter of data modeling
 Design with InstantView®
  • Focus on business domain
  • Questioning use case required
  • Use case reduction to the abstract structure of the existing object-oriented model
  • Use case is always part of a complete virtual company mapping
  • Bottom up design
  • Use case design is a matter of designing the user interface
Implementation (conventional)
  • Table and relation declaration, definition mapping, DB, GUI programming
  • Comprehensive program development cycles
  • Application logic has to be programmed
 Implementation with InstantView®
  • Dummy class and slot definition
  • Immediate, incremental runtime implementation
  • Application logic transfer into data
Updating/Maintenance (conventional) 
  • Use case upgrading usually causes data model modification or even a complete redesign
 Updating/Maintenance with InstantView®  
  • Use case upgrading rather causes a more extensive reusability of already existing objects and functionality
Conclusion
  • Using more and more complex technologies does not necessarily make application development easier
 Conclusion
  • A simple interface and encapsulated complexity cause faster application development and a broad functionality

simplified architecture layer - simplified implementation layers - simplified application programming