Experiences of using rational rose/visio for UML modeling in an undergraduate software engineering course: a student perspective

  • Authors:
  • Aydaen Lynch;Darynn Flango;Rob Smith;Matthew Lang

  • Affiliations:
  • Indiana University of Pennsylvania;Indiana University of Pennsylvania;Indiana University of Pennsylvania;Indiana University of Pennsylvania

  • Venue:
  • Journal of Computing Sciences in Colleges
  • Year:
  • 2004

Quantified Score

Hi-index 0.00

Visualization

Abstract

In the past, Visio has been used as the UML modeling tool for the software engineering concept course at IUP (Indiana University Of Pennsylvania). Two years ago, Rational Rose (Rose) was introduced in parallel. Students now have a choice of using either tool for UML modeling. Since the introduction of Rose, about 100 students have used both tools for UML modeling. In the fall of 2002, we set out to investigate the student experiences of using Rose and Visio. A student questionnaire survey was administered in the Computer Science Department at IUP. The main objective of the survey was to determine the usability of Rose and Visio for UML modeling in a software engineering course. Participating students were software engineering students registered for semester course. At the end of each semester, samples of data were collected. By the end of October 2003, we had a sample size of 95 to analyze. The collected data included student experiences of using Rose and Visio in the production of use-case diagrams, class diagrams, activity charts and collaboration charts. The 95 respondents had a great deal of exposure creating documentation for large software engineering semester projects and mini design projects. Typical examples of projects include the payroll systems, a web-based student registration system, a video rental system and children games (hangman and the number munchers game). The created use-case diagrams had an average of ten use-cases and eight actors. The class diagrams had an average of eight classes. The questionnaire was designed to provide information in the following categories; symbols used, interface, product features, intuitiveness in diagram creation, documentation and output.