Poor
design costs money in terms of maintenance and enhancement
lead times. Not only does poor design consume resources but
it also leaves you with dissatisfied and confused customers.
Software engineering has traditionally been associated with
process models that say very little about how you go about
building quality into your design. This has changed recently
with the advent of agile approaches such as eXtreme Programming
(XP) that focus on the concepts, principles, patterns and
techniques that underpin quality designs.
How do experienced OO developers cope with the complexity
inherent in software design? They do the simplest thing possible
to solve a problem, plus …
-
Apply design patterns where appropriate.
- Continuously look for weak spots in the design in order
to refactor them out.
- Say “what”, before they say “how”,
i.e. Write tests before they write solutions.
Who
should attend? |
Developers
who wish to improve their OO design skills and who already
have development experience using Java and UML.
Although
this course is taught using Java, its content applies
equally well to .NET projects.
back
to top>>
|
|