Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Requirements analysis
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
===Customer requirements=== Statements of fact and assumptions that define the expectations of the system in terms of mission objectives, environment, constraints, and measures of effectiveness and suitability (MOE/MOS). The customers are those that perform the eight primary functions of systems engineering, with special emphasis on the operator as the key customer. Operational requirements will define the basic need and, at a minimum, answer the questions posed in the following listing:<ref name="SEF01"/> *''Operational distribution or deployment'': Where will the system be used? *''Mission profile or scenario'': How will the system accomplish its mission objective? *''Performance and related parameters'': What are the critical system parameters to accomplish the mission? *''Utilization environments'': How are the various system components to be used? *''Effectiveness requirements'': How effective or efficient must the system be in performing its mission? *''Operational life cycle'': How long will the system be in use by the user? *''Environment'': What environments will the system be expected to operate in an effective manner?
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)