Software Development at Ascade
Tomas Lundström,Configuration Manager at Ascade, explains his successful software development process for simultaneously developing and maintaining numerous existing product versions in parallel to remain competitive in the telecom software market. Using RUP software best practices as a foundation, along with influences from OMT++, XP and other sources, the Ascade Development Process (ADP) is described in detail.
Contrary to some beliefs, RUP is not a huge out-of-the box process, which has to be adopted (or rejected) in its entirety. Rather, it should be viewed as a set of best practices supported by a fully configurable toolbox, where you only use (or add) the parts you need. For instance, there is nothing that would stop us from configuring RUP to mimic OMT++, or any other process with similar core ideas. To summarize:
- RUP can be configured to express many modern software development processes …
- … meaning that the process makes use of a subset of ‘core’ RUP …
- … and probably adds a few new things as well
Now, let us spend the next couple of chapters explaining what we mean by these statements. Then we will come back to describe how Ascade applies these ideas in more detail.
Register here to receive the free white paper.
You should receive an email with a link to download the PDF within five minutes. Whitelist our domain accurev.com to ensure you receive the email.
Featured Customers:
Featured Awards:
Download White Paper