users
[Top] [All Lists]

Cinjug January 22nd meeting

To: users@xxxxxxxxxx
Subject: Cinjug January 22nd meeting
From: "Mike Ball" <mwball@xxxxxxxxx>
Date: Wed, 10 Jan 2007 09:31:44 -0500
Delivered-to: mailing list users@cinjug.org
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=OQziAxk9/MFJaI+oo3owysOXL50eyzjCtmnmN1uqwyQlQD3r954+SZqLkyxh/fVHiTgccALvJvDUfTG3lnRx7ojDgFtaiCWYWYzPu8tDFwQNoGnabElzMrFAPL1nfxMo+CqiaHcN/kzNviOor5S7ykZueg8euTEZbWZKNRy/aCA=
Mailing-list: contact users-help@cinjug.org; run by ezmlm
IMPORTANT: The cinjug meeting this month has been rescheduled for the 22nd.

Time: 6pm for food, 6:30 for presentation
Location: Max Training - Mason
Topic: J2EE Architecture Review
Speaker:  Al Mannarino - Lead Systems Engineer for CodeGear(formally
Borland's Developers Tools Group)
Sponsor: Borland
Door Prize: JBuilder 2007 for Eclipse

J2EE Architecture Review
========================
- Using a Find-Fix-Avoid paradigm, we'll focus on finding J2EE
problems in an existing application, fixing those problems with
minimal effort, and avoiding the problems in future applications.

- Apply automated software inspection and run-time analysis tools to
help identify common problems that can cause performance and
scalability issues. Discuss the problems found and demonstrate how
tools can help accelerate the implementation of appropriate solutions.
Discuss what development teams can do to avoid the problems on future
projects.

Find:
=====
*       Apply software quality audits (check for common coding errors
and enforce standards)
*       Apply software quality metrics (measure object-oriented design
characteristics such as complexity, cohesion, and coupling)
*       Reverse engineer structure and behavior (Reverse engineer
class diagrams and generated sequence diagrams)
*       Apply Application Quality Analyzer (analyze J2EE components
for performance issues, detect misuses of J2EE, identify errors)
*       Discuss discovered problems (excessive temporary objects, dead
code, highly complex methods, etc.)
*       Generate documentation

Fix:
====
*       Discuss principles of software remodeling (audits/metrics,
design patterns, refactoring)
*       Create JUnit tests (code with confidence)
*       Apply simple refactoring (modify design without breaking
existing code, verify impact of refactoring)
*       Apply pattern-based refactoring

<Prev in Thread] Current Thread [Next in Thread>
  • Cinjug January 22nd meeting, Mike Ball <=