{"title":"使用TAM评估SysML图以记录需求","authors":"M. S. Soares, R. Nascimento","doi":"10.1145/2590651.2590661","DOIUrl":null,"url":null,"abstract":"A number of methods, languages, tools and techniques are widely used in Software Engineering projects even before being formally evaluated in practice. In critical phases of software life cycle, such as requirements engineering, this practice may lead to deceptions. In this paper, an evaluation of the Systems Modeling Language (SysML) diagrams and constructions when applied to requirements engineering activities is proposed. This evaluation was performed based on the Technology Acceptance Model (TAM). Three criteria were used to evaluate the acceptance of SysML as a language for requirements engineering: perceived usefulness, perceived ease of use, and perceived usage. The evaluation was performed in practice in a company that develops software-intensive systems.","PeriodicalId":165011,"journal":{"name":"Euro American Conference on Telematics and Information Systems","volume":"31 10 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2014-04-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"3","resultStr":"{\"title\":\"Evaluation of SysML diagrams to document requirements using TAM\",\"authors\":\"M. S. Soares, R. Nascimento\",\"doi\":\"10.1145/2590651.2590661\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"A number of methods, languages, tools and techniques are widely used in Software Engineering projects even before being formally evaluated in practice. In critical phases of software life cycle, such as requirements engineering, this practice may lead to deceptions. In this paper, an evaluation of the Systems Modeling Language (SysML) diagrams and constructions when applied to requirements engineering activities is proposed. This evaluation was performed based on the Technology Acceptance Model (TAM). Three criteria were used to evaluate the acceptance of SysML as a language for requirements engineering: perceived usefulness, perceived ease of use, and perceived usage. The evaluation was performed in practice in a company that develops software-intensive systems.\",\"PeriodicalId\":165011,\"journal\":{\"name\":\"Euro American Conference on Telematics and Information Systems\",\"volume\":\"31 10 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2014-04-02\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"3\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Euro American Conference on Telematics and Information Systems\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1145/2590651.2590661\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Euro American Conference on Telematics and Information Systems","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/2590651.2590661","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Evaluation of SysML diagrams to document requirements using TAM
A number of methods, languages, tools and techniques are widely used in Software Engineering projects even before being formally evaluated in practice. In critical phases of software life cycle, such as requirements engineering, this practice may lead to deceptions. In this paper, an evaluation of the Systems Modeling Language (SysML) diagrams and constructions when applied to requirements engineering activities is proposed. This evaluation was performed based on the Technology Acceptance Model (TAM). Three criteria were used to evaluate the acceptance of SysML as a language for requirements engineering: perceived usefulness, perceived ease of use, and perceived usage. The evaluation was performed in practice in a company that develops software-intensive systems.