Jump to: navigation, search

Changes


Internal:Customizing Guidelines

1,297 bytes added, 12:34, 24 November 2015
Created page with "This page contains guidelines and recommendations concerning various topics a service employee may come in touch with, like * {{UBIK}} customizing guidelines * {{UBIK}} admin..."
This page contains guidelines and recommendations concerning various topics a service employee may come in touch with, like
* {{UBIK}} customizing guidelines
* {{UBIK}} admin documentation
* Comos customizing guidelines
* Scripting guidelines
* Documentation
* Document management

Please do not hesitate to pass criticism on the author about the content or structure or if the reader misses a topic which should be covered in here.

== A few thoughts about the design process ==
The development of a new functionality might include the following phases:

# Conceptual phase
#* Define scope of required functionality
#* Identify relations to / effects on existing functionality
#* Design a data model (if required)

# Implementation phase
#* Use a separate development area
#* Stick to the UBIK, Scripting and Documentation guidelines

# Testing phase
#* Do the testing in the development first, but also in the productive area
#* Testing should be done by the customer or another person (if possible)
#* Keep records of the test results

# Documentation phase
#* Technical view: description how the functionality has been implemented technically (new / changed objects, data model, other relations, …)
#* User-specific view: description of the scope and application of the created functionality
10,686
edits