Software Engineering

189
11.2 
Behavioral analysis
3. 
No further decomposition is necessary when a function’s design solution can be 
comprehended or exists as a reusable software module.
4. 
Functions that involve several data transformation steps may not require further 
decomposition if the design solution is considered manageable.
5. 
If a function involves data transformation steps that are common with other 
functions, then decomposing the function represents an opportunity for estab-
lishing common subroutines that can reduce software complexity by eliminating 
duplication.
6. 
Avoid identifying a function that generates more than one output or product. 
With some deliberation it should be possible to identify an abstract function 
which can then be decomposed into subfunctions which generate alternative 
outputs or products.