{"title":"将UML和DODAF分解为对项目至关重要的一组图","authors":"John C. Zubeck","doi":"10.1109/SYSTEMS.2009.4815764","DOIUrl":null,"url":null,"abstract":"Most projects do not have the resources to produce and support all types of UML and DODAF diagrams. Analysis literature gives little guidance on which types of diagrams are vital for certain types of projects and domains. Here a veteran software engineer describes precisely which types of diagrams are vital and which are less important for different software projects. Also they offer some practical design strategies for applying UML and DODAF with projects centered around web database development.","PeriodicalId":131616,"journal":{"name":"2009 3rd Annual IEEE Systems Conference","volume":"31 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2009-03-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"2","resultStr":"{\"title\":\"Paring UML and DODAF down to the project-vital set of diagrams\",\"authors\":\"John C. Zubeck\",\"doi\":\"10.1109/SYSTEMS.2009.4815764\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Most projects do not have the resources to produce and support all types of UML and DODAF diagrams. Analysis literature gives little guidance on which types of diagrams are vital for certain types of projects and domains. Here a veteran software engineer describes precisely which types of diagrams are vital and which are less important for different software projects. Also they offer some practical design strategies for applying UML and DODAF with projects centered around web database development.\",\"PeriodicalId\":131616,\"journal\":{\"name\":\"2009 3rd Annual IEEE Systems Conference\",\"volume\":\"31 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2009-03-23\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"2\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2009 3rd Annual IEEE Systems Conference\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/SYSTEMS.2009.4815764\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2009 3rd Annual IEEE Systems Conference","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/SYSTEMS.2009.4815764","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Paring UML and DODAF down to the project-vital set of diagrams
Most projects do not have the resources to produce and support all types of UML and DODAF diagrams. Analysis literature gives little guidance on which types of diagrams are vital for certain types of projects and domains. Here a veteran software engineer describes precisely which types of diagrams are vital and which are less important for different software projects. Also they offer some practical design strategies for applying UML and DODAF with projects centered around web database development.
求助内容：
应助结果提醒方式：
京公网安备 11010802042870号
