X-Abuse-Report: abuse@teranews.com
Message-ID: <b1fb4ee212d4ffa3d1c040f73fa01bbc@news.teranews.com>
Path: newssvr20.news.prodigy.com!newsmst01.news.prodigy.com!prodigy.com!newsfeed.telusplanet.net!newsfeed.telus.net!news3.optonline.net!newsfeed-east.nntpserver.com!nntpserver.com!news.teranews.com!not-for-mail
Date: Fri, 10 Oct 2003 04:18:22 GMT
Lines: 27
From: "Mark Wright" <markwright@hotpop.com>
Newsgroups: comp.databases.theory
References: <1efdad5b.0310091820.7080843a@posting.google.com>
Subject: Re: Modelling databases with Use Cases?
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Xref: newssvr20.news.prodigy.com comp.databases.theory:21699

"Ryan Gaffuri" <rgaffuri@cox.net> wrote in message
news:1efdad5b.0310091820.7080843a@posting.google.com...
> What experiences have you had with Use Cases and then building a
> relational model off of them?
>
> Does this help if you have an object oriented front end and you need
> some way to map to the relational back end?

Ryan,

In my experience use cases are an effective way to help define and
communicate requirements and business rules. The clearer a system is
understood the easier it is to model.

They are simply a formal way to describe process interactions in plain
language. There is no magic about them. They just help us understand who
does what and why.

They get mentioned a lot lately in the same sentence as object oriented
programming because the UML has diagrammatic support for them and both
the UML and use cases are components of popular OOP analysis and design
methodologies.

Regards,
Mark


