Embedded in the test and fix cycle to ensure

This preview shows page 10 - 11 out of 16 pages.

embedded in the test and fix cycle to ensure efficient understanding of user change requirements andtest findings and their fixes for successful integration into the service pack baseline. Also, HFexpertise will be utilized to customize and tailor HMI documents and capabilities to specific missionrequirements and seat positions within the system enterprise.The process of designing the HMI begins with the analysis of requirements from the applicabledocumentation including the System Requirements Specification (SRS), Application RequirementsDocument (ARD), Functional Requirements Document (FRD), and the Capability DevelopmentDocument (CDD) when a higher level context is needed. In the case of the increment deliveryschedule, work breakdown structure documents and the SRS are utilized to specify the time andscope for delivery of components. From the requirements analysis phase, the HMI team expects tohave clear guidance on mission applications, tools, and capabilities that will be delivered per sprint orservice pack. The HMI team should be able to create a very high-level architecture based onknowledge elicited from analysis of requirement documentation and work patterns found during theUCD process.The discovery and capture of specific artifacts produced by the user community during userengagement events is essential to the design process for the HMI. The origin of such artifacts,including the overall data flow (inputs, processes, and outputs), must be captured before the HMI canbe fully designed. Input files and data, specific legacy applications, output formats, and deliveryvectors must be identified and codified to accurately associate their creation and delivery, and also tofacilitate better productivity and process flow.Legacy applications used to create outputs or complete work must be carefully analyzed by thosewith applicable C2 expertise. The legacy system architectures must be fully vetted for processcontrols and potential areas of improvement and analyzed in the context of program requirements toaid in the satisfaction those that are legacy-related or focused.Also, design personnel must fully encapsulate patterns of interaction from high levels (e.g., use oftabular data and interactive graphing components) down to terminally specific implementations ofdata, such as specific step-by-step procedures necessitated by the underlying command and controlcomputations and the variables assigned to each piece of data. User engagement will facilitate boththe determination of these existing steps, and should also elicit shortcomings, stopgaps, and areas forprocess improvement for HMI implementation.Once existing technologies, procedures, and outputs have been identified to prototype a highfidelity HMI, UCD identified replacement applications and technologies must be assessed for dataflow, interaction patterns, infrastructure design, and data service availability. Technical interchange

Upload your study docs or become a

Course Hero member to access this document

Upload your study docs or become a

Course Hero member to access this document

End of preview. Want to read all 16 pages?

Upload your study docs or become a

Course Hero member to access this document

Term
Spring
Professor
cao dinh kien
Tags

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture