31-01-2013, 12:37 PM
RTO OFFICE ADMINISTRATION USING UNIFIED MODELING LANGUAGE
1RTO OFFICE.doc (Size: 290.5 KB / Downloads: 24)
Introduction
This office is a Regional Transport Office a government organization. The main activity of the RTO office is issuing the LL, DL, Vehicle registration, Vehicle ownership transfer etc.., We proposed the computerized method managing all the data. Because it brings efficiency in the organization.
Purpose
The purpose of this document is to specify requirements and to give guidelines for the development of above said project. In particular it gives guidelines on how to prepare the above said project.
This document is intended to be a practical guide for people who developing this software.
Scope
This is of pilot project prepared RTO office to maintain all the records like issuing the LL, DL, Vehicle registration, Vehicle ownership transfer etc. Once all these get computerized to work efficiency of the employee will get increases.
Goal
The main goal of the project is to maintain the records of issuing the LL, DL, Vehicle registration, Vehicle ownership transfer etc.
Existing System
At present all records are maintained manually.
Proposed System
In the proposed system will help them to manage day to day operation very smoothly
It is having different modules to pul fill the requirement of the organization.
Software Requirement Specification
The software requirement specification is produced at the culmination of the analysis task. The function and performance allocated to software as part of system engineering are refined by establishing a complete information description, a detailed functional description, a representation of system behavior, an indication of performance requirement and design constraints appropriate validation criteria, and other information pertinent to requirement.
The introduction to software requirements specification states the goals and objectives of the software, describing it in the context of the computer based system.
The Information Description provides a detailed description of the problem that the software must solve. Information content, flow and structure are documented.
A description of each function required to solve the problem is presented in the Functional Description.
OBJECT ORIENTED SYSTEM DEVELOPMENT
Object-oriented analysis and design (OOAD) is a software engineering approach that models a system as a group of interacting objects. Each object represents some entity of interest in the system being modeled, and is characterized by its class, its state (data elements), and its behavior. Various models can be created to show the static structure, dynamic behavior, and run-time deployment of these collaborating objects. There are a number of different notations for representing these models, such as the Unified Modeling Language (UML).
Object-oriented analysis (OOA) applies object-modeling techniques to analyze the functional requirements for a system. Object-oriented design (OOD) elaborates the analysis models to produce implementation specifications. OOA focuses on what the system does, OOD on how the system does it.
Object-oriented systems
An object-oriented system is composed of objects. The behavior of the system results from the collaboration of those objects. Collaboration between objects involves them sending messages to each other. Sending a message differs from calling a function in that when a target object receives a message, it itself decides what function to carry out to service that message. The same message may be implemented by many different functions, the one selected depending on the state of the target object.
The implementation of "message sending" varies depending on the architecture of the system being modeled, and the location of the objects being communicated with.