LORE Method for Object-Oriented Development

A Standard-Based, Process-Driven, Tool-Enabled Object-Oriented Approach

LORE is a process that allows the timely delivery of high quality and robust software systems. The method integrates a set of process components that are structured to guide the development team from gathering requirements through to testing the finished system in a consistent manner. A thorough understanding of group dynamics and project management has been applied to ensure the process is smooth and the sequence of steps forms a series of logical extensions without confusing changes in focus.

The process components that form the LORE Method are adapted from many years experience in developing object-oriented systems and build on refinements of existing methodologies where they have proved successful. Recently, with the industry convergence towards the Unified Modelling Language (UML), Elixir has adapted the LORE Method to incorporate UML notations. Beyond adopting UML notations, LORE is unique in its infrastructure and focus of the techniques on encouraging the object-oriented mindset through guidelines and heuristics. Its emphasis is on the process of building object-oriented systems, rather than on the notation used to represent such designs. It is more important that object-oriented developers have a proven process to follow, which prescribes the necessary actions to develop a system.

Components have been integrated with the process to address Process Metrics, RDBMS integration and Detailed Design Specification to allow maximum code generation, for those projects that require these features.

Processes and Techniques

Discovery Team
A CRC-based approach that allows the group to explore the problem domain and highlight the key objects and interactions.

Object Glossary
Explores the objects participating in the system solution and the structural relationships between them.

Scenario Specification
Identifies the behaviour of objects through the sequence of interactions and collaborations between them.

Service Glossary
Defines the instance and class services of objects to support their structure and interaction with other objects. Contracts are used to ensure the complete and explicit specification of class interfaces.

Attribute Glossary
Defines the instance and class attributes directly accessible to the user. This includes type, format and other constraints on the attributes values. Modularity is ensured as attribute encapsulation is not breached.

Class Design
Captures more detailed design characteristics and considerations, such as memory usage, performance, timing etc. including the documentation of unit test cases for the class.

Testing
The information captured by the other process components provides a detailed integration and system test plan to ensure the quality of the system produced and conformance with requirements.

HOME | PRODUCTS | TRAINING | CONSULTANCY | ABOUT US