Stefan Roock

Agile Project Controlling

Agile methods like eXtreme Programming (XP, cf. [2]) are grass rooted. They derive from practicioneers and focus on their needs. Therefore, at the beginning, project controlling was not in the focus of agile methods. The paper shows how to integrate simple mechanisms for project controlling. These mechanisms address both developers and management needs.

From documents to applications via frameworks (poster session): the tools and materials approach

2 THE BASIC IDEA The Tools & Materials approach (see [2]) guides the developer through the entire process. To realize this, it provides an applicationand task-oriented methodology for software development. The main idea behind the approach is to realize high use quality of software. This involves the following aspects: • The functionality of the system is oriented to the tasks of the application domain. • Operation of the system is user-friendly. • The process and steps defined in the system can be easily adapted to actual requirements in accordance with the work situation. Based on object-oriented design and construction techniques, the T&M approach unifies various components such as a leitmotif with design metaphors, applicationoriented documents and an evolutionary approach using prototyping. Even the implementation is supported by a complete Java-based application framework, called JWAM (WAM is a German acronym for the Tools & Materials approach). The basic idea behind the approach is to achieve a structural similarity between the application domain and the software system. The benefit obtained is a close correspondence between the model of core application concepts and the software architecture. This structural similarity enhances maintainability, extensibility and other aspects of quality.

Operating and window systems will never strike back or independence day for Java developers

With the use of Java and the JDK*, independence from specific platforms (operating systems and window systems) becomes possible. For the development of commercial applications however, Java and the JDK are not enough, and tools such as a GUI-builder are needed. When employing a GUI-builder, new dependencies on the builder-generated code have to be considered. Independence is an important prerequisite for enabling portability and reusability. There are many GUI-builders on the market and it is impossible to say which will end up being successful. However, integration of existing programs designed with different GUI-builders is an ongoing problem. We have designed and implemented a Java framework, which uses a GUI-builder independent format to store GUI resources. This framework can be combined with any GUI-builder that supports JavaBeans.