Refactoring object-oriented frameworks
Refactoring object-oriented frameworks
Smalltalk: best practice patterns
Smalltalk: best practice patterns
Characterizing IS development projects
Proceedings of the IFIP TC8, WG8.1/8.2 working conference on method engineering on Method engineering : principles of method construction and tool support: principles of method construction and tool support
The Unified Modeling Language user guide
The Unified Modeling Language user guide
The Unified Modeling Language reference manual
The Unified Modeling Language reference manual
The unified software development process
The unified software development process
Refactoring: improving the design of existing code
Refactoring: improving the design of existing code
Adapting Analysis and Design to Software Context: The JECKO Approach
OOIS '02 Proceedings of the 8th International Conference on Object-Oriented. Information Systems
An Assembly Process Model for Method Engineering
CAiSE '01 Proceedings of the 13th International Conference on Advanced Information Systems Engineering
Towards a UML profile for interaction design: the wisdom approach
UML'00 Proceedings of the 3rd international conference on The unified modeling language: advancing the standard
Towards a UML profile for software architecture descriptions
UML'00 Proceedings of the 3rd international conference on The unified modeling language: advancing the standard
| Hi-index | 0.00 |
Currently, fewer and fewer applications are developed from scratch. Therefore, with any development process, it is very important to determine during the analysis and design phases whether there are any applications that must be safeguarded and how this could be accomplished. Legacy applications, as well as Enterprise Resource Planning integration are typical examples of developments that deal with safeguarding. Indeed, safeguarding may be necessary for a specific piece of work involving the integration of new developments with different parts of running applications. To support such a difficult but fundamental task, we recommend a set of extensions through a UML profile. In this proposal, we highlight three aspects of safeguarding which have to be taken into account: the business expertise, the interfaces, and the code itself. We then present how this profile can be used along the different phases of analysis and design; applicable guidelines are provided to support software designers in their daily work.