{"title":"针对非功能性需求的系统软件开发过程","authors":"H. Jung, Gil-Haeng Lee","doi":"10.1109/ICTC.2010.5674806","DOIUrl":null,"url":null,"abstract":"As the importance of non-functional requirements has increased, many researchers have become interested in software development process for non-functional requirements including the notation, modeling, and assessment of non-functional requirements. However, the characteristics of non-functional requirements are so sophisticated that there have been many topics that should be defined more clearly. In order to address one of the challenging topics, we propose a systematic software development process to support the management of nonfunctional requirements. The process consists of six steps, each of which is composed of detailed activities. Using the proposed process, the non-functional requirements can be more effectively and systematically managed and modeled.","PeriodicalId":149198,"journal":{"name":"2010 International Conference on Information and Communication Technology Convergence (ICTC)","volume":"9 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2010-12-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"14","resultStr":"{\"title\":\"A systematic software development process for non-functional requirements\",\"authors\":\"H. Jung, Gil-Haeng Lee\",\"doi\":\"10.1109/ICTC.2010.5674806\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"As the importance of non-functional requirements has increased, many researchers have become interested in software development process for non-functional requirements including the notation, modeling, and assessment of non-functional requirements. However, the characteristics of non-functional requirements are so sophisticated that there have been many topics that should be defined more clearly. In order to address one of the challenging topics, we propose a systematic software development process to support the management of nonfunctional requirements. The process consists of six steps, each of which is composed of detailed activities. Using the proposed process, the non-functional requirements can be more effectively and systematically managed and modeled.\",\"PeriodicalId\":149198,\"journal\":{\"name\":\"2010 International Conference on Information and Communication Technology Convergence (ICTC)\",\"volume\":\"9 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2010-12-23\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"14\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2010 International Conference on Information and Communication Technology Convergence (ICTC)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ICTC.2010.5674806\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2010 International Conference on Information and Communication Technology Convergence (ICTC)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ICTC.2010.5674806","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
A systematic software development process for non-functional requirements
As the importance of non-functional requirements has increased, many researchers have become interested in software development process for non-functional requirements including the notation, modeling, and assessment of non-functional requirements. However, the characteristics of non-functional requirements are so sophisticated that there have been many topics that should be defined more clearly. In order to address one of the challenging topics, we propose a systematic software development process to support the management of nonfunctional requirements. The process consists of six steps, each of which is composed of detailed activities. Using the proposed process, the non-functional requirements can be more effectively and systematically managed and modeled.