NOTICE: Due to a lapse in annual appropriations, most of this website is not being updated. Learn more.
Form submissions will still be accepted but will not receive responses at this time. Sections of this site for programs using non-appropriated funds (such as NVLAP) or those that are excepted from the shutdown (such as CHIPS and NVD) will continue to be updated.
An official website of the United States government
Here’s how you know
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock (
) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.
Inputs and outputs are ubiquitous in flow modeling, including popular programming languages. This paper examines how inputs and outputs can be formalized in the Process Specification Language (PSL) to reduce ambiguity and increase expressiveness compared to conventional flow modeling representations. Inputs and outputs are shown to be early design stage notions independent of existing PSL concepts, preconditions and postconditions in particular. The paper defines axioms for input and output, and constraints on existing PSL concepts. Some of these relate early and late stage design, while others provide for multiple views of inputs and outputs. It also identifies which aspects of input are metatheoretic and consequently outside the scope of PSL.
control and data flow, inputs and outputs, ISO, process model, UML 2
Citation
Bock, C.
and Gruninger, M.
(2004),
Inputs and Outputs in PSL, NIST Interagency/Internal Report (NISTIR), National Institute of Standards and Technology, Gaithersburg, MD, [online], https://doi.org/10.6028/NIST.IR.7152, https://tsapps.nist.gov/publication/get_pdf.cfm?pub_id=822179
(Accessed October 15, 2025)