LehighUML Project

1
LehighUML Project

• John Pequeno, Adam Balgach,
• Sally Moritz Professor Glenn Blank

2
Extreme Programming XP Method

• Iterative Development
• Iterations measured in minutes to weeks
• Time of iteration dependent on project type.
• LehighUML Iterations of 1 to 3 weeks
• Not by any means a rigid Software Process. Very
  open to interpretation, and custom
  implementations based on the requirements of a
  specific project.

3
Extreme Programming Reqs.

• The few XP Requirements that are a must are
• Short iterations of
• Req Solicitation-gt Iteration Design -gt
  Development -gt Testing -gt Acceptance Testing
• Very close communication with customer.

4
Extreme Programming Iteration
5
Integrated Development With Customer

• One of the few requirements of extreme
  programming (XP) is to have the customer
  available. Not only to help the development team,
  but to be a part of it as well. All phases of an
  XP project require communication with the
  customer, preferably face to face, on site. It's
  best to simply assign one or more customers to
  the development team ExpremeProgramming.com
• LehighUML Team Customer Sally Moritz Glenn
  Blank

6
Customer Bi-Weekly Meeting Goal

• Test for problems and bugs with current iteration
• Acceptance Testing
• Problem/bug fixes done for prior iterations
• New Features implemented in this iteration
• Decide on project velocity/new User Stories (i.e.
  Release Plan for next iteration).

7
Initial Brainstorming of Features

• Brainstormed a list of possible features to
  implement
• brainstorm.txt

8
Initial copy of User Stories

• When project first started we decided on an
  initial Requirements/User Stories document.
• Through the iterations of the XP cycle, changed
  the User Stories as required by customer.
• User Stories.doc

9
And After Months of Iterations

• The final product was delivered after some 15
  Iterations.
• Strengths of this Software Process
• No disconnect of customer to product
• Customer gets a product very close to what they
  expect.
• Fast Cycles offer low overhead, and allow for
  maintenance iterations easily if design changes
  need to be made.

10
Important References

• Eclipse.org home - Open Source Java IDE
• Most popular Java IDE.
• Very VERY good IDE. Most integrated Plug-In
  development environment weve ever seen.
• Books
• The Java Developers Guide to ECLIPSE
• Shavor, DAnjou, Fairbrother, kehn, Kerllerman,
  McCarthy
• Very good book with great section specifically on
  Eclipse Plug-In Development

11
Graphical Editing Framework

• GEF - Graphical Editing Framework for Eclipse
• The Entire Plug-In was built on the GEF
  framework.
• Allows for very easy creation of Logical Editors
  in Eclipse.
• Entire LehighUML Project built on top of GEF
  Framework
• GEF Project Overview with Examples
• A Shape Diagram Editor
• Very good starting point
• Displaying a UML Diagram with Draw2D in GEF

12
Product Presentation

• Lets take a look through the product, and
  briefly analyze some of its design.

13
Conclusions

• Looking for a few good men
• Possible features to work on next.
• UML Class Diagram Enhancements
• 2-Way Reverse Engineering including Code to
  Diagrams
• UML Sequence Diagrams
• Any Questions?