%0 Conference Paper %1 yavari_software_2011 %A Yavari, Yaeghoob %A Afsharchi, Mohsen %A Karami, Mojtaba %B Software Engineering (MySEC), 2011 5th Malaysian Conference in %D 2011 %I IEEE %K Case Software Use complexity; estimation; points requirements; software %P 257--262 %R 10.1109/MySEC.2011.6140680 %T Software complexity level determination using software effort estimation use case points metrics %X 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. %@ 978-1-4577-1530-3

@inproceedings{yavari_software_2011, 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.}, added-at = {2013-02-28T11:13:35.000+0100}, author = {Yavari, Yaeghoob and Afsharchi, Mohsen and Karami, Mojtaba}, biburl = {https://www.bibsonomy.org/bibtex/268e20519b1e2ed443703c7ee289f1e11/fritzsolms}, booktitle = {{Software Engineering {(MySEC)}, 2011 5th Malaysian Conference in}}, doi = {10.1109/MySEC.2011.6140680}, interhash = {57b26902227ab3bed488c95b0c06aa9d}, intrahash = {68e20519b1e2ed443703c7ee289f1e11}, isbn = {978-1-4577-1530-3}, keywords = {Case Software Use complexity; estimation; points requirements; software}, lccn = {0000}, month = dec, pages = {257--262}, publisher = {{IEEE}}, timestamp = {2013-02-28T11:14:12.000+0100}, title = {{Software complexity level determination using software effort estimation use case points metrics}}, year = 2011 }