1. Introduction

yoinkscreechedInternet και Εφαρμογές Web

13 Νοε 2013 (πριν από 3 χρόνια και 10 μήνες)

83 εμφανίσεις

eFusion

Object

Design Document


March 28, 2005


Software Engineering

Spring 2005

Section 1

Group 2


Group Manager:
Adelein Rodriguez

Yisell Diaz

Eduardo Soto

Eduardo Quan

Jose Cifuentes

Yaima Campos

Larissa Quintana



eFusion ODD
2

of
4

Outline

1. Introduction


1.1 Object de
sign trade
-
offs


1.2 Interface documentation guidelines


1.3 Definitions, acronyms, and abbreviations


1.4 References

2. Packages

3. Class interfaces





eFusion ODD
3

of
4

1. Introduction

e
Fusion consists of subsystems, which work separately but concurrently and interact wi
th
each other through subsystem calls. The object design phase of eFusion will serve as a
tool to take into considerations all the features of each subsystem and the interactions
among these different packages.


1.1.

Object design trade
-
offs

We made s
everal tr
ade
-
off decisions in order to

maximize data persistence and minimize
database connection delays
. In ord
er to implement storage of persistent

objects,
we
decided to
re
-
use

existing
database components. Specifically, MySQL
was chosen
since

it is
a
reliable o
pen
-
source
relational
database
and

provides

maintainability

to the system

as it transparently
benefits from

database
upgrades
and
tune
-
ups.
When deciding on
memory/
response
-
time
issues
, we realized that e
ntity objects
should

be
mapped
directly
into
r
ows in

the
relational
database
as

soon as
some persistent storage/
retrieval
is

needed.
Although t
his
implies

some

database
access slowdown
,

it
is more effective in terms of
data reliability which is the most i
mportant concern of our system and its audience.

It a
lso
helps maintain data consistency if an un
expected system failure occurs.
To minimize
connection delays we
use

Tomcat’s pooling manager, which allows an application to
have
access to a

pool

of opened connections.
Java Servlets and JSPs
w
ere

chosen
as the

technology for the solution domain
since

it provides an effective way of combining an
applications presentation and logic (boundary and control objects) for the web medium.

Moreover, Java technology has wide support from the open
-
source

community and
it
i
s
multiplatform
,

which adds portability to the system.


1.2. Interface documentation guidelines

In order to make uniform communication between the developers of eFusion we have
adopted specific interface documentation guidelines and conventions. First all

classes are
named with singular nouns or noun phrases, with each word commencing with a capital
letter. A similar convention will be used for naming all instances of the classes, but using
lower case words for the first letters. Names of class methods wil
l be in lower case, as
well as all class attributes, only if they contain more than one word, subsequent words
will be capitalized.





eFusion ODD
4

of
4

1.3. Definitions, acronyms, and abbreviations


ID: Identification

RAD: Requirements Analysis Document.

SDD: System Desi
gn Document

ODD: Object Design Document.

GUI: Graphical User Interface.

JSP: Java Server

Pages


1.4. References



Problem Statement



RAD



SDD



http://java.sun.com


2. Packages

See attachment