16-01-2013, 01:55 PM
Vehicle Investigation System
Vehicle Investigation.doc (Size: 2.91 MB / Downloads: 160)
ABSTRACT
This project is totally deals with the registration of vehicles as well as finding stolen vehicles using the registration number date. Before searching for the stolen vehicles the vehicle owner should register the stolen vehicle details. And it gives the information of the your vehicle registration if you forget the registration number. This also facilitates the buying the second hand vehicles, before buying it will check the status of the vehicle, also changes the owner of the vehicle.
Introduction
Overview:
In this application the second hand vehicle details are stored. In this system the user will search for the vehicle details which is going to be buy using Finance or through reference.
Aim:
The main aim of our application is to investigate a vehicle details for confirmation that whether the buying vehicle is stolen or not.
Scope:
The application will be use full for the persons who will search for the second hand vehicle
System Design
OBJECT ORIENTED ANALYSIS AND DESIGN (OOAD)
Object-oriented analysis and design (OAD) is often part of the development of large scale systems and programs often using the Unified Modeling Language (UML). OAD applies object-modeling techniques to analyze the requirements for a context — for example, a system, a set of system modules, an organization, or a business unit — and to design a solution. Most modern object-oriented analysis and design methodologies are use case driven across requirements, design, implementation, testing, and deployment. Use cases were invented with object oriented programming, but they're also very well suited for systems that will be implemented in the procedural paradigm. The Unified Modeling Language (UML) has become the standard modeling language used in object-oriented analysis and design to graphically illustrate system concepts. Part of the reason for OAD is its use in developing programs that will have an extended lifetime.
Object Oriented Systems
An object-oriented system is composed of objects. The behavior of the system is achieved through collaboration between these objects, and the state of the system is the combined state of all the objects in it. Collaboration between objects involves them sending messages to each other. The exact semantics of message sending between objects varies depending on what kind of system is being modeled. In some systems, "sending a message" is the same as "invoking a method". In other systems, "sending a message" might involve sending data via a socket.
Object Oriented Analysis
Object-Oriented Analysis (OOA) aims to model the problem domain, the problem we want to solve by developing an object-oriented (OO) system. The source of the analysis is a written requirement statements, and/or written use cases, UML diagrams can be used to illustrate the statements. An analysis model will not take into account implementation constraints, such as concurrency, distribution, persistence, or inheritance, nor how the system will be built. The model of a system can be divided into multiple domains each of which are separately analysed, and represent separate business, technological, or conceptual areas of interest. The result of object-oriented analysis is a description of what is to be built, using concepts and relationships between concepts, often expressed as a conceptual model. Any other documentation that is needed to describe what is to be built, is also included in the result of the analysis. That can include a detailed user interface mock-up document. The implementation constraints are decided during the object-oriented design (OOD) process.
Object Oriented Design
Object-Oriented Design (OOD) is an activity where the designers are looking for logical solutions to solve a problem, using objects. Object-oriented design takes the conceptual model that is the result of object-oriented analysis, and adds implementation constraints imposed by the environment, the programming language and the chosen tools, as well as architectural assumptions chosen as basis of design. The concepts in the conceptual model are mapped to concrete classes, to abstract interfaces in APIs and to roles that the objects take in various situations. The interfaces and their implementations for stable concepts can be made available as reusable services. Concepts identified as unstable in object-oriented analysis will form basis for policy classes that make decisions, implement environment-specific or situation specific logic or algorithms. The result of the object-oriented design is a detail description how the system can be built, using objects. Object-oriented software engineering (OOSE) is an object modeling language and methodology OOSE was developed by Ivar Jacobson in 1992 while at Objectory AB. It is the first object-oriented design methodology to employ use cases to drive software design. It also uses other design products similar to those used by OMT. The tool Objectory was created by the team at Objectory AB to implement the OOSE methodology. After success in the marketplace, other tool vendors also supported OOSE. After Rational bought Objectory AB, the OOSE notation, methodology, and tools became superseded.
Conclusion
Finally, our application is going to useful for persons who are going to purchase second hand vehicle by searching whether the vehicle is stolen or not and also search for details of vehicle in around the world