1 / 65

TTWCS v6 Presentation Layer Candidates

TTWCS v6 Presentation Layer Candidates. POC(s): Lead: Dave Manley Group Leads: Alan Thomas, Dave Dawson, Art Borst, Dan Bevis, & Robin Ross. Recommended v6 UPE Candidates. UPE09: Common Presentation Layer Infrastructure  UPE11: Integration of TTWCS/CCS Windows

ham
Download Presentation

TTWCS v6 Presentation Layer Candidates

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. TTWCS v6 Presentation Layer Candidates POC(s): Lead: Dave Manley Group Leads: Alan Thomas, Dave Dawson, Art Borst, Dan Bevis, & Robin Ross

  2. Recommended v6 UPE Candidates • UPE09: Common Presentation Layer Infrastructure  • UPE11: Integration of TTWCS/CCS Windows • UPE12: Enhance HCI for Maintaining Situational Awareness • UPE13: Enhance HCI for Tasking Management • UPE14: Enhance HCI for Engagement Planning • UPE15: Enhance HCI for Engagement Review and Approval • UPE16: Enhance HCI for Missile Selection and Preparation • UPE17: Enhance HCI for Mission Execution • UPE18: Enhance HCI for Onboard Mission Planning • UPE19: Enhance HCI for Post Launch Management • UPE20: Unified Display of Alerts, Notifications, Prompts and Pop Ups

  3. UPE09   UPE: Common Presentation Layer Infrastructure 

  4. UPE09: Common Presentation Layer Infrastructure Overview • Summary Description • Candidate doesn’t implement changes to the system; it creates a framework for future changes • Operator Perspective: None • This candidate has no direct impact on: • User windows or window behavior • Functionality of the system from the operator point of view • Re-Architect TTWCS to implement three principle layers of a system • Presentation Layer, Domain Layer, Data Source • Presentation Layer will implement and control all user interfaces • Keyboards, Displays, Trackballs, etc. • Eventually remove all windows from the business logic, domain, CSCIs • Start with windows undergoing user centered design for v6 • All windows by v7 • Data Source layer will avail a common communication and possible database for the TTWCS system • Step towards adherence to Open Architecture guidelines • Easier interaction to other systems • Domain layer already exist with current application level CSCIs

  5. UPE09: Common Presentation Layer Infrastructure Overview • CR Summary • Adaptive: 1 • Perfective: 0 • Corrective: 0 • TOTAL: 1

  6. UPE09: Common Presentation Layer Infrastructure Analysis • Technical Description • Re-Architecture of TTWCS • CSCI Impact • May need to create multiple presentation layer CSCIs • Will impact several existing TTWCS CSCIs • Presentation Layer • Presentation layer architecture will model the Model / View / Controller (M.V.C), architecture at the system level • Common tool set that will be used for all future TTWCS user interfaces • Data Source Layer • Identify “Middleware” for a common communications interface for the TTWCS system • Initially for communication with the presentation layer (between data layer and the Domain layer) • Evaluate use of database on the TTWCS system and possible implementation technologies • Conduct prototyping for best alternative for each layer • Data based or code based windows • Presentation layer toolsets • Communication layer middleware • Purpose database alternatives

  7. UPE09: Common Presentation Layer Infrastructure Analysis • Fleet Benefit: • Facilitates implementation of HCI Improvements • Easier to implement Task Centered Design • Easier to implement a common and consistent HCI style & behavior • Easier to implement new functionality, e.g. decision aids or displays • Share system components with other systems • Facilitates a common HCI across Land Attack systems • Merging with other system windows or sharing data with users on other systems • Modeling user interface changes to other systems • Common GUI will help reduce PRs • Easier to implement a change that affects multiple windows • Fleet Importance: N/A • Recommend this candidate not be briefed at Fleet Review • UPE09 Represents an internal improvement to TTWCS • Benefits not readily apparent to Fleet • Internal importance is high • This candidate facilitates implementation of all other UPE candidates

  8. UPE09: Common Presentation Layer Infrastructure Analysis • Effort: Medium to High (High is greater than1K SLOC) • Size: High • Complexity: Medium • External Dependencies: None • Risk: Medium to High • Technical Risk: Medium • Schedule Risk: Medium-to-High • Large change to current software architecture • Much of performance prototyping and trade-off analyses work is occurring during 2004 calendar year • Resource availability may be an issue • Addresses 1 CR Eliminates 0 TIP entries

  9. UPE09: Common Presentation Layer Infrastructure Recommendation • Recommendation Implement in v6 Defer for Future Consideration • Incorporation of this candidate facilitates all future HCI related (UPE) candidates • Incorporation of this candidate facilitates integration of TTWCS into future land attack systems • Issues • CR twcs00011359: This CR is listed as an adaptive CR, and believe it should be perfective • Justification: This CR does not change the system requirements for TTWCS (i.e, no SSS Changes) • It changes how TTWCS implements those system requirements

  10. UPE11: Integration of TTWCS/CCS Windows

  11. UPE11: Integration of TTWCS/CCS Windows Overview • Summary Description • This candidate involves developing the ability to incorporate CCS functionality on TTWCS • Operator’s Perspective: • On US SSN, the Task Manager involvement ends at 'plan save', then resumes at post launch • Provide interface for Task Manager to invoke CCS windows so that CCS capabilities would become an extension of the Task Manager • Improves overall HCI by enabling use of Task Manager to manage tasks all the way through launch and Post Launch Execution • CR Summary • Adaptive: 2 • Perfective: 0 • Corrective: 0 • TOTAL: 2

  12. UPE11: Integration of TTWCS/CCS Windows Analysis • Technical Description • Expand the 2210/3 Interface to improve the interaction between TTWCS and CCS • Enable Task Manager to display CCS information from missile preparation and launch through post launch execution • Provide interface for Task Manager to invoke CCS windows so that CCS capabilities would become an extension of the Task Manager • Assumption: • Candidate will not add CCS functionality to TTWCS • Candidate involves incorporating resident CCS functionality on TTWCS

  13. UPE11: Integration of TTWCS/CCS Windows Analysis • Fleet Importance: Medium • Improve integration of TTWCS and CCS on SSN • Effort: High • External Dependencies: JCM 2210/3 Interface • Risk: High • Technical Risk: Medium • Schedule Risk: High • Significant impacts to Task Manager • Need to assess a large amount of existing TTWCS and CCS functionality • Requires extensive modification to the 2210/3 interface • Addresses 2 CRs Eliminates 0 TIP entries

  14. UPE11: Integration of TTWCS/CCS Windows Recommendations • Recommendation • Implement in v6 Defer for future consideration • Issues • Scope of UPE11 still being defined • Investigation into the amount of CCS / TTWCS interface desired by the SSN Community is ongoing • Implementation requires extensive modifications to an interface not under TTWCS SSA control (2210/3)

  15. UPE12: Enhance HCI for Maintaining Situational Awareness

  16. UPE12: Enhance HCI for Maintaining Situational Awareness Overview • Summary Description • Enhance existing/develop new HCI to improve situational awareness: • Maintain Task-Specific Situational Awareness (TTWCS Operator Viewpoint) • Maintain Team Supervisor Situational Awareness (ECO/TAO/CO Viewpoint) • Operator’s Perspective: • Provide better Situational Awareness of Strike Status and required actions to the TTWCS operator • Improve supervisory-level summary displays • Drill-Down and De-cluttering capabilities • Provide max-follow on salvo size • Standardization nomenclature on new/modified v6 Windows (e.g., eliminate “LAC-C” terminology) • Provides logical & sequential task flow to TTWCS HCI • CR Summary • Adaptive: 9 • Perfective: 5 • Corrective: 0 • TOTAL: 14

  17. UPE12: Enhance HCI for Maintaining Situational Awareness Analysis • Technical Description • Potential redesign of “Task Manager” • Includes making Engagement Status more clear on TM • Potential redesign of “TTWCS Summary Display” • Add Drill Down capability, Max Follow-on Salvo, De-cluttering features, Pre-Planned missions and Launch Basket and Composite Launch Basket to this display • Improve ability to evaluate missile flight path by providing single screen that shows: • Correct missile path • Accurate land masses • All (organic and off-hull) contact information including AOU, source of AOU, and time of AOU • Appropriate stand-off distances per LAC intentions • All airspace control measures • Will not require the addition of any digital chart interfaces currently not used by TTWCS • Improve nomenclature on new/modified v6 Windows • Eliminate “LAC” references and use NTTP standard naming format • Use consistent reference of “Plan” or “Engagement” across system • Improve the way Plan # / TLD / MSN is shown across system.

  18. UPE12: Enhance HCI for Maintaining Situational Awareness Analysis • Technical Description (cont) • ATTD Transition Candidates: • Situational Awareness Plot • Automation & Decision Support Opportunities • Task Centered Design & Task Manager • Assumption: UPE09 is funded, requiring no additional modifications to “Business Logic” CSCIs • UPE09 will already address removal of HCI from business logic CSCIs • New/modified windows may require additional data from business logic CSCIs • Anticipate data requirement additions will be small

  19. UPE12: Enhance HCI for Maintaining Situational Awareness Analysis • Fleet Importance: High • Effort: High • External Dependencies: None • Risk: Medium • Technical Risk: Medium • Schedule Risk: Medium • Impacts to two large windows (Task Manager / TTWCS Summary display) • Need to assess a large amount of existing TTWCS functionality associated with these tasks • Addresses 14 CRs Eliminates 0 TIP entries

  20. UPE12: Enhance HCI for Maintaining Situational Awareness Recommendations • Recommendation • Implement in v6 Defer for future consideration • Task Analysis will include analysis of information requirements which will facilitate identifying information which should be provided to the operator. • Issues • None

  21. UPE13: Enhance HCI for Tasking Management

  22. UPE13: Enhance HCI for Tasking Management Overview • Summary Description • Enhance HCI associated with Tasking Management: • Create / Edit Strike Package • Create / Edit Communications Plan • Validate ESP • Send / Edit Exception Report • Operator’s Perspective: Candidate improves HCI used to manage tasking • Provides logical & sequential task flow to TTWCS HCI when creating, editing and validating Electronic Strike Packages (ESPs) • HCI Improvements may include reducing button clicks, making windows more intuitive, improved “drill-down” features, etc. • New Capabilities: • Reduce operator error rates when processing strike packages • Add Auto-Ready Spare to Assignment Type • Improve ability to create / modify the Communications Plan for a Strike Package • Provides logical & sequential task flow to TTWCS HCI • CR Summary • Adaptive: 0 • Perfective: 11 • Corrective: 10 • TOTAL: 21

  23. UPE13: Enhance HCI for Tasking Management Analysis • Technical Description • Improve HCI that addresses Tasking Management using User Centered Design Process • Candidate does not itself change TTWCS functionality • Functional changes identified during task analysis will be addressed via CR process • Scope includes modifying HCI associated with the following tasks: • Create / Edit Strike Package • Create / Edit Communications Plan • Validate ESP • Send / Edit Exception Report • Changes include: • Contains corrective fixes for situations where Creation or Editing of a Strike Package resulted in system hang ups or conflicts • Improve HCI related to creating or editing a Communications Plan • Assumption: UPE09 is funded, requiring no additional modifications to “Business Logic” CSCIs • UPE09 will already address removal of HCI from business logic CSCIs • New/modified windows may require additional data from business logic CSCIs • Anticipate data requirement additions will be small

  24. UPE13: Enhance HCI for Tasking Management Analysis • Fleet Benefit • Improve ability to manually enter or modify Strike Packages • Improve process to reduce potential of operator error from causing Tasking conflicts • Fleet Importance: Medium to High • Effort: Medium to High • External Dependencies: None • Risk: Medium-to-High • Technical Risk: Medium • Schedule Risk: Medium-to-High • Addresses 21 CRs Eliminates 1 TIP entries

  25. UPE13: Enhance HCI for Tasking Management Recommendation • Recommendation • Implement in v6 Defer for future consideration • Issues • None

  26. UPE14: Enhance HCI for Engagement Planning

  27. UPE14: Enhance HCI for Engagement Planning Overview • Summary Description • Enhance HCI associated with Engagement Planning: • Create Engagements • Edit Engagements • Apply defaults to Engagements • Generate, review and take action based on Conflict Identification Analysis report • Operator’s Perspective: Candidate improves HCI used to conduct Engagement Planning tasking • Provides logical & sequential task flow to TTWCS HCI from right after an Exception Report is sent, through creating and editing engagements and conflict analysis • HCI Improvements may include reducing button clicks, making windows more intuitive, improved “drill-down” features, etc. • New Capabilities: • Increased Automation of Waypoint Selection and Editing • Evaluate option to apply the current system planning parameters to selected engagements • Improve usability of the Conflict Analysis Report • CR Summary • Adaptive: 3 • Perfective: 9 • Corrective: 3 • TOTAL: 15

  28. UPE14: Enhance HCI for Engagement Planning Analysis • Technical Description • Improve HCI that addresses Engagement Planning using User Centered Design Process • Candidate does not itself change TTWCS functionality • Functional changes identified during task analysis will be addressed via CR process • User Centered Design will modify Engagement Planning windows • Individual CR’s may become OBE with modifications • Scope includes modifying HCI associated with the following tasks: • Create Engagements • Edit Engagements • Apply defaults to Engagements • Generate, review and take action based on Conflict Identification Analysis report

  29. UPE14: Enhance HCI for Engagement Planning Analysis • Technical Description (cont) • Changes include: • Evaluate changing from AOU terminology to MTST Ellipse terminology • Evaluate displaying Block IV Branch ID in Engagement Window • Evaluate option to apply the current system planning parameters to selected engagements • Evaluate how to reference engagements (e.g., by MSN / TLD / Plan #) to provide for correlation across the system • Evaluate ability to globally Add option to apply changes to all existing engagements on the System Planning Parameters Window • Evaluate increased Automation of Waypoint Selection and Editing • Allow the operator to modify waypoints whenever they are selected without requiring "TLAM PLAN" window to be displayed before the operator can do anything to waypoints graphically. • Allow overriding the flight path without selecting "manual" from the TLAM PLAN window. • Assumption: UPE09 is funded, requiring no additional modifications to “Business Logic” CSCIs • UPE09 will already address removal of HCI from business logic CSCIs • New/modified windows may require additional data from business logic CSCIs • Anticipate data requirement additions will be small

  30. UPE14: Enhance HCI for Engagement Planning Analysis • Fleet Benefit • Improve ability to edit Engagements and apply default parameters • Improve the way engagements are referenced to allow for easier tracking of an engagement from creation to execution • Reduce chances of human error by simplifying process and improving tracking of engagements • Fleet Importance: High • Effort: Medium • External Dependencies: None • Risk: Medium • Addresses 15 CRs Eliminates 0 TIP entries

  31. UPE14: Enhance HCI for Engagement Planning Recommendation • Recommendation • Implement in v6 Defer for future consideration • Issues • None

  32. UPE15: Enhance HCI for Engagement Review and Approval

  33. UPE15: Enhance HCI for Engagement Review and Approval Overview • Summary Description • Enhance HCI associated with Engagement Review and Approval: • Review Engagements • Approve Engagements • Send SCOs • Operator’s Perspective: Candidate improves HCI used to conduct Engagement Review and Approval • Provides logical & sequential task flow to TTWCS HCI used to conduct Engagement Review and Approval including sending SCOs. • HCI Improvements may include reducing button clicks, making windows more intuitive, improved “drill-down” features, etc. • New Capabilities: • Facilitate process and show status of all engagement reviews • Improve the process to send SCOs off-hull • CR Summary • Adaptive: 0 • Perfective: 2 • Corrective: 0 • TOTAL: 2

  34. UPE15: Enhance HCI for Engagement Review and Approval Analysis • Technical Description • Improve HCI that addresses Engagement Review and Approval using User Centered Design Process • Candidate does not itself change TTWCS functionality • Functional changes identified during task analysis will be addressed via CR process • Scope of candidate includes modifying HCI associated with: • Review Engagements • Approve Engagements • Send SCOs • Changes include providing improved inputs to show review status to Task Manager • Assumption: UPE09 is funded, requiring no additional modifications to “Business Logic” CSCIs • UPE09 will already address removal of HCI from business logic CSCIs • New/modified windows may require additional data from business logic CSCIs • Anticipate data requirement additions will be small

  35. UPE15: Enhance HCI for Engagement Review and Approval Analysis • Fleet Benefit • Reduce chances of human error by simplifying process and improving tracking of engagements • Fleet Importance: Medium • Effort: Medium • External Dependencies: None • Risk: Low • Addresses 2 CRs Eliminates 0 TIP entries

  36. UPE15: Enhance HCI for Engagement Review and Approval Recommendation • Recommendation • Implement in v6 Defer for future consideration • Task Analysis will determine appropriate levels of review to track and display • Issues • None

  37. UPE16: Enhance HCI for Missile Selection and Preparation

  38. UPE16: Enhance HCI for Missile Selection and Preparation Overview • Summary Description • Enhance HCI associated with Missile Selection and Preparation • Missile Preselection • Missile Selection • Missile Alignment and Preparation for Launch • Operator’s Perspective: Candidate improves HCI associated with Missile Selection and Preparation • Provides logical & sequential task flow to TTWCS HCI used to conduct Missile Preselection, Missile Selection, Missile Alignment and Preparation for Launch • HCI Improvements may include reducing button clicks, making windows more intuitive, improved “drill-down” features, etc. • Improves presentation of inventory functions and resolution of fault conditions • New Capabilities: • Improve navigation to Launcher Information Window • Improve how missile and launcher information is presented to the operator • CR Summary • Adaptive: 0 • Perfective: 4 • Corrective: 0 • TOTAL: 4

  39. UPE16: Enhance HCI for Missile Selection and Preparation Analysis • Technical Description • Improve HCI that addresses Missile Selection and Preparation using User Centered Design Process • Candidate does not itself change TTWCS functionality • Functional changes identified during task analysis will be addressed via CR process • Scope of candidate includes modifying HCI associated with: • Missile Preselection • Missile Selection • Missile Alignment and Preparation for Launch

  40. UPE16: Enhance HCI for Missile Selection and Preparation Analysis • Technical Description (cont) • Changes include: • Potential redesign of Launcher / Missile information windows to simplify overall view but allow for drill down information capability • Correct slow sorting on window, which causes failure to select missile • Perfecting MM Window Design • Improving navigation to Launcher Information Window from Job Bar or Task Manager equivalent windows • Perfecting Missile pre-selection / selection process so that it is not confusing to the operator • Assumption: UPE09 is funded, requiring no additional modifications to “Business Logic” CSCIs • UPE09 will already address removal of HCI from business logic CSCIs • New/modified windows may require additional data from business logic CSCIs • Anticipate data requirement additions will be small

  41. UPE16: Enhance HCI for Missile Selection and Preparation Analysis • Fleet Benefit • Make Missile Selection process more intuitive • Allow greater capability to use Cell Allocation as a planning tool • Fleet Importance: Medium • Effort: Medium • External Dependencies: None • Risk: Medium • Addresses 4 CRs Eliminates 0 TIP entries

  42. UPE16: Enhance HCI for Missile Selection and Preparation Recommendation • Recommendation • Implement in v6 Defer for future consideration • Issues • None

  43. UPE17: Enhance HCI for Mission Execution

  44. UPE17: Enhance HCI forMission Execution Overview • Summary Description • Enhance HCI associated with Mission Execution • Execute Engagement • Launch Weapons • Monitor Launcher / Missile Status • Respond to Launcher / Missile Faults • Operator’s Perspective: Candidate improves HCI associated with Mission Execution • Provides logical & sequential task flow to TTWCS HCI used to conduct execute engagements, launch missiles, monitor launcher/missile status, and respond to launcher / missile failures • HCI Improvements may include reducing button clicks, making windows more intuitive, improved “drill-down” features, etc. • CR Summary • Adaptive: 0 • Perfective: 3 • Corrective: 1 • TOTAL: 4

  45. UPE17: Enhance HCI forMission Execution Analysis • Technical Description • Improve HCI that addresses Mission Execution using User Centered Design Process • Candidate does not itself change TTWCS functionality • Functional changes identified during task analysis will be addressed via CR process • Scope of candidate includes modifying HCI associated with: • Execute Engagement • Launch Weapons • Monitor Launcher / Missile Status • Respond to Launcher / Missile Faults

  46. UPE17: Enhance HCI forMission Execution Analysis • Technical Description (Cont) • Changes include: • Add the P/R/B (or pool designation) to launch execution window • Correct display so that all cells of a module turn red after a Restrained Fire or similar casualty • Provide information so that operator can view Launcher Enable Status when viewing "Working Allocation Mode“ • Assumption: UPE09 is funded, requiring no additional modifications to “Business Logic” CSCIs • UPE09 will already address removal of HCI from business logic CSCIs • New/modified windows may require additional data from business logic CSCIs • Anticipate data requirement additions will be small

  47. UPE17: Enhance HCI forMission Execution Analysis • Fleet Benefit • Allows better monitoring of System, Missile and Launcher Status when executing Tasking • Provides better information to allow operator to accomplish tasking during casualties • Fleet Importance: Medium • Effort: Medium • External Dependencies: None • Risk: Medium • Potential risk associated with separating HCI from CSCIs handling Mission Execution (Primarily MM) • Have safety support on v6 Presentation Layer Team to address safety issues • Addresses 4 CRs Eliminates 0 TIP entries

  48. UPE17: Enhance HCI forMission Execution Recommendation • Recommendation • Implement in v6 Defer for future consideration • Issues • None

  49. UPE18: Enhance HCI for Onboard Mission Planning

  50. UPE18: Enhance HCI for Onboard Mission Planning Overview • Summary Description • Enhance HCI associated with Mission Execution • Create LPMP Missions • Generate exception report for LPMPs • Perform ACMS accountability Tasking • Operator’s Perspective: Candidate improves HCI used to execute CFF missions and create LPMPs associated with Onboard Mission Planning • Provides logical & sequential task flow to TTWCS HCI used to to execute CFF missions and create LPMPs • HCI Improvements may include reducing button clicks, making windows more intuitive, improved “drill-down” features, etc. • CR Summary • Adaptive: 0 • Perfective: 4 • Corrective: 4 • TOTAL: 8

More Related