1 / 17

Storyboards: A Medium for Stealth Knowledge Capture

Overview: Stealth Knowledge Capture. Common difficulty ? capturing design knowledgeOur approach ? integrate with designExample project ? storyboard toolPrincipals to apply to other projectsResponses. Difficulty ? Design Knowledge Capture. Not always clear when to capture the knowledgeSeveral t

aine
Download Presentation

Storyboards: A Medium for Stealth Knowledge Capture

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. Storyboards: A Medium for Stealth Knowledge Capture Carroll Thronesbery Debra Schreckenghost Arthur Molin 02 March 2006

    2. Overview: Stealth Knowledge Capture Common difficulty – capturing design knowledge Our approach – integrate with design Example project – storyboard tool Principals to apply to other projects Responses

    3. Difficulty – Design Knowledge Capture Not always clear when to capture the knowledge Several times during a meeting After each meeting, milestone in project, project completion Where is the reminder to capture design knowledge? How many design alternatives to capture? Important to know what was not selected for design and why Capturing too many alternatives can waste effort, time, project resource Too many alternatives can also reduce the usefulness of the repository Too few runs risk of repeating past design mistakes or wrong paths Resources are rarely dedicated to design knowledge capture (DKC) RFPs and contract requirements do not include DKC Can reduce cost effective competitiveness of current project Unclear how design knowledge will be used To support changes to current design To support design of future systems How similar will future systems be to the current design? While these issues need to be addressed, they should not be addressed during current system design – lose designer’s focus

    4. Our Approach: Stealth Capture Designers concentrate on design, DKC is a by-product Provide a tool that supports an aspect of system design Capture the design and design alternatives while supporting design Export the design knowledge data to mainstream design knowledge management software tools (DesKART)

    5. Our Project: Storyboard Tool SBIR project – just beginning Phase I Assist storyboard generation and refinement Assist in communicating storyboard design data to subsequent engineering tools System specification, requirements, design UML diagrams (XMI data format), Cradle, CORE Unified Modeling Language (UML) Extensible Markup Language (XML) XML Metadata Interchange (XMI) Capture design knowledge as a by-product

    6. Context of Storyboarding: System Acquisition Phase System acquisition timeline from Constellation Hazard Analysis Document (JSC 0000028585) – System Engineering Viewpoint During Mission Definition and System Definition Part of the Concept of Operation (ConOps) definition effort Purpose of ConOps is to convey the user’s concept of how the new system can support user mission performance

More Related