Your SlideShare is downloading. ×
0
Mcom Ba Training   Module 2
Mcom Ba Training   Module 2
Mcom Ba Training   Module 2
Mcom Ba Training   Module 2
Mcom Ba Training   Module 2
Mcom Ba Training   Module 2
Mcom Ba Training   Module 2
Mcom Ba Training   Module 2
Mcom Ba Training   Module 2
Mcom Ba Training   Module 2
Mcom Ba Training   Module 2
Mcom Ba Training   Module 2
Mcom Ba Training   Module 2
Mcom Ba Training   Module 2
Mcom Ba Training   Module 2
Mcom Ba Training   Module 2
Mcom Ba Training   Module 2
Mcom Ba Training   Module 2
Mcom Ba Training   Module 2
Mcom Ba Training   Module 2
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Mcom Ba Training Module 2

930

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
930
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. IT BUSINESS ANALYST<br />CAREER TRAINING<br />MODULE 2<br />
  • 2. WELCOME<br />
  • 3. AGENDA<br />INTRODUCTION TO UML<br />INTORDUCTION TO RATIONAL ROSE<br />DATA FLOW DIAGRAMS<br />USER INTERFACE (UI) STORYBOARDS<br />Q & A<br />
  • 4. OBJECT ORIENTED DESIGN<br />What is a model ?<br /><ul><li>A model is a simplification of reality.</li></ul>E.g., a miniature bridge for a real bridge to be built<br /><ul><li>Well...sort of….but not quite
  • 5. A model is our simplification of our perception of reality
  • 6. A model is an abstractionof something for the purpose of understanding, be it the problem or a solution.</li></li></ul><li>OBJECT ORIENTED DESIGN<br />Why a model ?<br /><ul><li>To understand why a software system is needed, what it should do, and how it should do it.
  • 7. To communicate our understanding of why, what and how.
  • 8. To detect commonalities and differences in your perception, my perception, his perception and her perception of reality.
  • 9. To detect misunderstandings and miscommunications. </li></li></ul><li>OBJECT ORIENTED DESIGN<br />
  • 10. OBJECT ORIENTED DESIGN<br />Water<br />Fresh water<br />have<br />Rivers<br />Oceans<br />have<br />have<br />live in<br />Salt water<br />have<br />Crocodiles<br />Fish<br />have<br />Penguins<br />
  • 11. INTRO TO UML<br />UML DIAGRAMS<br /><ul><li>Use case Diagrams
  • 12. Activity Diagrams
  • 13. Sequence Diagrams
  • 14. Collaboration Diagrams
  • 15. Package Diagrams
  • 16. Statechart Diagrams
  • 17. Class Diagrams
  • 18. Object Diagrams
  • 19. Component Diagrams
  • 20. Deployment Diagrams</li></li></ul><li>INTRO TO UML<br />Use case Diagrams<br />
  • 21. INTRO TO UML<br />Use case Diagrams<br />
  • 22. INTRO TO UML<br />
  • 23. INTRO TO UML<br />Use case Diagrams<br />USE CASE<br />Generalization<br />DEPENDENCY<br />ACTOR<br />
  • 24. INTRO TO UML<br />Activity Diagrams<br />
  • 25. INTRO TO UML<br />Activity Diagrams<br />
  • 26. INTRO TO UML<br />Activity Diagrams<br />
  • 27. INTRO TO UML<br />Activity Diagrams<br />DECISION<br />END <br />STATE<br />INITIAL <br />STATE<br />FLOW<br />ACTIVITY<br />TRANSITION<br />SWIMLANE<br />
  • 28. DATA FLOW DIAGRAMS<br />
  • 29. STORYBOARDS<br />
  • 30. STORYBOARDS<br />
  • 31. Q&A<br />

×