äR\{ŒŘ§MŽąSxĐ)–ÓZß;„3˘N‘ kçîhîŞűöŐĽťdI°Yiĺ~˘?ݚ‘őIĽĐ‘íČŽŘ "h5hŻźŞ *iǏ ŕ] /3Öʆ dőŒúočŸĆuâœ„ }Ž‹Ç ˆzڔŮ !Œl‰_Ç %ó™˛Ŕ )–Iřö š÷ĹźŐ-§cc\ą1´KŤb™5ť‡ŢQŕ9Ĺ€Üů˘=ËA ÝtBŮ0$Qä„F  ‘ayŽJ„sĺ’Nţx*ç–RŇ>ˇ ×|ŠŤV­pý€ą Z$:şV’ť) D†čÄ ,§DÚŐľ§jÖÚ U2΂ĺ![ya,é ËąB˘ĐOm8@€0€˙˙˙˙8@€0 €40€A40€a40€e40€h40€ m40€"q0 €$0 €&40€(t0 €)40€+{40€-‚0 €/40€1†40€3ˆ40€540€8—40€:›0 €<0 €>40€?Ÿ40€A¤0€ŕ— 0 €D40€F§40€I­40€Jˇ0 €K40€Mź0 €O40€QÂ0 €S˙˙˙˙ÂL•§eşŠE €ht{¤ŠŞ§Üˆ‹ŒˆŽˆLMNOžŸ Ąe’¸ˆ+ $<$0€?€?@@P§AŽA??€>€>ţ˙ÔAŕ:ˇ_šůÄ€?ÍĚĚ>VIź9h—ŇaD†eCťr‘C:€ď6Aš™B0ôĐ/ô=ôŚI°5l7Lóě÷­ľÜ€Üˆ‹ŒˆŽˆLMNOžŸ Ą’Z[\ $<$0ÍĚĚ> ף<€?€?P§AÍĚĚ???€>€>Ŕ@ÍĚĚ?žfЇyJâNśaĽnÉ}Ša€  ‘ˆ„Ďˆůˆŕˆ˛ˆ´ˆě>ń˙ˆ $?€?€?PAš™? @ €­ ŕˆ˛ˆ´ˆ $$A/€´ˆŕˆţ@#  ƒ˙˙˙˙h€ˆJAŔVerdana„”ˆ@DF ˙… •ˆ Ůc2Ąˆ¨ŔŠŹ€ÉČ`€  ‘ˆ„4ľˆˆ˛ˆŢˆ ˆ>ń $?€?€?PAš™? €­ ˛ˆ ˆ4ˆ $$A/€ ˆŢˆˆˆ ˆľˆ>„Bˆţ@# Thursday, January 13, 2005 ˙˙˙˙d€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ.¨Ŕ ŠŹ€ÉČ\€­ ˛ˆ ˆ4ˆ $$A/€ ˆŢˆˆˆ ˆ‡ˆ>„Bˆţ@#  1:04 PM ˙˙˙˙d€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨Ŕ ŠŹ€ÉČ\€ţ@# JP: Blab about ˙˙˙˙r€ˆ:AŔVerdana„”ˆ@F ˙ Ůc2Ąˆ¨ŔŹŁ€€ÉČP€!­  $$[/€ş  $$6/€€“”˜™   ‘ˆ„ $?€?€?ďîAš™?A33›A €š­  $$­+/€›  $$Ÿ,/€—  $$Ž+/€   $$ž,/€ąB˘ĐOm0€€€€0€€xĐ@8 `ŕ(8 ˜ č°°8 ˜ P Č , €€€€0€€$@€ˆř˜$@€ˆŔ8, €€€€0€€$@€ˆ@@Ř˙€AÂL•§eşŠE€>„Bˆţ@# Eclipse 3.1, JVM 1.5, ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ*¨ŔŠŹŁ€€ÉČ\€—  $$Ž+/€€Üˆ‹ŒˆŽˆLMNOžŸ Ą’Z[\+ $<$0ÍĚĚ> ף<€?€?P§AÍĚĚ???€>€>Ŕ@ÍĚĚ?€?ÍĚĚ>VIź9h—ŇaD†eCťr‘C:€ď6€?ÍĚĚ>ÔvĹÜ>ažfЇyJâNśaĽnÉ}Ša€  ‘ˆ„ůˆŕˆ˛ˆ´ˆě>ń˙ˆŰ $?€?€?PAš™? @ ÝÝOA€Üˆ‹ŒˆŽˆLMNOžŸ Ąe’¸ˆ+ $<$0€?€?@@P§AŽA??€>€>UUß@ŕ:ˇ_šůÄ€?ÍĚĚ>FIź9h—ŇaD†eCťr‘C*€ď6e onaŚI°5l7Lóě÷­ľÜ€ţ"# äI was happy to see you included your planned delivery dates for your  accelerated schedule on iterations 4,5,6. F˙˙˙˙8€ˆ„”ˆ F € Ůc2Ąˆđ§Ŕ揀É4€­  $$[/€ţ@# Project Plan F˙˙˙˙8€ˆ„”ˆ F € Ůc2Ąˆ¨ŔŹ€É4€­  $$[/€€ ­  $$[/€ţ"# pDoes the UCM standard specify the XML format for persistent storage or does it simply specify the interface objects and their properties. Will you be proposing the XML format as an  exchange standard for UCM. Are there generic standards for exchange formats for case tool notations that you should conform to? F˙˙˙˙8€ˆ„”ˆ F € Ůc2Ąˆ|§ŔrŹ€É4€!­  $$[/€ţ@# Impact Assessment F˙˙˙˙8€ˆ„”ˆ F € Ůc2Ąˆ ¨ŔŹ€É4€"­  $$[/€€#­  $$[/€ţ@# ÁThe other big risk is underestimating the difficulty in making a graphical user interface that is easy and convenient to use (in the context of building java systems in Eclipse) and which conforms to Eclipse style guidelines (which may be constantly evolving). I assume your quality assurance manager will be thinking about how to get early feedback and usability testing in order to succeed in this area (since it was listed as a major objective) F˙˙˙˙8€ˆ„”ˆ F € Ůc2ĄˆÎ¨ŔÄŹ€É4€$­  $$[/€ţ"# ŠOne way of managing risk for your project is being precise about the platform you are targeting (versions, OS etc.). If you are worried about adaptable your system is in the face of change in the platform, then deliberately target that you will support 2 or 3 different versions of Eclipse (but note this will complicate your life and I certainly do not require you to take on that level of work for the project & that is up to you and your customer). F˙˙˙˙8€ˆ„”ˆ F € Ůc2Ąˆ–§ŔŒŹ€É4€%­  $$[/€ţ@# Risks F˙˙˙˙8€ˆ„”ˆ F € Ůc2Ąˆ¨Ŕ Ź€É4€&­  $$[/€€'­  $$[/€ţ@# _Tell me precisely what version of Windows (including service pack) you are targeting for your system. What version of Eclipse, JVM, GEF and SWT. Also tell me what version of UCM you are going to support. I am assuming your development environment is Eclipse. It would also be good to indicate that you are intending to persist things in XML files. F˙˙˙˙8€ˆ„”ˆ F € Ůc2Ąˆl¨ŔbŹ€É4€(­  $$[/€ţ@# Architecture F˙˙˙˙8€ˆ„”ˆ F € Ůc2Ąˆ¨ŔŹ€É4€­  $$[/€€)­  $$[/€ţ"# "c) your mockup or storyboard is too vague. Show me what the XML looks like for your example. Show me precisely what you envision the list of options in the pop up menu to be. List what the menus will be. And be clear what all the panels are. Are you going to have 3 different tool boxes on the left? Or just one,or something else in the two empty spots. Same question about property windows on the right? Please understand that I am not expecting you to map out your entire user interface and freeze it now. But do make the details you choose to include in your storyboard precise and concrete. So that they accurately and unambiguously reflect your current thinking. Your thinking (and your change) will evolve a lot over the next few months & but if you want all 5 team members and your customer to be in synch while that evolution takes place then you need to capture your thinking clearly and unambiguously. F˙˙˙˙8€ˆ„”ˆ F € Ůc2Ąˆ.§Ŕ$Ź€É4€*­  $$[/€ţ"# ^b) your use case diagram is too low level and generic & that use case diagram would describe any simple generic graphical editor for creating a diagram that gets persisted in an XML file. Do you really want to think of your system at the level of add an element? Take a look at your storyboard you talk about inserting a responsibility. Your use case diagram should use language that reflects the domain you are in. Also, since this is an Eclipse plug in, isn t one of the use cases you should deal with is the installation and configuration of the plug in? F˙˙˙˙8€ˆ„”ˆ F € Ůc2Ąˆj§Ŕ`Ź€É4€+­  $$[/€ţ"# ¸a) you assume I know what UCM notation is & why not at least give me an example of it in use and some idea of the operations one would do with it, and the context in which one would use it while doing development work. F˙˙˙˙8€ˆ„”ˆ F € Ůc2ĄˆÄ§ŔşŹ€É4€,­  $$[/€ţ@# This section needs work. F˙˙˙˙8€ˆ„”ˆ F € Ůc2Ąˆ(¨ŔŹ€É4€-­  $$[/€ţ@# System Description F˙˙˙˙8€ˆ„”ˆ F € Ůc2Ąˆ"¨ŔŹ€É4€.­  $$[/€/0123456789:;<=>?@   ‘ˆ„> $?€?€?PAš™? €?ÍĚĚ>ąB˘ĐOm**ˆ4č)0 )ŕ)5°)0 8)x6)0 (@'Č7'0 ''8Ř&0 &h&p98&0 %H"đ:"0 $đ(;Ŕ0 #¸<ˆ0 "x=ŕ0 !Ř>Ř0 Đ? 0 (x@ř0 °H$@€ˆ , €€€€0€€$@€ˆh01$@€ˆ@fP,Cf0 `@eĐDe0 _@dĐEd0 ^@cĐFc0 ]@bĐ$@€ˆb02$@€ˆ ]đ+Gđ\0 \ \ĐHđ[0 [ [ĐIđZ0 Z ZĐ$@€ˆđY04$@€ˆ@Y°)JY0 Y@XĐKX0 X@WĐ$@€ˆW07$@€ˆ`V°'L0V0 W`UĐM0U0 V`TĐN0T0 U`SĐ$@€ˆ0S09$@€ˆO %OŕN0 TNĐPŕM0 SMĐ$@€ˆŕL0=˙€ŔhÂL•§eşŠE€Üˆ‹ŒˆŽˆLMNOžŸ Ą’Z[\+ $<$0ÍĚĚ> ף<€?€?P§AÍĚĚ???€>€>Ŕ@ÍĚĚ?€?ÍĚĚ>FIź9h—ŇaD†eCťr‘C*€ď6PVV P/VžfЇyJâNśaĽnÉ}Ša€´ˆŕˆţ@#  Milestone1 Ą˙˙˙˙†€ˆJAŔVerdana„”ˆ@DF ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ`ąB˘ĐOm$@€ˆ?(, €€€€0€€$@€ˆXm(, €€€€0€€7$@€ˆ0'(, €€€€0€€C7$@€ˆH—˜, €€€€0€€EC$@€ˆxš˜$@€ˆP™(€€ €€C0€€HE$@€ˆ¸˝(€€˙˙˙˙ÂL•§eşŠEeôó‰,°,0ŕ:ˇ_šůÄ&System DescriptionMilestone1=.5‰_…O—ÔT/ŘÎÁt€A܈‹ŒˆŽˆLMNOžŸ Ąe’¸ˆ+ $<$0€?€?@@P§AŽA??€>€>UŐ´Aŕ:ˇ_šůÄ€?ÍĚĚ>VIź9h—ŇaD†eCťr‘C:€ď6€?áÝýAčÖ_ôbŚI°5l7Lóě÷­ľÜ€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€A ­ $$™/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€B ­ $$™/"€/01CDEF2GHI34JK567LMN89OP:;<=QR>?@   ‘ˆ„>˝ˆ $?€?€?˙˙Á@XUÝA €?ÍĚĚ>"€ţ"# pDoes the UCM standard specify the XML format for persistent storage or does it simply specify the interface objects and their properties. Will you be proposing the XML format as an  exchange standard for UCM. Are there generic standards for exchange formats for case tool notations that you should conform to? v˙˙˙˙V€ˆ„”ˆ F € Ůc2Ąˆ|§ŔrŹŁ€€ÉČ4 5€!­  $$[/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€S ­ $$—/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€T ­ $$—/€ţ"# ŠOne way of managing risk for your project is being precise about the platform you are targeting (versions, OS etc.). If you are worried about adaptable your system is in the face of change in the platform, then deliberately target that you will support 2 or 3 different versions of Eclipse (but note this will complicate your life and I certainly do not require you to take on that level of work for the project & that is up to you and your customer). v˙˙˙˙V€ˆ„”ˆ F € Ůc2Ąˆ–§ŔŒŹŁ€€ÉČ4 Á€%­  $$[/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€U ­ $$”/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€V ­ $$“/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€W ­ $$“/€ţ@#  ˙˙˙˙r€ˆ:AŔVerdana„”ˆ@F ˙ Ůc2Ąˆ¨ŔŹŁ€€ÉČP€'­  $$[/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€X ­ $$’/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€Y ­ $$’/€ţ@#  ˙˙˙˙r€ˆ:AŔVerdana„”ˆ@F ˙ Ůc2Ąˆ¨ŔŹŁ€€ČÉP€)­  $$[/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€Z ­ $$/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€[ ­ $$/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€\ ­ $$/€ţ"# ^b) your use case diagram is too low level and generic & that use case diagram would describe any simple generic graphical editor for creating a diagram that gets persisted in an XML file. Do you really want to think of your system at the level of add an element? Take a look at your storyboard you talk about inserting a responsibility. Your use case diagram should use language that reflects the domain you are in. Also, since this is an Eclipse plug in, isn t one of the use cases you should deal with is the installation and configuration of the plug in? v˙˙˙˙V€ˆ„”ˆ F € Ůc2Ąˆj§Ŕ`ŹŁ€€ÉČ4 ,€+­  $$[/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€] ­ $$Ž/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€^ ­ $$/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€_ ­ $$/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€` ­ $$/€ţ"# ¸a) you assume I know what UCM notation is & why not at least give me an example of it in use and some idea of the operations one would do with it, and the context in which one would use it while doing development work. v˙˙˙˙V€ˆ„”ˆ F € Ůc2ĄˆÄ§ŔşŹŁ€€ÉČ4 Ů€,­  $$[/ąB˘ĐOm$@€ˆŘI!$@€ˆŕHřQ°H0 BŕGĐR°G0 AŕFĐ$@€ˆ°E0, €€€€0€€$@€ˆ0r0;$@€ˆ€q°#$@€ˆ€pcPp0 b€oĐdPo0 a€nĐ$@€ˆ`r , €€€€0€€fPug(u( e¸tp $@€ˆ€s8€€0€€h~h kŘ}( j¸| l|( iŔ{Đ$@€ˆˆz8€€0€€!$@€ˆ°ˆ(k$@€ˆ ‡j$@€ˆ0‡pho‡( n8†Đp†( m@…Đ$@€ˆ € +$@€ˆ €€0€€#!$@€ˆ˜Š¨,$@€ˆp‰(€€0€€%#$@€ˆ¨,$@€ˆ@(€€0€€'%rx“sP“( qŕ’p $@€ˆ¨‘8€€0€€('$@€ˆ@•H+$@€ˆ”(€€0€€*($@€ˆxŚ02$@€ˆ@˘8+$@€ˆ8ĄyĄ0 x8 Đz 0 wč txp vP( uHœ$@€ˆˆš(€€˙€ř´ÂL•§eşŠEeôó‰,°,0ŕ:ˇ_šůÄ&System DescriptionMilestone1=.5‰_…O—ÔT/ŘÎÁt€Üˆ‹ŒˆŽˆLMNOžŸ Ą’Z[\+ $<$0ÍĚĚ> ף<€?€?P§AÍĚĚ???€>€>Ŕ@ÍĚĚ?€?ÍĚĚ>FIź9h—ŇaD†eCťr‘C*€ď6PVV P/VžfЇyJâNśaĽnÉ}Ša€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€>„Bˆţ@# _UCM version working in UCMNav2 (email daniel for specific version number) and new revisions? Ü˙˙˙˙˛€ˆVAŔVerdana„$”ˆ@F ˙”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔbŠ­"Ž(&Ž(Ž(1Ł€€ÉČl& ,[€“”˜žŁ™   ‘ˆ„ $?€?€?ďîAš™?A33›A ąB˘ĐOm˘€nĐ €ĄX( ŸđŒp $@€ˆ¨‹H€€0€€B@$@€ˆŘ–p{$@€ˆh–pt$@€ˆđ•xh$@€ˆ”@€€0€€DB¤°źp Ś€›( $@€ˆ@źph$@€ˆĐťpt$@€ˆ›p{ĽČş$@€ˆš8€€ €€B0€€GDŠ˜&p ŹĐ( $@€ˆ PŤHŔŞ`p ¨@}( §8}€€0€€IG$@€ˆ0=$@€ˆŔ@!$@€ˆŕž0ľČz0 ´řyĐś¸~0 łxh­H~p ˛ˆÓ( ą`w0$@€ˆ˜vȧŽÓp °'( $@€ˆ@uXŻŔˆ°€€0€€JI$@€ˆxÄ Ż$@€ˆ¨ĂĐ|$@€ˆPÂX€€0€€LJ$@€ˆŘČxh$@€ˆĐ“(k$@€ˆČÇjť8( $@€ˆpĆXş˜ĹŘš`“p ¸řz( ˇ°Ó€€0€€NL$@€ˆ(Ëxh$@€ˆPÉ@€€0€€PNžXŃp Á}( $@€ˆ¨›`Ŕ¨Đ°ż8Đp ˙€ÂL•§eşŠE €ht{¤ŠŞ­ŽŻÜˆ‹ŒˆŽˆLMNOžŸ Ąe’¸ˆ+ $<$0€?€?@@P§AŽA??€>€>SUÚAŕ:ˇ_šůÄ€?ÍĚĚ>VIź9h—ŇaD†eCťr‘C:€ď6Aš™B  ŚI°5l7Lóě÷­ľÜ€ţ@# Yes it does, here it is. No. ˙˙˙˙r€ˆ:AŔVerdana„”ˆ@F ˙ Ůc2Ąˆ,¨Ŕ"ŹŁ€€ÉČP€ţ@# No other ones here. Only XML ó˙˙˙˙؀ˆ:AŔVerdana„”ˆ@F ˙ Ůc2Ąˆ’¨Ŕ"­hŽ(Ž(Ž(Ž(Ž(Ž(Ž(Ž(Ž(Ž(Ł€€ÉČP€>„Bˆţ@# gAre there generic standards for exchange formats for case tool notations that you should conform to? Ń˙˙˙˙ś€ˆd(AŔArialAŔVerdana„"”ˆ F €”ˆ@F ˙… •ˆ Ůc2ĄˆŽ¨ŔjŠ­Ž(dŽ(Ł€€ÉČz€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€´ ­ $$„4/€ˇ  $$6/€ht{—܈‹ŒˆŽˆLMNOžŸ Ąe’¸ˆ+ $<$0€?€?@@P§AŽA??€>€>TUpAŕ:ˇ_šůÄ€?ÍĚĚ>FIź9h—ŇaD†eCťr‘C*€ď6—]€4—]ŚI°5l7Lóě÷­ľÜ€>„Bˆţ@# Eclipse 3.0.1, JVM 1.5, ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ,¨ŔŠŹŁ€€ÉČ\€€§  $$r4/€ź  $$V</€Ŕ  $$S</=.5‰_…O—ÔT/ŘÎÁt€“”˜ž™   ‘ˆ„ $?€?€?ďîAš™?A33›A €˛   ‘ˆ„Ű $4ô?€?€?PAš™?Aš™ B ďîA€ł ­ $$„4/=.5‰_…O—ÔT/ŘÎÁtŠb?0˙˙˙˙ˆ&E@(¸}č~஠ř“ č ¨ČŃ ¸Ó˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙€>„Bˆţ@# #Cependant devrait marcher tous OS ?˙˙˙˙€ˆ‚AŔVerdana„P”ˆ@F ˙”ˆ@F ˙”ˆ@F ˙Hź”ˆ@F ˙Hź… •ˆ Ůc2Ąˆ|¨Ŕ&Š­JŽ( Ž(Ž(Ž(Ž(Ž(Ž(Ł€€ÉČ˜#   €‘  $$+/€ţ@#  ˙˙˙˙r€ˆ:AŔVerdana„”ˆ@F ˙ Ůc2Ąˆ¨ŔŹŁ€€ÉČP€ht{›Üˆ‹ŒˆŽˆLMNOžŸ Ąe’¸ˆ+ $<$0€?€?@@P§AŽA??€>€>TUpAŕ:ˇ_šůÄ€?ÍĚĚ>FIź9h—ŇaD†eCťr‘C*€ď6ĐĐé6ˆA BŚI°5l7Lóě÷­ľÜ€>„Bˆţ@# 3Eclipse 3.0.1, J2SE 5.0, GEF 3.0.1, SWT (? 3.0.1) ˘˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2ĄˆD¨Ŕ6ŠŹŁ€€ÉČ\ 0€ht{Ÿ Üˆ‹ŒˆŽˆLMNOžŸ Ąe’¸ˆ+ $<$0€?€?@@P§AŽA??€>€>Ş*¨Aŕ:ˇ_šůÄ€?ÍĚĚ>VIź9h—ŇaD†eCťr‘C:€ď6(A33ÇAP-VЀ>TUpAŕ:ˇ_šůÄ€?ÍĚĚ>FIź9h—ŇaD†eCťr‘C*€ď6Hňĺ1, ć1ŚI°5l7Lóě÷­ľÜ€>„Bˆţ@# Eclipse 3.0.1, J2SE 5.0 ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ*¨ŔŠŹŁ€€ÉČ\€>„Bˆţ@# EUCM version working in UCMNav2 (email daniel for specific version ×˙˙˙˙˛€ˆVAŔVerdana„$”ˆ@F ˙”ˆ@F ˙… •ˆ Ůc2Ąˆv¨ŔHŠ­"Ž(&Ž(Ž(Ł€€ÉČl& ,€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€œ  $$Ÿ,/€¸   ‘ˆ„Ű $?€?€?PAš™?AÍ̌@ ďî(A€j  $$¨'/=.5‰_…O—ÔT/ŘÎÁt€ht{T܈‹ŒˆŽˆLMNOžŸ Ąe’¸ˆ+ $<$0€?€?@@P§AŽA??€>€>Ş*¨Aŕ:ˇ_šůÄ€?ÍĚĚ>VIź9h—ŇaD†eCťr‘C:€ď6€?ŠˆŘAĐ(VĐVP9VŚI°5l7Lóě÷­ľÜeôó‰,°,0ŕ:ˇ_šůÄ&System DescriptionMilestone1=.5‰_…O—ÔT/ŘÎÁt€kopl   ‘ˆ„Ű $V?€?€?ďî0Aš™?AÍĚĚ> ‰ˆ.A€v   ‘ˆ„Ű $?€?€?PAš™?AÍĚě@ ‰ˆ&A€}†   ‘ˆ„Ű $V?€?€?PAš™?AffA ‰ˆ&A€  ‘ˆ„ůˆŕˆ˛ˆ´ˆě>ń˙ˆŰ $?€?€?PAš™? @ 23‘@ąB˘ĐOm0€€€€ @€ŕ  @€ˆ 0€€A™PX•˜, €€€€0€€FA$@€ˆ ˝˜€€0€€KF$@€ˆHŽ˜€€0€€MK$@€ˆĘ˜€€0€€OM$@€ˆ Ď˜€€0€€QO$@€ˆPŸ˜čŸÂL•§eşŠE€0eąˆžż $rjO?ń;OŸ{eő0>eáŕ:ˇ_šůÄޞ´˙˙Éŕ˙€Üˆ‹ŒˆŽˆLMNOžŸ Ą’Z[\+ $<$0ÍĚĚ> ף<€?€?P§AÍĚĚ???€>€>Ŕ@ÍĚĚ?€?ÍĚĚ>FIź9h—ŇaD†eCťr‘C*€ď6PVV P/VžfЇyJâNśaĽnÉ}Ša€  ‘ˆ„ůˆŕˆ˛ˆ´ˆě>ń˙ˆŰ $?€?€?PAš™? @ ÝÝOA€}†   ‘ˆ„Ű $V?€?€?PAš™?AffA ďî(A€Ľ  $$I4/ €ht{¤ŠŞ­ŽžżźÜˆ‹ŒˆŽˆLMNOžŸ Ąe’¸ˆ+ $<$0€?€?@@P§AŽA??€>€>ľŸŞ<ŕ:ˇ_šůÄ€?ÍĚĚ>VIź9h—ŇaD†eCťr‘C:€ď6HAÍĚź@  P<ô ŚI°5l7Lóě÷­ľÜąB˘ĐOm˝h}( ź`€€0€€RP$@€ˆžH€€˙˙˙˙ÂL•§eşŠE €ht{¤ŠŞ­ŽžŽÜˆ‹ŒˆŽˆLMNOžŸ Ąe’¸ˆ+ $<$0€?€?@@P§AŽA??€>€> Ş<ŕ:ˇ_šůÄ€?ÍĚĚ>FIź9h—ŇaD†eCťr‘C*€ď6ôPôĐô ŚI°5l7Lóě÷­ľÜeôó‰,°,0ŕ:ˇ_šůÄ&System DescriptionMilestone1=.5‰_…O—ÔT/ŘÎÁtąB˘ĐOm€€˙˙˙˙ÂL•§eşŠE€ÉČ\ €x ­ $$P)/&€/01CDEF2yzGHI34JK567LMN89OP:;cd<=QR>?@   ‘ˆ„>˝ˆ $?€?€?˙˙Á@XUÝA €?ÍĚĚ>&€ţ"# Db) your use case diagram is too low level and generic & that use case diagram would describe any simple generic graphical editor for creating a diagram that gets persisted in an XML file. Do you really want to think of your system at the level of add an element? Take a look at your storyboard you talk about inserting a responsibility. Your use case diagram should use language that reflects the domain you are in. Ň˙˙˙˙˛€ˆ2„&”ˆ F €”ˆF €Hź Ůc2Ąˆ˜§ŔF­JŽ(Ž(&Ž(Ž( Ž(Ž(NŽ(Ł€€ÉČH ž€+­  $$[/€ţ@#  We don' ź˙˙˙˙œ€ˆ:AŔVerdana„”ˆ@F ˙ Ůc2Ąˆ@¨Ŕ ­,Ž(Ž(Ž(Ž(Ł€€ÉČP eôó‰,°,0ŕ:ˇ_šůÄ&System DescriptionMilestone1=.5‰_…O—ÔT/ŘÎÁt€ht{|܈‹ŒˆŽˆLMNOžŸ Ąe’¸ˆ+ $<$0€?€?@@P§AŽA??€>€>¨ŞŔ@ŕ:ˇ_šůÄ€?ÍĚĚ>FIź9h—ŇaD†eCťr‘C*€ď6P{č6˜Ř,ŚI°5l7Lóě÷­ľÜ€|  $$ƒ)/€}   ‘ˆ„Ű $V?€?€?PAš™?AffA ďî(A€>„Bˆţ"# hShow me precisely what you envision the list of options in the pop up menu to be. List what the menus will be. And be clear what all the panels are. Are you going to have 3 different tool boxes on the left? Or just one,or something else in the two empty spots. Same question about property windows on the right? Please understand that I am not expecting you to map out your entire user interface and freeze it now. But do make the details you choose to include in your storyboard precise and concrete. So that they accurately and unambiguously reflect your current thinking. Your thinking (and your change) will evolve a lot over the next few months & but if you want all 5 team members and your customer to be in synch while that evolution takes place then you need to capture your thinking clearly and unambiguously. Ń˙˙˙˙ś€ˆd(AŔArialAŔVerdana„"”ˆ F €”ˆ@F ˙… •ˆ Ůc2ĄˆŽ§ŔjŠ­Ž(2Ž(Ł€€ÉČz€~ ­ $$~)/€>„Bˆţ#@ ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\ € ­ $$~)/(€/01CDEF2yzGHI3€4JK567LMN89OP:;cd<=QR>?@   ‘ˆ„>˝ˆ $?€?€?˙˙Á@XUÝA €?ÍĚĚ>(€ţ#@ Ş˙˙˙˙Š€ˆ2„&”ˆ F €”ˆF €Hź Ůc2ĄˆŒ¨Ŕb­"Ž(Ž(*Ž(3Ł€€ÉČH [_c) your mockup or storyboard is too vague. Show me what the XML looks like for your example. €*­  $$[/ąB˘ĐOm0€€,*$@€ˆČ´03$@€ˆ ł(*$@€ˆ˛€`˛0 ąĐ`ą0 ~đŠp{€Šp }XŠ( $@€ˆ(¨0|¨Śč€€0€€.,$@€ˆhĂŘ|$@€ˆXÂ$@€ˆ(Â0$@€ˆ¸şp~$@€ˆš(€€0€€0.$@€ˆxĐ0$@€ˆĎ`~$@€ˆÎ„ĐÍ0 ƒÍĐ…ĐĚ0 ‚ĆČ$@€ˆŘÄ0€€0€€20$@€ˆčŃ@‡HцŃ0 $@€ˆ¨Đp{€€0€€42$@€ˆŕß0…$@€ˆ¸Ţ(‚ŠˆŢ0 ¸ÝĐ‹ˆÝ0 ŽČÚŔ$@€ˆ Ů(ŒpŮ0 ‰ ŘЍpŘ0 ˆđԀ$@€ˆŔÓ0€€˙˙˙˙ÂL•§eşŠEeôó‰,°,0ŕ:ˇ_šůÄ&System DescriptionMilestone1=.5‰_…O—ÔT/ŘÎÁt€ht{¤$܈‹ŒˆŽˆLMNOžŸ Ąe’¸ˆ+ $<$0€?€?@@P§AŽA??€>€>ţŔAŕ:ˇ_šůÄ€?ÍĚĚ>FIź9h—ŇaD†eCťr‘C*€ď6ôPôWĐôŚI°5l7Lóě÷­ľÜ€ţ@# ?We won't be managing multiple versions of eclipse. Only 3.0.1 ­˙˙˙˙’€ˆ:AŔVerdana„”ˆ@F ˙ Ůc2Ąˆl¨ŔB­"Ž(Ž(:Ž(Ł€€ÉČP€v   ‘ˆ„Ű $?€?€?PAš™?AÍĚě@ ďî(A€kopl   ‘ˆ„ $V?€?€?ďî0Aš™?AÍĚĚ> €Ś   ‘ˆ„Ű $ô?€?€?PAš™?A33żA ďî Aeôó‰,°,0ŕ:ˇ_šůÄ&System DescriptionMilestone1=.5‰_…O—ÔT/ŘÎÁt€Üˆ‹ŒˆŽˆLMNOžŸ Ą’Z[\+ $<$0ÍĚĚ> ף<€?€?P§AÍĚĚ???€>€>Ŕ@ÍĚĚ?€?ÍĚĚ>FIź9h—ŇaD†eCťr‘C*€ď6PVV P/VžfЇyJâNśaĽnÉ}Ša1€/01CDEF2yzGHI3–€„…Š‹Œ4JK567LMN89OP:;cd<=ľśQR>?@   ‘ˆ„>˝ˆ $?€?€?˙˙Á@XUÝA €?ÍĚĚ>1€ţ"# ¨Does the UCM standard specify the XML format for persistent storage or does it simply specify the interface objects and their properties. Will you be proposing the XML format as an  exchange standard for UCM. v˙˙˙˙V€ˆ„”ˆ F € Ůc2Ąˆ´§ŔŞŹŁ€€ÉČ4 Đ €ht{¤ŠŞ­Ž‡Üˆ‹ŒˆŽˆLMNOžŸ Ąe’¸ˆ+ $<$0€?€?@@P§AŽA??€>€>LUÉ@ŕ:ˇ_šůÄ€?ÍĚĚ>VIź9h—ŇaD†eCťr‘C:€ď6Aťť#AĐôPôĐô ŚI°5l7Lóě÷­ľÜ€ţ@# #We don't care, but see the DTD .. ˙˙˙˙r€ˆ:AŔVerdana„”ˆ@F ˙ Ůc2Ąˆ0¨Ŕ&ŹŁ€€ÉČP€ţ@# -Please notice accelerated milestones 1,2,3. Ő˙˙˙˙ş€ˆ:AŔVerdana„”ˆ@F ˙ Ůc2Ąˆ‚¨Ŕ0­JŽ(Ž(Ž(Ž(Ž(Ž(Ž(Ł€€ÉČP€>„Bˆţ@# Jason ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨Ŕ ŠŹŁ€€ÉČ\ €ht{¤ŠŞ­ŽšˇÜˆ‹ŒˆŽˆLMNOžŸ Ąe’¸ˆ+ $<$0€?€?@@P§AŽA??€>€>UĄŞ<ŕ:ˇ_šůÄ€?ÍĚĚ>VIź9h—ŇaD†eCťr‘C:€ď6AÍ̌@Ű ŚI°5l7Lóě÷­ľÜ€ţ@# Utiliser exemple pizza. Ű˙˙˙˙Ź€ˆJAŔVerdana„$”ˆ@F ˙”ˆ@F ˙ Ůc2ĄˆP¨Ŕ­,Ž(Ž(Ž(Ž(Ł€€ÉČ`  €kťopl   ‘ˆ„ $V?€?€?ďî0Aš™?AÍĚĚ>  €ht{¤ŠŞ­ŽŽÜˆ‹ŒˆŽˆLMNOžŸ Ąe’¸ˆ+ $<$0€?€?@@P§AŽA??€>€> ŞŔ@ŕ:ˇ_šůÄ€?ÍĚĚ>Büő’I;´G'˛ĺĐGœź&€6 ôĐô ŚI°5l7Lóě÷­ľÜeôó‰,°,0ŕ:ˇ_šůÄ&System DescriptionMilestone1=.5‰_…O—ÔT/ŘÎÁt€kťopl   ‘ˆ„ $V?€?€?ďî0Aš™?AÍĚĚ> "Úť1Žň#‡ĺYOő$ć¨ŃÓy. Ń˙˙˙˙ś€ˆd(AŔArialAŔVerdana„"”ˆ F €”ˆ@F ˙… •ˆ Ůc2Ąˆę§ŔĆŠ­Ž(ŕŽ(Ł€€ÉČz€‚ ­ $$ó)/€>„Bˆţ#@ ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\ €ƒ ­ $$ó)/*€/01CDEF2yzGHI3€„…4JK567LMN89OP:;cd<=QR>?@   ‘ˆ„>˝ˆ $?€?€?˙˙Á@XUÝA €?ÍĚĚ>*€>„Bˆţ#@ Ö˙˙˙˙ś€ˆd(AŔArialAŔVerdana„"”ˆ F €”ˆ@F ˙eôó‰,°,0ŕ:ˇ_šůÄ&System DescriptionMilestone1=.5‰_…O—ÔT/ŘÎÁt€˝   ‘ˆ„Ű $A?€?€?PAš™?HAÍĚź@ ŢÝŃ@€ţ@# jpd ˙˙˙˙r€ˆ:AŔVerdana„”ˆ@F ˙ Ůc2Ąˆ¨ŔŹŁ€€ÉČPA€Á   ‘ˆ„Ű $ô?€?€?PAš™?AÍ̌@ ďî(A=.5‰_…O—ÔT/ŘÎÁt€ht{—܈‹ŒˆŽˆLMNOžŸ Ąe’¸ˆ+ $<$0€?€?@@P§AŽA??€>€>TUpAŕ:ˇ_šůÄ€?ÍĚĚ>FIź9h—ŇaD†eCťr‘C*€ď6° Č ŚI°5l7Lóě÷­ľÜ€°   ‘ˆ„Ű $?€?€?PAš™?Aš™B ďîA€ą  $$Œ4/€Át€ht{ˆÜˆ‹ŒˆŽˆLMNOžŸ Ąe’¸ˆ+ $<$0€?€?@@P§AŽA??€>€>¨Şđ@ŕ:ˇ_šůÄ€?ÍĚĚ>FIź9h—ŇaD†eCťr‘C*€ď6VĐVĐ$VŚI°5l7Lóě÷­ľÜ€>„Bˆţ"# |So that they accurately and unambiguously reflect your current thinking. Your thinking (and your change) will evolve a lot over the next few months & but if you want all 5 team members and your customer to be in synch while that evolution takes place then you need to capture your thinking clearly and unambiguously. Ń˙˙˙˙ś€ˆd(AŔArialAŔVerdana„"”ˆ F €”ˆ@F ˙… •ˆ Ůc2Ąˆ˘§Ŕ~Š­Ž(<Ž(Ł€€ÉČz€ˆ ­ $$x+/€>„Bˆţ#@ ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\ €‰ ­ $$w+/.€/01CDEF2yzGHI3€„…Š‹Œ4JK567LMN89OP:;cd<=QR>?@   ‘ˆ„>˝ˆ $?€?€?˙˙Á@XUÝA €?ÍĚĚ>.€>„Bˆţ#@ ˙˙˙˙؀ˆr(AŔArialAŔVerdana„0”ˆ F €”ˆ F €”ˆ@F ˙… •ˆ Ůc2ĄˆÄ¨ŔŒŠ­,Ž(hŽ(Ž(Ž(Ł€€ÉČˆh n…‰And be clear what all the panels are. Are you going to have 3 different tool boxes on the left? Or just one,or something else in the two empty spots. Same question about property windows on the right? Please understand that I am not expecting you to map out your entire user interface and freeze it now. But do make the details you choose to include in your storyboard precise and concrete. €Ž ­ $$e+/€>„Bˆţ#@ ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\ € ­ $$e+/€>„Bˆţ#@ Ö˙˙˙˙ś€ˆd(AŔArialAŔVerdana„"”ˆ F €”ˆ@F ˙… •ˆ Ůc2ĄˆF¨Ŕ"Š­Ž(Ž(Ł€€ÉČz List what the menus will be. €‚ ­ $$ó)/ąB˘ĐOm0€€€€0€€40áH@xâ0 ¨âx? ă0 Pă>Xă0 "ˆăx<ä0 $0ä(:Xć0 &ˆćp8řć0 ((çČ6đč0  éx5˜é0 ˙€˜ÂL•§eşŠE€ţ"# äI was happy to see you included your planned delivery dates for your  accelerated schedule on iterations 4,5,6. F˙˙˙˙8€ˆ„”ˆ F € Ůc2Ąˆđ§Ŕ揀É4€­  $$[/€ţ@# Project Plan F˙˙˙˙8€ˆ„”ˆ F € Ůc2Ąˆ¨ŔŹ€É4€­  $$[/€€ ­  $$[/€ţ@# Impact Assessment F˙˙˙˙8€ˆ„”ˆ F € Ůc2Ąˆ ¨ŔŹ€É4€"­  $$[/€ţ@# ÁThe other big risk is underestimating the difficulty in making a graphical user interface that is easy and convenient to use (in the context of building java systems in Eclipse) and which conforms to Eclipse style guidelines (which may be constantly evolving). I assume your quality assurance manager will be thinking about how to get early feedback and usability testing in order to succeed in this area (since it was listed as a major objective) F˙˙˙˙8€ˆ„”ˆ F € Ůc2ĄˆÎ¨ŔÄŹ€É4€$­  $$[/€ţ@# Risks F˙˙˙˙8€ˆ„”ˆ F € Ůc2Ąˆ¨Ŕ Ź€É4€&­  $$[/€ţ@# _Tell me precisely what version of Windows (including service pack) you are targeting for your system. What version of Eclipse, JVM, GEF and SWT. Also tell me what version of UCM you are going to support. I am assuming your development environment is Eclipse. It would also be good to indicate that you are intending to persist things in XML files. F˙˙˙˙8€ˆ„”ˆ F € Ůc2Ąˆl¨ŔbŹ€É4€(­  $$[/€ţ@# Architecture F˙˙˙˙8€ˆ„”ˆ F € Ůc2Ąˆ¨ŔŹ€É4€­  $$[/€ţ@# This section needs work. F˙˙˙˙8€ˆ„”ˆ F € Ůc2Ąˆ(¨ŔŹ€É4€-­  $$[/€ţ@# System Description F˙˙˙˙8€ˆ„”ˆ F € Ůc2Ąˆ"¨ŔŹ€É4€.­  $$[/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€A ­ $$™/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€B ­ $$™/€ţ"# pDoes the UCM standard specify the XML format for persistent storage or does it simply specify the interface objects and their properties. Will you be proposing the XML format as an  exchange standard for UCM. Are there generic standards for exchange formats for case tool notations that you should conform to? v˙˙˙˙V€ˆ„”ˆ F € Ůc2Ąˆ|§ŔrŹŁ€€ÉČ4 5€!­  $$[/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€S ­ $$—/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€T ­ $$—/€ţ"# ŠOne way of managing risk for your project is being precise about the platform you are targeting (versions, OS etc.). If you are worried about adaptable your system is in the face of change in the platform, then deliberately target that you will support 2 or 3 different versions of Eclipse (but note this will complicate your life and I certainly do not require you to take on that level of work for the project & that is up to you and your customer). v˙˙˙˙V€ˆ„”ˆ F € Ůc2Ąˆ–§ŔŒŹŁ€€ÉČ4 Á€%­  $$[/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€U ­ $$”/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€V ­ $$“/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€W ­ $$“/€ţ@#  ˙˙˙˙r€ˆ:AŔVerdana„”ˆ@F ˙ Ůc2Ąˆ¨ŔŹŁ€€ÉČP€'­  $$[/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€X ­ $$’/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€Y ­ $$’/€ţ@#  ˙˙˙˙r€ˆ:AŔVerdana„”ˆ@F ˙ Ůc2Ąˆ¨ŔŹŁ€€ČÉP€)­  $$[/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€Z ­ $$/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€[ ­ $$/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€\ ­ $$/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€] ­ $$Ž/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€^ ­ $$/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€_ ­ $$/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€` ­ $$/€,­  $$[/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€a ­ $$§/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€b ­ $$§/€ţ@#  ˙˙˙˙r€ˆ:AŔVerdana„”ˆ@F ˙ Ůc2Ąˆ¨ŔŹŁ€€ÉČP€#­  $$[/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€i  $$ł'/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€m  $$a(/€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€n  $$`(/€kopl   ‘ˆ„ $V?€?€?ďî0Aš™?AÍĚĚ> €ţ@# Utiliser exemple pizza. Ű˙˙˙˙Ź€ˆJAŔVerdana„$”ˆ@F ˙”ˆ@F ˙ Ůc2ĄˆP¨Ŕ­,Ž(Ž(Ž(Ž(Ł€€ÉČ`  €j  $$¨'/€ţ"# ¸a) you assume I know what UCM notation is & why not at least give me an example of it in use and some idea of the operations one would do with it, and the context in which one would use it while doing development work. Í˙˙˙˙˛€ˆ2„&”ˆ F €”ˆF €Hź Ůc2Ąˆ §Ŕş­JŽ(HŽ(Ž("Ž( Ž(Ž(CŽ(Ł€€ÉČH€ţ@# Non, c'est un unzip. Ń˙˙˙˙Ź€ˆJAŔVerdana„$”ˆ@F ˙”ˆ@F ˙ Ůc2ĄˆN¨Ŕ­,Ž(Ž(Ž( Ž(Ł€€ÉČ` €u  $$Q)/€v   ‘ˆ„Ű $?€?€?PAš™?AÍĚě@ ďî(A€>„Bˆţ"# Also, since this is an Eclipse plug in, isn t one of the use cases you should deal with is the installation and configuration of the plug in? Ń˙˙˙˙ś€ˆd(AŔArialAŔVerdana„"”ˆ F €”ˆ@F ˙… •ˆ Ůc2ĄˆD§Ŕ Š­Ž(Ž(Ł€€ÉČz€w ­ $$P)/€>„Bˆţ#@ ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\ €x ­ $$P)/€ţ"# Db) your use case diagram is too low level and generic & that use case diagram would describe any simple generic graphical editor for creating a diagram that gets persisted in an XML file. Do you really want to think of your system at the level of add an element? Take a look at your storyboard you talk about inserting a responsibility. Your use case diagram should use language that reflects the domain you are in. Ň˙˙˙˙˛€ˆ2„&”ˆ F €”ˆF €Hź Ůc2Ąˆ˜§ŔF­JŽ(Ž(&Ž(Ž( Ž(Ž(NŽ(Ł€€ÉČH ž€+­  $$[/€|  $$ƒ)/€>„Bˆţ#@ ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\ € ­ $$~)/€ţ#@ Ş˙˙˙˙Š€ˆ2„&”ˆ F €”ˆF €Hź Ůc2ĄˆŒ¨Ŕb­"Ž(Ž(*Ž(3Ł€€ÉČH [_c) your mockup or storyboard is too vague. Show me what the XML looks like for your example. €*­  $$[/€ţ@# %We don't care, but here's the dtd. —˙˙˙˙r€ˆ:AŔVerdana„”ˆ@F ˙ Ůc2Ąˆ2¨Ŕ(ŹŁ€€ÉČPA!€>„Bˆţ#@ ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\ €ƒ ­ $$ó)/€>„Bˆţ#@ Ö˙˙˙˙ś€ˆd(AŔArialAŔVerdana„"”ˆ F €”ˆ@F ˙… •ˆ Ůc2Ąˆ|¨ŔXŠ­Ž(RŽ(Ł€€ÉČz PUShow me precisely what you envision the list of options in the pop up menu to be. €~ ­ $$~)/€}†   ‘ˆ„Ű $V?€?€?PAš™?AffA ďî(A€‡­  $$+/€ąB˘ĐOm-Čé€0Hę0 .xęx/đę0 A ëĐRđë0 B ěĐQđě0 ! í=(đ0 SXđĐP(ń0 TXńĐO(ň0 %Xň 9xö0 U¨öĐNx÷0 V¨÷ĐMxř0 W¨řĐLxů0 '¨ů°7Xú0 XˆúĐKXű0 YˆűĐJXü0 )ˆü°48ý0 ZhýĐI8ţ0 [hţĐH8˙0 \h˙ĐG80 ]hĐF80 ^hĐE80 _hĐD80 `hĐC80 1h0 a˜Đdh0 b˜Đch0 #˜°;H0 ixĐlH( mpĐp@ ( nh Đo8 ( h` p jĐ kŕ ( , ¨u°v¸( tŕp wP zp0 x Đyp0 + 82Ř0 }( 0Đ€0 *0(3X0 |ˆŘƒ`Đ„00 ~``Ŕ0 {đp †`0 ‡…ŕß0 ‚¸Ţ(ŠˆŢ0 ¸ÝĐ‹ˆÝ0 ŽČÚŔ Ů( ŒpŮ0 ‰ ŘЍpŘ0 ˆđԀŔÓ0 , €€€€0€€64$@€ˆ2ŘŽ$@€ˆ`10‚$@€ˆř/h~$@€ˆĐ.($@€ˆ .03$@€ˆ -*–p-0 •0,@Č+h “ +( ’*”h*( ‘˜)Đ$@€ˆX(@€€0€€96™Ř0 š¸$@€ˆhp$@€ˆ˜ˆ(”$@€ˆ‡˜‘˜( —¨č$@€ˆčŃ0€€0€€;9$@€ˆP|č—$@€ˆ {0€€0€€=;$@€ˆ0č—$@€ˆ0€€0€€>=$@€ˆ0(˜$@€ˆ Š—$@€ˆĐ}x8“( œh’Đž( $@€ˆp‰0›‘P€€0€€@>$@€ˆŔp€$@€ˆ Ž(ž$@€ˆPop›Łř( ˙€@qÂL•§eşŠE€Ź   ‘ˆ„Ű $?€?€?PAš™?A33ßA ďî(A€Ż  $$˜4/€Üˆ‹ŒˆŽˆLMNOžŸ Ą’Z[\+ $<$0ÍĚĚ> ף<€?€?P§AÍĚĚ???€>€>Ŕ@ÍĚĚ?€?ÍĚĚ>FIź9h—ŇaD†eCťr‘C*€ď6PVV P/VžfЇyJâNśaĽnÉ}Ša€ht{‘܈‹ŒˆŽˆLMNOžŸ Ąe’¸ˆ+ $<$0€?€?@@P§AŽA??€>€>TUpAŕ:ˇ_šůÄ€?ÍĚĚ>VIź9h—ŇaD†eCťr‘C:€ď6AŢݝA dŚI°5l7Lóě÷­ľÜ€>„Bˆţ@#  ˙˙˙˙‚€ˆFAŔVerdana„”ˆ@F ˙… •ˆ Ůc2Ąˆ¨ŔŠŹŁ€€ÉČ\€‘  $$+/€ţ@# Windows xp sp2 ŕ˙˙˙˙ś€ˆJAŔVerdana„$”ˆ@F ˙”ˆ@F ˙ Ůc2ĄˆR¨Ŕ­6Ž(Ž(Ž(Ž(Ž(Ł€€ÉČ`  €’  $$š+/€“”   ‘ˆ„ $?€?€?ďîAš™?A33›A €>„Bˆţ@# 5Show me what the XML looks like for your example. ×˙˙˙˙ź€ˆj(AŔArialAŔVerdana„(”ˆF €Hź”ˆ@F ˙… •ˆ Ůc2Ąˆ\¨Ŕ8Š­Ž(2Ž(Ł€€ÉČ€€• ­ $$•+/€ţ#@ ´˙˙˙˙”€ˆ2„&”ˆ F €”ˆF €Hź Ůc2Ąˆd¨Ŕ0­,Ž(Ž(Ž((Ž(Ł€€ÉČH )-c) your mockup or storyboard is too vague. €*­  $$[//€/01CDEF2yzGHI3–€„…Š‹Œ4JK567LMN89OP:;cd<=QR>?@   ‘ˆ„>˝ˆ $?€?€?˙˙Á@XUÝA €?ÍĚĚ>/€>„Bˆţ#@ Ý˙˙˙˙€ˆp(AŔArialAŔVerdana„.”ˆF €Hź”ˆ@F ˙Hź… •ˆ Ůc2Ąˆ|¨ŔXŠ­Ž(RŽ(Ł€€ÉȆUShow me precisely what you envision the list of options in the pop up menu to be. €>„Bˆţ#@ Ý˙˙˙˙€ˆp(AŔArialAŔVerdana„.”ˆF €Hź”ˆ@F ˙Hź… •ˆ Ůc2ĄˆF¨Ŕ"Š­Ž(Ž(Ł€€ÉȆList what the menus will be. €>„Bˆţ#@ ˙˙˙˙ö€ˆ†(AŔArialAŔVerdana„D”ˆF €Hź”ˆ F €”ˆ F €”ˆ@F ˙… •ˆ Ůc2ĄˆÎ¨ŔŒŠ­6Ž(&Ž(BŽ(Ž(Ž(Ł€€ÉČœh n‰And be clear what all the panels are. Are you going to have 3 different tool boxes on the left? Or just one,or something else in the two empty spots. Same question about property windows on the right? Please understand that I am not expecting you to map out your entire user interface and freeze it now. But do make the details you choose to include in your storyboard precise and concrete.