60 likes | 181 Vues
This document outlines the Justification for prioritizing UI and database interactions that align closely with business value, emphasizing the importance of clean domain knowledge free from technical clutter. It advocates for representing domain models directly in code, using Java, and applying high-level concepts from Domain-Driven Design (DDD) and streamlined modeling techniques. The approach highlights automatic UI generation from domain models and integrates technologies like Guice for dependency injection, JMock for testing, and AspectJ for aspect-oriented programming, ensuring robust software development practices.
E N D
TeamwareAgile Application Framework XtremeObjects
Justification (Why?) • UI & DB work (60%) does notdirectlyaddvalue to the business • Domainknowledgeshouldbeselfevidentandunpollutedfromtechnicalldetails • Codeshouldbethedomainmodel
What it is? • DomainModeling in Code (Java) • HighLevelConceptsfrom DDD, DNC (Uml in Colors), UML, StreamlinedModeling, xUMLdirectlyonthecode • Automatic UI generationfromdomainmodel
InsideInfo • Guice as DI • AssistedInject (to automaticallycreatefactories for assistedinjection) • Jmock • Hamcrest (AssertionandMatching) • HamcrestCollections (Collectionmatching) • Hibernate • Eclipse Forms • OSGi • EL (ExpressionLanguage) • OCL (ObjectConstraintLanguage) • AspectJ (AspectOriented Programming)