{"title":"比较两种软件应急过程模型","authors":"J. Snygg, Mira Kajko-Mattson, E. Hammargren","doi":"10.1109/ICSSP.2012.6225960","DOIUrl":null,"url":null,"abstract":"Organizations need guidance on how to efficiently manage emergency software problems. Such guidance, however, is available in only one process model today, CM3: Emergency Problem Management. In this paper, we compare CM3: Emergency Problem Management with an industrial software emergency process model. Our comparison results lead to the extensions of CM3: Emergency Problem Management with a pre-alert phase and a co-ordination of the management of emergency software problems with a crisis management process.","PeriodicalId":166836,"journal":{"name":"2012 International Conference on Software and System Process (ICSSP)","volume":"165 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2012-06-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"2","resultStr":"{\"title\":\"Comparing two software emergency process models\",\"authors\":\"J. Snygg, Mira Kajko-Mattson, E. Hammargren\",\"doi\":\"10.1109/ICSSP.2012.6225960\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Organizations need guidance on how to efficiently manage emergency software problems. Such guidance, however, is available in only one process model today, CM3: Emergency Problem Management. In this paper, we compare CM3: Emergency Problem Management with an industrial software emergency process model. Our comparison results lead to the extensions of CM3: Emergency Problem Management with a pre-alert phase and a co-ordination of the management of emergency software problems with a crisis management process.\",\"PeriodicalId\":166836,\"journal\":{\"name\":\"2012 International Conference on Software and System Process (ICSSP)\",\"volume\":\"165 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2012-06-02\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"2\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2012 International Conference on Software and System Process (ICSSP)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ICSSP.2012.6225960\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2012 International Conference on Software and System Process (ICSSP)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ICSSP.2012.6225960","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Organizations need guidance on how to efficiently manage emergency software problems. Such guidance, however, is available in only one process model today, CM3: Emergency Problem Management. In this paper, we compare CM3: Emergency Problem Management with an industrial software emergency process model. Our comparison results lead to the extensions of CM3: Emergency Problem Management with a pre-alert phase and a co-ordination of the management of emergency software problems with a crisis management process.