Andere Kunden interessierten sich auch für
![OPTICAL MODELING TECHNIQUES FOR UML]( "OPTICAL MODELING TECHNIQUES FOR UML")
OPTICAL MODELING TECHNIQUES FOR UML29,99 €![Python Mania]( "Python Mania")
Python Mania51,99 €![A Framework for Sharing Constructivist E-Learning Resources]( "A Framework for Sharing Constructivist E-Learning Resources")
A Framework for Sharing Constructivist E-Learning Resources36,99 €![Smart Glasses For Blind People]( "Smart Glasses For Blind People")
Smart Glasses For Blind People32,99 €![A Practical Guide to Using UML Tools in System Analysis and Design]( "A Practical Guide to Using UML Tools in System Analysis and Design")
A Practical Guide to Using UML Tools in System Analysis and Design32,99 €![Behavioural Models]( "Behavioural Models")
Behavioural Models37,99 €![Recherche en informatique]( "Recherche en informatique")
Recherche en informatique29,99 €
We have performed in this work some extensions to UML in order to give opportunity to designers to deal with exception handling in the early phases of software life cycle. We have done our proposed extensions according to a defined profile that extends UML in order to introduce exception handling concepts, notations and terminology in UML diagrams. This feature does not exist in standard UML. Extensions we have done have been applied to use case and sequence diagrams. These extensions are translated to graphical notations that make sense for designers. Designers have looked always after making standard use case diagram and defining standard interactions or sequence diagram, then the developer will look after exception handling in the last phase of software life cycle. Even developer could sometimes extract all exceptions and define their handlers efficiently, but this is dependent on the kind of the software that he implements. Our approach push the designer to avoid these mistakes, because the difficulty of making a reliable software will be divided between designers and developers and dissociated along the software life cycle.