mirror of
https://github.com/amyjko/cooperative-software-development
synced 2024-12-26 21:58:27 +01:00
remove 'a'
This commit is contained in:
parent
76d1a6884b
commit
3f7a140d88
1 changed files with 1 additions and 1 deletions
|
@ -4,7 +4,7 @@ As you've probably noticed by now, this type of process doesn't really scale, ev
|
||||||
|
|
||||||
The techniques we've discussed so far for avoiding this boil down to _specifying_ what code should do, so everyone can write code according to a plan. We've talked about [requirements specifications|requirements], which are declarations of what software must do from a users' perspective. We've also talked about [architectural specifications|architecture], which are high-level declarations of how code will be organized, encapsulated, and coordinated. At the lowest level are *functional specifications*, which are declarations about the _properties of input and output of functions in a program_.
|
The techniques we've discussed so far for avoiding this boil down to _specifying_ what code should do, so everyone can write code according to a plan. We've talked about [requirements specifications|requirements], which are declarations of what software must do from a users' perspective. We've also talked about [architectural specifications|architecture], which are high-level declarations of how code will be organized, encapsulated, and coordinated. At the lowest level are *functional specifications*, which are declarations about the _properties of input and output of functions in a program_.
|
||||||
|
|
||||||
In their simplest form, a functional specification can be a just some natural language that says what an individual function is supposed to do:
|
In their simplest form, a functional specification can be just some natural language that says what an individual function is supposed to do:
|
||||||
|
|
||||||
`javascript
|
`javascript
|
||||||
// Return the smaller of the two numbers,
|
// Return the smaller of the two numbers,
|
||||||
|
|
Loading…
Reference in a new issue