Process specification

<h2 id="use-in-systems-development">Use in systems development</h2>
<p>The process specification defines what must be done to transform inputs into outputs. It is a detailed set of instructions outlining a business procedure that each elementary level business activity is expected to carry out. Process specifications are commonly included as integral components of requirements documents in systems development. 
</p>
<h2 id="techniques">Techniques</h2>
<p>A variety of approaches can be used to produce a process specification, including:
</p>
<ul><li><a href="/facts/Decision_tables/KbWcbltC">Decision tables</a></li>
<li>Structured English (favored technique of most systems analysts)</li>
<li>Pre/post conditions</li>
<li><a href="/facts/Use_cases/8pNHjsIr">Use cases</a>, basic course or events/alternate paths in <a href="/facts/Use_cases/8pNHjsIr">use cases</a></li>
<li><a href="/facts/Flowcharts/BtNXBfUG">Flowcharts</a></li>
<li><a href="/facts/Nassi%E2%80%93Shneiderman_diagram/zqzSRRM6">Nassi–Shneiderman diagrams</a></li>
<li><a href="/facts/Unified_Modeling_Language/3tlNS0tH">UML</a> <a href="/facts/Activity_diagram/GTb2xMln">Activity diagrams</a></li></ul>
<p>No matter what approach is used, a specification must communicate to system development designers, implementers and support professionals, and be verifiable by stakeholders and end users.
</p>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Specification_(technical_standard)/xEMUsktp">Specification (technical standard)</a></li></ul>
<h2 id="external-links">External links</h2>
<ul><li><a href="https://web.archive.org/web/20151205091250/http://www.yourdon.com/strucanalysis/wiki/index.php/Chapter_11">Chapter 11</a> of the <a href="https://web.archive.org/web/20151208030959/http://www.yourdon.com/strucanalysis/wiki/index.php?title=Introduction">Structured Analysis Wiki</a>, by <a href="/facts/Ed_Yourdon/W8GpbN3n">Ed Yourdon</a></li></ul>

Process specification open-in-new

Process specification