Re: [AM] Unfounded assertion
Hubert Matthews <[email protected]>
| Newsgroups | gmane.comp.programming.modeling.agile |
|---|---|
| Organization | Oxyware Ltd |
| Message-ID | <[email protected]> |
Jason Gorman wrote: > But new requirements can't be handled by refactoring, surely? If you have new requirements > then aren't you changing the behaviour of the system? Refactoring requires you to preserve > requirements at that moment in time, surely. Refactoring is isofunctional - agreed. My view is that it should be done both before changing the system so the new functionality is easier to add, and afterwards (to a lesser extent) to tidy up once a correct solution approach has been found. The reason for the "lesser extent" comment for post-change refactoring is because it is easy to keep fiddling with the code without any obvious ending criteria. -- Hubert Matthews http://www.oxyware.com/ Software Consultant [email protected] For more information about AM, visit the Agile Modeling Home Page at www.agilemodeling.com --^---------------------------------------------------------------- This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrKDA.bWnbtk.Z2NtYS1h Or send an email to: [email protected] TOPICA - Start your own email discussion group. FREE! http://www.topica.com/partner/tag02/create/index2.html --^----------------------------------------------------------------