Comparison of CASE tools Rational Software Architect and Poseidon

1. Comparison of CASE tools Rational Software Architect and Poseidon Presented by Mehrdad Nojoumian Mohammad AlHaj

2. Content Context High-level goals Evaluation criteria Evaluation methodology Presentation tools Evaluation of candidate tools/techniques Summary and recommendation

3. Context Integrated Software Systems, Inc. is a computer software company. ISS originally provided software-consulting services to financial institutions desiring to develop financial software. Developed a Loan Payment Processing software (LPP) Between 1988 and 1996, ISS developed three releases (LPP88, LPP92 and LPP96).

4. In 2000, a new software product (LPP2000) was released. Client complain: some of the new functions did not operate properly. There was a serious problem in the software itself Poor designing of the new features was the cause of the problem. This was due to using improper development tools Reviewing the design/implementation phase using a suitable UML tool that is capable of achieving round trip engineering

5. Goals Diagram support support all the nine diagrams that make up UML. Forward Engineering Generate code from the UML models of the system under development Reverse Engineering Extract model diagrams from the code Integrating with the current development process Change management

6. Compatibility with other tools Integrate with the other tools which are used in the company Help document support Provide a well design and easy use help document Implementation cost

7. Evaluation Criteria UML diagram set Level of impact: Medium Code generation Level of impact: High Code Compilation/Execution Level of impact: High Model transformation Level of impact: Medium

8. Model Extraction Level of impact: High Model accuracy Level of impact: High Code manipulation Level of impact: Medium Model Manipulation Level of impact: Medium

9. Easy browsing Level of impact: Low Initial/Operation cost Level of impact: Low Training cost Level of impact: Low

10. Evaluation Methodology We developed a test case for each evaluated criteria. Test case is a set of procedures or conditions under which a tester will determine if a requirement upon an application is partially or fully satisfied. For each test case, we developed a scenario

11. Test cases used to evaluate the Forward Engineering TC-1: Test Code generation Develop a tested Class Diagram Generate code from it Check and count the conflict between the code and the tested class diagram Add new class diagram to the tested diagram Repeat procedure (b), and (c) TC-2: Test Code compilation/Execution Use the code generated from TC-1 Compile the code, and find if there is errors or warnings. Then execute. Repeat (b) after each changes in TC-1

12. Test cases used to evaluate the Reverse Engineering TC-3: Test Model Extraction Develop a tested Code Extract a class diagram from it Check and count the conflicts between the code and the class diagram Add new class to the tested code Repeat procedure (b), and (c) TC-4: Test Model accuracy Use the tested code from TC-3 Add, delete, or change the components of the code Determine the accuracy by counting the conflicts between the code and the class diagram

13. Test case used to evaluate the Diagram Support TC-5: Test UML diagram set Open User case, Class, Object, Sequence, Activity, State, Collaboration, Component, and Deployment diagrams Check the diagram components library Compare the diagram set completeness of each tool Test case used to evaluate the Help Support TC-5: Test Easy browsing Check for the feature of the “Help” command in the tool bar Search for technical word, a tool function, or operation Compare the easiness of each tool

14. Presentation of tools Rational Rose Modeling tool from Rational Software Corporation Rose stands for "Rational Object-oriented Software Engineering” An integrated, full cycle-solution which claims to combine software engineering best practices, market-leading tools, and professional services. It comes in different versions suited to different requirements

15. Rational Rose Enterprise Interesting feature of Rational Rose is the ability to publish the UML diagrams as a set of Web pages and images

16. Poseidon Developed by Gentleware It originated from the ArgoUML open source project. Supports forward and reverse engineering and documentation generation by using special-purpose plug-ins. It comes in different flavors suited to different requirements Poseidon Professional Edition v4.1 It offers the Poseidon for UML Community Edition 1.5 free for individual software developers.

17. Evaluation of tools This section is not finished We developed a test application (Information System) It contains 33 classes, with a multiple layer architecture Evaluation grades: Fully supported 4 grades Good support 3 grades Partially supported 2 grades Weakly supported 1 grade Unsupported 0 grade

19. TC-5: Test UML diagram set

21. TC-5: Test Easy browsing

23. Summary and recommendation The purpose of the project is to make comparison between Rational Rose Ent. And Poseidon Pro. The business goal is buying a UML tool that is capable of achieving round trip engineering From the business goal, we defined the sub-goals From the sub-goals, we defined the evaluation criteria. We developed a test cases to test the criteria Right now, We are not able not recommend any tool , because the evaluation is not finished.

24. Questions