Child pages
  • Benefits of using the SBForge platform
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

If you need convince yourself or others why using SBForge as hosting platform, here are the arguments.

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

Integrated tools

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 i a single application at a time, eg. your information context is defined by the tool. 

Unknown macro: {table}
Unknown macro: {tr}
Unknown macro: {td}

Fragmented project information in non-integrated tools

Unknown macro: {td}

Integrated information model

Unknown macro: {td}

Unknown macro: {td}

Unknown macro: {tr}

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 project information cload, based on the current role or problem you are interessested in. 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. In a integrated information model you would be able to focus directly on the features, with the tools aggregation information from the different project models into a feature centric view. You can of course still view the information in a process focused -, user focus way or any other categorization of the project information.

Classical process focused documentation

Dynamically generated feature centric view


We have tried to find tools enabling us to tailor the tools to suite our specific needs. The all the tools making up the SBForge platform are therefore all very configurable, both on global and project basis. The vast majority of this configuration is easily done through the tools individual GUI's.   


All the tools used in SBForge are based on plugin architecture, allowing us to extend the functionality of the base applications, with the features suited for our needs.

Powerful permission model

Because of the integrated nature of the SBForge information model an advanced permission model needs to be part of the setup. This is achieved by using tools with powerful permission configurations, couple to a central user management system (Crowd).


Even though the SBForge platform consists of a number of heavily integrated tool, it is not required that you only use SBForge tools in your project. You may chose to use other tools besides the ones provided by SBForge, this will in fact proberly be the case for most of the projects hosted at SBForge.

Open Source friendly tools

All of the tools used at SBForge are provided free to the Open Source community. As a result many Open Source projects are based on the tools used at SBForge.

Best-of-breed tools

The SBForge tools have all been selected and implemented according to the qualities mentioned.

The advantages of the individual tools are listed below:

Error formatting macro: contentbylabel: com.atlassian.confluence.api.service.exceptions.BadRequestException: Could not parse cql : null
  • No labels