271
Integration in Systems Engineering Context
purpose of testing is to show that the functions are required by the final
product or service are substantiated in a manner that invokes the desired
behaviors of the users. Therefore, testing requires more than the test model
that is typical of most projects today. To assure that the required functionality is present, testing must not only confirm the mechanical, electrical, chemical, biological, computer hardware, and computer software issues, but also
the fitness for use and the sociological aspects of the user behaviors. There
are likely no quick fixes to the product or service after it has been placed into
operation, so the operative moments to deal with these issues is during the
system design phase when the subsystems are being identified and the
requirements are being allocated to components. System design involves
evaluating off-the-shelf components, evaluating alternatives, determining
the selection criteria, analyzing and allocating requirements from the system
requirements, and identifying the interfaces. Components are defined in the
system design in terms of their functionality and performance.
System Design
System design is the opportunity to conceptualize the user’s needs by
answering the following example questions:
• What decisions does the user need to make?
• How much information does the user need to make those decisions?
• From where will the information come?
• How much detail does the information need to assist the user?
• How does the user determine what information is needed?
• What level of trust does the user ascribe to the information?
• How should the information be represented?
• How should the information be presented to the user?
• What is the time line for the user’s decisions?
• Is there a natural sequence in which the information should be provided to the user?
• What are the differences between the users and their decisions?
• What procedures should be built into the product or service that are
most natural to assist the user in making decisions?
• What are the functional characteristics of the product or service that
the user requires to complete the user’s tasks?
• What are the performance(s) of the functions that are expected?
How do those expectations compare with the requirements?
Integration in Systems Engineering Context
purpose of testing is to show that the functions are required by the final
product or service are substantiated in a manner that invokes the desired
behaviors of the users. Therefore, testing requires more than the test model
that is typical of most projects today. To assure that the required functionality is present, testing must not only confirm the mechanical, electrical, chemical, biological, computer hardware, and computer software issues, but also
the fitness for use and the sociological aspects of the user behaviors. There
are likely no quick fixes to the product or service after it has been placed into
operation, so the operative moments to deal with these issues is during the
system design phase when the subsystems are being identified and the
requirements are being allocated to components. System design involves
evaluating off-the-shelf components, evaluating alternatives, determining
the selection criteria, analyzing and allocating requirements from the system
requirements, and identifying the interfaces. Components are defined in the
system design in terms of their functionality and performance.
System Design
System design is the opportunity to conceptualize the user’s needs by
answering the following example questions:
• What decisions does the user need to make?
• How much information does the user need to make those decisions?
• From where will the information come?
• How much detail does the information need to assist the user?
• How does the user determine what information is needed?
• What level of trust does the user ascribe to the information?
• How should the information be represented?
• How should the information be presented to the user?
• What is the time line for the user’s decisions?
• Is there a natural sequence in which the information should be provided to the user?
• What are the differences between the users and their decisions?
• What procedures should be built into the product or service that are
most natural to assist the user in making decisions?
• What are the functional characteristics of the product or service that
the user requires to complete the user’s tasks?
• What are the performance(s) of the functions that are expected?
How do those expectations compare with the requirements?