Minor Project Content Repaired)

8/2/2019 Minor Project Content Repaired)

http://slidepdf.com/reader/full/minor-project-content-repaired 1/52

1.1 Introduction

Cheque generator is a desktop based application , it is made for a insurance company Bhomi . Its

main purpose is security. Cheques are widely used in modern day financial transaction. Cheque

generator software is a computer program that can easily create and print beautiful checks simply

by entering the desired data into the blank fields in the computer program.

It has a feature like password protection, check preview, security system that reduces user error.

This software enables secure, flexible, and cost effective solutions for cheque printing.

This software is convient and error less. It maintain details against which payment are made. A

login screen keeping unauthorized users out. Print single or multiple checks on customized bank

layout. Have a report of cheque printed over a period of time. Cheque printing software has an

ability to view original report data with formatting-without the database. Cheque printing is very

fast .

1



2.1 Introduction – Literature Review

Cheque Generator is an enterprise-level cheque printing software that provides a multi-user

environment to print and manage your cheques. Cheque Generator provides a complete cheque

printing which can print all the cheque elements; include Payee, Date, Amount, A/C Payee Only,

Bearer, etc. You are no need to write any, just fill in the software and print the cheque. The cheque

is ready to issue once sign.

Cheque Generator supports different types of printers, Laser, Inkjet, and Dot-Matrix printers. Allissued cheques are kept in records and listed in the cheque book. The cheques issued history can be

tracked easily. You can also move to-and-fro to review your issued cheque. Payee report and

account report give you every detail about the issued cheque.

It is simple to manage the issue of cheques in accordance with banking procedures.

ChequePrinting.Net allows you to create multiple users to access the software. There are two types

of user: Administrator and General User . The multi-user environment allows different user to

access the same set of data in a centralized database.

It is very easy to use GUI interface. Once the formatting is done, you just have to provide basic

information like client name, bank name, date and amount (numeric). Cheque Generator Software

is compatible with any printer and is very fast in printing.

Cheques are widely used in modern day financial transaction. Cheque generator software is a

computer program that can easily create and print beautiful checks simply by entering the desired

data into the blank fields in the computer program.

It has a feature like password protection, check preview, security system that reduces user error.

This software enables secure, flexible, and cost effective solutions for cheque printing.

2



2.2 Non-Financial:

• The Admin (Head of the Organization) should be able to create the user profiles like

the login id and the password for the users and as well he alone has the right to declare and

modify the information of the users and even he can issue the cheque to the users.user can oly

view the details regarding issued cheque.

• The user can only enter and check the details of the issued cheque and as well he can

change the password or even he can update his details. He can also see the details of the cheque

issued ,date of issuing and further details of the cheque . But he cannot access the details of the

other useres as he is not authorized for it.

•

This product is developed for better Business look.• Especially for Personnel, Offices, Small Business, MLM Companies, Doctors, CA,

Lawyers, Trusts, Clubs, Hotels, Hospitals etc

• Search for any cheque is possible..

• Easy to use.

• Cheques history provides the cheque register to view. Unlimited Payee Records.

• Advanced search option is needed to be included so as to fetch the details of the cheque

issued.

• The details of the users, no of cheques issued and various other details are needed to be

maintained with the help of the database.

2.3 Financial

The application software should charge on cartridge refilling of the printer including softwaredeployment , maintenance and time to time updating cost by the developer.

3



2.4 Functional Requirements

• Full payment during the deployment of the application software by the developer

• The admin has the right to access all the pages of the website

• The user will only be able to access the details of specific pages of the website like he can

only view the status of cheque issued and even update the status.

• Also the user has the password as the combination of his first name and father’s name for

logging in to his a/c and as well he can update his profile and the profile thus change can be altered

only after the admin agrees for it.

• A database to store all the details cheque issued as well as all the details of the user and

admin.using all the details one can check whether a particular cheque is issued to a specific person

or not.

• The project needs printer as a hardware requirement for printing the cheques.

• The User can change his or her password by using change password facility.

2.5 Non Functional Requirements

• Shows all the reports of cheque issued to whom on which date.

• The GUI Interface is easy to understand and work on .

• For the preview of the report system will take some time but if we consider the

overall performance it is good.

• System is reliable to a great extent and provide the admin with overall view of the

cheque transactions.

• Confidentiality of each and every user is maintained to a great extent since this

application s/w has different view for admin and users.

4



• Financial constraint is fully satisfied according to the end user.

3.1 Problem Statement

This project is aimed at developing an application software that can be used in any large

enterprise where it is difficult to maintain the no of cheque issued per day with all the details like

whom cheque is paid to, all the details of the payee etc. The project is an application software

that can be accessed by two set of users. This system can be used for maintaining all the details

related to issued cheque by the organization which is using it. There are additional features like

weekly report generators using the database to keep a hard copy of the record as well in case if

backup of database is not present etc in this system.

3.1.1 Description of present situation

The application software allows to edit cheque print text, e.g., Not Transferable. It has Simplified

Registration Process. Printed cheque cannot be edited and deleted. Cheque number cannot beduplicated except VOID cheque. Print out quality is greatly enhanced which gives clear and

precise printing. When a cheque is printed again, alert will be prompted. When a void cheque is

printed, alert will be prompted . Date format is specific and during printing of cheque it will take

the date from system. Compatible with Windows Xp ,Windows 7,Windows vista and Windows 98

but there will be speed problem with windows 98 software will take more time as compared to

other to preview the cheque and reports.It provides with an upgraded run-time kernel. It gives

performance Enhancement facilities on Loading and Parsing Documents. Fine tune database

kernel to enhance performance and resolve database locking issue. Give the preview of cheque and

record with great performance.

5



3.1.2 Brief description of goal

Now we want an application software to be incorporated in the

systems of large organizations to customize their work . It should be a

convenient tool which allow to create the cheques and print a no of cheque with a great

performance. It should provides a complete cheque printing which can print all the cheque

elements; include Payee, Date, Amount, A/C Payee Only, Bearer, etc. One need not to write

anything , just fill the details requied in the software and print the cheque. It should be a easy and

powerful search tools enable to search and find a Cheque with full details .Payee list managementshould be done for any future correspondance .Before printing approval for every Cheque is

required .Keeps record of all issued/non-issued, cleared/uncleared Cheques. Detailed reports

shoule be a feature.It should update the cheque book status .If during the print event of any cheque

the current supply is terminated or because of any other reason if the system is off then when the

current supply is again started one can print that cheque.It should be user-friendly, fast , secure

,flexible, powerfull and relaible. Makes the work results more accurate than manual cheque

making.

3.2 Software used

• Jdk 1.7

• My SQL

• NetBeans IDE 6.9

• Ireport plugins

6



3.3 Description of users and their role

3.3.1 Admin

The Admin (Head of the Organization) should be able to create the user profiles like the login id

and the password for the employees and as well he alone has the right to declare and modify the

charges.

3.3.2 User

The employee can only enter or edit the details of the deliverables and as well he can change the

password or even he can update his details. He can also see the details of the charges, contact

information based on the location, and the pin codes of the location. But he cannot access the

details of the other employees as he is not authorized for it.

7



4.1 Technical Aspects of the System

4.1.1 Auto-Increment Fields are Indispensable

If you are designing a database, make sure that you add an auto-incriminating identity field to

every table. It’s a fastest, easiest and least error-prone way to assign a unique “identification

number” to every record. If you create a table without a unique identification column, you will

have trouble when you need to select that specific row for deletion or updates.

4.1.2 Accessing Data the Easy Way

The “easy way” to access data is to perform all your database operations manually and Not worry

about maintaining disconnected information. This model is closest to traditional ADO

programming, and it allows you to side-step potential concurrency problems, which result whenmultiple users try to update information at once.

The application should alone calculate the details of the charges based on the type of service,

destination location, and as well based on the weight of the deliverable. If a customer chooses for

the VPP service he need not pay at the time of dropping the deliverable at the organization as it

will be charged at the time of delivering at the destination address

8



4.2 Software & Hardware Specification

4.2.1 Hardware Requirements

s.no Description Alternatives (If

available)1 PC with 5 GB

hard-disk and 512

MB RAM

Not-Applicable

2 Printer (any type)

3 Pentium 4

processor

NotApplicable

4 Windows

Xp,Windows

7,Windows vista

Windows 98 (but

performance will be

slow)

4.2.2 Software Requirements

Number Description

1 Jdk 1.7

2 My-SQL server

3 NetBeans IDE 6.9

4 IReport plugins

9



4.3 Functional Requirements

• Full payment during the deployment of the application software by the developer

• The admin has the right to access all the pages of the website

• The user will only be able to access the details of specific pages of the website like he can

only view the status of cheque issued and even update the status.

• Also the user has the password as the combination of his first name and father’s name for

logging in to his a/c and as well he can update his profile and the profile thus change can be altered

only after the admin agrees for it.

• A database to store all the details cheque issued as well as all the details of the user and

admin.using all the details one can check whether a particular cheque is issued to a specific person

or not.

• The project needs printer as a hardware requirement for printing the cheques.

• The User can change his or her password by using change password facility.

10



4.4 Data Flow Diagram

4.4.1 DFD Level 0

Place order View status

View item Get item

Get status of item Update status

11

CUSTOME

R

TARS DELIVERY

SYSTEM



Fig 4.4.1: DFD Level 0

4.4.2 DFD Level 1 EMPLOYEE

Update

Get profile Update

Update profile

Update status update

Get status

o

place order

12

EMPLOYE

E

CREAT

PROFILE

STATUS

DELIVREABLE ITEM

ADMIN

EMPLOYEE

CUSTOMER

Tars



Service

Fig 4.4.2: DFD Level1

4.5 System Flow Diagram

13



Fig 4.5.1: System Flow Diagram

4.6 Entity Relationship Diagram

14



Fig 4.6.1: Entity Relationship Diagram

15



4.7 Testing

4.7.1 Introduction

A project is incomplete without successful testing. A successful system design helps in efficient

testing. Testing is vital to the success of a system.

4.7.2 Objective

• Testing is a process of executing a program with the intent of finding an error.

• A good test case is one that has a high probability of finding an as-yet-undiscovered error.

• A successful test case is one that uncovers an as-yet-undiscovered error.

Testing is applicable to our project, in the form of the following techniques. Testing is done in

each and every module so that the customer can by the models without any loop holes and security

is maintained throughout the transaction.

4.7.3 Testing Techniques

Different types of testing applicable to our project are:

• Unit Testing.

• Integrated Testing.

• Acceptance Testing.

16



4.7.3.1 Unit Testing

In this testing each sub module was tested individually with the test data and then integrated in to

the overall system. The modules dynamic loading and customer cart. These modules contain

several sub modules that are necessary for unit testing.

4.7.3.2 Integrated Testing

Integrated testing is carried systematically for constructing the program structure while at the same

conducting tests to uncover errors associated with interfacing. The modules discussed here are

interrelated i.e. One module can have effect on another module .So, in unit testing each sub

modules are tested for accuracy and error free. Here all modules are combined and tested as a

whole.

4.7.3.3 Acceptance testing:

Acceptance testing is performed to do real life testing of the data to the client. The need for

acceptance testing is the find overall system performance. The objective is to obtain customer

satisfaction and build up customer loyalty and goodwill.

4.7.4 SDLC, Deployment & Debugging

4.7.4.1 Software Development Life Cycle (SDLC)

The development processes specify the major development and quality assurance activities that

need to be performed in the project, and hence form the core of the software development

processes.

The key activities that have to be part of any software development activity:

Requirements Definition: During the requirements definition activity or phase, a

requirements definition team prepares the requirements document and completes a draft of

17



the functional specifications for the system. This should identify the intended use

performance expected from the system as visualized by the user. System Requirements

Review (SRR) can be planned at the end of this activity to evaluate the requirements. An

implementation plan can be prepared describing the plan to build the software.

Requirements Analysis: The next activity is requirement analysis, during which the

development team classifies each specification and performs functional or object-oriented

analysis. Working with the requirements definition team, developers resolve ambiguities,

discrepancies and to-be-determined (TBD) specifications, producing a final version of the

functional specifications document and a requirements analysis report. This phase is

concluded with a Software Specification Review (SSR), at which the results of the analysis

are presented for evaluation. The base lined functional specifications forms a contract

between the requirements definition team and the software development team, and are the

starting point for preliminary design.

Preliminary Design: Members of the development team produce a Preliminary Design

Report (PDR) in which they define the software system architecture and specify the major

subsystems, input/output (I/O) interface, and processing modes. The preliminary design

review (PDR), conducted at the end of this activity provides an opportunity to evaluate the

design presented by the development team.

Detailed Designed: The System architecture defined during the previous phase is

elaborated in greater detail, to the level of subroutines. The development team fully

describes user input, system output; I/O files, and inter-module interfaces. The

corresponding documentation, including complete baseline diagrams, makes up the

detailed design document. At the critical Design Review (CDR), the detailed design is

evaluated o determine if the levels of detail and completeness are sufficient for coding to begin.

Implementation: During implementation (code, unit testing, and integration) activity. the

development team codes the required modules using the detailed design document. The

18



system grows as new modules are coded, tested, and integrated. The developers also revise

and test reused modules and integrate them into the evolving system. Implementation is

complete when all code is integrated, and when supporting documents (system test plan

and draft user’s guide) are written.

System Testing: This activity involves the functional testing of end-to –end system

capabilities according to the system test plan. The development team validates the

completely integrated system and produces a preliminary system description document.

The end of this activity requires successful completion of tests.

Maintenance and operation: Maintenance and operation are the important and unavoidable

activities that begin when acceptance testing ends. The system becomes the responsibility

of the maintenance and operation group. For some support software, the maintenance and

operation phase may be very active due to changing user needs.

4.7.4.2 Deployment

All Software development organization will have to carry out these activities if they have to

develop a product. The sequence and detailed level of these activities will depend on the nature of

the project and application, the methods and tools to be used, and the controls and deliverables that

are required. All the modules done in the “Cheque Generator” have been deployed successfully.

Only minor changes have adapted after the deployment process which doesn’t change the progress

of the project in any way. All the modules have worked as per the description after deployment.

19



Debugging

Need For Debugging:

Before an application can be successfully deployed, all syntax errors and semantic errors need to

be completely eliminated. Software should be tested before it is considered completely reliable.

This process of testing software should an integral part of the software development process.

However, while testing will help identify whether the output is correct or not, it will not help to

identify where exactly the error occurred. This is where debugging comes in the picture. The

fundamental principal of debugging is confirmation. Finding the bug is process of confirming

many things that the developer believes are true until the developer finds one which is not true.

Types of Errors:

Syntax Errors:

Syntax errors are the most obvious types of errors that come across while coding. These arise

when the programmer does not follow the rules of the language while writing code.

Runtime Errors:

Run time errors occur when the application attempts to perform an operation that is not

possible to carry out. These types of errors happen at run-time.

Procedure of Debugging:

20



Typically most programmers try to isolate a problem by calling output functions to print some

message to indicate that the code up to that point is executing perfectly. These functions may also

be used to track and display the value of a variable within the program. This is a valid debugging

technique. However, the tedious part is that once the problem has been located and fixed, all these

extra function calls need to be removed from the entire code. This becomes quite a tedious process.

To simplify this, most programming languages and tools provide debuggers that enable

programmer to observe the run-time behavior of a program, track values of variables and identify

the location of semantic errors. The benefit of using a debugger is that values of variables can be

inspected without inserting any output statements to display them, Visual Studio.NET provides a

debugger that the programmer can use to debug code written in one of the .NET supported

languages. It provides the programmer with means to evaluate and edit variables, suspend or pause

program execution view contents of registers and view the memory space consumed by the

application.

The VS.NET debugger provides several windows to monitor program execution. Some of the

windows which are useful while debugging are:

Locals Window

Watch Window

Quick Watch dialog box

Immediate window

Each of these windows is explained in the sections that follow:

Locals Window:

The local Window displays the values present in the local variables. It lists only the variables that

are within the current scope (that is, the method being executed) and tracks their values.

Watch Window:

The watch window is used to evaluate variables and expressions and track their values through the

program. It can be also be used to edit the value of a variable.

21



Quick Watch Dialog Box:

The Quick Watch Dialog Box can be used to quickly evaluate or expression. The value of a

variable can also be modified via this dialog box.

Immediate Window:

The immediate mode of the Command Window can be used for checking the value of a variable,

for assigning a value to a variable as well as to run a line of code.

4.8 Databases Used

4.8.1 Bills

IDBill Nchar(10)

CustomerName Nchar(10)

CustomerAddress Nchar(10)

IDCardNo Nchar(10)

SentDate Nchar(10)

IDEmployee Nchar(10)

TotalFee Nchar(10)

4.8.2 Bill Details

IDBillDetails Nchar(10)

22



IDBill Nchar(10)

IDService Nchar(10)

PackageList Nchar(10)

Weight Nchar(10)

DestinationAddress Nchar(10)

IDDistanceFee Nchar(10)

Fee Nchar(10)

ReceiveDate Nchar(10)

DeliveryStatus Nchar(10)

4.8.3 Employees


Username Nchar(10)

Password Nchar(10)

Empname Nchar(10)

Sex Nchar(10)

Address Nchar(10)

Phone Nchar(10)

Email Nchar(10)

IDBranch Nchar(10)

Role Nchar(10)

23



Enabled Nchar(10)

4.8.4 Branch

IDBranch Nchar(10)

BranchName Nchar(10)

BranchAddress Nchar(10)

PINCode Nchar(10)

Phone Nchar(10)

Email Nchar(10)

Website Nchar(10)

Picture Nchar(10)

Enabled Nchar(10)

4.8.5 Distance Fee

IDDistanceFee Nchar(10)

DistanceType Nchar(10)

Description Nchar(100)

Fee Nchar(10)

24



Enabled Nchar(10)

4.8.6 News

IDNews Nchar(10)

Title Nchar(20)

ComposeDate Nchar(20)


Content Nchar(100)

4.8.7 PINCode

PINCode Nchar(10)

City Nchar(10)

Enabled Nchar(10)

4.8.8 Service

IDService Nchar(10)

ServiceName Nchar(30)

25




Fee Nchar(10)

Enabled Nchar(10)

4.8.9 WeightFee

IDWeightFee Nchar(10)

WeightType Nchar(20)


Fee Nchar(10)

Enabled Nchar(10)

5.1 Screen Shots of Web Pages (Results)

26



5.1.1 Home Page (Home.aspx)

It will display the home page of the TARS Delivery System, which will carry the information

regarding that the Online Post Office Management System.

5.1.2 Postal Rates (PosRates.aspx)

27



This page shows the Postal Rates for the delivery of the mails based on the type of the service

preferred, weight of the mail and as well based on the distance.

5.1.3 Postal Services (PosServices.aspx)

28



This page displays the various types services like Mail Delivery, Normal Post, Speed Post, VPP,

ems and money orders etc…. which is providing by the TARS Delivery System which is having a

different branches at different cities.

29



5.1.4 Postal Network (PssNetwork.aspx)

This page displays the List of branches in TARS Delivery System. Here if the user choose any

city it will display the different branches and Pin code following the particular city or Province

name, which the user have chosen.

30



5.1.5 Introduction(Introduction.aspx)

This page gives the introduction regarding TARS Delivery System.

31



5.1.6 News (News.aspx)

This page consists of News regarding the TARS Delivery System.

32



5.1.7 FAQs (Faqs.aspx)

This page is for TARS Web Shipping Frequently Asked Questions.

33



5.1.8 Contact Us (ContactUs.aspx)

In this page the user or customer can contact to the Organization head.

34



5.1.9 Site Map (SiteMap.aspx)

In this page the user can moves or navigate to different pages from the current page.

35



5.1.10 Login Page (Login.aspx)

The login page consists of username and password. According to the type of user login page navigates to the respective pages. Admin has full privileges Employees and Users

have partial privileges as they are using only the functions related to products and services.

5.1.11 Change Profile(AdminProfiles.aspx)

36



In this page the user/admin can change his/her Profile and also change the password after logginginto the system.

37



5.1.12 Manage News(AdminNews.a

This page consists of editing, adding or deleting about Postal News.

38



5.1.13 Manage Service(AdminServices.aspx)

This page consists of editing, adding or deleting about Postal Services.

39



5.1.14 Manage Fees(AdminFees.aspx)

The organization head alone decides the charges for the services and he can alone change them

(edit, delete etc)

40



5.1.15 Manage Branches(AdminBranches.aspx)

In this page the admin can edit the details about the different branches.

41



5.1.16 Manage Employee (AdminEmployees.aspx)

In this page shows the details about the employees based on different branches.

42



5.1.17 Details Of Customers (EmpCustomers.aspx)

This page provides the details of customers and the admin can add a new employee to the

organization by giving the default password 123456.

43



5.1.18 Manage Pin Codes(EmpPinCodes.aspx)

In this page the admin can edit details about the Pin Code and also he can add a new Pin Code.

44



5.1.19 View Services & Rates (EmpServicesRates.aspx)

In this page the user can get the information about Postal Services and Postal Rates.

45



5.1.20 Edit Delivery Details (EmpEditDelivery.aspx)

In this page the user can get the details about the deliveries which have been sent depending on the

various services of the organization.

46



5.1.21 New Delivery Details (EmpNewDelivery.aspx)

In this page the employee can create a new delivery.

47



5.2 Discussions

5.2.1 Liability Disclaimer

The information contained in this Web Site has been prepared solely for the purpose of providing

information about Department of Posts .This Web Site has been compiled in good faith by

Department of Posts , but no representation is made or warranty given (either express or implied)

as to the completeness or accuracy of the information it contains. You are therefore requested to

verify this information before you act upon it by calling the concerned Post office. By accessing

this Web Site, you agree that Department will not be liable for any direct or indirect loss arising

from the use of the information and the material contained in this Web Site. The copyright in the

material contained in this Web Site belongs to and remains solely with Department.

5.2.2 Hyper linking Policy

We do not object to you linking directly to the information that is hosted on our site and no prior

permission is required for the same. However, we would like you to inform us about any links

provided to our site so that you can be informed of any changes or updations therein. Also, we do

not permit our pages to be loaded into frames on your site. Our Department’s pages must load

5.2.3 Site Security

For site security purposes and to ensure that this service remains available to all users, this

Government computer system employs commercial software programs to monitor network traffic

to identify unauthorized attempts to upload or change information, or otherwise cause damage.

48



· Except for authorized law enforcement investigations, no other attempts are made to identify

individual users or their usage habits. Raw data logs are uses for no other purposes and are

scheduled for regular deletion.

· Unauthorized attempts to upload information or change information on this service are strictly

prohibited and may be punishable under the Indian IT Act.

5.2.4 Alternate Privacy Policy Statement

As a general rule, this website does not collect Personal Information about you when you visit the

site. You can generally visit the site without revealing Personal Information, unless you choose to

provide such information.

5.2.5 Collection of Personal Information

If you are asked for any other Personal Information you will be informed how it will be used if you

choose to give it. If at any time you believe the principles referred to in this privacy statement have

not been followed, or have any other comments on these principles, please notify the webmaster

through the contact us page.

49



6.1 Conclusion

The project work titled “Online Post Office Management SystemOnline Post Office Management System” has been Designed and

developed using Visual Studio 2005 IDE version (ASP.Net) as the front end for the creation of

web page and SQL Server 2005 as backend. Many user friendly Form controls are added to make

it very user interactive application. It provides all necessary features that are available in the

currently working system. The forms and reports have been subjected to testing and have been

successful.

The web page has fulfilled all the objectives identified. The web page has been developed in an

attractive user interactive fashion. So the user with common knowledge about the computer can

handle it very easily. The webpage has produced all the reports required by the user. The webpage

has fulfilled all the objectives identified and provides an attractive user friendly interface. The

reports requested by the client had been generated and all documentation required for the operation

and maintenance of the webpage has been provided.

50



6.2 Future Scope of our Project

The project can be made more user friendly by providing a user interface for the website

maintainers to make the entries in the database. Future enhancement of the project through the user

of RMI (Remote Method Invocation) and other advanced topics to communicate with the product

vendors, to facilitate a complete transaction right from the client’s request to the delivery of the

models. Using the services available for online transaction can enhance the project. By using such

systems, the middleware can find out the credit card account status from suitable service providers.

FUTURE ENHANCEMENT:

• More flexible translations can be done.

• Most extent possible flexibility is provided for easy interfacing, understanding and future

modifications.

• Other enhancements may be done based on the technological changes.

BIBLIOGRAPHY

51



Books:

1. Herb Schildt , “C# 3.5 Complete Reference Book”

2. Mac Donald, Matthew, “ASP .Net 3.5 Complete Reference Book”

3. Steven Holzner , “VB.Net BlackBook”

4. Mike Gunderloy, Joseph L. Jorden, David W. Tschanz, “Mastering SQL Server 2005”

Website:

http://www.startvbdotnet.com

http://www.w3schools.com

http://www.microsoft.com

http://www.microsoft.com

http://www.startvbdotnet.com/

http://www.startvbdotnet.com/