Reviews are a key aspect to improving product design and development. Not only do reviews provide an opportunity to find errors, omissions, risks and opportunities early and often in the product lifecycle, but they also enable increased understanding and communication amongst the development team. Comments, design decisions and rationale are valuable outputs from these reviews, and yet this data is frequently not recorded and kept with the data it describes. Meeting minutes, action item lists and other review artifacts are scattered in different tools, notes, notebooks, and folders disjointed from the design artifacts.
Product line growth can create a natural degradation into chaos. The common engineering solution follows a copy-and-tailor for requirements, designs, code, and tests rather than a strategic, planned reuse. A global, strategic configuration management approach across lifecycle domains (e.g. requirements) can bring order to this chaos. Order replaces uncontrolled costs with direct profits. In this webcast we walk you through a detailed scenario based on a real product line problem and solution.
This talk presents the “Agile System Engineering Specification Workshop” and our experiences applying it. We begin with a background or lean-agile principles and practice and discuss where specification workshops fit into the lean-agile flow. We then present the workshops details specifics including guidance structure, mechanics, attendees, frequency, and logistics. We discuss how behavioral threads from SysML specifications become backlog items and how to prioritize by focusing on the highest
- View Webcast Applying Large-Scale Agile with IBM Continuous Engineering and SAFe 4.0
- View Webcast Managing Change with SAFe Kanbans Using Rational CLM
- View Webcast Agile Planning and Alignment with Rational Team Concert
- View Webcast Supporting Continuous Build-Deploy-Test Cycles with IBM Solutions
- View Webcast Being “SAFe” in Regulated Industries with IBM CE
- View Webcast Using Rational Solution for SAFe Metrics and Reporting
- View Webcast Medical Device Solution Overview
- View Webcast Managing Change, Collaboration, and Configuration Management Using Rational Team Concert
- View Webcast Testing Quality Assurance and Traceability with Rational Quality Manager
- View Webcast Agile Model-Based Development for Medical Devices
- View Webcast Automating Requirements Management and Providing Traceability Using DOORS Next Generation
- View Webcast Model-Based Systems Engineering Using Rhapsody and Design Manager
This webinar will describe the role of the Systems Engineer in agile development with emphasis on the principles. A principle is a fundamental truth or proposition that serves as a foundation for a system of belief or behavior. The value realized in Scrum and Agile are practices that place humans, not processes or techniques, at the center of an organization. Remaining true to these principles results in higher quality products that meet stakeholder needs and team members that are happy.
The Boeing Company has established an enterprise wide initiative, Integrated Product Architecture (IPA), to implement model-based systems engineering (MBSE) across the company. IPA offers programs a choice of two different MBSE implementations: SysML using IBM Rhapsody and Structured Methods using Siemens Teamcenter® software for Systems Engineering. This presentation will present the rationale for creating the initiative, and why we are offering two different implementations, the challenges we face and what we need from industry.
View WebcastIn this webcast I will demonstrate how GM has taken the variation and allocation of requirements out of the DOORS environment and placed them into model based tools (Gears & Rhapsody). Connections are maintained between the tools, and data can be freely exchanged. Each tool can then be used for what it is best suited. Gears for modeling variation, DOORS for textual requirements, and Rhapsody for allocating and defining system design.
View WebcastLarge programs are routinely late and over budget. Commercial complex systems gain quality only via expensive testing. Stunning, newsworthy failures occur with disturbing frequency. How can these risks and issues be mitigated? It’s a tough problem but there is a solution that is better than merely managing complexity; one must actively reduce it to permit scaling. This includes elements like organization-follows-architecture, and iteration to tighten feedback loops. We’ll show you! Please join us.
View WebcastThis webcast will provide an introduction to AUTOSAR and provide a demonstration of how IBM Rational Rhapsody supports AUTOSAR modeling and code-generation.