Tag Archive for: Product Development & Management Page 4
Tag Archive for: Product Development & Management
Jama Software is always looking for news that would benefit and inform our industry partners. As such, we’ve curated a series of customer and industry spotlight articles that we found insightful. In this blog post, we share an article from Innovation News Network, titled “Electric Vehicles vs Hydrogen Fuel Cell Vehicles: Comparing the Benefits” – originally published on March 18, 2024.
Electric Vehicles vs Hydrogen Fuel Cell Vehicles: Comparing the Benefits
The debate between electric vehicles (EVs) and hydrogen fuel cell vehicles (HFCVs) is shaping the future of green energy and transportation.
As we stand at the crossroads of a pivotal shift from fossil fuels to sustainable energy sources, it becomes imperative to compare and contrast these two leading alternatives. Both EVs and HFCVs offer promising solutions to reduce our carbon footprint, yet they also present unique challenges and potential drawbacks.
In understanding the economic viability, environmental impact, safety concerns, and infrastructural needs of these green vehicles, we can anticipate the trajectory of this green energy showdown.
This critical analysis sets the stage for a deeper exploration of each technology’s strengths, weaknesses, and role in our sustainable future.
Understanding fossil oil substitutes
Delving into the realm of fossil oil substitutes, it is crucial to comprehend the pivotal role of electric vehicles and hydrogen fuel cell vehicles in transforming the transportation sector, which is a major consumer of global oil resources.
The push towards these alternatives is largely driven by the need for energy security and carbon neutrality, with both options offering significant potential in reducing oil consumption and carbon emissions.
Renewable energy sources are integral to both EVs and HFCVs, making them a key part of the solution to our energy security concerns. With renewable energy, we’re not just shifting the source of our oil consumption from one non-renewable source to another but changing the game entirely by introducing a virtually inexhaustible energy source.
In the quest for carbon neutrality, EVs and HFCVs play a critical role. Both types of vehicles produce zero tailpipe emissions, contributing significantly to reducing carbon emissions in the transportation sector. However, it is important to note that the carbon neutrality of these vehicles largely depends on how the electricity or hydrogen fuel they use is produced.
The transition to EVs and HFCVs also presents challenges. Developing charging infrastructure for EVs and refueling stations for HFCVs requires significant investment and planning. Furthermore, there are technical and economic hurdles to overcome, such as improving battery technology for EVs and reducing the cost of hydrogen production for HFCVs.
When evaluating the potential of electric and hydrogen fuel cell vehicles as sustainable alternatives to traditional internal combustion engine (ICE) vehicles, a comprehensive comparison reveals distinct advantages and challenges associated with each technology.
From a performance comparison and cost efficiency standpoint, EVs generally outperform HFCVs. EVs are known for their high efficiency, quick acceleration, and quiet operation. In contrast, HFCVs, while offering longer ranges and quicker refueling times, face challenges due to their higher production costs and complex refueling infrastructure.
The environmental impact of both options is subject to the source of electricity or hydrogen. EVs can be powered by renewable sources, reducing their carbon footprint. However, hydrogen production for HFCVs often involves natural gas, leading to CO2 emissions.
Market adoption is skewed towards EVs, likely due to advantages in technology advancements and existing infrastructure. The global EV market has grown significantly in recent years, with major automakers investing heavily in this technology.
Performance:
EVs: High efficiency
HFCVs: Longer range, quick refueling
Cost Efficiency:
EVs: Lower cost per mile
HFCVs: Higher production cost
Environmental Impact:
EVs: Dependent on the power source, EVs have the potential for a low carbon footprint
HFCVs: CO2 emissions during hydrogen production can be produced
Infrastructure development for EVs
Infrastructure development for electric vehicles is a critical component in the transition towards sustainable transportation, requiring strategic planning and investment in areas such as renewable energy power supply systems and charging facilities.
A robust charging network is integral to this development, facilitating the widespread use of EVs. This infrastructure, however, also demands advancements in battery technology and energy storage solutions to ensure efficiency and reliability.
Battery technology and energy storage are pivotal to the performance and viability of EVs. Modern battery technologies increase the range of EVs and reduce charging time, enhancing their appeal to potential users. On the other hand, energy storage systems play a critical role in managing the power demand from EVs, ensuring a steady power supply during peak charging times.
Grid integration is another vital aspect of EV infrastructure. Integrating EVs into the power grid can help optimize energy use, balance power demand and supply, and potentially serve as an energy storage solution during periods of low power demand.
Sustainable infrastructure is the cornerstone of EV adoption. It encompasses the physical charging stations and supporting services, such as maintenance and repair facilities, that ensure the smooth operation of EVs.
The development of sustainable EV infrastructure involves a holistic approach, considering the environmental, economic, and social implications of the transition to electric mobility.
Innovations in sustainable energy technology
Pushing the boundaries of traditional energy sources, innovations in sustainable energy technology are playing a pivotal role in addressing the environmental challenges associated with transportation. These innovations are enabling the transition towards greener, more sustainable models of transportation, specifically with the advent of EVs.
The introduction of smart grids has allowed for a more efficient and reliable power supply for EVs, paving the way for crucial charging advancements. These smart grids, enhanced by the integration of solar power, have not only improved the lifecycle assessment of EVs but have also significantly reduced greenhouse gas emissions.
However, the successful transition towards sustainable energy technology heavily relies on its acceptance within society. Acceptance factors play a crucial role and are influenced by various aspects, ranging from the availability of charging infrastructure to the cost and performance of EVs.
To illustrate these key points, the following table outlines the role of each innovation in sustainable energy technology:
Innovation
Smart Grids
Role: Efficient power supply for EVs
Impact: Reduced greenhouse gas emissions
Solar Integration
Role: Enhanced renewable energy source
Impact: Improved lifecycle assessment of EVs
Acceptance Factors
Role: Influences adoption of sustainable energy tech
Impact: Aids transition towards greener transportation
Charging Advancements
Role: Faster, more efficient charging
Impact: Increases practicality and usability of EVs
Promotion of electric vehicles
In the transportation sector, electric vehicles are being promoted as a key strategy towards achieving carbon neutrality. Governments are providing incentives and establishing infrastructure to support the widespread adoption of EVs.
This not only aids in emission reduction but also enhances energy efficiency as EVs convert over 77% of the electrical energy from the grid to power at the wheels, far above the energy efficiency of conventional internal combustion engine vehicles.
Moreover, international cooperation plays a vital role in these global initiatives. The Paris Agreement, for example, unites nations in a common cause to combat climate change with a vital emphasis on emission reduction and sustainable energy technology.
Amidst the global drive towards zero-emission vehicles, policy intervention emerges as a critical catalyst in expediting this transition and fostering an era of sustainable transportation.
The policy implications are vast, pivoting around the need to create an environment conducive to the uptake of electric and hydrogen vehicles while simultaneously phasing out the use of fossil fuel-powered cars.
Regulatory frameworks play a significant role in this process. They outline the rules and standards that manufacturers, consumers, and other stakeholders must abide by, often encouraging the development and adoption of green vehicles.
Additionally, government support is crucial in advancing green vehicles, taking the form of financial incentives such as tax breaks or subsidies for consumers and investments in infrastructure like charging stations.
The legislative impact on the green vehicle sector cannot be understated, with laws enacted to mandate the use of green vehicles in certain sectors or areas or to require a certain percentage of vehicles sold by manufacturers to be electric or hydrogen.
Challenges in adopting hydrogen fuel cell vehicles
Despite policy measures, challenges remain in adopting hydrogen vehicles. High costs, primarily due to expensive fuel cell production, the lack of robust refueling infrastructure, and technology limitations hinder widespread adoption.
Additionally, market acceptance among consumers poses a significant hurdle, with concerns regarding awareness, safety, and preference for established technologies like EVs.
The future of zero-emission vehicles
Looking ahead, electric and hydrogen fuel cell vehicles are poised to play a pivotal role in the global shift towards sustainable and efficient transportation systems. Ongoing advancements in battery technology, coupled with the expansion of charging networks and refueling stations, are crucial for this success.
Moreover, consumer adoption is increasing rapidly due to environmental benefits, lower operating costs, and improved driving experience, with government incentives playing a key role in stimulating demand.
Despite challenges, the future of zero-emission vehicles looks promising, with ongoing advancements and increasing consumer adoption driving the transition towards sustainable transportation systems.
https://www.jamasoftware.com/media/2024/09/spotlight-ad-4-2.jpg5121024Jama Software/media/jama-logo-primary.svgJama Software2024-10-01 03:00:272024-09-30 12:55:12Electric Vehicles vs Hydrogen Fuel Cell Vehicles: Comparing the Benefits
In this blog, we’ll recap a section of our eBook, “Best Practices Guide to Requirements and Requirements Management in Architecture, Engineering, and Construction (AEC) Industry” – Click HERE to download it in its entirety.
Buyer’s Guide: Selecting a Requirements and Compliance Management Solution for Complex Architecture, Engineering, and Construction (AEC) Projects
Use a Single Platform to Streamline Complex AEC Project Requirements and Compliance Management
Architecture, engineering, and construction (AEC) companies face numerous challenges in managing complex project requirements and compliance due to growing complexity and enhanced regulatory scrutiny and business competition.
Project delays and cost overruns are common for a variety of reasons. Poor planning, miscommunication, and unanticipated changes can create a chaotic environment. Incomplete or mismanaged requirements are often dispersed across various isolated systems. Keeping up to date and demonstrating compliance with the latest safety, environmental, zoning and land use regulations, building codes and permits, labor, and employment laws are time-consuming and resource intensive. Without a structured approach, identifying and mitigating risks in projects is challenging. Inadequate documentation and poor knowledge management can result in lost information, repeated mistakes, and inefficiencies that lead to higher project costs and delays. Traceability – the ability to connect the dots between requirements, standards, and tests – is fundamental for AEC projects to succeed.
Companies often make the situation worse by attempting to manage critical processes using Word, Excel, or PDF document-based technology. While this manual approach may be adequate for small, simple AEC projects, it fails as complexity and scale increase. Reliance on legacy document management software such as SharePoint for tracing, storing, sharing, and retrieving project requirements and compliance documents means dealing with data siloes, lack of interoperability, constant changes, security threats, and limited collaboration and analysis.
As a result, companies have difficulty:
Reporting compliance to standards
Directly tracing regulations and standards to project requirements
Managing updates and implementing changes across concurrent projects
Collaborating effectively at a granular level around standards and design requirements
Creating an audit trail around sign-off and implementation of requirements and compliance
BOTTOM LINE
The increasing complexity and reliance on outdated tools make it difficult for AEC companies to efficiently manage requirements and compliance for complex projects that meet both internal and customer needs.
This Buyer’s Guide incorporates insights from Jama Software®’s more than 15 years of experience partnering with forward-thinking project requirements and compliance teams and industry experts. We’ve designed a platform that helps AEC companies efficiently manage and deliver complex projects by providing a centralized repository for all project requirements and regulatory compliance accessible by all stakeholders. This allows them to:
Take advantage of modern digital solutions
Manage regulations and standards with more confidence and efficiency
Demonstrate compliance with regulations systematically and consistently
Provide visibility into latest requirements, regulations, and standards
Collaborate in a single source of truth with a complete audit trail of activities
Avoid unnecessary costs and delays
Use these insights to better understand the challenges you’re up against and thoughtfully consider potential solutions. Plus, learn how to get the buy-in you need to undertake the kind of transformation necessary to succeed with complex projects.
Making the Case for Change
Jama Connect® helps AEC organizations manage complex project requirements and regulatory compliance by replacing documents and legacy tools with a powerful — but easy-to-use — digital platform that provides a single source of truth which is easily accessible by all stakeholders at any time. When project requirements, regulations, and safety analyses are managed in a centralized platform, users benefit from a straightforward process and the business impact and value of the platform becomes clear across the organization, making management buy-in easier.
If your company is not considering the importance of transitioning to a more modern, streamlined process, time is not on your side. Failing to act quickly can leave your organization even further behind.
But to see the value of a positive impact a system can have, stakeholders in an organization have to appreciate the challenges first.
This is where you come in. You can help quantify the problem within your organization and provide data to help make the case for change.
Go through the exercises in the next section using data from your organization to identify your current situation and the size of the potential opportunity.
Tools to Assess the Situation in Your Organization
Throughout the past decade of working with AEC (among other industries managing complex projects), four common pain points continuously arise for those who have yet to transform their process.
We’ll provide context around the problems and share equations with examples to help you uncover the savings from a modern project requirements and regulatory compliance solution. Remember to adjust the variables according to your company’s metrics to get a more precise estimate, and rethink how your team functions.
Improving any one of these four aspects of your process produces real savings. While the calculations on the following pages aren’t cumulative, they impact one another and can add up to significant value for your organization.
This is the potential of using a modern digital platform. If realized, it can radically change your business and be the competitive edge you need in today’s market.
THE FOUR COMMON PAIN POINTS
Unproductive Work Time
Lengthy Time-to-Completion
Rework
Project Issues
Unproductive Work Time
Are your days spent in inefficient meetings, sifting through emails and document versions for historical information or waiting for reviews and approvals? You’re not alone. Many teams suffer the repercussions of archaic, siloed project work. A modern process maximizes efficiency by tackling the root causes of momentum-killing delays and holdups.
Calculate how much unproductive work time is costing your business and imagine the possibilities of getting that time back. What could you do with
one extra hour each day?
We’ve seen long status meetings shrink or vanish when teams have the right solutions in place. Think about your team’s schedule and adjust the average time saved per person based on the time spent in meetings each week.
Lengthy Time-to-Completion
Time-to-completion and quality are usually seen as compounding challenges. Conventional wisdom says the quicker you complete a project, the more likely it is to have issues, and vice versa.
Understanding the impact of change, capturing decisions, communicating feedback, and reusing existing intellectual property — all aspects that can help speed time-to-completion — can be improved with a modern project requirements and compliance management solution.
Cost savings can certainly be great and have an impact on your bottom line, but don’t forget the qualitative implications. Consider what it would mean for your
company’s reputation to complete high quality, compliant projects faster.
Rework
In our experience, approximately 30-50% of a given project is rework. Rework is any time spent on extra work — including mid-project changes, incorrect testing, unnecessary scope creep, or fixing problems — and it costs your company big time. Requirements errors cause the majority of rework. Improving the ability to track requirements from definition through testing to catch changes and adjust scope can ensure you’re doing or building the right thing and massively reducing overall lifecycle costs.
Complete the equation below to get an understanding of the number of hours your team spends in rework and the value of that in working hours alone.
If your organization is working on more than one project at a time, repeat this calculation for each and add up the savings for a holistic view.
Project Issues
It’s common for a project to experience issues at some point between launch and completion. The important thing is to have a system in place that can quickly and accurately identify and track their impact up and downstream. This provides visibility into the issues as early as possible when it’s less detrimental to fix.
This calculation factors in personnel hours, but you should also think about the cost of delays and missed opportunities. Plus, should issues go undetected due to sub-par project requirements or testing, achieving incomplete compliance or delivering lower-quality projects could have devastating consequences.
Five Key Elements to Help Shape Your Decision
Now that you have a clearer picture of the opportunity a new solution can bring, how should you assess the available options?
There are five key elements you’ll need to factor into your decision. There are multiple facets to each component, so we’ve laid out what to look for as you’re evaluating solutions.
1. Requirements/Compliance Process
From defining and prioritizing, to reviewing, negotiating, and approving, to verifying and validating changes, project requirements and compliance management is an ongoing, complex process. A single source of truth and visibility helps minimize interpretation — often a top barrier to success.
With Jama Connect you can:
Create and Analyze Traceability – Traceability ensures that project requirements have been met and verified, providing necessary evidence from the requirements and compliance management process. Jama Connect allows you to easily produce traceability documentation required by certifiers and contract deliverables. Your Trace Score™ enables you to continually measure and improve your process.
Reuse and Baseline Management – Compare versions of a requirement, generate branches to develop a variant, and create catalogs of reusable project requirements to improve requirements and compliance.
Manage Risk Analysis – Jama Connect helps teams identify and mitigate risks earlier, saving teams from frustrating late-stage changes and supporting the path to safety, environmental, and security regulatory compliance.
Reviews and Approvals – Increase early stakeholder visibility and participation in the review process cutting review cycles drastically.
Maintain Audit Trails and Export Data – Real-time reporting and baselining allow you to track all changes to information within the system, including timestamps and associated users. Data is easily exported from Jama Connect if your current process dictates release to customers or partners as contract deliverables or storage in a document management system.
Verification and Validation – Seamlessly manage traceability to verifications and validations, providing evidence to comply with government regulations and standards or contract requirements.
2. Compliance and Reliability
When regulatory compliance is necessary, you want a solution you can trust. We help you get ramped up quickly with templates, training and documentation aligned with regulatory agency regulations and industry standards they reference as an acceptable means of compliance. A platform’s features can inherently ease the process of proving compliance.
A respectable solution instills trust through:
Relationship rules aligned to Trace Matrix needs, configured item types, pick lists and views, workflows guiding, requirement acceptance, and project and export templates.
Export Templates to support document generation from Jama Connect. Remote consulting is available to apply style and align with the customer’s desired output.
Customer Success Programs supported by the Jama Software Professional Services team to ensure systems adoption success with your team’s information — and exclude noise that may cause unnecessary risk.
OUR SUCCESS PROGRAMS: AN ACTION ORIENTED APPROACH, DESIGNED FOR HOW YOUR TEAMS WORK
At Jama Software, we put client success at the forefront of everything we do. We are dedicated to helping you achieve your business goals and accelerate time to value. Jama Connect Success Programs are designed to help you align your people, processes, and data to maximize the success of your project requirements and compliance management process. We work with your team to quickly onboard and launch Jama Connect. Learn more here » jamasoftware.
An efficient rollout increases adoption and shortens your time-to-market. There are many aspects to consider when updating your process. An expert can assist with process alignment and optimization to ensure a smooth launch and operation. When you purchase Jama Connect, our consultants partner with you to adapt Jama Connect to fit your process and build adoption of Jama Connect within your organization.
Alignment Phase
The alignment phase aims to determine and implement the best use of Jama Connect for your organization based on an understanding of your processes, business objectives and desired team workflow. This phase includes:
Preliminary project planning and discovery sessions to understand your people, process, and data as it pertains to requirements management, verification and validation, and risk management.
Onsite workshop or remote working sessions focused on alignment of processes to governing regulations.
Consultants partner with you to determine exporting needs and properly configure standard templates to generate necessary documentation
Your Jama Software consultant will work with the core implementation team to prepare Jama Connect for use by end users, over a small number of remote working sessions if needed.
Launch Phase
Once Jama Connect is ready to use, your Jama Software consultant will lead a remote or onsite training to show your teams how to use Jama Connect. Following the training, your consultant will be available remotely to provide assistance in other activities as needed to support your initial implementation.
4. Customer Experience
Customer experience should be a driving force — not an afterthought. A project requirements and compliance management solution must have the functionality to get the job done, but added benefits like customer care, collaborative consultants and online user communities help turn things like a potentially frustrating experience into a delightful exchange. For a top-notch customer experience, look for:
A partner who will have your back. Whether it’s a technical issue or you just want assistance with process improvement, you need to know the person on the other end of the phone will take the time to troubleshoot and thoughtfully consider your situation.
Quick and consistent support. You need a support team that makes you a priority. We offer 24/7 support for any production outages.
Industry experts. Sometimes you need consultants to help with getting started and maximizing value from a new solution. Make sure you’re working with experts who understand your needs including process alignment, deployment and adoption, training and optimization.
An active, user-led customer community. The ability to leverage insights from your peers — those solving the same challenges as you — is priceless. The Jama Software User Community connects users with educational resources, support, articles, and ideas to get the most out of your Jama Connect experience.
5. Adoption
Software on its own won’t solve any of your organization’s problems. Your team needs to use it as intended to reap the benefits. And for people to willingly adopt it, the introduction of the software must be seamless.
A convoluted tool that doesn’t match your company’s process or workflow will result in teams reverting to rudimentary methods.
Look for a solution that:
Works with any project requirements and compliance management process. A solution should fit your way of working, not the other way around.
Leverages a balanced license structure. Not everyone in your company creates and edits content, but they still need visibility and a voice in the conversation when necessary. Jama Connect offers named licenses for core users and floating licenses for those who access it less frequently.
Incorporates familiar behaviors. An intuitive understanding of certain aspects of the software will go a long way in making the solution feel like second nature.
Provides customized training. Training centered around your people, process and data can improve deployment for minimal negative impact on your teams.
Gives you an opportunity to test drive the software through a trial. Key stakeholders can get their hands dirty interacting with both the functionality and one another to
determine how relatively seamless it is to use.
https://www.jamasoftware.com/media/2024/09/2024-09_best-practices-to-rm-guide-for-aec-ebook-1-1.jpg5121024Jama Software/media/jama-logo-primary.svgJama Software2024-09-25 03:00:252024-09-23 09:49:14Buyer’s Guide: Selecting a Requirements and Compliance Management Solution for Complex Architecture, Engineering, and Construction (AEC) Projects
Conquering the Top Test Management Challenges in Product, Systems, and Software Development
Effective test management is essential to deliver high-quality products, systems, and software on time and within budget. As development projects grow in complexity, managing the testing process becomes increasingly challenging. From coordinating teams to handling intricate data, test management can become a daunting task.
In this blog post, we’ll explore the top test management challenges and provide actionable strategies to conquer them.
1. Coordinating Cross-Functional Teams
The Challenge: One of the biggest challenges in test management is coordinating cross-functional teams. In modern development environments, testing often involves collaboration between developers, QA engineers, product managers, and sometimes even external stakeholders. Miscommunication or lack of alignment among these groups can lead to delays, errors, and ultimately, a product that doesn’t meet customer expectations.
The Solution: To overcome this challenge, establish clear communication channels and define roles and responsibilities early in the project. Implement regular stand-ups and meetings to ensure that everyone is on the same page. Additionally, using collaboration tools like Jira, Confluence, or Slack can streamline communication and keep everyone aligned. It’s also essential to foster a culture of collaboration where feedback is encouraged and acted upon.
“Jama Connect® covers all the needs regarding requirements management. If anyone requires a tool for requirements, tests, and traceability, Jama Connect is perfect for it.” – Software Test Manager,Software Test Manager, Industrial Conglomerates Company
2. Managing Test Data
The Challenge: Managing test data, particularly in complex systems or software development, is another significant challenge. Test data must be relevant, up-to-date, and secure, especially when dealing with sensitive information. Inadequate test data can lead to incomplete testing, which increases the risk of bugs and compromised quality in the final product.
The Solution: Invest in test data management tools – like TestRail – that allow you to create, maintain, and secure test data effectively. Mask sensitive information to comply with data protection regulations and ensure that test data is regularly updated to reflect real-world scenarios. Automating the generation and management of test data can also save time and reduce the potential for human error.
The Challenge: In today’s fast-paced development environments, especially with the adoption of Agile and DevOps methodologies, testing teams often struggle to keep up with rapid development cycles. Continuous integration and continuous deployment (CI/CD) practices demand that testing be both thorough and fast, which can be a difficult balance to achieve.
The Solution: Automate as much of the testing process as possible. Automated testing tools can run tests quickly and consistently, allowing your team to keep pace with rapid development cycles. Prioritize test cases based on risk and impact to ensure that the most critical areas are tested first. Integrating automated tests into your CI/CD pipeline will help catch issues early, reducing the need for last-minute fixes.
“If working in Aerospace / Avionics engineering, Jama Connect is a solid option to handle requirements, elements of detailed design and Test artifacts. It also enhances cross-team collaboration through the Review Center, the Stream feature.” – Arthur Bouisson,Process Engineer, RUAG Real Estate
4. Handling Complex Test Environments
The Challenge: Test environments are often complex, involving multiple systems, configurations, and platforms. Setting up and maintaining these environments can be time-consuming and prone to errors. Moreover, inconsistent test environments can lead to false positives or missed defects.
The Solution: Leverage virtualization and containerization technologies, such as Docker or Kubernetes, to create consistent and reproducible test environments. These technologies allow you to simulate various environments and configurations with ease, ensuring that tests are conducted in conditions that closely mirror production. Additionally, maintain a detailed configuration management process to document and track changes in test environments.
5. Ensuring Comprehensive Test Coverage
The Challenge: Achieving comprehensive test coverage is a constant challenge. With the increasing complexity of products and software, it’s easy to overlook certain areas, leading to gaps in testing that could result in critical defects.
The Solution: Adopt a risk-based testing approach. Focus on areas of the product that are most critical or most likely to fail, and ensure these areas receive the most attention. Use code coverage tools to identify untested parts of your codebase and supplement manual testing with automated tests to expand coverage. Regularly review and update your test cases to reflect changes in the product or system.
“We know Jama Connect has improved our test coverage (>15%) and allowed for faster more comprehensive reviews. Interestingly, these reviews have found bugs or issues that were not uncovered by traditional directed and random testing.” – Jama Administation,Jama Administation, Internet Software & Services Company
6. Managing Test Automation Effectively
The Challenge: While test automation is a powerful tool for improving efficiency and coverage, managing it effectively presents its own set of challenges. Common issues include maintaining the test scripts, dealing with flaky tests, and ensuring that automation delivers the expected return on investment.
The Solution: Focus on building robust, maintainable test scripts by following best practices, such as modularizing your code and using descriptive naming conventions. Regularly review and update your automation suite to remove flaky tests and ensure that it continues to provide value. Finally, measure the effectiveness of your automation efforts through metrics like defect detection rates and test execution times, and adjust your strategy as needed.
The Challenge: Finding the right balance between manual and automated testing is another common challenge. Over-reliance on one approach can lead to inefficiencies and missed defects.
The Solution: Develop a testing strategy that leverages the strengths of both manual and automated testing. Use automated testing for repetitive, time-consuming tasks, and manual testing for areas that require human judgment, such as user experience and exploratory testing. Regularly evaluate and adjust this balance as your project evolves and new testing needs arise.
“We screened three of the top requirements, risk, and test management tools and found Jama Connect scored much higher than the competitors. Jama Connect definitely meets our user needs.” – Principal Systems Engineer,Principal Systems Engineer, Health Care Providers & Services Company
8. Poorly Written or Incomplete Requirements
The Challenge: A testing suite can only be as good as the requirements being tested. Poor quality requirements or missing requirements = untrustworthy testing results and increased chances of defects. This is preventable and it’s much more expensive to catch issues with requirements by the time testing is happening. It’s far better to improve requirements quality earlier in the process.
The Solution: Educate team writing requirements on best practice frameworks (e.g. Easy Approach to Requirements Syntax – EARS). Review requirements for completeness and quality before building out test coverage. Make sure there’s collaboration between test writers/testers and requirements authors in case there are questions.
9. Undetected Impact of Changes
The Challenge: Changes happen, and no one likes to be blindsided. It can be challenging to accurately measure the impact of change and communicate to all impacted stakeholders. Not communicating changes to the appropriate stakeholders can lead to wasted resources on tests that don’t apply or need to be updated, delays, recalls, etc.
The Solution: Establish a change control process. Use a tool that helps you track and visualize the potential impact of changes across connected bodies of work, processes, and stakeholders. Review potential impact, discuss tradeoffs, and communicate with impacted stakeholders.
“Jama Software® is always looking for opportunities to improve its requirement management tool offering by adding new features and applications (e.g. Testing, Risk Management, V&V, SW application integration tools, etc.) – Jama Software listens to customer feedback for possible improvements to Jama Connect” – Director,Internet Software & Services Company
Conclusion
Test management is a critical component of successful product, systems, and software development. By addressing these common challenges with proactive strategies, you can improve the efficiency and effectiveness of your testing efforts. Clear communication, effective use of tools, and a balanced approach to testing will help you deliver high-quality products that meet both business objectives and customer expectations.
In the end, the key to conquering these challenges lies in continuous improvement. Regularly assess your testing processes, learn from past mistakes, and be willing to adapt to new tools and methodologies. With the right approach, even the most daunting test management challenges can be overcome.
a
Note: This article was drafted with the aid of AI. Additional content, edits for accuracy, and industry expertise by Ashley Ernst and McKenzie Jonsson.
https://www.jamasoftware.com/media/2024/09/Test-Management-1.png10801920Ashley Ernst/media/jama-logo-primary.svgAshley Ernst2024-09-19 03:00:252024-09-19 11:06:32Conquering the Top Test Management Challenges in Product, Systems, and Software Development
Connect with the Jama Software® Team in Person: Our Fall 2024 Event Lineup
Join the Jama Software® team in person this fall at some of the industry’s most exciting events. Whether you’re attending to learn about the latest trends in cybersecurity, systems engineering, requirements management, or Model-Based Systems Engineering (MBSE), our team of subject matter experts will be on hand to meet, discuss, and demonstrate how Jama Connect® can help you tackle complex development challenges.
Below is our lineup of events for September and October—let’s connect!
SIDO Lyon Cyber Expo – Lyon, France – September 18-19, 2024
About this Event: Jama Software is exhibiting alongside Sofiatech at SIDO Lyon, the premier event for innovation in IoT, AI, XR, and Robotics! Visit us at Booth E334 — we’re excited to connect with forward-thinking leaders and innovators shaping the future.
AUTOMA 2024 – Dusseldorf, Germany – October 14-16, 2024
Industry: Oil & Gas
Jama Software Representatives:Mate Harsing, Solutions Architect and Vlad Tanasescu, General Manager – ICE
Booth Number: 23
About this Event: The AUTOMA Congress is a B2B networking event focused on automation and digitalization throughout the oil & gas lifecycle. Connect with us at Booth 30 to see how Jama Connect empowers oil & gas companies to improve efficiency, quality, and schedules while reducing overall costs.
About this Event: Insuretech Connect is the world’s largest gathering of insurance innovation! Discover solutions to your biggest challenges, gain access to unique and meaningful education, and meet the insurance industry’s best and brightest.
MedTech Conference – Toronto, Canada – October 15-17, 2024
Industry: Medical Device & Life Sciences
Jama Software Representatives:Vincent Balgos, Director – Solutions & Consulting and Jason Gaither, Senior Account Executive
Booth Number: 503
About this Event: The MedTech Conference in Toronto is where industry innovators come together to drive the future of healthcare. Visit Booth #503 to connect with Jason Gaither and Vincent Balgos for live Jama Connect demos, expert insights, and exclusive swag!
Autodesk University 2024 – San Diego, USA – October 15-17, 2024
Industry: Architecture, Engineering, Construction (AEC)
Jama Software Representatives:Joe Gould, Senior Account Executive, Steven Meadows, Principal Solutions Lead, and Kevin Andrewjeski, General Manager – Growth Markets
Booth Number: 163
About this Event: Autodesk University unites professionals from architecture, engineering, construction, product design, manufacturing, media, and entertainment to forge connections, celebrate innovations, and bring the future of AEC to life.
Congress ELIV 2024 – Bonn, Germany – October 16-17, 2024
Industry: Automotive & Semiconductor
Jama Software Representatives:Matt Mickle, Director – Solutions & Consulting, Stefan Stange, Managing Director – Sales, and Neil Stroud, General Manager – Auto & Semi
Booth Number: 41
About this Event: Join us at ELIV Congress 2024 and discover the future of digital innovation in automotive electronics, software and application industry!
About this Event: We’re sponsoring the TSIA World Envision Expo in Las Vegas, where tech executives and professionals gather to network, connect, and explore solutions. Visit us at Booth #226 and join our Expo Theatre Session on Wednesday, October 23, at 12:15 PM to discover the power of Jama Connect.
Reuters Automotive USA 2024 – Detroit, Michigan, USA – October 21-23, 2024
Industry: Automotive & Semiconductor
Jama Software Representatives:Neil Stroud, General Manager – Auto & Semi and Steve Rush, Principal Solutions Consultant
Booth Number: 18
About this Event: Reuters’ Automotive USA is the automotive industry gathers to hear from trailblazing OEMs, innovative solution providers, and government agencies tackling today’s biggest challenges. Be sure to stop by the Jama Software booth #18 and say hi!
NDIA 27th Annual System and Mission Engineering Conference – Norfolk, Virginia, USA – October 27-31, 2024
Industry: Aerospace & Defense,
Jama Software Representatives:Cary Bryczek, Director – Solutions & Consulting and Rob Wilmot, Senior Account Executive
Booth Number: 4
About this Event: The Annual Systems & Mission Engineering Conference gathers defense professionals from industry, government, and academia to discuss improving defense acquisition and system performance. Jama Software is hosting a workshop on Monday, October 28 at 5:00pm in the Imagination Meeting Room. No prior experience with MBSE or Jama Connect is required. Space is limited. Contact us to learn more!
We’re excited to meet with you and explore how Jama Connect can optimize your complex projects. Don’t miss this chance to connect with our experts, dive into the latest innovations, and gain insights tailored to your specific needs. Be sure to mark your calendar and reach out to schedule a one-on-one conversation at any of these events!
https://www.jamasoftware.com/media/2024/09/2024-9-18-event-promotion-part1-1.jpg512986Jama Software/media/jama-logo-primary.svgJama Software2024-09-18 03:00:142024-09-23 11:00:02Connect with the Jama Software® Team in Person: Our Fall 2024 Event Lineup
In this blog, we’ll recap our recent webinar, “Elevating MBSE with SysML: Jama Connect® and CATIA Magic in Action” – Click HERE to watch it in its entirety.
Elevating MBSE with SysML: Jama Connect® and CATIA Magic in Action
What happens when Jama Software®’s Traceable MBSE™ combines with Dassault Systèmes’ enterprise and system architecture modeling expertise in systems engineering?
This powerful and intuitive integration between CATIA/Cameo Systems Modeler and Jama Connect® aligns business and engineering, bridging the gap between requirements management, system architecture, design, and product management.
Key trends shaping the future of MBSE across the aerospace & defense industry
Challenges keeping Systems Engineers up at night
The impact of Jama Connect Traceable MBSE in defense applications
How Cameo Systems Engineering enhances system architecture
A live demonstration of Cameo DataHub’s integration with Jama Connect
Don’t miss this opportunity to see how this integration can transform your MBSE approach, driving success from concept to deployment.
Below is an abbreviated transcript of our webinar.
Cary Bryczek: To kick things off, I want to set the stage with some trends across the aerospace and defense industry that we’re seeing. I’ll talk about how those trends are creating challenges for chief engineers and describing what keeps them up at night, then I’ll set the stage for Saulius’s presentation by showing you what Jama Connect’s Traceable MBSE looks like and how it’s designed to solve those challenges. Saulius is going to take you on a deeper dive to show you how system models and Jama Connect interoperate.
So in the aerospace and defense industry, we are developing a new system that has complexity that far exceeds commercial product development. For example, the FAA’s program to develop the Unmanned Aircraft Traffic Management system involves not just a pilot and drone, but is designed to enable autonomous and semi-autonomous operation of multiple air systems, including the passenger and cargo delivery, in a really tightly integrated civil airspace. The elements in blue on the diagram are all distinct systems of their own, and the new traffic management system needs to integrate communications and data across all of those systems to provide this new capability.
In the highly constrained environment of outer space, for example, NASA’s Cislunar and I’m pretty sure the Artemis programs are focusing on the operation and survivability of autonomous systems. To develop a space system, NASA doesn’t do this in their own silo, but they have lots and lots of contracts and companies that they work with deliver parts of the system, just like in the DoD. For example, you have Blue Origin. They are developing a friction stir additive manufacturing part of the system in partnership with Langley, right? You have Redwire out of Erie, Colorado. They are developing another in-space manufacturing system. You have Canopy out of Denver. Colorado seems to be a popular place for space. They’re developing low-cost reusable thermal protection systems, right? And there’s really dozens more. The Cislunar and the Artemis programs are developing ecosystems and the ecosystems of those partners, right?
In the government agencies and aerospace and defense companies, they’re always evolving their strategies to be able to deal with this high degree of complexity to help streamline their engineering processes. For example, the DoD, they have published a new adaptive acquisition framework. So even not just in the engineering parts of it but the acquisition parts of it as well, there’s a new framework. This particular pathway is intended for large-scale traditional hardware acquisitions to help facilitate rapid and iterative delivery, like what the software capability programs are doing.
In 2018, we had the Digital Engineering Strategy outlining a vision to modernize how DoD designs develops, delivers, operates, and even sustains systems, right? By connecting people and process and data and developing these end-to-end digital enterprises.
The DoD’s Systems Engineering and Architecture group within the DoD itself is focusing on modernizing the systems engineering practice and they’re leveraging the capabilities coming out of SERC and MOSA to build systems that can be upgraded to incorporate new technology and respond to emerging threats, right?
With this new modernization of the SE approach, and now I know this is sort of an eye chart, you guys can look at it after the fact, the DoD has moved away from visualizing its process using that shape of the V model in favor of what more realistically takes place from a process standpoint, which is that modern systems engineering is highly cyclic in nature. Now, the outermost ring is as close to what the old V model, where concept definition is in the upper left, moves to system definition through architecture and design, over to V&V, and back around to start the next cycle. What’s important is that there’s a strong emphasis on measuring not just the system being built, but the process to build that system and that data and models are at the heart of it all. To the fullest extent, models should be used in favor of documents and data should inform the decision-making.
There really is a challenge to using a data-driven approach in the models. The DoD, I love this quote, “There’s a lack of an integrated approach to implementing systems engineering focus areas that’s creating a delay in implementing the digital transformation, which is necessary to ensure relevant guidance, skills, and training are available to deliver a disciplined approach to acquiring a weapon system.” Continuing to use legacy tools and approaches is what making integrated approaches gravely difficult. What’s necessary is to take a federated approach to data across the tool ecosystem and use tools with robust APIs, modern architectures that are standards-based. An MBSE approach requires an integrated approach to connect that system model’s architecture and requirements to program teams and software and hardware teams. It doesn’t mean using a siloed system modeling tool and expect those teams to be able to consume and understand that model. In fact, kind of what I hear a lot is, “How do I achieve the benefits of MBSE when no other engineers can access model parameters they need to use to make downstream decision-making, and how do I make decisions on tests and other things that’s downstream from the system model?” I hear that quite a lot.
Bryczek: Those with technical oversight and responsibility for program success who are executing MBSE or even just traditional systems engineering commonly raise these following questions. This is what I think keeps chief engineers up at night. “How do I know if the architecture and system requirements are satisfying all the needs?” “How do I know if a change in the architecture will impact those needs?” “How do I know if a change in the architecture will impact hardware or software teams?” And, “How do I streamline model design reviews?” I have a fourth one, too, “How do I detect unallocated systems architecture and requirements that sort of transcends the system model area and goes into the software models and the hardware models?” So that’s another favorite that I have.
So these questions really, we think, can be answered using what we term Traceable MBSE. The reality at most companies is that the end-to-end systems development processes is fragmented into domain-specific tools and spreadsheets that really don’t have a lot of collaboration or any, and this leads to fragmented requirements traceability and requires significant manual effort through emails and meetings and maybe even luck to try and prevent delays, defects, rework, cost overruns, right? Most companies have come to accept this situation as an unchangeable reality given the lack of a single platform to enable this entire process, nor a method to integrate spreadsheets and desktop tools. Using Traceable MBSE, the system model in the modeling tool is joined with the Jama Connect model. Jama [Connect] is continually calculating traceability and coverage and provides scores that can be used to identify high-risk areas that can be drilled into to determine corrective actions, the system model can detect those changes, and the modeling engineers can take corrective action.
Keep in mind that model-based systems engineering is more than using the power of SysML. It is powerful. Systems engineering’s superpower to enable digital transformation comes when it’s able to connect to the entire development effort and facilitate software and mechanical teams with the ability to align their efforts to the system model, systems engineers being able to manage the state of development across the disciplines and automatically identifying risks through all stages of development.
So let’s maybe see what this looks like in Jama [Connect.] This is Jama Connect in a web browser. I’m showing a Traceable MBSE project for development of a cube set. In it, I’m managing the end-to-end development of the program mission goals and objectives, stakeholder needs, concept of operations, system requirements, subsystems, software and hardware requirements, architecture, safety risks, verification and validation, and even user stories from Jira. Jama [Connect] is going to provide that measurable end-to-end traceability for all of their elements. Their version control and baselines provide design, review, and approval, plus make the data visible onto a series of dashboards.
All the interactions with Jama [Connect] are done in this web browser. Just to give you a little bit of navigation overview, if you’ve never seen Jama [Connect], you can see the data. You can organize the data pretty much however you want. You’re not constrained to how you want to call the data. Want to look inside stuff, you can open up and look inside the dashboards. The series of dashboards can be laid out however you want. You can have multiple dashboards. So this is my main one. I want to see a trace exception dashboard, I’m able to just organize them how I want, surface up that information. And they’re live too, so if I wanted to go and look at what any of these are, show me my objectives, needs, or goals, I can just click on them and it takes me pretty much right to where I want to be.
One of the things that makes Jama [Connect] special is the ability to define a data model for the information that you’re going to be managing in the model or the Jama [Connect] project and define how the traces are related together. And then our Live Trace Explorer™ is used to show real-time progress against expected traceability. So I open up my Live Trace Explorer for this particular project. The Live Trace Explorer is used to show the real-time state of progress of all of the items that are being managed in the system against the expected traceability according to those rule sets. When integrated with system modeling tools, like managing architecture, Jira managing the flow of tasks, using Live Trace Explorer, you can obtain this holistic view of quality across your entire system development and software factory process.
So this left-hand side shows requirements coverage and the right-hand side of the Live Trace Explorer shows test coverage, similar to a V model. Here you can see the program system-level requirements. So here we scroll down, we have the program system level requirements and all of the relationships established for traceability. This is based on the project’s traceability rule set, remember? Your project might use different names than what you see here. You’re not really constrained to using what comes out-of-the-box Jama [Connect] at all.
Bryczek: The Trace Explorer in the upper right, this Trace Score™ shows an overall traceability score for your project that you can use to gauge how quality changes, hopefully improves over time. So all of these metrics are real-time from what’s happening right now, and so 64% traceability, this is probably maybe early to midstream in development. We’re still seeing people still establishing traceability, right? But by increasing your traceability score, we really hope to reduce the risk of defects, cost overruns, and delays.
So what about some of those questions that keep chief engineers and program managers up at night? What about the ones that we were asked about? So question one is, “How do I know if architecture and system requirements are satisfying all the needs?” This is tracked in our Live Trace Explorer as a percentage of coverage between the linkages. So here we see a 55% coverage between these stakeholder expectations, which we have 36 stakeholder expectations, so 55% traceability established so far between those. And we only have, and if you scroll down, if you want to see what the architecture is, the architecture, we only have 50% coverage between the architecture and requirements.
So what about, “How do I know if a change in architecture is going to impact testing”? You can really easily see that here, the changes between what’s happening to testing. You can even see a percentage of the suspect changes. So right now, I might’ve already changed some of the requirements of your architecture. 11% is showing suspect. Right now, I don’t have a lot of test plan coverage. Still kind of in the early phases as well.
What about the third question, “How do I know if a change in architecture will impact hardware or software teams?” Right? Again, you can easily see any of the downstream traces to different things. And this is live, too, so if I wanted to see exactly, show me those objects, I can just click, it’s all interactive, and see exactly what the traceability between architecture and system requirements look like. I want to add more information to the view, maybe I want to see what the rationale is or the status, I can add that kind of view really super easily to my view. Jama [Connect] is really designed to make it easy for anyone to come in, understand what’s going on in the program, click and see instant traceability based on what you’re looking at.
So another question is, “How do I detect unallocated system architecture and requirements?” Unallocated activity can be used by running a query. So I have a filter that says, “Show me all of the unallocated architecture.” So I have four architectural elements that have no traces for requirements, and if I turn my trace view on, you can see these are just standalone objects. There’s no traceability either up or downstream to requirements of any kind. We really want to make this as easy as possible, as powerful as possible for people to measure in real time what does their traceability look like, how do I use traceability to effectively enhance the process and remediate actions before they might possibly happen.
So in summary, as systems development continues to increase in velocity, engineering leaders and program managers really need answers to those really tough questions. System modeling tools alone don’t easily provide that. With Jama [Connect]’s Live Trace Explorer, this is providing that real-time traceability score. Our approach for managing and controlling process is using actual data. Jama [Connect] is really the only one that can provide that holistic view. Very exciting.
And now, Saulius would love to show us how Dassault is connecting Jama [Connect] and CATIA Magic.
Saulius Pavalkis: So you saw the Jama [Connect]site. Now we’ll talk about the integration part with CATIA Magic leading SysML and MBSE solution for system architecture. So what is the reason, what is the differentiator, why it is the leading solution? So this was first product to support SysML v1, and pretty much all the versions from that was supported with the complete standard, following already for almost 20 years, as we can see, of the SysML appearance. Now we’ll be working on SysML v2, which will be another evolution and, again, the same goals. We became de facto standard for the many different project types in the industry, and pretty much the quality and scalability of the product and strict following of the standard enabled that. You can’t support all the big clients with the custom solutions unless you will follow some standard approach which allows to customize for each specific one later on.
And that brings us to our core values. So it is completely open. Also, as we will see here also from OpenAPI side, because that enabled us integrate in the proper way with the requirement management solution, Jama Software.
Standard compliance, another big deal because if you support the standard, maybe it is a bit harder than to integrate specifically for specific needs, right? But once you follow that, it’ll apply for all the different purposes, plus it will be clear which part of the integration needs to be updated with the standard update and with the tool development, which is not the case when you don’t follow the standards, right?
Efficiency and user-friendliness, ability to customize, and that’s like one of the most significant values because again, if you follow the standard, you get the 90% for the industry needs, but then you need to customize for specific industry, like what type of the data you want, as you saw in the Jama [Connect], you can select data set, what’s needed for specific project, have ability to create your own data set and then synchronize only on that data set and work on that model.
We support mostly system engineering community needs, and that is pretty much 90% or something of the product, because standard compliance is one thing, but then actually system engineering to enable better results with the model than PowerPoint, better tables and data management, and Excel is the key differentiator when you want to work with the model sufficiently.
The big part is continuity to disciplines. As you saw, traceability is big part of the Jama Software solution. Same for us, we dedicate most the attention for these integrations with the rest of the ecosystem. This is perhaps one of the most popular integrations, maybe the most popular integrations which we have. But in general, these are disciplines in engineering and analysis.
And also system engineering life cycle, as Cary mentioned, design reviews, this is very important process. Every organization goes through it and also in collaboration with suppliers, and that’s technically insight but also other processes which requires formal process with the approvals and baselines.
So talking about this integration specifically, we are using DataHub as integration framework. What are the highlights? It comes as a plugin actually for CATIA Magic. It’s built in in CATIA Magic. And this integration is also not an exception. It’s using this major integration framework, which is mostly for requirement tools integration. One of the most used integrations which we have is actually requirement management tools, and the most useful integration, used integration likely will be Jama Software integration from requirements management side. It provides similar experience for all the integrations and already set up operations which are common for the users, not to expect some surprises, but it is also redesigned to be more optimal, more user-friendly, and supports the standards like OSLC v2, but in our case, we are using direct API to Jama Connect, which is always the best case when you have ability to leverage that, and that shows again the openness of Jama Software and CATIA Magic.
Pavalkis: The workflow is very simple, so pretty much you connect the data source to Jama [Connect]. Jama [Connect] can be on the cloud, on premises. You select the scope for the synchronization. We support only one operation, copy and synchronize, which is by far the most popular one from all the experience we have. We then select the mapping based on the data sets selected, you know, could be new requirement types, could be new relations and so, and then we synchronize, first of all, by copying the data, but later on by checking changes, seeing the changes available and acting on those changes, synchronizing and acting on those changes with suspect links in our site. And also, on top of that, we support diagrams as an image interchange, which is a big deal because then you can actually work independently without all these requiring to see another solution for the part of the data.
Now, when we work together, what are the key connection highlights? So we support advanced authentication methods, simple authentication, and OAuth 2.0. On project selection, we select the data which will be available, what type of data will be available, and that data will allow us to map just to those elements from Jama Software type and see them synchronized to CATIA Magic using DataHub. As you can see here, we have this Cameo DataHub view in CATIA Magic, Cameo, and it is based on the same selected data in Jama Software for the project, right? And then you can see it with the icons with the exact representation that allows you to have the seamless interface.
The leverage, the same dedicated UI for identifying changes, what’s new, what is modified, move, delete it out of scope, and this allows us to see the change before synchronizing, so you can even apply element-by-element synchronization and, based on the direction of synchronization, you can choose one or another way to synchronize, which is always good to choose in advance not to have the conflicts on the authoritative source of truth.
We have number of items, type of elements in Jama Software which we synchronize. You can see the full list. It’s far more than just requirement, the different other types of attachments and so on. We allow, as I said before, to import the images to CATIA Magic and from CATIA Magic export diagrams as images to Jama, which allows you to review the diagrams in Jama Software and also see the architecture views from Jama Software and CATIA Magic and act on them.
https://www.jamasoftware.com/media/2024/09/Elevating-MBSE-with-SysML-Jama-Connect®-and-CATIA-Magic-in-Action-1.png5121024Cary Bryczek/media/jama-logo-primary.svgCary Bryczek2024-09-17 03:00:032024-09-19 11:03:35[Webinar Recap] Elevating MBSE with SysML: Jama Connect® and CATIA Magic in Action
The Jama Software® Discovery Center: Learn the Value of Jama Connect® for Complex Development
Welcome to the Jama Software® Discovery Center — a dynamic resource designed to guide you on your journey with Jama Connect®. Whether you’re just beginning to explore modern requirements management or you’re an experienced user looking to optimize your processes, the Discovery Center provides everything you need— right at your fingertips. Learn about Jama Connect and grow your knowledge at your own pace with this comprehensive resource.
Explore the Four Key Areas of the Discovery Center
The Discovery Center is organized into four main areas, each designed to meet you wherever you are on your journey with Jama Connect or simply better understanding how to optimize complex product, systems, and software development.
Here’s an overview of what you can expect:
Discover – Just starting out? Begin your journey in the Discover section, where you’ll find a wealth of resources to help you grasp the fundamentals of modern requirements management. This area is equipped with a comprehensive buyer’s guide, best practices for requirements management (RM), and insights on how centralizing your RM can mitigate risks in product development. Whether you’re evaluating RM tools or seeking to refine your current processes, this is the ideal starting point.
Explore – Curious about how Jama Connect can address your development challenges? The Explore section is for you. Here, you can delve into how Jama Connect® can cater to your specific product, systems, or software development needs. Access curated resources, including customer stories, a complimentary 30-day trial of Jama Connect, and our Get Started video series. This section is designed to facilitate informed decision-making by demonstrating why industry-leading organizations worldwide, choose Jama Connect.
Align & Launch – Ready to implement Jama Connect or better understand what that might look like? The Align & Launch area serves as your go-to resource for successful installation and adoption of Jama Connect within your organization. This section provides key resources to support implementation planning, including FAQs, installation tips, and an in-depth examination of the platform’s features and functionality. It encompasses everything you need to ensure a seamless transition and effective rollout.
Optimize – Already using Jama Connect and seeking to maximize its potential? The Optimize section is tailored for users who want to enhance their environment and ensure long-term success. Here, you’ll find comprehensive information on the REST API, optimization videos, workshops, tutorials, and other tips and tricks to help you fully harness the power of Jama Connect’s robust capabilities.
The Jama Software Discovery Center is more than just a resource collection — it’s a comprehensive guide that empowers you to take control of your knowledge journey with Jama Connect. Whether you’re discovering, exploring, aligning, launching, or optimizing, the Discovery Center is here to support your success every step of the way.
Note: This article was drafted with the aid of AI. Additional content, edits for accuracy, and industry expertise by Decoteau Wilkerson, Kenzie Jonsson, Karrie Sundbom.
https://www.jamasoftware.com/media/2024/09/2024-09-10_discovery-center_024x512-1-1-1.jpg5121024Jama Software/media/jama-logo-primary.svgJama Software2024-09-12 03:00:202024-09-20 14:10:21The Jama Software Discovery Center: Learn the Value of Jama Connect for Complex Development
In this blog, we’ll recap our recent webinar, “Achieving Success in Energy Storage Development: Tips & Best Practices” – Click HERE to watch it in its entirety.
Achieving Success in Energy Storage Development: Tips & Best Practices
Are you prioritizing the safety and success of your energy storage systems (ESS) development?
Teams developing ESS must prioritize product safety and effectively navigate the certification process. By learning best practices and gaining insights into Underwriter Laboratories (UL) standards, they can enhance safety and ensure compliance with industry regulations.
You’ll gain a thorough understanding of these topics and more:
Proven best practices for energy storage system development
Key tips for achieving certification to UL standards
How Jama Connect®‘s pre-defined framework supports successful energy storage systems development and ensures compliance
Don’t miss this opportunity to gain valuable insights and learn how a modern requirements management solution can streamline your energy storage development efforts.
Below is an abbreviated transcript of our webinar.
Steven Meadows: Welcome to today’s webinar on achieving success, as well as energy storage development tips and best practices. So for today’s webinar, we’re going to dive into some essential topics that are going to be very important for successful and safe energy storage system development and successful certification. So our agenda really is going to cover a few areas, including key tips for achieving certification with UL standards and development best practices, Jama Software’s perspective on development challenges, and the effective use of Jama Connect for managing the development of energy storage systems, as well as a sneak peek into our new energy storage development framework.
Now, before we get started, I’d like to briefly introduce myself and my background. My name is Steven Meadows and I’m a principal solutions lead here at Jama Software. With a pretty robust background in requirements management, I bring around about 10 years of experience in implementing software and working with hardware and software teams across a broad spectrum of industries, helping important market game changers really succeed in their development efforts. Now, throughout my career, I’ve had the privilege of working closely with many, many incredibly innovative and life-changing organizations, helping them navigate the intricate landscape of engineering. So Jama Software, my focus has been on empowering teams to achieve their project goals efficiently and with precision. Whether it’s harnessing the full capabilities of Jama connect the platform or strategizing for complex project scenarios and engineering scenarios. My passion really lies in delivering tangible results that drive innovation and enhance operational excellence. Today I’m excited to be joined by Chris Flueckiger who will be talking about energy storage development best practices and certification tips. He’s a bit of a guru in the space. Would you like to introduce yourself, Chris?
Christopher Flueckiger: Sure. Thank you. It’s nice to meet everybody. I’ve spent about the first half of my career working with the design phase of electrical equipment and then the past almost 30 years in the certification of renewable energy systems including battery energy storage systems. So I’ve been working with large companies. I work with all the certifiers currently and represent companies as they look towards certification, all the way from the concept and design of a product through the final certification in marketing and installation. So I look forward to talking with everybody.
Flueckiger: This is going to be interesting. In a half hour, we’re going to try to cover the complexity of certification, but to do so in a way that’ll provide efficient moving from the development of a product to the marketplace. And this is an image of that process when we talk about certification. It starts with a list of documentation, knowledge, and an understanding of what applies to your product. And to go back just one step, it’s understanding what your standards and codes are that are driving that certification of your device. You’ll see the blue text here that represents work that you can do ahead of time to ease the process of certification when you actually present your product to the certifier. And this blue information here is a collection of documentation and evidence, if you will, that your product indeed complies with whatever standards might apply.
When we’re talking about energy storage systems, we’re looking primarily at UL9540 and UL9540A. And the code that drives that is going to be the NFPA 855. And so all these little blue boxes are critical as we prepare for our submission for certification. I will say that not having this information as you enter into certification results in significant time delays, and resource costs as far as samples needed, retesting, redesign, etc. And so what we’re going to do is go through some of these critical points here and discuss how we can make it easier, what we can do to prepare better so that we can be as efficient as possible. Just an example of how efficiency can help you, a typical certification of an energy storage system is going to take about … Well, it could be anywhere from 14 to 16 weeks. We’ve had some certifications that have taken more than a year to complete when they haven’t been prepared properly or they’ve had to be redesigned or test results have come back that have shown a lack of compliance with the UL9540 standard. So it’s critical that we move forward in a smart, organized, and efficient manner.
Talking about the beginning of this whole process is a knowledge of all of your codes and standards that apply to your energy storage system. It’s more than just a marketing scheme. It’s a legal requirement that devices are certified or proven safe to the authorities having jurisdictions or AHJs that approve those installations in one of the many, many, approximately 3000 different jurisdictions across the United States. Those codes are called out by the building codes. From there it calls out specific codes for electrical and fire safety. And those codes are adopted by local jurisdictions giving them some teeth. They’re legislated into effect, which gives them the legal basis as a requirement in order to install an energy storage system within a particular jurisdiction. And that legal basis is important. When we talk about certification, often companies see it as a necessary step, maybe even an obstacle that they have to achieve just to get their product to market, but it has more meaning than that.
It basically establishes a bar of entry for electrical devices that are suitable and acceptable for installation in specific jurisdictions. Now in the United States, we fortunately have the NFPA 70 or National Electrical Code that drives those requirements for safe electrical equipment, and that follows through along with the fire codes. So there is a legal basis for doing this. And yes, it can be time-consuming and it can be costly to go for certification, but it’s a necessary step in order to demonstrate that our products meet the industry standards for a level of safety. We do that basically as a consensus agreement within the industry on the requirements that are established both in the codes and in the standards. So it’s not simply a checkoff, it is an integral part of the safety of our electrical systems in the United States.
Meadows: Have you worked with teams in the past, maybe missed the upfront research around codes and standard requirements, and any examples of some of the impacts of that?
Flueckiger: Oh, absolutely. And oftentimes, as I say, they’re looked at as a necessary evil and bypassed, if you will, during the design phases. And then they come back later with those requirements and try to implement them at the last minute. And that often requires redesign of electrical circuits, repackaging of the product, et cetera. So it can be rather detrimental and costly to wait until the end. Good question.
So when we look at typical requirements that are included in the standards and the codes, we’ll be referencing UL9540 quite often here. They’re broken down into three major categories. We have your general construction requirements, and this is your design, right? These are the components that you’re putting together into a package that provides whatever functionality you are advertising or you’re stating that your energy storage system will provide. For example, you may have an input voltage of 480 volts. You might have an output voltage of 120 volts, whatever the case might be. You may have a certain amount of energy storage and, a number of batteries in your system that operates in a certain way to provide either backup power or to even maybe clean up a microgrid someplace in an industry, for example. But all of those general requirements for ratings rely on construction. Everything from the wire nuts holding two wires together or the connectors, all the way to the batteries and through the whole system with cooling systems potentially, and other systems that make up a part of the whole system that you’re looking to market.
And so those general construction requirements are basically material type requirements, component requirements, and mechanical requirements, and all of them are specified or delineated in UL9540. From the electrical side, we have a little bit more to deal with as well. For example, there are different circuits in battery energy storage systems. We may have an AC connection, we may have a DC set of batteries, we may have an inverter that is making that DC energy usable to the outside world, etc. All of those different circuits within the system have to be isolated from each other so that we don’t have somebody touching an antenna on a communications device and getting 480 volts at that antenna. We want to make sure they’re safe and that they’re separated. And one of the common things that’s missed along the way is that isolation. Spacing is a word that’s commonly used in electrical to define how we develop that isolation using air, for example, as an insulator.
We also might use materials that we talked about in the general construction requirements that have certain dielectric strengths to them so that we don’t have arc over within electrical circuits going from a high voltage, for example, to low voltage. So that’s an important part that has a huge impact on whether or not design is adequate, the design of your circuit boards, your interconnection of devices, etc. Whether or not they’re adequate to meet the requirements of the standards.
And then that follows by those individual components that we’re interconnecting. Whether it’s the batteries, the interconnection to a battery management system or a charging system to an inverter, to a fan, to a cooling system, or an HVAC system depending on the size of your system. But those components that make up the structure have to be relied upon in order to function safely. Not only to function safely but to produce the desired output that’s required of your energy storage system, whether it’s AC or DC, whether your input is AC or DC. All those components work together and are interconnected to produce the output and the functionality of your system.
https://www.jamasoftware.com/media/2024/09/Achieving-Success-in-Energy-Storage-Development-Tips-Best-Practices.png9001600Steven Meadows/media/jama-logo-primary.svgSteven Meadows2024-09-10 03:00:092024-09-26 13:20:02[Webinar Recap] Achieving Success in Energy Storage Development: Tips & Best Practices
Jama Connect Features in Five: Jama Connect Interchange – What Sets Us Apart
Learn how you can supercharge your systems development process! In this blog series, we’re pulling back the curtains to give you a look at a few of the powerful features in Jama Connect… in about five minutes.
In this Features in Five Integration Series video, Mario Maldari, Director of Solutions Architect at Jama Software – will demonstrate the Jama Connect to Jira integration via Jama Connect Interchange™.
VIDEO TRANSCRIPT
Mario Maldari: Hello. My name is Mario Maldari and I’m the Director of solution architecture here at Jama Software. Today we’ll be discussing the Jama Connect to Jira integration via our Jama Connect Interchange. We’ll be focusing on some specific advantages and differentiators that our integration provides for our clients. These advantages provide added value to our integration and allow our clients to better meet the needs of their process and ultimately speed up their development time with improved quality.
Let’s start in Jama Connect’s Live Trace Explorer™ and analyze gaps in coverage between system requirements and user stories. We can easily drill down into the trace view and identify gaps within our coverage. Once the gaps are identified, we can create new user stories to satisfy the coverage and improve our traceability score. Let’s go ahead and do that.
You’ll now see the gap in coverage for this particular item has been satisfied and is no longer being flagged by the tool. One unique aspect of our Jira integration is that a user can configure the synchronization interval. It can range from 15 seconds to up to 24 hours. This built-in flexibility allows for the integration to be customized to meet the needs of many different process flows and organizational needs.
Maldari: Navigating back to the user story that we just created in Jama Connect, you will now see an integration URL has been populated to the corresponding user story that was just created in Jira. In this case, the synchronization was quick, 15 seconds. Any subsequent update made to the item in Jira will synchronize and reflect back in Jama Connect with the same frequency. This way the two tools are always kept in sync and there is essentially no lag time.
Another major differentiation that our integration provides is the ability to create conditional rules for the integration. This allows users to be very specific about conditions for the creation and synchronization. They do not have to worry about the burden and overhead of sinking their entire project. They can be very specific regarding the conditions.
As an example, imagine a process that dictates that a new user story in Jama Connect will only get created in Jira when the Jira status in Jama Connect is set to do. This provides the requirements manager a level of process control where they can review the user stories and determine which ones and when they should be created in Jira.
In the Jama Connect Interchange configuration, if I navigate to the creation rule tab, I can see that there is a rule for user story creation. It’s configured to be triggered when the Jira status is set to do. I can add any number of rules and conditions based on my particular process flow. This allows for customization at a lower level and does not require the entire project to be synchronized.
Now let’s see how this works in Jama Connect. Utilizing Jama Connect’s List View, I can see which stories do not currently have a Jira status field set. I can review these and determine that I would like them to be created and synchronized to my Jira project. I can utilize the bulk edit feature and set the status for multiple items at a time.
Maldari: Because of the conditional rule I have set in my Jama Connect Interchange settings, all three of these user stories will be created in Jira and participate in synchronization. You will see that the Jira URL has now been populated and the corresponding item has been created in Jira. This is just an example, but you can imagine how this flexibility can be applied across your projects and specific to your attributes.
Another important distinction to note is how relationships in Jama Connect and Jira are maintained through the integration. This allows for a more holistic, contextual view of how requirements and user stories relate outside the direct linkage of the integration. For example, as a developer in Jira, I may want to have a reference to how the requirements relate to upstream and downstream links. By choosing a relationship type and performing a field mapping, I’m able to get this reference to display as web links in Jira. As a developer in Jira, this allows me to get a sense for the overall context of the traceability.
In this example, a developer will see a user story come into their queue, and they will have a web link reference to the upstream and downstream requirements in Jama Connect. This provides them with additional context while working on developing the user story. They are even able to navigate directly to those items in Jama Connect for further detail.
One of our core philosophies at Jama Software is making our tools easy to use and therefore easy to adopt and maintain. Our integration to Jira is no exception. The user interface is point and click and the field mapping has intelligence built in that does most of the work for you. It’s also worth noting that we do not require you to be a Jama Connect administrator to set up, configure, and utilize our integration. Jama Connect Interchange also provides detailed event logging, which allows IT teams to monitor events and current status of the configured integrations.
As you can see, the Jama Connect to Jira integration offers teams a robust set of features with configuration options to meet various organizational needs. This flexibility and ease of use combined with specific well-thought-out functionality sets us apart from other requirement tools in Jira integrations. To find out more about our Jama Connect to Jira integration through our Jama Connect Interchange, please reach out to your customer success manager or visit our website today at jamasoftware.com
https://www.jamasoftware.com/media/2024/09/FIF-JCI-New-Integration-series-1.png10801920Mario Maldari/media/jama-logo-primary.svgMario Maldari2024-09-06 03:00:102024-10-04 10:10:24Jama Connect® Features in Five: Jama Connect Interchange™ – What Sets Us Apart
Jama Software is always looking for news that would benefit and inform our industry partners. As such, we’ve curated a series of customer and industry spotlight articles that we found insightful. In this blog post, we share an article, sourced from MedTech Dive, titled “FDA Seeks Feedback On Health Equity for Medical Devices” – originally published on August 6, 2024, and written by Nick Paul Taylor.
FDA Seeks Feedback On Health Equity for Medical Devices
The agency plans to develop a framework for when devices should be evaluated in diverse populations to support marketing authorization.
Dive Brief:
The Food and Drug Administration is seeking feedback on health equity for medical devices to inform a potential regulatory approach to the topic, the agency said Monday. The paper is open for comment until Oct. 4.
In the discussion paper, the FDA shared its thinking on how sponsors can select study populations that adequately reflect the intended use for a particular medical device.
The discussion paper is part of a broader focus on health equity, one of the Center for Devices and Radiological Health’s strategic priorities, that also includes advice on diversity action plans.
The FDA framed the discussion paper as a response to the “urgent public health need for innovative technologies that help to reduce barriers to achieving health equity.” Seeking to address that need, the CDRH has committed to developing “a framework for when a device should be evaluated in diverse populations to support marketing authorization” as part of its strategic focus on health equity.
Running clinical trials that generate results consistent with how a device will perform in the real world is a way to improve health equity. Acknowledging that generating clinical data “can be complex,” the agency said it has focused its discussion paper on “a few important considerations that may be relevant for FDA’s evaluation of clinical evidence.”
The paper outlines factors that may help sponsors and investigators develop study objectives. To inform early trial design, the FDA recommends asking how the burden of disease and how the prognosis of a disease varies across a device’s intended use population. Sponsors can also ask how a device may introduce, exacerbate or mitigate differences in outcomes across the study population.
Another section of the document describes considerations related to the FDA’s evaluation of safety and effectiveness. The FDA reviews marketing authorization filings to determine whether there is reasonable assurance the device will be safe and effective in the intended population. As such, the agency is looking at whether clinical data “are generalizable to, and representative of, the intended use population.”
The FDA said it “considers it important to understand a sponsor’s rationale regarding the relevance of the provided clinical data to the intended use population.” The rationale could cover the processes used to select and enroll study populations, the agency said, or help the FDA understand difficulties a sponsor encountered when trying to obtain data from certain populations.
In the final section of the paper, the FDA describes example scenarios intended to prompt feedback on its assessment of the benefits and risks of devices. The section features a table that shows how the FDA may respond depending on whether the evidence suggests there are differences in patient populations and health outcomes, as well as whether the sponsor included specific populations in the clinical study.
In some cases, clinical trial sponsors may choose to design studies with “enriched” populations, meaning they intentionally enroll people from groups where differences are expected. The table suggests sponsors that fail to enrich study populations to reflect the intended use may face difficulties at the FDA if the available information suggests differences in patient populations.
The FDA said the absence of enriched populations may “introduce uncertainty” on the applicability of the data to the intended use population.
https://www.jamasoftware.com/media/2024/09/Screenshot-2024-08-30-at-12.43.19 PM-1.png5111024Jama Software/media/jama-logo-primary.svgJama Software2024-09-03 03:00:392024-08-30 13:04:46FDA Seeks Feedback On Health Equity for Medical Devices
In this blog, we recap our webinar, “Application of Systems Engineering in Healthcare”. Click HERE to watch the entire webinar.
When it comes to healthcare, the first to market usually gains 80% of the market share, making development speed one of the most crucial aspects of success – or failure. That’s why many organizations are looking at systems engineering as a way of connecting needs to solutions.
In this webinar, Chris Unger of PracticalSE LLC and Vincent Balgos Director, Medical Device Solutions at Jama Software® have partnered up for an engaging webinar on the application of systems engineering in healthcare.
We invite you to join in as we delve into transformative role systems engineering is playing in the healthcare industry.
What to Expect:
1. The Power of Simplicity:
Discover how focusing on the basics, while maintaining world-class performance levels, can yield astonishing returns. We’ll show you how simplicity can be a game-changer in the complex world of healthcare systems engineering.
2. Market-Driven vs. Contract-Driven:
Intrigued by the difference between market-driven and contract-driven industries? We’ll explore how systems engineering varies in these two landscapes. Learn why “Market Driven” industries emphasize competitive value creation and use cases more than traditional requirements, and how this shift can redefine your approach in healthcare.
3. Striking the Perfect Balance:
Explore the ideal state of systems engineering in healthcare, often a harmonious blend of Agile, Lean Startup, and more traditional systems approaches. Uncover strategies to adapt, innovate, and succeed in this dynamic field.
Don’t miss this opportunity to gain a comprehensive understanding of how systems engineering can revolutionize healthcare. Whether you’re a seasoned professional or just beginning your journey in healthcare systems, this webinar promises valuable takeaways for all.
Below is an abbreviated transcript of our webinar.
Application of Systems Engineering in Healthcare
Chris Unger: We’re going to talk today about systems engineering in the medical industry, particularly medical device development. So the medical device industry faces several challenges. There’s clearly constant time pressure in developing and launching safe and effective products. We’ve got to be faster than the competition with better products. And as you can see from the statistics, this is a challenge. Part of the challenges in delivering things on time is the shifting regulatory landscape. I’m sure everyone’s aware of MDR. There’s software for medical devices. The FDA is going to think about redoing design controls next year. When we were at GE Healthcare, there were like 8,000 regulations we had to monitor. So it’s a very challenging and shifting regulatory landscape. Not only do you have to be compliant with regulations, but you have to ensure your device is safe. And so quality issues, safety and just keeping performance are key elements of delivering on time and that’s getting more and more expensive as you can see here, billions of dollars of financial risk of getting this wrong.
So to make all that harder, there’s a constant increase in complexity. When I first started, there were typical software development teams were 20 to 40 people. It’s now hundreds of people and lots of interactions. So additional things like AI, machine learning, or new technologies, really have to manage a lot of complexity inside of your devices. The organizational structure is getting more and more complex. There’s a heavy focus on acquisition, so you’re integrating new teams, new cultures, and geographically distributed development teams. So that makes it all challenging. So we’re going to talk about how systems engineering can help address some of these particular challenges.
Unger: As I mentioned, a key differentiator is getting to market faster. So the success of a program in a market-driven environment is basically profits. The first mover tends to collect the lion’s share of the profits. We typically have many customers. You don’t have a single customer marketing and product management tells you roughly what they think the competition will be and what differentiates versus in a contract-driven environment, success is satisfying the contract. So within GE Healthcare, the avionics and oil and gas businesses typically had a single customer. We would produce a floating city block to British Petroleum or Shell, go to the North Sea or the Caribbean and you had a contract and you delivered to that contract versus an engine, an aircraft engine, or a medical device, we deliver to the marketplace. We decide the timing, we decide the features.
So the stakeholders and market-driven are internal to the business and you can negotiate budget and time. If you get a really, really cool feature, you can take an extra month or quarter to develop it, versus in a contract-driven, it’s really fixed. So the challenges of market-driven and contract-driven are different. Contract-driven requirements are a key commitment. You’ve got to negotiate a formal design control versus within a market-driven environment they’re critical. You have to deliver validated requirements, but they’re definitely an internal business tool that helps communication across all the business functions.
So what’s the value of systems engineering in a market-driven industry? We basically turn the ambiguous needs that we get from product marketing or product management and turn them into clear and feasible solutions to be implemented by the hardware and software teams. The key value we produce is that those implementations seamlessly integrate into the customer’s workflow and work systems. So they work really well from day one, they reliably meet their needs. They work really well after five years and not just meet their needs, they delight the customer. We really want to deliver something that the customer enjoys using. So we have to make it work day one, we need to make it work day 50. We need to make it work for every single customer. So you have to deal with all the known variability of hardware and process. Every installation and every service event has to produce a uniform, high-quality, high-performing product.
So with those constraints, we want to optimize the business value. So when we have multiple options, marketing will tell us the customer value of these options. The implementation teams will tell us the delivery and product cost of those functions. The role of systems engineering is to make trade-offs between those and really optimize the business impact based on the cost of implementation. So we want to make sure the work done by those implementation teams is tied to the maximum market impact. And associated with that is managing technical risks. If you go down a path and it turns out to be infeasible, while it might’ve been nice if it worked, you just wasted a lot of that work. So that cost has to be scaled by risk.
In doing all those first four bullets, our key value is making sure design decisions are identified and closed predictably, and that the team acts with one voice. So decisions are framed, the options are agreed to, the decision criteria are agreed to and the final decision is closed and stays closed as stakeholders change. So once you have a frozen design, do you want to make sure that actually integrates easily and when you have integration or quality problems, they’re found early and resolved early. When you have time to react, it’s a lot easier to adjust your design in the first half of your program. It’s really hard when you find severe quality issues with a month left before shipping.
Unger: And so really winning products happen when systems thinkers are effective. So clearly there’s going to be a need for some systems engineering process thinkers, but they’re system thinkers across the entire program. And so we want to make sure that everybody’s involved in systems and that the creativity of the entire program is maximized. So getting specific to GE Healthcare, what is systems engineering at GE Healthcare? Well, we have the essential customer-perceived performance. So a lot of our programs are imaging, so we have the image quality. Still, we also have things like maternal-infant care where we deliver the right humidity and temperature around the neonate. In delivering that essential performance, you’ve got to make sure it’s safe and you’ve got to make sure you have regulatory compliance. And I mentioned we really want products that are easy to use and delight the customer. So usability is a critical part of systems engineering. In doing that, we make sure we define the right implementation requirements and the right reliability strategy, and that it can be installed and serviced properly.
So with that being the overall goal, how do we organize? Well, there are a lot of things that are common across all of our product teams. We do have common program milestones. We do have a common systems’ lifecycle. It’s basically the V-cycle with iteration and agile built in. What differs is that different product teams at GE Healthcare have different levels of safety hazards, so FDA risk. We go from anesthesia where you can easily kill somebody down to ultrasound, where it’s non-ionizing equipment, that’s the light handheld probes. You can’t pinch or crush anybody to even service software that has zero patient impact. There are also almost no risks for anybody and we respond to that by adjusting the process rigor so that the higher-risk safety risk modalities have higher process rigor.
Additionally, things vary across the world or we have different locations with different cultures and different sizes of organizations. We have many systems engineers across the company, but the SE team sizes vary from less than 10. In fact, we had some sites with maybe 10 engineers and the systems engineer was half a person to teams that had over a hundred systems engineers. The scale of the programs we work on is less than 10 engineers and months-long programs to many hundred as engineers applied to a program that might last three years and were based on technology developed over the prior decade. And you want some systems engineering thinking even during that basic research decade.
Unger: The organization goes from product centralized, it’s like the SE GM for that hundred engineering group where they all reported to a dotted or solid line, to decentralized in where that team of 10 with one or half a systems engineer, there the manager was a general engineering manager and did not have a lot of systems engineering experience. So I joke that if there is a way of organizing systems engineering, we have one of those within our group somewhere.
But how did we think about tailoring? And so this is a page I put together that was generalized that you might be able to use. Obviously, as I mentioned, higher technical risks including safety risks. One way of measuring that is how many risks there are in your hazard analysis. For things that are a higher risk we looked for a higher level of functional excellence, more process documentation, more process compliance, and higher rigor of the technical design reviews, and maybe more independent reviewers. Team experience. This is subjective to measure, but Joel Goldstein did a very nice study, from Carnegie Mellon, that the value of systems engineering increases with program complexity, but it decreases with a more experienced team if you have a small team that is experiencing the technology and the application, they can get by with less process rigor and while systems engineering excellence delivers some value, it delivers less value.
https://www.jamasoftware.com/media/2023/10/Application-of-Systems-Engineering-in-Healthcare-1.png5121024Chris Unger/media/jama-logo-primary.svgChris Unger2024-08-29 03:00:072024-09-26 13:24:33[Webinar Recap] Application of Systems Engineering in Healthcare
![[Webinar Recap] Elevating MBSE with SysML: Jama Connect® and CATIA Magic in Action](https://www.jamasoftware.com/media/2024/09/Elevating-MBSE-with-SysML-Jama-Connect®-and-CATIA-Magic-in-Action-1.png "[Webinar Recap] Elevating MBSE with SysML: Jama Connect® and CATIA Magic in Action")
![[Webinar Recap] Application of Systems Engineering in Healthcare](https://www.jamasoftware.com/media/2023/10/Application-of-Systems-Engineering-in-Healthcare-1.png "[Webinar Recap] Application of Systems Engineering in Healthcare")