![\"Systems](\"https:\/\/www.jamasoftware.com\/media\/2022\/08\/2022-08-02-IEEE-v2-managing-complexity-systems-engineering-1.jpg\")
<\/p>\n<\/p>\n
Editor’s Note:<\/strong> This blog was originally published through IEEE Innovation at Work, “Managing Complexity in Systems Engineering for Product Development with Live Traceability<\/a>,” by author Nikhil Rai, IEEE Senior Member, Senior Director of Product and Solutions Marketing at Jama Software.<\/em><\/p>\n In today\u2019s world, technological innovations across embedded systems, the Internet of Things (IoT), and artificial intelligence (AI) are aggressively pushing the envelope on product complexity and accelerating digital transformation. The next generation of autonomous cars, electric vehicles, robots, and space shuttles are all complex systems that need to seamlessly interact with multiple layers of software, hardware, and humans across different environments.<\/p>\n Because complex technology products require intricate interfaces with various systems or sub systems, there is an inherent challenge of coordinating the multiple development teams, who are often geographically spread across the world. Furthermore, large teams typically work on different stages of product development within their own silos. The different development tools, architecture, and IT environments used across various teams and organizations can significantly add to the challenges of developing new technologies.<\/p>\n Manufacturing sectors will reap the AI technology benefits of enhanced monitoring and supply chain optimization. In financial institutions, AI techniques can be used to identify which transactions are likely to be fraudulent. Through AI, the industry could also adopt fast and accurate credit scoring while automating manually intense data management tasks. Disruptions in the transport and logistics realm could include autonomous trucking and delivery on the roads and automated picking in warehouses.<\/p>\n Most complex system development starts with defining user needs and requirements, which involves design, software, and hardware teams developing deliverables that ultimately get tested and integrated for delivering the product. Given the disparate nature of these teams, there is an inherent need to optimize and continuously keep track of systems information from concept to development and delivery. However, there is often a gap in terms of how information is consumed across engineering departments, as well as its availability and traceability. The digital thread in engineering today is still a collection of different tools, which means traceability is usually accomplished in a cumbersome and manual fashion via time-consuming meetings and disconnected documents.<\/p>\n Traceability is a key both to product development and software engineering for tracking the systems development lifecycle. Helpful in achieving regulatory compliance, traceability can also be used within software engineering for running test cases and gaining valuable insights.<\/p>\n While some organizations make it a point to map product development stages and improve traceability to gain these benefits, traceability is often considered after-the-fact by others. This means that once an issue is identified, there is effort required to trace back where the error originally occurred to prevent that same failure from occurring in the future. This approach can cause multiple cost overruns, product delays, and inefficient management of change impacts. Think of addressing a car recall or fixing a complex medical device or industrial equipment\u2014 the costs can be enormous. By emphasizing the importance of traceability from the start, organizations can avoid the extra effort and cost associated with implementing it after an error has been made.<\/p>\n The solution lies in bringing a practical approach of Live Traceability\u2122 to the systems engineering world. Optimizing and measuring the systems development process with Live Traceability is a crucial competitive advantage that companies can leverage. For any complex product, systems, or software development, the requirements and user needs form the first level of abstraction. Live Traceability can be measured and monitored by using systems requirements as an anchor to manage information used in different stages of the systems development lifecycle.<\/p>\n At Jama Software, we define live requirements traceability as the ability for any engineer at any time to see the most up-to-date and complete upstream and downstream information for any requirement\u2014 no matter the stage of systems development or how many siloed tools and teams it spans. Live Traceability of system requirements is required by industry standards<\/a> to ensure product safety and forms the foundation for digital engineering and model-based systems engineering. This enables the engineering process to be managed through data and its performance improved in real time.<\/p>\n Through better requirements management and a focus on traceability, companies can improve their systems development performance with higher quality products and improved cycle times. The industry is now embracing the idea that to improve engineering efficiency within the systems development process, we need to continuously monitor and measure traceability.<\/p>\n <\/p>\n
\nSystems Engineering for Product Development with Live Traceability<\/h2>\n
Complexity of Product Development is Exploding<\/h3>\n
\nRELATED: <\/strong>Systems Engineers Career Path \u2013 How to Elevate<\/a><\/span><\/span><\/h4>\n
\nReality of Today\u2019s Complex Systems Development<\/h3>\n
Challenges in Traceability<\/h3>\n
\nRELATED: <\/strong>Requirements Traceability \u2013 How to Go Live<\/a><\/span><\/span><\/h4>\n
\nLive Traceability\u2122<\/h3>\n
\n<\/div>\n