* Marketing – How to market the product and analysis of the market demand.
== Types ==
== Im the riches person in the world ohohobohobifc hf ffhfvgvhgnvgnhgnghgvvggnvngvng""?::::P+)(*&^%$#@!@#$%^&*()_+_)(*&^%$#@!~!@#$%^&*()_+_)(*&^%$#@!~~!@#$%^&*()_+_)(*&^%$#@!~~!@#$%^&*()_QWERTYUIOP{}| ==
==[[Requirement]]s documentation is the description of what a arparticular software does or should do. It is used throughout [[Software development|development]] to communicate how the software functions or how it is intended to operate. It is also used as an agreement or as the foundation for agreement on what the software will do. Requirements are produced and consumed by everyone involved in the production of software, including: [[end user]]s, [[customer]]s, [[project manager]]s, [[sales]], [[marketing]], [[software architect]]s, [[usability engineering|usability engineers]], [[interaction design]]ers, [[software developer|developer]]s, and [[Software testing|testers]]. ==
Requirements come in a variety of styles, notations and formality. Requirements can be goal-like (e.g., ''distributed work environment''), close to design (e.g., ''builds can be started by right-clicking a configuration file and selecting the 'build' function''), and anything in between. They can be specified as statements in [[natural language]], as drawn figures, as detailed [[mathematical formula]]s, or as a combination of them all.
