Revision as of 04:28, 6 June 2023 edit 67.198.37.16 (talk) →Software architecture: Remove EMACS example. It's OR. It's not even close to reality, as discussed on LambdaTheUltimate ← Previous edit		Revision as of 04:29, 6 June 2023 edit undo 67.198.37.16 (talk) →Software architecture: Remove misleading statement about OOP Next edit →
Line 42: {{main\|Structure chart}} {{weasel section\|date=September 2019}} Functional Decomposition is a design method intending to produce a non-implementation, architectural description of a computer program. ~~Rather than conjecturing Objects and adding methods to them ([[Object-oriented programming\|OOP]]), with each Object intending to capture some service of the program, the~~The software architect first establishes a series of functions and types that accomplishes the main processing problem of the computer program, decomposes each to reveal common functions and types, and finally derives Modules from this activity. ===Signal processing===

Functional decomposition: Difference between revisions