2. I. UML Tool review (Rhapsody) and II. Requirement and TEST in UML modeling May 31th 2005 KIM, YUN GOO Lab Seminar

3. 2 I. UML Tools  There are many UML TOOLs  Rational Rose  I-Logixs Rhapsody  Boland Together  Plastic Software (KOREA)  Each Tool has it’s own characteristics  Rhapsody has been reviewed (3 day training course)  Major characteristics of Rhapsody  Usage of each type of UML diagram in Rhapsody

4. 3 Basic Window Configuration Browser Object Model Diagram Active code view

5. 4 Review Rhapsody with Examples.  Cash Register

6. 5 Package Diagram- Object Model Diagram

7. 6 Requirement Pkg  Requirement is only for information

8. 7 Analysis Pkg – Use Case Diagram

9. 8 Rhapsody-Class Diagram

10. 9 Rhapsody-Implementation Dynamic Model Code Associates

11. 10 Rhapsody-State chart Diagram  2 diagrams are used for code generation (Class, State chart)  Every condition and action for the state change should be manually coded.

12. 11 Sequence Diagram  Sequence chart is used for modeling.  Animated Sequence chart can be generated

13. 12 Sequence Diagram - Comparison One major difference!

14. 13 Summary for Rhapsody  Characteristics  State chart Diagram based modeling and code generation  Automatic code generation.  Usage of UML Diagram  Code generation  Class diagram  State chart diagram  Modeling  Use case diagram (analysis)  Sequence diagram (model check)  Requirement – Text based (No UML diagram)

15. 14 S/W development and V&V plan Statement UML Requirements Design Implementation Test SRS Statement UML SDD Automatic Code Generation Concept CD Statement UML Test Procedure Test case Generation Conversion algorithm to Formal specification Formal verification Test Case Generation-I STATEMATE MAGNUM Apply to RMS S/W V&V SRS for RMS SDD for RMS Test Execution Sample Module Code Generation RMS Software 1 st year 2 nd year : Korea Univ. Test Case Generation-II

16. 15 Requirement V&V Activity  Traceability analysis  Software requirement evaluation  Interface analysis  Criticality analysis  System V&V test plan generation and verification  Acceptance V&V test plan generation and verification  Configuration management assessment  Hazard analysis  Risk analysis  Concept document  SRS  IRS  System test plan  Acceptance test plan DocumentsActivities  Use case diagrams  Test case generation from use case diagram UML

17. 16 Test Case Generation Requirement Design Test  System Requirement  System test (Plan, procedure & report)  Acceptance Test Implementation  Unit Requirement  Detail Function Black Box Test White Box Test Unit Test  Unit Test  Integration Test Use Case Diagram, Class Diagram Use case diagrams Class diagrams Sequence Diagram Collaboration diagram Activity, and interaction diagrams

18. 17 Requirement with Use Case Diagram  General Requirement : (KHNP ITT Spec)  The Radiation Monitoring System (RMS) shall be a computer based data acquisition, analysis, display, and report generating system.

19. 18 Requirement with Class Diagram  The following indications and control functions shall be provided at each local unit panel as a minimum:  Alarm indication and acknowledge  Data entry  Contact output signal (optically isolated signal for Class 1E monitor)  Check source control  Sample pump/blower control (if required)  Purge/flush control (if required)  Data digital display  Display selection  Moving filter control  Analog output signal (isolated signal for Class 1E monitor)  Lamp test for all alarms and status indications  LED lights shall be used for the indicating lights as much as practicable. average minAvg hourAvg dayAvg calibrationConstant const1 const2 alarmSetPoint alertSetPoint highSetPoint

20. 19 Requirement with UML : Difficulties  Below requirement is difficult to be modeled with UML  Access to the radiation monitoring system's alarm setpoints shall be under administrative control.  The alarms shall not operate if the RMS is switched off.  Detail design part is needed.  Stereotype will be considered.

21. 20 Summary and Discussion  One of UML Tool, Rhapsody is reviewed.  Powerful code generation  State chart diagram is the main diagram and other diagram is used just for analysis or requirement.  Rhapsody can be used in our research project, but it can not cover all UML diagram.  Requirement for RMS is reviewed.  Test case generation during S/W life cycle is considered.  Requirement try to be written with UML  Detail configuration is needed  Requirement will be written with UML  Test plan and procedure will be written in requirement phase