 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Struts - A MVC web framework | | Tomcat - JSP/Servlet container | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | | JSP - A mailing list about Java Server Pages specification and reference | |
Struts & Hibernate
|
|
|
| | | domain model to design | domain model to design 2004-08-11 - By Michael New
Back
domain model to designUse XP!
User stories will give you requirements and estimates, and technical design
will evolve as the system is coded.
Mike New
-- -- Original Message -- --
From: Pradeep Kumar
To: J2EE-INTEREST@(protected)
Sent: Wednesday, August 11, 2004 12:40 AM
Subject: domain model to design
Greetings group,
We used to TogetherJ to get our business domain model (or problem domain
model) using color modelling. We are not sure about the best approach to go for
the design (next step). We would like to retain most of the business model
during the design phase. We are planning to use Hibernate for persistence and
stateless session beans as facades. Our business objects are between these 2
layers. Also, our framework classes are in place.
The confusion is mainly due to 2 archetypes (actors and moment intervals). We
are not sure if they should be persisted or remain as POJOs (non persisted
POJOs) or remove them fully/partly based on business context.
We looked at FDD (feature driven development); however, we are not getting a
clear picture.
Does anyone know of a good methodology for transforming the business model to
technical design?
Thanks.
Pradeep
===========================================================================
To unsubscribe, send email to listserv@(protected) and include in the body of
the message "signoff J2EE-INTEREST". For general help, send email to listserv
@(protected) and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to listserv@(protected) and include in the body
of the message "signoff J2EE-INTEREST". For general help, send email to
listserv@(protected) and include in the body of the message "help".
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>domain model to design</TITLE>
<META http-equiv=Content-Type content="text/html; charset=windows-1252 (See http://ows-1252.ora-code.com)">
<META content="MSHTML 6.00.2800.1458" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Use XP!</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>User stories will give you requirements and
estimates, and technical design will evolve as the system is coded.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Mike New</FONT></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT:
#000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">-- -- Original Message -- -- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=TC00328@(protected) href="mailto:TC00328@(protected)">Pradeep
Kumar</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=J2EE-INTEREST@(protected)
href="mailto:J2EE-INTEREST@(protected)">J2EE-INTEREST@(protected)</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, August 11, 2004 12:40
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> domain model to design</DIV>
<DIV><BR></DIV>
<P><FONT size=2>Greetings group,</FONT> </P>
<P><FONT size=2>We used to TogetherJ to get our business domain model (or
problem domain model) using color modelling. We are not sure about the best
approach to go for the design (next step). We would like to retain most of
the
business model during the design phase. We are planning to use Hibernate for
persistence and stateless session beans as facades. Our business objects are
between these 2 layers. Also, our framework classes are in place.</FONT></P>
<P><FONT size=2>The confusion is mainly due to 2 archetypes (actors and
moment
intervals). We are not sure if they should be persisted or remain as POJOs
(non persisted POJOs) or remove them fully/partly based on business
context.</FONT></P>
<P><FONT size=2>We looked at FDD (feature driven development); however, we
are
not getting a clear picture. </FONT></P>
<P><FONT size=2>Does anyone know of a good methodology for transforming the
business model to technical design? </FONT></P>
<P><FONT size=2>Thanks.</FONT> <BR><FONT size=2>Pradeep</FONT>
</P>=========================================================================
==
To unsubscribe, send email to listserv@(protected) and include in the body
of
the message "signoff J2EE-INTEREST". For general help, send email to
listserv@(protected) and include in the body of the message "help".
<P></P></BLOCKQUOTE></BODY></HTML>
===========================================================================
To unsubscribe, send email to listserv@(protected) and include in the body
of the message "signoff J2EE-INTEREST". For general help, send email to
listserv@(protected) and include in the body of the message "help".
<p>
|
|
|
