Ex.

no: 1 Date: UML DIAGRAMS

STUDY OF UML DIAGRAMS

There are three classifications of UML diagrams: • • • Behavior diagrams. A type of diagram that depicts behavioral features of a system or business process. This includes activity, state machine, and use case diagrams as well as the four interaction diagrams. Interaction diagrams. A subset of behavior diagrams which emphasize object interactions. This includes communication, interaction overview, sequence, and timing diagrams. Structure diagrams. A type of diagram that depicts the elements of a specification that are irrespective of time. This includes class, composite structure, component, deployment, object, and package diagrams. Description Learning Priority Depicts high-level business processes, including High data flow, or to model the logic of complex logic within a system. Shows a collection of static model elements such as High classes and types, their contents, and their relationships. Shows instances of classes, their interrelationships, Low and the message flow between them. Communication diagrams typically focus on the structural organization of objects that send and receive messages. Formerly called a Collaboration Diagram. Depicts the components that compose and Medium application, system, or enterprise. The components, their interrelationships, interactions, and their public interfaces are depicted. Depicts the internal structure of a classifier(such as Low a class, component, or use case), including the interaction points of the classifier to other parts of the system. Shows the execution architecture of systems. This Medium includes nodes, either hardware or software execution environments, as well as the middleware connecting them. A variant of an activity diagram which overviews Low the control flow within a system or business process. Each node/activity within the diagram can represent another interaction diagram.

Diagram Activity Diagram Class Diagram Communication Diagram

Component Diagram Composite Structure Diagram Deployment Diagram Interaction Overview Diagram

Object Diagram

Package Diagram Sequence Diagram State Machine Diagram Timing Diagram

Depicts objects and their relationships at a point in Low time, typically a special case of either a class diagram or a communication diagram. Show how model elements are organized into Low packages as well as the dependencies between packages. Models the sequential logic, in effect the time High ordering of messages between classifiers. Describes the states an object or interaction may be Medium in, as well as the transitions between states. Formerly referred to as a state diagram, state chart diagram, or a state-transition diagram. Depicts the change in state or condition of a Low classifier instance or role over time. Typically used to show the change in state of an object over time in response to external events. Shows use cases, actors, and their Medium interrelationships.

Use Case Diagram

USE CASE DIAGRAM: A use case diagram is a type of behavioral diagram defined by the Unified Modeling Language (UML). Its purpose is to present a graphical overview of the functionality provided by a system in terms of actors, their goals- represented as use cases- and any dependencies between those use cases. Use case diagram depict: • • • Use cases. A use case describes a sequence of actions that provide something of measurable value to an actor and is drawn as a horizontal ellipse. Actors. An actor is a person, organization, or external system that plays a role in one or more interactions with your system. Actors are drawn as stick figures. Associations. Associations between actors and use cases are indicated in use case diagrams by solid lines. An association exists whenever an actor is involved with an interaction described by a use case. Associations are modeled as lines connecting use cases and actors to one another, with an optional arrowhead on one end of the line. The arrowhead is often used to indicating the direction of the initial invocation of the relationship or to indicate the primary actor within the use case. The arrowheads are typically confused with data flow and as a result I avoid their use. System boundary boxes (optional). You can draw a rectangle around the use cases, called the system boundary box, to indicate the scope of your system.

Anything within the box represents functionality that is in scope and anything outside the box is not. System boundary boxes are rarely used, although on occasion I have used them to identify which use cases will be delivered in each major release of a system. • Packages (optional). Packages are UML constructs that enable you to organize model elements (such as use cases) into groups. Packages are depicted as file folders and can be used on any of the UML diagrams, including both use case diagrams and class diagrams. I use packages only when my diagrams become unwieldy, which generally implies they cannot be printed on a single page, to organize a large diagram into smaller ones.

List Items

View Item

Edit Item Actor

Create Item

Delete Item RELATIONSHIPS IN USE CASE DIAGRAM: Three relationships among use cases are supported by the UML standard, which describes graphical notation for these relationships. Include In one form of interaction, a given use case may include another. The first use case often depends on the outcome of the included use case. This is useful for extracting truly common behaviors from multiple use cases into a single description. The notation is a dashed arrow from the including to the included use case, with the label “<<include>>”. This usage resembles a macro expansion where the included use case

and then immediately enrolls in three seminars. . A sequence diagram shows. There are no parameters or return values. is a visual object code. or in accommodating new requirements during system maintenance and extension. 2. (the extension) may extend another. as horizontal arrows. plus one or more alternate scenarios. One way to think of sequence diagrams. a given use case. as parallel vertical lines. For example. Generalization In the third form of relationship among use cases. a generalization/ specialization relationship exists. the messages exchanged between them. Usage scenarios. particularly highly detailed diagrams. Sequence diagrams can be used to explore the logic of a complex operation. The notation is a solid line ending in a hollow triangle drawn from the specialized to the more general use case. and deal same as except details in the specialized cases. It may also be one entire pass through use case. This can be useful for dealing with special cases.behavior is placed inline in the base use case behavior. The logic of a usage scenario may be part of a use case. different processes or objects that live simultaneously. constraints and assumptions to the general use case. A given use case may be specialized form of an existing use case. such as the logic described by the basic course of action or a portion of the basic course of action. in practice it can be both useful and effective to factor common behaviors. The logic of methods. a student enrolls in the university. Extend In another form of interaction. function. perhaps an alternate course. describe them once. in the order in which they occur. This resembles the object-oriented concept of sub-classing. A usage scenario is a description of a potential way your system is used. or procedure. and. This relationship indicates that the behavior of the extension use case may be inserted in the extended use case under some conditions. The logic of a usage scenario may also be a pass through the logic contained in several use cases. Sequence diagrams are typically used to model: 1. with the label <<extend>>. This allows the specification of simple runtime scenarios in a graphical manner. The notation is a dashed arrow from the extension to the extended use case. To make the points at which extension may occur explicit extension points may be defined in use cases which are listed in a compartment below the use case name. SEQUENCE DIAGRAM: The well-known Message Sequence Chart technique has been incorporated into the Unified Modeling Language (UML) diagram under the name of Sequence Diagram.

an activity diagram represents the business and operational step-by-step workflows of components in a system. This includes web-services as well as business transactions implemented by a variety of technologies such as CICS/COBOL or CORBA-compliant object request brokers (ORBs). An activity diagram shows the overall flow of control. Renee Bob Waiter Hank Cook Fred Patron Cashier order food() order food() serve wine() Pickup() serve food() Pay() ACTIVITY DIAGRAM: In the Unified Modeling Language. . often one that can be invoked by a wide variety of clients.3. The logic of services. A service is effectively a high-level method.

also called swim lanes. or electronic. The filled circle with a border is the ending point. • • • • • • • • • • • . A diamond with one flow entering and several leaving. based on any guards on the outgoing flow. Registrar. An initial node isn’t required although it does make it significantly easier to read the diagram. Text such as [Incorrect Form] on a flow. An activity diagram can have zero or more activity final nodes. I’ll use the term flow. The rake in the bottom corner of an activity. Join. Condition. Decision. All flows going into the join must reach it before processing may continue. A black bar with several flows entering it and one leaving it. Flow final. indicating who/what is performing the activities (the Applicant. Sub-activity indicator. The rounded rectangles represent activities that occur.Describing the basic notations: • Initial node. An activity may be physical. The circle with the X through it. indicates that the activity is described by a more finely detailed activity diagram. This denotes the end of parallel processing. Merge. Flow/edge. A black bar with one flow going into it and several leaving it. or System). such as Inspect Forms. Activity. The flows leaving include conditions although some modelers will not indicate the conditions if it is obvious. This denotes the beginning of parallel activity. Although there is a subtle difference between flows and edges I have never seen a practical purpose for the difference although I have no doubt one exists. defining a guard which must evaluate to true in traverse the node. such as Display Create Student Screen. A diamond with several flows entering and one leaving. Activity Diagram is organized into many partitions. Partition. The filled in circle is the starting point of the diagram. Activity final node. such as in the Apply to University activity. Fork. The arrows on the diagram. This indicates that the process stops at this point. The implication is that one or more incoming flows much reach this point until processing continues.

a class diagram is a type of static structure diagram that describes the structure of a system by showing the system’s classes. their attributes. and the relationships between the classes.Verify reservation [incorrect] [correct] Get preferences Send to airport travel agency [no baggage] [baggage] Receive baggage and print receipt Print boarding Card Give travel documentation to passenger CLASS DIAGRAM: In the Unified Modeling Language (UML). .

A link is an instance or an association. composition is more specific than aggregation. multiplicity. its contents are not. an aggregation can be named and have the same adornments that an association can. Higher order associations can be drawn with more than two ends. There are five different types of association. Bi-directional and uni-directional associations are the most common ones. In UML. In such cases. and other properties. . it is graphically represented as a clear diamond shape on the containing class end of the tree of lines that connect contained class(es) to the containing class. the ends are connected to a central diamond. but where the contained classes do not have a strong life cycle dependency on the container—essentially. For instance. It can be shown on an object diagram or class diagram. Binary associations (with two ends) are normally represented as a line. if the container is destroyed. Associations can only be shown on class diagrams. with each end connected to a class box. However.Relationships A relationship is general term covering the specific types of logical connections found on class and object diagrams. composition is more specific than aggregation. an aggregation may not involve more than two classes. o Aggregation Class diagram showing Aggregation between two classes Aggregation is a variant of the “has a” or association relationship. Aggregation can occur when a class is a collection or container of other classes. ownership indicators. visibility. It is represented as a line connecting two or more object boxes. a flight class is associated with a plane class bi-directionally. An association can be named. and the ends of an association can be adorned with role names. UML shows the following relationships: • Instance-Level Relationships o Link A Link is the basic relationship among objects. o Association An Association represents a family of links. o Composition Composition is a stronger variant of the “has a” or association relationship. As a type of association.

. an aggregation relationship is best.”an oak is a type of tree”.g. derived class. an engine is part of a car. In practice.1 or 1. e. The relationship is most easily understood by the phrase ‘A is a B’. • Generalization-Specialization relationship A is a type of B E.g. This is often called a “catalog” relationship.g. every instance that it contains is destroyed as well. or inheriting type. or base type. However. The subtype in the generalization relationship is also known as the “child’. inheriting class. ENG01 may be also part of a different car model. the composition relationship is most appropriate. o Differences between Composition and Aggregation The whole of a composition must have a multiplicity of 0. this means that any instance of the subtype is also an instance of the supertype. subclass. • Class Level Relationships o Generalization Class diagram showing generalization between one super class and two subclasses The generalization relationship indicates that one of the two related classes (the subtype) is considered to be a specialized form of the other (the supertype) and supertype is considered as GENERALIZATION of subtype. base class. The generalized relationship is also known as the inheritance or “is a“ relationship. The UML graphical representation of a composition relationship is a filled diamond shape on the containing class end of the tree of lines that connect contained class(es) to the containing class. The whole of an aggregation may have any multiplicity. When attempting to represent real-world whole-part relationships.. “a sedan is a type of vehicle” . e.. derived type. car model engine ENG01 is part of a car model CM01. The supertype in the generalization relationship is also known as the “parent”. when representing a software or database relationship. as the engine. super class.Composition has a strong life cycle dependency between instances of the container class and instances of the contained class(es): If the container is destroyed. The UML graphical representation of a Generalization is a hollow triangle shape on the supertype end of the line (or tree of lines) that connects it to one or more subtypes. indicating that a part must be for only one whole. CM02.

this is most easily understood through the phrase ‘A has a B’{a mother cat has kittens. Common multiplicities are: Indicator 0.* n 0.n 1. In contrast with the generalization relationship. A realization is displayed in the diagram editor as a dashed line with an unfilled arrowhead towards the supplier.n Meaning No instances.. may) Exactly one instance Zero or more instances One or more instances(at least one) Exactly n instances(n>1) Zero or n instances(n>1) One or n instances(n>1) .1 1 0. or one instance(optional. or both.. A dependency can be between instances.o Realization In UML modeling. • Multiplicity The association relationship indicates that (at least) one of the two related classes makes reference to the other. a realization relationship is relationship between model elements.* or * 1... class.. in which one model element (the client) realizes the behavior that the other model element (the supplier) specifies. The UML representation of an association is a line with an optional arrowhead indicating the role of the object(s) in the relationship. This is indicated by a dashed pointing from the dependent to the independent element. Several named varieties exist. • General Relationship o Dependency(UML) A dependency exists between two defined elements if a change to the definition of one would result in a change to the other. kittens have a mother cat}. and an optional notation at each end indicating the multiplicity of instances of that entity ( the number of objects that participate in the association).

<<Class Module>> main window +1 +1 <<Class Module>> login window +1 +1 <<Class Module>> welcome window <<Class Module>> login control <<Class Module>> error message COMPONENT DIAGRAM: In the Unified Modeling Language. Component diagrams are particularly useful with larger teams. Once the interfaces are defined. changes that need to be negotiated between the sub teams and then implemented appropriately. a component diagram depicts how a software system is split up into physical components and shows the dependencies among these components. it makes it much easier to organize the development effort between sub teams. UML component diagrams are great for doing this as they enable you to model the high-level software components. and more importantly the interfaces to those components. Component diagrams can be used to model and document any system’s architecture. link libraries. <<ActiveX DLL>> view courses details <<ActiveX DLL>> login <<ActiveX DLL>> registration <<ActiveX DLL>> security <<ActiveX DLL>> validation . for example. files. or packages. header. Physical components could be. You will discover the need to evolve the interfaces to reflect new requirements or changes to your design as your project progresses. and agreed to by your team. Your initial architectural modeling efforts during cycle 0 should focus on identifying the initial architectural landscape for your system. executables. modules.

sequence. Rational Rose documents the diagram as it is being constructed and then generates code in the designer’s choice of C++.More recent versions of Rational Rose also allow for additional documentation in the form of word-processed documents and/or URLs to Web-based materials. without dealing with the specifics of how it will be implemented.) Then. objects(rectangles) and messages/relationships(arrows) in a sequence diagram using dragand-drop symbols. Views in UML/Rational Rose There are four views for a model created in Rational Rose. and Corba component standards. which . JavaBeans. Two popular features of Rational Rose are its ability to provide iterative development and round-trip engineering. The purpose of the use case view is to envisage what the system must do.CORBA or Data Definition Language.(This is in contrast to waterfall development where the whole project is completed from start to finish before a user gets to try it out. Visual Basic. Logical View The logical view contains the diagrams used in object design(class diagrams and state transition diagrams). Rational rose is extensible. as the developer begins to understand how the components interact and makes modifications in the design. actors).INTRODUCTION TO RATIONAL ROSE Rational rose Rational Rose is an object-oriented Unified Modeling Language(UML) software design tool intended for visual modeling and component construction of enterprise-level software applications. The basic element in this view is the class. and all the elements that compromise these diagrams(e. and collaboration). each representing the system from a different point of view.g. Java. The Use Case View The use case view contains the diagrams used in analysis(use case. It supports COM/DCOM(ActiveX). Oracle8. use case elements(ovals).. Rational Rose allows designers to take advantage of iterative development(sometimes called evolutionary development) because the new application can be created in stages with the output of one iteration becoming the input to the next. a software designer uses Rational rose to visually create(model) the framework for an application by blocking out classes with actors(stick figures). with downloadable add-ins and third-party applications. Rational Rose can perform what is called “round-trip engineering” by going back and updating the rest of the model to ensure the code remains consistent. It offers a detailed view of how the system envisaged in the use case view will be implemented. In much the same way a theatrical director blocks out a play.

A programmer can put together an application using the components provided with Visual Basic itself.includes an outline of its attributes and operations. This directly corresponds to a class created in your chosen implementation language. Components can be pre-existing. This view is necessary for complex applications in which a system will have different components located on different machines. From the logical view. changes that need to be made during implementation can be reflected in the documentation of the design model. Scripting languages such as VBA and VBScript are syntactically similar to Visual Basic. access to databases using DAO. INTRODUCTION TO VISUAL BASIC Visual Basic (VB) is an event driven programming language and associated development environment from Microsoft for its COM programming model. executable programs. The language not only allows programmers to create simple GUI applications. In addition. Component View The component view is a step up from the logical view and contains diagrams used in system design(component diagrams). but also reverse engineer programs created in these languages into Rational Rose models. skeletal code can be generated for implementation into a computer language. For example. Visual Basic was derived from BASIC and enables the rapid application development(RAD) of graphical user interface(GUI) applications. Visual Java. and creation of ActiveX controls and objects. This allows existing components to be included in documented models. or ADO. More recent versions of Rational Rose not only can generate skeletal code for Visual C++. This includes information about the code libraries. but perform differently. interface components may be located on a user machine while other components may be located on a network server. if there is access to the source code. runtime libraries. LANGUAGE BASICS: Visual Basic was designed to be easy to learn and use. Deployment View The deployment view illustrates how the completed system will be physically deployed. but can also develop fairly . but doing so requires external function declarations. Components that do not exist and need to be created by the developers will have to be designed in the logical view. or Visual BASIC. a Windows program in Visual C++ will utilize Microsoft Foundation Class to provide the framework for the Windows interface. for example. and other software components that comprise the completed systems. RDO. Programs written in Visual Basic can also use the Windows API.

text boxes. etc. the program can automatically translate the case of the text being entered.complex applications as well. although it will transform keywords into a standard case configuration and force the case of variable names to conform to the case of the entry within the symbol table entry. but restrictions in the IDE do not allow the creation of some targets (Windows model DLL’s) and threading models. . Default values are provided when the control is created. and writing additional lines of code for more functionality. expands to fill up the form. code can be inserted into the form resize event handler to reposition a control so that it remains centered on the form. The Visual Basic compiler is shared with other Visual Studio languages(C. but can be made case insensitive if so desired. String comparisons are case sensitive by the default. etc. Forms are created using drag and drop techniques. Visual Basic is generally not case sensitive. a simple program can be created without the programmer having to write many lines of code.. but may be changed by the programmer. Controls have attributes and event handlers associated with them. C++). but with faster computers and native code compilation this has become less of an issue. or even prevent certain characters from being inserted. For example. Programming in VB is a combination of visually arranging components or controls on a form. Unlike many other programming languages. buttons. specifying attributes and actions of those components. By inserting code into the event handler for a keypress in a text box. Many attribute values can be modified during run time based on user actions or changes in the environment. A tool is used to place controls (e. providing a dynamic application.) on the form (window). Since default attributes and actions are defined for the components. Result: Thus the UML diagrams and introduction to Visual Basic was studied.g. Performance problems were experienced by earlier versions.

The administrator will be provided with an option to display the current status of application to the applicant. No: 2. The core of the system is to get the online registration form (with details such as name.PASSPORT AUTOMATION SYSTEM Ex. So this system uses several programming and database techniques to elucidate the work involved in this process.1 Purpose If the entire process of 'Issue of Passport' is done in a manual manner then it would take several months for the passport to reach the applicant.a Date: Aim: To Study the software requirements specification for passport automation system. 1. • The authority concerned with the issue of passport can use this system to reduce his workload and process the application in a speedy manner.0 Introduction Passport Automation System is an interface between the Applicant and the Authority responsible for the Issue of Passport.. . After all the necessary criteria has been met. an Automated System becomes essential to meet the demand. from which they can select one. This system adopts a comprehensive approach to minimize the manual work and schedule resources. The system forwards the necessary details to the police for its separate verification whose report is then presented to the administrator.2 Scope • The System provides an online interface to the user where they can fill in their personal details and submit the necessary documents (may be by scanning). the original information is added to the database and the passport is sent to the applicant. Considering the fact that the number of applicants for passport is increasing every year. Software Requirements Specification 1. It aims at improving the efficiency in the Issue of Passport and reduce the complexities involved in it to the maximum possible extent. The application is then processed manually based on the report given by the system.) filled by the applicant whose testament is verified for its genuineness by the Passport Automation System with respect to the already existing information in the database. time in a cogent manner. Problem Statement Passport Automation System is used in the effective dispatch of passport to all of the applicants. 1. address etc. the information is in turn forwarded to the regional administrator's (Ministry of External Affairs) office. After the first round of verification done by the system. which they can view in their online interface. As this is a matter of National Security. the system has been carefully verified and validated in order to satisfy it. and any forfeiting identified can make the applicant liable to penalty as per the law. This forms the first and foremost step in the processing of passport application. The system also provides the applicant the list of available dates for appointment to 'document verification' in the administrator's office.

0 Overall Description 2. • J2EE – Java 2 Enterprise Edition is a programming platform and it is the partof the java platform for developing and running distributed java applications. This system tries to make the interface as simple as possible and at the same time not risking the security of data stored in. • Web Server . • Back End . 1.Markup Language used for creating web pages.6 Tools to be Used • Eclipse IDE ( Integrated Development Enivronment) • Rational Rose tool ( for developing UML Patterns) 1. • HTML . • Javascript • AJAX . 1. It can be any higher official in the Regional Passport Office of Ministry of External Affairs.4 References IEEE Software Requirement Specification format. • HTTP .Refers to this Passport Automation System.7 Overview SRS includes two sections overall description and specific requirements .3 Definitions.One who wishes to obtain the Passport. Specific requirements will describe roles & functions of the actors.The applicant and Administrator online interface is built using JSP and HTML.1 Product Perspective The PAS acts as an interface between the 'applicant' and the 'administrator'.2 Software Interface • Front End Client . • Users/Applicants will come to know their status of application and the date in which they must subject themselves for manual document verification. • PAS . 2. The Administrators's local interface is built using Java. • Transfer of data between the Passport Issuing Authority and the Local Police for verification of applicant's information.Overall description will describe major role of the system components and inter-connections. 1.Refers to the super user who is the Central Authority who has been vested with the privilege to manage the entire system.5 Technologies to be used • HTML • JSP • Java • XML 1. • Applicant . 2. • TCP/IP – Transmission Control Protocol/Internet Protocol is the communication protocol used to connect hosts on the Internet.Oracle database.Hyper Text Transfer Protocol. This minimizes the time duration in which the user receives the passport.• Provide a communication platform between the applicant and the administrator. Acronyms and the Abbreviations • Administrator .Glassfish application server(Oracle Corporation).

there is always a chance of intrusion in the web world which requires constant monitoring. The client systems have access to the database in the server. Result: Thus the software requirements specification for passport automation system was studied. The usecase model describes the uses of the system and show the courses of events that can be performed.3 Hardware Interface The server is directly connected to the client systems. • Panel for Passport Application Status Display by the Administrator. Much care is required.7 Use Case Model Description The usecase model is a representation of the interaction between the users and the system. 2. • The user has to be careful while submitting the information.He is the person who upon receiving intimation from the PAS. perform a personal verification of the applicant and see if he has any criminal case against him before or at present. 2. Grouping of usecases can manages the complexities and reduce the number of usecases in the package. A usecase is an interaction between user and system. It captures the goals of the users and the responsibility of the system to the users.They are the people who desires to obtain the passport and submit the information to the database.He has the certain privileges to add the passport status and to approve the issue of passport. . • The applicants may be required to scan the documents and send. It defines what happens in the system when the usecase is performed.6 Constraints • The applicants require a computer to submit their information. • SMS and Mail updates to the applicants by the administrator.5 User Characteristics • Applicant . It is a special flow of events through the system. He communicates via this PAS. • Although the security is given high importance. 2. He may contain a group of persons under him to verify the documents and give suggestion whether or not to approve the dispatch of passport.8 Assumptions and Dependencies • The Applicants and Administrator must have basic knowledge of computers and English Language.4 System Functions • Secure Registration of information by the Applicants. • Schedule the applicants an appointment for manual verification of original documents. 2. He has been vetoed with the power to decline an application by suggesting it to the Administrator if he finds any discrepancy with the applicant. • Administrator . 2. it captures the goals of the user and the responsibility of the system to its users.2. • Administrator can generate reports from the information and is the only authorized personnel to add the eligible application information to the database. • Police .

Gantt Chart for Passport Automation System Ex No : 2. precedence network) relationships between activities. Introduction: A Gantt chart is a type of bar chart that illustrates a project schedule. .. Terminal elements and summary elements comprise the work breakdown structure of the project. Gantt charts can be used to show current schedule status using percent-complete shadings and a vertical "TODAY" line as shown here.e. Gantt charts illustrate the start and finish dates of the terminal elements and summary elements of a project. b Date: Aim: To develop a risk management and project plan for passport automation system using Gantt Chart. Some Gantt charts also show the dependency (i.

Detailed Design 5. Testing 6. Literature Survey and Specification 3.Passport Automation System For the project. the activities considered are: 1. Operation and Maintenance Result: Thus the risk management and project plan for passport automation system was designed using Gantt Chart. . Preliminary Design 4. Requirement Analysis 2.

Parents’ Name. PROBLEM STATEMENT To create a software system for the applicant(s). 2. they need to provide the DD details. Applicant Applicant has to provide the information like Name. And check whether the applicant is provided with passport or not. Phone no. Rational Rose 2.2 HARDWARE REQURIMENTS 1. Age. Gender. 128MB RAM 2. applying for the passport by verifying the information provided by them. Also.1 SOFTWARE REQURIEMENTS 1. 3. Passport Issuing Authority This system will verify the details provided by the applicant. Communication address. Pentium III Processor .NO:2 c DATE: AIM: To analyze and design a system for Passport Automation using Rational Rose tool. Database This will store the details of the applicant for future reference. OVERALL DESCRIPTION The modules are for 1. 1. PASSPORT AUTOMATION SYSTEM 2. The details of the applicant are stored in the Database. 2. Qualification. etc.EX.

1 USE CASE DIAGRAM apply for passprot ing A pplicant Issue applicant details P assport issue authority V erifythe applicant details Issue Passport Cancellation D B 3.3. DESIGN 3.2 CLASS DIAGRAM .

3.2 SEQUENCE DIAGRAM .

4 COMPONENET DIAGRAM JAVA CODING: Database.java public class database { private int applicantDetails. public database() { } public void storeTheDetails() { } .3.3 COLLABORATION DIAGRAM 3.

java public class APPLICANT { private int firstName. } public APPLICANT() { } PassportIssueAuthority. private int presnetAddress. private int Sex. private int phoneNumber. public passportIssueAuthority() {} public void issuePassport() { } public void verify() { } public void cancellation() { } } RESULT: . private int height. private int workPlace. public APPLICANT theAPPLICANT. private int permanentAddress. private int weight. private int authorityId. private int fathersName.public void issueDetailsToAuthortiy() { } } Applicant. public database theDatabase. public passportIssueAuthority thePassportIssueAuthority. private int DOB. private int DDNO. private int placeOfBirth. private int DDDATE. private int surname. private int mothersName.java public class passportIssueAuthority { private int authorityName. private int emailId. private int district. private int qualification.

4. To provide the students with the information on books and scheduled times of book rental available. c.schedule.syllabus and payment as per required.The booking or reservation of the books is online. 3. 2.categories. To ensure validity and security in the online book bank management system. Focus is laid solely on the book display.Thus the UML diagrams for Passport Automation System was analyzed and designed using Rational Rose.The student must register themselves online. EXNO:3 DATE: 1. • This program will not be dependent on any other software and is not a component of another program. PRODUCT PERSPECTIVE: • This product requires a web browser which is capable of playing flash media.SCOPE OF THE PROJECT: The book bank system project is a software tool created to help and access the students gather required information about the various books in the institution the project is web based interactive application. b.FUNCTIONAL REQUIREMENTS: BOOK BANK . • This program does not require any new hardware.PROJECT DESCRIPTION: USER PERSONAL AND CHARACTERISTICS: The target client for our software are students who lively are interested in rental of books be it either from engineering or medical genre in the institution.which is free.REQUIREMENTS: (a).OBJECTIVE: a. To implement book bank system online.They can log into our website and browse the courses which they have aspiration to study.the detailed description about their book package and necessary terms and condition norms would be emailed to the students registered email address which he/she may provide during the time of registration.

Logout. i. A function is described as a set of inout. 4. reliability. security. Maintain and update book details. 6. The should prepare the requirements which are need for the software. PERFORMANCE REQUIREMENTS: Performance requirements define acceptable response times for system functionality. i. Displaying details. iv. 3. 5.NON. logical database requirements. Viewing book details. 2. The developer should prepare the requirements of the project. DESIGN: Project manager should design the layout of the project before going to implement time allocation. The system should have the requirements of the project. standard compliance.e from usecase to deployment.we have to test the particular projects. design constraints. MAINTAINENCE: The system should be easily updated.the behaviour and output. IMPLEMENTATION: After encomposing all the diagrams. REQUIREMENTS: 1. maintainability and portability.The system should utilize the interchangeable plugins software developed should maintain the cost and time schedule of the project. Login iii.we have to generate code for each and every diagrams i. (b).cost allocation and staff allocation wil coming under design process.A functional requirement defines a function of a software system on its component.FUNCTIONAL REQUIREMENTS: Nonfunctional requirements define the needs in terms if performance. TESTING: Afteer implementing the diagram with domain language. availability. . vi. ANALYSIS: Analyze the requirements whether it provides proper operations/output and performs the task. v. ii. A main menu including a brief help section.

MAINTAINABILITY:  The system shall utilize interchangeable plugins. DESIGN CONSTRAINTS: The software shall be a standard system running in a windows environment. MSAccess . i. Rational Rose Enterprise suite. AVAILABILITY: The system should have an availability of 99.  Queries shall results within five seconds.MODULE DISCRIPTION: In this project we have defined different modules to enable the Book Bank system in successful manner. (c).  The system shall be easily updateable for fixes and patches.99%. 40 GB. Processor 2 . Front end Tool 3. RAM 4 . Back end Tool 5. iii. vi.  The system shall be easy to migrate or backed up via another use drive.HARDWERE REQUIREMENTS: 1 . RELIABILITY: Specify the factors required to establish the required reliability of the software system at time of delivery.  The login information shall be verified within the seconds. OS 2.0 GHZ. The total time for user interface screens will take no longer than two seconds. iv. 512mb 1 nos.SOFTWARE REQUIREMENTS: 1. REGISTER: Windows XP/vista. Hardware 3 . PORTABILITY:  The system should be extremely via the usb drive. v. (d). DVD RAM Intel Pentium IV-2. iii. The system shall be developed using rational enterprise suite and oracle 10i database.

vi. Password etc. This Partial layer architecture shows the interface of the sequence diagram. iii. It includes Username and Password. the payments. Address. iii.  In object oriented analysis.  It illustrates the concept in the domain. DISPLAY DETAILS: Display the details about the students particulars. LOGOUT: To sign off from the webpage or your account log off. It provides a big picture overview of how a set of interaction are related in terms of logic and process flow. This also contains another field called as categories where can select the category of the book. 6. E-mail id. v. PARTIAL LAYERED ARCHITECTURE: Sequence diagram is an interaction overview diagram. .The register module contains the application form or registration form which contains following details. LOGIN: The Login module contains the form which contain membership name and member password. here the administrator shows the interface by displaying actor symbol.  Name. iv. 7. the books.  It act as a source of inspiration for designing some software objects. Contact number. the domain model is the most important. from this list we search for the book which we need. MAINTAIN BOOK DETAILS: The administrator maintains the details of books. rental and schedule times for books etc.DOMAIN MODEL: A domain model is a visual representation of conceptual classes or real situations object in a domain. SEARCH BOOK: The search book module contain list of books.

9.FUNCTION AND PRE-FUNCTION: MODULE: Registering PRE-FUNCTION:  Login to the website. Continuing stream of requirements changes.  Making a list of all of the potential dangers that will affect the project.8. 11. RISK CONTROL:  Monitoring the effectiveness of the strategies and the changing levels of risk throughout the project. 10.  Assessing the probability of occurrence and potential ross of each item listed. POST. RISK ACTIVITY:         Personal short falls. Real time performance short falls. Developing the wrong functions and programs. Developing the wrong user interface.  Techniques and strategies to migrate the highest ordered risks. Unrealistic schedules and budgets. what the time is taken for the project action of core product. sub system layer. LOGICAL ARCHITECTURE: The Logical architecture is large scale organization of software class into packages. Straining computer science capabilities. . RISK ASSESSMENT:  Figure out what the risks are and what to focus on. Short falls in externally furnished component. It is called logical architecture because there is no direction about how these elements are display on different operating system.GANTT CHART: It describes the time schedule for the planning to complete the corresponding and after completion of core product.

POST-FUNCTION:  Verification of documents submitted. MODULE: Display book details PRE-FUNCTION: Analyze the course of semester of logger. Here we have grouped the 6 main elements of software project grouped the in order register. 12. A package name may be based on tab if the package shows the member of main package. Collection the required documents submitted for registration. search book. It goes to update and sales record. to be  Conformation email sent accessing that authentication can be prevailed for the individual. . POST-FUNCTION: Display the required book details. login. UML PACKAGE DIAGRAM: A package diagram provides a way to group element.

components of the software process for any admin seek the registration for new visitor. ii. REGISTERED USER: Registered user can search the book whatever needs and can read the book in online. Admin keep sales record i. The visitor can search books and read the boook but he must register to buy or download the book. Admin can keep those records update. VISITOR: The visitor can register the application form and become a member of the website. we are going to generate the coding in java or VB the project domain is now finalized in JAVA/VB. iii. can download the book but after payment.TECHNICAL SERVICES LAYER: Technical service layer describes the relationship between different actors. ADMIN: The administrator is used to register a new visitor for the website. So that the new visitor can login the website and search for book and if need can buy it.e. USER INTERFACE LAYER: i. 14. DOMAIN SERVICES LAYER: After technical services layer from partial layered architecture. 15. If user is satisfied with this book.. .13. now much book is downloaded and how much book is buyed newly with copy write etc.

. Use case diagram and case relationship are secondary in use case work use case text document.UML USECASE DIAGRAM: Uml provides use case diagram notation to iilustrate the names of use case and author relationship between them.

. we have already introduced and used their uml diagram while domain modeling. They are used for static object modeling.UML CLASS DIAGRAM: The Uml class diagram is to illustrate class interfaces as their actions.

It is generalize between two or more specialized diagram.UML SEQUENCE DIAGRAM: A sequence diagram illustrate a kind of format in which each object interact via message. .

PARTIAL LAYER ARCHITECTURE DIAGRAM: Sequence diagram is an interaction overview diagram. here the administrator shows the interface by displaying actor symbol . This Partial layer architecture shows the interface of the sequence diagram. It provides a big picture overview of how a set of interaction are related in terms of logic and process flow.

. The collaboration comes from sequence diagram.UML COLLABRATION DIAGRAM: COLLABRATION diagram illustrate that object interact on a graph or network format in which object can be placed where the diagram. In collaboration diagram the object can be placed in anywhere on the diagram.

UML STATE CHART DIAGRAM: A Uml state machine represents the interaction events and states of an object and behavior of an object in reaction to an event.. It is included with initial pseudo state and fins end state . Transaction shown as allows labeled with their event.

UML ACTIVITY DIAGRAM: A Uml activity diagram shows sequential and parallel activates in a process. work flows. . data flows and compiler algorithm.

UML COMPONENT DIAGRAM: Components are slightly fuzzy concept in this Uml, because both class and components can be used to model the something.

UML DEPLOYEMENT DIAGRAM: Deployment diagram shows the assignment of concrete software artifact to computational nodes. It shows the deployment of software elements to the physical elements. Deployment diagram are useful to communicate or deployment architecture.

IMPLEMENTATION: After the completion of UML diagrams for BOOK BANK SYSTEM we should generate the code. Select the tools option from main menu then select the sub option program module in which we are going to generate the code in JAVA/VB/J2EE. Then go ahead and select the generate code option as a result of code generation.

TESTING: To perform the testing for the generated code again select the tools option from menu bar and choose quality architecture option a sub window gets opened. We are going to perform Unit Test and Scenario testing for our project. So, select these testing option one by one and testing activity is carried out for all the coding and testing is carried out.

This is a database to store the transaction that takes places between the Manufacturer. The Stock is the database used in our System which records all transactions that takes place between the Manufacturer and the Dealer and the Dealer and the Retailer. Date of manufacture. The customers get Item from the Shop Keeper and not directly from the Manufacturer or the Dealer. Number of Item available and their Company Address. STOCK MAINTENANCE SYSTEM Ex.CONCLUSION: Thus the project for BOOK BANK SYSTEM has been successfully executed and codes are generated. USE CASE DIAGRAM : . The Shop Keeper or Retailer is the one who is prime source for selling items in the market. best before use. Dealer and the Shop Keeper that includes stock inward and stock outward with reference to the dealer. No: 4 Date: AIM: To analyze and design a system for Stock Maintenance System using Rational Rose tool. Problem Statement: INVENTORY SYSTEM is a real time application used in the merchant’s day to day system. The Dealer is only responsible for distribution of the Item to the Retailers in the Town or City. Here we assume our self as the Dealer and proceed with the transaction as follows: The Manufacturer is the producer of the items and it contains the necessary information of the item such as price per item. The Dealer is the secondary source of an Item and he purchases Item from the manufacturer by requesting the required Item with its corresponding Company Name and the Number of Items required.

Purchase Sales C pany name om C pany name om PR U ER OD C Price/item D EALER Price/Item SH OP KEEPER Item ordered s Item ordered s T otal price T otal price ACTIVITY DIAGRAM : I vnoy ne t r Ss m y te Sl c f o e t rm e th Mn e eu Pr hs uc ae Sle as Sc to k Ei xt D p yth is la e T na t n e i r s cio Dta a ls Cma y o pn Nm ae P eI e r /t m ic N oI e s o ft m o ee r rd d Tt l Pc oa r e i I Aa bity>N o f vila il of I m O ee te s r r d d D p y I s fic n is la s n u ie t f n o it m of es D p y pic is la s r e oI m f te s SEQUENCE DIAGRAM : .

O I E S RE E N 4 O FTM ODRD .P R H S 32 O P N NM : . MA Y A E C 2 OP N NM .S L S 63 R E E : .P IC /IT M 1 : 6 EM IN U F IEN /T T L P IC 1 .IT S S F IC T O A R E DAE E L R S O K E H P E P R E COMPONENT DIAGRAM : . O I E S RE E N 5 O L RE . LS S 2 OP N NM .P IC /IT M 9 5 O A P IC : .C M A Y A E 8 4 OO IT M O D R D : . I / E P CI 4 O FTM ODRD .C M A Y A E 7 4 OO IT M O D R : . E K W AA B T C N T L L 6TM I S FI I N T TL R E .POUE RDCR 1 UCA E .T T L R E P O U R DC E R 11 U CA E : . MA Y A E C 3 R ETM .C E K G IT V IL B IT 2 1 AE : . E SNUF E T O P I I C / A C COLLABORATION DIAGRAM : 53 R E E : .N F E S RE E 1 : 5 H C IN W HA A A IL Y 0 . RHS P DAE EL R S OKE E HP E P R 1 AE . I / E PCI 3 R ETM . T PI T A C 5 HCI G I H V I A I I Y .N F E S R E ED 42 O P N N M : .

MNF A UA CU E TRR D AE EL R SOK HPE EE PR DTB S AA A E CLASS DIAGRAM : M N F CU E A UA T R R M n fa tu r N m a u c re a e C ma yN m o pn a e D teo M n f c re a f a ua tu d Ad s d re s Cn c Nme o ta t u b r P e ric P rc a e u h s () S le () a s DEE ELR Da rN m e le a e D teo Ite s R c iv d a f m ee e Ad s d re s Cn c Nme o ta t u b r P e ric N o Ite s O e d o f m rd re N o Ite s S ld o f m o P rc a e u h s () S le () a s S o s c D ta () h w to k e ils SOKEE HPEPR S o K e e Nm hp epr a e Ad s d re s Cn c Nme o ta t u b r P e ric N o Ite s O e d o f m rd re P rc a e u h s () S le () a s DEPLOYMENT DIAGRAM : Process or Printer Mouse Keyboar d .

private int noofitemsordered. public dealer theDealer. public manufacturer theManufacturer. private int dateofitemsreceived.java public class manufacturer { private int manufacturername. private int address. private int dateofmanufactured. private int price. private int contactnumber. private int contactno. public manufacturer() { } public void purchase() { } public void sales() { } } Dealer. private int companyname. private int name. private int noofitemssold. public shopkeeper theShopkeeper. public dealer() { } public void purchase() { } .java public class dealer { private int dealername. private int addres.Javacoding: Manufacturer.

 The student can see the courses available to him and register to the course he wants.{ public void sales() } public void showstockdetails() { }} Shopkeeper.java public class shopkeeper { private int shopkeepername. Problem statement  The system is built to be used by students and managed by an administrator. private int contactnumber. public shopkeeper() { } public void purchase() { } public void sales() { }} RESULT: Thus the UML diagrams for Stock Maintenance was analyzed and designed using Rational Rose. using Rational Rose tool. private int address. public dealer theDealer. private int price. Ex No: 5 Date: ONLINE COURSE REGISTRATION SYSTEM AIM: To create a system through which students can register to the courses desired by them.  The student and employee have to login to the system before any processing can be done. private int numberofitemsordered.  The administrator can maintain the course details and view all the students .

If it is invalid. a student can search all the courses available to him and choose the best course he wants. Use-case name: Display details After registration to any course. the user’s account becomes available. an appropriate message is displayed to the user. faculty and department of the courses he may choose. The student can view the course duration. the student may see the details of his current course. Student 2. System requirements Rational Rose Software Use-case diagram The course registration system has the following use-cases Login View course details Registration Display details Maintain course details Logout The actors involved in the system are 1. The administrator also has the privilege to display details of the the students and the corresponding course for which they have registered. he can register to that course. He may wish to know details about fees and other information. Upon registration.who have registered to any course. the student’s details are stored in the database. If entered details are valid. Use-case name: Maintain course details The administrator has to perform the duties of maintaining the course details. Any change to the course structure is maintained by the administrator. . Use-case name: View course details In this use case. Administrator Use-case name: Login The user enters the username and password and chooses if the user is student or administrator. Use-case name: Registration When a student has successfully chosen a course.

the user may choose to logout from the system to save all he changes they have made. register (). The course registration system makes use of the following classes: 1. 2) Administrator . Administrator 1) Stud It consists of the details of all the students present in the database. logout (). The operations available to this class are login (). attributes and relationships.Use-case name: Logout After all the desired transactions are made. Stud(student details) 2. course and attendance. The attributes present in this class are student id. sex. password. The object of this class is created as soon as the student registers to a course. Use-case diagram for course registration system Class diagram The class diagram is a graphical representation of all the classes used in the system and their operations. confirmation (). age. name. and view course details ().

Class diagram for course registration system Sequence diagram Sequence and collaboration diagram for login to the system . display course (). ma course details (). marks. The attributes present in this class are username. and attendance. fees due. The operations available to this class are login (). logout (). and confirmation (). password.It consists of details of all the courses available to the student. course fees.

Sequence and collabaration diagram for logout .

Sequence and collabaration diagram for registration to a course .

Private string passwd. Public stud() { } Public void logout() { } Public void confirm() { } RESULT: Thus the Online course registration system was designed and analyzed using Rational Rose. Private int age. Public admin. Private int sex. .ACTIVITY DIAGRAM : lo in g v wh ie t e cu e or s rg t r eise dpy is la lo o t gu JAVA CODE: Public class stud { Private int sid.

PROBLEM STATEMENT To book a ticket for a user online ticket reservation system software and to confirm the ticket booking.Ex No: 6 Date: ONLINE TICKET RESERVATION SYSTEM (E – Ticket) AIM: To analyze and design a system for Online Ticket Reservation System (E – Ticket) using Rational Rose tool. Provide a dropdown box for the date. . get the number of passengers. reschedule. users have to login Get the username and password from existing users. LOGIN • • • Before entering the system. 2. making the payment. printing the tickets has to designed using Rational Rose tool. AVAILABILITY • • • Get the source and destination. Check availability of tickets. 2. OVERALL DESCRIPTION 1. 3. RESCHEDULE • • • If tickets are available. Give new users the option to sign up. Get the name and age of all passengers. If tickets are not available. 1.

Get the payment details from the user.4. Display confirmed ticket to the user. Confirm the details and the ticket. PAYMENT DETAILS • • • • Print the cost of the tickets. destination Check availability Booking Server Customer Enter details Request booking Make payment Bank System Confirm booking . USECASE DIAGRAM Choose source.

ACTIVITY DIAGRAM Display availability Get booking request Display payment details Get user's payment details No If complete Print ticket CLASS DIAGRAM CustomerDetails Name Address Email Age book() Booking Booking_no Date Total Status name Pay() Payment Date Amount .

reschedule Enter information Reconfirm booking Payment Confirm payment Get ticket COLLABORATION DIAGRAM .SEQUENCE DIAGRAM Customer Server Bank Check availability Yes If no.

2: Yes 1: C heck av ailability 4: Enter information C ustomer 3: If no. reschedule 5: R econfirm bookin g 8: G ticket et Serv er 7: C onfirm paym ent 6: Paym ent Bank STATE CHART DIAGRAM Displaying availability Request booking Check availability Displaying payment details User's payment details Print Ticket COMPONENT DIAGRAM .

private int age. private int email. private int address.Bank Online Booking Server Customer DEPLOYMENT DIAGRAM Server Update Railway Database User PC Javacoding: Customerdetails. .java public class customerdetails { private int name.

private int name. . private int amount. public booking() { } public void pay() { } } Payment. private int date. public payment thePayment. public customerdetails() { } public void book() { } } Booking. private int total.public booking theBooking.java public class payment { private int date. private int status.java public class booking { private int booking_no.

Login The employee details has to be entered and if needed the details can be edited. employee name. Pay slip It contains details such as employee id. Ex No:7 Date: SOFTWARE PERSONNEL MANAGEMENT SYSTEM AIM: To analyze and design a system for Software Personnel Management System using Rational Rose tool. . 2. using Rational Rose tool.public payment() { } } RESULT: Thus the Online Ticket Reservation System have been designed and verified using Rational Rose Tool. OVERALL DESCRIPTION The three modules are 1. 2. PROBLEM STATEMENT To compute the gross pay of a person using the software personnel management system software and to add new details to the existing database and update it. 2.

Rational Rose 2.1 SOFTWARE REQURIEMENTS: 1. and basic pay. Pentium III Processor 3.View Updated database would be present. The details of the employee can be used for further reference. experience. DESIGN USECASE DIAGRAM . 3.2 HARDWARE REQURIMENTS: 4. 128MB RAM 5. 2.department.

CLASS DIAGRAM .

SEQUENCE DIAGRAM COLLABORATION DIAGRAM .

SEQUENCE DIAGRAM COLLABORATION DIAGRAM .

ACTIVITY DIAGRAM JAVA CODING: .

private int ename. public viewdetails theViewdetails.PAYROLLLOGIN.JAVA . public payrolllogin() { } public void exit() { } } VIEWDETAILS. public viewdetails() { } public void view() { } public void exit() { } } PAYSLIP. private int dept. private int exp.JAVA public class viewdetails { private int eid. private int bpf. private int gpay. public payslip thePayslip. private int hra. private int da. private int editdetails. private int basicpay.JAVA public class payrolllogin { private int enterdetails.

private int da. public payslip() { } public void delete() { } public void new1() { } public void save() { } public void calculate() { } public void exit() { } } RESULT: Thus the Software personnel management system was designed and analyzed using Rational Rose. Ex. private int experience.public class payslip { private int name. private int department. private int gpay. private int basicPay. private int eid. private int bpf. NO. private int har.:8 .

When it is used for processing money for institutions transactions and retransactions takes place between the customer and the agent for sponsoring finance and manage customer account. If all the details given by the customer is valid then the transaction of money takes place. When the customer uses credit card.Date: CREDIT CARD PROCESSING Aim: To analyze and design the credit card processing system on rational rose software tool. Data modeling:  Use case diagram  Class diagram  Sequence diagram  Collaboration diagram  Package diagram  Interaction diagram  State chart diagram PROBLEM STATEMENT: Credit card is used by customers for the transactions and processing money between customers. USECASE DIAGRAM Perform Card Transaction Customer Retail Institution Process Customer Bill Reconcile Transaction Individual Customer Corporate Customer Manage Customer Account Sponsoring financial Institution SEQUENCE DIAGRAM .the administrator enquires about the pin number and the authentication details.

ACTIVITY DIAGRAM .

CLASS DIAGRAM: .

java public class bank { private int balance. JAVA CODE : Bank.bank balance accountNo getBalance() buyersAccount() bank() FinancialAccount report +theFinancialAccount getavaliableReport() FinancialAccount() systemSecurity key +theSystemSecurity getsystemClerance() systemSecurity() +theReportingSystem ReportingSystem report key avaliableReport() ReportingSystem() COMPONENT DIAGRAM: Component diagrams describe software components and their relationships within the implementation environment. they indicate the choices made at implementation time. private int accountNo. They may be simple files. public FinancialAccount theFinancialAccount. public bank() { } public void getBalance() { } . or libraries loaded dynamically.

public systemSecurity() { } public void getsystemClerance() { } } RESULT: Thus the credit card system was designed and analyzed using Rational Rose. public systemSecurity theSystemSecurity.java public class ReportingSystem { private int report.public void buyersAccount() { } } ReportingSystem.no: 9 . public ReportingSystem() { } public void avaliableReport() { } } SystemSecurity.java public class systemSecurity { private int key. private int key. Ex.

book It contains the list of e-book(s) available along with the search option.Book Management System using Rational Rose tool. Login The user has to be enter his/her login details and if needed the details can be edited.book in the future. OVERALL DESCRIPTION The four modules are 1. The e-book should contain index of the topics. 3. Search Topic: Choose the required topic and double click on it.Date: E-BOOK MANAGEMENT SYSTEM AIM: To analyze and design a system for E . PROBLEM STATEMENT To maintain and find the required e – book(s). When the main page is visited index of the topics is displayed. Select the required topic and double click on it. Update The database can be updated with new arrived e . Then the page with the contents of the selected topic will be displayed. Then the page with the contents of the selected topic will be displayed 4. 1. A certain option is also present in that page to go back to main page and search for other topics. 2. Select E . 2. USE-CASE DIAGRAM: .

SELECT TOPIC DISPLAY TAB LE CONTENTS USER SEARCH FOR TOPIC SYSTEM DISPLAY THE INFORMATION EXIT ACTIVITY DIAGRAM: START SELCET E-BOOK CHOOSE MAIN TOPIC SELECT SUB-TOPIC (1 TO n) STOP SEQUENCE DIAGRAM: .

USER SYSTEM SELECT TOPIC DISPLAY TABLE CONTENTS SEARCH FOR TOPIC DISPLAY INFORMATION EXIT COLLABORATION DIAGRAM: 1: S E LE CT TOP IC 3: S E A RCH FO R TOP IC 5: E XIT US E R S Y S TE M 2: DIS P LA Y TA B LE CO NTE NTS 4: DIS P LA Y INFORM A TION DEPLOYMENT DIAGRAM: .

java .CPU KEY BOARD PRINTER MOUSE Javacoding: System. public system() { } public void display() { } } User.java public class system { private int info.

public system theSystem. public user() { } public void search() { } public void exit() { } } RESULT: Thus the E – Book management system was designed and analyzed using Rational Rose.NO:10 . EX. private int topic.public class user { private int name.

OVERALL DESCRIPTION The three modules are 2. DESIGN . Pentium III Processor 3.2 HARDWARE REQURIMENTS 1. 4.Date: AIM: RECRUITMENT SYSTEM To analyze and design a system for Recruitment using Rational Rose tool. 128MB RAM 2. 2. Recruitment test This system will generate random question to test the skills of the Candidate and check whether the candidate is suitable for the position offered by the company. Result This will show whether the candidate is selected or not selected for the position by displaying the message. 2. PROBLEM STATEMENT To create a software system this can test the skills of the candidate by generating random question and answer. Login User can login using the username and password and they can start attend the test for the specified vacancy 3. Rational Rose 2.1 SOFTWARE REQURIEMENTS 1. 1.

3 CLASS DIAGRAM .3.2 ACTIVITY DIAGRAM lo gin in a use v lid r a nsw r the e q estion u ge the result t 3.1 USE CASE DIAGRAM login (from usecase m odel) candidate (from usecase model) database view the questions (from usecase model) (from usecase m odel) attend the test (from usecase model) display result (from usecase model) 3.

4 SEQUENCE DIAGRAM candidate re critm ent system ente by login and passw r ord v erify lo gin D ba ata se re quest fo questio for th test r ns e send question for te st display qu estions an er a the q sw ll uestions v erify the answ er display re sult display m essag e 3.5 COLLABORATION DIAGRAM .candidate login password name2 attend() result() databse question score id display() calculate() result display() recruitment test question display question() submit the answer() display msg() 3.

7 DEPLOYMENT DIAGRAM DATAB SE RECRUI TME.6 COMPONENET DIAGRAM candidat e recruitment system database 3.. CANDID ATE JAVA CODING: .1: enter by login and password 6: answer all the questions candidat e 5: display questions 9: display message 2: v erify login 3: request for questions for the test 7: v erify the answer 4: send question8: display result for test recritment system Databas e 3..

public dataBase() { } public void display() { } public void calculate() { } public void resultDisplay() { .Candiate.java public class candiate { private int login. private int id. private int score. private int name2. private int password. public candiate() { } public void attend() { } public void result() { } } DataBase. public recruitmentTest theRecruitmentTest.java public class dataBase { private int question.

Ex. public recruitmentTest() { } public void displayQuestionj() { } public void submitTheAnswer() { } public void displayMessage() { } } RESULT: Thus the UML diagrams for Recruitment System was analyzed and designed using Rational Rose. NO: 11 DATE : EXAM REGISTRATION SYSTEM .} } RecruitmentTest.java public class recruitmentTest { private int question. public dataBase theDataBase.

128MB RAM . 1. the user can select the subject to register for the exam. Registration for the exam In this module. Rational Rose HARDWARE REQUIRMENTS 1. address can be done.AIM: To analyze and design a system for Exam registration using Rational Rose tool. Modification in the Database In this module the user can change the data’s like the phone number. 3. SOFTWARE REQUIRMENTS 1. Cancellation for the registered subject In this module the user can cancel their name which is registered for the exam.the four modules are 1. Modification in the student database. 4. PROBLEM STATEMENT To create an Exam registration software that will meet the needs of the applicant and help them in registering for the exam .modification in database and cancellation for the registered project. Enquiry about the registered subject.enquiry about the registered subject . OVERALL DESCRIPTION The Exam Registration System is an integrated system that has four modules as part of it. canceling the registered subject 2. 2. Form for Registration In this module the user can apply for the exam by giving the details about the candidate and selecting the subject for the registration.

2. Pentium III Processor USE CASE DIAGRAM: student (from actor) register for exam (from use case) databse (from actor) select the exam (from use case) cancel the exam registration enter datas (from use case) (from use case) maintain student info modify databse (from use case) (from use case) ACTIVITY DIAGRAM: enter into system cancel regisrtation select the subject apply the exam modify databse DEPLOYMENT DIAGRAM .

student exam registration Databse CLASS DIAGRAM: student name id address phone number subject name select the subject() apply() cancel() modify() exam database id name address phone number subject update() modify() select() display id() database if name phone no subject display registartion() display subject() update() SEQUENCE DIAGRAM: .

student 1: enter the data 2: select the subject examregistratio n database 3: apply for the exam 4: apply for the exam 5: generation fo registration id 6: note id 7: modify databse 8: cancel the subject registration COLLABRATION DIAGRAM: 1: enter the data 2: select the subject 3: apply for the exam examregist ration student 6: note id 7: modify databse 8: cancel the subject registration 5: generation fo registration id 4: apply for the exam databas e .

private int phoneNumber. private int subjectName. private int id. public examdatabase theExamdatabase. public student() { { { { { } public void selectthesubject() } } } } public void apply() public void cancel() public void modify() .COMPONENT DIAGRAM student exam registration Databse JAVA CODING: Student. private int address.java public class student { private int name.

private int phhonenumber. public studentex theStudent. public database2 theDatabase. private int name.java public class examdatabase { private int id.java: public class database { private int id. private int subject. public examdatabase() { { { { { } Database. private int phoneno. private int subject. public database() { } } public void update() } } } } public void modify() public void select() public void display() . private int address.} Examdatabase. private int name.

resultdisplay(){ } RESULT: Thus the UML diagrams for Exam Registration was analyzed and designed using Rational Rose.calculate(){ } void database.public void displayregistration() { } public void displaysubject() { } public void update() { } } void database. Ex No: 12 Date: .

Rational Rose . 2. OVERALL DESCRIPTION: 1. Login: Authenticate the user and administrator. Database: The details about the conferences going to conduct by various institutions. 3.1 SOFTWARE REQURIEMENTS: 2. PROBLEM STATEMENT: This project deals with the conference management system.Conference view: This form contains the details about the conferences is conducting by various institutions and we can see the date and time for the conference. 2. 4. 2. 1. Administrator will add the details about the various conferences available to attend for various department students and staff members. As a students or staff members are required to view the details of conference is going to conduct in various colleges or institutions and to attend the conference to gain knowledge from the conferences. Administrator can add the details about the conference for the students and also for the staff members.CONFERENCE MANAGEMENT SYSTEM AIM: To analyze and design a system for Conference Management System using Rational Rose tool. Department Selection: This form will give the options for selecting the department to get knowledge about the conference.

Pentium III Processor 3. ACTIVITY DIAGRAM: . USE CASE DIAGRAM: login (fro m u se ca se ) user (fro m a cto r) admin (fro m a cto r) enquriy (fro m u se ca se ) view details (fro m u se ca se ) add details (fro m u se ca se ) 4.2. 128MB RAM 7.2 HARDWARE REQURIMENTS: 6.

enter the id

select department

exit

view the details

5. CLASS DIAGRAM:

administrator admin_pass : variant validate_pass() add details() view detals()

user pass : variant depat : variant view the details()

6. SEQUENCE DIAGRAM:

USER

DEPARTMENT

ADMINISTRAT OR

DATABASE

Enter the username and password Verify password Ok display the selection of department

select the department

verify the department

verify

ok

ok

view the details

7. COLLABORATION DIAGRAM:
5: select the department USER DEPART MENT

1: Enter the username and password 10: v iew the details 4: display the selection of department 9: ok 6: verify the department

3: Ok 8: ok DATABA SE 2: Verify password 7: verify ADMINIST RATOR

8. COMPONENT DIAGRAM:

Admin

Database

Display

Student

9. DEPLOYMENT DIAGRAM:

databas e

admin

user

display

Javacodings:
Administrator.java public class administrator { private variant admin_pass; public administrator() {

public Administrator.java public class user { private variant pass. private variant depat. .} public void validate_pass() { } public void adddetails() { } public void viewdetails() { } } User. public user() { } public void viewthedetails() { } } Result: Thus the Conference management system was designed and analyzed using Rational Rose.