This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Technology Matrix Cell Transitions"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [[category:RIMBAA Issue]] | + | [[category:Closed RIMBAA Issue]] |
| + | Closed - the technology matrix has its uses; documentation of best practices will always cross cells. This avenue of documentation is no longer pursued by RIMBAA. | ||
| + | |||
==Summary== | ==Summary== | ||
| − | *Document/describe (for all possible cell transations) how those steps could be supported/achieved. | + | *Document/describe (for all possible cell transations in the [[Technology Matrix]]) how those steps could be supported/achieved. |
==Analysis== | ==Analysis== | ||
| Line 10: | Line 12: | ||
<table border=1> | <table border=1> | ||
<tr align=center><td></td><td>Persistent Representation</td><td>Object Representation</td><td>Serialized Representation</td></tr> | <tr align=center><td></td><td>Persistent Representation</td><td>Object Representation</td><td>Serialized Representation</td></tr> | ||
| − | <tr align=center><td>RIM (generic) Model</td><td>RP | + | <tr align=center><td>RIM (generic) Model</td><td>RP</td><td>RO</td><td>RS (XML ITS new!)</td></tr> |
| − | <tr align=center><td>RIM Constrained Information Model</td><td>CP | + | <tr align=center><td>RIM Constrained Information Model</td><td>CP</td><td>CO</td><td>CS (XML ITS)</td></tr> |
<tr align=center><td>Application Specific Model</td><td>AP</td><td>AO</td><td>AS</td></tr> | <tr align=center><td>Application Specific Model</td><td>AP</td><td>AO</td><td>AS</td></tr> | ||
</table> | </table> | ||
| Line 17: | Line 19: | ||
The following transitions were deemed to be worthwile of our description: | The following transitions were deemed to be worthwile of our description: | ||
*RP-RO | *RP-RO | ||
| + | **RO<->RP: [[ORM]] software, e.g. Hibernate, JPA | ||
*RO-RS | *RO-RS | ||
*CP-CO | *CP-CO | ||
| Line 27: | Line 30: | ||
*CS-RS | *CS-RS | ||
| − | Note that diagonal cell transitions (e.g. CO to RS) were decided always to involve (however minimalistically) the adjacent *O square (in this example: RO). Therefore | + | Note that diagonal cell transitions (e.g. CO to RS) were decided always to involve (however minimalistically) the adjacent *O square (in this example: RO). Therefore diagonal transitions won't be documented/analysed. |
===Transitions in Dimension 2=== | ===Transitions in Dimension 2=== | ||
| Line 38: | Line 41: | ||
</table> | </table> | ||
| − | The PL-*O | + | The PL-*O transition issue is described on another wiki page: [[Processing Logic in RIMBAA Applications]]. |
| + | |||
| + | Some thoughts about the UI is discussed on [[User Interface for RIMBAA Applications]]. | ||
Latest revision as of 17:26, 4 October 2010
Closed - the technology matrix has its uses; documentation of best practices will always cross cells. This avenue of documentation is no longer pursued by RIMBAA.
Summary
- Document/describe (for all possible cell transations in the Technology Matrix) how those steps could be supported/achieved.
Analysis
- Suggestion was made (during the Orlando WGM) to describe the problem-space (type of problem) as well as the path itself. That to determine if different problem spaces lead to different paths through the technology matrix.
Transitions in Dimension 1
| Persistent Representation | Object Representation | Serialized Representation | |
| RIM (generic) Model | RP | RO | RS (XML ITS new!) |
| RIM Constrained Information Model | CP | CO | CS (XML ITS) |
| Application Specific Model | AP | AO | AS |
The following transitions were deemed to be worthwile of our description:
- RP-RO
- RO<->RP: ORM software, e.g. Hibernate, JPA
- RO-RS
- CP-CO
- CO-CS
- AO-CO
- CO-RO
- AO-RO
- AS-CS
- AS-RS
- CS-RS
Note that diagonal cell transitions (e.g. CO to RS) were decided always to involve (however minimalistically) the adjacent *O square (in this example: RO). Therefore diagonal transitions won't be documented/analysed.
Transitions in Dimension 2
| Processing/Business Logic | Object Representation | User Interface |
| PL | RO | UI |
| CO | ||
| AO |
The PL-*O transition issue is described on another wiki page: Processing Logic in RIMBAA Applications.
Some thoughts about the UI is discussed on User Interface for RIMBAA Applications.
