mca final year projects in php
BACK END - SQL SEVER 2007
MCA FINAL YEAR PROJECT Project SYNOPSIS OF ONLINE EXAMINATION SYSTEM
Final Report Of Online Examination System with full Documentation
SYNOPSIS of Project Sanatorium (Hospital Information System)
Click here to download Final report of project Hospital Information System
BCA Project 3# ONLINE AUCTION SYSTEM
FRONTEND
- C # AND .NET FRAMEWORK
BACKEND
- SQL
SERVER 2008
SYNOPSIS OF PROJECT ONLINE
AUCTION SYSTEM
FINAL REPORT WITH FULL DOCUMENTATION and SOURCE CODE OF
PROJECT ONLINE AUCTION SYSTEM
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 tvehicleough 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
The application mainly uses the platform DOT.NET which
is case sensitive
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 esubmitted to the costumer.
This project deals with five modules – Costumer, Business development officer (ADMIN),
Developer, Human Resource Manager (VEHICLE), 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 his own timesheet, updates and views the
timesheet. PM can also check the status of the project.
Vehicle Project Mangaement 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 is 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 inherit 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 recepts of the payment is not online any one
can steel the recepts.
·
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 are to 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. Tvehicleowing
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.
·
To 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 chose 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.
2. SYSTEM ANALYSIS
2.1 REQUIREMENT
ANALYSIS
A requirement is a
feature that must be included in the actual design and implementation, getting
to know the system to be implemented is of prime importance.
Main emphasis is on:
The inputs to the system.
The output expected from the system.
The people involved in the working of the system.
The volume of DATA (inputs)
and the amount of Information (outputs)
that will be involved.
With respect to the system itself, the following facts are taken
into consideration.
The major process involved.
The main points of application.
The processing rules for the collected data.
The exceptions that may be present.
The checks that should be placed in order to avoid wrong entries.
2.2 VEHICLE
REQUIREMENT SPECIFICATION
PURPOSE:-
The
purpose of this document is that it deals with various levels of project development
and will account for time used in analysis, design, programming, testing
and verification etc.
SCOPE:-
The tool involved
in giving the management the clear picture of the usage of time by projects by
analyzing the results provided by the vehicle.
Documentation overview:-
This document has major
sections.
§
Section1 costumer.
§
Section2 provides the product
that will be produced.
§
Section3 addresses the specific
requirements of the system.
2.3
PROPOSED SYSTEM
To
take advantage of the latest technology and to facilitate costumer to make
Online inquires about their project status a tool need to be developed. The
tool should accomplish the following functions:
§
The tool should be able to
manage all the registrations effectively and ensure that
payment cycle goes on smoothly and they are completed on time.
§
While accepting vehicle details,
all necessary validations should be performed. It should also store the
costumer’s details.
§
The system should generate the
following reports:
Ø
Costumer’s details list.
Ø
installments details list.
Ø
vehicle details list.
Ø
Allocated EMI list.
INVESTIGATION:
For the study of the project, I met the costumer and collect his
requirements and got the
information about various levels of project development and time
assigned for each phase.
The main objective of
this study is to determine whether the proposed system is feasible or not.
Solution strategies are usually generated without regard for feasibility
because one cannot be both creative and critical at the same time. Hence
feasibility analysis is a must to arrive at the most appropriate solution
strategy. This feasibility analysis is done after the thorough study of the
system.
The planning objective is achieved tough
vehicle a process of information discovery that leads to reasonable estimation.
Keeping the following aspects in mind, the system analysis for the
development of the project is done.
Identify the drawbacks of the existing system.
Identify the need for conversion.
Perform feasibility study.
Identify, vehicle and the database requirements.
Create a system definition that performs the foundation for the
subsequent work.
PROJECT SCOPE:
The first
activity in vehicle project planning is the determination of the vehicle scope.
The functions and performance allocated to vehicle should be assesses to
establish a project scope. Vehicle scope describes function, performance,
reliability and constraints.
ESTIMATION:
Vehicle
project planning estimate can be done in many ways such as Lines Of Code (LOC)
based estimation, Functional Point Estimation (FP), Process Based Estimation.
We should select best of them depending on the requirement.
RESOURCE AVAILABILITY:
The
resources which are common to any system, consist of human effort, information and development resource.
Developing any system with out satisfactory resources is inappropriate and
impossible. The design development team for this project consists of five
members or roles that are responsible for vehicle development and internal
testing and its usage. Information assembly is vital to this project. Various
sources of information are available.
2.4 ROLES
Business Development Officer:
He is
a person who actually, interacts with the people who are demanding
the project. He collects all the requirements of their essentials.
Manager[ADMIN]:
The
manger from the name itself indicates that to manage the projects. He plans the
project and takes requirements from the VEHICLE. he then divides the project
into tasks and assigns those tasks to the developers. He fills his own
timesheet and also checks the developer’s timesheets.
CLIENT:
He
deals with the actual coding part i.e. filling the time sheets and perform
coding according to the time allotted to him. He then submits the filled
timesheets and completed task to the system.
FINANCE Resource Manager:
His
main activity is to provide resources to the vehicle. he also checks the time
sheets and decides the remuneration for the work done according to the time, in
that timesheet.
Costumer:
He is the
person who demands the project and specifies the time, for which he needs the
project back done. If the time is large slot then he has to accept the
problems, and partial results. So that, he could place the new requirements for
his project along with the advancement in the technology used.
2.5 OPERATIONAL
FEASIBILITY:
The
system is operationally feasible, it is made so easy that operator will not
encounter any problem during working, as it is very user-friendly. Operational
feasibility checks the scope of the system. The system under consideration
should have enough operational research.
It is observed
that the proposed system would provide a very interactive means to share
information and have a far and wide range. The proposed system would make information
more interactive. Thus operational feasibility of the proposed system id found
to be high.
3. HARDWARE AND VEHICLE SPECIFICATION
Hardware Specification
Processor : PIII 500MHZ or above
Processor Speed : 250 MHz to
833MHz
RAM : 512MB
Hard Disk : Minimum 1GB Hard disk space
Vehicle Specification
Language : ASP.NET
Technologies : ASP.NET
Database : SQL SERVER
2000
Web/Application server : Internet
Information services (IIS)
Operating
System : Windows
NT/2000/XP
No comments:
Post a Comment