Implementing agile in your organization? Tackling
challenges on your latest agile project? Build an agile
training program from our new courses including:
Scrum Master Certification, Design Patterns
Explained, User Stories and Estimation in Agile
Development, and Practical Test-Driven Development.

With these courses you can apply lean-agile principles
to software development projects, learn Test-Driven
Development techniques, understand how to use design
patterns in an agile environment, write user stories
and estimate development in an agile development
process, and learn much more.

March 30 – April 3, 2009 * Washington, DC
Courtyard Alexandria Pentagon South
http://www.sqe.com/go?Agile09

Draft paper submission deadline extended: SETP-09
 
The deadline for draft paper submission at the 2009 International Conference on
Software Engineering Theory and Practice (SETP-09) (website:
http://www.PromoteResearch.org ) is extended due to numerous requests from the
authors.  The conference will be held during July 13-16 2009 in Orlando, FL,
USA. We invite draft paper submissions. The conference will take place at the
same time and venue where several other international conferences are taking
place. The other conferences include:
·         International Conference on Artificial Intelligence and Pattern
Recognition (AIPR-09)
·         International Conference on Automation, Robotics and Control Systems
(ARCS-09)
·         International Conference on Bioinformatics, Computational Biology,
Genomics and Chemoinformatics (BCBGC-09)
·         International Conference on Enterprise Information Systems and Web
Technologies (EISWT-09)
·         International Conference on High Performance Computing, Networking and
Communication Systems (HPCNCS-09)
·         International Conference on Information Security and Privacy (ISP-09)
·         International Conference on Recent Advances in Information Technology
and Applications (RAITA-09)
·         International Conference on Theory and Applications of Computational
Science (TACS-09)
·         International Conference on Theoretical and Mathematical Foundations
of Computer Science (TMFCS-09)
 
The website http://www.PromoteResearch.org contains more details.
 
Sincerely
John Edward
Publicity committee
 




[Non-text portions of this message have been removed]

---------- Forwarded message ----------
From: filip_neven <filip_neven@...>
Date: Tue, Feb 24, 2009 at 3:20 AM
Subject: [citcon] dbmaintain released
To: citcon@yahoogroups.com


  Dbmaintain <http://www.dbmaintain.org> is a new open source project that
takes care of the database part of automatic deployments. Essentially it
does the same as the dbdeploy <http://dbdeploy.com/> project, but it has
more features.

It updates the database incrementally: you create a 'delta' script for each
change to the database - the system automatically detects whether there are
new/updated scripts. It supports various kinds of scripts: incremental
scripts, repeatable scripts and postprocessing scripts. There's also a
from-scratch option: if enabled, the database is rebuilt from scratch if for
example an existing incremental script is modified.

The features of dbmaintain exist already quite some time in the project
unitils <http://www.unitils.org> - I recently decided to split it up into a
new project. I've just released the first version. You might want to take a
look at it, I would be very happy to get some feedback!

Regards,
Filip Neven




[Non-text portions of this message have been removed]

Yesterday at Software Development (www.sdexpo.com) Bob Martin gave a really good
keynote exploring the history of the Agile movement.  During the talk he
overviewed the Manifesto for Software Craftsmanship,
http://manifesto.softwarecraftsmanship.org/ , which extends the values of the
Agile Manifesto in very interesting ways.

- Scott
Scott W. Ambler
Chief Methodologist/Agile, IBM Rational
Agile at Scale: http://www.ibm.com/developerworks/blogs/page/ambler


       __________________________________________________________________
Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your
favourite sites. Download it now at
http://ca.toolbar.yahoo.com.

All,
I have a client that wants to utilize UML in their General Business Data Model
development effort.

What is the status of the UML standard as it relates to Data Modeling.   I know
there was an RFP, but that is the last I saw on the topic.

Any information would be helpful.

Thank You,
Barry Sunshine

Hi all:

Curious to know what unit-testing framework(s) you use on SQL Server, and how. 
I am tasked with setting our corporate standard, and I'd like to get an
understanding of the existing landscape.

My first inclination is to create / acquire something that is SQL Server-native,
so we don't have to train our database developers in .NET as well.  I don't see
much out there, which leads me to suspect that folks are either rolling their
own unit tests without a framework (as I have historically done -- very
time-consuming), wrapping their DAL and testing from the application level, or
aren't bothering at all.

If I end up building, I envision assertions, fixtures, a runner and (text-based)
visual feedback/reporting.  What non-obvious features would make such a tool
compelling for you?

Thanks;
Duncan

You could take a look at DB Ghost - www.dbghost.com - which has a build
feature, good for code verification.




regards,
Mark Baekdal

http://www.dbghost.com <http://www.dbghost.com/>

Developers taking control of SQL Server code.





From: agileDatabases@yahoogroups.com
[mailto:agileDatabases@yahoogroups.com] On Behalf Of thatguyduncan
Sent: 24 March 2009 17:23
To: agileDatabases@yahoogroups.com
Subject: [agileDatabases] unit testing framework(s) for SQL Server 200x



Hi all:

Curious to know what unit-testing framework(s) you use on SQL Server,
and how. I am tasked with setting our corporate standard, and I'd like
to get an understanding of the existing landscape.

My first inclination is to create / acquire something that is SQL
Server-native, so we don't have to train our database developers in .NET
as well. I don't see much out there, which leads me to suspect that
folks are either rolling their own unit tests without a framework (as I
have historically done -- very time-consuming), wrapping their DAL and
testing from the application level, or aren't bothering at all.

If I end up building, I envision assertions, fixtures, a runner and
(text-based) visual feedback/reporting. What non-obvious features would
make such a tool compelling for you?

Thanks;
Duncan





[Non-text portions of this message have been removed]

I'm using a slightly altered version of t-sqlunit. It is native t-sql and uses
naming convenstions for test suite naming grouping and execution, setup and
teardown etc.

it does an OK job, I don't like the fact that it has a footprint on the server.

This is just for ms-sql.

I've tried the db-pro (visual studio for database professionals) and found the
t-sql facade over the .net testing framework a bit confusing, but it met my zero
footprint desire, and had some better options for testing output.

Interested in hearing what other folks are doing on this front.

Tc


________________________________

From: agileDatabases@yahoogroups.com <agileDatabases@yahoogroups.com>
To: agileDatabases@yahoogroups.com <agileDatabases@yahoogroups.com>
Sent: Tue Mar 24 12:22:49 2009
Subject: [agileDatabases] unit testing framework(s) for SQL Server 200x


Hi all:

Curious to know what unit-testing framework(s) you use on SQL Server, and how. I
am tasked with setting our corporate standard, and I'd like to get an
understanding of the existing landscape.

My first inclination is to create / acquire something that is SQL Server-native,
so we don't have to train our database developers in .NET as well. I don't see
much out there, which leads me to suspect that folks are either rolling their
own unit tests without a framework (as I have historically done -- very
time-consuming), wrapping their DAL and testing from the application level, or
aren't bothering at all.

If I end up building, I envision assertions, fixtures, a runner and (text-based)
visual feedback/reporting. What non-obvious features would make such a tool
compelling for you?

Thanks;
Duncan






[Non-text portions of this message have been removed]

> Curious to know what unit-testing framework(s) you use on SQL Server, and how.
 I am tasked
> with setting our corporate standard, and I'd like to get an understanding of
the existing landscape.

For testing the DB, I use the FitNesse/DbFit combination.  I guess
it's not "unit testing" of the purest form, but it does serve to test
my database, which mostly involves testing stored procedures.

/bs

> From: agileDatabases@yahoogroups.com
> [mailto:agileDatabases@yahoogroups.com] On Behalf Of Brad Stiles
>
> For testing the DB, I use the FitNesse/DbFit combination.  I guess
> it's not "unit testing" of the purest form, but it does serve to test
> my database, which mostly involves testing stored procedures.

+1 for DbFit. I've started using it instead of utPL/SQL, and so far it
seems to be an improvement. And a plus is that the tests are
readable/maintanable by our analysts. It seems to be able to do most of
what I've used utPL/SQL for, and it's a lot less verbose.

Alistair
*****************************************************************
Confidentiality Note: The information contained in this message,
and any attachments, may contain confidential and/or privileged
material. It is intended solely for the person(s) or entity to
which it is addressed. Any review, retransmission, dissemination,
or taking of any action in reliance upon this information by
persons or entities other than the intended recipient(s) is
prohibited. If you received this in error, please contact the
sender and delete the material from any computer.
*****************************************************************

I third dbFit. It is the best out there. It utilizes Fit + Fitnesse which is
mostly used as acceptance testing framework but for database it ends up
being pure unit testing. You just have to learn a few fixture names, set up
connections, and start building your test pages. No coding required if you
don't count your SQL test statements. It works great with SQL Server.

On Wed, Mar 25, 2009 at 8:51 AM, Bayley, Alistair <
Alistair_Bayley@...> wrote:

>   > From: agileDatabases@yahoogroups.com<agileDatabases%40yahoogroups.com>
> > [mailto:agileDatabases@yahoogroups.com<agileDatabases%40yahoogroups.com>]
> On Behalf Of Brad Stiles
>
> >
> > For testing the DB, I use the FitNesse/DbFit combination. I guess
> > it's not "unit testing" of the purest form, but it does serve to test
> > my database, which mostly involves testing stored procedures.
>
> +1 for DbFit. I've started using it instead of utPL/SQL, and so far it
> seems to be an improvement. And a plus is that the tests are
> readable/maintanable by our analysts. It seems to be able to do most of
> what I've used utPL/SQL for, and it's a lot less verbose.
>
> Alistair
> *****************************************************************
> Confidentiality Note: The information contained in this message,
> and any attachments, may contain confidential and/or privileged
> material. It is intended solely for the person(s) or entity to
> which it is addressed. Any review, retransmission, dissemination,
> or taking of any action in reliance upon this information by
> persons or entities other than the intended recipient(s) is
> prohibited. If you received this in error, please contact the
> sender and delete the material from any computer.
> *****************************************************************
>
>
>


[Non-text portions of this message have been removed]

DBFit does the work for me - it's not only for sql server.
Much easier than writing the code.

http://gojko.net/fitnesse/dbfit/

HTH
ak

--- In agileDatabases@yahoogroups.com, "Todd Carrico" <todd.carrico@...> wrote:
>
> I'm using a slightly altered version of t-sqlunit. It is native t-sql and uses
naming convenstions for test suite naming grouping and execution, setup and
teardown etc.
>
> it does an OK job, I don't like the fact that it has a footprint on the
server.
>
> This is just for ms-sql.
>
> I've tried the db-pro (visual studio for database professionals) and found the
t-sql facade over the .net testing framework a bit confusing, but it met my zero
footprint desire, and had some better options for testing output.
>
> Interested in hearing what other folks are doing on this front.
>
> Tc
>
>
> ________________________________
>
> From: agileDatabases@yahoogroups.com <agileDatabases@yahoogroups.com>
> To: agileDatabases@yahoogroups.com <agileDatabases@yahoogroups.com>
> Sent: Tue Mar 24 12:22:49 2009
> Subject: [agileDatabases] unit testing framework(s) for SQL Server 200x
>
>
> Hi all:
>
> Curious to know what unit-testing framework(s) you use on SQL Server, and how.
I am tasked with setting our corporate standard, and I'd like to get an
understanding of the existing landscape.
>
> My first inclination is to create / acquire something that is SQL
Server-native, so we don't have to train our database developers in .NET as
well. I don't see much out there, which leads me to suspect that folks are
either rolling their own unit tests without a framework (as I have historically
done -- very time-consuming), wrapping their DAL and testing from the
application level, or aren't bothering at all.
>
> If I end up building, I envision assertions, fixtures, a runner and
(text-based) visual feedback/reporting. What non-obvious features would make
such a tool compelling for you?
>
> Thanks;
> Duncan
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

It was recommended that I chime in even though some might see it as
shameless self-promotion.  I use NUnit and DataConstructor together.



Max Guernsey, III

Managing Member, Hexagon Software

  <http://www.hexsw.com/> http://www.hexsw.com

  <http://www.dataconstructor.com/> http://www.dataconstructor.com



From: agileDatabases@yahoogroups.com [mailto:agileDatabases@yahoogroups.com]
On Behalf Of alexander_karmanov
Sent: Wednesday, March 25, 2009 5:46 AM
To: agileDatabases@yahoogroups.com
Subject: [agileDatabases] Re: unit testing framework(s) for SQL Server 200x



DBFit does the work for me - it's not only for sql server.
Much easier than writing the code.

http://gojko.net/fitnesse/dbfit/

HTH
ak

--- In agileDatabases@yahoogroups.com
<mailto:agileDatabases%40yahoogroups.com> , "Todd Carrico"
<todd.carrico@...> wrote:
>
> I'm using a slightly altered version of t-sqlunit. It is native t-sql and
uses naming convenstions for test suite naming grouping and execution, setup
and teardown etc.
>
> it does an OK job, I don't like the fact that it has a footprint on the
server.
>
> This is just for ms-sql.
>
> I've tried the db-pro (visual studio for database professionals) and found
the t-sql facade over the .net testing framework a bit confusing, but it met
my zero footprint desire, and had some better options for testing output.
>
> Interested in hearing what other folks are doing on this front.
>
> Tc
>
>
> ________________________________
>
> From: agileDatabases@yahoogroups.com
<mailto:agileDatabases%40yahoogroups.com>  <agileDatabases@yahoogroups.com
<mailto:agileDatabases%40yahoogroups.com> >
> To: agileDatabases@yahoogroups.com
<mailto:agileDatabases%40yahoogroups.com>  <agileDatabases@yahoogroups.com
<mailto:agileDatabases%40yahoogroups.com> >
> Sent: Tue Mar 24 12:22:49 2009
> Subject: [agileDatabases] unit testing framework(s) for SQL Server 200x
>
>
> Hi all:
>
> Curious to know what unit-testing framework(s) you use on SQL Server, and
how. I am tasked with setting our corporate standard, and I'd like to get an
understanding of the existing landscape.
>
> My first inclination is to create / acquire something that is SQL
Server-native, so we don't have to train our database developers in .NET as
well. I don't see much out there, which leads me to suspect that folks are
either rolling their own unit tests without a framework (as I have
historically done -- very time-consuming), wrapping their DAL and testing
from the application level, or aren't bothering at all.
>
> If I end up building, I envision assertions, fixtures, a runner and
(text-based) visual feedback/reporting. What non-obvious features would make
such a tool compelling for you?
>
> Thanks;
> Duncan
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>





[Non-text portions of this message have been removed]

I use tSQLt. It is a native T-SQL unit testing framework for SQL Server
2005. The key features allow you to isolate different pieces of code. For
example, if you have a view you want to test, and that view uses several
tables with FKs to several other tables, then the ability to put data into
those underlying tables becomes increasingly complex. tSQLt introduces the
concept of FakeTables (and some other fake object types) which allow you to
isolate the unit under test. You can find more about it at
http://www.sqlity.net/sqlity/articles/tSQLtTutorial

If you like these features, but still need to write tests for SQL 2000,
there are some extensions for TSQLUnit which you can read about here:
http://www.sqlity.net/sqlity/articles/DbTDD

If you decide to use or experiment with these, let me know - I would like to
hear any feedback on the project.
Cheers!
-Dennis

On Tue, Mar 24, 2009 at 1:22 PM, thatguyduncan <thatguyduncan@...>wrote:

>   Hi all:
>
> Curious to know what unit-testing framework(s) you use on SQL Server, and
> how. I am tasked with setting our corporate standard, and I'd like to get an
> understanding of the existing landscape.
>
> My first inclination is to create / acquire something that is SQL
> Server-native, so we don't have to train our database developers in .NET as
> well. I don't see much out there, which leads me to suspect that folks are
> either rolling their own unit tests without a framework (as I have
> historically done -- very time-consuming), wrapping their DAL and testing
> from the application level, or aren't bothering at all.
>
> If I end up building, I envision assertions, fixtures, a runner and
> (text-based) visual feedback/reporting. What non-obvious features would make
> such a tool compelling for you?
>
> Thanks;
> Duncan
>
>
>


[Non-text portions of this message have been removed]

Hi,

Greetings!

I'm a newbie with agiledatabase. But I work exclusively with Oracle databases on
Sun Solaris. I appriciate if someone could give me references to implement
agiledatabase environment along with tools.


Thank you.
Mark Sastry
email: msastry1@...





[Non-text portions of this message have been removed]

Hey Everybody-
I'm the development manager at Genius.com.  We follow an agile development
process based on Scrum with heavy doses of Lean and XP.  One of the core tenets
of our process is the need for developers to write unit tests.  As a web dev
team, we ran into a lot of problems trying to effectively unit test code that
depended on the DB.  As a result we have developed a fixture framework that
setups up a test database with test data for our unit tests to test against. 
We've distilled the evolution of our db testing framework into a blog post:
http://eng.genius.com/blog/2009/03/30/testing-db-dependencies-with-phpunit/

We welcome your feedback.

Take Care,
Ryan Ausanka-Crues
Development Manager
Genius.com

I’ll be teaching Scum Certified(TM) Agile Master courses in the following
cities this month:

April 2-3 Toronto, Canada
April 6-7 Sydney, Australia
April 8-9 Munich, Germany
April 10-11 Tokyo, Japan
April 13-14 Sao Paulo, Brazil
April 15-16 Helsinki, Finland
April 17-18 Chicago, USA
April 20-21 Moscow, Russia
April 22-23 London, England
April 24-25 Shanghai, China
April 27-28 Los Angeles, USA
April 29-30 Johannesburg, South Africa

For this month only the fee is $995 per person if you enroll online, or $1,195
per person if you enroll at the door.  For more information about becoming a
Scum Certified(TM) Agile Master and to enroll, visit
http://www.ambysoft.com/certification/scam.html .

If you’re interested in becoming a Scum Certified(TM) Trainer, visit
http://www.ambysoft.com/certification/scamArtist.html

Thanks.

- Scott
PS -- Please forward this announcement to other appropriate mailing lists.





       __________________________________________________________________
Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your
favourite sites. Download it now
http://ca.toolbar.yahoo.com.

Hi All,
I am a newbie OO designer. I use an object database, db4o ( http://www.db4o.com
) for a project. I am having problem to document my object schema design. Is
there any standard notation in UML class diagram to define constraints like
these:

- unique constraint value of a member field. For example: "an ISBN is unique
value for Book class"

- referential integrity between class, Cascade Delete. For example: There is 2
category class, fiction and non-fiction Book. If i delete fiction class, all
books belong to that category will be deleted too.

- inverse relationship, bi-directional

regards,
Muntasir Rahman

That's funny ;)
Scott, I couldn't help but notice that you'd be absolutely worn out by the jet
lag if you did follow the tour locations and dates.

--- On Thu, 4/2/09, Muntasir Rahman <muntasir.rahman@...> wrote:

<snip>
> - unique constraint value of a member field. For example:
> "an ISBN is unique value for Book class"

Easist thing is to use a note, see http://www.agilemodeling.com/style/note.htm
for examples.

You could also use OCL, but few people actually know it.

If ISBN is some form of key, see
http://www.agiledata.org/essays/umlDataModelingProfile.html#Keys

>
> - referential integrity between class, Cascade Delete. For
> example: There is 2 category class, fiction and non-fiction
> Book. If i delete fiction class, all books belong to that
> category will be deleted too.

See
http://www.agiledata.org/essays/umlDataModelingProfile.html#ConstraintsTriggers

>
> - inverse relationship, bi-directional
>

http://www.agiledata.org/essays/umlDataModelingProfile.html#Relationships

- Scott
Scott W. Ambler
Chief Methodologist/Agile, IBM Rational
Agile at Scale: http://www.ibm.com/developerworks/blogs/page/ambler




       __________________________________________________________________
Instant Messaging, free SMS, sharing photos and more... Try the new Yahoo!
Canada Messenger at http://ca.beta.messenger.yahoo.com/

Hi all,
--- In agileDatabases@yahoogroups.com, Scott Ambler <scottwambler@...> wrote:
> --- On Thu, 4/2/09, Muntasir Rahman <muntasir.rahman@...> wrote:
> <snip>
> > - unique constraint value of a member field. For example:
> > "an ISBN is unique value for Book class"
> Easist thing is to use a note, see http://www.agilemodeling.com/style/note.htm
for examples.
> You could also use OCL, but few people actually know it.
> If ISBN is some form of key, see
http://www.agiledata.org/essays/umlDataModelingProfile.html#Keys
I am currently documenting an operational database and I am confronted with a
key-related modeling problem as well.  On
http://is.tm.tue.nl/staff/pvgorp/fora/key-issue1.png you find a fragment where I
apply <<K>> to denote natural keys of the tables underlying particular classes
(User and Host).  The diagram is at the level of *logical* data modeling. 
Therefore, I have not mapped the three associations to attributes (that would
correspond directly to table columns).

The problem I am faced with now, is that
http://www.agiledata.org/essays/umlDataModelingProfile.html#Keys (or any other
data modeling source I am aware of) does not provide a means to model the
InternetAccess(user,host) key from the underlying database.  On
http://is.tm.tue.nl/staff/pvgorp/fora/key-issue1.png I show two OCL constraints
that do formalize the intended constraint but I am looking for a more readable
modeling style.  I do not consider the OCL readable, because:
  1) database administrators may not know the OCL (see comment from Scott),
  2) I need to specify the constraint from two sides explicitly.

I think (2) is a bigger problem than (1) because the OCL example is based on
straightforward logics and may be comprehensible even to people that are
unfamiliar with the language.  No matter what, I think the OCL application shown
in the example is bad style.

I have some old, rough experience on
http://is.tm.tue.nl/staff/pvgorp/research/datamodelingprofile/HR-example.png but
at the time (2003?) I did not consider the need to include (to-one) association
ends in key definitions either...

As potential solutions, I am thinking of
http://is.tm.tue.nl/staff/pvgorp/fora/key-issue2a.png and
http://is.tm.tue.nl/staff/pvgorp/fora/key-issue2b.png.  Both approaches raise
new issues from a tooling perspective (it is impossible to use AssociationEnd as
types in in TagDefinitions) but currently I am primarily interested in:

  1) have others ever wanted to include association ends in natural key
definitions?
  2) what (informal) syntax have others applied?

Kind regards,
and thanks in advance for your input,
Pieter Van Gorp

Hey All,

The STAREAST software testing conference starts next week
and there are many opportunities to save on your registration.
Check it out: http://www.sqe.com/STAREAST/WaysToSave.aspx

When: Wednesday, June 10, 2009 5:00 PM-7:30 PM (GMT-05:00) Eastern Time (US &
Canada).
Where: The Hartford: Atrium Conference Room

*~*~*~*~*~*~*~*~*~*

This meeting will feature Marcus Ranum, inventor of the firewall as well as a
special presentation on combining security with agile software development...

The Open Web Application Security Project (OWASP) is a worldwide free and open
community focused on improving the security of application software. Our mission
is to make application security "visible," so that people and organizations can
make informed decisions about application security risks. Everyone is free to
participate in OWASP and all of our materials are available under a free and
open software license.

The agenda for this meeting is posted at:
http://www.owasp.org/index.php/Hartford

To receive future invites, please subscribe to our mailing list at:
https://lists.owasp.org/mailman/listinfo/owasp-hartford
************************************************************
This communication, including attachments, is for the exclusive use of addressee
and may contain proprietary, confidential and/or privileged information.  If you
are not the intended recipient, any use, copying, disclosure, dissemination or
distribution is strictly prohibited.  If you are not the intended recipient,
please notify the sender immediately by return e-mail, delete this communication
and destroy all copies.
************************************************************


[Non-text portions of this message have been removed]

Hi,

I am new to this group and thinking about buying the book
(http://www.ambysoft.com/books/refactoringDatabases.html
) mentioned in
http://www.agiledata.org/essays/umlDataModelingProfile.html.

There is another book
(http://www.informit.com/store/product.aspx?isbn=0201721635
) I have bought but I have my problems with it.
The book seems to discuss only the visual part of the profile, but not
exactly the invisible part (tagged values used beside an element
as of Table 6. Tagged values for modeling keys in the above second
link).

My problem is to select the best profile to be used in my project. I
need an exact profile description or better the profile as a XMI 2.1
file.
I tried to reengineer a database (of the Postbooks project) and I came
to a problem with multiple foreign keys per a pair of tables. There
are other issues I have to cope with, but that would be the important
one in my view. Thus my solution of creating a XMI file is not at the
best. That's why I am searching for a more 'official' notation or
profile.

On both solutions I didn't have yet found a ready made sample project
including the XMI file. Are there any samples available?

Who has used one of the profiles to reengineer existing databases like
the Postbooks database (http://postbooks.sourceforge.net/)?

I am using BoUML (bouml.free.fr) as my preferred UML 2 tool. Does
someone else using this tool (why / why not)?

I have identified a major difference between the two approaches and it
is about using single stereotypes
(http://www.informit.com/store/product.aspx?isbn=0201721635
) per element and multiple stereotypes
(http://www.agiledata.org/essays/umlDataModelingProfile.html
).

BoUML seems not to support multiple stereotypes and I think, this
could be avoided by using multiple inheritance of the stereotype class
definitions
in the profile.

Why are here used multiple stereotypes?

Are they allowed in UML 2 or any newer version?

I hope these questions are not too novice :-)

I stuck in my project because I am not clear, what profile I should
use inside my own profile. It is an independent part of the project,
because UML
generation is only one solution one could use with my tool, but using
a widely used approach would make it more interesting. This would also
affect
my current solution to read from UML (XMI) models.

Thanks

Lothar

-- | Rapid Prototyping | XSLT Codegeneration | http://www.lollisoft.de
Lothar Behrens
Heinrich-Scheufelen-Platz 2
73252 Lenningen

dear friends,
    Access can be very confusing, If you need help i recomend searching for an
access help forum. There is TONS of info you can get from these types of
websites.

For your database your going to have at least 2 tables. One table will be called
something like tbl_Customers and the other might be called tbl_invoices.
You will set your tables up to keep track of all information you want to hold
for their respective entity. You may want customer name and nothing else or you
may want their address, phone number..ect.. it's really up to you. You need to
set your fields up initially so it's a good idea to understand what you want
before you start. Good Database design is mostly done before you actually make
the database.

You will need a unique identifier for your customers (usually an auto generated
number) Then you will create a link so that when you add an invoice to your
invoice table you can link it to the customer table based on the customer's
unique ID.

If you need more help or need ideas or to know how to do something (or maybe
some screen shots) feel free to email me.
http\\rangefindecamera.50webs.com

Hi,

I came to know about this group from Martin Fowler's article about "Evolutionary
Database Design".

I have been looking into this subject lately as I have found that it's become a
pain point for us especially that we've been developing multiple features in
parallel on the same system.

I found the article above to be quite useful, although I'd have loved to hear
more about the concept of "lineages" and how to manage them on multiple
environments, i.e. SIT, UAT, etc.

I have a question, though, about the database refactoring part and the idea of
accumalating incremental scripts. Before reading the article, I had come to a
conlcusion that this approach is far from being perfect. The reason is, if some
incremental script is partially rolled back by a subsequent one, e.g. someone
added three columns to a table then it was decided to remove one of them, then
it becomes the responsibilty of the DBA to manually come up with the final
incremental script which should actually be executed on the testing environment.

I assume it's not a good idea when moving to production to actually add the
column and then remove it, but rather to drop it from the original script
altogether.

I had thought that using a tool to do that would be better. So instead, use a
tool which can store a version of the schema/database and then after the
iteration/release is complete, ask the tool to generate the delta script.

What do you think about this approach? Have you faced the issue above and how
did you solve it?

Your feedback is appreciated.

Best regards.

This is exactly how we do our deployments. We develop until feature
complete. Then we run a Diff Tool (Visual Studio's Data Dude) to generate
our Delta Script. During development we incrementally add to a DML script
for any reference, meta data that needs to go along with the release - HTH

On Tue, Jun 2, 2009 at 2:15 PM, tnabil76 <tarekmnabil@...> wrote:

>
>
> Hi,
>
> I came to know about this group from Martin Fowler's article about
> "Evolutionary Database Design".
>
> I have been looking into this subject lately as I have found that it's
> become a pain point for us especially that we've been developing multiple
> features in parallel on the same system.
>
> I found the article above to be quite useful, although I'd have loved to
> hear more about the concept of "lineages" and how to manage them on multiple
> environments, i.e. SIT, UAT, etc.
>
> I have a question, though, about the database refactoring part and the idea
> of accumalating incremental scripts. Before reading the article, I had come
> to a conlcusion that this approach is far from being perfect. The reason is,
> if some incremental script is partially rolled back by a subsequent one,
> e.g. someone added three columns to a table then it was decided to remove
> one of them, then it becomes the responsibilty of the DBA to manually come
> up with the final incremental script which should actually be executed on
> the testing environment.
>
> I assume it's not a good idea when moving to production to actually add the
> column and then remove it, but rather to drop it from the original script
> altogether.
>
> I had thought that using a tool to do that would be better. So instead, use
> a tool which can store a version of the schema/database and then after the
> iteration/release is complete, ask the tool to generate the delta script.
>
> What do you think about this approach? Have you faced the issue above and
> how did you solve it?
>
> Your feedback is appreciated.
>
> Best regards.
>
>
>


[Non-text portions of this message have been removed]

Hello and welcome.

Why are you making this assumption? If you add three columns and then later drop
one, it doesn't matter. There is no need for DBA intervention to create an
alternative migration. It is more work and more risk to maintain more than one
database migration. You should always apply database changes with the same
migration. By doing this, you don't need to worry about multiple environments
because all database migrations are the same.

What we do is a sort of "poor-man's migration." In each script, it inserts a row
into a table called "SchemaVersion" so we can see what  incremental version the
database is currently at. We have a JUnit test to make sure we don't forget to
add that insert to each script.

Every so often, we "re-base" our baseline database to match what is currently in
production.  Our DBA extracts the DDL and we replace all of our incremental
changes in development that have been applied to production. It basically
squishes all of our changes that have made it to production into a new baseline
script. (This eventually cleans up all of the "three column/two column"
business.)

Hope this helps.
Tim Andersen



--- In agileDatabases@yahoogroups.com, "tnabil76" <tarekmnabil@...> wrote:
>
> Hi,
>
> I came to know about this group from Martin Fowler's article about
"Evolutionary Database Design".
>
> I have been looking into this subject lately as I have found that it's become
a pain point for us especially that we've been developing multiple features in
parallel on the same system.
>
> I found the article above to be quite useful, although I'd have loved to hear
more about the concept of "lineages" and how to manage them on multiple
environments, i.e. SIT, UAT, etc.
>
> I have a question, though, about the database refactoring part and the idea of
accumalating incremental scripts. Before reading the article, I had come to a
conlcusion that this approach is far from being perfect. The reason is, if some
incremental script is partially rolled back by a subsequent one, e.g. someone
added three columns to a table then it was decided to remove one of them, then
it becomes the responsibilty of the DBA to manually come up with the final
incremental script which should actually be executed on the testing environment.
>
> I assume it's not a good idea when moving to production to actually add the
column and then remove it, but rather to drop it from the original script
altogether.
>
> I had thought that using a tool to do that would be better. So instead, use a
tool which can store a version of the schema/database and then after the
iteration/release is complete, ask the tool to generate the delta script.
>
> What do you think about this approach? Have you faced the issue above and how
did you solve it?
>
> Your feedback is appreciated.
>
> Best regards.
>

Hello,

My experience with evolutionary database development based on incremental
scripts is that it is better to actually run the scripts on production
exactly as they evolved during development. Repeatability is one of the
biggest benefits of having a database evolve using incremental scripts.

Besides, what are you really going to lose by adding a field and then
deleting it on production? The obvious answer is time, but you may actually
lose more time generating the deltas from production. Other factors may be
present, like fragmenting of the physical structures, etc. but these would
most likely be easily solved using the tools provided to you by your
database vendor.

In a pure eveolutionary database development team a DBA shouldn't be allowed
to modify the database structure in an ad-hoc manner. Involving a DBA in
anything more than just approving the incremental scripts is risky, as it
goes against the idea of repeatability.

Anyway, if you are interested in tools that generate deltas, there are a
number of offerings out there, including SQL Compare, DB Ghost (for SQL
Server), Microsoft's DB Dude, etc.

However, I believe the way of synching the development and production
databases that these tools promote, is exactly the ad-hoc way of deploying a
database that leads to all the troubles evolutionary DB development tries to
avoid.

Regards,
Milen Kovachev

On Tue, Jun 2, 2009 at 8:15 AM, tnabil76 <tarekmnabil@...> wrote:

>
>
> Hi,
>
> I came to know about this group from Martin Fowler's article about
> "Evolutionary Database Design".
>
> I have been looking into this subject lately as I have found that it's
> become a pain point for us especially that we've been developing multiple
> features in parallel on the same system.
>
> I found the article above to be quite useful, although I'd have loved to
> hear more about the concept of "lineages" and how to manage them on multiple
> environments, i.e. SIT, UAT, etc.
>
> I have a question, though, about the database refactoring part and the idea
> of accumalating incremental scripts. Before reading the article, I had come
> to a conlcusion that this approach is far from being perfect. The reason is,
> if some incremental script is partially rolled back by a subsequent one,
> e.g. someone added three columns to a table then it was decided to remove
> one of them, then it becomes the responsibilty of the DBA to manually come
> up with the final incremental script which should actually be executed on
> the testing environment.
>
> I assume it's not a good idea when moving to production to actually add the
> column and then remove it, but rather to drop it from the original script
> altogether.
>
> I had thought that using a tool to do that would be better. So instead, use
> a tool which can store a version of the schema/database and then after the
> iteration/release is complete, ask the tool to generate the delta script.
>
> What do you think about this approach? Have you faced the issue above and
> how did you solve it?
>
> Your feedback is appreciated.
>
> Best regards.
>
>
>


[Non-text portions of this message have been removed]

Hello,

My experience with evolutionary database development based on incremental
scripts is that it is better to actually run the scripts on production exactly
as they evolved during development. Repeatability is one of the biggest benefits
of having a database evolve using incremental scripts.

Besides, what are you really going to lose by adding a field and then deleting
it on production? The obvious answer is time, but you may actually lose more
time generating the deltas from production. Other factors may be present, like
fragmenting of the physical structures, etc. but these would most likely be
easily solved using the tools provided to you by your database vendor.

In a pure evolutionary database development team a DBA shouldn't be allowed to
modify the database structure in an ad-hoc manner. Regarding database structure,
involving a DBA in anything more than just approving the incremental scripts is
risky, as it goes against the idea of repeatability.

Anyway, if you are interested in tools that generate deltas, there are a number
of offerings out there, including SQL Compare, DB Ghost (for SQL Server),
Microsoft's DB Dude, etc.

However, I believe the way of synchronizing the development and production
databases that these tools promote, is exactly the ad-hoc way of deploying a
database that leads to all the troubles that evolutionary DB development tries
to avoid.

Regards,
Milen Kovachev

--- In agileDatabases@yahoogroups.com, "timander37" <timander@...> wrote:
>
> Hello and welcome.
>
> Why are you making this assumption? If you add three columns and then later
drop one, it doesn't matter. There is no need for DBA intervention to create an
alternative migration. It is more work and more risk to maintain more than one
database migration. You should always apply database changes with the same
migration. By doing this, you don't need to worry about multiple environments
because all database migrations are the same.
>
> What we do is a sort of "poor-man's migration." In each script, it inserts a
row into a table called "SchemaVersion" so we can see what  incremental version
the database is currently at. We have a JUnit test to make sure we don't forget
to add that insert to each script.
>
> Every so often, we "re-base" our baseline database to match what is currently
in production.  Our DBA extracts the DDL and we replace all of our incremental
changes in development that have been applied to production. It basically
squishes all of our changes that have made it to production into a new baseline
script. (This eventually cleans up all of the "three column/two column"
business.)
>
> Hope this helps.
> Tim Andersen
>
>
>
> --- In agileDatabases@yahoogroups.com, "tnabil76" <tarekmnabil@> wrote:
> >
> > Hi,
> >
> > I came to know about this group from Martin Fowler's article about
"Evolutionary Database Design".
> >
> > I have been looking into this subject lately as I have found that it's
become a pain point for us especially that we've been developing multiple
features in parallel on the same system.
> >
> > I found the article above to be quite useful, although I'd have loved to
hear more about the concept of "lineages" and how to manage them on multiple
environments, i.e. SIT, UAT, etc.
> >
> > I have a question, though, about the database refactoring part and the idea
of accumalating incremental scripts. Before reading the article, I had come to a
conlcusion that this approach is far from being perfect. The reason is, if some
incremental script is partially rolled back by a subsequent one, e.g. someone
added three columns to a table then it was decided to remove one of them, then
it becomes the responsibilty of the DBA to manually come up with the final
incremental script which should actually be executed on the testing environment.
> >
> > I assume it's not a good idea when moving to production to actually add the
column and then remove it, but rather to drop it from the original script
altogether.
> >
> > I had thought that using a tool to do that would be better. So instead, use
a tool which can store a version of the schema/database and then after the
iteration/release is complete, ask the tool to generate the delta script.
> >
> > What do you think about this approach? Have you faced the issue above and
how did you solve it?
> >
> > Your feedback is appreciated.
> >
> > Best regards.
> >
>