8 | | |
9 | | We don't think so... |
10 | | In this approach |
11 | | |
12 | | |
13 | | Model-based Source Code Editing |
14 | | generates UML-like views of classes, methods, and their relationships being involved in a specific test case. Based on such mid-level abstractions, developers can edit these models and the related source code is changed automatically in background. |
15 | | |
16 | | |
17 | | (see also [wiki:path:pathView PathView]). |
| 12 | We propose model-based source code editing that makes no difference between a model and the underlying source code. |
| 13 | Our single-source technique relies on source code and test cases as executable program representations and allows developers to derive higher-level abstractions. |
| 14 | This baseline enables a comfortable synchronization mechanism that reflects changes in the model directly in source code and vice versa. |
| 15 | Based on such mid-level abstractions, developers can edit these models and the related source code is changed automatically in background. |
| 16 | [wiki:path:pathView PathView] is our model-based source code editor that semi-automatically creates class diagrams for a specific concern. |
| 17 | Depending on the development tasks, developers can now choose if they prefer a standard browser or a model and they can switch whenever desired. |