Pub Date : 2011-12-01DOI: 10.1109/MYSEC.2011.6140688
S. S. Kamaruddin, A. Deraman, J. Yahaya, Ruzita Ahmad
This article presents a feature subset selection method for the purpose of selecting the appropriate attributes for software quality assessment. The existing software quality assessment models do not support dynamic assessment. In dynamic software quality assessment, new quality attributes can be added to the model as they emerge. Therefore, this work focuses on the development of an intelligent method that is able to learn and adapt new quality attributes into the model to establish dynamic software quality assessment
{"title":"Feature subset selection method for dynamic software quality assessment","authors":"S. S. Kamaruddin, A. Deraman, J. Yahaya, Ruzita Ahmad","doi":"10.1109/MYSEC.2011.6140688","DOIUrl":"https://doi.org/10.1109/MYSEC.2011.6140688","url":null,"abstract":"This article presents a feature subset selection method for the purpose of selecting the appropriate attributes for software quality assessment. The existing software quality assessment models do not support dynamic assessment. In dynamic software quality assessment, new quality attributes can be added to the model as they emerge. Therefore, this work focuses on the development of an intelligent method that is able to learn and adapt new quality attributes into the model to establish dynamic software quality assessment","PeriodicalId":137714,"journal":{"name":"2011 Malaysian Conference in Software Engineering","volume":"9 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121079474","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2011-12-01DOI: 10.1109/MYSEC.2011.6140647
Asmiza Abdul Sani, F. Polack, R. Paige
The development of model transformations is commonly an ad-hoc activity in MDE. Transformations are engineering artefacts, and can be developed in a disciplined way, like other software artefacts. A model transformation development process can produce transformations expressed in many different styles; transformation patterns can be used to underpin such different properties to be constructed. This paper introduces a systematic approach to development of model transformation specifications that are amenable to automated formal verification of its properties. The paper introduces a process for planning transformation and a language for capturing structural and behavioural characteristics of a model transformation, that supports templates which, when instantiated, automatically produce equivalent formal specification with analysis capabilities. The approach is illustrated with a small example, UML Class to Relational Database transformation, and verification using Alloy.
{"title":"Model transformation specification for automated formal verification","authors":"Asmiza Abdul Sani, F. Polack, R. Paige","doi":"10.1109/MYSEC.2011.6140647","DOIUrl":"https://doi.org/10.1109/MYSEC.2011.6140647","url":null,"abstract":"The development of model transformations is commonly an ad-hoc activity in MDE. Transformations are engineering artefacts, and can be developed in a disciplined way, like other software artefacts. A model transformation development process can produce transformations expressed in many different styles; transformation patterns can be used to underpin such different properties to be constructed. This paper introduces a systematic approach to development of model transformation specifications that are amenable to automated formal verification of its properties. The paper introduces a process for planning transformation and a language for capturing structural and behavioural characteristics of a model transformation, that supports templates which, when instantiated, automatically produce equivalent formal specification with analysis capabilities. The approach is illustrated with a small example, UML Class to Relational Database transformation, and verification using Alloy.","PeriodicalId":137714,"journal":{"name":"2011 Malaysian Conference in Software Engineering","volume":"69 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122695773","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2011-12-01DOI: 10.1109/MYSEC.2011.6140714
Md. Nasim Adnan, Md. Rashedul Islam, S. Hossain
The structure of a software system deteriorates as a result of continuous maintenance activity. For the purpose of software reengineering or reverse engineering, software engineers often get the original source code as the most updated source of information due to lack of current documentation and limited or nonexistent availability of the original designers. The application of clustering techniques to software systems aiming to discover feature-oriented and meaningful subsystems can help software engineers involved in software reengineering or reverse engineering to understand high-level features provided by those subsystems. Continuous research is going on in the recent years — addressing different issues in the software clustering problem. Our software clustering approach introduces the use of Knowledgebase, which leads to considerable improvement than the existing approaches. Similarity measurement is the key to perform successful clustering. Similarity measurement in the existing approaches has a common drawback that they do not incorporate the diversity of software systems. Our approach uses Knowledgebase which acts as a repository of information about the internal structure of the generic types of the software systems to provide guidelines on similarity measurement criteria and their respective weightages. The final clustering is done by populating automatically generated subsystems along with the known subsystems (provided by Knowledgebase). In our research, we have developed a tool named “ULAB Cluster 1.0” which implements our new clustering approach. This clustering tool has been evaluated by using a benchmark named “MoJo distance” for different well-known software systems. The experimental results show that our approach generates more appropriate subsystems than the other existing clustering approaches and outperforms others in different dimensions of software clustering quality.
{"title":"Clustering software systems to identify subsystem structures using knowledgebase","authors":"Md. Nasim Adnan, Md. Rashedul Islam, S. Hossain","doi":"10.1109/MYSEC.2011.6140714","DOIUrl":"https://doi.org/10.1109/MYSEC.2011.6140714","url":null,"abstract":"The structure of a software system deteriorates as a result of continuous maintenance activity. For the purpose of software reengineering or reverse engineering, software engineers often get the original source code as the most updated source of information due to lack of current documentation and limited or nonexistent availability of the original designers. The application of clustering techniques to software systems aiming to discover feature-oriented and meaningful subsystems can help software engineers involved in software reengineering or reverse engineering to understand high-level features provided by those subsystems. Continuous research is going on in the recent years — addressing different issues in the software clustering problem. Our software clustering approach introduces the use of Knowledgebase, which leads to considerable improvement than the existing approaches. Similarity measurement is the key to perform successful clustering. Similarity measurement in the existing approaches has a common drawback that they do not incorporate the diversity of software systems. Our approach uses Knowledgebase which acts as a repository of information about the internal structure of the generic types of the software systems to provide guidelines on similarity measurement criteria and their respective weightages. The final clustering is done by populating automatically generated subsystems along with the known subsystems (provided by Knowledgebase). In our research, we have developed a tool named “ULAB Cluster 1.0” which implements our new clustering approach. This clustering tool has been evaluated by using a benchmark named “MoJo distance” for different well-known software systems. The experimental results show that our approach generates more appropriate subsystems than the other existing clustering approaches and outperforms others in different dimensions of software clustering quality.","PeriodicalId":137714,"journal":{"name":"2011 Malaysian Conference in Software Engineering","volume":"66 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124980483","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2011-12-01DOI: 10.1109/MYSEC.2011.6140675
R. Abdullah, Z. D. Eri, A. M. Talib
Software testing is the process on how to identify and deliver the software as a product based on the specification that has been given and required by the users. In order to ensure that the product is working based on the user specification, there are many people who are working together for that purposes as a community of practice (CoP). The CoP in software testing environment is including the system designer, programmer, and system tester as well as the user by himself. Based on this scenario of working together or collaboratively in order to avoid a lot of mistake or errors and causes the software failure, which may be found during the processes of software testing process, so that there is a need for CoP to have a tool called knowledge management system (KMS) in managing the knowledge of best practice and lesson learnt. The paper will discuss the concept on how the KMS is offering of its processes through knowledge life cycle which starting from knowledge acquisition, knowledge storing, knowledge dissemination, and knowledge application. Therefore, by using the model of KMS in managing knowledge of software testing, CoP can utilize the knowledge in KMS and it will reduces the mistake or errors, so that they can delivered a good product besides to enhance the quality of software of the particular users.
{"title":"A model of knowledge management system in managing knowledge of software testing environment","authors":"R. Abdullah, Z. D. Eri, A. M. Talib","doi":"10.1109/MYSEC.2011.6140675","DOIUrl":"https://doi.org/10.1109/MYSEC.2011.6140675","url":null,"abstract":"Software testing is the process on how to identify and deliver the software as a product based on the specification that has been given and required by the users. In order to ensure that the product is working based on the user specification, there are many people who are working together for that purposes as a community of practice (CoP). The CoP in software testing environment is including the system designer, programmer, and system tester as well as the user by himself. Based on this scenario of working together or collaboratively in order to avoid a lot of mistake or errors and causes the software failure, which may be found during the processes of software testing process, so that there is a need for CoP to have a tool called knowledge management system (KMS) in managing the knowledge of best practice and lesson learnt. The paper will discuss the concept on how the KMS is offering of its processes through knowledge life cycle which starting from knowledge acquisition, knowledge storing, knowledge dissemination, and knowledge application. Therefore, by using the model of KMS in managing knowledge of software testing, CoP can utilize the knowledge in KMS and it will reduces the mistake or errors, so that they can delivered a good product besides to enhance the quality of software of the particular users.","PeriodicalId":137714,"journal":{"name":"2011 Malaysian Conference in Software Engineering","volume":"16 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127793464","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2011-12-01DOI: 10.1109/MYSEC.2011.6140637
M. Man, J. A. Jusoh, M. Rahim, M. Z. Zakaria
Most developer prefers not to use formal specification (FS) approach in designing a database system. In recent years, these approaches have been seen as rivals, a new consensus has been developed in which software developers are agreed it as complementary. Theoretically this approach can reduce the overall development time, use to provide an unambiguous and precise supplement to natural language descriptions. Focus to this point, it can be rigorously validated and verified leading to the early detection of specification errors or debugs during software development process. Correcting errors at the early development stage is cheaper than modifying a delivered system. A FS could be verified in order to explore the consequences of this specification and potentially find mistakes. After it was done, we have greater confidence that the testing of such system against the actual user requirement specification. This paper discusses the FS of spatial and non spatial Information Databases Integration (SIDIF) model as a case study.
{"title":"Designing multiple types of spatial and non spatial databases integration model using formal specification approach","authors":"M. Man, J. A. Jusoh, M. Rahim, M. Z. Zakaria","doi":"10.1109/MYSEC.2011.6140637","DOIUrl":"https://doi.org/10.1109/MYSEC.2011.6140637","url":null,"abstract":"Most developer prefers not to use formal specification (FS) approach in designing a database system. In recent years, these approaches have been seen as rivals, a new consensus has been developed in which software developers are agreed it as complementary. Theoretically this approach can reduce the overall development time, use to provide an unambiguous and precise supplement to natural language descriptions. Focus to this point, it can be rigorously validated and verified leading to the early detection of specification errors or debugs during software development process. Correcting errors at the early development stage is cheaper than modifying a delivered system. A FS could be verified in order to explore the consequences of this specification and potentially find mistakes. After it was done, we have greater confidence that the testing of such system against the actual user requirement specification. This paper discusses the FS of spatial and non spatial Information Databases Integration (SIDIF) model as a case study.","PeriodicalId":137714,"journal":{"name":"2011 Malaysian Conference in Software Engineering","volume":"54 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121659849","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2011-12-01DOI: 10.1109/MYSEC.2011.6140665
Raja Zurina Raja Mohamed Ali, S. Ibrahim
Currently, a number of specific international standards are made available within software engineering discipline to support Software Process Improvement (SPI) such as Capability Maturity Model Integration (CMMI), ISO/IEC 15504, ISO/IEC 90003 and ISO/IEC 12207. However, different standards and practices may require substantial resources and cost, resulting in reluctance of adoption by software organizations especially those of Small and Medium Enterprises (SME). Integrated Software Process Improvement Knowledge Base and Methodology is a proposed initiative being developed on the premise to harmonize and integrate a number of existing software process assessments and practices including improvement standards, models and benchmarks. This paper describes an application tool which was developed to implement the iSPA (Integrated Software Process Assessment) model. This tool was specially designed and formulated to support locally software development companies, especially of small scale enterprises to achieve some flexibility and choices in their self-assessment based on a customized SPI model for Malaysia SME which is iSPA.
{"title":"An application tool to support the implementation of integrated software process improvement for Malaysia's SME","authors":"Raja Zurina Raja Mohamed Ali, S. Ibrahim","doi":"10.1109/MYSEC.2011.6140665","DOIUrl":"https://doi.org/10.1109/MYSEC.2011.6140665","url":null,"abstract":"Currently, a number of specific international standards are made available within software engineering discipline to support Software Process Improvement (SPI) such as Capability Maturity Model Integration (CMMI), ISO/IEC 15504, ISO/IEC 90003 and ISO/IEC 12207. However, different standards and practices may require substantial resources and cost, resulting in reluctance of adoption by software organizations especially those of Small and Medium Enterprises (SME). Integrated Software Process Improvement Knowledge Base and Methodology is a proposed initiative being developed on the premise to harmonize and integrate a number of existing software process assessments and practices including improvement standards, models and benchmarks. This paper describes an application tool which was developed to implement the iSPA (Integrated Software Process Assessment) model. This tool was specially designed and formulated to support locally software development companies, especially of small scale enterprises to achieve some flexibility and choices in their self-assessment based on a customized SPI model for Malaysia SME which is iSPA.","PeriodicalId":137714,"journal":{"name":"2011 Malaysian Conference in Software Engineering","volume":"9 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125907102","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2011-12-01DOI: 10.1109/MYSEC.2011.6140652
Prabodha Tilakaratna, J. Rajapakse
Current object oriented modeling languages either concentrating on application domain characteristics or system functionalities but not on both. Hence the absence of a common modeling language to represent application domain and system functionalities will disintegrate the analysis and design phases. This paper proposes a framework which uses Unified Modeling Language (UML) as the common modeling language in the two phases thereby integrating both phases.
{"title":"Forward engineering the object oriented analysis and design","authors":"Prabodha Tilakaratna, J. Rajapakse","doi":"10.1109/MYSEC.2011.6140652","DOIUrl":"https://doi.org/10.1109/MYSEC.2011.6140652","url":null,"abstract":"Current object oriented modeling languages either concentrating on application domain characteristics or system functionalities but not on both. Hence the absence of a common modeling language to represent application domain and system functionalities will disintegrate the analysis and design phases. This paper proposes a framework which uses Unified Modeling Language (UML) as the common modeling language in the two phases thereby integrating both phases.","PeriodicalId":137714,"journal":{"name":"2011 Malaysian Conference in Software Engineering","volume":"3 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134052382","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2011-12-01DOI: 10.1109/MYSEC.2011.6140661
Aedah Abd Rahman, S. Sahibuddin, S. Ibrahim
Concurrent adoption of software engineering process improvement frameworks have been widely practiced by the software organizations. The software development organizations leverage these frameworks to better address process improvement challenges. This paper develops an integrated framework for software engineering process improvement practices and unifies the theories in process definition and establishment. The unified framework provides a set of formal descriptions for software engineering process improvement frameworks. Requirements and architectures for software engineering process improvement frameworks are investigated. The main challenge in the integration is the interoperability of the frameworks. Inaccurate integration approach results in inefficiency of the integration process. Common interoperability issues in the integration of current process models and methodologies are addressed. In addition to this, omissions, differences and gaps can be identified and further examined for development of new unified framework. Taxonomy for software engineering process framework is used to support the understanding and comparison of diverse software quality frameworks. The taxonomy should be based on discipline-specific framework. Besides, other alternative approaches for comparing the software engineering process improvement framework are presented. The research outcome is expected to identify the structural relationships among the frameworks. Derivation from the taxonomy includes characteristics and categories of attributes tailored to the discipline-specific framework.
{"title":"A unified framework for software engineering process improvement — A taxonomy comparative analysis","authors":"Aedah Abd Rahman, S. Sahibuddin, S. Ibrahim","doi":"10.1109/MYSEC.2011.6140661","DOIUrl":"https://doi.org/10.1109/MYSEC.2011.6140661","url":null,"abstract":"Concurrent adoption of software engineering process improvement frameworks have been widely practiced by the software organizations. The software development organizations leverage these frameworks to better address process improvement challenges. This paper develops an integrated framework for software engineering process improvement practices and unifies the theories in process definition and establishment. The unified framework provides a set of formal descriptions for software engineering process improvement frameworks. Requirements and architectures for software engineering process improvement frameworks are investigated. The main challenge in the integration is the interoperability of the frameworks. Inaccurate integration approach results in inefficiency of the integration process. Common interoperability issues in the integration of current process models and methodologies are addressed. In addition to this, omissions, differences and gaps can be identified and further examined for development of new unified framework. Taxonomy for software engineering process framework is used to support the understanding and comparison of diverse software quality frameworks. The taxonomy should be based on discipline-specific framework. Besides, other alternative approaches for comparing the software engineering process improvement framework are presented. The research outcome is expected to identify the structural relationships among the frameworks. Derivation from the taxonomy includes characteristics and categories of attributes tailored to the discipline-specific framework.","PeriodicalId":137714,"journal":{"name":"2011 Malaysian Conference in Software Engineering","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130531152","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2011-12-01DOI: 10.1109/MYSEC.2011.6140662
Hossein Monem, Ab Razak Che Hussin, R. Sharifian, Habib Shaterzadeh
Customer Relationship Management (CRM) related issues, during three consecutive years, were in the top nine lists of most concern for the hospitals' chief executive officers in the USA and furthermore, Information Technology (IT) projects' failure rate in the organizations were quite high. To deal with such problems Success Factors (CSF) from different perspectives such as management, staff, patient and software were reviewed in previous healthcare's literatures. In this paper, software and patient factors deeply were focused and added to the Egg model and a five perspective map was created. Implementation success factors map depicts inadequate study on patient's trust and perception and software's customization, complexity, usability, privacy and usefulness. Chief Information Officers (CIO) and Chief Executive Officers (CEO) of hospitals and hospital's CRM system vendors can use proposed factors' map for more successful implementations. It should be noted that this result is part of a PhD research and further investigation is required to test these factors in term of practical usage in heath care environment.
{"title":"CRM software implementation factors in hospital: Software & patient perspectives","authors":"Hossein Monem, Ab Razak Che Hussin, R. Sharifian, Habib Shaterzadeh","doi":"10.1109/MYSEC.2011.6140662","DOIUrl":"https://doi.org/10.1109/MYSEC.2011.6140662","url":null,"abstract":"Customer Relationship Management (CRM) related issues, during three consecutive years, were in the top nine lists of most concern for the hospitals' chief executive officers in the USA and furthermore, Information Technology (IT) projects' failure rate in the organizations were quite high. To deal with such problems Success Factors (CSF) from different perspectives such as management, staff, patient and software were reviewed in previous healthcare's literatures. In this paper, software and patient factors deeply were focused and added to the Egg model and a five perspective map was created. Implementation success factors map depicts inadequate study on patient's trust and perception and software's customization, complexity, usability, privacy and usefulness. Chief Information Officers (CIO) and Chief Executive Officers (CEO) of hospitals and hospital's CRM system vendors can use proposed factors' map for more successful implementations. It should be noted that this result is part of a PhD research and further investigation is required to test these factors in term of practical usage in heath care environment.","PeriodicalId":137714,"journal":{"name":"2011 Malaysian Conference in Software Engineering","volume":"32 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115186224","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2011-12-01DOI: 10.1109/MYSEC.2011.6140680
Y. Yavari, M. Afsharchi, Mojtaba Karami
Software estimations are regarding based on prediction properties of system, with attention to development methodology. In object-oriented analysis, Use Case models describe the functional requirements of a software system, so they can be basis for software measurement and sizing. Use Case points method that suggested by karner, is based on size and complexity of Use Cases. This method earns the great successes in industry and university. Although this method doesn't have enough precision and accuracy, because of inaccuracy in determining Use Case complexity metrics. In this research, we are going to assessment weak points of Use Case complexity metrics specially transaction metric in Use Case points method and then we will introduce other metrics for determining Use Case complexity that it can be led to simplify calculating UUC and it can be also tried to cover the most of aspects of Use Cases.
{"title":"Software complexity level determination using software effort estimation use case points metrics","authors":"Y. Yavari, M. Afsharchi, Mojtaba Karami","doi":"10.1109/MYSEC.2011.6140680","DOIUrl":"https://doi.org/10.1109/MYSEC.2011.6140680","url":null,"abstract":"Software estimations are regarding based on prediction properties of system, with attention to development methodology. In object-oriented analysis, Use Case models describe the functional requirements of a software system, so they can be basis for software measurement and sizing. Use Case points method that suggested by karner, is based on size and complexity of Use Cases. This method earns the great successes in industry and university. Although this method doesn't have enough precision and accuracy, because of inaccuracy in determining Use Case complexity metrics. In this research, we are going to assessment weak points of Use Case complexity metrics specially transaction metric in Use Case points method and then we will introduce other metrics for determining Use Case complexity that it can be led to simplify calculating UUC and it can be also tried to cover the most of aspects of Use Cases.","PeriodicalId":137714,"journal":{"name":"2011 Malaysian Conference in Software Engineering","volume":"28 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115677017","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：