1. A good requirement DOES NOT specify A. Functions (what the artefact does) B. States and modes (sets of conditions and functional groups) C. Performance (how well a function is performed) D. External interfaces (the required characteristics at a point in the system where it interacts with the world or next higher assembly) E. Performance equivalent to a particular set of hardware or software

2. A Functional requirement A. Must include an action and an object of action B. States how well a function should be performed C. Specifies everything that will enter or leave the system D. Includes constraints on the effect of the system on its external environment E. Includes resource requirements state limits on consumption or use of externally provided resources

3. Which of these statements DOES NOT apply to the reliability of a system design? A. Reliability is not something that can be easily added to a design after it is complete B. Is about managing the dependability of an artefact in the design phase C. Deals with the estimation, prevention and management of high levels of lifetime engineering uncertainty and risks of failure. D. Dependability is the ability of an artefact or system to function under stated conditions for a specified time. E. Every design should be dependable and is the sole responsibility of a design engineer

4. The following is NOT a characteristic of a good systems engineer A. Diverse technical skills B. Self -confidence and arrogance C. Comfortable with uncertainty D. Comfortable with change E. Ability to make system-wide connections