1.
Overview
When developing software system we normally define or write multiple programs in order to achieve the goal(s).  Computer Programs often stand alone to solve a user¡¯s specific problems.  Most of the computer programs are, however part of a larger system (Farrell, 2002).  If you were developing a College Information System, you may have to develop a number of programs to perform individual tasks within the system.  You may have to develop a program to addStudentEnrollment(), createSemesterSchedule(), changeStudentEnrollment() and so on.  Because of this scenario, the UML was developed.  The UML would allow for each programmer, though programming different parts of the system, to view a common model of the system before proceeding to write any code.  This will allow them to write the code allowing the programs to be integrated without any problems.

This paper focuses on representing graphical depictions a software system utilizing the UML¡¯s main diagrams.  You can find out more about the UML from the books mentioned in the further reading section of this paper and from the UML specification documents found at the Object Management Groups UML resource