Inventory Management

www.kashipara.
in
CANDIDATES DECLARATION
We declare that final semester report entitled Inventory Control is our own work
conducted under the supervision of the external guide, Project Guide at .
Submitted to :
Computer epartment,
!ajkot
"nventor# Control www.kashipara.in
C$%%&G& C&!'"("C)'&
College of information technolog# www.kashipara.in *
ACKNOWLEDGEMENT
'he presented project is a result of our hum+le effort to put forward our cali+er, which
could not +e possi+le to get present shape without the facult# mem+ers, colleagues and
our guide.
(irst, We are sincerel# thankful to, irector of College, !ajkot for giving us permission
to undergo training and alwa#s looking to provide great training to students in an# case,
motivates to do something extra,ordinar#. -e provides us ver# friendl# environment in
the institute.
)t the moment of su+mitting this report, we sei.e the opportunit# to express our heartfelt
gratitude towards our esteemed guide, for this entire piece of work. 'heir guidance has
+een so su+lime as to render it possi+le for us to +uild this work with a feeling of pride.

We are also thankful to for providing me all the re/uired information.
We feel gratitude in thanking the all staff mem+ers of College of "nformation
'echnolog#, !ajkot.
!RO"ECT A#STRACT
College of information technolog# www.kashipara.in 0
-ere we have developed a project on "nventor# Control to reduce the
effort for manage a stock.
1# using our project an# customer or user can manage his stock so our
project can +e ver# help full for all the customer or user.
We have added man# forms and function which makes project user friendl#
and eas# to understand.
We have tried to add that t#pe of controls and functions which can +e easil#
understand the whole project easil# +# an# technical person.
TA#LE O$ CONTENTS
TITLE !AGE
No
CANDIDATE DECLARATION 34
CERTI$ICATE 3*
ACKNOWLEDGEMENT 30
A#STRACT 32
CONTENTS 35
% INTROD&CTION
4.4 Project 6ummar# 37
4.* Purpose 8 Goals 9 $+jectives 37
4.0 6copes 3:
4.2 'echnologies and %iterature !eview 3:
4.5 )dvantages of s#stem 3;
' !RO"ECT MANGEMENT
*.4 Project planning and scheduling 44
*.* !isk <anagement 42
*.0 &stimation 47
( !RO"ECT RE)&IREMENS ST&D*
0.4 =ser Characteristics *4
0.* Constraints **
+ S*STEM ANAL*SIS
2.4 !e/uirements of >ew 6#stem *2
2.* (easi+ilit# 6tud# *?
2.0 !e/uirements @alidation *7
2.2 ata dictionar# *:
2.5 <ain <odules of >ew 6#stem *;
2.? 6election of -ardware and 6oftware *;
, IM!LEMENTATION !LANNING AND DETAILS
5.4 "mplementation &nvironment 0*
5.* 6ecurit# (eature 0*
5.0 Coding 6tandards 0*
- SCREEN S.OTS 00
/ CONCL&SION AND DISC&SSION 23
0 #I#LIOGRA!.* 2*
% INTROD&CTION
College of information technolog# www.kashipara.in ?
4.4 !RO"ECT S&MMAR*
"nventor# Control is a ver# user friendl# project. "n this project user can easil#
understand and fill up the "nventor#. "n this project there are various t#pes of forms are
there like sell form, +u# form in which user can insert his "nventor#, >eeds 9 facilities
then upload his inventor#.
"n this project all the forms which user want to fill up its totall# eas# to understand. 6o in
an# wa# user is not distur+ed or not confuse at all, an#one can easil# fill up "nventor#.
itAs totall# user friendl#.
%' !&R!OSE
GOALS 1 O#"ECTI2ES
'he Purpose of the project is ver# clear that user can manage his inventor#
easil#.
=ser can see stock of all inventor#.
'he <ain Goal of this project is to provide an ver# faster inventor# management.
'he goal of m# project is that " want m# project totall# user friendl# project and "
hope " get success. When " make the project " kept one thing in m# that when
user can not have an accounting knowledge so there are not an# kind of
confusion are there , an# one which is technical person apart from the technical
field and non technical person +oth t#pe of person are easil# understand a+out the
fields and easil# handle it.
"t saves lots of time , now a da#s there is a fast process world an# one can work
fastl# so, this project help that people who are working in inventor# organi.ation.
6o, "nventor# Control is a esktop application made in the CB.>et. 6o with the
help of this project user can manage inventor#.
%( SCO!ES
"nventor# Control is a totall# esktop application made in CB.>et. With the help of
this project a user are manage inventor#. this process is a ver# fast process and
accurate also.
)s we know that "nventor# Control is a esktop application. 6o user which is
operate this software little knowledge of computer the# can understand easil#.
College of information technolog# www.kashipara.in :
%+ TEC.NOLOGIES AND LITERAT&RE RE2IEW O$ !AST
WORK3S*STEM
%+% TEC.NOLOG*
(ront end8 CB.>et
1ack end8 6C% 6erver *335
CLINT SIDE SCRI!TING
C4NET
CB.>&' com+ines unprecedented developer productivit# with performance, and
relia+ilit#.
Develo5er !rodu6tivity
% $le7ible L8n9u89e O5tion:
CB.>&' lets #ou leverage #our current programming language skills. =nlike classic
)6P, which supports onl# interpreted @16cript and D6cript, .>&' now supports
more than *5 .>&' languages giving #ou unprecedented flexi+ilit# in #our choice
of language.
' Ri6; Cl8:: $r8me<or=
)pplication features that used to +e hard to implement, or re/uired a 0rd,part#
component, can now +e added in just a few lines of code using the .>&'
(ramework. 'he .>&' (ramework offers over 2533 classes that encapsulate rich
functionalit# like E<%, data access, file upload, regular expressions, image
generation, performance monitoring and logging, transactions, message /ueuing,
6<'P mail, and much moreF
College of information technolog# www.kashipara.in ;
In6re8:ed Reli8bility
<emor# %eak, eadlock and Crash Protection8 .>&' automaticall# detects and
recovers from errors like deadlocks and memor# leaks to ensure #our application is
alwa#s availa+le to #our users.
%, AD2ANTAGES O$ !RO!OSED S*STEM
'his s#stem has technicall# high approach.
"t can also stop the repetition of the work.
)n# technical expert can operate the s#stem smoothl#.
"t is reall# times saving s#stem.
"t also provides the work satisfaction to the staff.
' !RO"ECT MANAGEMENT
'% !RO"ECT !LANNING 1 SC.ED&LING
'%% !ro>e6t Develo5ment A55ro86;
'o solve actual pro+lems in an industr# setting, a software development strateg# must +e
incorporated that encompasses the process, methods and tools for software engineering.
'his strateg# is often referred to as 6oftware Process <odel or 6oftware &ngineering
Paradigm. ) software process model for software engineering is chosen +ased on the
nature of project and application, the methods and tools to +e used and the controls and
delivera+les that are re/uired.
)mong them, we have chosen a ver# popular one, 'he Classical 6#stem evelopment
%ife C#cle <odel or the Waterfall <odel. 'his approach is classicall# thought of as a set
of six interrelated activities that make up the entire s#stem development life c#cle.
W8ter $8ll Model:
'his is also called Classic %ife C#cle <odel or %inear 6e/uential <odel or 6oftware
evelopment %ife C#cle <odel G6%CH. 'his model has the following activities8
4. 6#stem "nformation &ngineering and <odeling
*. 6oftware !e/uirement )nal#sis
0. 6#stem )nal#sis and esign
2. Code Generation
5. 'esting
?. <aintenance
College of information technolog# www.kashipara.in 4*
%? Sy:tem3In@orm8tion En9ineerin9 8nd Modelin9
)s software development is large process so work +egins +# esta+lishing re/uirements
for all s#stem elements and then allocating some su+set of these re/uirements to
software. 'he view of this s#stem is necessar# when software must interface with other
elements such as hardware, people and other resources. 6#stem is the ver# essential
re/uirement for the existence of software in an# entit#. "n some cases for maximum
output, the s#stem should +e re,engineered and spruced up. $nce the ideal s#stem is
designed according to re/uirement, the development team studies the software
re/uirement for the s#stem.
'? So@t<8re ReAuirement An8ly:i:
6oftware !e/uirement )nal#sis is also known as feasi+ilit# stud#. "n this re/uirement
anal#sis phase, the development team visits the customer and studies their s#stem
re/uirement. 'he# examine the need for possi+le software automation in the given
software s#stem. )fter feasi+ilit# stud#, the development team provides a document that
holds the different specific recommendations for the candidate s#stem. "t also consists of
personnel assignments, costs of the s#stem, project schedule and target dates.
'he re/uirements anal#sis and information gathering process is intensified and focused
speciall# on software. 'o understand what t#pe of the programs to +e +uilt, the s#stem
anal#st must stud# the information domain for the software as well as understand
re/uired function, +ehavior, performance and interfacing. 'he main purpose of
re/uirement anal#sis phase is to find the need and to define the pro+lem that needs to +e
solved.
(? Sy:tem An8ly:i: 8nd De:i9n
"n this face, the whole software development process, the overall software structure and
its outla# are defined. "n case of the clientsIserver processing technolog#, the num+er of
tiers re/uired for the package architecture, the data+ase design, the data structure design
etc are all defined in this phase. )fter designing part a software development model is
created. )nal#sis and esign are ver# important in the whole development c#cle
process. )n# fault in the design phase could +e ver# expensive to solve in the software
development process. "n this phase, the logical s#stem of the s#stem product is
developed.
+? Code Gener8tion
"n Code Generation phase, the design must +e decoded into a machine,reada+le form. "f
the design of software product is done in a detailed manner, code generation can +e
achieved without much complication.
,? Te:tin9
)fter code generation phase the software program testing +egins. ifferent testing
methods are availa+le to detect the +ugs that were committed during the previous phases.
) num+er of testing tools and methods are alread# availa+le for testing purpose.
6) Maintenance
6oftware will definitel# go through change once when it is delivered to the customer.
'here are large num+ers of reasons for the change. Change could happen due to some
unpredicted input values into the s#stem. "n addition to this the changes in the s#stem
directl# have an effect on the software operations. 'he software should +e implemented
to accommodate changes that could +e happen during the post development period.
2.1.2 Project Plan
Project planning includes description of project tasks, activities and functions, dependencies,
resource re/uirements and a detailed schedule. 'his activit# results in the software project
management plan for the <atrimonial Project.

S6;edule o@ !ro>e6t
)nal#sisJ* weeks
esignsJ0 Weeks
CodingJ5 Weeks
'estingJ* Weeks
BWee=C<i:e 5ro>e6t !l8nnin9?
'' RISK MANGEMENT
''% Ri:= Identi@i68tion
Te6;ni68l Ri:=:
'echnical risks threaten the /ualit# and timeliness of the software to +e produced. "f a
technical risk +ecomes a realit#, implementation ma# +ecome difficult or impossi+le.
'echnical risks identif# potential design, implementation, interface, verification, and
maintenance pro+lems.
#u:ine:: Ri:=:
1usiness risks threaten the visi+ilit# of the software to +e +uilt. 1usiness risks often
jeopardi.e the project or the product. Candidates for the top five +usiness risks are
G4H 1uilding an excellent product or s#stem that no one reall# wants.
G*H 1uilding a product that no longer fits into the overall +usiness strateg# for the
compan#
G0H 1uilding a product that the sales force doesnAt under stand how to sell
G2H %osing the support of senior management due to a change in focus or a
change in people and
G5H %osing +udgetar# or personnel commitment.
!rodu6t SiDe
!isks associated with the overall si.e of the software to +e +uilt or modified.
!ro6e:: de@inition
!isks associated with the degree to which the software process has +een defined and is
followed +# the development organi.ation.
''' Ri:= An8ly:i:
!isk 'a+le.
College of information technolog# www.kashipara.in 4?
!isks Categor# Pro+a+ilit# "mpact
eliver# deadline will +e tightened 1= 53K *
&nd,=sers resist s#stem 1= 23K 0
Customer will change re/uirements P6 :3K *
'echnolog# will not meet exceptions '& 03K 4
6taff "nexperienced 6' 03K *
%ack of training on tools & :3K 0
%ess reuse than planned P6 73K *
Categor#8 "mpact values8
1= , 1usiness impact 4 , catastrophic
P6 , Product 6i.e * , critical
'& L 'echnolog# to +e +uilt 0 , marginal
& L evelopment &nvironment 2 , negligi+le
6' L 6taff si.e and experience
"n an# software the anal#sis part is the most important part. "n risk
management the programmer or software developer can think seriousl#
a+out the risk like what kind of risks are there in the project if the risks are
solva+le or not or what is the solution or which wa# he or she can solve
the risk this the main things comes into the anal#sis part . if this part is
good means developer can anal#.e the risk so there is a no chance of risk
and if possi+l# risk is come so it is easil# solve
6o if developer or programmer can anal#.e a+out the risks related to their
project there is a no or less chance of errors and make a nice project. 6o
risk anal#sis is the good part to remove the risk or prevent #our project to
future risks.
''( Ri:= !l8nnin9
'o assist the project team in developing a strateg# for dealing with risk, an effective
strateg# must consider three issues8
!isk avoidance.
!isk <onitoring.
!isk management and contiguous planning
Ri:= Miti98tin9
<eet with current staff to determine causes for turnover
<itigate those causes that are under our control +efore the project starts.
$nce the project commences, assume turnover will occur and develop techni/ues
to ensure continuit# when people leave.
$rgani.e project teams so that information a+out each development activit# is
widel# dispersed.
efine documentation standards and esta+lish mechanisms to ensure that
documents are developed in a timel# manner.
)ssign a +ackup staff mem+er for ever# critical technologist.
Ri:= Monitorin9
General attitude of team mem+ers +ased on project pressures.
'he degree to which the team has jelled.
"nterpersonal relationships among team mem+ers.
Potential pro+lems with compensation and +enefits.
'he availa+ilit# of jo+s within the compan# and outside it.
RMMM !l8n
) risk management strateg# can +e included in the software project plan or the risk
management steps can +e organi.ed into a separate !isk <itigation, <onitoring and
<anagement Plan.
'he !<<< plan documents all work performed as part of risk anal#sis and is used
+# the project manager as part of the overall project plan.
'( ESTIMATION
'(% E@@ort E:tim8tion
'oda# software is the most expensive element of virtuall# all computer,+ased s#stems.
(or complex, custom s#stems, a large cost estimation error can make the difference
+etween profit and loss. Cost overrun can +e disastrous for the developer.
College of information technolog# www.kashipara.in 4:
'oo man# varia+les,human, technical, environmental, political,can affect the ultimate
cost of software and effort applied to develop it. -owever, software project estimation
can +e transformed from a +lack art to a series of s#stematic steps that provide estimates
with accepta+le risk.
'o achieve relia+le cost and effort estimates, a num+er of options arise8
ela# estimation until late in the project.
1ase estimates on similar projects that have alread# +een completed.
=se relativel# simpl# decomposition techni/ues to generate project cost and effort
estimates.
=se one or more empirical models for software cost and effort estimation.
T;e COCOMO Model
%ike all estimation models for software, the C$C$<$ models re/uire si.ing
information. 'hree different si.ing options are availa+le as part of the model hierarch#8
o+ject points, function points, and lines of source code.
%ike functional points, the o+ject point is indirect software that is computed using counts
of the num+er of
G4H 6creens Gat the user interfaceH,
G*H !eports,
G0H Components likel# to +e re/uired to +uild the application.
$nce complexit# is determined, the num+er of screens, reports, and components are
weighted according to 'a+le a+ove. 'he o+ject point count is then determined +#
multipl#ing the original num+er of o+ject instances +# the weighting factor in ta+le
a+ove and summing to o+tain a total o+ject point count. When component +ased
development or general software reuse is to +e applied, the percent of reuse GKreuseH is
estimated and the o+ject point count is adjusted8
College of information technolog# www.kashipara.in 4;
NO! E Bob>e6t 5oint:? F GB%HH C Ireu:e? 3 %HHJ
Where >$P is defined as new o+ject points. 'o derive an estimate of effort +ased
on the computed >$P value, a productivit# rate must +e derived. 'a+le +elow
presents the productivit# rate
!RODENO! 3 5er:onCmont;
(or different levels of developer experience and development environment
maturit#. $nce the productivit# rate has +een determined, an estimate of project
effort can +e derived as
E:tim8ted e@@ort E NO!3!ROD
College of information technolog# www.kashipara.in *3
( !RO"ECT
RE)&IREMENT ST&D*
(% &SER C.ARACTERISTICS
'he user must have +asic knowledge of the Computer. =ser must +e familiar with all
the application whose documents are used in the s#stem. 'he user must +e familiar with
these computer +ased s#stem and their operations done in the s#stem.
.ARDWARE RE)&IRMENTS
.8rd<8re Minimum ReAuirement
CP= 6peed 4 G-.
!)< 54* <1
-ard,disk 6pace *3 G1
SO$TWARE RE)&IRMENTS
So@t<8re ReAuirement
$perating 6#stem Window EP or more
"nternet &xplorer
G(ront &ndH
"& ? M
'ools @isual 6tudio *33:
6C% 6erver *335
<6.>&' (ramework 0.5
'echnolog# CB.>et
CB 6cripting %anguage
ocumentation 'ools <6 Word *337
!ational !ose
College of information technolog# www.kashipara.in **
(' CONSTRAINTS
&ver# project has to follow some constrain throughout its lifec#cle. (ollowing are the
constraints identified that must +e followed during the development of m# s#stem.
Time Con:tr8int:: 'he project should +e developed and implemented within the time
limit of two months.
!er:on8l Con:tr8int:: 'he constraints imposed +# the skills possessed +# the mem+er
for the development. " had to learn CB.>&' and then implement the s#stem.
('% Reli8bility ReAuirement:
'he s#stem should +e relia+le enough in the following areas8
"ntegrit# of data should +e maintained, re/uiring the atomicit# of transactions
%oss of data should +e minimi.ed
"ntegrit# of the s#stem should +e maintained, re/uiring a tight login securit# so
that onl# the authori.ed used is allowed to perform a transaction.
('' S8@ety 8nd Se6urity Con:ider8tion
Without log into %ogin (orm user cannot access the application.
'he data+ase is on centrali.ed server so onl# authori.ed user can use this
data+ase.
+ S*STEM ANAL*SIS
+% RE)&IREMENTS O$ NEW S*STEM
'he s#stem must +e authori.ed.
'he s#stem must +e accessi+le to account +ranch of compan#.
'he s#stem must +e a+le to store inventor#.
)dvanced 6earching facilities must +e included.
'he s#stem should +e convenient and work according to the Compan#
!e/uirements.
ReAuirement An8ly:i:
"n !e/uirement anal#sis, we met to the compan# head and project guide. We
discussed a+out their re/uirements and the pro+lems the# are facing with existing
s#stem.
$86t $indin9 Te6;niAue
uring re/uirement determination phase, the s#stem anal#st has to find out how
the current s#stem works and what is expected from a new s#stem. (or that it is
re/uired to spend considera+le time in talking with users and gathering all
relevant information on the project.
In@orm8tion Sour6e:
<ain sources of information are8
=ser of the s#stem.
ocuments used in the organi.ation.
Procedure manuals and rule+ooks, which specif# how various activities,
are carried out in the organi.ation.
@arious reports used in the organi.ation.
An8ly:i: o@ 86tu8l d8t8
'he data collected during the fact finding stud# and included in data flow and
decision anal#sis documentation are examined to determine how well the s#stem
is performing and whether it will.
<eet the organi.ationAs demand.
Reli8bility
!elia+ilit# could +e defined as an extend to which application can +e perform its
intended function with re/uired precision. "t is evaluated +# measuring the
fre/uenc# and severit# of failure and the a+ilit# to recover from failure. 'hus the
application should +e as relia+le as possi+le to overcome the failure and recover
from it.
M8int8in8bility
'he application to +e developed should +e easil# maintained and should locate
undiscovered error and fix them as soon as possi+le. (or maintenance of the
application the contact num+er of the application provider would +e given to the
end user to resolve the /ueries.
!ort8bility
Porta+ilit# means an effort to transfer the application from one hard ware andIor
software s#stem environment to another. $ur application is to +e developed in
CB.>et, so the application can +e install on various Windows Platform +ut the
.>et framework needs to +e installed.
College of information technolog# www.kashipara.in *?
E@@i6ien6y
'he application should make optimal use of s#stem resources. )lso the runtime
performance of the s#stem should +e considered.
M8inten8n6e
6oftware maintenance applies to following phases in the existing program
Change in software due to errors.
Change in software +ecause the software must +e adapted to accommodate
changes in its external environment.
Change in software when the customer re/uires functional or performance
enhancements.
+' $EASI#ILIT* ST&D*
+'% Doe: t;e :y:tem 6ontribute to t;e over8ll ob>e6tive: o@ t;e
or98niD8tionK
)s from the feasi+ilit# stud# that we carried out, we can sa# that the s#stem
contri+utes to the over all o+jectives of the organi.ation for which the s#stem is
+eing developed.
)n important outcome of the preliminar# investigation i.e. after defining the scope of
the project, the determination that the s#stem re/uested is feasi+le or not is re/uired
to done.
+'' C8n t;e :y:tem be im5lemented u:in9 t;e 6urrent te6;nolo9y 8nd
<it;in t;e 9iven 6o:t 8nd 6on:tr8int:K
'he s#stem has +een developed using the current technologies and maintaining the
given specification and the re/uirements +# the organi.ation.
(rom the stud# of &conomic (easi+ilit# we can sa# that the s#stem that has +een
developed can +e implemented with the given cost and constrains.
(rom the stud# of 'echnical (easi+ilit#, the s#stem developed can +e implemented
using the current technologies.
+'( C8n t;e :y:tem be inte9r8ted <it; ot;er :y:tem: t;8t 8re 8lre8dy
in 5l86eK
)s said earlier that this is a s#stem of managing the pre, production and post,
production process.
6o this is a s#stem that can +e used separatel#. 6o from the stud# $perational
(easi+ilit# we can sa# that it has +een developed in such wa# that it can +e integrated
with other s#stem and also with the current s#stem that is alread# in place. 1ut as
this s#stem varies with the t#pe of organi.ation so it definitel# depends on the t#pe
of organi.ation with whose s#stem the new s#stem can +e integrated.
+( RE)&IREMENTS 2ALIDATIONS
"t means that the developed software is as per re/uirement or notN 6impl# stating
whatever we are doing is right or wrong as per re/uirementsN
-ere we check each and ever# re/uirement and compare with our product and that it
satisfies the user need.
College of information technolog# www.kashipara.in *:
Cl8:: Di89r8m:
$i9ure +( Sy:tem Cl8:: Di89r8m
College of information technolog# www.kashipara.in
Inventory Control
Lo9in @orm
&:er 1 !8::<ord
Inventory In@orm8tion
:;o< inventory
S;o< :ell inventory
S;o< buy inventory
In:ert det8il:B?
&5d8te det8il:B?
Delete det8il:B?
*;
++D8t8 Di6tion8ry
ata is the ke# to the overall s#stem design and must +e structured to meet the user
re/uirement. 'he collection of structured data +uilds up data dictionar#, which is an
important tool in data flow anal#sis. 'he complete set of data definitions provides the
+asis of the data dictionar#. "t facilitates cross,referencing and assessment of the
implication of changes. &ach data item is uni/uel# identified +# its definitions +ut
referred +# different name at different ta+les.
+, MAIN MOD&LES O$ NEW S*STEM
Sy:tem Admini:tr8tion
"n this module, we have developed different functions for )dministrators. )dmin can
update or delete an# details. -e can also add, delete new items or details in data+ase
+- SELECTION O$ .ARDWARE AND SO$TWARE AND
"&STI$ICATION
C4NET 'HH0
" was often surrounded +# anti,<icrosoft stories and propaganda. -owever, when "
heard a+out .>&', " decided " wanted to know more and that the +est wa# to do that was to
learn at the source.

)s " got into the technolog# and the compan#, what " found was more than a little
surprising. 'he .>&' (ramework, the CB language, )6P.>&', and 6C% 6erver are
sophisticated and technicall# +eautiful achievements
'he platform developers made, and that the resulting s#stem helped to su+stantiall#
improve m# productivit# as a developer. " also found the <icrosoft engineering teams to +e
wonderfull# +right, creative, andLperhaps most surprising of all.
S)L :erver 'HH,
6C% 6erver *335 released in $cto+er *335, is the successor to 6C% 6erver
*333.
6C% 6erver *335 introduced O<)!6O G<ultiple )ctive !esults 6etsH, a method of
allowing usage of data+ase connections for multiple purposes.
6C% 6erver *335 introduced <@s G#namic <anagement @iewsH, which are
speciali.ed views and functions that return server state information that can +e used to
monitor the health of a server instance, diagnose pro+lems, and tune performance.
6C% 6erver *335 introduced ata+ase <irroring, +ut it was not full# supported until
the first 6ervice Pack release G6P4H. "n the initial release G!'<H of 6C% 6erver *335,
data+ase mirroring was availa+le, +ut unsupported. "n order to implement data+ase
mirroring in the !'< version, #ou had to appl# trace flag 4233 at startup. ata+ase
mirroring is a high availa+ilit# option that provides redundanc# and failover
capa+ilities at the data+ase level. (ailover can +e performed manuall# or can +e
configured for automatic failover. )utomatic failover re/uires a witness partner and an
operating mode of s#nchronous Galso known as high,safet# or full safet#H.
'he main unit of data storage is a data+ase, which is a collection of ta+les with t#ped
columns. 6C% 6erver supports different data t#pes, including primar# t#pes such as
"nteger, (loat, ecimal, Char Gincluding character stringsH, @archar Gvaria+le length
character stringsH, +inar# Gfor unstructured +lo+s of dataH, 'ext Gfor textual dataH
among others. 'he rounding of floats to integers uses either 6#mmetric )rithmetic
!ounding or 6#mmetric !ound own G(ixH depending on arguments.
<icrosoft 6C% 6erver also allows user,defined composite t#pes G='sH to +e defined
and used. "t also makes server statistics availa+le as virtual ta+les and views Gcalled
#namic <anagement @iews or <@sH. "n addition to ta+les, a data+ase can also
contain other o+jects including views, stored procedures, indexes and constraints,
along with a transaction log. ) 6C% 6erver data+ase can contain a maximum of *04
o+jects, and can span multiple $6,level files with a maximum file si.e of **3 '1. 'he
data in the data+ase are stored in primar# data files with an extension .mdf. 6econdar#
data files, identified with a .ndf extension, are used to store optional metadata. %og
files are identified with the .ldf extension.
+-% .8rd<8re
'he hardware selected for development for this project is given +elow8
C$!& * uo processor
4 G1 !)<
:3 G1 -ard isk
, IM!LEMENTATION
,% IM!LEMENTATION EN2IRONMENT
1# appl#ing the implementations and a+ove anal#sis we have created We+ )pplications
in )sp.net and 6C% data+ase. 'hat is ver# to operate.
'he interrelated data+ase of 6C% server *335 is connected to )sp.net.

,' SEC&RIT* $EAT&RE
"nventor# Control is developed in CB.>&' and the +ackend is 6C% 6erver *335
data+ase which provides maximum securit#. 6ecurit# is a ke# feature of 6C%
6erver *335, which provides confidentialit#, integrit#, and availa+ilit# of
mission,critical data.
=ser authentication feature in "nventor# Control provides authentication so that
an# unauthori.ed user can not use this application.
,( CODING STANDARDS
Code conventions are important to programmers for a num+er of reasons8
?3K of the lifetime cost of a piece of software goes to maintenance
-ardl# an# software is maintained for its whole life c#cle +# original author.
Code convention improves the reada+ilit# of the software, allowing engineers to
understand new code more /uickl# and thoroughl#.
"f #ou ship #our source code as product, #ou need to make sure it is as well
packaged and clean as an# other product #ou create.
-SCREEN S.OT AND &SER MAN&AL
ELLo9in
ELAdd
College of information technolog# www.kashipara.in 0?
EL#uy
ELSell
College of information technolog# www.kashipara.in 0:
ELS;o< #uy
College of information technolog# www.kashipara.in 0;
ELS;o< Sell
College of information technolog# www.kashipara.in
/ CONCL&SION
AND DISC&SSION
24
CONCL&SION
'his esktop application provides eas# wa# to manage "nventor#. 'his application
developed is designed in such a wa# that an# further enhancements can +e done with
ease.
'his application is going to +e used for our compan# to easil# manage document. 6o,
we are ver# happ# to develop this desktop application as it provides all the re/uirements
of our compan#.
#iblio9r85;y
#OOKS :
!ro9r8mmin9 in C4 8 5rimer
#y: & 1alagurusam#
!ubli68tion: 'ata <cGraw -ill
So@t<8re En9ineerin9
#y: 6ommerville
!ubli68tion: %ow Price &dition
MyS)L Server 'HH,BeCboo=?
#y: Pen -enderson
!ubli68tion: )ddison,Wesel# Professional
WE# RE$ERENCES:
<<<@uturi:mte6;nolo9ie:6om
<<<6ode5ro>e6t6om
<<<en<i=i5edi8or9
<<<9oo9le6om

Inventory Management

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Inventory Management

Încărcat de

Drepturi de autor:

Formate disponibile

www.kashipara.

S-ar putea să vă placă și