Core Issues of Naked Objects Architectural Pattern
The Naked Objects Architectural Pattern was conceived in 1999, and is the foundation for our TrueView™ framework.
Naked Objects extends traditional software architecture with a fresh approach, whilst retaining the essence of software best practices.
Key benefits of Naked Objects
The Naked Objects Pattern is ideal for applications that:
- Are better at accommodating unforeseen changes
- Take less development effort
- Provide a common understanding between users and developers
- Force better design of the software
- Take advantage of your user’s problem solving abilities
What is a ‘Naked object’?
Naked Objects represent entities within your business. They could be tangible, like Customers and Invoices, or intangible such as Payments or History. Effort is only placed in the development of these objects, and little else.
Naked Objects are then exposed directly to the end-user, for them to manipulate as needed.
IBM impressed by Naked Objects
DSFA commit to Naked Objects
In 2001, Ireland’s Department of Social and Family Affairs (DSFA) committed to using Naked Objects for their enterprise systems.
Two mission critical systems have been deployed to date.