Re: [JXTA discuss] Project Proposal: JXTA-Ruby - JXTA for Ruby in Constrained Environments

--=-8UKti37bx+61bG2/z0kQ
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2005-08-16 at 07:45 -0700, Shane Isbell wrote:
> Hi Henry,
>=20
> What we need to discuss is how the software process should be done for
> this project. The way I am seeing it, we have two separate
> subprojects, the infrastructure level and the application level. The
> application level API should be simple and not have much of a concept
> of pipes or protocols. It just has message senders, content receivers,
> etc. The infrastructure API allows more control for developers who
> understand JXTA.
>=20

I agree we should have an easy to understand/use API. I don't have ideas
on how can they be separated, maybe we can discuss later with some
concrete proposal. :-)

> I follow the RUP process for most projects because it results in a
> good domain model and traceability. I have not seen as much benefit,
> however, employing RUP for infrastructure design. We should break this
> up into two groups and then have an integration effort where we use
> the infrastructure API to implement the application API. Thoughts?
>=20

Same here. I don't really follow the process, typically I will just have
the class diagram and class definitions, along with some sequence
diagram to describe key scenarios. Plus state diagram if state machine
is involved.

The principal is to clearly identify/document what to be implemented and
how they interact/related.

Cheers,
--=20
Henry Jen the slowhog
http://blogs.sun.com/slowhog

--=-8UKti37bx+61bG2/z0kQ
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBDA2gRLNaoAyBG0PURAmevAJ0apBLKIfoyrexfkg03V0j1DXw/dACcCcnI
8CmLbMzMyGnaCs/3+suVQD0=
=OUvu
-----END PGP SIGNATURE-----

--=-8UKti37bx+61bG2/z0kQ--