How to spend less time searching for the artifacts you need and more on engineering smarter products and systems
AndyGurd 270001QKDH Visits (2182)
Engineers and managers in product and systems development teams know all too well the challenge of solving increasingly complex problems. Add to that the complexities of engineering involving multiple disciplines such as software, electrical and mechanical engineering and you can end up with a complicated organization, development process and tool environment. Among all of the challenges that this complexity brings, have you stopped to think about how much time you or your engineers spend simply searching for the artifacts they need for a particular task or to make a design decision? How easy is it for you to find, say, all the requirements, systems design, software design, source code files, electrical design and test cases for the ‘cruise control’ – does this search involve multiple engineering teams, tools, repositories and/or documents? At IBM we’ve spent some time looking into industry research and asking our clients about their experiences with this seemingly simple challenge, and the findings are quite staggering. We’ve captured the essence of the problem, the time and effort engineering teams can spend on search and reporting, and how you can realize potentially significant savings with help from IBM capabilities, in this short animation:
I’d like to know what your experiences are in your product or systems development organization and how you’re currently tackling this challenge. I’d also love to know what you think of the animation – does it ring true for you and your organization? And are you interested to learn more about the proposed solution?