 | 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 Pradeep Kumar
Back
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".
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2656.60">
<TITLE>domain model to design</TITLE>
</HEAD>
<BODY>
<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>
</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>
|
|
|
