RIPPLE-TRAC is like a skeleton key, it opens doors into your computer code
regardless of computer language.
RIPPLE-TRAC finds it greatest benefit in helping z/OS organizations distinguish
high- from low-leverage features or behaviors (concerns) in highly complex systems. In effect, RIPPLE-TRAC lies in seeing through complexity to the underlying structures and relationships regardless of computer language.
RIPPLE-TRAC organizes the complexity into a coherent story that illuminates the concerns and how the concerns can be decomposed into manageable and comprehensive parts without investing in new hardware.
Multi-dimensional separation of concerns is an approach to separation of concerns, supporting construction, evolution and integration of software. Its goals are to enable:
Encapsulation of all kinds of concerns in a software system, simultaneously.
Overlapping and interacting concerns.
On-demand remodularization.
Separation of concerns is a concept that is at the core of software engineering. It refers to the ability to identify, encapsulate, and manipulate those parts of software that are relevant to a particular concern (concept, goal, purpose, etc.). Concerns are the primary motivation for organizing and decomposing software into manageable and comprehensible parts. Many kinds of concerns may be relevant to different developers in different roles, or at different stages of the software lifecycle.
Appropriate separation of concerns has been hypothesized to reduce software complexity and improve comprehensibility; promote traceability; facilitate reuse, non-invasive adaptation, customization, and evolution; and simplify component integration.
The term multi-dimensional separation of concerns (MDSOC) refers to flexible and incremental separation, modularization, and integration of software artifacts based on any number of concerns.
RIPPLE-TRAC overcomes limitations of existing mechanisms by permitting clean separation of multiple, potentially overlapping and interacting concerns simultaneously (500 at a time). RIPPLE-TRAC promotes reuse, improves comprehension, reduces the impact of change, eases maintenance and evolution, improves traceability, and opens the door to system refactoring and reengineering.
Click this Link to see a schematic of how RIPPLE-TRAC creates separation of concerns
The separation allows:
To allow people to work on individual pieces of the system in isolation;
To facilitate reusability;
To ensure the maintainability of a system;
To add new features easily;
To enable everyone to better understand the system;
To allow support for multi-dimensional separation of concerns.
Remember, a dimension of concern is simply an approach to decomposing, organizing, and structuring software according to concerns of a particular kind. RIPPLE-TRAC falls into the realm of multi-dimensional separation of concerns.
50 Great Reasons to choose RIPPLE-TRAC over TSO 3.14
WE ALSO PROVIDE WORKSHOPS
ON SITE TRAINING WITH REAL WORLD GUIDANCE INTO YOUR EXISTING LEGACY SYSTEMS
You can use RIPPLE-TRAC or we can do it for you on our mainframe.