If you haven't checked out the dW On Demand Demo page, you might want to. We had a tremendous increase in demo views in 2009. It was an 86% increase compared to demo views in 2008.
southworth 100000HBX4 Tags:  tester team doors policy clearquest requirements architect forge system clearcase concert appscan data build requisitepro infosphere security rational composer 1 Comment 5,018 Visits
Here are the top 10 demos for 2009, that your colleagues have found very interesting. It is all part of building the skills to create a smarter planet, through software.
8. Creating a requirement in Rational Requirements Composer and transferring it to RequisitePro for management
southworth 100000HBX4 Tags:  requirements get problem? concert team rational smart a tools! communication is composer 2,268 Visits
I remember the days of software development when we had huge war room meetings to get status from each team lead. The project manager would manage these 2 or 3 hour meetings and hope to goodness that everyone would remember what requirements need to be updated, who is to fix which bug and well, the list goes on. The closer we got to the end of the development cycle, the longer and more frequent these meetings would be. What if all the managers, team leads and developers had a dashboard to evaluate progress and update status? What a concept!
There are many development tools that help teams communicate perfectly throughout the software development cycle. These tools will help enable teams to follow good software development habits and team communication will improve. Just understanding these tools and following the guidelines will get the team communicating like never before. I'll continue to mention different development tools that help you develop quality code quicker, throughout my blogs, but today I will focus on Rational Requirements Composer and Rational Team concert.
Rational Team Concert collaborative development environment connects teams so they can work together to simplify, automate and govern software delivery in real time. Project mangers and others can gain greater visibility into individual and team work. They can reduce overhead balance resources and provide real-time insight. In addition, you can track project progress with dashboards that include real-time project statuses. Now this is every manager's dream to manage and view the status of a development project, without having huge war room meetings.
Another great product, Rational Requirements Composer helps teams define and use requirements effectively across the project lifecycle. The whole team creates and uses requirements. Better, faster requirements lead to less project rework, faster time to market, and better business outcomes. The earlier you know and manage your requirements, the more money you will save in rework. Get your customers and stakeholders involved early and manage your requirements so that everyone understands and communicates updates and priorities.
Now couple Rational Team Concert with Rational Requirements Composer and you have a match made in heaven. The beauty is that IBM® Rational® Requirements Composer and Rational Team Concert are integrated. Check out the demo below and learn how the integration between IBM® Rational® Requirements Composer and Rational Team Concert highlights the capabilities that ensure project deliverables stay aligned to current business goals and requirements. Specifically, see examples of how to create a link from a requirement in a vision document artifact in Rational Requirements Composer to the work item stored in Rational Team Concert. Then see how to use filters to query across all the products on the Jazz platform. These capabilities help reduce project risk, reduce rework, and increase productivity.
Check out the demo! Align business with Rational Requirements Composer and Rational Team Concert
Requirements are the foundation of effective project delivery; poor practices and results, make it difficult to be successful in your projects or in the marketplace in general.
Let's discuss some the problems that can result from poor requirements practices;
One major issue in requirements practices is that there may be little to no stakeholder to stakeholder communication. For example, one stakeholder will send information and assets but may not have time or desire to discuss thoroughly. Another stakeholder will indicate that his process is the most important and should take priority. If there is no stakeholder to stakeholder discussion, the result is poor alignment of the strategy.
Another result is that the analyst may provide disparate, disjointed and inconsistent data in a variety of different formats that are impossible to understand and organize. This problem results in information overload that leads to ignored information and missing requirements.
Office tools and products have typically been the administrative tools to document our software development processes. They Have become the de-facto standard for defining requirements. As much as the tools work for individual recording functions, connecting and linking them in a meaningful way becomes very challenging and this exacerbates the process. Remember, documents are islands. They don't have version control, no reuse, team access and input may be difficult, just to mention a few issues with traditional office tools.
The result is that when the project continues with fuzzy unclear requirements and Stakeholders are unclear of timelines and expectations. The development team is placed on hold then suddenly placed in fire-drill mode to try and meet project deadlines. This is a project managers nightmare.
It is all about creating a smarter planet through software. Use great team tools to manage your development requirements. Some solutions are: Rational Requirements Composer which is designed to provide a solution for the creation and composition of meaningful requirements, based on user and stakeholder needs. Rational RequisitePro is designed to provide a platform for the management of Requirements assets, the establishment of priorities, the estimation of costs, difficulty, etc.
We'll talk more about this next week in more detail.
Align business with Rational Requirements Composer and Rational Team Concert
Learn how the integration between IBM® Rational® Requirements Composer and Rational Team Concert highlights the capabilities that ensure project deliverables stay aligned to current business goals and requirements. Specifically, see examples of how to create a link from a requirement in a vision document artifact in Rational Requirements Composer to the work item stored in Rational Team Concert. Then see how to use filters to query across all the products on the Jazz platform. These capabilities help reduce project risk, reduce rework, and increase productivity.
southworth 100000HBX4 Tags:  requirements collaboration composer jazz rational importance the team of 1,599 Visits
Over the last couple of weeks I've been talking about Jazz and Rational Team concert, the importance of collaboration they provide and the architecture of Jazz. This week I will go into a little more detail of the collaboration capabilities of Rational Team Concert.
Rational Team Concert makes it easy to exchange information directly in the context of your work. If an enhancement request changes, you and other team members are notified of the change automatically. You can reference the change in chat sessions and link to artifacts. Business stakeholders can also automatically stay informed about the status of task changes that interest them.
Several views enable you to share team information. You can track team activity, present information in more detail, or configure which information is visible at any time.
Many aspects of the software development lifecycle are integrated, including iteration planning, process definition, source control, defect tracking, build management, and reporting. Each of these aspects is integrated in a single environment. You can track and manage the relationships between artifacts, promote sound development processes, and gather project information automatically and unobtrusively.
All this collaboration within the tool provides the ability to reduce meetings and status reports, reduce rework and leverage top technical and business talent by matching skills with work items through the tool.
It is all about communicating all the details and changes throughout the development cycle and that is smart software development.
Use Rational Requirements Composer & Rational Quality Manager to align business with IT
Learn how the integration between Rational Requirements Composer (RRC) and Rational Quality Manager (RQM) highlights the capabilities that ensure project deliverables stay aligned to current business goals and requirements. The demo illustrates how IBM is taking integration and collaboration to a new level to help reduce project risk, reduce rework and increase productivity so that organizations can build the right product faster.
southworth 100000HBX4 Tags:  team rational development concert requirements software 1,587 Visits
Nearly all teams face challenges in getting their clients and other stakeholders involved enough in the requirements stage, of the development process. Especially when defining the outcomes and the details of what it will take to realize those outcomes. Rational Requirements Composer (RRC) is designed to provide a solution for the creation and composition of meaningful requirements, based on user and stakeholder needs.
IBM Rational Requirements Composer can help extended teams understand requirements faster by Using the best notation or sets of notations to communicate client and stakeholder needs by making the latest information available to the whole team, which will help shorten the review and approval cycles.
Teams can save valuable development time by using the web-based review and approval workflow. For example, the ability to have role based (reviewer, approver, optional reviewer) participants, will greatly enhance the ability to help everyone understand their role and what they need to accomplish.
With role base team members, status of both formal and informal reviews are visible to the entire team and automatic notifications help to keep participants engaged and informed. There is no need to maintain a separate record system of the approval process (but if you have one, you can still use it for final approvals).
Without a proper requirements management tool, many tools, document formats and repositories create “information islands”, making it hard to find, relate and use this information as requirements artifacts as well as use use it to inform downstream lifecycle activities. This old fashion system makes it hard to relate the requirements together, to keep the project coherent, and maintain team relationships.
Team members undertake heroic measures to consolidate, understand, monitor status, and make decisions based on this information. These manual processes often don’t scale and introduce errors.
Rational Requirements Composer enables you to use these documents together with RRC native artifacts. It can relate them to one another with links, apply attributes, include them in collections, manage review and approval status, and maintain every revision on the server. You can copy and paste Word and Excel tables into RRC in an intelligent manner and mark requirements in Word, to create individual requirements managed in the RRC database.
Align business with Rational Requirements Composer and Rational Team Concert
southworth 100000HBX4 Tags:  pants of requirements the by develop into software your project rational model for smarter planet - seat composer a don't fly 3,032 Visits
"Fly by the seat of your pants" is an early aviation term when aircraft had few navigation aids and flying was accomplished by means of the pilot's judgment.
The term emerged in the 1930s and was first widely used in reports of Douglas Corrigan's flight from the USA to Ireland in 1938.
That flight was reported in many US newspapers of the day 'Corrigan Flies By The Seat Of His Pants',
We all know that we can't fly by the seat of our pants in software development. There are so many tools today that help us make smarter software faster.
From use case development all the way to modeling, solution analysis, design activities and project management. And thank goodness that aircraft
now have the navigation tools to fly more safely.
Check out these tools to help develop software smarter!
This demo shows how to transform an IBM® Rational® Requirements Composer project into a model in IBM Rational Software Architect or IBM Rational
Software Modeler.See how use cases and process flow requirements captured in IBM Rational Requirements Composer can be used as a basis for your
solution analysis and design activities within Rational Software Architect or Rational Software Modeler.
southworth 100000HBX4 Tags:  smart are tools integrated requirements rational key composer to software development 1,958 Visits
Software development needs to be smart. Development tool integration is key to smart software development. Let's talk about Rational® Requirements Composer, which is a suite of requirements definition and business prototyping tools. Its graphical editors enable you to quickly develop requirements, construct use cases, build glossaries, create business processes and design user interface sketches and storyboards.
When you define requirements with IBM®Rational Requirements Composer, you can elicit, capture, elaborate, discuss, and review requirements using a variety of requirements definition techniques and collaboration capabilities. Rational Requirements Composer integrates with IBM Rational RequisitePro®, IBM Rational DOORS, and the Jazz-based products IBM Rational Team Concert™ and IBM Rational Quality Manager. Rational Requirements Composer also integrates with IBM Rational Software Architect and other Rational Software Delivery Platform products. Could a development team ask for anything more? Integration and communication is key to a smart development environment, which reduces risks and costs, by increasing team communication within the team tool set.
It is all part of creating a smarter planet, beginning with software development!
southworth 100000HBX4 Tags:  to doors planet requirements rational opens traceability door ibm the a smarter 2,175 Visits
Now this is a tool to help create a smarter development environment!
IBM® Rational® DOORS® Web Access enables stakeholders across your organization immediate access to the latest project requirements and traceability relationships. Rational DOORS Web Access provides secure, zero-footprint access to the central DOORS repository to enable stakeholders such as business users, developers, QA, marketing, and suppliers to stay up-to-date with the latest project requirements -- across the project and around the world. Take a closer look at how DOORS Web Access provides clear visibility into requirements and traceability relationships using the DOORS desktop client.
Check out the demo!
It is all part of creating a smarter planet through software!
southworth 100000HBX4 Tags:  requirements stakeholder communication enabling collaboration through 1,462 Visits
In past blogs, we have discussed the issues and challenges pertaining to requirements. Now let's discuss some of the IBM Rational solutions for addressing the challenges through Rational Requirements Composer (RRC) built on the collaborative Jazz platform.
Rational Requirements Composer is designed to provide a solution for the creation and composition of meaningful requirements based on user and stakeholder needs. Rational RequisitePro is designed to provide a platform for the management of Requirements assets, the establishment of priorities, the estimation of costs, difficulty, etc.
One issue is that many notations are needed to express requirements. How the information is related and maintenance of the relationships need to persist. RRC uses hyperlinks, collections, tags and attributes to create relationships among artifacts.
Not everything needs to be expressed in text – UI storyboards are a great way to flesh out high-level scenario options and get user validation. Also great for fleshing out low level requirements that have dimensions that are visible in the UI.
A simple scenario using storyboards would be:
1. Product managers record and organize stakeholder requests
2. Product managers collaborate with development on milestone scenarios and use cases
3. Architects and subject matter experts use process diagrams and text to outline scenarios
4. UI Storyboards help team to rapidly iterate on scenario options and flesh out design
Another benefit with RRC is Distributed teams can collaborate around the world. Teams can save valuable development time by using the web-based review and approval workflow, which is role based with reviewers, approvers, and optional reviewers.
- Project managers Understand the status of work to implement and validate requirements
- Business analysts define, validate, organize, and analyze requirements and use custom dashboards; share common views with the extended team
- Product owners contribute requirements and the market view and do reviews and approvals
- Developers and Testers ask for clarifications, help elaborate scenarios, and and give feedback
You need to bridge your information islands to help create smart software faster and at a lower cost.