SAE: Transforming Automotive Engineering by Tackling Complexity
Thurs, Feb 25, 2021 at 11:00AM ET
Electrification and ADAS are accelerating product complexity to unmanageable levels. The nexus of this complexity is where software and electrical engineering converge. The problem with current processes and tools is they’re disconnected and discontinuous, creating challenges in single engineering domains and across domains.
This webinar examines how to enable a transformation of automotive engineering through an integrated multi-domain tool chain that supports industry imperatives and offers increased efficiency, automation, and traceability. It discusses the partnership of Siemens and IBM and how they have worked together to connect cross-domain processes, information, and tools, especially between systems, electrical, and software engineering.
Join us to learn how to:
Simplify wiring, reduce ECUs, & increase functionality & flexibility Optimize vehicle cost & weight Iimprove quality while reducing warranty costs driven by software & electrical engineering incompatibilities Establish traceability to drive a design path for safety-critical functions Enable a shared & common set of requirements Leverage & extend existing investments efficiently
Looking for help to get started with IBM DOORS NG?
IBM Rational DOORS Next Generation is a web-based requirements management solution for complex software and systems engineering environments. This playlist is for anyone who wants to learn about IBM Rational DOORS Next Generation. The topics are at a high level, providing an overview of key use cases and product features.
The IBM Continuous Engineering and Collaborative Lifecycle Management solutions have a rich heritage in helping teams around the world to develop products and applications faster, in a more dependable way, and at a higher quality. Over time we have come to see that the biggest challenges — and where we can offer the most help — are with teams addressing their engineering lifecycle: software engineering, certainly, and also systems engineering and the many other engineering disciplines that are necessary to create the amazing products and systems that power our economy today. We are addressing Engineering Lifecycle Management, and we are renaming our products to make that more obvious.
Why are we renaming the products?
Two reasons: to make it easier to identify each product’s primary function by its name, and to communicate our focus and investment in helping teams to implement effective Engineering Lifecycle Management.
When will I see the new names?
The products are being renamed in a phased manner. Web pages will start referencing the new names in the coming months. The v18.104.22.168 products and product documentation (released today!) retain the old names, and we intend to adopt the new names in the follow-on release.
Why are we renaming the products in a phased manner?
This phased approach gives you (and us!) time to adjust to the new names. For example, if you have written your own documentation or training materials for your customers, you can update and use them with the Jazz v6.0.6.x release family while you make plans for more significant changes when you adopt the follow-on release.
What products are being renamed?
Here are the major changes:
Are the products changing when the names change?
They are the same market-leading engineering lifecycle management products. Even the part numbers are the same. As you would expect, future enhancements will be introduced in releases of the newly-named products.
We recognize that product development is getting more complex while the product lifecycle is shrinking, customers are becoming more technically savvy and demanding, and compliance and regulatory requirements are growing. We want to make sure our product naming does not compound this complexity, and we believe this renaming will promote simplicity and clarity over time.
IBM® Engineering Lifecycle Management (ELM) integrates ELM products to provide a complete set of applications for software or systems development. ELM includes IBM Engineering Requirements Management DOORS® Next (DOORS Next), IBM Engineering Requirements Management DOORS (DOORS), IBM Engineering Workflow Management (EWM), and IBM Engineering Test Management (ETM), IBM Engineering Systems Design Rhapsody® – Model Manager (RMM), and IBM Engineering Lifecycle Optimization – Engineering Insights (ENI) with Jazz™ Team Server. This solution is designed for requirements analysts, developers, systems engineers, and testers.
The following diagram shows the development lifecycle that the solutions support. To see overviews of the applications that are represented in the image, click the boxes. For example, clickValidate and verify to see an overview of ETM.
To support the development lifecycle, ELM products let you link artifacts across applications, as shown in the following figure and examples: Figure 1. ELM connects analysts, developers, and testers
Requirements are implemented by iteration plans and validated by test plans.
Requirements are elicited, documented, elaborated, and validated by analysts. Their implementation progress is tracked in work items, and their correctness is validated by test cases.
Project managers and development managers use iteration plans to implement requirements in the context of a development schedule.
Team leads plan the iterations using iteration plans, where the work is divided further into tasks.
Developers work on defects that are submitted by testers as a result of test execution.
The test team links requirements to test plans and test cases.
Testers link test cases to work items to ensure coverage of the implementation.
Testers run test cases and submit defects for test failures.
ELM integrates the work of analysts, developers, and testers by providing the following cross-application features:
Link between artifacts across applications: For example, you can link test cases to work items and requirements.
Hover over a link to see details about the link target: For example, testers can monitor the status of a defect that they reported to the development team.
Track status across projects by adding widgets from different applications to a dashboard: For example, you can add a widget that shows the defects that are blocking testers.
Jazz Team Server
The Jazz Team Server provides the foundational services, such as user management and license management, that enable the ELM applications to work together as a single logical server. In this way, the Jazz Team Server serves as an integration hub for the applications. After you install the ELMproducts, you install product license keys into the Jazz Team Server to permit access to the capabilities provided by the applications. For details about the topologies supported for new or upgraded installations, see Planning the deployment and installation.
Products and applications
For a detailed overview of the products and applications in ELM, see the following topics:
ELM products are developed transparently on the open and extensible Jazz platform. On Jazz.net, you can download the products and their milestones, track development schedules, join discussion forums, open enhancement requests, and interact with the product developers. To learn more about the products, see the developer-written articles in the Jazz.net library or the topics about complex deployment scenarios on the Deployment wiki.
To learn more about ELM, see these resources:
ELM on Jazz.net: Learn about the new features, read the release notes, and download the binaries to install the solution.
ELM videos: These videos highlight the configuration management capabilities of the solution.
ELM sandbox: You can try a series of exercises in an online sandbox to learn more about a broad range of capabilities across the application development lifecycle.
ELM on Jazz.net: Learn about the new features, read the release notes, and download the binaries to install the solution.
ELM demo series: This set of recorded demonstrations offers a full lifecycle walk-through, and videos that highlight specific industry needs, in-depth tools, and practice topics.
IBM’s requirements management solutions have been used for years to help organizations build software and hardware systems. And now, an IBM software as a service (SaaS) solution helps government and engineering/constructions projects to run smoothly. One particularly high-profile application of this solution is the Melbourne Metro Tunnel Project.
The largest investment ever in public transport in Melbourne, Australia
Rail Projects Victoria (RPV) uses IBM’s technology to simplify the management of the delivery of the Metro Tunnel Project. This AUD 11 billion (11 billion Australian dollars) initiative creates a new underground pathway for trains to accommodate over 500,000 new passengers during peak hours each week. Construction involves the cooperation and collaboration of many different public and private organizations.
IBM’s DOORS® Next requirements management SaaS solution was implemented by the RPV team to provide a single, collaborative, secure environment to capture, trace, analyze and manage project requirements in real-time. And as it does so, it preserves the data privacy and intellectual property of the various organizations delivering the project.
Collaborators no longer need to gather updates from different companies’ systems. Instead, they use the IBM solution to obtain a single, reliable source of information. It’s securely controlled and selectively shared with each organization as needed. This improves project predictability, minimizes rework and increases communication.
IBM business partners in Australia—including Acmena—are supporting this project. Acmena, is supporting this project, and is using this solution as a platform to share requirements on large public works projects in New Zealand and Australia. Recently several large engineering/construction firms in the US and Canada have also turned to IBM’s requirements management SaaS solution for managing large public construction projects. One firm is a consortium developing rail and light rail transit infrastructure in Canada. Another client is one of the top five largest contractors in North America.
Three reasons construction firms choose IBM SaaS requirements management
Increasing competition and greater project complexity are driving architectural, engineering and construction (AEC) firms and public entities to seek ways to reduce costs and improve project performance. For AEC firms, requirements are the basis for project planning, risk management and acceptance testing. They define what the stakeholders need and what the product must meet in order to satisfy those needs.
The project development process often lacks identification, management and traceability of the requirements. IBM’s requirements management solution, DOORS Next, helps solve these gaps.
Requirements management tools are not as prevalent in the construction industry as they are in the system and software world. The large number of diverse stakeholders in these large construction projects significantly increases complexity and makes coordination of effort difficult – hence the need for a requirements management solution to keep everyone on the same page.
Why software as a service?
Typically, an organization chooses a SaaS solution for a variety of reasons. These include the desire to lower overall cost, increase efficiency, improve productivity or enable flexibility. However, large engineering and construction projects are unique in that they often involve dozens of different organizations. A cloud-based solution allows these companies to collaborate without compromising corporate firewalls. Organizations can scale up and down depending on their involvement in various stages of the project. They don’t need to make a capital investment in hardware and software.
Learn more about how the IBM DOORS Next requirements management solution can help you keep your large construction projects on track.
Read these articles about the Rail Projects Victoria (RPV) project: