mirror of
https://github.com/amyjko/cooperative-software-development
synced 2024-12-26 21:58:27 +01:00
Updated name.
This commit is contained in:
parent
84f328cda0
commit
c2ae64d4a8
1 changed files with 1 additions and 1 deletions
|
@ -25,7 +25,7 @@
|
||||||
<small>Credit: Creative Commons 0</small>
|
<small>Credit: Creative Commons 0</small>
|
||||||
|
|
||||||
<h1>Architecture</h1>
|
<h1>Architecture</h1>
|
||||||
<div class="lead">Andrew J. Ko</div>
|
<div class="lead">Amy J. Ko</div>
|
||||||
|
|
||||||
<p>Once you have a sense of what your design must do (in the form of requirements or other less formal specifications), the next big problem is one of organization. How will you order all of the different data, algorithms, and control implied by your requirements? With a small program of a few hundred lines, you can get away without much organization, but as programs scale, they quickly become impossible to manage alone, let alone with multiple developers. Much of this challenge occurs because requirements <em>change</em>, and every time they do, code has to change to accommodate. The more code there is and the more entangled it is, the harder it is to change and more likely you are to break things.</p>
|
<p>Once you have a sense of what your design must do (in the form of requirements or other less formal specifications), the next big problem is one of organization. How will you order all of the different data, algorithms, and control implied by your requirements? With a small program of a few hundred lines, you can get away without much organization, but as programs scale, they quickly become impossible to manage alone, let alone with multiple developers. Much of this challenge occurs because requirements <em>change</em>, and every time they do, code has to change to accommodate. The more code there is and the more entangled it is, the harder it is to change and more likely you are to break things.</p>
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue