AgileSTEP Project A Summary of the Final Report

1. AgileSTEP ProjectA Summary of the Final Report Jim U�Ren March, 2004

2. Task Description Identify standards-based technologies that can be used to communicate Information Exchange Requirements (IER�s)

3. AgileSTEP Team Members Program Management Gerald Graves/ATI Tom Thurman/Rockwell Collins Mike Keenan/Boeing Greg Smith/Boeing Bill Anderson/PDES, Inc.

4. What is an IER? The data that is passed across an interface A mechanism for communicating information between system development participants The data that is required to satisfy an interface exchange agreement, i.e., Interface Control Document The output from a process that may be input into another

5. Characteristics Common to IERs Can be atomic (attribute value pairs) Can be a collection of atomic elements Can have structural relationships Can reference each other Can be hierarchical Can grow in complexity throughout the development cycle Often implied but not specified

6. Candidate IERs for Agile STEPLevel of Coverage

7. Mapping STEP elements to DODAF elements � M. Ward/Eurostep

8. Working High-level Spacecraft Process Model

9. Evolving IER Information Content Example

10.

11. Effectiveness Measure IER usually called �Measures of Effectiveness� Definition: Criterion by which system solutions will be judged from a stakeholder perspective Highly subjective and not currently well defined within system engineering community Example: �Land a man on the Moon and return him safely to Earth before the end of the decade� � Apollo program Mission data return �Did it work or not?� Definition: �The measure of effectiveness is the criterion by which solutions will be judged �proposed solutions, solutions under test, or solutions in being�, Goode, Harry H., and Robert E. Machol, the Design of Large-scale Systems, New York: McGraw-Hill Book, 1957 Measures of effectiveness provide metrics to judge how well a system satisfies a requirement from a stakeholder perspective; measures of Performance provide similar information from an engineer�s perspective Example: MoEs can be direct metrics with weightings (e.g., number of ships sunk on a sortie) or weightings applied to optional requirements (e.g., the computer casing shall have a glassy finish) Definition: �The measure of effectiveness is the criterion by which solutions will be judged �proposed solutions, solutions under test, or solutions in being�, Goode, Harry H., and Robert E. Machol, the Design of Large-scale Systems, New York: McGraw-Hill Book, 1957 Measures of effectiveness provide metrics to judge how well a system satisfies a requirement from a stakeholder perspective; measures of Performance provide similar information from an engineer�s perspective Example: MoEs can be direct metrics with weightings (e.g., number of ships sunk on a sortie) or weightings applied to optional requirements (e.g., the computer casing shall have a glassy finish)

12. Tools used to generate IER data: Requirements Tools may be configured to handle MoEs Optimisation, design of experiment and trade-off tools, e.g., ANOVA-TM, DOE Wisdom, Stadium, STN may be used to compute MoEs Requirements tools may also employ user-defined attributes to store weightings and MoE information Relevant data models: AP233 Requirements modules (as included in PLCS ISO standard ballot package) Current level of coverage: Complete (using classification mechanism in AP233 Requirements Model)

13. Key Performance Parameter (KPPs) IER Definition: Critical subset of system Measures of Performance Quantitative and may have a threshold and an objective value Example: Mass, Cost and Data Rate (JPL PDC favorites ) Coverage, Revisit Time and Resolution (NRO favorites)

14. Key Performance Parameter IER (cont.) Tools used to generate IER data: Requirements management tools and requirements engineering tools System performance models Examples � spreadsheets, custom tools and software Relevant Data Model AP233 Requirements Model Current level of coverage: Complete (using classification mechanism) Weighting to be supported in AP233 Allocation Module (future development)

15. Time Sequence Event IER Definition: An aggregation of space system activities and external events in a time ordered sequence Reference: APGEN Users Guide Version 1.0 Example: APGEN Predicted Event File (PEF)

16. Time Sequence Event IER (cont.) Tools used to generate IER data: APGEN Relevant data models: AP233, Mandate Time Model Current level of coverage: partial SC4 Mandate yet to be implemented AP 233 planning to reuse Mandate in Behavorioal Module Sets

17. Orbit Specification IER Definition: specification of the basic orbit parameters including angles defining the spacecraft orientation. Examples: Keplerian (orbit) State Vector (orbit) Euler Angle � Roll, Pitch & Yaw (attitude) Quaternions (attitude) Tools used to generate IER data: ESARAD, STK, etc. Relevant data models: STEP-TAS Other related standards: OrbitML Current level of coverage: Complete (Keplerian)

18. Orbit IER Example � Keplerian Element Sets

19. Mass IER Definition: A quantitative measure of that property of matter which causes a resistance to any change in the motion of a body. The mass depends on the volume of the body and the density of the material comprising the body. Example: The mass of the landing gear of an F -XY Block Z fighter plane exceeds 200 kilograms.

20. Mass IER Tool that generate Mass Properties IER data: CATIA, UG, Pro-Engineer, etc. Tools that contain Mass Properties IER data: MS Word, MS Excel table, Relevant data models: STEP AP 209, 214, Part 1039 Current level of coverage: Partial 1039 � Partial -1039 � Partial -

21. Design Rules IER Definition: A constraint, either conditional or unconditional, quite often levied via system requirements, physical limitations or environmental restrictions that may effect one, many or all of the life cycle processes (e.g., design, manufacture, disposal, recycle, etc.) for a given product or family of products. Example: GUIDELINE: Components and hardware should not extend below the bottom side of a PCA more than 0.175 inches.

22. Design Rules IER (cont.) Example (cont.): RATIONALE: The depth of the flow solder wave is approximately 0.200 inches. Approximately 0.025 inch of solder mask is applied to all hardware and some components prior to wave solder. Components or hardware that exceed this value will get caught on the wave nozzle and be trapped over the solder pot REFERENCE: Automated Flow Solder Machine, Electrovert 2000, Dual wave, finger conveyor computer controlled, capable of handling boards up to 19.5 inches wide

23. Design Rules IER (cont.) Tools used to generate IER data: APGEN Relevant data models: AP210, STEP Part 50 Current level of coverage: partial AP210 (in the area of design rules) is being refined Part 50 is being examined for possible use in providing infrastructure to support functional definition

24. Conclusions IERs are a language which organizations use to communicate internally and with their partners The older, more conventional way is to communicate IER information through document-based systems A more precise and efficient way to communicate is to use standardized data structures as an alphabet and grammar for exact communication STEP data models can be use to provide the context and precision required

25. Work to be performed Detailed mapping of test data to standard data models Prototype extensions of existing models to support test cases Investigate adapting existing tools to this approach of creating IER data, e.g., API tool kits