|
North America | Worldwide |
|
  |
 |
|
|
Home / Solutions /
Optimal /
|
|
|
 |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Webcasts On-Demand
Seven crucial factors that will impact your requirements effectiveness This webcast gives you, in a very short amount of time, some of the most valuable requirements information you'll hear this year! James Robertson brings his wealth of requirements experience to bear on the factors that give you the best return on your investment in requirements projects. He describes how you can take advantage of them to make your requirements even more effective. Fergal illustrates how you can apply the seven pillars of wisdom when using Compuware's Optimal Trace. Optimal Trace elicits requirements, applies structure and manages them throughout the application lifecycle creating testable requirements. Practical techniques: Trace operational and other non functional requirements to business intent This webcast discusses practical methods to balance business goals and operational requirements in the software development process. Fergal McGovern speaks about achieving balance between business goals and the associated operational requirement can be a set challenge. Too often, different stakeholders are defining the business and operational requirements. This can lead to disconnects in the systems delivered, requiring expensive rework either late in the development cycle or in post production maintenance releases. Fergal will preview the new release of Compuware Optimal's, Business Requirements solution, Optimal Trace 5.0 Using Optimal Trace and Visual Studio Team System to trace requirements from business need to application delivery In this webcast Compuware and Microsoft experts explain the benefits of integrating business requirements early in the development process, to guarantee requirements coverage from a build and test perspective. Defining the right requirements early in development is the key to creating business applications that deliver a competitive edge. In this webcast, highlighting the integration of Compuware Optimal Trace and Visual Studio Team System 2005, you will learn how you can leverage business requirements throughout the application lifecycle. Practical techniques to elicit effective requirements while building trust This webcast highlights practical techniques for project stakeholders to collaborate while exploring requirements; build a plan to trace them back to the business need throughout the project life cycle, to deliver competitive edge. Ellen Gottesdiener states that, "there is no silver bullet for building and enhancing software and requirements are key". She speaks about specific techniques early in requirements development that build both effective requirements and trust. Fergal McGovern highlights that IT organizations can optimize the delivery of new application value that satisfy both business customers by making business requirements the central focus of the delivery process. With Compuware's Application Delivery Management Solution, requirements are propagated to all aspects of the delivery process, including project management, development, quality and performance assurance. This capability provides the best possible assurance that the application will meet the expectation of the business and delivers the value required. Deliver what the business expects – every time: An executive webcast on business-driven quality assurance Research and experience show us the fact of the problem: poor alignment between business and IT and the resulting gap between project requirements and QA is the prime cause of project failure – and wasted IT dollars. What to do? This session outlines some strategic measures than will help senior IT managers direct better project outcomes. Melinda-Carol Ballou, Program Director, Application Lifecycle Research, IDC and Mike Burba, Marketing Director Application Management, Compuware will discuss and demonstrate tactics for success in tightening the links between QA and early-cycle project planning. Requirements-driven testing: The journey from business needs to test and user acceptance Nearly two-thirds of IT projects fail. A critical stress point is the connection between QA/test and requirements. A requirements-driven testing approach will help improve the quality of requirements, involve QA earlier in the lifecycle and maximize your projects' ability to deliver on their business objectives. This webcast will show concrete techniques for optimizing the QA and testing processes by keeping testing activities aligned with business facing and performance oriented requirements. Requirements-driven testing: The clear solution for improving application quality Poor requirements lead directly to poor application quality. When business requirements are ambiguous, missing or just plain wrong, it is impossible for testers to confidently build a test plan that truly validates an application's business functionality. Instead, testers are force to "fly blind" and try to guess what the business expects the application to do. The results of this approach are disastrous: IDC research indicates that 70-80% of project failures stem directly from poor business requirements. The approach --called Requirements-driven testing--is specifically designed to address this problem. Requirements-driven testing improves application quality by enabling teams to capture better business requirements and directly leverage them in the testing process. Featured solutions our Optimal Trace, Compuware's requirements definition and management solution and QACenter, Compuware's test management solution. Together, these tools deliver a tightly integrated solution that enables project teams to deliver higher quality applications. Get IT right the first time – Requirements Definition, the root of the problem Explore the key tenets of the Agile Manifesto and learn how People, Co-operation and Communication are the critical success factors of software delivery. This session will delve into the implications of Agile, “Just Enough” and “Fit for Purpose” and will demonstrate the application of these guiding principals - particularly through the usage of Requirements driven projects in Optimal Trace.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
 |
