Download presentation

Presentation is loading. Please wait.

1
**Estimating Software Size with UML Models**

Ghislain Levesque, Valery Bevo UQAM, Canada De Tran Cao University of Cantho, Vietnam

2
**AGENDA INTRODUCTION MEASURING WITH COSMIC-FFP and UML V. 1.4**

INCORPORATING DATA MANIPULATION with UML V. 2.0 DISCUSSION OF RESULTS CONCLUSION

3
**INTRODUCTION Why do we measure software size ?**

How can we measure software size ? What are the techniques and methods ? Do the result take into account the tools used to develop the software ? Are there tools that automate this process? What was the evolution of Function Points Methods?

4
**Evolution of Function Points Method**

5
**AGENDA INTRODUCTION MEASURING WITH COSMIC-FFP and UML V. 1.4**

INCORPORATING DATA MANIPULATION with UML V. 2.0 DISCUSSION OF RESULTS CONCLUSION

6
**MEASURING WITH COSMIC-FFP and UML V. 1.4**

COSMIC-FFP software model

7
**MEASURING WITH COSMIC-FFP and UML V. 1.4 : Rice Cooker**

Use cases diagram

8
**MEASURING WITH COSMIC-FFP and UML V. 1.4 : Rice Cooker**

Sequence diagram - Select Cooking Mode

9
**MEASURING WITH COSMIC-FFP and UML V. 1.4 : Rice Cooker**

Sequence diagram - Set target temperature

10
**MEASURING WITH COSMIC-FFP and UML V. 1.4 : Rice Cooker**

Sequence diagram - Control Heater

11
**MEASURING WITH COSMIC-FFP and UML V. 1.4 : Rice Cooker**

Sequence diagram - Control Indicator Lamps

12
**MEASURING WITH COSMIC-FFP and UML V. 1.4 : Rice Cooker**

Results: COSMIC case study v. 2.1 : 12 CFSU (function points) UML v. 1.4 : 13 messages Difference : two control lamp objects instead of one that receive their own messages

13
**AGENDA INTRODUCTION MEASURING WITH COSMIC-FFP and UML V. 1.4**

INCORPORATING DATA MANIPULATION with UML V. 2.0 DISCUSSION OF RESULTS CONCLUSION

14
**INCORPORATING DATA MANIPULATION with UML V. 2.0**

Analyze-triangle specification in narrative text The analyze triangle process accepts values A, B and C that represent the side dimensions of triangle. The process tests the dimension values to determine whether all values are positive. If a negative value is encountered, an error message is produced. The process evaluates valid input data to determine whether the dimensions define a valid triangle and if so, what type of triangle- equilateral, isosceles or scalene – is implied by the dimensions. The type is the output.

15
**INCORPORATING DATA MANIPULATION with UML V. 2.0**

According to COSMIC-FFP, the size of this software is : One entry : side dimensions Two exits : error message and type of triangle Total : 3 CFSU (function points)

16
**INCORPORATING DATA MANIPULATION with UML V. 2.0**

According COSMIC-FFP and UML v. 1.4, the size of this software is three messages :

17
**INCORPORATING DATA MANIPULATION with UML V. 2.0**

Flowchart showing the 5 cases to test

18
**INCORPORATING DATA MANIPULATION with UML V. 2.0**

19
**INCORPORATING DATA MANIPULATION with UML V. 2.0**

According to UML v. 2.0, there are 6 messages exchanged So estimating the size by the number of messages exchanged would mean that this software has 6 function points.

20
**AGENDA INTRODUCTION MEASURING WITH COSMIC-FFP and UML V. 1.4**

INCORPORATING DATA MANIPULATION with UML V. 2.0 DISCUSSION OF RESULTS CONCLUSION

21
DISCUSSION OF RESULTS By modeling software in Actor-Object sequence diagram according to UML v. 1.4, it is possible to obtain an equivalent software size estimation to COSMIC-FFP by counting the number of messages exchanged

22
DISCUSSION OF RESULTS Going further and modeling software by UML v. 2.0 Actor-Object sequence diagram, it is possible to take into account data movements and data manipulation to size this software by counting the number of messages exchanged.

23
DISCUSSION OF RESULTS By modeling software in UML sequence diagram, and counting the number of messages involved, it is possible to get 3 types of measures: Actor-System Actor-Object (UML v. 1.4) Actor-Object (UML v. 2.0) which corresponds to stepwise refinement of requirements and models These results should then be tested at large with a sample of projects to model productivity

24
**AGENDA INTRODUCTION MEASURING WITH COSMIC-FFP and UML V. 1.4**

INCORPORATING DATA MANIPULATION with UML V. 2.0 DISCUSSION OF RESULTS CONCLUSION

25
**CONCLUSION UML is a standard notation to model software**

If those results are confirmed at large, the size could be determined at each step of the development process with more precision The count would be provided by case tools The software engineers would get the size directly by modeling the software and counting messages; he could forget about function point methods.

26
**Contact Ghislain Levesque and Valery Bevo De Tran Cao**

University of Quebec at Montreal Dept.of Computer Science P.O. Box 8888, Station C.V., Montreal De Tran Cao University of Cantho CICT, Vietnam

Similar presentations

OK

Requirements Engineering-Based Conceptual Modelling From: Requirements Engineering E. Insfran, O. Pastor and R. Wieringa Presented by Chin-Yi Tsai.

Requirements Engineering-Based Conceptual Modelling From: Requirements Engineering E. Insfran, O. Pastor and R. Wieringa Presented by Chin-Yi Tsai.

© 2018 SlidePlayer.com Inc.

All rights reserved.

To make this website work, we log user data and share it with processors. To use this website, you must agree to our Privacy Policy, including cookie policy.

Ads by Google