Questions to the Customer

From DaVinci

Please post questions on the discussion tab and broadcast to the team. If the team cannot answer the question, the customer contact will forward the questions to our customer. Regardless of how we get the answer, once we have the answer to the question both the question and its answer will be moved to the article (rather then the discussion) page. Please follow the existing example for formatting and include the signature/timestamp when adding a new question set. The signature/timestamp wiki syntax is: --~~~~

Question Set 1

  1. Who defines acceptance criteria for DaVinci deliverables?
    • The customer has not defined any acceptance criteria. Team DaVinci is responsible for defining tests and the customer may come up with additional test cases based on those team DaVinci creates.
  2. What version of JAVA should team DaVinci use for implementation
    • JAVA 1.4.
  3. What documentation does team DaVinci need to deliver?
    • UML diagrams (class and sequence) that are not too detailed.
    • Notional architecture to show tactics for achieving specified quality attributes.
    • Java Doc (functional, class, and package levels).
  4. Is there any reason why team DaVinci should not use Clover or mention on the team website that Clover is being used?
    • Do not use Clover if it requires a change to the OSATE license. Otherwise, it is OK to use and list on the web.
  5. Should team DaVinci add their JUnit tests to the OSATE CVS repository?
    • Yes. 
--Chris 20:35, 28 February 2006 (Eastern Standard Time)

Question Set 2

  1. There is a recent release OSATE 1.2 available on www.aadl.info, which depends on the latest EMF etc. Should team DaVinci use this latest release as a base for the development? Earlier direction was to use OSATE 1.1. Side note; latest ATL also depends on EMF 2.1.1, which could fuel the argument of using the latest OSATE.
    • Preferably DaVinci must use the most recent version in CVS. Otherwise use OSATE 1.2 because it fixed a lot of bugs found in 1.1. 
--Harry 18:49, 23 March 2006 (Eastern Standard Time)
--Luis 13:19, 1 April 2006 (Eastern Standard Time)

Question Set 3

  1. Based on experience from prototyping port group creation, the plug-in feature seems to automatically operate on every single AADL model in the Navigator view when a single AADL model is selected for plug-in feature operation. Is this true?
    • If so, is there any restriction on how the use case verification model be arranged for acceptance?
    • Can it be loaded one by one or needs to be imported into the Navigator view at the same time (this implies independent UC model setup)?
  2. The port group nameing convention based on Customer Meeting Notes 030306 Answer for Q#9 only covers the scenario where a component is the source for one port group with multiple destination. If a component is the source for multiple port group it is not clear how to distinquish different source port group. Potential Suggestions: (1) SrcComponentIdTargetComponentId_PG (2) SrcComponetId#_PG. 
--Carl 10:49, 1 April 2006 (Eastern Standard Time)
Retrieved from "http://seiproject.homeip.net:8088/wiki/index.php/Questions_to_the_Customer"