Premium
5.2.3 Capitalizing on Systems Engineering
Author(s) -
Sherey Jason J.
Publication year - 2006
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2006.tb02779.x
Subject(s) - schedule , asset (computer security) , documentation , project management , new product development , engineering management , computer science , systems engineering , business , risk analysis (engineering) , engineering , marketing , computer security , programming language , operating system
Project managers often find it difficult to justify allocating significant resources and schedule to systems engineering tasks when “real” engineering has to be done. With ever‐decreasing time to market demands, systems engineering continually loses out to design, integration, and test. A new method of systems engineering called Pattern‐Based Systems Engineering (PBSE) enables companies to transfer portions of systems engineering costs out of project specific budgets and into company capital asset accounts. Such a change in accounting provides a series of benefits that include improved documentation and management of core corporate intellectual property, best practices, and standards as well as not having to reserve as much precious project money on tasks that need constant re‐justification to product development managers with typically constrained budgets. This paper reviews PBSE, relevant accounting standards, and how much of systems engineering can be performed as a company‐wide capital asset development program instead of as project overhead.