<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>DSpace Collection:</title>
  <link rel="alternate" href="http://dspace.dtu.ac.in:8080/jspui/handle/123456789/53" />
  <subtitle />
  <id>http://dspace.dtu.ac.in:8080/jspui/handle/123456789/53</id>
  <updated>2026-04-28T04:04:55Z</updated>
  <dc:date>2026-04-28T04:04:55Z</dc:date>
  <entry>
    <title>PROJECT REPORT ON STUDY OF RATIONAL ROSE</title>
    <link rel="alternate" href="http://dspace.dtu.ac.in:8080/jspui/handle/repository/13524" />
    <author>
      <name>KUMAR, AMRENDRA</name>
    </author>
    <author>
      <name>DANGRI, ANUJ</name>
    </author>
    <author>
      <name>SAINI, ASHISH KUMAR</name>
    </author>
    <author>
      <name>KOCHHAR, SHIKHA</name>
    </author>
    <id>http://dspace.dtu.ac.in:8080/jspui/handle/repository/13524</id>
    <updated>2014-12-19T11:15:52Z</updated>
    <published>2006-01-30T00:00:00Z</published>
    <summary type="text">Title: PROJECT REPORT ON STUDY OF RATIONAL ROSE
Authors: KUMAR, AMRENDRA; DANGRI, ANUJ; SAINI, ASHISH KUMAR; KOCHHAR, SHIKHA
Abstract: Rational Rose is a CASE Tool, a category of software that&#xD;
provides a development environment for programming teams. It&#xD;
helps to automate, manage and simplify the Software&#xD;
development process. These can include tools for: Summarizing&#xD;
initial requirements, Developing flow diagrams, Scheduling&#xD;
development tasks, preparing documentation, controlling&#xD;
software versions and developing program code.&#xD;
Rational Rose is the visual modeling software solution that lets&#xD;
you create, analyze, design, view, modify, and manipulate&#xD;
components. You can graphically depict an overview of the&#xD;
behavior of your system with a use-case diagram. Rational Rose&#xD;
provides the collaboration diagram as an alternative to a usecase&#xD;
diagram. It shows object interactions organized around&#xD;
objects and their links to one another. The statechart diagram&#xD;
provides additional analysis techniques for classes with&#xD;
significant dynamic behavior. Activity diagrams provide a way to&#xD;
model a class operation or the workflow of a business process.&#xD;
The logical architecture is captured in class diagrams that&#xD;
contain the classes and relationships that represent the key&#xD;
abstractions of the system under development. The component&#xD;
architecture is captured in component diagrams that focus on the&#xD;
actual software module organization within the development&#xD;
environment. The deployment architecture is captured in&#xD;
deployment diagrams that map software to processing nodes—&#xD;
showing the configuration of run-time processing elements and&#xD;
their software processes.&#xD;
The thesis starts with an introduction to Rational Suite&#xD;
Components and how the use of rational suite makes the&#xD;
development process simplified. Then a brief description of&#xD;
Visual modeling is given followed by UML description and how a&#xD;
10&#xD;
system is depicted in UML notations. Then a brief about&#xD;
Rational Rose is provided with its features. How to start working&#xD;
in Rational Rose is summarized via the Interface area of&#xD;
Rational Rose. Namely interface is divided into: Application&#xD;
window, Browser window, Documentation window, Diagram&#xD;
window, Overview window, Specification window and Log&#xD;
window.&#xD;
Then various diagrams which are supported by Rational Rose&#xD;
are explained, namely: Class diagram, Object diagram, Use-case&#xD;
diagram, Collaboration diagram, Sequence diagram, Component&#xD;
diagram, Statechart diagram, Deployment diagram and Activity&#xD;
diagram.&#xD;
After this much of theoretical introduction two case studies are&#xD;
done, namely: Student Registration System and Online Auction&#xD;
System. For both case studies all diagram windows are created&#xD;
and the overall complex structure for problems is simplified by means of object orientation
Description: BE PROJECT REPORT</summary>
    <dc:date>2006-01-30T00:00:00Z</dc:date>
  </entry>
</feed>

