Praktisches & Grundsätzliches zur Informatik




Comparing two Process Models for Software Development



Please note: SST is to be understood as a spiral process (rather than as a strictly waterfall model) because Requirements are allowed to change (though strictly controlled by change management). To have a change management process in place is necessary at least in projects creating software for a fixed price.

What in XP is achieved by Pair Programming, SST achieves by stipulating that Design and Code should be created by different persons: The programmer is seen as the designer's subcontractor.

SST also recommends that code implementing a given design should be tested – from a black box point of view – by the author of the design (he or she will know better than any other person whether the design was implemented correctly, and so there is no need for a third person to learn the design).



When choosing a process modell for your own project, please convince yourself that you know precisely where in the spectrum between XP and SST you want it to be (and for what reasons exactly).



Menu » NoMenu « for greiterweb.de

All Navigation Menus (= sitemap versions) are:






spw/frame_NoMenu.htmSiteNavigationMenus . . News?

Mehr + B G E + S H A + More