Level: Introductory Granville Miller (rmiller@togethersoft.com), Mentor, TogetherSoft
01 Jun 2002 Welcome to Java modeling, a monthly column for Java developers that examines best practices in the UML, a standard notation for modeling object-oriented systems. The column begins with some introductory articles to build a foundation, but will quickly move to more advanced applications. All of the articles are presented here for your convenience. A UML workbook, Part 4
June 2002
Level: Introductory
Granville Miller re-opens the UML workbook for an in-depth discussion of one of the fundamental components of the use case diagram: the actor. The actor is not only essential in UML modeling, it can also play an important role in creating Java applications and may even suggest patterns in J2EE application design. Follow along as Granville uses sequence and class diagrams to explain the role of the actor in use case diagramming and Java application development. Holonic software development, Part 2
October 2001
Level: Introductory
Granville Miller continues his discussion of holonic software development, with a conceptual overview of requirements gathering. Find out how the four most common requirements gathering processes -- features, user stories, use cases, and the traditional software requirements specification -- fit into the larger context of an agile software development process. Holonic software development, Part 1
August 2001
Level: Introductory
Granville Miller temporarily abandons the topic of requirements gathering for one more compelling: holonic software development. Find out how this method complements and extends the tenets of the agile development movement, and how its emergence into mainstream development circles may alter the education of software developers, as well as the practice of software development. A UML workbook, Part 3
June 2001
Level: Introductory
Granville leads you into the gray zone between modeling and method, with a look at requirements gathering via use case modeling. In particular, he focuses on the relationship between user interfaces, system interfaces, and use case descriptions. While tempting to do so, it is generally considered bad form to include user interface logic in a use case. Follow along as Granville uses sequence diagrams and system interfaces to show you why. A UML workbook, Part 2
June 2001
Level: Introductory
Granville continues his discussion of the Unified Modeling Language and sequence diagramming. He examines the role of conditional logic in sequence diagramming and discusses why you might choose to include or exclude conditions and loops from a diagram. Granville also describes the two forms of sequence diagram -- generic and instance -- and explains their respective applications in the development cycle. A UML workbook, Part 1
May 2001
Level: Introductory
In this first installment of his new column, Granville Miller introduces one of the building blocks of the Unified Modeling Language: sequence diagramming. Sequence diagrams are used throughout the design process to demonstrate the internal interactions between actors and objects as a system executes over time. Follow along with Granville as he creates one of these diagrams, using a loan processing application as his example. | 
