1 / 33

Requirements Analysis Review

Requirements Analysis Review. Modeling Team Matt Weyant 26 Oct 1999. Goals. Create model of airplane and its components Develop API for virtually navigating the airplane model Provide API for graphically manipulating “Stickies” Build a web-based navigation tool. What is this model?.

daughertyr
Download Presentation

Requirements Analysis Review

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Requirements Analysis Review Modeling Team Matt Weyant 26 Oct 1999

  2. Goals • Create model of airplane and its components • Develop API for virtually navigating the airplane model • Provide API for graphically manipulating “Stickies” • Build a web-based navigation tool

  3. What is this model? • CAD-generated 3D model • Data structure is a component tree

  4. View of Model (rendered)

  5. Functional Requirements • Provide navigation methods for navigation through a 3D model of an airplane and its components • Provide location information in a 3D coordinate system for the airplane and its components • Map locations (x,y,z) to specific parts of the airplane and back

  6. Functional Requirements, cont… • Locate Stickies associated with components or the whole airplane • Provide a GUI and manipulation methods for Stickies in a Sticky database owned by Workflow

  7. Nonfunctional Requirements • User interface and human factors • Documentation • Hardware considerations • Performance characteristics • Error handling and extreme conditions • System interface • Quality issues

  8. Nonfunctional Requirements, cont... • System modifications • Physical environment • Security issues • Resources issues

  9. User Interface and Human Factors • Web-based user interface • Built on API’s • Intuitive • Restricted access • Access rights • Web users will have “read” access to database • View/navigate through existing data

  10. Documentation • Describe features and operation of Web-based navigation tool • Help pages • Demos • Javadoc of implementation • Extensive additional docs available to other subsystems

  11. Hardware Considerations • Large storage space • Lots of memory • Graphics acceleration not available • Web availability on remote machine

  12. Performance Characteristics • Real time requests • AR • Authoring • Non-real time requests • Workflow • Java3D

  13. Error Handling and Extreme Conditions • Error Handling • Method calls between subsystems • Dialogue with Web user • Examples • Extreme Conditions • Multiple uses on same CPU • Memory shortage

  14. System Interface • Augmented Reality • Maintenance/Workflow • Authoring

  15. Augmented RealitySystem Interface • AR’s event-based model • AR publishes a Vector event with a reference to an empty frame • Modeling fills the frame and returns it • API holds methods for rotating, translating and scaling that view • Web-UI will use AR’s event- and UI-model

  16. Maintenance/WorkflowSystem Interface • Modeling provides API for Sticky manipulation • Place • Remove • Review • Modify • Must interface with Sticky database owned by Workflow

  17. AuthoringSystem Interface • Same methods provided to Authoring as AR • Generate IETMs using these methods

  18. Quality Issues • System overload • Another system unavailable • Accurate output for given input • Platform-independent

  19. System Modifications • Extending system for some other weapons system • Abstract Factory pattern means minimal changes

  20. Physical Environment • Never comes in contact with physical surroundings

  21. Security Issues • Shared memory • Each subsystem must limit access • Data encryption to prevent “eavesdropping”

  22. Resources Issues • No permanent Workflow data • Navigation information must be stored

  23. Constraints • Platform-independence • Speed of Java • Together/J

  24. System Model • Scenarios • Use case models • Object models • Dynamic models • Navigational paths and screen mockup

  25. ScenariosSystem Model • Inspection • Repair • Browser

  26. Use Case ModelsSystem Model

  27. NavigateComponent Use CaseUse Case Models • NavigateComponent • Actors: Authoring, AR, RemoteUser • Entry: Actor wants to view/manipulate model • Flow of Events • 1. Request entry of system if not already in • 2. Call method to use for model manipulation • 3. Exit system if done • Exit: Actor is done manipulating model • Special Requirements: Is system on local machine? Speed?

  28. Object ModelsSystem Model

  29. Dynamic ModelsSystem Model

  30. Navigational TextSystem Model • NavigateComponent Sequence Diagram • Actor initializes display of the model; a wireframe is returned. • Actor could draw components of the model; a new wireframe is returned. • Actor could rotate and zoom model/components; a new wireframe is returned.

  31. Screen MockupSystem Model

  32. Questions?

More Related