Introduction to using UML with Rational Rose #1.pdf

Department of Electrical & Electronic Engineering specification is not available, and in practice part of your job would be to refine these
Department puter Science & Software Engineering requirements to the point that they can be documented and form the basis of an agreement (or
Software Engineering 104 - Laboratory contract) to proceed with the design of the software to meet those requirements. Now "refining
the requirements" sounds easy, but in fact, it requires a great deal of skill and experience to do it
right (and this is because failures in many software projects can be traced to getting this early bit
UML #1: Introduction to using UML with Rational Rose wrong). It also requires lots of "people skills" (and patience) as well as good technical skills. For
the unit registration system you are told that you have all the requirements there are, which is
1. Aims very rare. In practice, this usually requires many meetings, so what is very important is to have
mon a language as possible between the "requirements capturer" and the "requirements
The approach taken in this lab to give you some "hands-on" with UML, is to solve a problem generator". In UML that part of the language is the use case.
posed by a requirement to design a small software system, and then use UML via Rational Rose
to partially document that design. You will not use anywhere nea