• Introduction

  Specification and team management examples

  Generation examples

• Requirement

  An item of a requirement specification

• Use case

  A requirement associated to a use case

• Use case actor

  The actor of a use case

• Bundle

  A collection of internationalization items

• Bundle entry

  A single internationalization item

• Control

  A control of the nodes application

• Swing control

  An extension, a swing control

• Page

  A page of the nodes application

Introduction

The following examples may be divided into two groups.

Specification and team management examples

This includes requirements, use cases and associated actors. Not shown here, but in the same category you could create test cases, test runs, tasks, bugs and more.

Generation examples

Other virtual pages are used to describe elements of the architecture of the system.

The structure imposed by the node type schema not only allows to enforce a systematic approach for the architectural elements. As the repository can be accessed by external builds, either by RMI or by the applet communication framework, the information can be used to generate artifacts. This

• improves consistency between specification and implementation.
• allows to trace the requirements, i.e. to find, which requirement is implemented in which implementation artifact(s), if requirement virtual pages are linked to the corresponding architecture virtual pages which in turn will be connected to the generated artifacts.

  The application, at least its functionally relevant parts, is built around an architectural skeleton described in the repository.

• comes with the common advantages of generation: High consistency within the application, maintenance of whole groups of architectural components by modifying the generation procedures.

Integration

These examples have been selected to demonstrate the intention of the system.

Combining the two groups of documents in one repository will allow all participants of the software lifecycle to have a common view of the software product.

All parts of the product, that have functional impact will be fully specified in a publicly available and understood medium. They will no longer be located in implementation specific artifacts not visible to all people that take part in the development.

Conventions

All virtual pages will be described in three sections

• A general introduction describing the purpose of the page.
• A chapter describing the schema (node type) of the page. In this chapter, the notation of the custom_nodetypes.xml will be used. For a short overview of the meaning, please compare the jackrabbit description, the specification of the JCR, which includes the node types, can be found at sun, JSR-170 and JSR-283.
• A chapter describing the template, that is, the page layout and its mapping to node type elements. For this, screenshots of the template assistant have been used.

  The mapping can be determined from the left explorer panel part of the screenshot. It displays the HTML element structure. Mappings have been added in gray to the corresponding HTML element in the tree view, in addition, the icon of the element is highlighted in blue/gold. The node type of referenced nodes is added in green.