DEV475 Mastering Object-Oriented Analysis and Design with UML ...
Share Embed Flag
Download ePaper

DEV475 Mastering Object-Oriented Analysis and Design with UML ...

DEV475 Mastering Object-Oriented Analysis and Design with UML ... DEV475 Mastering Object-Oriented Analysis and Design with UML ...

crnarupa.singidunum.ac.rs
from crnarupa.singidunum.ac.rs More from this publisher
12.07.2015 Views

DEV475 Mastering Object-Oriented Analysis and Design with UMLVisual Modeling With the Unified Modeling LanguageVisual Modeling With the Unified Modeling Language• Multiple views• Precise syntax andsemanticsSequenceDiagramsUse-CaseDiagramsClassDiagramsStaticDiagramsObjectDiagramsCollaborationDiagramsModelsComponentDiagramsDynamicDiagramsStatechartDiagramsActivityDiagramsDeploymentDiagramsMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved20In building a visual model of a system, many different diagrams are needed torepresent different views of the system. The UML provides a rich notation forvisualizing models. This includes the following key diagrams:• Use-Case diagrams to illustrate user interactions with the system• Class diagrams to illustrate logical structure• Object diagrams to illustrate objects and links• Component diagrams to illustrate physical structure of the software• Deployment diagrams to show the mapping of software to hardwareconfigurations• Activity diagrams to illustrate flows of events• Statechart diagrams to illustrate behavior• Interaction diagrams (that is, collaboration and sequence diagrams) to illustratebehavior1 - 20

ƯÁ¤¹®¼- ¿¡ ´ëÇ Ñ º ¸±â¸¦»ç¿ëÀÚ°¡ ¿äûÇÑ´Ù.È-ÀÏ°ü¸®ÀÚ´Â Àоî¿Â¹®¼ -ÀÇ Á ¤º¸¸¦ ÇØ ´ç ¹® ¼-°´Ã¼¿¡ ¼³Á¤À» ¿äûÇÑ´Ù.È-¸é °´Ã¼´Â ÀоîµéÀΰ ´Ã¼µé¿ ¡ ´ëÇØ À̸§ º° ·ÎÁ ¤·ÄÀ» ½ÃÄÑ È-¸é¿¡º¸ ¿©ÁØ´Ù.Forwarduser : Clerkuser1: Doc vi ew request ( )mainWnd : MainWndfileMgr : FileMgrrepository : Repository1: Doc v iew request ( )L9: sortByN ame ( )2: fetc hDoc( )7: readFile ( )5: readDoc ( )mainWnd fileMgr :FileMgr9: sortByName ( )2: fetchDoc( )3: create ( )6: fill Document ( )4: create ( )8: fillFile ( )document :Document4: c reate ( )8: fillFile ( )3: create ( )6: fillDocument ( )5: readDoc ( )7: readFile ( )gFile : GrpFiledocument : DocumentgFilerepositoryrepRepositoryname : char * = 0readD oc( )readFile( )FileMgrfetchD oc( )sortByName( )(from Persistence)FileListadd( )del ete( )read( )FileDocumentListad d( )del ete( )fList1GrpFileread( )op en( )create( )fillFile( )Documentname : i ntdoci d : intnumField : intget( )open( )close( )read( )sortFileList( )create( )fillDocument( )read() fill thecode..OpenningReadingadd file [ numberOffile==MAX ] /flag OFFclose fileClosingclose fileadd fileWritingWindow95¹®¼ -° ü¸®Å¬óÀ̾ðÆ®.EXEWindowsNTW indow sNT¹®¼-°ü¸® ¿£Áø.EXEWindows95IBMMainfra meµ¥ÀÌŸº£À̽º¼-¹öSolarisÀÀ¿ë¼-¹ö.EXEW indow s95¹®¼-°ü¸® ¾ÖÇø´AlphaUNIXModule 1 - Best Practices of Software EngineeringVisual Modeling Using UML DiagramsVisual Modeling Using UML DiagramsUse-CaseDiagramClass DiagramStatechartDiagramUse Case 1Actor AActor BUse Case 2Use Case 3CollaborationDiagramFileManagerRepositoryDocumentListDeploymentDiagramDocumentGraphicFileFileFileListSequenceDiagramMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reservedComponentDiagram21andReverseEngineeringTargetSystemVisual modeling with the UML makes application architecture tangible, permitting usto assess it in multiple dimensions. How portable is it? Can it exploit expectedadvances in parallel processing? How can you modify it to support a family ofapplications?We have discussed the importance of architectural resilience and quality. The UMLenables us to evaluate these key characteristics during early iterations — at a pointwhen design defects can be corrected before threatening project success.Advances in forward and reverse engineering techniques permit changes to anapplication’s model to be reflected automatically in its source code, and changes toits source code to be automatically reflected in its model. This is critical when usingan iterative process, in which we expect such changes with each iteration.1 - 21

ƯÁ¤¹®¼- ¿¡ ´ëÇ Ñ º ¸±â¸¦»ç¿ëÀÚ°¡ ¿äûÇÑ´Ù.È-ÀÏ°ü¸®ÀÚ´Â Àоî¿Â¹®¼ -ÀÇ Á ¤º¸¸¦ ÇØ ´ç ¹® ¼-°´Ã¼¿¡ ¼³Á¤À» ¿äûÇÑ´Ù.È-¸é °´Ã¼´Â ÀоîµéÀΰ ´Ã¼µé¿ ¡ ´ëÇØ À̸§ º° ·ÎÁ ¤·ÄÀ» ½ÃÄÑ È-¸é¿¡º¸ ¿©ÁØ´Ù.Forwarduser : Clerkuser1: Doc vi ew request ( )mainWnd : MainWndfileMgr : FileMgrrepository : Repository1: Doc v iew request ( )L9: sortByN ame ( )2: fetc hDoc( )7: readFile ( )5: readDoc ( )mainWnd fileMgr :FileMgr9: sortByName ( )2: fetchDoc( )3: create ( )6: fill Document ( )4: create ( )8: fillFile ( )document :Document4: c reate ( )8: fillFile ( )3: create ( )6: fillDocument ( )5: readDoc ( )7: readFile ( )gFile : GrpFiledocument : DocumentgFilerepositoryrepRepositoryname : char * = 0readD oc( )readFile( )FileMgrfetchD oc( )sortByName( )(from Persistence)FileListadd( )del ete( )read( )FileDocumentListad d( )del ete( )fList1GrpFileread( )op en( )create( )fillFile( )Documentname : i ntdoci d : intnumField : intget( )open( )close( )read( )sortFileList( )create( )fillDocument( )read() fill thecode..OpenningReadingadd file [ numberOffile==MAX ] /flag OFFclose fileClosingclose fileadd fileWritingWindow95¹®¼ -° ü¸®Å¬óÀ̾ðÆ®.EXEWindowsNTW indow sNT¹®¼-°ü¸® ¿£Áø.EXEWindows95IBMMainfra meµ¥ÀÌŸº£À̽º¼-¹öSolarisÀÀ¿ë¼-¹ö.EXEW indow s95¹®¼-°ü¸® ¾ÖÇø´AlphaUNIXModule 1 - Best Practices of Software EngineeringVisual Modeling Using <strong>UML</strong> DiagramsVisual Modeling Using <strong>UML</strong> DiagramsUse-CaseDiagramClass DiagramStatechartDiagramUse Case 1Actor AActor BUse Case 2Use Case 3CollaborationDiagramFileManagerRepositoryDocumentListDeploymentDiagramDocumentGraphicFileFileFileListSequenceDiagram<strong>Mastering</strong> <strong>Object</strong> <strong>Oriented</strong> <strong>Analysis</strong> <strong>and</strong> <strong>Design</strong> <strong>with</strong> <strong>UML</strong>Copyright © 2003 Rational Software, all rights reservedComponentDiagram21<strong>and</strong>ReverseEngineeringTargetSystemVisual modeling <strong>with</strong> the <strong>UML</strong> makes application architecture tangible, permitting usto assess it in multiple dimensions. How portable is it? Can it exploit expectedadvances in parallel processing? How can you modify it to support a family ofapplications?We have discussed the importance of architectural resilience <strong>and</strong> quality. The <strong>UML</strong>enables us to evaluate these key characteristics during early iterations — at a pointwhen design defects can be corrected before threatening project success.Advances in forward <strong>and</strong> reverse engineering techniques permit changes to anapplication’s model to be reflected automatically in its source code, <strong>and</strong> changes toits source code to be automatically reflected in its model. This is critical when usingan iterative process, in which we expect such changes <strong>with</strong> each iteration.1 - 21

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!