[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [epf-dev] RE: Database Design content in OpenUP
|
Brian
OK - no problem. I'll add a guideline for now and we can look at the other stuff for the next release.
Ana rightly points to the Data View which we have already defined in the Architecture content - which itself is a viewpoint on the Design, so it should be consistent.
cheers
Mark
Mark Dickson
Principal Solution Architect
SAE Practice
m 0780 1917480
w
www.xansa.come
mark.dickson@xxxxxxxxx
-----epf-dev-bounces@xxxxxxxxxxx wrote: -----
To: <Mark.Dickson@xxxxxxxxx>
From: "Brian Lyons" <blyons@xxxxxxxxxxxxx>
Sent by: epf-dev-bounces@xxxxxxxxxxx
Date: 09/11/2006 02:13PM
cc: epf-dev@xxxxxxxxxxx
Subject: [epf-dev] RE: Database Design content in OpenUP
hiho,
At this point less than three weeks from our release date, I wouldn?t want to do any more than add a guideline or two that do not significantly affect the existing content.
For the scale of OpenUP/Basic, I don?t consider the Data Model anything more than a part of the design tuned to support that context. But perhaps we can initiate a discussion of this during a face-to-face meeting with the OpenUP leadership after we get through this release. I think we need to do a session on the coverage of both data and UI in the Basic process.
I support Ana?s idea that the data model could be considered a ?view? in the architecture. But that view would still reside in the design.
---------- b
From: Mark.Dickson@xxxxxxxxx [mailto:Mark.Dickson@xxxxxxxxx]
Sent: Monday, September 11, 2006 8:13 AM
To: Brian Lyons
Cc: epf-dev@xxxxxxxxxxx
Subject: Database Design content in OpenUP
I'm looking at bug 154625 - Database Modeling content in OpenUP.
I had intended simply to add a new guideline under Development with content modified from RUP for Small Projects Data Model description.
Looking in more detail, I'd like us to consider
- Adding a new Step to the Design Solution Task called Design the Database (that can be ignored if there are no persistence requirements for the project) OR modifying the existing text to make it clearer that data design is part of the work. Personally, I prefer adding the step.
- Add a new Guideline called "Database Design" based on the RUP Task of the same name.
- Add a new visual modeling Guideline called Data Modeling, based on the RUP Guideline for Data Model.
Do you think that the data model should be described as a part of the Design product or called out as a product in it's own right? I tend to think that the latter is more consistent with our overall approach.
Let me know what you'd like to do and I'll crack on and make the changes,
Whilst this email has been checked for all known viruses, recipients should undertake their own virus checking as Xansa will not accept any liability whatsoever.
This email and any files transmitted with it are confidential and protected by client privilege. It is solely for the use of the intended recipient.
Please delete it and notify the sender if you have received it in
error. Unauthorised use is prohibited.
Any opinions expressed in this email are those of the individual and not
necessarily the organisation.
Xansa, Registered Office: 420 Thames Valley Park Drive ,
Thames Valley Park , Reading , RG6 1PU , UK .
Registered in England No.1000954.
t +44 (0)8702 416181
w www.xansa.com
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
Whilst this email has been checked for all known viruses, recipients should undertake their own virus checking as Xansa will not accept any liability whatsoever.
This email and any files transmitted with it are confidential and protected by client privilege. It is solely for the use of the intended recipient.
Please delete it and notify the sender if you have received it in
error. Unauthorised use is prohibited.
Any opinions expressed in this email are those of the individual and not
necessarily the organisation.
Xansa, Registered Office: 420 Thames Valley Park Drive,
Thames Valley Park, Reading, RG6 1PU, UK.
Registered in England No.1000954.
t +44 (0)8702 416181
w www.xansa.com
