Equipment Leasing

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 35

CHAPTER 1

INTRODUCTION

1.1 PROBLEM DESCRIPTION

Equipment Leasing Management is a highly complicated issue due the high volatile
of container demand and supply. Shipping Container is not a direct demand at all, but a
derived demand of the international trade in industry. Therefore containers are faced
with a demand to strike a balance between the demands and supply. The Present
Equipment Leasing Management solutions are reactive rather than proactive. The need
for an effective Equipment Leasing Management comes in to play under such market
conditions. ‘Container’ means, an article of transport equipment of a permanent
character and accordingly strong enough to be suitable for repeated use or any
type of container, transportable tank or flat, swap body, open top , dry wan , or any
similar unit load used to consolidate goods, and any equipment ancillary to such unit
load. Container ships and containers are supplementary to each other thus Container
Shipping Lines cannot transport cargo if containers are not available. In order to
fulfill the demand and satisfy the lessee to lease the container in the efficient way this
application is developed. Generally, container shipping companies reposition empty
containers from surplus ports to deficit ports. As a result, obviously, there is a cost
involved in balancing the container fleet by respective shipping lines. The available
containers are uploaded to this application by the lessor (owner), and he specifies all the
details like container history, container type, and container id and container rate per year.
A truck trailer body that can be detached from the chassis for loading into a vessel, a rail
car or stacked in a container depot. Containers may be ventilated, insulated, refrigerated,
flat rack, vehicle rack, open top, bulk liquid or equipped with interior devices

ABOUT THE ORGANIZATION


We as a team with zeal and vivid values, create a bonding relationship among
customers in order to nurture various organizations with our services. We don’t just
deliver results; we deliver it with values and resolute solutions to each of our clients. Our
leaders are accountable to institutional performances and to the community as a whole.
As Peter Ducker says we embody "The Sprit of Performance" by exhibiting high levels
of integrity in our moral code of conduct; focusing on results; building on strengths; and
leading beyond borders to meet the requirements of stake holders; ultimately serving the
common good. We continue to inspire by not how to do, but how to be?

Our Vision
To lead, to serve, to innovate and inspire in contributing to our society.

OUR Mission
 Continuously improve and innovate to strengthen our clients.
 Delivering outstanding solutions with high quality.
 Create not just success solution, but solutions with values.

OUR PROCESS

We are bold enough to acknowledge that it is in our process that we adhere


reaps us the success and reputation in the market. It’s not just our hard and smart
works, neither talent nor experiences. It is our process, the approaches that we laid
down keeps us ahead and bring in the quality. Processes are designed in a way that we
listen to our customers and their problems and understand to the extent that we are
fully satisfied in understanding before planning and creating a solution space.

CORPORATE SOCIAL RESPONSIBILITY

Responsibilities towards Employees :


 Equal Opportunities for all – Gender, Religion, beliefs, special abilities
Work Culture – Conductive to growth, Motivating, Healthy, Safe
The Corporate Responsibility :
Corporate Associates – Customers, Stake holders, Business Partners
Business Practices – Fair & Transparent, Committed, Creditable
The Social Responsibility :
Community – Giving back to the society
Earth – Reduce, Reuse, Recycle
CHAPTER 2
SYSTEM ANALYSIS
2.1Existing System
 In existing system, there is only option for viewing the details of the container and
the company who lease the container. Which is developed in windows application and
in proposed we use MVC to develop the project.

 Only the details of the company and the container are shown to the lessee in existing
system.

2.2 Proposed System


 In this project the container leasing system, implementation of online leasing has been
done. So that the lessee can lease the container by using this application wherever he
is.Once lessee login to this application he will be shown with a details and all the
information about the container.
 This makes container leasing simple way to lease the container.
 The lessor can update the latest information and data to this application by the
approval of admin.
 All the details given by the lessee and the lessor are stored in the database using sql.

2.3 FEASIBILITY ANALYSIS

Any project is considered to be feasible only if the proposed system is useful to the
people and organization. In feasibility study we considered the economic aspects of the
problem which is being studied. Three key considerations are involved in the feasibility
analysis are the technical, operational and economical.

2.3.1 TECHNICAL FEASIBILITY

The project has been developed in the ASP.NET technology (front end) and SQL
SERVER (backend). ASP.NET runs on different platforms (windows, Linux, UNIX, etc.)
and it is compatible with almost all servers used today (Apache, IIS etc.) It runs efficiently on
the server side. The memory capacity and speed of the hardware is so user friendly that even
an illiterate can operate the proposed system easily. The SQL server database has become the
world’s most popular open source database because of its consistent fast performance, high
reliability and ease of use.

2.3.2 ECONOMIC FEASIBILITY

This project is use full to a homeo doctors and homeopathy using patient also got the
benefits to this project using process. It main use is save the time and easy to store the details.

2.3.3 OPERATIONAL FEASIBILITY

There is no difficulty in implementing the proposed system, which is user friendly and
functionally reliable that the user is public, will find that the new system reduces the hard ships. The
user of the system is fully aware of the internal working of the system. So they have no problem in
running the system. Thus the system is found to be operationally feasible. Proposed system is
beneficial only if they are turned into information system that will meet the organization’s operation
requirements. This system will certainly be supported since it produces good results and reduces
manual work.
CHAPTER 3
SOFTWARE REQUIREMENT SPECIFICATION

3.1 INTRODUCTION
The hardware requirements are sufficient for installing and running the application; however,
for best results, expand the hardware requirements to optimize performance. The
requirements can be expanded based on the size of your website and the number of users you
will have you determine what hardware requirements would best suit your needs. The most
common set of requirements defined by any operating system or software application is the
physical computer resources, also known as hardware. A hardware requirements list is often
accompanied by a hardware compatibility list (HCL), especially in case of operating systems.
An HCL lists tested, compatible, and sometimes incompatible hardware devices for a
particular operating system or application. The following sub-sections discuss the various
aspects of hardware requirements. Software requirements deal with defining software
resource requirements and prerequisites that need to be installed on a computer to provide
optimal functioning of an application. These requirements or prerequisites are generally not
included in the software installation package and need to be installed separately before the
software is installed.

3.2 Minimum Hardware Requirements

CPU : Intel i3
Primary Memory : 4 GB RAM
Secondary Memory: 500GB HDD
Input Device : Mouse & Keyboard
Output Device : VGA Monitor

3.3 Minimum Software Requirements

Operating System : Windows 7, 8, 10


Front End : ASP.NET- MVC
Back End : MS SQL Server 2014
IDE : MS-VISUAL STUDIO 2015
Languages Used : C#

3.4 SYSTEM DESCRIPTION


3.4.1 MICROSOFT VISUAL STUDIO 2015

Microsoft Visual Studio is an integrated development environment (IDE) from


Microsoft. It is used to develop computer programs, as well as web sites, web apps, web
services and mobile apps. Visual Studio uses Microsoft software development platforms such
as Windows API, Windows Forms, Windows Presentation Foundation, Windows Store and
Microsoft Silver light. It can produce both native code and managed code.

Visual Studio includes a code editor supporting IntelliSense (the code completion
component) as well as code refactoring. The integrated debugger works both as a source-level
debugger and a machine-level debugger. Other built-in tools include a code profiler, forms
designer for building GUI applications, web designer, class designer, and database schema
designer. It accepts plug-ins that enhance the functionality at almost every level—including
adding support for source control systems (like Subversion) and adding new toolsets like
editors and visual designers for domain-specific languages or toolsets for other aspects of the
software development lifecycle (like the Team Foundation Server client: Team Explorer).

Initially referred to as Visual Studio "15", it was released on 7 March 2017.The first
Preview was released on 30 March 2016. Visual Studio "15" Preview 2 was released 10 May
2016.Visual Studio "15" Preview 3 was released on 7 July 2016.Visual Studio "15" Preview
4 was released on 22 August 2016. Visual Studio "15" Preview 5 was released on 5 October
2016.

Current version:

Microsoft Visual Studio current version is Visual Studio 2017 and using .NET Core
2.0.

4.1.1 .NET FRAMEWORK:

.NET Framework (pronounced dot net) is a software framework developed by


Microsoft that runs primarily on Microsoft Windows. It includes a large class library named
Framework Class Library (FCL) and provides language interoperability (each language can
use code written in other languages) across several programming languages. Programs
written for .NET Framework execute in a software environment (in contrast to a hardware
environment) named Common Language Runtime (CLR), an application virtual machine that
provides services such as security, memory management, and exception handling. (As such,
computer code written using .NET Framework is called "managed code".) FCL and CLR
together constitute .NET Framework.

FCL provides user interface, data access, database connectivity, cryptography, web
application development, numeric algorithms, and network communications. Programmers
produce software by combining their source code with .NET Framework and other libraries.
The framework is intended to be used by most new applications created for the Windows
platform. Microsoft also produces an integrated development environment largely for .NET
software called Visual Studio.

.NET Framework began as proprietary software, although the firm worked to


standardize the software stack almost immediately, even before its first release. Despite the
standardization efforts, developers, mainly those in the free and open-source software
communities, expressed their unease with the selected terms and the prospects of any free and
open-source implementation, especially regarding software patents. Since then, Microsoft has
changed .NET development to more closely follow a contemporary model of a community-
developed software project, including issuing an update to its patent promising to address the
concerns.

.NET Framework led to a family of .NET platforms targeting mobile computing,


embedded devices, alternative operating systems, and web browser plug-ins. A reduced
version of the framework, .NET Compact Framework, is available on Windows CE
platforms, including Windows Mobile devices such as Smartphone. .NET Micro Framework
is targeted at very resource-constrained embedded devices. Silver light was available as a
web browser plug in. Mono is available for many operating systems and is customized into
popular Smartphone operating systems (Android and iOS) and game engines. .NET Core
targets the Universal Windows Platform (UWP), and cross-platform and cloud computing
workloads.

4.1.2 MVC (MODEL VIEW CONTROLLER)

As per the official definition, Model-View-Controller (MVC) is a software


architectural pattern for implementing user interfaces. It divides a given software application
into three interconnected parts, so as to separate internal representations of information from
the ways that information is presented to or accepted from the user.
The Model-View-Controller (MVC) is an architectural pattern that separates an
application into three main logical components: the model, the view, and the controller. Each
of these components are built to handle specific development aspects of an application. MVC
is one of the most frequently used industry-standard web development framework to create
scalable and extensible projects.

MVC Components

Following are the components of MVC

 Model
 View
 Controllers

Model

The Model component corresponds to all the data-related logic that the user works
with. This can represent either the data that is being transferred between the View and
Controller components or any other business logic-related data. For example, a Customer
object will retrieve the customer information from the database, manipulate it and update it
data back to the database or use it to render data.

View
The View component is used for all the UI logic of the application. For example, the
Customer view will include all the UI components such as text boxes, dropdowns, etc. that
the final user interacts with.

Controller

Controllers act as an interface between Model and View components to process all the
business logic and incoming requests, manipulate data using the Model component and
interact with the Views to render the final output. For example, the Customer controller will
handle all the interactions and inputs from the Customer View and update the database using
the Customer Model. The same controller will be used to view the Customer data.

FRONT END

4.1.3 ASP.NET MVC

ASP.NET supports three major development models: Web Pages, Web Forms and
MVC (Model View Controller). ASP.NET MVC framework is a lightweight, highly testable
presentation framework that is integrated with the existing ASP.NET features, such as master
pages, authentication, etc. Within .NET, this framework is defined in the System.Web.Mvc
assembly. The latest version of the MVC Framework is 5.0. We use Visual Studio to create
ASP.NET MVC applications which can be added as a template in Visual Studio.

ASP.NET MVC provides the following features:

 Ideal for developing complex but lightweight applications.


 Provides an extensible and pluggable framework, which can be easily replaced and
customized. For example, if you do not wish to use the in-built Razor or ASPX View
Engine, then you can use any other third-party view engines or even customize the
existing ones.
 Utilizes the component-based design of the application by logically dividing it into
Model, View, and Controller components. This enables the developers to manage the
complexity of large-scale projects and work on individual components.
 MVC structure enhances the test-driven development and testability of the
application, since all the components can be designed interface-based and tested using
mock objects. Hence, ASP.NET MVC Framework is ideal for projects with large
team of web developers.
 Supports all the existing vast ASP.NET functionalities, such as Authorization and
Authentication, Master Pages, Data Binding, User Controls, Memberships, ASP.NET
Routing, etc.
 Does not use the concept of View State (which is present in ASP.NET). This helps in
building applications, which are lightweight and gives full control to the developers.

4.1.4 ACTIVE SERVER PAGES.NET

ASP.NET is a programming framework built on the common language runtime that


can be used on a server to build powerful Web applications. ASP.NET offers several
important advantages over previous Web development models:

 Enhanced Performance. ASP.NET is compiled common language runtime code


running on the server. Unlike its interpreted predecessors, ASP.NET can take
advantage of early binding, just-in-time compilation, native optimization, and caching
services right out of the box. This amounts to dramatically better performance before
you ever write a line of code.
 World-Class Tool Support. The ASP.NET framework is complemented by a rich
toolbox and designer in the Visual Studio integrated development environment.
WYSIWYG editing, drag-and-drop server controls, and automatic deployment are
just a few of the features this powerful tool provides.
 Power and Flexibility. Because ASP.NET is based on the common language
runtime, the power and flexibility of that entire platform is available to Web
application developers. The .NET Framework class library, Messaging, and Data
Access solutions are all seamlessly accessible from the Web. ASP.NET is also
language-independent, so you can choose the language that best applies to your
application or partition your application across many languages. Further, common
language runtime interoperability guarantees that your existing investment in COM-
based development is preserved when migrating to ASP.NET.
 Simplicity. ASP.NET makes it easy to perform common tasks, from simple form
submission and client authentication to deployment and site configuration. For
example, the ASP.NET page framework allows you to build user interfaces that
cleanly separate application logic from presentation code and to handle events in a
simple, Visual Basic - like forms processing model. Additionally, the common
language runtime simplifies development, with managed code services such as
automatic reference counting and garbage collection.
 Manageability. ASP.NET employs a text-based, hierarchical configuration system,
which simplifies applying settings to your server environment and Web applications.
Because configuration information is stored as plain text, new settings may be applied
without the aid of local administration tools. This "zero local administration"
philosophy extends to deploying ASP.NET Framework applications as well. An
ASP.NET Framework application is deployed to a server simply by copying the
necessary files to the server. No server restart is required, even to deploy or replace
running compiled code.

 Scalability and Availability. ASP.NET has been designed with scalability in mind,
with features specifically tailored to improve performance in clustered and
multiprocessor environments. Further, processes are closely monitored and managed
by the ASP.NET runtime, so that if one misbehaves (leaks, deadlocks), a new process
can be created in its place, which helps keep your application constantly available to
handle requests.
 Customizability and Extensibility. ASP.NET delivers a well-factored architecture
that allows developers to "plug-in" their code at the appropriate level. In fact, it is
possible to extend or replace any subcomponent of the ASP.NET runtime with your
own custom-written component. Implementing custom authentication or state services
has never been easier.
 Security. With built in Windows authentication and per-application configuration,
you can be assured that your applications are secure.
4.1.5 ABOUT MICROSOFT SQL SERVER 7.0

Backend
Microsoft SQL Server is a Structured Query Language (SQL) based, client/server
relational database. Each of these terms describes a fundamental part of the architecture of
SQL Server.
Microsoft SQL Server is a relational database management system developed
by Microsoft. As a database server, it is a software product with the primary function of
storing and retrieving data as requested by other software applications—which may run either
on the same computer or on another computer across a network (including the Internet).

Microsoft markets at least a dozen different editions of Microsoft SQL Server, aimed
at different audiences and for workloads ranging from small single-machine applications to
large Internet-facing applications with many concurrent users.

Microsoft SQL Server Management Studio (SSMS) is an integrated environment to


manage a SQL Server infrastructure. It provides a user interface and a group of tools with
rich script editors that interact with SQL Server

Database

A database is similar to a data file in that it is a storage place for data. Like a data file,
a database does not present information directly to a user; the user runs an application that
accesses data from the database and presents it to the user in an understandable format.

A database typically has two components: the files holding the physical database and
the database management system (DBMS) software that applications use to access data. The
DBMS is responsible for enforcing the database structure, including:

 Maintaining the relationships between data in the database.


 Ensuring that data is stored correctly and that the rules defining data relationships are
not violated.
 Recovering all data to a point of known consistency in case of system failures.

4.1.6 STRUCTURED QUERY LANGUAGE (SQL)

To work with data in a database, you must use a set of commands and statements
(language) defined by the DBMS software. There are several different languages that can be
used with relational databases; the most common is SQL. Both the American National
Standards Institute (ANSI) and the International Standards Organization (ISO) have defined
standards for SQL. Most modern DBMS products support the Entry Level of SQL-92, the
latest SQL standard (published in 1992).

SQL Server Features

Microsoft SQL Server supports a set of features that result in the following benefits:

Ease of installation, deployment, and use

SQL Server includes a set of administrative and development tools that improve your
ability to install, deploy, manage, and use SQL Server across several sites.

Scalability

The same database engine can be used across platforms ranging from laptop
computers running Microsoft Windows® 95/98 to large, multiprocessor servers running
Microsoft Windows NT®, Enterprise Edition.

Databases

A database in Microsoft SQL Server consists of a collection of tables that contain


data, and other objects, such as views, indexes, stored procedures, and triggers, defined to
support activities performed with the data. The data stored in a database is usually related to a
particular subject or process, such as inventory information for a manufacturing warehouse.

SQL Server can support many databases, and each database can store either
interrelated data or data unrelated to that in the other databases. For example, a server can
have one database that stores personnel data and another that stores product-related data.
Alternatively, one database can store current customer order data, and another; related
database can store historical customer orders that are used for yearly reporting. Before you
create a database, it is important to understand the parts of a database and how to design these
parts to ensure that the database performs well after it is implemented.

SSMS tools

SSMS provides tools to configure, manage and administer instances of Microsoft


SQL Server, and it brings together a range of graphical and visual design tools and rich script
editors to simplify working with SQL Server. SSMS combined features come from Enterprise
Manager, Query Analyzer and Analysis Manager, along with features included in previous
releases of SQL Server. It supports most of SQL Server's administrative tasks and maintains a
single, integrated environment for SQL Server Database Engine management and authoring.

SSMS components

Microsoft SQL Server Management Studio features include Object Explorer, which
can view and manage all objects in a SQL Server instance; Template Explorer, which builds
and manages files of text that can be reused to speed up query and script development;
Solution Explorer, which builds the projects used to manage administration items, such as
queries and scripts. (Microsoft plans to remove Solutions Explorer in versions beyond
Microsoft SQL Server 2016). SSMS components customize keyboard shortcuts and viewing
property pages; connect to instances of the Database Engine and Analysis Services; visual
design tools; and interactively build and debug queries and scripts.

SSMS versions and updates

The first SSMS version was released alongside SQL Server 2005, and it has continued
to be a part of management for Microsoft SQL Server 2008, SQL Server 2012, and SQL
Server 2016. It also provides support for Azure SQL Database and Azure SQL Data
Warehouse. It is also possible to administer Azure SQL Databases and servers using SSMS.
On Azure, SSMS can create and manage logins and monitor SQL databases through dynamic
management views.

CHAPTER 4
SYSTEM DESIGN

INTRODUCTION
System design is the process of defining the elements of a system such as the architecture,
modules and components, the different interfaces of those components and the data that goes
through that system. It is meant to satisfy specific needs and requirements of a business or
organization through the engineering of a coherent and well-running system.

3.1 Data Flow Diagram:


A two-dimensional diagram that explains how data is processed and transferred in a
system. The graphical depiction identifies each source of data and how it interacts with other
data sources to reach a common output. Individuals seeking to draft a data flow diagram mast
(1) identify external inputs and outputs, (2) determine how the inputs and outputs relate to
each other, and (3) explain with graphics how these connections relate and what they result in

Data Flow Symbols:

Symbol Description
An entity. A source of data or
destination for data.

A process or task that is


performed by the system.
A data store, a place where data is
held between processes.

A data flow.

Level 0
In LEVEL O diagrams explains the whole process in the system. The user
appointment the software and the admin make the scheduling and user details. Those details
are stored and modified by the admin.

Login/Register request for equipment/upload

USER EQUIPMENT ADMIN


LEASING
LESSOR/LESSEE

Verification/approves approves
leasing upload/equipment

LEVEL 1

In LEVEL 1 diagrams fully explains the user process such as the user first enrol their
Details in the system Details are username, password and their personal details. Then the user
Views Available list in the website. The users select the appointment. The user enters their
username and password for installing the software.

Login/Register request equipment

LESSEE EQUIPMENT LESSOR


LEASING
approves leasing login / request uploading

verify leasing approves uploading

ADMIN

LEVEL 2
In LEVEL 2 diagram explain the admin side process. The admin have rights to add
the details about the maintain the user details. User details are user name, password, address,
and Appointment details. The main process is admin read the view user address.

EQUIPMENT
LEASING
LESSOR LESSEE

Registe Register
r table table

Lessor details View updates Lessee details

Booking
table
Upload
Request for Request Approval Book
uploading upload table Containers

Approval for
Request
uploading leasing
uploading
Request for
leasing

Approval request
Upload from lessee
table
payment

request
Approval Payment
table table
4.3 USE CASE DIAGRAM:

4.4 CLASS DIAGRAM


5.1 Architectural Design:

Home
ABOUT GALLERY REGISTER LOGIN CONTACT

LESSEE LESSOR ADMIN

Lessor page
Lessee page Home

View equipment Lessor update

Select/request for leasing Update request

Lease equipment View updated data

Register for update Return to home

Return to continue

Lessee approval Lessor approval View Lessee View Lessor


4.6 SEQUENCE DIAGRAM

2.7DATA DICTIONARY:

TABLE 1: LESSOR (OWNER) REGISTRATION TABLE

COLUMN NAME DATATYPE CONSTRAINTS


Owner ID Varchar (10) Primary key

Owner Name Varchar (20) Not Null

Age Number (10) Not Null

Address Varchar (20) Not Null

Phone Number Number (10) Not Null

E Mail ID Varchar (20) Not Null

ID Proof Varchar (25) Not Null

TABLE 2: LESSEE (USER) REGISTRATION TABLE

COLUMN NAME DATATYPE CONSTRAINTS

User ID Varchar (10) Primary key

User Name Varchar (20) Not Null

Age Number (10) Not Null

Address Varchar (20) Not Null

Phone Number Number (10) Not Null

E Mail ID Varchar (20) Not Null

ID Proof Varchar (25) Not Null

TABLE 3: LESSOR (OWNER) REQUEST FOR UPLOADING TABLE


COLUMN NAME DATATYPE CONSTRAINTS

Owner ID Varchar (10) Primary key

Address Varchar (20) Not Null

Equipment ID Number (10) Primary key

Equipment name Varchar (20) Not Null

Pictures Image Not Null

TABLE 3: LESSEE (USER) REQUEST FOR EQUIPMENT TABLE

COLUMN NAME DATATYPE CONSTRAINTS

User ID Varchar (10) Primary key

Address Varchar (20) Not Null

Equipment ID Number (10) Primary key

Equipment name Varchar (20) Not Null

Duration Varchar (25) Not Null

Usage Varchar(25) Not null


4.1 Methodology:
The V - model is SDLC model where execution of processes happens in a sequential
manner in V shape. It is also known as Verification and Validation model.V - Model is an
extension of the waterfall model and is based on association of a testing phase foreach
corresponding development stage. This means that for every single phase in the development
cycle there is a directly associated testing phase. This is a highly disciplined modeland next
phase starts only after completion of the previous phase.

Use v shape model

The V-shaped model extends the SDLC waterfall model to include a set of verification
and validation steps. The waterfall model includes:

 requirements analysis
 design
 implementation
 testing
 verification
 maintenance

Each of these phases of the SDLC have distinct activities with distinct deliverables, or
outcomes. In the V-shaped model, all the steps have a corresponding testing phase. Let's take
a look.

 The Requirements phase, a document describing what the software is required to do


after the software is gathered and analysed and the corresponding test activity is user
acceptance testing.
 The Architectural Design phase, where a software architecture is designed and
building the components within the software and the establishing the relationships
between the components and the corresponding test activity is System Testing.
 The High Level Design phase, breaking the system into subsystems with identified
interfaces; then gets translated to a more detailed design and the corresponding test
activity is Integration testing.
 The Detailed Design phase, where the detailed implementation of each component is
specified. The detailed design broken into Data structures, Algorithm used and the
corresponding test activity is unit testing.
 Coding in which each component of the software is coded and tested to verify if
faithfully implements the detailed design.

Advantages and Limitations of V-Model:

Advantages:

 Emphasize for verification and validation of the product in early stages of product
development.
 Each stage is testable.
 Project management can track progress by milestones.
 Easy to understand implement and use.

Limitations:

 Does not easily handle events concurrently.


 Does not handle iterations or phases.
 Does not easily handle dynamic changes in requirements.
 Does not contain risk analysis or Mitigation activities.
V- Model Pros and Cons
The advantage of V-Model is that it’s very easy to understand and apply. The
simplicity of this model also makes it easier to manage. The disadvantage is that the model is
not flexible to changes and just in case there is a requirement change, which is very common
in today’s dynamic world, it becomes very expensive to make the change.

Pros:
 This is a highly disciplined model and Phases are completed one at a time.
 Works well for smaller projects where requirements are very well understood.
 Simple and easy to understand and use.
 Easy to manage due to the rigidity of the mode each phase has specific deliverables
and a review process.

Cons
 High risk and uncertainty.
 Not a good model for complex and object-oriented projects.
 Poor model for long and on going projects.
 Not suitable for the projects where requirements are at a moderate to high risk of
changing.
 Once an application is in the testing stage, it is difficult to go back and change a
functionality

CHAPTER V

SYSTEM IMPLEMENTATION

5.1 INTRODUCTION

Equipment Leasing Management is a highly complicated issue due the high volatile of
container demand and supply. Shipping Container is not a direct demand at all, but a derived
demand of the international trade in industry. Therefore containers are faced with a
demand to strike a balance between the demands and supply. The Present Equipment
Leasing Management solutions are reactive rather than proactive. The need for an effective
Equipment Leasing Management comes in to play under such market conditions. ‘Container’
means, an article of transport equipment of a permanent character and accordingly
strong enough to be suitable for repeated use or any type of container, transportable
tank or flat, swap body, open top , dry wan , or any similar unit load used to consolidate
goods, and any equipment ancillary to such unit load. Container ships and containers are
supplementary to each other thus Container Shipping Lines cannot transport cargo if
containers are not available. In order to fulfill the demand and satisfy the lessee to lease
the container in the efficient way this application is developed. Generally, container shipping
companies reposition empty containers from surplus ports to deficit ports. As a result,
obviously, there is a cost involved in balancing the container fleet by respective
shipping lines. The available containers are uploaded to this application by the lessor
(owner), and he specifies all the details like container history, container type, and container id
and container rate per year. A truck trailer body that can be detached from the chassis for
loading into a vessel, a rail car or stacked in a container depot. Containers may be ventilated,
insulated, refrigerated, flat rack, vehicle rack, open top, bulk liquid or equipped with interior
devices.

Project description:
The Container Leasing Management is an application developed for leasing containers
without any issues or exceptions for shipping porpose. This application is developed in .net
platform for connecting admin,lessee(user who takes lease) and lessor(owner of the
container).This application is very efficient and simple way for lessee(user) to lease the
container through this application and it is not only useful for the lessee(user), it is also
useful for the lessor(owner) also to upload the current details and adding informations about
the container.These all informations that are given by the lessor are stored in the database and
approved by the admin to upload it to the lessee view.For leasing the container the lessee
needs to register the information and that should be approved by the admin to lease any type
of container.These informations given by the lessee are stored in the database and the
approval is managed by the admin.This container leasing management is an efficient
application for leasing the containers online. In existing system, there is only option for
viewing the details of the container and the company who lease the container. Only the
details of the container are shown to the lessee in existing system. In this project the container
leasing system, implementation of online leasing has been done. So that the lessee can lease
the container by using this application wherever he is.Once lessee login to this application he
will be shown with a details and all the information about the container. This makes container
leasing simple way to lease the container. The lessor can update the latest information and
data to this application by the approval of admin.All the details given by the lessee and the
lessor are stored in the database using sql. Any number of customers can book the container
at the same time without any traffic or issues. It avoids time consuming and makes the
process effective. Using java script the data and information in login and register are secured.
5.3 LIST OF MODULES

 Index
 Registration
 Login
 Admin
 Lessor
 Lessee
 DB Module
 Approval

5.4 MODULES DETAILS

Index:

 The index module shows all the details such as : about ,gallery, blog, contact us, icons
,blog, typography etc.

 By using this module both the lessee and lessor can easily acquire the knowledge
about this container leasing application.

Registration:

 This registration module is a must one for lessor and lessee if they are new to this
application both of them have to register them selves to login to this application.

 After the registration process their details will be stored in the database.

Login:
 The login module is used to login into this application by using the user name and
password.

 Here all the three that is : lessor, lessee and the admin can login using this module , as
we have given login as option in this module. After this process they will be diverted
to their respective web pages automatically.

Admin:

 This administrator module plays an vital role in controlling the actions done by lessor
and lessee.

 This admin will approve the lessor for uploading their container details and lessee for
leasing the containers from the lessor. Without admin approval they can’t proceed
further .

 This admin module holds all the datas of the lessor and lessee that is stored in the
database.

Lessor:

 In this module the lessor is allowed to update their container details to the admin for
getting the admin’s approval.

 First the lessor have to request the admin for updating the leasing details. After
getting the approval only they will be allowed to update their container details to their
page.

Lessee:

 Here the lessee needs the approval of the admin to move to the leasing page.

 After getting the approval they can view the leasing page where they can view
containers details and their lessor details, then they can fill and book the required
containers for leasing and request the admin for leasing the container.

 After getting the approval for leasing request the lessee once again needs to conform
leasing.

DB Module:
 The database module stores all the data’s and informations that are entered by the
lessor and lessee immediately.

 These informations can be viewed only by the authorized person that is the admin.

 The admin can retrieve the data’s from this module whenever he needs without any
problem.

Approval:

 This approval module one of the important module in this application this is a
common module which is present on both lessor and lessee side to get the approval of
the admin.

CHAPTER VI

TESTING

6.1 INTRODUCTION

Software testing is an activity to check whether the actual results match the expected results
and to ensure that the software system is Defect free. Software testing also helps to identify
errors, gaps or missing requirements in contrary to the actual requirements. It can be either
done manually or using automated tools. Some prefer saying Software testing as a white box
and Black Box Testing.

When the design is complete, coding follows and the finished code is then tested at the unit
or module level by each programmer; at the component level by the group of programmers
involved; and at the system level when all components are combined together. At early or late
stages, a product or service may also be tested for usability.

6.2 UNIT TESTING


Unit testing a testing technique using which individual modules are tested to determine if
there are any issues by the developer himself. It is concerned with functional correctness of
the standalone modules. The main aim is to isolate each unit of the system to identify,
analyze and fix the defects. Unit testing is a software development process in which the
smallest testable parts of an application, called units, are individually and independently

scrutinized for proper operation. Unit testing can be done manually but is often automated.

CHAPTER 7

CONCLUSION

CONCLUSION:
The Container Leasing Management is an application developed for leasing
containers without any issues or exceptions for shipping porpose. This application is
developed in .net platform for connecting admin,lessee(user who takes lease) and
lessor(owner of the container).This application is very efficient and simple way for
lessee(user) to lease the container through this application and it is not only useful for the
lessee(user), it is also useful for the lessor(owner) also to upload the current details and
adding informations about the container.These all informations that are given by the lessor
are stored in the database and approved by the admin to upload it to the lessee view.For
leasing the container the lessee needs to register the information and that should be approved
by the admin to lease any type of container.These informations given by the lessee are stored
in the database and the approval is managed by the admin.This container leasing management
is an efficient application for leasing the containers online

CHAPTER 8

FUTURE ENHANCEMENT

8.1Future Enhancement:

The Equipment leasing can be improved even more by including tracking but it
is difficult to track when it is shipping , and only satellite communication can be
done so it may be possible when maximum level of scientific operation are
used.

7. CHARTS

7.1 PERT CHART


Review on
requirement
Requirement analysis System Study and
specification
analysis
Start 1 7days 2 8days 3 6days

14/11 20/11 22/11 29/11 1/12 6/12

System Review on system System Design and


Implementation design Charts
7-10 31days 6 7days 4-5 14 days
11/01 11/02 4/01 10/01 7/12 20/12

Review on system
System testing Deployment
implementation
7.2 GANTT CHART

A Gantt Chart is a graphical deputation of a project schedule and it is a type of bar


chart that shows the start and finish dates of several elements of a project that include resources, tasks
and dependencies Henry Gantt, an American Mechanical Engineer designed the Gantt Chart.

The following chart explains about my project schedule from my title selection till
validating and testing. The scheduling is done according to the weeks and time management plays a
major role in building up my project coding plays a huge part of my project where testing and
validation serves an essential role

TASK/WEEK 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Project proposal
approval

System study and


analysis

System design

PERT and Gantt


chart

I review

System
implementation

System
implementation

System
implementation

System testing

II review

Rough draft
submission

Rough draft
submission after
correction

Final record
submission

Final viva

You might also like