Re: [agileDatabases] Agile Methods, Universities and Misc Thoughts
- From: "James McGovern"
Sent: Friday, February 06, 2004 6:55 AM
Subject: [agileDatabases] Agile Methods, Universities and Misc Thoughts
> Academia is really good about teaching heavyweight methods. Any thoughtson
> what it takes to get a university to teach agile methods as part of a CS,SE
> program?Do you mean besides a hefty bribe (err... I meant alumni contribution,
of course)? [grin - I think]
There are a number of academics that are doing it with a fair degree
of success. Ralph Johnson at UIUC comes immediately to mind, as
does Rick Mugridge in New Zealand.
At the risk of misrepresenting Ralph's position, I remember
him stating that he gets much better success in doing a one
semester course in XP before a one semester course in RUP,
both courses focused on actually building a system (not just
text and lecture.) The reason is that at the undergraduate
level the students don't have any significant design skills, so
the design, build, debug cycle of standard software engineering
leaves them lost at the starting gate, and they can end the
semester without anything completed on the project, while
with XP they will have a working (although incomplete)
My own position is that I would much rather take the
first programming course and teach TDD and simple
design, with refactoring in the strict sense as a follow-on.
I think it might go rather well with one simple project per
week where the student has the customer tests defined for
the project up front, and the unit tests are part of the
work to turn in.
> James McGovern
> Co-author of bestselling book: Practical Guide to Enterprise Architecture
- I know this is a little late in the day... But I have only just found
this forum :P
>>In light of that, what should I make of a highly normalized databaseAs pointed out by the above text, it should be quite possible to stick
>>table structure that is organized more according to what role the data
>>plays than grouped in an object-like manner?
>My experience is that a highly normalized DB schema often maps very
>to the data aspects of a well-designed object model.
to a one object/table design as long as your object model is fine
If you need to work remotely with the info in your objects (reducing
calls etc) consider mapping parts of the object graph into data
transfer objects and using a service layer.