Beruflich Dokumente
Kultur Dokumente
PROJECT REPORT
ON
COURIER SERVICES
SUBMITTED IN THE PARTIAL FULFILLMENT OF THE
REQUIREMENT FOR THE AWARD OF THE DEGREE
OF
BACHELOR OF COMPUTER APPLICATION
(2003-2006)
INSTITUTE OF MANAGEMENT
STUDIES
C-238, BULANDSHAHAR G.T. ROAD, LAL QUAN, P.B.
NO. 57,
GHAZIABAD-201009
ACKNOWLEDGMENT
I am also thank to Miss Taru Varshney ( Project Guide BCA) for her guided
us in this project idea.
DHANANJAI SINGH
BCA-VI SEM.
INDEX
1. ACKNOWLEDGEMENT
2. CERTIFICATE OF ORIGINALITY
3. INTRODUCTION
4. HARDWARE REQUIREMENT
5. SOFWARE REQUIREMENT
9. BIBLIOGRAPHY
Introduction
INTRODUCTION
PURPOSE :
The project on Intranet Module shall be a useful product for managing the courier
services within a organization. It facilitates the users to send the couriers to other person
and to receive from others.
SCOPE:
This project provides the facility to all users to send and receive the courier. They can also
update and delete the courier, and also get the information of the status of the courier.
DOCUMENT CONVENTIONS:
The conventions shall be used to design the system are given below in the
following table so that the user can easily understand the system -
Abbreviation Meaning
D.I.M. Development of
the Intranet
Module
S/W Software
H/W Hardware
The rest of the document have very less number of abbreviation and
easy to understand as it is written in simple English language. The
document contain mainly description of product ,hardware
requirement system requirement etc . S/W requirement and hardware
requirement is mainly meant for Mr. Manish ( Lab Incharge ).
Description of features of system is mainly meant for Prof. Nishit
Goel and our team members.
PROJECT SCOPE :-
The scope of project shall be describe in following points:
1) BENEFITS :-
The main benefit of this project is that it facilitate user to communicate in a
faster manner in comparison of manual system. Through this system
the current status of the courier can be known easily whereas in
manual system it is a difficult task.
2) OBJECTIVE :-
To provide quick service without any delay.
REFERENCES :-
• Mastering in VB
• Oracle Developer Guide by Ivan Bayross
• Visual Basic 6 in 21 Days by Greg Perry
System Features
3. System Features
3.1 Administrator
3.2 Working
3.3 Dispatching
3.4 Enquiry
3.1 Administrator : -
This department have all right to provide or restrict to any department or employee to the
functionality of the project.
Here, our the user interface of the proposed system shall be VB forms
containing Menu bars, Buttons, Keyboard Shortcuts, Check boxes, List boxes etc.
according to the requirement. User can use Mouse to click the button or choose
from the menu and Keyboard to enter the data.
This software product shall be run properly on IBM PC or any other PC the
minimum hardware requirement for this software product shall be 64 MB RAM, 10
GB or more secondary memory, CD ROM for installation of this product. This
software product shall use WINDOW 98 operating system for establish the
interface between software and hardware. The interfaces provided by the Windows
OS are sufficient. Oracle and VB also use same interfaces.
The performance requirements of this product shall be not very critical. The system
shall be perform efficiently at 64 MB RAM. The product could run also at 32 MB
RAM but to perform well it is necessary to require the above specified quantity of
RAM.
Our product is absolutely safe to use. Its usage won’t provide any damage or any
type of loss to the systems already in use. Also the security model is prepared
regarding the safety of Database so that data is not lost in case of any damage to
the system.
5.3.Security Requirements
Security of the system shall definitely be maintained through the password system.
The system is devided in the four security module concern. These are administrator,
enquiry department, working department, dispatching department. Each and every
employee of every department will be authenticated with a login id and password.
Any employee can not change the system date to make proxy presentation of
yourself.
Availability: -- since this product shall use the S/W which are easily available and
runs under very nominal conditions.
Portability: -- this product shall perfectly portable since it shall easy to install this
product normally on any systems with minimum hardware and software
requirements.
Reusability: -- this product shall not for just single time useable. User shall reuse
this product many time as he or she wants.
Till this time, any further requirement is not visible. If in case, the need arises, that’ll
be specified afterwards.
Appendix A: Glossary
As this is just a single project and the terms and language used in this project are
easy to interpret, and the abbreviations have already been described . The need
of building a separate Glossary is not viewed.
The pending decision is about User Documentation that in what form the help shall
be provided with the proposed system. It may require use of HTML pages if on-line
help is to be provided and this’ll not take any special requirements hence, could be
easily implemented if decided to do so.
Design
Database Design
Enter
Login Validate for
login &
emp_login
Administrator password
And
Password
add Employee C_emp
Attendence
sheet attendence
Administrator
Update calculation
calculation table
Courier Courier_details
Informatio
n
New Courier
Update
Entry Delete
Courier
Courier
Update Courier
Courier Information
Courier_details
Courier_details
Enter Login
Validate Login &
Enquiry
Department emp_login
& Password Password
About
About Courier
About Charges
Employee
The System Development Life Cycle (SDLC), was developed because, historically,
many computer system were being delivered which did not satisfy user requirements, and
because those few projects that did satisfy user requirement were being developed over –
budget or over time. The SDLC is a methodology that has been constructed to ensure that
systems are designed and implemented in a methodical, logical and step-by-step
approach. there are seven steps, known as phases, in the SDLC :
• The Preliminary Investigation Phase
• The Analysis Phase
• The Design Phase
• The Development Phase
• The Implementation phase
• The Maintenance Phase
• Post Implementation Evaluation and Maintenance
The waterfall model represents the first significant attempts at formalizing the software
development process and as such is probably the most widely known of the life-cycle
models. This model is linear and original, and makes the questionable assumption that
each development phase can be completed largely in isolation. This has been recognized
to a certain extent in later variant of the waterfall model that shows a limited form of
iteration between stages, but essentially retains their strict chronology. Because of it’s
heavy reliance on elaborate documentation as completion criteria, the waterfall model is
suitable for tightly specified systems such as compilers or operating system but breaks
down when applied to highly interactive projects such as graphical end user applications.
The spiral model represents a considerable evolution of the waterfall model by offering
a risk driven approach that emphasizes the activities of prototyping and the evaluation of
alternatives against initial hypotheses. This model also recognizes the applicability of
existing development model to particular tasks and as such can accommodate them as
special cases of the spiral model. the spiral model considers the development process as a
number of successive progressions through each of the model’s stages, each time at a
greater level of elaboration, thus providing an incremental approach to both software
development and maintenance. This approach is graphically represented as a continuous
spiral traversal through each of the model’s stages. Another advantages over the waterfall
model is that depending on specific project objectives and constraints, and the outcome of
the risk analysis phase, different development approaches or particular combinations will
prove to be more suitable than others. Thus for any given application, not all of the
model’s stages will be equally important, followed in the same sequence, or iterated
through the same number of times. However, despite the fact that it represents a
significant improvement over the waterfall model, the spiral model does not adequately
address the sufficient emphasis on the problem domain or the behavioral aspects of
system development.
To understand the structure and working of the SDLC, we’ll examine each phase in turn.
Design
The exceptional (or foolish) programmer might begin coding without a good design.
Programmers who do so may find themselves going back to modify piece of code they’ve
already written as they move through the project with a good design, the likelihood of
this happening will be reduced dramatically. The end result is a program that will have in
the way it was intended, and will generally have with the shorter overall program
development time. Design in the SDLC encompasses many different elements. Here is a
list of the different components that are ‘designed’ in the phase : G input G output G
Processing H Files by the end of the design phase, we would hope to hope to have a
format requirements statement for the program, and a rough sketch of what the user
interface will look like.
Most programs are designed by the output of the program. The reasoning here is that if
you know what the output of the program should be, you can determine the input needed
to produce that output more easily. Once you know both the output from, and the input to
the program, you can then determine what processing needs to be performed to convert
the input to output. You will also be in a position to consider what information needs to
be saved, and in what sort of file. While doing the output and input design, more
information will be available to add to the requirement statement. It also possible that a
first screen design will take shape and at the end of these designs, and a sketch will be
made of what the screen will like. At this stage of the SDLC it isn’t necessary to discuss
the ‘how’ of what the program will do, just to get the requirement down on paper.
Development
The Development Phase is in many ways the most exciting time of the SDLC. During
this phase, computer hardware is purchased and the software is developed. That means
that we actually start coding the program. In the development phase, examination and
reexamination of the requirement statement is needed to ensure that it is being followed
to the letter. Any deviations would usually have to be approved either by the project
leader or by the customer. The development phase can be split into two sections, that of
Prototyping and Production ready Application Creation. Protyping is the stage of the
development phase that produces a pseudo-complete application, which for all intents and
purpose appears to be a fully functional. Developers use this stage to demo the
application to the customer as another check that the final software solution answers the
problem posed. When they are given the OK from the customer, the final version code is
written into this shell to complete this phase.
Implementation
In the implementation phase, the project reaches fruition. After the development phase of
the SDLC is complete, the system is implemented. Any hardware that has been purchased
will be delivered and installed. Software, which was designed in phase 3, and
programmed in phase 4 of the SDLC, will be installed on any PCs that require it. Any
persons that will be using the program will also be trained during this phase of the SDLC.
The system development life cycle during the implementation phase, both the hardware
and the software is tested. Although the programmer will find fix many problems, almost
invariably, the user will uncover problems that the developer ha been unable to simulate.
This leads on the sixth and final stage.
Audit and Maintenance
Phase 6 of the SDLC is the Audit and Maintenance Phase. In this phase someone (usually
the client, but sometimes a third party such as an auditor) studies the implemented system
to ensure that it actually fulfills the requirement statement. Most important, the system
should have solved the problems or deficiency, or satisfied the desire that was identified
in phase 1 of the SDLC – the preliminary investigation. More than a few programs and
systems have been fully developed that, for one reason or another, simply never met the
original requirements. The maintenance portion of this phase deals with any changes that
need to be made to the system. Changes are sometime the result of the system not
completely fulfilling its original requirements, but they could also be the result of
customer satisfaction. Sometimes the customer is so happy with what they have got that
they want more. Changes can also be forced upon the system because
Form
and
Coding
Dim objconn As ADODB.Connection
Dim objrs As Recordset
Dim date_value As Variant
Private Sub Form_Load()
Set objconn = New ADODB.Connection
With objconn
.Provider = "msdaora"
.ConnectionString = "user id=scott;password=tiger"
.Open
End With
On Error GoTo error_lable
Set objrs = New ADODB.Recordset
objrs.Open "select * from attendece", objconn, adOpenDynamic,
adLockOptimistic
Exit Sub
error_lable:
MsgBox " Not a correct login name ", 0, "alert"
error_lable:
MsgBox " Not a correct login name ", 0, "alert"
error_lable:
MsgBox " Not a correct LOGIN NAME ", 0, "alert"
'above is database connectivity
End Sub
'error_lable:
' MsgBox " SYSTEM PROBLEM CONTACT ADMINISTRATOR
& MAKE DATE UPDATE ", 0, "alert"
'above is database connectivity
End Sub
Private Sub attach_textfields_to_emplogin_tablefields()
Set objrs = New ADODB.Recordset
objrs.Open "select * from emp_login " & " where login_name = " & "'" &
T_LOGIN_NAME.Text & "' ", objconn, adOpenDynamic,
adLockOptimistic
Text9.Text = objrs("designation")
Text8.Text = objrs("login_password")
Text5.Text = objrs("standby_password")
On Error GoTo err_alias
Text7.Text = objrs("alias_name")
Text6.Text = objrs("alias_password")
Exit Sub
err_alias:
MsgBox "ALIAS FOR USER DOESN'T EXIST", vbOKOnly
Text7.Text = ""
Text6.Text = ""
End Sub
Private Sub attach_textfields_to_empdetails_tablefields()
Set objrs1 = New ADODB.Recordset
objrs1.Open "select * from c_emp,emp_login where c_emp.emp_id =
emp_login.emp_id and emp_login.login_name = " & "'" &
T_LOGIN_NAME.Text & "' ", objconn, adOpenDynamic,
adLockOptimistic
Text4.Text = objrs1("emp_name")
Text11.Text = objrs1("emp_address")
Text10.Text = objrs1("emp_phone")
End Sub
Private Sub attach_textfields_to_empattendence_tablefields()
Set objrs2 = New ADODB.Recordset
objrs2.Open "select attendece.present from attendece,emp_login where
attendece.login_name = emp_login.emp_id and emp_login.login_name = "
& "'" & T_LOGIN_NAME.Text & "'", objconn, adOpenDynamic,
adLockOptimistic
'Text2.Text = objrs2("")
'Text3.Text = objrs2("")
End Sub
Private Sub Form_Load()
L_DATE.Caption = Format$(Now, "d - mmm - yy")
End Sub
Dim WithEvents adoPrimaryRS As Recordset
Dim mbChangedByCode As Boolean
Dim mvBookMark As Variant
Dim mbEditFlag As Boolean
Dim mbAddNewFlag As Boolean
Dim mbDataChanged As Boolean
mbDataChanged = False
End Sub
Private Sub Form_Resize()
On Error Resume Next
'This will resize the grid when the form is resized
grdDataGrid.Height = Me.ScaleHeight - 30 - picButtons.Height -
picStatBox.Height
lblStatus.Width = Me.Width - 1500
cmdNext.Left = lblStatus.Width + 700
cmdLast.Left = cmdNext.Left + 340
End Sub
GoPrevError:
MsgBox Err.Description
End Sub
mbDataChanged = False
End Sub
adoPrimaryRS.MoveFirst
mbDataChanged = False
Exit Sub
GoFirstError:
MsgBox Err.Description
End Sub
adoPrimaryRS.MoveLast
mbDataChanged = False
Exit Sub
GoLastError:
MsgBox Err.Description
End Sub
GoPrevError:
MsgBox Err.Description
End Sub
End Sub
'error_lable:
End Sub
Dim reply As Variant
Dim objconn As ADODB.Connection
Dim WithEvents objrs As Recordset
'error_lable:
' MsgBox " Not a correct EMPLOYEE ID ", 0, "alert"
'above is database connectivity
End Sub
End Sub
End With
On Error GoTo error_lable
Set objrs1 = New ADODB.Recordset
If o_ady_emp.Value = False Then ' not going to check attendence for
administrator
objrs1.Open "select * from attendece " & " where login_name = " & "'"
& T_login_name.Text & "'" & "and" & " a_date = " & "'" & date_value &
"'", objconn, adOpenDynamic, adLockOptimistic
End If
l_attendence = objrs1("present")
If o_ady_emp.Value = True Then
l_attendence = "yes" ' for administrator
End If
Exit Sub
error_lable:
If o_ady_emp.Value = True Then
l_attendence = "yes" ' for administrator
Else
MsgBox " CHECK WITH ADMINISTRATOR FOR UR
ATTENDENCE OR UR SYSTEM DATE IS NOT CORRECT", 0, "alert"
End If
End Sub
Dim objconn As ADODB.Connection
Dim WithEvents objrs As Recordset
End Sub
Private Sub C_DELETE_Click()
If O_DELETE_COURIER.Visible = True Then
reply = MsgBox("ARE YOU SURE YOU WANT TO DELETE???", 1,
"COFIRMING YOUR DELETE")
End If
MsgBox "Enter Amount less than 1000", vbOKOnly
End If
On Error GoTo AddErr
commandstring = "insert into courier_details values ( " & "'" &
t_courier_id.Text & "'" & "," & "'" & Text2.Text & "'" & "," & "'" &
Text3.Text & "'" & "," & "'" & Text4.Text & "'" & "," & "'" & Text5.Text &
"'" & "," & "'" & Text6.Text & "'" & "," & "'" & Text7.Text & "'" & "," & "'"
& Text8.Text & "'" & "," & "'" & Text9.Text & "'" & "," & "'" &
Text10.Text & "'" & "," & "'" & 1 & "'" & ")"
With objconn
.Execute (commandstring)
End With
Exit Sub
AddErr:
MsgBox "EITHER not a unique courier_id OR data is invalid", vbOKOnly
End Sub
error_lable:
MsgBox " No Such Destination", 0, "alert"