Boeing Wiring System (BWS) is a suite of wiring tools, divided into two parts:

• BWS-DME (Design and Manufacturing Engineering) which will replace WIRS/MAPPER.
• BWS-CM (Change Management) which will replace the change management tools

UX focuses on establishing a consistent UI experience through a design style guide and UI framework as well as being the end-user advocate through user interviews/testing. For DME, UX is responsible for supporting the following work packages:

• Work Package 3 - Wire Design and Wire Bundle Installation
• Work Package 4 - Physical Design and Electrical Corrective Action
• Work Package 5 - ME/IE/Operations (Change Tracking and Visibility)
• Work Package 6/7 - Schedmatic/Diagram Control and CADDS5 replacement

The UX team supports the Product Owners (PO), Functional Engagement Focals (FE), Business, and Developers

• Product Owners - Provide style guide and UI Framework so PO's can log visual defects
• Functional Engagement - Work with FE's to design new screens through user interviews, design studios, prototyping, and user testing
• Business - Work with business, which is engineering (BCA) in this case to validate assumptions in the business requirements
• Developers - Provide style guide and UI Framework as a set of standards developers can reference when resolving defects

• UI Standards - Consists of Geri Hathaway-Arndt and Matthew Amberg who jointly maintain the UI framwork with UX. They are contacted when there is a UI discrepancy in the code, such as the wrong code for a button being used on a page.
• Commons - Consists of Phil Davenport, Melissa Chapman, Matthew Amberg, Craig Blatter, and Aaron Vergaray who work on components that are common across the tool such as audits, general syntax/verbiage, data grid, reports, import/export, data marking.
• UX - Consists of Christopher Chung who manages the DME UX homepage, Style Guide, UI framework, to ensure a consistent UI experience. They are contacted when designing new screens or validating assumptions/business requirements,

Navigate to the TFS backlog from the UX homepage and submit a new user story tagged with "UX" Make sure to include the following details:

• Brief description of the request and any supporting documentation
• Urgency of request so it can be prioritized
• Contact info and availability so that a followup meeting can be scheduled to discuss the request

The style guide provides a quick reference guide for the look and feel of the tool. It includes the indidivudal components on the first page, as well as several examples of screens in the tool and new concepts. The UI framework provides the supporting documentation, indicating how, when, and where to the use the individual or grouped components from the style guide. This helps with logging defects, as the visual defects can reference and even link to the style guide or UI framework, to make it easier for devs to resolve.

• SAFE - Although there should be a single UX role assigned to each balanced team in the SAFE model, due to the lack of UX designers, the UX role works outside of the balanced team and instead supports multiple balanced teams. In BWS-DME's case, it's Work package 3,4,5,6/7, and Commons
• DTE - DTE follows Agile with UX integrated into the process, starting with Design + Framing (D + F) where the scope is defined through user research conducted by UX. Once that's complete, a problem statement and list of assumptions are defined, where UX can conduct user interviews and create prototypes and user test to validate assumptions defined in D + F. In BWS-DME's case, since its replacing an existing app and there's a lot of legacy work already done, there is no D + F, just validation of assumptions.

The plan is to establish parity between BWS-CM and BWS-DME on the UX side through merging the two UX teams, so that UX designers can be familiar and support both tools. However the style guide and ui frameworks will be kept separate for the two teams, due to the underlying platform (BWS-CM is web-based, while BWS-DME is desktop). BWS-DME will have its own UX homepage hosting the style guide and UI framework, same as BWS-CM. In the future, when parts of BWS-DME that are web-based and integrate with BWS-CM are developed, they will follow the style guide and UI framework from BWS-CM, so that all web-based screens are consistent.

UX debt consists of usability issues and visual/cosmetic defects that are non-functional. These are often deprioritized over techincal debt (aka functional defects). However, it is important to take care of UX debt, since it can propagate very quickly, especially with so many work packages working in parallel. What can happen is a code snippet for a button style gets passed around that conflicts with the UI framework, and if it isn't logged and resolved immediately, then multiple button styles start appearing in the code, and it becomes much more work to resolve later down the line.