1 / 46

24 th International Forum on COCOMO and Systems/Software Cost Modeling

24 th International Forum on COCOMO and Systems/Software Cost Modeling. COSYSMO Workshop. COSYSMO for Human Systems Integration. 1. requirements. Determine System of Interest. Requirements Decomposition for COSYSMO: Overview. 1. 2. requirements. Determine System of Interest.

nichelle-brown
Télécharger la présentation

24 th International Forum on COCOMO and Systems/Software Cost Modeling

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. 24th International Forum on COCOMO and Systems/Software Cost Modeling COSYSMO Workshop COSYSMO for Human Systems Integration

  2. 1 requirements Determine System of Interest Requirements Decomposition for COSYSMO: Overview

  3. 1 2 requirements Determine System of Interest Can Requirements be: Tested? Verified? Designed? Yes No Re-define requirement Requirements Decomposition for COSYSMO: Overview

  4. 1 2 requirements Determine System of Interest Can Requirements be: Tested? Verified? Designed? Yes No Re-define requirement Omit/ Guess (bad) Decompose Assign High Uncertainty Requirements Decomposition for COSYSMO: Overview

  5. 1 2 requirements Determine System of Interest Can Requirements be: Tested? Verified? Designed? Yes No 3 Sketch System of Interest’s Relationship to Rest of System Requirements Decomposition for COSYSMO: Overview

  6. 1 2 requirements Determine System of Interest Can Requirements be: Tested? Verified? Designed? Yes No 3 4 Sketch System of Interest’s Relationship to Rest of System Count Only Requirements at the Level of the System of Interest Shall’s Will’s Must’s Requirements Decomposition for COSYSMO: Overview

  7. 1 2 requirements Determine System of Interest Can Requirements be: Tested? Verified? Designed? Yes No 3 4 Sketch System of Interest’s Relationship to Rest of System Count Only Requirements at the Level of the System of Interest Shall’s Will’s Must’s Assess Complexity 5 Requirements Decomposition for COSYSMO: Overview

  8. Scenario A much-celebrated feature of modern aircraft design has been the glass instrument panel: they are cheaper to produce than standard instruments and can be easily modified to fit different missions. You are an engineer at a major auto company. Your company is exploring the possibility of developing a glass console display for its upcoming luxury line of SUVs. They have written some preliminary requirements for the console and would like you to review them. You decide to apply the decomposition rules found in COSYSMO to assist you in your recommendations. You will work in teams of two; please only communicate with your partner.

  9. Part 1: System of Interest. Is the stated requirement at the level of the glass console being designed or is it higher or lower? Help: If it is lower, what higher-level requirement could be used to capture this concept for the glass console? If it is higher, what derived requirement(s) would capture this requirement’s intent at the level of the glass console? If you can’t answer these questions, perhaps the level of interest is actually correct!

  10. 1 requirements Determine System of Interest

  11. Cautions and Warnings. Method for displaying system warnings, cautions, and alarms must be appropriate given the importance of the situation (Threshold). Requirement #1 Exercise #1: Identify the System of Interest

  12. Timeliness and Accuracy of Information. The glass console will present accurate and timely data from many important systems to the driver. The console must detect data errors and display an error message instead of incorrect information (threshold). An error message must be displayed if the system detects a lag of greater than (threshold=20ms, objective=2ms) Requirement #2 Exercise #1: Identify the System of Interest

  13. User Interface. The user must be able to interact with the console using either touch or voice (threshold). Requirement #3 Exercise #1: Identify the System of Interest

  14. Response Time. User must be able to perceive and process all information displayed by console in under (threshold=20ms, objective=2ms). Requirement #4 Exercise #1: Identify the System of Interest

  15. Map Readability. Maps displayed for the GPS function of the console shall be readable with 20/20 vision at 1 meter (threshold). Requirement #5 Exercise #1: Identify the System of Interest

  16. Emergency Override. In the case that the console receives an emergency interrupt from vehicle sensors, it shall display the appropriate emergency caution, alarm, or alert in under (threshold=2ms) Requirement #6 Exercise #1: Identify the System of Interest

  17. Data Redundancy. All sensors built into the vehicle must provide a copy of its output to the glass console for possible integration into alerts, alarms, or cautions (threshold). Requirement #7 Exercise #1: Identify the System of Interest

  18. Speech Displays. If the console is to employ computer-generated speech to communicate with the driver, speech rate must not exceed 150 wpm (threshold) Requirement #8 Exercise #1: Identify the System of Interest

  19. Part 2: Can the requirement be tested, verified, OR designed? If you have to decompose the requirement in order to be able to test, verify, or design it, then the answer is no. Help What is the test? Even if a requirement can be tested, that doesn’t mean the designer could have done anything to design it into the system. How would you design the requirement?

  20. 1 2 requirements Determine System of Interest Can Requirements be: Tested? Verified? Designed? Yes No Re-define requirement Requirements Decomposition for COSYSMO: Overview

  21. 1 2 requirements Determine System of Interest Can Requirements be: Tested? Verified? Designed? Yes No Re-define requirement Omit/ Guess (bad) Decompose Assign High Uncertainty Requirements Decomposition for COSYSMO: Overview

  22. Cautions and Warnings. Method for displaying system warnings, cautions, and alarms must be appropriate given the importance of the situation (Threshold). Exercise #2: Can the Requirement be Tested, Verified, OR Designed? Requirement #1

  23. Response Time. The driver must be able to perceive and process all information displayed by console in under (threshold=20ms, objective=2ms). Exercise #2: Can the Requirement be Tested, Verified, OR Designed? Requirement #2

  24. Display Contrast. All text displayed by the glass console must have a contrast ratio of (objective=5000:1, threshold=1000:1), defined as the ANSI standard contrast ratio in an ideal room. Exercise #2: Can the Requirement be Tested, Verified, OR Designed? Requirement #3

  25. Display Reliability. The glass console must not fail due to electrical malfunction within the lifetime of an average vehicle (assume 10 years) (threshold). Exercise #2: Can the Requirement be Tested, Verified, OR Designed? Requirement #4

  26. Mitigation of Divided Attention. The driver shall be able to operate all aspects of the glass console without having a measurable impact upon driving performance (threshold). Exercise #2: Can the Requirement be Tested, Verified, OR Designed? Requirement #5

  27. Console Startup/Shutdown Times. The glass console must be available for the driver to interface with within (objective=2s, threshold=5s) of the beginning of the ignition sequence. The glass console must be in a low-power or standby state within (threshold=10s) of vehicle power-off. Exercise #2: Can the Requirement be Tested, Verified, OR Designed? Requirement #6

  28. Function Execution. The driver must be able to perform any single task (menu selection, radio station switching) in under (threshold=5 s) Requirement #7 Exercise #1: Identify the System of Interest

  29. Data Integration. All displays within the glass console shall use a standard set of buttons and labels to improve intuitiveness (threshold) Exercise #2: Can the Requirement be Tested, Verified, OR Designed? Requirement #8

  30. Part 3: Sketch the system-of-interest within the system Could this requirement be decomposed into HSI requirements relevant to the system-of-interest? If so, 1 Requirement OR Many Requirements 1 or multiple domains affected? Please provide a short justification

  31. HSI requirements include, but are not limited to, any requirement pertaining to one or more domains of HSI, or the integration of those domains. Broadly, the term encompasses any requirement that contributes to the integration of human considerations into the system being developed.

  32. Manpower---Addresses the number and type of personnel in the various occupational specialties required and potentially available to train, operate, maintain, and support the deployed system. The Manpower domain includes the pursuit of engineering designs that optimize the efficient and economic use of manpower, keeping human resource costs at affordable levels. Determination of required Manpower positions must recognize the evolving demands on humans (cognitive, physical, and physiological) and consider the impacts that technology can make on humans integrated into a system. Manpower in HSI is related to but not identical to Human Resources.

  33. Personnel---Considers the type of human knowledge, skills, abilities, experience levels, and human aptitudes (i.e., cognitive, physical, and sensory capabilities) required to operate, maintain, and support a system; and the means to provide (recruit and retain) such people. Personnelrecruitment, testing, qualification and selection are driven by system requirements. The Personnel domain helps define the human performance characteristics of the user population and then determine target populations to select for occupational specialties. Personnel must manage occupational specialties to include career progression and assignments. Personnel population characteristics can impact manpower and training, as well as drive design requirements. Personnel is related to Human Resources, but not identical to it.

  34. Training---Encompasses the instruction and resources required to provide personnel with requisite knowledge, skills, and abilities to properly operate, maintain, and support systems. The Training domain develops and delivers individual and collective qualification training programs, placing emphasis on options that enhance user capabilities, maintain skill proficiencies (through continuation training and retraining), expedite skill attainment, and optimize the use of training resources. Training systems, such as simulators and trainers, should be developed in conjunction with the emerging system. The overall training system may be required prior to fielding the system so that personnel can be adequately trained to operate, maintain, and support the system when it is fielded; therefore, it also is important to develop the training system concurrent with the operational system.

  35. 1 2 requirements Determine System of Interest Can Requirements be: Tested? Verified? Designed? Yes No 3 Sketch System of Interest’s Relationship to Rest of System Requirements Decomposition for COSYSMO: Overview

  36. Timeliness and Accuracy of Information. The glass console will present accurate and timely data from many important systems to the driver. The console must detect data errors and display an error message instead of incorrect information (threshold). An error message must be displayed if the system detects a lag of greater than (threshold=20ms, objective=2ms) Exercise #3: How does the system-of-interest fit into the larger system? Requirement #1

  37. Temperature Control. The inside temperature must remain within 2 degrees Celsius of the desired temperature set by the driver during normal driving conditions (threshold). Exercise #3: How does the system-of-interest fit into the larger system? Requirement #2

  38. Passenger Safety. In the case of a front or side-impact collision at speed over 80 mph, but under 100mph, chance of survival for all passengers must be greater than 95%, given an average adult male or female (threshold). Exercise #3: How does the system-of-interest fit into the larger system? Requirement #3

  39. Documentation. All manuals/documentation for the vehicle will include all information necessary to operate the vehicle in a safe and effective way (threshold). Exercise #3: How does the system-of-interest fit into the larger system? Requirement #4

  40. Air Quality. Air quality must be maintained to standards as set forth in QLT-STD-1234 (threshold). In the case that air quality degrades below these standards, appropriate alarms or alerts shall warn the driver (threshold). Exercise #3: How does the system-of-interest fit into the larger system? Requirement #5

  41. Maintenance Time. All minor to medium-level vehicle maintenance tasks shall take no longer than (objective=1hr, threshold=2hrs) to complete. Exercise #3: How does the system-of-interest fit into the larger system? Requirement #6

  42. Ambient Light. All displays must function to identical performance characteristics in low light as well as direct sunlight (threshold). Exercise #3: How does the system-of-interest fit into the larger system? Requirement #7

  43. Console Startup/Shutdown Times. The glass console must be available for the driver to interface with within (objective=2s, threshold=5s) of the beginning of the ignition sequence. The glass console must be in a low-power or standby state within (threshold=10s) of vehicle power-off. Exercise #3: How does the system-of-interest fit into the larger system? Requirement #8

  44. Discussion

More Related