![]() |
Systems Engineering Glossary |
||||||||||||||||||||||||||||
|
U
Other |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
|
Use Cases. Use cases and user scenarios are very useful because users often find it easiest to describe their view of the system in terms of examples and illustrations of how it might be used and how users will interact with it. User. The user can be an enterprise, an organisation, a group of individuals, or an individual that makes use of the system products once fielded. User Requirements Document (URD). The User Requirement Document contains the requirements from the stakeholders particularly the users (operators, maintainers, trainers, marketers, etc). Utilisation Phase. The Acquisition Phase ends with acceptance testing (Formal Qualification Review) after which the system is introduced into service and the Utilisation Phase begins.
If you wish to suggest related words or phrases for our glossaries, please contact Argos Press. © Argos Press Pty Ltd, Canberra, 2003-2004. All rights reserved. Please contact Argos Press Pty Ltd to request permission to reproduce, broadcast, adapt and communicate content from this web site (including this glossary entry on Systems Engineering). Our other resources include Antennas, Appliances, Broadband Internet, CDMA, Communications Systems, GSM, Modems, Project Management, Radar, Risk Management and Decision Making, Satellite Communications, SMS, Speakers, Systems Engineering, Team Building, Time Management, Transmitters and Receivers, and XML. |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||