{"title":"非功能性需求(可用性、安全性)","authors":"","doi":"10.56536/jicet.v2i1.18","DOIUrl":null,"url":null,"abstract":"Ideally the use of software is determined by the performance of both its functionality, such as its usefulness, flexibility, functionality, synergy, security. However, there has been a third-party emphasis on software performance, even if the functionality is not helpful or used without he necessary non-functional features. we discuss the state of the art in the design of non-functional requirements (hereafter, NFRs), while providing hope for some future directions.","PeriodicalId":145637,"journal":{"name":"Journal of Innovative Computing and Emerging Technologies","volume":"134 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2021-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Non-Functional Requirements (Usability, security)\",\"authors\":\"\",\"doi\":\"10.56536/jicet.v2i1.18\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Ideally the use of software is determined by the performance of both its functionality, such as its usefulness, flexibility, functionality, synergy, security. However, there has been a third-party emphasis on software performance, even if the functionality is not helpful or used without he necessary non-functional features. we discuss the state of the art in the design of non-functional requirements (hereafter, NFRs), while providing hope for some future directions.\",\"PeriodicalId\":145637,\"journal\":{\"name\":\"Journal of Innovative Computing and Emerging Technologies\",\"volume\":\"134 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2021-01-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Journal of Innovative Computing and Emerging Technologies\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.56536/jicet.v2i1.18\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Journal of Innovative Computing and Emerging Technologies","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.56536/jicet.v2i1.18","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Ideally the use of software is determined by the performance of both its functionality, such as its usefulness, flexibility, functionality, synergy, security. However, there has been a third-party emphasis on software performance, even if the functionality is not helpful or used without he necessary non-functional features. we discuss the state of the art in the design of non-functional requirements (hereafter, NFRs), while providing hope for some future directions.