Much of the early work in developing a system involves the definition and decomposition of requirements. Requirements from a variety of sources and disciplines must be analyzed to remove conflicts. The human effort engineer is primarily concerned with concerned with two types of requirements, human performance requirements and human engineering design requirements.
Human performance requirements include times and accuracies for tasks assigned to humans. The human effort engineer must ensure that the proposed requirements are in fact achievable by the intended operators and users. The human performance requirements are based on external requirements and the specifications of other system components and in some cases, the capabilities and limitations of cooperating operators and users. The human effort engineering design requirements concern specific aspects of the hardware and software that are necessary to fit the operators and assist them in their assigned tasks. These requirements define what must be designed and constructed to permit the operators to interact with one another and the rest of the system. Human effort engineering input and also human factors engineering inputs are required to ensure the completeness of system requirements involving users or operators.
Human performance requirements are frequently derived from or at least bounded by other performance requirements levied on the system such as the time available to complete an action or to make a decision. The accuracy, response time, and other attributes of the operator tasks will affect the ability of the system to satisfy related requirements at the system level. Therefore, the human performance requirements should be in a format similar to that of the system-level requirements. Common format within a given project, both visually and electronically, will make the derivation of human performance requirements easier, and it will also make the verification or approval of those requirements by the systems engineers a simpler task. Other domains will also be more apt to incorporate requirements in a format similar to their own. In the same way, the human effort engineering design requirements should share a common format. In the case of these requirements, a common format is even more important as they must be reviewed or followed by system designers in other disciplines. Although the human effort engineer is the one who may set requirements for the design of other system components, the complete design and construction of those components will be the responsibility of others within the project. As designs become more detailed, a continuous interaction between the human effort engineer and other disciplines becomes more valuable. The implementation of the requirements needs to be verified, and additional design decisions need to be made as the design progresses.
Source:
Report of Manning Affordability Initiativ of the Office of the Naval Research (Section 3.2.2)
http://www.hf.faa.gov/docs/508/docs/Human_System_Engineering_(NSWC).pdf
Human performance requirements include times and accuracies for tasks assigned to humans. The human effort engineer must ensure that the proposed requirements are in fact achievable by the intended operators and users. The human performance requirements are based on external requirements and the specifications of other system components and in some cases, the capabilities and limitations of cooperating operators and users. The human effort engineering design requirements concern specific aspects of the hardware and software that are necessary to fit the operators and assist them in their assigned tasks. These requirements define what must be designed and constructed to permit the operators to interact with one another and the rest of the system. Human effort engineering input and also human factors engineering inputs are required to ensure the completeness of system requirements involving users or operators.
Human performance requirements are frequently derived from or at least bounded by other performance requirements levied on the system such as the time available to complete an action or to make a decision. The accuracy, response time, and other attributes of the operator tasks will affect the ability of the system to satisfy related requirements at the system level. Therefore, the human performance requirements should be in a format similar to that of the system-level requirements. Common format within a given project, both visually and electronically, will make the derivation of human performance requirements easier, and it will also make the verification or approval of those requirements by the systems engineers a simpler task. Other domains will also be more apt to incorporate requirements in a format similar to their own. In the same way, the human effort engineering design requirements should share a common format. In the case of these requirements, a common format is even more important as they must be reviewed or followed by system designers in other disciplines. Although the human effort engineer is the one who may set requirements for the design of other system components, the complete design and construction of those components will be the responsibility of others within the project. As designs become more detailed, a continuous interaction between the human effort engineer and other disciplines becomes more valuable. The implementation of the requirements needs to be verified, and additional design decisions need to be made as the design progresses.
Source:
Report of Manning Affordability Initiativ of the Office of the Naval Research (Section 3.2.2)
http://www.hf.faa.gov/docs/508/docs/Human_System_Engineering_(NSWC).pdf
Great topic for the day with "H"
ReplyDeleteMine I am still working on it come later today
Best Wishes
P V