Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Changed macro table to normal table


If you are wondering why you should use SBForge as hosting platform, here are the arguments.

Table of Contents
Children Display

Collaborative tools

Modern approaches to software development are based on a teambased collaberative effort, opposed to the more classical silo based partitioning of work in a project. The SBForge development platform are heavily focus on lowering the barriers to sharing of information.

The central idea is to provide a shared updated information model, which can be accessed by all project members. Without a collaborative tooling model, the sharing of information will be done on a occasional and general basis, mostly face-to-face, by email or over the telephone. In the collaborative tooling setup all the project information can be accessed continuously and with as many details as need . 

Classical project

Collaborative project

Collaberative and
integrated project

Image Modified

Image Modified

Image Modified

The SBForge information model isn't confined to individual project, so the information can be aggregated form across entire the SBForge site. Other relevant context could be information regarding a specific user (me), organisation unit (SBForge), content type (forum), process area (test) or just plain 'googling' for information to a specific question.


A major is the ability to integrate data across the project tools. This capability is critical to the concept of focused views. Without integrated tools you would be limited to access the information contained in a single application at a time, eg. your information context is defined by the tool. 

Fragmented project information in non-integrated toolsIntegrated information model

Image Added

Image Added

If you on the other hand use a sufficiently integrated tooling platform, like SBForge, information will not be localized to the individual tool, but you can instead access the whole of the information cloud, focusing on the model aspect specific on your current role or problem you are working on. An example of this is accessing the information related to a specific feature. In a non-integrated information system you would properly access information through the documents containing the feature aspects, this could be test documentation, QA documentation, task documentation, code, etc, which would provide a very fragmented view of the feature if you could find all the relevant information at all. In a integrated information model you would be able to focus directly on the features, with the tools aggregation all the feature releated information from the different project models into a focused view. You can of course still view the information in a process focused, user focused  or any other way you require.

Classical process focused documentation

Dynamically generated feature centric view

Image Modified

Image Modified


We have tried to find tools enabling us to tailor the tools to suite our specific needs. The means all the tools making up the SBForge platform are highly configurable, both on global and project basis. The vast majority of this configuration is easily done through the tools individual GUI's, which is necessary for us to use the customization possibilities in practice .   


The advantages of the individual tools are listed below:

Content by Label
cqllabel = "tool-benefits" and space = "APP"