Learn > Model & Process
The guilding process
|
Himalia models allow the developer to focus on the greatest impact activities. The following diagram shows in a schematic way, an activity and artifact map for the guilding process. When possible, the task is accompanied with a repository. Starting with a use case set, the developer generates a Navigation Model contemplating the initial use case set navigational requirements. After that, he applies a presentation scheme (using the Layout Models), and chooses the controls to use in each area for each navigational element. Finally, a user interface make-up can be made by creating specific themes and styles. 
The separation of aspects in the UI construction allows model-level reusability. For example, when defining Use Cases we can simply bring a “Sign In” template from the repository and adapt it to our particular scenario. When it is ready, we can resave it to the repository, in order to reuse it in a future process. In this case, reuse is occurring at requirements time, very early in the development process. The process is iterative, incremental and can jump from any activity to another. The above diagram represents the “normal flow,” even though we know that usually the flow is defined in each guilding process. The guilding process is very agile. Release notesTemplates and repositories are not supported in version 0.8 [beta]. |
| © Copyright 2006 Himalia. |