06-12-2012, 06:29 PM
A representative paper design on Bus Reservation System
A representative paper.docx (Size: 420.14 KB / Downloads: 46)
AIM:
Design a representative design on bus reservation system using Navigation Diagram, Component Diagram, Interface Diagram & Deployment Diagram using UML 2.0
THEORY:
Interface Diagram:
An interface is a classifier that has declarations of properties and methods but no implementations. You can use interfaces to group common elements between classifiers and provide a contract a classifier that provides an implementation of an interface must obey. For example, you can create an interface named Sortable that has one operation named comesBefore(...). Any class that realizes the Sortable interface must provide an implementation of comesBefore(...).
Some modern languages, such as C++, don't support the concept of interfaces; UML interfaces are typically represented as pure abstract classes. Other languages, such as Java, do support interfaces but don't allow them to have properties. The moral is that you should be aware of how your model is going to be implemented when modeling your system. There are two representations for an interface; which one you should use depends on what you're trying to show. The first representation is the standard UML classifier notation with the stereotype .
Navigation Diagram (Navigation Map):
Navigation diagram or navigation map is based on the use cases and shows the most important navigation paths. A navigation path is a sequence of screens (windows, web pages) traversed by the user. How does the map look like. The active screen is considered to be the state of the user interface and the transition arrows show the possible navigation paths.
Component Diagram:
Component Diagrams illustrate the pieces of software, embedded controllers, etc. that will make up a system. A Component diagram has a higher level of abstraction than a Class diagram -usually a component is implemented by one or more classes (or objects) at runtime. They are building blocks, such that eventually a component can encompass a large portion of a system. Components are similar in practice to package diagrams as the define boundaries and are used to group elements into logical structures. The difference between Package Diagrams and Component diagrams is that Component Diagrams offer a more semantically rich grouping mechanism. With Component Diagrams all of the model elements are private whereas Package diagrams only display public items.