Abstract
Abstract“Automation Tools for Systems Engineers are good and the right thing to do…” has never been a good enough justification in most companies for purchasing tools for Systems Engineers. Arguments such as “Systems Engineering has been successfully done without automation over the last thousands of years” (the pyramid builders were Systems Engineers or we landed a man on the moon with my slide rule) always took the wind out of our justification sails. Of course the basic response to that argument is that computerized tools are needed to handle the complexity, communication, control, and myriad other issues that Systems Engineers are called upon to design/manage; but we could never quite pin it down financially. This article attempts to gather the appropriate cost/benefit financial justification arguments in one place and presents a framework for dealing with management unbelief.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
