1 September 2003
IBM Rational software tools offer you proven solutions for common development problems. This roadmap helps you find the right tool to solve your problem.
If you've heard about software development best practices and tools from IBM Rational, but you're not sure how they can help you-or if you're unsure of the right place to start in the Rational area within IBM developerWorks-then this is the place for you.
The roadmap below lists the common development problems you can expect to encounter, and then guides you to the specific area within the developerWorks Rational section where you can find solutions to those problems. Click on the links underneath the Rational Tool section of each Problem Scenario to find those solutions.
You can see all the common development problems we've identified in the Problem Scenario list just below this introduction. The name of each Problem Scenario links to the pertinent starting place on the roadmap.
Within the roadmap, you'll first find the Problem Scenario itself, where we state the problem as simply as possible, for example, "Not enough time to write good code." Next, under Elaboration, you'll find a slightly expanded description to help you understand the problem ("Too much time pressure on my team" and so on). Next under Root Causes, we identify some of the possible causes of the problem. (In our example, one of the possible causes is "Too much time spent on requirements and design).
Next, under Solution, we propose the Rational-recommended high-level solution to the problem. These general solutions come straight out of the Rational Unified Process; in fact, each solution is actually one of the standard six RUP "best practices." In our example, the applicable best practices that will solve the problem are "Develop Iteratively" and "Manage Requirements." If you're not familiar with the RUP Best Practices, we recommend you read the Rational whitepaper that introduces them and visit the RUP area with the Rational Developer Domain. (For your convenience, we also link to the whitepaper from each mention of a best practice in the roadmap.)
The next two sections, Rational Toolset and Rational Tool, provide the names of the tool family and the specific tool(s) you can use to implement a solution. In the case of our example, these are "Configurable Process" and "Rational Unified Process," respectively. The links under Rational Tool in each scenario lead you directly to areas within the Web site about each tool, with solutions you can start applying today to help address your development problems. The specific product areas contain links to technical introductions to the products and how-to articles, examples, tutorials, and other materials to help you start solving real development problems by using Rational tools and best practices.
We hope the roadmap provides you a quick, intuitive way of finding what you are looking for in the developerWorks Rational section. If you're ever not sure what you are looking at, you can find a legend at the bottom of the roadmap that describes the terminology we just described. (Following the links from the numbers next to each team also takes you to the legend.)
We will continue to develop the roadmap, and the rest of the Rational developer Web site, to help make it easier for you to find what you want and to start benefiting from Rational technology-based solutions to your development issues. If you have ideas for us, please send them to editors@us.ibm.com and we will do our best to respond to them.
- My project is late
- My project is over budget
- My project is experiencing feature creep
- My application doesn't meet the requirements
- Requirements change during my project
- Designing our application is taking too long
- We have to re-invent stuff every time we start working on an application
- I'm having problems understanding real-time system behavior
- Our code base is too complex
- I have to work with different tools, GUIs for each part of the process
- Not enough time to write good code
- Development is too expensive
- Project changes are out of control
- My application performs poorly, crashes too frequently, or can't scale to meet my users' demands
- QA testing takes too long
- Can't effectively track bug/defect resolution
| Problem: My project is late |
|
Elaboration2
Root causes3
Solution4 Rational Toolset5
Rational Tool6
|
| Problem: My project is over budget |
|
Elaboration2
Root causes3
Solution4 Rational Toolset5
Rational Tool6
|
| Problem: My project is experiencing feature creep |
|
Elaboration2
Root causes3
Solution4 Rational Toolset5
Rational Tool6
|
| Problem: My application doesn't meet the requirements |
|
Elaboration2
Root causes3
Solution4 Rational Toolset5
Rational Tool6
|
| Problem: Requirements change during my project |
|
Elaboration2
Root causes3
Solution4 Rational Toolset5
Rational Tool6
|
| Problem: Designing our application is taking too long |
|
Elaboration2
Root causes3
Solution4 Rational Toolset5
Rational Tool6
|
| Problem: We have to re-invent stuff every time we start working on an application |
|
Elaboration2
Root causes3
Solution4 Rational Toolset5
Rational Tool6
|
| Problem: I'm having problems understanding real-time system behavior |
|
Elaboration2
Root causes3
Solution4 Rational Toolset5
Rational Tool6
|
| Problem: Our code base is too complex |
|
Elaboration2
Root causes3
Solution4 Rational Toolset5
Rational Tool6
|
| Problem: I have to work with different tools, GUIs for each part of the process |
|
Elaboration2
Root causes3
Solution4 Rational Toolset5
Rational Tool6
|
| Problem: Not enough time to write good code |
|
Elaboration2
Root causes3
Solution4 Rational Toolset5
Rational Tool6
|
| Problem: Development is too expensive |
|
Elaboration2
Root causes3
Solution4
Rational Toolset5
Rational Tool6
|
| Problem: Project changes are out of control |
|
Elaboration2
Root causes3
Solution4 Rational Toolset5
Rational Tool6
|
| Problem: My application performs poorly, crashes too frequently, or can't scale to meet my users' demands |
|
Elaboration2
Root causes3
Solution4 Rational Toolset5
Rational Tool6
|
| Problem: QA testing takes too long |
|
Elaboration2
Root causes3
Solution4 Rational Toolset5
Rational Tool6
|
| Problem: Can't effectively track bug/defect resolution |
|
Elaboration2
Root causes3
Solution4 Rational Toolset5
Rational Tool6
|
1.) Problem scenario: Short description of a major problem faced by a development team.
2.) Elaboration: What this problem looks like to you and your team
3.) Root causes: Some of the significant possible causes of the problem
4.) Solution: A procedural solution to the problem, as defined by the Rational Unified Process (RUP)
5.) Rational Toolset: Name of the set of Rational software tools that help you implement a solution to the problem
6.) Rational Tool: The specific Rational tool you can use to implement a solution, with a link to the appropriate area within the Rational Developer Domain where you can find how-to articles and examples to help you solve the problem.
Comments (Undergoing maintenance)





