• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Supporting Documentation - Part II

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am done with the diagrams for Part II and am in the process of creating the supporting documentation. I have checked and rechecked the exam deliverables for Part II and they don't mandate supporting documentation. Considering Part III is about the decisions you made for Part II what amount of supporting documentation is really required? I am basically planning on providing documentation only for the class and component diagrams and possibly an assumptions document. Is there really any need for documenting the sequence diagrams? I would really appreciate some guidance from people who have taken Part II.
 
Ranch Hand
Posts: 149
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Anand Jaiswal:
I am done with the diagrams for Part II and am in the process of creating the supporting documentation. I have checked and rechecked the exam deliverables for Part II and they don't mandate supporting documentation.



Only assumptions document is required.
 
Ranch Hand
Posts: 172
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
if you have good diagrmas .. UML speak for itself, so you dont need to write a los of documentation explaning wath you do, bu for example if you change some cardinalities of DBM you mus justify it ...
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic