procurement Flashcards
sources of HF design requirements
Refinements can occur as a result of:
-Change/better defined scope of project
-Analysis being started (OER, FA, TA)
-User requirements are better understood
- Concepts of Operations is defined
also requirements come from standards/guidelines
8 areas of requirements
- Basic Design Elements
- Simplicity
- Consistency
- Standardization
- Safety
- User-Centered Perspective
- Support
- Maintenance
Simplicity
The equipment shall represent the simplest design consistent with
functional requirements and expected operational conditions.
Functions shall be automated only to attaingreater overall effectiveness, efficiency, reliability, simplicity, economy, and system safety rather than relying on human performance alone
Critera for requirements
- Clear, unique, consistent,
- Traceable to source requirement
- Verifiable
- Not redundant, nor in conflict with, any other known requirement
- Not biased by any particular implementation
example of requirement
The System shall fit a 95th percentile US Male Patient
Headlight replacement shall take no more than 15 minutes
bad requirements
The software architecture needs to be flexible and modular
The GUI shall be user friendly
(subjective) (needs to be user validated)
Shall v. should in requirements
shall for safety considerations
sometimes you can do something vague and say should, or specific and say shall
Ways to communicate requirements to a project
-include in system/sub-system design requirements(specific section)
-Include in technical specifications for procurement
-Identify standards to be followed
-Produce specific project design guidelines
-communicated in DR document
Design Requirements (DR) Document
- It can be a constantly evolving document.
- There can be a need to modify requirements as the
project progresses and as more information is learned.
-Detail is added as the design progresses. - BUT, typically, design projects want to FREEZE the DR quite early so that the design can be progressed and finished.
Minimum inclusion for DR
Functional requirements
Performance requirements
Maintenance/Layout requirements
Operating environment requirements
Human Factors requirements (User requirements)
Steps of typical procurement process
- Prepare Engineering Quotation Request (EQR)
- Evaluation of bids
- Selection
Selection
Should define acceptance criteria (not just cost)
Prepare Engineering Quotation Request (EQR)
Includes
-Technical Specification
-Required documentation (drawings, manuals)
-Training requirements
Evaluation of bids
Evaluate product
Accept/reject exception
why are HF issues often viewed as difficult to incorporate into requirements?
HF issues often viewed as difficult to incorporate into requirements/ specifications and assessments because they are considered difficult to specify and measure consistently (“soft” requirements)