February 01, 2011
Mark Wielaard: New GPG key.
Finally created a new GPG key using gnupg. The old one was a DSA/1024 bits one and 8 years old. The new one is a RSA/2048 bits one. I will use the new one in the future to sign any release tarballs I might create. pub 2048R/57816A6A 2011-01-29 Key f...
More »
February 01, 2011
Andrew Hughes: [SECURITY] IcedTea6 1.7.8, 1.8.5, 1.9.5 Released!.
We are pleased to announce a new set of security releases, IcedTea6 1.7.8, IcedTea6 1.8.5 and IcedTea6 1.9.5.
This update contains the following security updates:
The IcedTea project provides a harness to build the source code from OpenJDK6 u...
More »
December/2024
Sun | Mon | Tue | Wed | Thu | Fri | Sat |
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 |
22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | | | | |
|
|
Agile Methods Applied in JSR Spec and Reference Implementation Development
The JCP site has published a new article, Agility: Definitions, Principles, and Practices for Today, written by Susan Mitchell. The article focuses on the agile methods that are being employeed by three JCP Spec Leads:
Ronald Toegl - JSR 321, Trusted Computing API for Java
Ed Burns - JSR 314, Java Server Faces 2.0
Emmanuel Bernard - JSR 303, Bean Validation
At first glance, it might seem strange to find agile software development methods applied within the context of a standards organization. Isn't it more natural, perhaps even more appropriate, for a standards organization to define a specification in detail prior to any implementation of the spec? On the other hand, it seems like simultanteous hands-on development could also be useful, since development complications that are not readily forseeable will show up earlier during the process of creating a reference implementation for the JSR.
Spec Lead Ronald Toegl believes the "implement first and specify later" apprach is the best for JSR 321:
To us, agility provides an efficient use of resources, short feedback cycles, and a chance to consider different approaches while still moving forward. It also allows us to take small, easy-to-reach steps.
The JSR 321 Expert Group started with a minimal prototype, from which Java interface definitions were extracted. After some discussion, these were released as an Early Draft. Currently, the team is implementing the interface...
Date: February, 01 2010
Url: http://www.java.net/blog/editor/archive/2010/02/01/agile-methods-applied-jsr-spec-and-reference-implementation-developme
Others News
|