Hola...recien entre al grupo ..
Estoy interesada en revisar material sobre la metodologia MIDAS
(MIDAS/db)...el material que hasta ahora encuentro en la WEB no me
es muy util porque no me indica con claridad como manejar la
metodologia...
Alguien puede ayudarme con algun link ??
Gracias mil !!

Elsa, debes recorder que la lista de distribucion es en ingles, no postees
en castellano.
Suerte
Below the translation for the original message.

Hi, I'm new in the group.
I'm interested in reading something about MIDAS (MIDAS/db) technology... the
material I've found so far in the web it's not very useful because it does
not explains how to handle the method.
Can anybody help me with a link?
Thank you very much.


-----Original Message-----
From: elsaherrera2003 [mailto:elsaherrera2003@...]
Sent: Saturday, October 04, 2003 00:50
To: agileDatabases@yahoogroups.com
Subject: [agileDatabases] Ayuda

Hola...recien entre al grupo ..
Estoy interesada en revisar material sobre la metodologia MIDAS
(MIDAS/db)...el material que hasta ahora encuentro en la WEB no me
es muy util porque no me indica con claridad como manejar la
metodologia...
Alguien puede ayudarme con algun link ??
Gracias mil !!



To unsubscribe from this group, send an email to:
agileDatabases-unsubscribe@yahoogroups.com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

Below is the official press announcement for Software Development's annual
Jolt awards (I'm a contributing editor with the magazine).

If you happen to think that a product that you use that was released this
year, or a book published this year, is exceptionally noteworthy then you
may want to suggest to the producer/publisher that they nominate it.

- Scott

====================================================

Software Development Magazine Opens Nominations for the 14th Annual Jolt
Product Excellence Awards



14 categories to honor those who have joltedthe industry




San Francisco, October 8, 2003 - Software Developments editors today
announced that nominations for the 14th Annual Software Development Jolt
Product Excellence Awards are now open.  Each year Software Development
partners with Jolt Cola to acknowledge those products, books and
technologies that joltthe industry with their significance.  The 2004 Jolt
Award winners will be announced at a gala ceremony on March 17, 2004 at the
Software Development Conference & Expo West at the Santa Clara Convention
Center. Winners will also be featured in the June 2004 issue of Software
Development.


Last year over 200 nominations for books, tools, technologies and web sites
were submitted for the coveted trophies and this years competition promises
to be just as exciting.  Its always fascinating to see what nominations pop
up from beneath our radar. We do product reviews throughout the year, but
this is a chance for our judges to survey the field in a broad way while
remaining free from vendor biasand thats increasingly rare these days,said
Editor in Chief Alexandra Weber Morales.



The categories are:

·               Books: Practical/General Developer Interest

·               Books: Technical

·               Business Integration and Data Tools

·               Change and Configuration Management

·               Design and Analysis Tools

·               Languages and Development Environments

·               Libraries, Frameworks and Components

·               Mobile Development Tools

·               Project Management Tools

·               Security Tools

·               Testing Tools

·               Utilities

·               Web Development Tools

·               Websites and Developer Networks



Nominations should be submitted online at -
https://www.sdmediagroup.com/view/jolt/jolt01.jsp


Deadline for nominations is December 15, 2003. The nomination fee is $150.
Nominations received prior to November 15, 2003 will receive an early bird
discount of $50. Nonprofit makers of open source products may waive their
nomination fee.


More information on the Jolt Product Excellence and Productivity Awards is
available at <http://www.sdmagazine.com>www.sdmagazine.com




About Software Development magazine

Software Development is the leading magazine for software development
managers. It is the definitive source to empower those who implement and
manage teams, technologies, practices and tools integral to successful
development projects. Software Development is a monthly publication
reaching 100,840 subscribers. Software Development readers, who average
more than 12 years' experience in the field, are trailblazing managers who
care passionately about enlivening and expediting the task of delivering
successful software on time and under budget.

Software Development magazine is part of CMP Media LLC's Software
Development Media Group, which also publishes Dr. Dobb's Journal, MSDN
magazine, C/C++ Users Journal, Windows Developer's Magazine, Byte and
SysAdmin; holds the semiannual Software Development Conference and
Exposition; and produces 15 Web sites. The Software Development Media Group
reaches the largest, most influential audience of software developers and
business solution providers available through a single media company.






About CMP Media LLC

CMP Media LLC (www.cmp.com) is a leading integrated media company providing
essential information and marketing services to the entire technology
spectrumthe builders, sellers and users of technology worldwide.
Capitalizing on its editorial strength, CMP is uniquely positioned to offer
marketers comprehensive, integrated media solutions tailored to meet their
individual needs.  Its diverse products and services include newspapers,
magazines, Internet products, research, direct marketing services,
education and training, trade shows and conferences, and custom publishing.


====================================================
Scott W. Ambler
Senior Consultant, Ronin International, Inc.
www.ronin-intl.com/company/scottAmbler.html

www.agiledata.org
www.agilemodeling.com
www.ambysoft.com
www.enterpriseunifiedprocess.info
www.modelingstyle.info
www.ronin-intl.com

My new book Agile Database Techniques
(www.ambysoft.com/agileDatabaseTechniques.html) is now available (Amazon
still has it listed as a pre-order, but it is in fact shipping).

The book is interesting for several reasons:
1. It makes the case that data professionals and developers need to find
ways to work together effectively.
2. It provides an overview of the basic skills that each group needs to
understand the other one.  Because I feel that developers should understand
the basics of data modeling and data normalization and that data
professionals understand object-orientation and the UML I include chapters
on each topic.  These chapters just provide the basics, you won't become an
expert by reading them but you will gain an appreciation for the topic and
be pointed to other good resources to help you to extend your knowledge if
you so desire.
3. It makes an argument for evolutionary (iterative and incremental
development), showing that one approach (e.g. objects) doesn't necessary
drive the other approach (e.g. data), or vice versa, but instead you must
evolve both views in parallel.
4. It provides detailed descriptions of evolutionary database techniques,
including database refactoring, Agile Model Driven Development (AMDD),
evolutionary performance tuning, O/R mapping, and test-driven development
(TDD) among others.  It is possible, and in fact very desirable, to take an
evolutionary approach to data-oriented development.
5. It provides detailed descriptions of a variety of strategies for
addressing common development issues such as concurrency control,
referential integrity, security access control, and reporting (among
many).  The bottom line is that these issues are critical to your success,
you have options when implementing each one, and that they invariably are
cross platform (e.g. object and data) issues and not just database issues
as many traditional developers may believe.
6. It describes the fundamental skills required for DBAs to work in an
agile manner, something that I think most people would want to have on
their resume.  Similarly it describes fundamental skills required for
developers to work effectively with agile DBAs.

In short, I think that this book pretty much defines how data professionals
can become effective and productive members on agile software development
teams -- a critical issue that has been mostly ignored until now.   My hope
is that you'll find Agile Database Techniques to be of interest.

- Scott
PS -- Please pass this announcement on to your colleagues if you think it's
appropriate.

====================================================
Scott W. Ambler
Senior Consultant, Ronin International, Inc.
www.ronin-intl.com/company/scottAmbler.html

www.agiledata.org
www.agilemodeling.com
www.ambysoft.com
www.enterpriseunifiedprocess.info
www.modelingstyle.info
www.ronin-intl.com

Try here...

http://info.borland.com/midas/papers/

Emlyn

> -----Original Message-----
> From: Adrian Gonzalez Alonso
> [mailto:adrian_gonzalez_alonso@...]
> Sent: Tuesday, October 07, 2003 7:13 PM
> To: agileDatabases@yahoogroups.com
> Cc: elsaherrera2003@...
> Subject: RE: [agileDatabases] Ayuda - Translation
>
>
> Elsa, debes recorder que la lista de distribucion es en
> ingles, no postees
> en castellano.
> Suerte
> Below the translation for the original message.
>
> Hi, I'm new in the group.
> I'm interested in reading something about MIDAS (MIDAS/db)
> technology... the
> material I've found so far in the web it's not very useful
> because it does
> not explains how to handle the method.
> Can anybody help me with a link?
> Thank you very much.
>
>
> -----Original Message-----
> From: elsaherrera2003 [mailto:elsaherrera2003@...]
> Sent: Saturday, October 04, 2003 00:50
> To: agileDatabases@yahoogroups.com
> Subject: [agileDatabases] Ayuda
>
> Hola...recien entre al grupo ..
> Estoy interesada en revisar material sobre la metodologia MIDAS
> (MIDAS/db)...el material que hasta ahora encuentro en la WEB no me
> es muy util porque no me indica con claridad como manejar la
> metodologia...
> Alguien puede ayudarme con algun link ??
> Gracias mil !!
>
>
>
> To unsubscribe from this group, send an email to:
> agileDatabases-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>
>
>
> ------------------------ Yahoo! Groups Sponsor
> ---------------------~-->
> Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark
> Printer at MyInks.com. Free s/h on orders $50 or more to the
> US & Canada.
> http://www.c1tracking.com/l.asp?cid=5511
> http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/z3wwlB/TM
> --------------------------------------------------------------
> -------~->
>
> To unsubscribe from this group, send an email to:
> agileDatabases-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>

If you are interested in becoming a reviewer of manuscripts in
progress by industry thought leaders, a new Yahoo Group has been
created: http://groups.yahoo.com/group/computerbookreviewers.

While their is no monetary compensation, the authors will provide you
with your name acknowledged in print and a copy of the book when it is
released.

Authors are currently seeking feedback on the following topics:

Enterprise Architecture
Web Services
PHP
Service-Oriented Architectures
Agile Methodologies
Oracle 10G
Project Management

James McGovern
Co-author of the Amazon Top 100 book: The Practical Guide to Architecture
http://www.amazon.com/exec/obidos/tg/detail/-/0131412752/

On November 14 2003 I'll be giving a talk entitled "Agile Database
Techniques: Data Doesn't Have to be a Four-Letter Word Anymore" in
Philadephia at the DAMA meeting held at Towers Perrin (1500 Market
St).  The meeting itself is an all day event, my presentation is in the
afternoon from 1 until 3:15.


DAMA Philadelphia/Delaware Valley:
<http://www.dama-phila.org/>http://www.dama-phila.org/


Talk Description:
Agile Database Techniques: Data Doesnt Have To Be A Four-Letter Word Anymore
Data is clearly an important aspect of software-based systems, a fact that
the information technology (IT) industry has understood for decades, yet
many agile development teams are struggling to involve data professionals
within their projects.  The goal of the Agile Data (AD) methodology
(www.agiledata.org) is to define strategies for data-oriented activities
within agile projects, to define ways that application developers and data
professionals can work together effectively.

This presentation will explore:
- The 6 philosophies of the AD method
- The four AD roles
- Challenges we need to overcome
- Techniques for agile database development

Hope to see you there.

- Scott

====================================================
Scott W. Ambler
Senior Consultant, Ronin International, Inc.
www.ronin-intl.com/company/scottAmbler.html

www.agiledata.org
www.agilemodeling.com
www.ambysoft.com
www.enterpriseunifiedprocess.info
www.modelingstyle.info
www.ronin-intl.com

The CFP is posted at
http://www.agiledevelopmentconference.com/callpapers.html for anyone
interested in submitting a paper.

- Scott

====================================================
Scott W. Ambler
Senior Consultant, Ronin International, Inc.
www.ronin-intl.com/company/scottAmbler.html

www.agiledata.org
www.agilemodeling.com
www.ambysoft.com
www.enterpriseunifiedprocess.info
www.modelingstyle.info
www.ronin-intl.com

Dear colleagues,

We would like to thank everyone who took time to complete the
Employee Satisfaction in Agile Teams survey. For those of you who
have not had a chance to take the survey, we want to remind you that
it is still available at
http://www.agilenetwork.ca/study/

It should not take more than 15 minutes to complete. All responses
are anonymous. All aggregate results and analysis will published and
made available to this list and the public.


Regards,

Grigori Melnik/Frank Maurer
University of Calgary

I just updated www.agiledata.org/essays/umlDataModelingProfile.html to
include style issue discussions for many of the stereotypes.  I how that
this will help to clear up why some things are optional whereas others are not.

Also, any feedback you may have to help improve the profile would be
appreciated.

- Scott

====================================================
Scott W. Ambler
Senior Consultant, Ronin International, Inc.
www.ronin-intl.com/company/scottAmbler.html

www.agiledata.org
www.agilemodeling.com
www.ambysoft.com
www.enterpriseunifiedprocess.info
www.modelingstyle.info
www.ronin-intl.com

The Experience Framework Repository for Agile Methodologies is now
online.

Contribute to it by adding your experience in Agile Methodologies.

This will lead to a better understanding of the effects of Agile
Methodologies for everyone benefits!!

The URL is: http://caseserver.unibz.it:8080/name/

The manual for using it is at URL:

http://name.case.unibz.it/General/FormsMaterial/ExperienceFramework/in
dex.html

The Experience Framework Repository for Agile Methodologies is the
final outcome of the NAME project (Network for Agile Methodologies
Experience) funded by the European Community in the 5th Framework
Program. For more information, visit http://name.case.unibz.it

Have fun,

Giancarlo


 

Giancarlo Succi, PhD, PEng
Professor and Director
Center for Applied Software Engineering
Faculty of Computer Science
Free University of Bozen
Dominikanerplatz 3 Piazza Domenicani
I-39100 Bozen, Italy
ph: +39(0471)315-640 - fax: +39(0471)315-649
e-mail: Giancarlo.Succi@...

Hi all,

Currently Involved in Research Analysis process in identifying the

1) Demerits of choosing the Software Architecture First and then choosing
the Technology for the particular Business Requirement solution.

2)Demerits of the choosing the Technology first and then choosing the
Software Architecture second for Business Requirement solution.

I would like to get help from peoples like u. in achieving this particular .

Please provide me your suggestions and also provide me this the resource
locator where can I get more informations  regarding this particular topics.

Please provide me information where could i find case studies regarding
this particular topics.

thanks

regards,

krthekeyan.s

http://www.agiledata.org/essays/vision.html#Philosophies is a good starting
point IMHO.

- Scott


At 10:22 PM 11/25/2003 -0800, you wrote:
>Hi guys,
>I'm a total newbie as far as agile databases go. Can someone like gimme a
>quick run down and distill the philosophy behind them for me in like 1 e-mail?
>
>Oh, and does anybody know a good site or some good literature that I can
>peruse 2 get clued up on the whole object database scenario?
>
>Hungry 4 knowledge,
>David
>
>
>2365d1.jpg
>
>To unsubscribe from this group, send an email to:
>agileDatabases-unsubscribe@yahoogroups.com
>
>
>
>Your use of Yahoo! Groups is subject to the
><http://docs.yahoo.com/info/terms/>Yahoo! Terms of Service.

====================================================
Scott W. Ambler
Senior Consultant, Ronin International, Inc.
www.ronin-intl.com/company/scottAmbler.html

www.agiledata.org
www.agilemodeling.com
www.ambysoft.com
www.enterpriseunifiedprocess.info
www.modelingstyle.info
www.ronin-intl.com

Over the last 2 months many people took time to respond to the
survey regarding their views on various job satisfaction factors
(whether you are part of an agile team or not). Thanks for your
participation.

If you haven't had a chance to post your answers yet, please do it
now at
http://www.agilenetwork.ca/study/

The survey will close for data collection on November 29, 2003.

Regards,

Grigori


--- In agileDatabases@yahoogroups.com, "Grigori Melnik"
<grigori.melnik@s...> wrote:
> Dear colleagues,
>
> We would like to thank everyone who took time to complete the
> Employee Satisfaction in Agile Teams survey. For those of you who
> have not had a chance to take the survey, we want to remind you
that
> it is still available at
> http://www.agilenetwork.ca/study/
>
> It should not take more than 15 minutes to complete. All responses
> are anonymous. All aggregate results and analysis will published
and
> made available to this list and the public.
>
>
> Regards,
>
> Grigori Melnik/Frank Maurer
> University of Calgary

David.

look at the links section of the group

http://groups.yahoo.com/group/agileDatabases/links

-Pramod
--- In agileDatabases@yahoogroups.com, David Mukaiwa <dmukaiwa@y...>
wrote:
> Hi guys,
> I'm a total newbie as far as agile databases go. Can someone like
gimme a quick run down and distill the philosophy behind them for me
in like 1 e-mail?
>
> Oh, and does anybody know a good site or some good literature that I
can peruse 2 get clued up on the whole object database scenario?
>
> Hungry 4 knowledge,
> David
>
>
> ---------------------------------
> Do you Yahoo!?
> Protect your identity with Yahoo! Mail AddressGuard

XP Agile Universe 2004: CALL FOR CONTRIBUTIONS

Calgary, Alberta, Canada
August 15 - 18, 2004

www.xpuniverse.com

The Role of Extreme Programming and Agile Methods as Mainstream Software
Development Techniques


  main·stream:   (P)  Pronunciation Key  (mnstrm) n.   The prevailing current
of thought, influence, or activity.

What does it mean for Extreme Programming and other Agile Methods to be
mainstream software development techniques? What does it take to move them
to a level of acceptance that well transcends the current contexts.
Following the success of the previous three conferences, XP/Agile Universe
2004 will continue to transform the prevalent thinking in the software
development community, targeting both advocates and skeptics, through
learning, experiencing, and sharing. To that end, we are soliciting
proposals and papers in several categories. Topics of interest include, but
are not limited to:

Bang for the Buck

  Return on Investment
  Management of Agile Projects
  Measurement in Agile Projects
  Agility and Risk Management
  Agile Testing and Quality Assurance
  Contracting in Agile Projects
  Empirical Results and Validation

Getting and Maintaining Agility

  Cultural and Organizational Issues
  Scalability of Agile Methods
  Teamwork and Collaboration
  Customer Involvement
  Knowledge Management
  Adoption, Education, and Training
  Tool Support
  Issues of Frequent Deployment
  Offshore/Distributed Development

The Bread and Butter

  Testing Techniques and Practices
  Refactoring
  Pair Programming
  Writing User Stories
  Planning Projects
  Managing Requirements

New Horizons

  New Agile Methods and Practices
  Agile Modeling and Design
  Balancing Agility and Planning
  Hybrid Methods
  Widely Dispersed Agile Teams
  Open Source and Agility

IMPORTANT DATES

January 25, 2004 11:59pm EST - Submission deadline for workshop and tutorial
proposals

February 27, 2004 - Notification of acceptance for workshop and tutorial
proposals

February 29, 2004 11:59pm EST - Submission deadline for all papers
(including education symposium papers) and all proposals except workshops
and tutorials

March 7, 2004 11:59pm EST - Tutorial and workshop descriptions due for
advance program

April 2, 2004 - Notification of acceptance for all papers and all
outstanding proposals

May 2, 2004 11:59pm EST - Camera-ready copies due for all papers

Further Information: www.xpuniverse.com

Fifth International Conference on
                   eXtreme Programming and Agile Processes
                         in Software Engineering

                                   XP2004

              June 6-10, 2004, Garmisch-Partenkirchen, Germany

http://www.xp2004.org/

General Chair : Martin Fowler, ThoughtWorks, USA
Program Chair : Jutta Eckstein, Objects in Action, Germany
Academic Chair: Hubert Baumeister, Ludwig-Maximilians-Universität
München, Germany

Location
--------

Garmisch-Partenkirchen is situated 90 km from Munich at the base of
the Wetterstein mountains and is one of the most favoured tourist
centres in Germany. The Wetterstein mountains include the Zugspitze,
with 2964 m the highest mountain in Germany. Neuschwanstein, the
fairy-tale castle of King Ludwig II, is only 60 kilometres away.

In 1968 the legendary Nato Software Engineering Conference was held
in Garmisch-Partenkirchen, where for the first time the term software
engineering was used.

Call for Papers
---------------
Program Chair: Jutta Eckstein

The "Fifth International Conference on eXtreme Programming and Agile
Processes in Software Engineering" is a unique forum for industry and
academic professionals to discuss their needs and ideas for
incorporating eXtreme Programming and agile methodologies into their
professional life under consideration of the human factor.

We will celebrate this year's conference by reflecting on what we have
achieved in the last half decade and also focus on the challenges we
are facing in the near future.

XP 2004 facilitates to swap ideas in a number of ways, including
featured talks by professionals on the cutting edge of eXtreme
Programming and agile processes, technical presentations, activity
sessions, panels, posters, code camps, workshops, tutorials, and other
opportunities to exchange and elaborate on new findings. XP 2004
features additionally a PhD Symposium for PhD students, and an
Educational Symposium for everybody with a vested interest in training
and education.

Conference Topics
-----------------

The conference will stress practical applications and implications of
XP and other agile methodologies (AM). Conference topics include, but
are not limited to:

* Foundations and rationale of XP and AM
* Case studies, experiments and practioner's reports
* XP, AM, and "Lean Management"
* Organizational change
* Other management and organizational issues
* Scalability issues
* Education and training
* Introducing XP and AM into an organization
* New insights into XP practices and their interrelations
* Refactoring and continuous integration
* XP, AM, and process/product certifications (CMM, ISO 9001, ...)
* Unit and acceptance testing: practices and experiences
* Use of software development tools and environments
* Merging of agile processes

Instructions for Authors
------------------------

The conference proceedings will be published by Springer in the
Lecture Notes in Computer Science series. Papers must be original and
not under consideration for publication elsewhere. Authors must
clearly explain the contribution of their work in terms of its
theoretical and/or practical value and relationship to previous
work. Submissions must be full papers of at most 9 pages or extended
abstracts of at most 4 pages in English using the Springer LNCS
style. PhD symposium submissions are limited to one page. Each
submission must include an abstract and a list of keywords. Panel
proposals must include the moderator's name, an abstract, and the list
of panelists that have consented to participate. Accepted papers and
panel positions will appear in the conference proceedings. All
submissions should be submitted electronically in Postscript or PDF
format to Jutta Eckstein: program_chair@....

Important Dates
---------------

Deadline for submissions: January 11, 2004
Acceptance notification:  February 28, 2004
All final manuscripts:    March 28, 2004
Pre-registration ends:    April 1, 2004

Recfactor our Writings
----------------------

Getting folks writing papers about useful information is
good. However, a forest of ideas with no organization is bad. We would
like authors and groups of authors come together to refactor older,
related papers into new, consolidated pieces of literature that
communicate comprehensive ideas on an important subject. We need to
encourage ourselves to refactor what we've written in order to produce
excellent new pieces of literature. Please contact Vera Peeters at
workshop_chair@... for further information.

Program Committee:
------------------

Ann Anderson, USA
Barbara Russo, Italy
Bernhard Rumpe, Germany
Charles Poole, USA
Daniel Karlström, Sweden
David Hussman, USA
Diana Larsen, USA
Dierk König, Switzerland
Don Wells, USA
Erich Gamma, Switzerland
Frank Westphal, Germany
Giancarlo Succi, Italy
Helen Sharp, UK
Hubert Baumeister, Germany
Jim Highsmith, USA
Joe Bergin, USA
John Favaro, Italy
José H. Canós Cerdá, Spain
Joseph Pelrine, Switzerland
Joshua Kerievsky, USA
Laurie Williams, USA
Leon Moonen, NL
Linda Rising, USA
Martin Fowler, USA
Martin Lippert, Germany
Mary Lynn Manns, USA
Mary Poppendieck, USA
Michael Hill, USA
Michele Marchesi, Italy
Mike Holcombe, UK
Nicolai Josuttis, Germany
Paul Grünbacher, Austria
Rachel Davis, UK
Rachel Reinitz, USA
Rick Mugridge, New Zealand
Ron Jeffries, USA
Scott W. Ambler, USA
Sian Hopes, UK
Steve Freeman, UK
Steven Fraser, USA
Tim Mackinnon, UK
Till Schümmer, Germany
Vera Peeters, Belgium
Ward Cunningham, USA

Call for Tutorials
------------------
Tutorial Chair: Rachel Davies

The XP2004 tutorial program provides conference participants the
opportunity to gain new insights, knowledge, and skills in topics
related to extreme Programming and Agile software
development. Participants may include software developers, managers,
teachers, researchers, and students.

Tutorials are an independent instruction on a self-contained topic of
relevance to XP and Agile software development. Therefore no
commercial or sales-oriented presentations will be accepted.

We encourage tutorial proposals that provide clear utility to
practitioners, especially innovative tutorials, which depart from
lecture style delivery, and tutorials on highly advanced topics.

Tutorials are presented in half-day (3-hour) or full-day sessions
(6-hour), primarily during the first day of the conference.

Important Dates:

     * Tutorial Submissions Deadline: January 11, 2004
     * Acceptance notification: February 28, 2004
     * Final manuscripts: March 28, 2004

Submission Guidelines for Tutorials
-----------------------------------

A tutorial proposal of up to 2 pages should include:

     * Tutorial title and one line summary
     * Abstract
     * Audience and benefits of attending
     * Content outline and process
     * Presenter resume with contact information
     * History of tutorial
     * Examples of supporting material

Submissions must be in English using the Springer LNCS style. All
submissions should be submitted electronically in Postscript or PDF
format to tutorial_chair@....

Call for Workshops
------------------
Workshop Chair: Vera Peeters

The XP2004 workshop program provides a forum for groups of
participants to exchange opinions and to enhance community knowledge
about research topics and real life applications of Agile Processes.

Workshops also provide the opportunity for representatives of a
technical community to coordinate efforts and to establish collective
plans of action.

We particularly encourage proposals for novel, highly-interactive
workshops that fall outside the conventional workshop format. The
intention is that everybody learns from the experience, the organisers
as well as the participants.

To ensure a sufficiently small group for effective interaction,
workshop organizers manage attendance based on a review of short
position papers from potential attendees.

Workshops are typically half-day (3-hour) or full-day sessions
(6-hour).

This call for participation is for workshop organizers only: a later
call will occur for workshop attendees. Each workshop must have at
least two organizers, preferably from different organizations. The
organizers will typically manage a workshop Web site and the whole
workshop participation process.

Important Dates:

     * Submissions Deadline:   January 11, 2004
     * Acceptance notification   February 28, 2004
     * Final manuscripts:   March 28, 2004

Submission Guidelines for Workshops
------------------------------------

A workshop proposal of up to 2 pages should include:

     * Workshop title and one line summary (used in advance program)
     * Abstract
     * Audience and benefits of attending
     * 0utline of the theme and goals of the workshop
     * A description of the desired number of participants, the
       participant solicitation and selection process
     * Presenter resume with contact information

Submissions must be in English using the Springer LNCS style. All
submissions should be submitted electronically in Postscript or PDF
format to workshop_chair@....

Acceptance will be based on an evaluation of the workshop's potential
for generating useful results, the timeliness and expected interest in
the topic, and the organizers' ability to lead a successful
workshop.

Call for Panels and Activities
------------------------------
Panels and Activities Co-Chairs: Steven Fraser and Joshua Kerievsky

XP2004 panels/activity-sessions will be lively, participatory,
educational, and entertaining. They offer an interactive opportunity
to share perspectives, debate opinions, and communicate
best-practices. Panels are not intended as unison gab-fests of
mini-presentations - contrasting opinions are important! Panel formats
have included: traditional; talk show; game show; fish bowl; formal
debate; and special events. A proposal must include a relevant topic,
an appealing format and participants with different points of
view. Part of the enduring appeal of XP2004 panels is to showcase the
opinions of leading researchers and industry leaders. Panelists need
not be experts - dispatches from the trenches can prove as
enlightening as the latest sound bites from the usual suspects. You
don't have to be an XP200N regular to organize a panel.

Important Dates:
     * Submissions Deadline:   January 11, 2004
     * Acceptance notification   February 28, 2004
     * Final manuscripts:   March 28, 2004

Submission Guidelines for Panels and Activities
-----------------------------------------------

Panel proposals must include:

     * Title
     * Convener/Moderator contact information with bios
     * Proposed panelists (names, bios, positions)
     * Panel value proposition (value, innovation, timeliness,
       controversy factor, appeal, history)
     * Format description (traditional panel, debate, fish-bowl, talk
       show, game show, special event)
     * Complete panel material 'camera-ready' for publication in the
       proceedings

Submissions must be in English using the Springer LNCS style. All
submissions should be submitted electronically in Postscript or PDF
format to activityandpanel_cochair@....

Call for Posters
----------------
Poster Chair: Rachel Reinitz

The poster session is an informal and highly interactive environment
that gives XP2004 attendees the opportunity to engage with one another
in discussions about relevant, ongoing work and critical issues in key
areas. Posters are ideal for presenting preliminary research results,
experience reports, late-breaking developments, or for giving an
introduction to interesting, innovative work Posters provide attendees
with a unique opportunity to make their work highly visible during the
conference.

Submissions are sought in all relevant areas of XP and Agile
Methodologies. This is a great forum that spans from sharing real-life
experiences to innovative research. Workshop organizers and/or
attendees may present posters that summarize results from one or more
XP200x workshops, thus making the results immediately and widely
available to the community. Authors of work that is presented in the
XP2004 technical program can obtain even more benefit by presenting
their work in a poster as well, since the poster session provides them
the opportunity to engage in the one-on-one discussions that are not
possible during technical sessions. PhD candidates are particularly
encouraged to submit reports describing their ongoing work, in
addition to attending the PhD symposium.

The Posters program begins with a special session at the Welcome
Reception. Poster authors are required to attend this scheduled
interactive poster session, staying with their poster so that they can
discuss their work with conference attendees. After the Welcome
Reception, the posters will be displayed where XP2004 participants can
view them at their convenience and to enable interactions on the
topics throughout the conference.

Important Dates:

     * Submissions Deadline:   January 31, 2004
     * Acceptance notification   March 15, 2004
     * Final manuscripts:   March 28, 2004

Submission Guidelines:
----------------------

A workshop proposal of up to 2 pages should include:

     * Poster title and one line summary
     * A short abstract that summarizes the content of the poster
     * a two-page extended abstract, suitable for inclusion in the XP2004
     Conference Proceedings
     * The poster itself, or a preliminary graphic layout of the
     poster. The preliminary graphic layout should consist of 1 to 3
     pages that sketch the layout for an 8 feet (wide) by 4 feet (high)
     bulletin board. Please use 10 point or larger font in the
     preliminary layout, and 12 point or larger in the final poster, so
     that it is readable.
     * References or supporting material
     * Presenter resume with contact information

Successful posters are carefully designed to convey technical
details. They should also have a strong visual impact that attracts
the attention of attendees as they stroll past the displays, either
during the interactive poster session or at other times during the
conference. The poster should be self-explanatory, allowing viewers to
examine the information presented without verbal assistance. The goal
is to develop a poster that encourages and facilitates small groups of
individuals interested in a technical area to gather and interact.

The submissions must be in English using the Springer LNCS style. All
submissions should be submitted electronically in Postscript or PDF
format to poster_chair@....

Call for Contributions to the Second Symposium on Extreme Training and
Education a Special Forum for trainers and educators in Extreme
Programming and Agile Processes
----------------------------------------------------------------------

A Special Forum for trainers and educators in Extreme Programming and
Agile Processes

Educational Symposium Co-Chairs: Helen Sharp and Mike Holcombe

This Symposium is for industry and academic professionals who are
interested in teaching and learning extreme programming and agile
processes. Professionals from academia and industry are invited to
discuss their needs and ideas for integrating extreme programming and
agile processes into training plans and courses. The Symposium aims to
share experiences in a variety ways. For example invited talks by
professionals on the leading edge of technology, lively and engaging
discussions, pre-submitted papers and posters. Most importantly, we
want to encourage interaction and debate rather than passive listening
to presentations, and so we'd like to invite you to submit your ideas,
successes, challenges and insights to make the Symposium yours.

We'd like to especially encourage submissions that address issues
concerned with integrating XP and other agile approaches into the
mainstream curriculum in areas such as quality, requirements capture,
HCI, user-centred design and the realities of business.

Important Dates:

     * Submissions Deadline:   January 11, 2004
     * Acceptance notification   February 28, 2004
     * Final manuscripts:   March 28, 2004

Submission Guidelines:
----------------------
Trainers and educators from all levels of industry and academia are
invited to send submissions. There will be two types of submission:
presentation materials such as papers and posters, and active sessions
such as panels and group work. Questions should be directed to Mike
Holcombe or Helen Sharp, the Symposium co-chairs at:
educationalsymposium_cochair@....

Active sessions

Submissions in this category will have a summary printed in the
Symposium notes. Submissions should contain the following information:

     * Overview of the topic to be covered
     * Type of session proposed, e.g. panel discussion, group work,
     goldfish bowl debate, mini workshop, etc.
     * Materials and preparation required (if any)
     * Process for the session (include timings)

Presentation materials

Submissions in this category will be published in the Symposium
proceeding notes. Selection will be based on clarity, originality,
technical and educational value, and, most important the "synergy
effect", i.e. the possible significance to other trainers and
educators. The review committee will focus on ideas that have the most
value for others at the Symposium. Acceptance of your paper only
guarantees that it will be published in the Symposium proceeding
notes. It does not guarantee that the one-day programme will allow
time to present it. However, all those with accepted papers will have
the opportunity to participate in some way on the day.

There are three categories of presentation materials:

     * Experience paper: There is no doubt that all professionals in
     training and education face similar challenges in teaching extreme
     programming and agile processes. Submissions in this group will
     present a challenge encountered in an industry or academic
     environment and a description of an innovative idea that was used
     to meet that challenge. Everyone has something to contribute in
     this category - both negative and positive experiences are most
     welcome! We are favoring topics in the area of expertise in other
     domains (interdisciplinary teaching and learning); facilitation a
     learning organization (educating for change); and active
     learning. If you do not wish to submit a paper, please put your
     idea on a poster.

     * Research paper: Research papers are welcome, which report on
     projects contributing to foster the knowledge in the area of
     extreme programming and agile processes. Please ensure that your
     submission includes how your findings are applicable to teachers
     of extreme programming and agile processes.

     * Poster / Demonstration: Posters and Demonstrations allow to share
     teaching and learning tools and techniques (teaching and learning
     software; effective course material and handouts; various stuff
     like urls references to books and the like). Furthermore the open
     format enables the participants to establish and deepen their
     networks with other professionals in the same area. The posters
     and demonstrations will be set up similar to an exhibition and
     will be open for the whole Extreme Educational Symposium
     day. There will be a specific timeframe alloted for circling
     around, but every break can also be used for gathering
     information. - No official proposal is required, just bring it
     along.

Please prepare your experience or research paper according to the
Springer LNCS style. All submissions should be submitted
electronically in Postscript or PDF format to
educationalsymposium_cochair@....

Call for Phd Symposium
----------------------
Phd-Symposium Chair: Jose H. Canos

The PhD symposium will provide a forum for doctoral students doing
research in the area of XP or other agile methodologies. In the
symposium students will present and discuss their research objectives,
methods, and (preliminary) results.

The goal is to provide mutual feedback and guidance from mentors as
well as from other symposium participants. The mentors are senior
university or industry researchers, e.g., current or former members of
the XP200x series program committee. The goal of the symposium is to
expose students to helpful criticism before their thesis
defense. Mentors provide constructive criticism about the current
status of the work, and give advice about possible future direction
and focus.

The PhD Symposium has the same scope as the main XP 2004 conference.

We encourage doctoral students to present their work at the
symposium. Accepted abstracts will be published in the conference
proceedings.

Important Dates:

     * Submissions Deadline:   March 1, 2004
     * Acceptance notification   March 15, 2004
     * Final manuscripts:   March 28, 2004
     * PhD Symposium:   June 2004 (date TBA)

Submission Guidelines for Phd Symposium
---------------------------------------

Students interested in participating should submit a paper describing
their doctoral work to the symposium chair. Abstracts should:

     * identify the research question the work is addressing,
     * explain significant problems and current solutions,
     * discuss the proposed approach, and
     * outline the results achieved so far.

Submissions should not be longer than 1 page and must be in
English using the Springer LNCS style. All submissions should be
submitted electronically in Postscript or PDF format to
phdsymposium_chair@....

For any additional information
please contact Jutta Eckstein at program_chair@...

Call for Social Activities
--------------------------
Social Activity Chair: Nicolai Josuttis


Social events are an important occasion to get in contact with other
people, exchange experiences, and find some new ideas, questions,
solutions, and fellows. We'd like to give you the opportunity to
suggest the way such a social event will be performed. Come with small
and large, cool and hot suggestions (but keep in mind that we have a
limit in costs).

Please submit the proposal in whatever form you like until Februrary
29, 2004 to social_activities@....

Call For Participation Agile Development Conference 2004 June 23-26
Salt Lake City, Utah USA

http://www.agiledevelopmentconference.com/index.html

The Agile Development Conference is an integrated, 4-day conversation
about techniques and technologies, attitudes and policies, research
and experience, and the management and development sides of agile
software development. The Agile approach focuses on the early delivery
business value and the ability to respond to changing requirements over
the lifetime of a project. It accentuates the use of rich, informal
communication channels, frequent delivery of running, tested systems,
and careful attention to the human component of software development.

The Agile Development Conference gives attendees access to the
latest thinking in the discipline. The event brings together the diverse
communities in software development to exchange ideas and experiences:
researchers, executives, managers, developers, testers, and customers.

The Agile Development Conference is not about a single methodology
or approach, but rather provides a forum for agile development technologies.


Some quotes from last year
---------------------------

"This conference had the highest proportion of people I wanted to talk
with of any conference I have been to." - Brian Marick

"This conference exceeded my expectations. I met far more intriguing,
insightful and worth keeping in touch with people at this conference
than any conference I have been to in a long time." - Kevin Tate

"People are so welcoming. You don't have to feel stupid. There is an
emphasis on the human side of technology." - Mary Lynn Manns


We invite you to share your knowledge and experience via the submission of:

Tutorials
---------

Tutorials are an independent instruction on a self-contained topic of
relevance to conference attendees. We encourage tutorial proposals that
provide clear utility to practitioners, especially innovative tutorials,
which depart from lecture style delivery, and tutorials on highly advanced
topics in agile processes. It is important in the tutorials track to provide
sessions that appeal to the various job roles present at the conference and
ensure balanced coverage of agile techniques.


Peer to Peer
------------
Peer to Peer sessions are designed for attendees to pool their
experience and learn from each other. We have some established formats,
but we also welcome new formats to enourage communication within a
group. Peer to Peer sessions should include learning, participation,
concrete outcomes, and (not least) fun. Session leaders should provide an
understanding of the topic and a structure to help the participants learn
from each other.


Experience Reports
--------------------

Experience reports contain first-hand information and reflection: "We
saw this, did that, and consider this-and-that about our experiences."
Experience reports serve two purposes: as raw data for researchers, and
as an exchange vehicle for practitioners. We are particularly interested
in techniques you have employed to push the envelope of current agile
thinking.


Research Papers
-----------------

Research Papers present significant contributions to the field of agile
software development, advancing the state of the art, influencing the
framework of thought in the field, or, perhaps, criticizing current
agile development methodologies in a reasoned fashion.


Key Dates:
-----------

Tutorials Proposals due January 5
Peer to Peer proposals due January 12
Research Papers Proposals due January 31
Experience Reports proposals due February 15

Please forward this call to anyone who you feel would make an excellent
contribution to this conference.








====================================================
Scott W. Ambler
Senior Consultant, Ronin International, Inc.
www.ronin-intl.com/company/scottAmbler.html

www.agiledata.org
www.agilemodeling.com
www.ambysoft.com
www.enterpriseunifiedprocess.info
www.modelingstyle.info
www.ronin-intl.com

Hello agileDatabases,



--
Best regards,
  Lesyk                          mailto:lesyk@...

My Jan 2004 column in SD magazine just came online the other day.  It is
entitled "Are You Certifiably Agile?" and is located at
http://www.sdmagazine.com/documents/s=9001/sdm0401k/sdm0401k.html.  It
presents the pros and cons of certification and argues that we may
eventually be looking at some sort of certification of agility (sigh).

Regardless, it might prove some food for thought.

- Scott

====================================================
Scott W. Ambler
Senior Consultant, Ronin International, Inc.
www.ronin-intl.com/company/scottAmbler.html

www.agiledata.org
www.agilemodeling.com
www.ambysoft.com
www.enterpriseunifiedprocess.info
www.modelingstyle.info
www.ronin-intl.com

Hello All,

I'm an Oracle/SQL2K database admin/developer, currently involved in
providing database development and admin support to a J2EE
development group. To my surprise, I'm quite enjoying myself (after
the initial culture shock :-)). I find myself picking up some
basic OO and Java skills, and in turn educating my colleagues
on relational theory, practice and individual product quirks.
It's working quite nicely, but I'm sure things could be improved.
To this end, I have written up some of our practices below. The
intent is to share our group's experiences and to elicit
suggestions /advice from others working in similar environments:

0. Design: I lack UML skills, but I learned enough to decipher
my colleagues' efforts. Based on their work, I developed designs
using conventional entity relationship diagrams. These schema
designs were (and are still being) refined through the use
of OR mapping tools. We find that schema auto generation tools
provide a nice check on our understanding of the mapping.

1. Development databases: Each developer gets his/her own schema
(on Oracle) and  database (on MSSQL). We find that this avoids
unnecessary maintenance overhead associated with each developer
having their own instance, yet each developer remains isolated
from the others.

2. Database scripts: Scripts for schema maintenance are kept in a
  central repository. The scripts themselves are generic as far as
  possible (for tasks such as disable constraints, delete data etc)
  - the generality being maintained through the use of dynamic SQL.
  Of course, there are several cases that can't be "genericised"
  (such as specific schema generation scripts). These, to the extent
  possible,  are auto-generated by OR mapping tools. This has worked
  reasonably well so far, but I'm always on the look out for better
  ways to work.

3. Testing: this is proving to be something of a problem. Currently
I write manual tests to exercise the OR mapping. The tests are based
on our understanding of how the database will be used. An example -
save,read, update, delete an order and all its related persistence
classes. I'm still uneasy that we have left out as yet unforeseen
ways in which the database will be accessed. On another note: I've
not yet automated these tests as I have not yet got around to
picking up unit testing skills. This is still on my todo
list.

Ours is not an Agile development environment in the strict sense of
the term.  Yet, at least as far as database development is
concerned, we have more in common with the Agile philosophy than
with traditional database programming and admin. I'm keen to contact
others  working in environments similar to mine, and I look forward
to exchanging notes with others in this group.

My apologies for the rather verbose post, and thanks for taking the
time to read it!

Regards,

Kailash.

(responding to Kailash)

> 1. Development databases: Each developer gets his/her
> own schema (on Oracle) and  database (on MSSQL). We
> find that this avoids unnecessary maintenance overhead
> associated with each developer having their own instance,
> yet each developer remains isolated from the others.
>
> 2. Database scripts: Scripts for schema maintenance are
> kept in a central repository. The scripts themselves are
> generic as far as  possible (for tasks such as disable
> constraints, delete data etc) - the generality being
> maintained through the use of dynamic SQL.  Of course,
> there are several cases that can't be "genericised"  (such
> as specific schema generation scripts). These, to the extent
> possible,  are auto-generated by OR mapping tools. This
> has worked reasonably well so far, but I'm always on the
> look out for better  ways to work.

It wasn't clear to me how changes to schema would be made.
Do the developers make changes locally, test them on their
own 'schema', then integrate once tested?

Does integration of changes cause you problems?  I'd
imagine if you're limited to manual tests and guessing
which are appropriate, integration might be a bit fraught.
How frequently do you manage to complete integration?


Paul Oldfield
www.aptprocess.com

> 0. Design: I lack UML skills, but I learned enough to decipher
> my colleagues' efforts. Based on their work, I developed designs
> using conventional entity relationship diagrams. These schema
> designs were (and are still being) refined through the use
> of OR mapping tools. We find that schema auto generation tools
> provide a nice check on our understanding of the mapping.
You may want to research some SQL Generation tool such as jaxor
(http://jaxor.sourceforge.net).
These kind of tools map the database tables to the objects and provide
an automated way of
generating the access/persistence layer.

> 1. Development databases: Each developer gets his/her own schema
> (on Oracle) and  database (on MSSQL). We find that this avoids
> unnecessary maintenance overhead associated with each developer
> having their own instance, yet each developer remains isolated
> from the others.

Good point. we do this all the time. You can also have databases with
different sets of data for various kinds of
testing (performance, acceptance etc)
which can be backed up and used by developers/team by restoring a copy
for their local testing

> 2. Database scripts: Scripts for schema maintenance are kept in a
>  central repository. The scripts themselves are generic as far as
>  possible (for tasks such as disable constraints, delete data etc)
>  - the generality being maintained through the use of dynamic SQL.
>  Of course, there are several cases that can't be "genericised"
>  (such as specific schema generation scripts). These, to the extent
>  possible,  are auto-generated by OR mapping tools. This has worked
>  reasonably well so far, but I'm always on the look out for better
>  ways to work.

we also store the database creation scripts (like create
tables,indexes, views, stored proc, views , RI constraints, DB
comments etc)
in the repository, so that you can recreate the database when ever you
want against the distribution that you want the application deployed
against.
In other words you can match the application release/build against a
database schema build which matches with the application.
This is huge thing, since this allows you to deploy any build at any
time against the right database schema.


> 3. Testing: this is proving to be something of a problem. Currently
> I write manual tests to exercise the OR mapping. The tests are based
> on our understanding of how the database will be used. An example -
> save,read, update, delete an order and all its related persistence
> classes. I'm still uneasy that we have left out as yet unforeseen
> ways in which the database will be accessed. On another note: I've
> not yet automated these tests as I have not yet got around to
> picking up unit testing skills. This is still on my todo
> list.
>

Using a SQL Generation layer will help you write unit tests against
the persistence layer also.
One more point to stress would be keep all of your database access
code at one place/layer in your application.
This will make it easy for you to refactor later on.

more follow up reading at
(http://www.martinfowler.com/articles/evodb.html)

Thanks
Pramod

(responding to Kailash)

> 1. Development databases: Each developer gets his/her
> own schema (on Oracle) and  database (on MSSQL). We
> find that this avoids unnecessary maintenance overhead
> associated with each developer having their own instance,
> yet each developer remains isolated from the others.
>
> 2. Database scripts: Scripts for schema maintenance are
> kept in a central repository. The scripts themselves are
> generic as far as  possible (for tasks such as disable
> constraints, delete data etc) - the generality being
> maintained through the use of dynamic SQL.  Of course,
> there are several cases that can't be "genericised"  (such
> as specific schema generation scripts). These, to the extent
> possible,  are auto-generated by OR mapping tools. This
> has worked reasonably well so far, but I'm always on the
> look out for better  ways to work.

It wasn't clear to me how changes to schema would be made.
Do the developers make changes locally, test them on their
own 'schema', then integrate once tested? 

Does integration of changes cause you problems?  I'd
imagine if you're limited to manual tests and guessing
which are appropriate, integration might be a bit fraught.
How frequently do you manage to complete integration?


Paul Oldfield
www.aptprocess.com

---

Yahoo! Groups Links

• To visit your group on the web, go to:
  http://groups.yahoo.com/group/agileDatabases/
   
• To unsubscribe from this group, send an email to:
  agileDatabases-unsubscribe@yahoogroups.com
   
• Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

> 0. Design: I lack UML skills, but I learned enough to decipher
> my colleagues' efforts. Based on their work, I developed designs
> using conventional entity relationship diagrams. These schema
> designs were (and are still being) refined through the use
> of OR mapping tools. We find that schema auto generation tools
> provide a nice check on our understanding of the mapping.
You may want to research some SQL Generation tool such as jaxor
(http://jaxor.sourceforge.net).
These kind of tools map the database tables to the objects and provide
an automated way of
generating the access/persistence layer

> 1. Development databases: Each developer gets his/her own schema
> (on Oracle) and  database (on MSSQL). We find that this avoids
> unnecessary maintenance overhead associated with each developer
> having their own instance, yet each developer remains isolated
> from the others.

Good point. we do this all the time. You can also have databases with
different sets of data for various kinds of
testing (performance, acceptance etc)
which can be backed up and used by developers/team by restoring a copy
for their local testing

> 2. Database scripts: Scripts for schema maintenance are kept in a
>  central repository. The scripts themselves are generic as far as
>  possible (for tasks such as disable constraints, delete data etc)
>  - the generality being maintained through the use of dynamic SQL.
>  Of course, there are several cases that can't be "genericised"
>  (such as specific schema generation scripts). These, to the extent
>  possible,  are auto-generated by OR mapping tools. This has worked
>  reasonably well so far, but I'm always on the look out for better
>  ways to work.

we also store the database creation scripts (like create
tables,indexes, views, stored proc, views , RI constraints, DB
comments etc)
in the repository, so that you can recreate the database when ever you
want against the distribution that you want the application deployed
against.
In other words you can match the application release/build against a
database schema build which matches with the application.
This is huge thing, since this allows you to deploy any build at any
time against the right database schema.


> 3. Testing: this is proving to be something of a problem. Currently
> I write manual tests to exercise the OR mapping. The tests are based
> on our understanding of how the database will be used. An example -
> save,read, update, delete an order and all its related persistence
> classes. I'm still uneasy that we have left out as yet unforeseen
> ways in which the database will be accessed. On another note: I've
> not yet automated these tests as I have not yet got around to
> picking up unit testing skills. This is still on my todo
> list.
>

Using a SQL Generation layer will help you write unit tests against
the persistence layer also.
One more point to stress would be keep all of your database access
code at one place/layer in your application.
This will make it easy for you to refactor later on.

more follow up reading at
(http://www.martinfowler.com/articles/evodb.html)

Thanks
Pramod

---

Yahoo! Groups Links

• To visit your group on the web, go to:
  http://groups.yahoo.com/group/agileDatabases/
   
• To unsubscribe from this group, send an email to:
  agileDatabases-unsubscribe@yahoogroups.com
   
• Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Dear experts,

Could anyone describe what AgileDatabase is? Nowadays, a few new
methodologies came out, suchlike XtremeProgramming, AgileModeling,
AgileDatabase, AgileProjectManagement, XtremeProjectManagement, and
etc. Could anyone share with me; as a fast understanding on the
concept, objectives, and benefits of AgileDatabase?

Best regards,
kamyen

From: "kamyen" <kamyen.at.yahoo.com@...>
Sent: Wednesday, January 14, 2004 8:36 PM
Subject: [agileDatabases] What is AgileDatabase?


> Dear experts,
>
> Could anyone describe what AgileDatabase is? Nowadays, a few new
> methodologies came out, suchlike XtremeProgramming, AgileModeling,
> AgileDatabase, AgileProjectManagement, XtremeProjectManagement, and
> etc. Could anyone share with me; as a fast understanding on the
> concept, objectives, and benefits of AgileDatabase?

The typical understanding of relational data bases is that they
are hard to change, so you need to be right up front. Agile
Database says that, in order to fit in with other Agile processes,
  they had better be easy (or at least a lot easier) to change, and
what do you need to do to make it so.

The rest, as they say, is detail. See Scott Ambler's web site
(www.agiledata.org).

John Roth

>
> Best regards,
> kamyen

Thanks.  A good starting point might be www.agiledata.org/essays/vision.html

- Scott

At 08:49 PM 1/14/2004 -0500, you wrote:
>From: "kamyen" <kamyen.at.yahoo.com@...>
>Sent: Wednesday, January 14, 2004 8:36 PM
>Subject: [agileDatabases] What is AgileDatabase?
>
>
> > Dear experts,
> >
> > Could anyone describe what AgileDatabase is? Nowadays, a few new
> > methodologies came out, suchlike XtremeProgramming, AgileModeling,
> > AgileDatabase, AgileProjectManagement, XtremeProjectManagement, and
> > etc. Could anyone share with me; as a fast understanding on the
> > concept, objectives, and benefits of AgileDatabase?
>
>The typical understanding of relational data bases is that they
>are hard to change, so you need to be right up front. Agile
>Database says that, in order to fit in with other Agile processes,
>  they had better be easy (or at least a lot easier) to change, and
>what do you need to do to make it so.
>
>The rest, as they say, is detail. See Scott Ambler's web site
>(www.agiledata.org).
>
>John Roth
>
> >
> > Best regards,
> > kamyen
>
>
>
>
>Yahoo! Groups Links
>
>To visit your group on the web, go to:
>  http://groups.yahoo.com/group/agileDatabases/
>
>To unsubscribe from this group, send an email to:
>  agileDatabases-unsubscribe@yahoogroups.com
>
>Your use of Yahoo! Groups is subject to:
>  http://docs.yahoo.com/info/terms/

====================================================
Scott W. Ambler
Senior Consultant, Ronin International, Inc.
www.ronin-intl.com/company/scottAmbler.html

www.agiledata.org
www.agilemodeling.com
www.ambysoft.com
www.enterpriseunifiedprocess.info
www.modelingstyle.info
www.ronin-intl.com