ADMIN 2004; Nastansky, Ludwig: Middleware on top of Middleware: Notes/Domino-Integration erfordert Komponentisierung im N/D-Development, GCC 2003.

40 Lotus Notes/Domino (N/D) hat seine Rolle geändert. War N/D zunächst eine hocheffiziente Technologie für Groupware-Insellösungen, so sind aktuell Leistungsprofil und Produktivität als leistungsfähige Middleware-Plattform zur Entwicklung kollaborativer Lösungskomponenten in einem integrierten Kont...

THEMES: ADMIN 2004 | Nastansky, Ludwig\...\03_ADMIN_Muenc...
YEAR: 2003

Comments/attachments: Close
Middleware on top of Middleware:

N/D-Integration erfordert Komponentisierung im N/D-Development

  • 0 Scenario, Context, Motivation
    e-Business Architectures
  • 1 Collaborative Solutions
  • 2 N/D rtf Undervalued
    e-business is e-documents
  • 3 N/D Pseudo Form:
    optimize complexity
  • 4 Graphical UIs:
    have imagination
  • 5 Q&A
  • Contacts


Login (when asked for):
ID: GCC-MediumAccess
PW: knowledge

Best viewed with 1280 pixel hoizontal resolution.
WACO-Demo (web access control object) <alt> ARV
Using pseudo-forms
instead of N/D-native form design:
An option with PROs and CONs
  • Independance from N/D designer, including
    people / skills & corporate development process
  • Narrowing omplexity gap: distributed & versatile user demands vs. development process
  • Independant form corporate design changes on NSFs (refresh/replace design)
  • Re-use concept/documents with pseudo-forms in arbitrary NSFs independatn from design
  • Mobile: can be communicated via simple (mail-) messaging
  • Less complex database architecture
  • Persistence of objects: no direct global re-design mechanism
  • Security
  • Transparency of 'hidden' document-embedded field collections
  • UI poorer than native N/D-design forms
  • N/D architecture not optimized for this approach
. 3c