STARS Requirements Review - Questions, Answers, and Open Issues

Authoring - John Rosenberg

• Issue: AIMSS 4.0 and ACS are not compatible.

  Status: Looking for OCR software to replace ACS.

Workflow - Kaushik Merchant

• Issue: Where do we get a list of users to be notified?
  
• Issue: Control of the Document interface: should other teams be able to commit changes to it?
  

• Question(Eric Stein): Is "Consists of" the right association between Documents and AssociatedDocuments? This doesn't seem to give a Document any identity other than the collection of AssociatedDocuments that make it up. Consider a change in terminology.

  Kaushik: We think it's right; aggregation allows the aggregate to be more than the sum of its parts.

• Question(Client): How can one IETM refer to others?

  Kaushik: That's out of Workflow's scope. Within an IETM, it can be anything necessary.

Modeling - Matthew Weyent

• Issue: Can complexity be reduced if it doesn't run on a wearable computer?

Inspection - Zeb Drivdahl

• Issue: Workorders:

  • How are they created?
  • How are they related to stickies?
  • What is their lifetime?

  Status: These should be dealt with by the new Workorder team.

• Issue: How are stickies placed?

  Status: Handled by AR and Modeling teams; the main interaction for the Inspection team is through AR.

• Question: What are IETM-based workorders?

  Answer: Workorders should have references to parts of IETMs so they can be pulled up during inspection.

• Question: What is the "standard Inspection Process?"?

  Answer: The workorder will explain what to do.
  Stickies will be placed to create new workorders.

• Question: How are IETMs going to be used in the Inspection process?

  Answer: Se the answer to "What are IETM-based workorders?"

• (Issue)Question: How will IETMs be navigated?

  Answer: Open Issue.

• Issue: Still don't know the details on PEDD/HMD hardware.

Repair - Pat Larkin

• Issue: The Notification interface is not well-defined.

  The system currently in use by the Navy is manual notification. In the worst case, they can continue this system.

• Issue: Current free-form speech recognition systems do poorly on open-ended vocabularies.
• Issue: IETMs are large.
• Issue: Authentication standards haven't been established.

• Question: What are the CPU&storage limits on a PEDD?

  Answer: Pentium 166 with 32Megs are required for speech recognition.

• Question: Your presentation referenced a "Submit" interface to the Workflow subsystem. Note that this is distinct from "Update"; you probably mean the latter.

  Answer: Ok.

• Question: Is the network needed during the action of repairing the plane?

  Answer: Not for any core functionality, but it would allow us to update workorders and such during the work, which may be interesting.

• Question: Given an IETM, how do you generate speech?

  Answer: A text-to-speech system.

• Question: Can this speech synthesis system parse SGML?

  Answer: No, that'll have to be done outside of the speech system.

• (Issue) Question: How can the repairer use a PEDD to lookup part of an IETM using only voice input, if there are many levels to an IETM?

  Answer: We currently assume that the worker has enough knowledge of the IETM to request the section by exact name. We could provide a way to search for a section.

• Question: Who's doing the IETM interface? (Authoring or Repair)?

  Answer: Repair will call Authoring's interface for this.

• Question: Where'd you get the milk graphic?

  Answer: Somewhere on Microsoft's page.

• Question: If you're displaying the workorder and/or IETM on the screen, why do speech as well?

  Answer: It can be hard to look at the display - even a head-mounted display - while working.

Project Management (Architecture) - Daniel Heller

Note that this is SPMP information, not RAD information.

• (Issue) Question: The subsystem decomposition doesn't look right. For example, I think the Inspection and Repair subsystems want to talk directly to eachother.

  Answer: Could be. We'll look into it at the Architecture meeting.

Augmented Reality - Jeremy Jones

No Issues or questions.

Q&A - October 26

• (Issue) Question(Bill): The unique id's for document id's: are they owned by Workflow or Authoring?

  (No Answer)

• Question(Bill): Is there some sort of handle to get the document from Workflow?

  Answer(Kaushik): Yes.

• Question: Authentication - is it inter-subsystem?

  Answer(Kaushik): No.

• Question: Where is the model stored?

  Answers:

  • Matt: Some database somewhere.
  • Kaushik: It could easily be put into workflow.

• Question: IETMs can be viewed with what program?
  

  Answer: IETMs are SGML documents; they can be viewed with any SGML viewer.

• (Issue) Question: How big will the IETM-viewr be?

  Answer: Framemaker-ish. Authoring will come up with a more specific answer.

• Question: Workflow, re: robustnes: What happens when asynchronous notification is requested byt "the subsystem" is down?

  Answer: Kaushik: It should eventually time out and notify someone else.

• Question: How about concurrent updates?

  Answer: Kaushik: Not allowed.

• (Issue) Question: Will the system notice when a subsystem is down and notify someone?

  Answer: No answer at this time.

• (Issue) Question: Synchronous notification: pager v. wearable computer. If wearable, the system needs to know who's loggged in to each computer, which is something that hasn't been addressed. I.e., all other authentication issues have been resolved by required authentication to happen for each transaction, but this requires something to keep track.
  

  Answer: No answer at this time.
  

Q&A - October 28

• Question (for Augmented Reality): What's the Timer object for?

  Answer: Just for updating the display.

  (Issue) Question (for Augmented Reality): You know Java's got a Timer?

  Answer: We haven't looked into that yet.

• Question (for Augmented Reality): How are you anticipating that the memory on the PEDD will be divided between the systems?

  Answer: The PEDD has 128 megabytes of RAM. We anticipate Modeling using 64, subsystem [ed: didn't catch it] using 32, and splitting the rest up among the other subsystems.

• Question (for Augmented Reality): Who is doing IETM viewing?

  Answer: Inspection or Repair.

• Question: How much network bandwidth is needed?

  Answer: As fast as possible. There probably won't be more than 10bT available.

• Question: Will there be a read-ahead cache (i.e., downloading the next page of an IETM while viewing the current one.)

  Answer: We plan to have all needed parts of the IETM cached on disk before the repair is begun.

  Another Semantic point: The client was somewhat insistant that "IETMs don't have "pages".".

  Answer: Ok, we'll use the concepts of "screens" or "sections" instead.

• Question: What's the actual structure of an IETM?

  Answer: It's fairly involved. Someone from Authoring will post a link that the clients gave us.

• Update from Authoring: because of conversations with the client, we've decided to store IETMs in the database in sections, not as single entities.