15-10-2016, 11:30 AM
1459170378-ChethanaEMI.doc (Size: 207 KB / Downloads: 8)
Abstract
This Project Explains about a software application which is useful for automobiles dealers for maintaining purchased vehicles EMI installments information and other information related to purchased vehicle. This software consists of messaging option through which EMI information is updated to customer’s mobile number.
Automobile EMI Management System Project explains about a software application which is useful for automobile dealers for maintaining purchased vehicles EMI installments information and other information related to purchased vehicle. This project report covers functionality of different modules in the application, problems of existing system, system analysis and hardware and software requirements.
In this online vehicle registration application automobile dealers will provide registration application to users while purchasing new vehicle. This registration form consist of automobile number, vehicle number, user mobile number and loan amount paid, pending amount that to be paid in the form of EMI.
This software consists of messaging option through which EMI information is updated to customer’s mobile number. Users can pay online payments through this online web application. This application is developed in ASP.NET platform.
Automobile registration application is implemented in five modules. Customer will request information to administrator admin will update details as a project and submit to business development officer he will check the details and update information to database. Human resource management department will look after dealings with customer and them project manager will approve the process.
1. INTRODUCTION
1.1 DEFINITION:
The vehicle registration is an application which specifies about the EMI (Every Month Installment) of a vehicle purchased on loan basis. This application states about the customer details and remaining installments and etc….
1.2 DESCRIPTION:
The vehicle registration is a online application which specifies about the individual vehicle registered in the application and the major methods like applying the vehicle in details like vehicle number, engine number, customer mobile num, amount of loan amount which is to be paid monthly, customer, monthly payment of the customer and the mobile num of the customer.
In the application the main advantage is that the date of the installment and the payment of the installment will be sent to the costumer’s mobile number vehicle through SMS
The application contain the payment option which is applicable and logged in by the admin who uses the application and logged with the admin
Vehicle Registration Tool gives the individual reports of the project, which contains time used for various tasks. In this tool costumer gives requirements to the ADMIN and makes an agreement with him. The new project information is entered by the ADMIN, based on the project information the manager will take resources from the VEHICLE and assign activities to developers who are working under him. Employees fill the time sheet and submitted to the costumer.
This project deals with five modules – Costumer, Business development officer (ADMIN), Developer, Human Resource Manager (VEHICLE), and Project Manager (PM).
Costumer deals with checking the status of the project by the costumer. Only the authenticated costumer login to the web page and checks in which phase the project is.
ADMIN deals with collecting the requirements from the costumer and add the costumer details and project details into the database and also views and updates the respective details
Costumer deals with filling the timesheets. Updating and viewing the timesheets and also checking the project status.
FINANCE deals with providing resources to the project manager by checking the employee details like skill and designation. VEHICLE can also view the status of the project.
EMI deals with planning the project i.e. dividing the project into different tasks and assigning those tasks to the developers. PM also checks the timesheets of developers. Fills hisown timesheet, updates and views the timesheet. PM can also check the status of the project.
Vehicle Project Management Tool (SPMT) will do the following tasks:
• Record monthly income of the costumer.
• Define the monthly installment of the vehicle.
• Keep a track of EMI schedules.
• Record payment definition.
• Phase wise project closures.
• Assign resources to a project.
• Access control for resources.
• Take daily efforts from each resource.
1.3 OBJECTIVES
The objectives of this application are functionality and architecture of the ‘Vehicle Registration ’, and to estimate the effort of the project.
The general objectives are:
• Maintain project details.
• Maintain costumer details.
• Maintain employee details.
• Maintain timesheet for various levels project.
1.4 OVERVIEW
Vehicle finance has inherited problem with determining the time it takes to complete it. Vehicle programming is quite different than say, nail production. When one produces nails it is known how many nails machine produces per hour. If you need to produce x number of nails figuring the time it takes is easy. If you need 12h of time, you know that one of your workers can handle the overtime and omitting for the sake of argument certain safety concerns, your worker will be as productive at hour 1 as hour 12. Unfortunately, vehicle development is much harder than nail manufacturing. There are many more unknowns - risks that have to be accounted for. In order to attain rapid vehicle development, four different aspects have to be considered. These are:
• Risk management
• Avoiding common mistakes
• Practicing development fundamentals
• Following practices leading to best possible schedule
The rest of this guide will discuss each of above four elements of project management. All of above are equally important, if any of above four is omitted then the whole structure might fail. The reason for "might" is the risk based aspect - as mentioned before things may go right or wrong. It's all about leaning in favor of successful resolution instead of using methods that increase the chance of failure. One of the methods that increase risk, but are widely used due to their simplicity, is programmer total commitment. This disorganized way of project management has its successes; however these successes are a result of inefficient, hard work - not of smart work that can be achieved by following above four principles.
1.5 PROBLEMS IN EXISTING SYSTEM
People
• Admin cannot maintain day to day schedule.
• Under-trained employees with low qualifications.
• As the receipts of the payment are not online any one can steal the receipts.
• Company encouraged vehicles "heroics", emphasis on "can-do" attitudes.
• Adding people to projects that are over-running their schedule.
• Working environment that prevents employees from focusing on their work. Customer interactions that are too frequent or lead to open conflicts.
• Unrealistic expectations, usually in the area of project scheduling, wishful thinking.
• Absence of executive project sponsorship, absence of agreement between all parties involved in the project.
• Absence of customer involvement in the project causing delivery of vehicle that doesn't meet customer expectations which in turn cause feature creep.
• Involving developers in company politics more than is necessary.
Process
• Schedules that is too short for the project at hand - too much emphasis on optimism.
• No risk management or insufficient risk management.
• Problems with contractors (part of risk assessment)
• Luck of or insufficient project planning. vehicle out plans when placed under excessive pressure to complete project. Deliberately omitting non-code related activities, like design, due to excessive pressure.
• Spending excessive amounts of time on project approval and budgeting.
• Poor design and poor quality assurance.
• Too few controls placed on the development process causing schedule slips to go unnoticed.
• Attempting to enter project "polishing" stage to early or more than once (frequent attempts to get it shipped).
• Thinking that project which is in trouble can be saved by "catch up" later on.
Product
• Too many requirements, attempting to build systems that can do everything.
• Adding to many new features to the ongoing project - feature creep.
• Allowing developers to use new technology project for reasons other than project requirement.
• Attempting to treat vehicle research as regular vehicle development.
Technology
• Silver bullet technology syndrome, over-estimating benefits of new tools and technology.
• Changing tools or methods in the middle of the project.
• Failure to keep code backups, no source control vehicle.
1.6 Solutions of These Problems
• There is no one single best practice that leads to the best vehicle development method. For each specific project a method has to be chosen that is appropriate for it. For example, mission critical vehicle products have to be of much higher quality than a product vehicle.
• Not all projects need to optimize their development speed many upper managers ask for speed but mean other things. For example, costumer will talk about quick development when they really want to minimize project overall cost.
• Unless product has a strong schedule constraint development speed might not be of top priority. If speed is not the most important factor, concentrate on quality.
• Remember that the only desired admin can only run the application
• There is an absolute limit on the minimal time it will take to complete any given project.
• Projects cannot have 100% probability of completing on any given time because they involve risks (not everything in a project is certain) thus we are dealing with probabilities of completing on a given date.
• Projects that are rapidly developed can be seen by customers as slow because they don't provide a lot of feedback as to project progress.
• Remember that cutting time from the top most (done 1st) stages of the project will force you to pay back in time many times over in lower stages of the project. For example, design flow will cost much more to fix in the construction phase than design phase.