{"title":"Systems Engineering at the Enterprise Level","authors":"R. Stevens","doi":"10.1109/ISRE.2001.948580","DOIUrl":null,"url":null,"abstract":"Summary form only given, as follows. The principles of systems and software engineering can be re-applied beyond the range of the individual project. Traditional enterprise-wide tasks such as technology management, decision-making, organizational objectives, reuse, innovation and outsourcing are amenable to systems engineering. Examples of all of these areas will be presented. The rewards from a disciplined approach are clearly higher when applied at this level. Indeed some aspects (such as re-use) are only possible across projects. The problem of introducing this change is primarily cultural, because of the wide range of skills (including non-technical areas) involved in this coordination. Moreover the time-scales and commitment needed are higher than for individual projects. Shaping systems processes around traditional tasks and terminology helps convince management of the need for system engineering.","PeriodicalId":90955,"journal":{"name":"Proceedings. IEEE International Requirements Engineering Conference","volume":"66 1","pages":"276"},"PeriodicalIF":0.0000,"publicationDate":"2001-08-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings. IEEE International Requirements Engineering Conference","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ISRE.2001.948580","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0
Abstract
Summary form only given, as follows. The principles of systems and software engineering can be re-applied beyond the range of the individual project. Traditional enterprise-wide tasks such as technology management, decision-making, organizational objectives, reuse, innovation and outsourcing are amenable to systems engineering. Examples of all of these areas will be presented. The rewards from a disciplined approach are clearly higher when applied at this level. Indeed some aspects (such as re-use) are only possible across projects. The problem of introducing this change is primarily cultural, because of the wide range of skills (including non-technical areas) involved in this coordination. Moreover the time-scales and commitment needed are higher than for individual projects. Shaping systems processes around traditional tasks and terminology helps convince management of the need for system engineering.