IT Project Documentation - Example

DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
1. Introduction
Our team consists of two members, namely Mr. Your Nameand Mr. Your
partners name - if any. Apart from being great friends we are great at work to,
we understood each other well, a parameter on which our team was
formulated.
We followed the professional approach of democratic decentralized and

agreed on informal interpersonal medium of communication.
We consider our self lucky ones to get such a challenging project for our
graduation. Ramlord Apparels and intermediates a textile manufacturing and
export company and [Company Name] a company in IT business offered us
this opportunity.
Ramlord Apparels, which needed a quick, easy and customized computerized

solution which can control the functioning of the sister concern company
[Company Name].
Since their system was not computerized, they had to manually control all the
functioning of the company [Company Name]. This involved a lot of problems
like it was time consuming, involved a lot of man power and included the risk
of human error.
Software started taking its shape, not on papers or compilers but in our minds.
We intensified our work by thoroughly studying company’s process, current
system, proposed a system, its effects on company, etc.
1
One primary concern of the company was to implement new system without
much hassle. So we thoroughly studied its current working and proposed new
system on it. Our aim was not to drastically change company’s work processes
but to enhance it with computers overcoming all the current limitations, so
employees could digest new system with ease.
Next, was to name our new software package. We traversed through many
different names and finally stalled at “[Project/Software System Name
Name]”.
Since our software project was not like any other normal inventory tracking
project, we had to study the details of both the companies for which we had to
work. Establishing the communication process with both the companies in our
software application suite was hardest of all and off course most challenging.
We sighed with relief, once we were able to develop the exact relation
between the companies and understand the working of both the companies
which was very essential for the software application suite to perform
efficiently, with immediate effect.
Now our software designing skills were on test since top level officials at
Ramlord Apparels wanted its software interface to be simple and easy to
understand. Designing software’s interface according to company
requirements was done.
Final milestone of our project was when we successfully developed

[Project/Software System Name Name] incorporating all company
requirements and fulfilling all promises made when we had initially proposed
the system.
2
Next, obvious phase was to implement this software package with extensive
end-user training. The top level management, the actual user who are going to
use this software were educated with software’s scope, benefits, shortcomings
at their specific timings.
Our hard work was rewarded by company’s CLASS A certification. We thank

all people, companies directly or indirectly involved in this projects success.
2. Synopsis
[PROJECT/SOFTWARE SYSTEM NAME NAME]

(MCS)
The following is a synopsis for the proposed software application suite which
is supposed to be developed by Your NameIT04003 and Your partners name -
if any IT04005 as a part of their university curriculum. This software suite
will be developed in a prestigious company named RAMLORD APPARELS.
Ramloard Apparels is a company which has a business in textile industry

primarily. The company has two factories manufacturing the textile products
and an administrative office. The export is usually in gulf countries. The
company is a government recognized export house. The company also has
3
another company under its supervision [Company Name] which deals in the
hardware and software for computer systems.
The company has given us their working of [Company Name] and we

have understood their requirements and have proposed the software
application suite named [Project/Software System Name Name](MCS) for the
management of [Company Name]. The software will be developed for the top
level management of Ramlord Apparels to keep a track on the working of
[Company Name]. The software application suite is a network based
application and will have a client server interaction. The company will also be
provided with a website to enhance their business and give them new business
opportunities. The software will be developed in Visual Basic 6.0 and the
database which will be used as a back end to the software will be Microsoft
Access. The following are the modules of the proposed software:
Human Resource: which includes the details about all the employees and
options to add, delete and alter the employees and the details of the
employees. The software application suite will also deal in maintaining the
details about leave application by a particular employee. The application will
help the top level management to browse the information about each and
every single employee of the company.
Inventory which helps in keeping the track of the goods in the organization.
The inventory management provides details of the minimum required level
and the reorder level which will help the organization in smooth functioning.
It also provides for an easy data entry and retrieval operation.
Reports which will include detailed reports about inventory transactions,

consignment transactions, product below required level, sales drill down
report and list of payrolls.
Delivery orders: This maintains the details of all the delivery orders and also
has options for creating new delivery orders. This also handles the automated
invoicing facility.
4
Purchase orders: This maintains the details of all the purchase orders and also
has options for creating new purchase orders.
Accounts Receivable: which include the details about all the customers, their
credit limit and the total amount due to the organization.
Accounts Payable: This includes all the details of the suppliers of the
company and the amount due to them and also keeps a check on the due date.
Payroll: This handles the generation of all the payroll slips. The software
application suite will also check for the number of hours worked by the
employee and the overtime done by the employee. It also helps in calculating
the number of days that the employee was on leave. The payroll generated
automatically calculates the EPF and SOSCO deductions and generate the
net salary for the employee.
The website will have general information about the company and business
opportunities for their customer as well as the company .The developers of the
software application suite will add furthermore modules in the software suite
as and when required by the company.
We the undersigned, developers of this project [PROJECT/SOFTWARE

SYSTEM NAME NAME] (MCS) state that the synopsis is prepared to the best
5
of our knowledge and assure the authentication of this document to our

R.D.NATIONAL COLLEGE and the company RAMLORD APPARELS.
YOUR PARTNERS NAME - IF ANY HARDIK

BAJARIA
DEVELOPERS OF THE SOFTWARE APPLICATION SUITE

[PROJECT/SOFTWARE SYSTEM NAME NAME] (MCS).
6
3. Software development life cycle
a. AN OVERVIEW
System Development Life Cycle (SDLC) is the overall process of developing

information systems through a multi-step process from investigation of initial
requirements through analysis, design, implementation and maintenance.
There are many different models
• Waterfall,
• Fountain,
• Spiral,
• Build and fix,
• Rapid prototyping,
• Incremental, and
7
b. WATERFALL MODEL: OUR CHOICE
The Waterfall Model is the earliest method of structured system development.

Although it has come under attack in recent years for being too rigid and
unrealistic when it comes to quickly meeting customer's needs, the Waterfall
Model is still widely used. It is attributed with providing the theoretical basis
for other Process Models, because it most closely resembles a "generic" model
for software development.
The Waterfall Model consists of the following steps:
8
• Feasibility Study: It refers to the consideration of all aspects of the

targeted business function or process, with the goals of determining
how each of those aspects relates with one another, and which aspects
will be incorporated into the system.
• Systems Analysis: This step refers to the gathering of system

requirements, with the goal of determining how these requirements will
be accommodated in the system. Extensive communication between the
customer and the developer is essential.
• System Design: Once the requirements have been collected and

analyzed, it is necessary to identify in detail how the system will be
constructed to perform necessary tasks. More specifically, the System
Design phase is focused on the data requirements (what information
will be processed in the system?), the software construction (how will
the application be constructed?), and the interface construction (what
will the system look like? What standards will be followed?).
• Coding: Also known as programming, this step involves the creation of

the system software. Requirements and systems specifications from the
System Design step are translated into machine readable computer
code.
• Implementation: It includes deploying the software at the company. A

detailed information plan should be drawn as to what, when and how to
9
implement. Implementation also involves thorough end-user training to

enable them to adapt in a change in operating environment. Training
ensures that these changes are digested by the end-user positively.
The main reason why we opted for this model is because a good progress
tracking can be kept due to its clear development stages.
10
3.1 Feasibility study
This is first phase of software development life cycle. It was the starting point
of the project where we had to thoroughly study present system and its
limitations. In this phase, we had to identify the real problem and had to
define it in user understandable term.
The overview of this phase can be summarized as follows.
3.1.1 UNDERSTANDING THE REQUIREMENTS
The proposed software application suite was to be developed for the top level
management of Ramlord Apparels to help them get the just in time
information of the sister concerned company [Company Name]. The
management of Ramlord apparels required only limited information such as
accounts receivable, accounts payable, inventory control, payroll and crystal
reports which will help them know the current position of the company. This
software application suite required that it provide real time information to the
top level management, so we the developers had to maintain a very good
database to avoid repetition and redundancy of data. The system required
accuracy of data that will be fed into the system.
11
3.1.2 CURRENT SYSTEM
The working of the system begins at the start of each process i.e. each
transaction in the company [Company Name]. The transactions taking place in
the company [Company Name] were not available to the top level
management of the company Ramlord apparels. The only data available to
them was reports which were not sufficient for them. This situation made the
officials demand for accounts and inventory registers from the company
[Company Name]. To meet this demand was a hectic task for the employees
and officials at [Company Name]. This also resulted in lot of manual work
and caused human errors. It also resulted in waste of the very precious time.
There is a department in charge for making note of the transactions. The
departments primary work is to make note of the transactions and enter it into
register/ledgers.
While keeping note of the transactions the data from all the department of the
company [Company Name] has to be coming in to them in real time.
Suppose for example, the person in charge for this job has to record the
transactions every day for the company [Company Name] which is to be
presented to the top level officials of the company Ramlord apparels, he has
to undergo the following steps:
• Synchronize the transactions which he will be referring.
• Start entering the transactions in the journal/registers/ledgers.
• Select a format in which it has to be presented.
12
• As soon as the format is selected get it approved with the management

of Ramlord Apparels.
• Repeats step no. 2 and 3 till the journal/register/ledger is submitted for

scrutinity.
• Re-enters all the transactions into another register for storing purpose.
• Optionally, for important transactions will have to enter these

transactions into MS Excel sheets.
• Optionally, for important reports will have to plot graphs of the

recorded transactions.
Tow copies of records are maintained, one to submit it to the management at

Ramlord apparels and the other for storing purpose for long time requirement.
At some offices after a financial year has been completed the transactions are
entered in MS Excel manually in order to maintain their records on electronic
medium.
The current system at [Company Name] and Ramlord apparels is among one
of the traditional and manual ones.
13
3.1.3 IDENTIFING “THE REAL PROBLEM”
As the current domain is manually driven, they have many limitations:
• While the department in charge records transactions of one department

in the company at a time it tends to skip transactions of other
departments.
• Unnecessary humane power is wasted in recording transactions, instead

can be used for some productive work.
• Retrieving transactions is tedious and time-consuming since recorded

transactions are stored manually in ledgers.
• Even by using MS Excel, the transactions are to be entered manually.
• Optionally, for important processes and reports the graphs has to be

plotted manually.
• Data transfer of recorded transactions across branch offices is a very

tedious job.
• Retrieving the information submitted for the top level management is a

very time consuming job.
14
• Detection of errors in data entry is difficult.
3.2 System analysis
By now we had studied the current system and identified the grey problematic
areas of current system. Now we had to move to the second phase of software
development life cycle i.e. system analysis.
In this phase, we had to propose a system which can overcome the limitations
faced with current system. Proper communication with the company was
established to convey our system analysis report. Once an agreement was
reached with company we defined project objectives, scope and their
advantages.
This phase can be described as follows
3.2.1 UNDERSTANDING COMPANY

REQUIREMENTS
Company was very clear in what they wanted and we had no problems in
understanding them. They required software which:
• Is a simple, easy to understand software interface.

• Enables the user to retrieve transactions in real-time from the company
[Company Name] automatically.
15
• Enables generation of reports to get the summary.

• Enables graphical view of already stored data.
• Enables backup and restore facility.
3.2.2 PROPOSED SYSTEM OBJECTIVES
Primary objective of our project was to develop and deploy such a system
which overcomes the current systems limitations. Along with overcoming of
limitations, the challenge was to develop and deploy such a system which will
foster new e-working environment within the company.
Taking into consideration the work tasks involved in current system, the new
system has been designed. The proposed working system is totally
computerized version of the present working system with many enhancements
that the present system lacked.
Our primary objectives of project include:
• Obtaining accounts and inventory control in real-time when

transactions are in progress.
• Automatic real-time report generation when transactions are in

progress.
• Storing records by default in database.
• Providing tickers to the users which acts like a notice board.
16
3.2.3 THE SCOPE OF PROPOSED SYSTEM
The proposed system caters to the needs of the company. The proposed system
is intended to be built on Microsoft Visual Basic 6.0 as the Front End and
Microsoft Access as the Back End. The Access database can be accessed
directly if necessary to view records in database format if the user is aware of
the tables in the database. This is achieved by providing a SQL console to the
users of the system.
In the proposed system we have tried to overcome every disadvantage of the

current system.
• A program capable of real time, offline data logging and report

generation for both. Which will also have extensive help and support
options.
• An interface for Real-Time Monitoring wherein we can directly view

real-time data (i.e. transactions) and simultaneously plots s for the
same.
• Another interface for monitoring the inventory controls and keeping a

check of the inventory in the company [Company Name].
• Next, an interface which can let the management of the company

Ramlord apparels view the accounts of the company [Company Name].
17
• Lastly an extensive and comprehensive help and support feature for

user simplicity, online help for updates, manuals and much more.
3.2.4 FEATURES AND ADVANTAGES OF

PROPOSED SYSTEM
• Meets ISO 9001 parameterized requirements, for company to get

certification.
• Data is in organized manner.
• Saves lots of humane power, thus money.
• As compared to register lockers a computer requires a considerably

small amount of space.
• It is very easy to store and transfer data through computer peripherals

like floppy disks etc.
• Real-Time data is logged along with real time plotting of reports.
• Already recorded data can also be viewed in the form of reports and
data.
• Data migration across all the branch offices possible.
• The storage provided by the computer is enormously larger as

compared to registers.
18
• Data accuracy is highly guaranteed in real-time situation.
3.3 System design
This is one of the most important phase of software development life cycle i.e.
system design. Independent analysis of company requirements and its system
points were understood by now. Now we had to mould these company
requirements into system design phase.
In accordance to company requirements, we decided on programming platform

(i.e. it’s front-end and back-end) on which the software is to build. For
programming, we choose Microsoft Visual Basics 6.0 (front-end) and
Microsoft Access (back-end).
In simple words, in this phase we had to design such an interface using Visual
Basics 6.0 which covers all company requirements and fulfills all aspects of
proposed solution.
This phase can be summarized as follows
19
3.3.1 CONTEXT LEVEL DIAGRAM
T e m p e r a t u r e D i s p l a y
T e m p e r a t u r e I n f o D i s p l a y P a n e l
S c a n n e r D a t a ( G r a p h )
L o g g e r
S u i t e
20
3.3.2 LEVEL 1 DFD
21
T e m p e r Ya - t b u i r t e
S c a n n e r O p e n
T e m p e r a t u r e
p o r t
D a t a L o g g e r
R e c o r d
T e m p e r a t u r e
3
D i s p l Da y i s p l a y P a n e l
G r a p h
G e n e r a t i o n
C l o s e
P o r t
3.3.3 GRAPHICAL USER INTERFACE DESIGNING
22
These are forms names designed using Visual Basics 6.0:
1. frmSplash
2. frmMain
3. frmDataLogging
4. frmTerminal
5. frmGraphs
6. frmPortSettings
7. frmHelpSupport
8. frmHelp
9. frmOnlineSupport
10. frmAbout
Each form gives us various functionalities and has different properties.

Details of every form are as listed hereby.
1. frmSplash :
23
This form gives information about the company for which software is
developed.
Object Property Setting
frmSplash Name frmSplash

Caption (blank)
cmdOk Name cmdOk

Caption OK
picLogo Name picLogo
lblLicenceTo Name lblLicenceTo

Caption License to: Ramlord
Apparels
lblProductName Name lblProductName

Caption [Project/Software
System Name Name]
(MCS)
lblCopyright Name lblCopyright
Caption Your Nameand Your
partners name - if any
lblWarning Name lblWarning

Caption For authorized user only
lblVersion Name lblVersion
Caption Version: 1.0.0
24
2. frmLogin :
This form will provide the user to enter the software application suite. This
will add security to the software application suite.
frmLogin Name frmLogin

Caption User Login
Label1 Name Label1

Caption Username :
Label2 Name Label2
Caption Password :
txtUsername Name txtUsername
txtPassword Name txtPassword

PasswordChar *
3. frmMain :
This is the Main form of our project, the first form. This will be displayed as
soon as the user logs into the software application suite.
frmMain Name frmMain

Caption [Project/Software
System Name Name]
(MCS)
frmShortcuts Name lblStartLogging

lvDeliveries Name lvDeliveries
Frame1 Name Frame1
25
4.frmCustomer_New:
This form will allow the admin to add new customer.
frmCustomer_New Name frmCustomer_New
Caption Add New customer
txtname Name txtname
cmbcountry Name cmbcountry
cmbstate Name cmbstate
cmbcity Name cmbcity
txtzip Name txtzip
txtcreditimit Name txtcreditimit
txtterm Name txtterm
txtphone Name txtphone
cmdsave Name cmdsave
26
5.frmpurchase:
This form will allow the user to make a purchase order.
6. frmpurchase_details
This form will help the user see all the purchase order. A user also edit the
frmpurchase
frmPurchase_details Name frmpurchase
FrmPurchase_details
Caption Purchase order details
Caption Purchase order
Ivdet Name Ivdet
Optcash Name
Caption Optcash
(Blank)
optcredit Name optcredit

txtdesc Name desc
cmbsupplier Name cmbsupplier
txtcust Name cust
cmbdate Name cmbdate
Txtqty Name qty
cmbemployeeId Name cmbemployeeId
Unitlabel Name Unitlabel
txtnotes Name txtnotes
txtPrice Name price
Ivcart Name Ivcart
cmdedit Name cmdedit

cmdclear Name cmdclear
cmdclose Name cmdclose
cmdremove Name cmdremove
details of the particular purchase order if needed.
27
7. frmpurchase_main
This form will help the user see all the purchase order. A user also edit the
details of the particular purchase order if needed.
frmPurchase_details
frmPurchase_Main
frmProduct_Browse Name FrmProduct_browse
FrmPurchase_details
Caption Purchase order
Inventory control
details
Ivdet
Ivinventory Name Ivinventory
Ivdet
Caption (Blank)
txtdesc
cmbfilter Name desc
cmbfilter
txtcust
lblmin Name cust
Lblmin
Txtqty
lblreorder Name qty
lblreorder
Unitlabel
Optin Name Unitlabel
optout
txtPrice
lblquantity Name price
lblquantity
cmdedit
txtquantity Name cmdedit
txtquantity
cmdclose
cmdDone Name cmdclose
cmdDone
8. frmproduct_browse
28
This form will help the user see all the products. A user also see details of the
quantity available also location, reorder etc.
frmProduct_Details Name FrmProduct_Details

Caption (blank)
Ivhistory Name Ivhistory

Caption (Blank)
txtproductID Name txtproductID
txtdescription Name txtdescription
cmbcategory Name cmbcategory
cmbbrand Name cmbbrand
txtunitprice Name txtunitprice
txtquantity Name txtquantity
Cmdedit Name cmdedit
9. frmproduct_Details
This form will help the user to see a particular product details with use of the
productdi, also it has a feture to edit the productdetails.
29
10. frmproduct_New
This form will help the user to add a new product.
frmProduct_New Name FrmProduct_New

Caption (blank)
Txtdescription Name txtdescription

Caption (Blank)
cmbBrand Name
cmbBrand
cmbcategoryID Name cmbcategoryID
txtunitPrice Name txtunitPrice
Txtminlevel Name txtminlevel
txtReorderlevel Name txtReorderlevel
Txtlocation Name txtlocation
11. frmpayroll_New
This form will gives detail information about the payroll it also has selected
option to select a particular employee
30
12. frmpayroll_Print
frmPayroll_New Name frmPayroll_New

Caption (blank)
Ivemployees Name Ivemployees

Caption (Blank)
Optpay1 Name Pay1
Optpay2 Name Pay2
Optpay3 Name Pay3
txthrs Name Txthrs
txtUpleaves Name txtUpleaves
txtAnnual Name txtAnnual
txtsick Name txtlocation
txtOthrs Name txtOthrs

This form will Prints detail information about the Each employee
31
13. frmReport_Main
This form will gives the reports of all consignment,sales,payroll listing etc.
frmPayroll_Print Name frmPayroll_print

Caption (blank)
cmdprint Name cmdPrint
Optpayroll Name allpayroll
Optonlyselected Name onlyselected
IvEmp Name IvEmp
datpk Name datpk
32
frmReport_main Name frmReport_main

Caption (blank)
lblinventory Name lblinventory
Label3 Name Salesdrill-down
Label4 Name Payroll listing
33
14. frmReport_Payroll
This form will gives the reports of payroll listing which has a select month
and year option to select a particular month and year report.
frmReport_payroll
frmReport_Sales Name frmReport_
frmReport_payroll
Caption (blank)
cmbmonth Name cmbmonth
cmbyear Name cmbyear
CmdResult Name CmdResult
Ivpayroll Name Ivpayroll
Label1 Name Select a month
Label2 Name Select a year
15. frmReport_Sales
This form will gives the reports of sales in a year which also has a select
option form which we can select a year it also has a chart feture option to it.
34
frmReport_Consignment Name frmReport_consignment

Caption (blank)
txtcustomer Name txtcustomer
txtcontractid Name txtcontractid
txtstratdate Name txtstartdate
Ivcon Name Ivcon
txtenddate Name enddate
cmdclose Name Cmdclose
16. frmReport_consignment
This form will gives the reports of detail information about the consignment
transaction.
35
frmselected Name Frmselected

Caption (blank)

Caption (Blank)
txtref Name txtref
txtprice Name txtprice
cmbunitprice Name cmbunitprice
Cmdclose Name cmdclose
17. frmselected
This form will gives the details information about the product which also has
a textbox ion which you can put a price for sale.
36
18.frmselectedforPO
frmselected Name Frmselected

Caption (blank)

Caption (Blank)
txtref Name txtref
txtprice Name txtprice
cmbunitprice Name cmbunitprice
Cmdclose Name cmdclose
This form will help you to select the purchase order using its productID it also
has the details about the product name,price,description,reference,unitprice &
quantity
37
19.frmstates.
This form will gives the detail information about the states following by its
country name.
frmstates Name Frmstates

Caption (blank)
Ivcountries Name Ivcountries

Caption (Blank)
Ivstates Name Ivstates
lblhidden Name lblhidden
txtstateID Name txtstateID
cmdadd Name Cmdadd
cmddelete Name cmddelete
cmdclose Name Cmdclose
38
20.Supplier_new:
This form will help the user to add a new by asking the details of the supplier
Like country,state,city,name etc.
21.Suppliers.
frmSupplier_new Name frmSuppliers

frmSupplier_new
Caption Add
suppliers
new supplier

Txtname
txtaddress
xtaddress Name txtaddress
Cmbcountry Name Cmbcountry
cmbstate Name cmbstate
Cmbcity Name Cmbcity
txtzip Name txtzip
txtcreditlimit Name txtcreditlimit
txtterm Name txtterm
cmdedit
cmdsave Name cmdedit
cmdsave
This form will gives the details about all the suppliers It also help the user to
make changes in the details of suppliers.
39
txtcurrentbal Name txtcurrentbal
mnuoptions Name
txtphone1 Name txtphone1
txtphone2 Name txtphone2
txtemail Name txtemail
txtfax1 Name Txtfax1
Txtfax2 Name Txtfax2
Mnupurchase order Name mnupurchaseorder
mnuaccount Name mnuaccount
List_suppliers Name List_suppliers
List_history Name List_history
22.frmtickers_new:
This form will add a new ticker in the ticker list
40

frmTickers Name frmTickers

Frmtickers_new Name
Caption Frmtickers_new
Tickers Management
Caption publictickermessage
Ivticker Name Ivticker

txttitle Name Ivemployees
txttitle Name txttitle

txtmsg Name txtmsg
txtmsg Name txtmsg

Labal3 Name Public date
cmbcreated Name cmbcreated
cmbdd
cmbuser Name
Name dd
cmbuser
Cmbmm
Cmbdd Name
Name mm
Cmbdd
cmbyyyy
Cmbmm Name
Name yyyy
Cmbmm
cmdadd Name Cmdadd

Cmbyyyy Name Cmbyyyy
cmdcancel Name cmdcancel

23.Tickers:
This form will manage all the tickers which are there in the list. User also edit
the ticker if he wants to.
41
24frmuser_Add:
This form will add a new user in the system.
frmuser_add Name frmuser_add
Caption Add new user
cmbemployeeID Name cmbemployeeID
txtusername Name txtusername
txtpassword Name txtpassword
chkstatus Name chkstatus
chkaccess Name chkaccess
25.frmuser_main:
42
This form will allows the admin to see all the users it also has features of
add,remove & properties
frmuser_main Name frmuser_main

Caption User managementconsole
Cmdadd Name Cmdadd
Cmdremove Caption Cmdremove
cmdproperties Name cmdproperties
List_users Name List_users
Optpay3 Name Pay3
26.frmuser_properties:
This form contains the properties of the user like which function should be
enable or disabled
43
frmuser_properties Name frmuser_properties
Caption Add new user
cmbemployeeID Name cmbemployeeID
txtusername Name txtusername

txtpassword Name txtpassword

frmadjustment Name frmadjustment
Caption Account adjustment
chkstatus Name chkstatus
optdebit Name debit
chkaccess Name chkaccess
optcredit Name Credit
cmdapply Name cmdapply
txtAmount Name txtAmount
cmdcancel Name Cmdcancel
cmdsave Name Cmdsave
cmddate Name cmddate
27.frmadjusment:
This form will help the user to adjust the accouts of the customers.
44
28 .frmAdmin_logging:
frmAdmin_logging Name frmAdmin_logging

Caption View logs
tvlog Name tvlog
Ivlogging Name Ivlogging

This form will allows the admin to view the logging of different employees
With date & time
45
29.frmAdmin_setings:
This form will allows the admin to do changes for employee and human
resources
frmAdmin_settings Name frmAdmin_setings
Caption (blank)
chkPrice Name Ivhistory
txtcartmax Name txtcartmax
txtsalary Name txtsalary
Txtemp Name Txtemp
txtDO Name txtDO
txtPO Name txtPO
txtprod Name txtprod
txtcompanyname Name txtcompanyname
Cmdupdateuser Name Cmdupdateuser
46
30.frmCategory_browse:
This form will allows the user to add, edit the categories of products.
frmCategory_browse Name frmCategory_browse

Caption (blank)
Ivcategory Name Ivcategory

Caption (Blank)
txtcategoryID Name txtcategoryID
cmdAdd Name cmdAdd
cmbbrand Name cmbbrand
cmdmodify Name cmdmodify
31frmConsignment_browse:
47
This form will show the consignment of the products. It also includes
quantity,reorder level and minimum amount of quantity available
frmConsignment_Browse Name frmConsignment_Browse

Caption (blank)
IvInventory Name IvInventory

Caption (Blank)
cmbfilter Name cmbfilter
lblmin Name Lblmin
lblreorder Name lblreorder
Optin Name optout
lblquantity Name lblquantity
cmdDone Name cmdDone

32.frmConsignment_main:
This form will help the user to add a new contract in the contract list. It also
has fretures to edit and delete the contracts
48
33. FrmCustomer_payment:
This form will help the user to put the amount,date,customers name &
cheque no. basically this will keep the record of customers payments
FrmCustomer_payment
frmConsignment_main Name
Name FrmCustomer_payment
frmConsignment_main
Caption
Caption (blank)
(blank)
IvDO
IvContracts Name
Name IvDO
IvContracts
Caption
Caption (Blank)
(Blank)
cmbcust
cmbcustomerID Name
Name cmbcust
cmbcustomerID
cmbdate
txtcontract Name
Name cmbdate
txtcontract
txtamt
txtstart Name
Name txtamt
txtstart
txtend Name txtend

txtchq Name txtchq
cmdnew Name cmdnew
txtowning Name owning
Cmdclose Name cmclose
Cmdcancel Name Cmdcancel
34.frmDelivery:
49
This form will help the user to make the new delivery order. It also has a
view cart facility to add a products that has to be delivered
35.frmDeliverydetails:
frmdelivery Name frmdelivry

Caption (blank)
IvCart Name IvCart

Caption (Blank)
cmbemployee Name cmbemployee
cmbdate Name cmbdate
cmbcustomerID Name cmbcustomerID
cmbdeldate Name cmbdeldate
cmbdeltime Name cmbdeltime
txtDes Name txtDes
Cmdclear Name Cmdclear
This form will gives the details about the products which has to be delivered
to the customers. It also has edit feture to edit the delivery order
50
36.frmDelivery_Main:
This form will manage all the delivery orders which has to be delivered to the
customers.it also has fetures of edit and delete th orders.
frmDelivery_Details
frmDelivery_Main Name frmDelivery_Main
frmDelivery_Details
Caption (blank)
IvDet
IvDO Name IvDO
IvDet
Caption (Blank)
txtproductID
txtDonum Name txtproductID
txtDonum
txtdescription
cmbdate Name txtdescription
cmbdate
txtref Name cmbref

cmbcustomer Name cmbcustomer
Cmbunitlabel Name Cmbunitlabel
txtPo Name txtPo
txtunitprice Name txtunitprice
txtAttn Name txtAttn
txtRemark Name txtRemark
Cmbemployee Name Cmbemployee
51
cmbdeldate Name cmbdeldate
cmbdeltime Name cmbdeltime
txtcharges Name txtcharges
txtnotes Name txtnotes
cmdnew Name cmdnew
cmddelete Name cmddelete
37.frmEmployees:
This form is having the list of all the employees .it also has feture to add,edit
and change the properties of employees
52
frmEmployees Name frmEmployees

Caption (blank)
List_Employees Name List_Employees
cmdAdd Name cmdAdd
cmdRemove Name cmdRemove
cmdproperties Name cmdProperties
38.frmemployees_New
This form will allows the administrator to add new employee in the
department
53

frmEmployees_new Name frmEmployees_new
Cmdcancel
Caption (blank)
Cmdcancel
Name
txtIc Name txtIc
txtadd Name txtadd
optgender Name optgender
cmbcountry Name cmbcountry
Cmbstate Name Cmbstate
Cmbcity Name Cmbcity
txtzip Name txtzip
Cmbposition Name Cmbposition
54
3.4 System Coding
Till now, system points were defined, programming language and resources
were discussed and also system design was confirmed with the company.
Now, in this phase we have to translate system design into computer

understandable language i.e. system coding. Since, we had decided on
Microsoft Visual Basics 6.0 we had to follow its syntactical procedures and
conventions.
55
This can be summarized as follows:
3.4.1 SPLASH SCREEN
Form Name: frmSplash

File Name: frmSplash.frm
Specifications: This form gives information about the company
for which software is developed.
Program Level Pseudo code:
1. IF clicked on OK THEN
a. The user will enter into the system.
b. The Splash form disappears and the login form of the
software application suite appears.
Screen Layout:
56
Form Code:
Place Your Code Here. Do remember to put in comments that describe your
code- it goes a long way.
Test Results:
The form is validated successful and it does not consist of any errors.
3.4.2 FORM LOGIN
Form Name: frmLogin

File Name: frmLogin.frm
Specification: It provides the user with security. It helps only authorized
user to access the data and use the software application
suite.
57
1. IF clicked on login THEN

a) Check whether the user name and password matches.
b) If yes then, the login form disappears.
c) Main screen is loaded.
Screen Layout:
58
Form Code:
Test Result:
The form is validated successful and does not consist of any errors.
3.4.3 MAIN SCREEN
Form Name: frmMain

File Name: frmMain.frm
Specification: This is the Main form of our project, the first form. This
will be displayed as soon as we enter after the login page.
1. IF clicked on New Delivery Order THEN

a. The current form will be hidden
b. The Delivery order form will appear.
2. IF clicked on Help and Support THEN
59
a. The current form will be hidden

b. The Help and Support form will appear.
3. IF clicked on Purchase Order THEN
a. The current form is hidden
b. The Purchase Order form will appear.
4. IF clicked on Colleagues THEN
b. The employees form will appear.
5. IF clicked on Inventory THEN
b. The Inventory Window appears.
6. IF clicked on any of the Menu Controls THEN
a. The Window corresponding to the control appears.
7. IF clicked on Search THEN
a. The search query as per the criteria appears and the search
operation is performed
Screen Layout:
60
61
Form Code:
Test Result:
3.4.4 CHANGE PASSWORD
Form Name: frmPassword

File Name: frmPassword.frm
Specification: This form will allow the authorized user to change their
password.
1. IF clicked on save THEN

a. Validate the old password
b. Check whether the new password matches with the re-entered
password
62
c. Update the new password in the database
Screen Layout:
Form Code:
63
Test Result:
3.4.5 ADDING A TICKER
Form Name: frmTicker_Personal

File Name: frmTicker_Personal.frm
Specification: This form will enable user to add a new personal ticker
message which will act as a notice board for the users of
the software application suite.
1. IF clicked on Add THEN

a) Validate the user input for a ticker.
64
b) Check for the publish date.

c) Update the ticker in the database.
Screen Layout:
Form Code:
Test Result:
65
3.4.6 Managing Tickers
Form Name: frmTickers

File Name: frmTickers.frm
Specification: The form has all the parameters that need to manage the
tickers which will act as a notice board for the
management. It has options to edit the current tickers and
also to delete the ones not required.
1. IF clicked on Edit THEN

a. The selected ticker will be available for edit.
66
b. The edited ticker must be saved when clicked on save.

2. IF clicked on Delete THEN
a. The selected ticker should not appear in the tickers
b. The selected ticker should be removed from the database.
Screen Layout:
Form Code:
67
Test Result:
3.4.7 Adding a new Customer
Form Name: frmCustomer_New

File Name: frmCustomer_New.frm
Specification: This form is especially dedicated for adding a new

customer in the database.
68
1. IF clicked on Save THEN

a) The input provided by the user will be validated.
b) The details of the new customer will be entered in the
database.
Screen Layout:
Form Code:
69
Test Result:
3.4.8 Customer Details
Form Name: frmCustomers

File Name: frmCustomers.frm
Specification: This form provides the user with an extensive detailed

report of the customer which helps the user in getting the
required information.
1. IF clicked on Any of the Menu Controls THEN

a. The corresponding form should appear.
a. The details of the current selected customer will be available to
edit.
b. The edited details will be stored.
Screen Layout:
70
71
Form Code:
Test Result:
3.4.9 View Delivery Orders
Form Name: frmDelivery_Main

File Name: frmDelivery_Main.frm
Specification: This form enables user to get details of the delivery orders
received till date.
1. IF clicked on Filter THEN

a. The display the delivery details of selected date only.
2. IF clicked on New THEN
72
a. The new delivery form( frmDelivery.frm) will be displayed.

b. On creating a new delivery the new delivery form will be hidden
and the delivery order form will appear.
a. The selected delivery order is available to edit.
b. The edited delivery order will be updated in the database.
a. The selected delivery order is deleted.
b. The delivery order is removed from the database.
5. IF clicked on Close THEN
a. The current form is unloaded.
b. The MDI screen appears.
Screen Layout:
73
Form Code:
Test Result:
74
3.4.10 VIEWING SUPPLIERS INFORMATION
Form Name: frmSuppliers

File Name: frmSuppliers.frm
Specification: This is the form which will help the user get a detailed
report of suppliers of the products and help in editing the information and also
in deleting the information of a supplier.
1. IF clicked on any of the Menu Controls THEN

a. The Corresponding form will be displayed.
b. On completion the flow is redirected to the suppliers form.
a. The current selected supplier details is available for edit.
b. The edited details will be updated in the database.
a. The current form is unloaded.
75
b. The MDI Screen will appear.
Screen Layout:
76
Form Code:
Test Result:
3.4.11 PURCHASE ORDER MANAGEMENT
Form Name: frmPurchases_Main

File Name: frmPurchases_Main.frm
77
Specifications: This form will help the user to get the details about
the purchases made in the company. It will also allow the user to create a
new purchase order, edit and delete a purchase order.
1. IF clicked on New THEN

a. The new Purchase order form(frmPurchase.frm) will appear.
b. On completion it will be redirected to the purchase order
management form.
a. The selected purchase order will be available to edit.
b. The edited purchase order will be updated in the database.
a. The selected purchase order will be deleted.
b. The purchase order will be removed from the database.
a. The Purchase order form will be unloaded.
b. The MDI Screen will be loaded.
Screen Layout:
78
Form Code:
Test Result:
3.4.11 HUMAN RESOURCE MANAGEMENT
79
Form Name: frmEmployees

File Name: frmEmployees.frm
Specification: This form enables user to get details of the employees and
edit the details and also provides for deleting and employee.
2. IF clicked on Add THEN

a. The form for creating a new employee
(frmEmployees_New.frm) is displayed.
b. On completion, employee form (frmEmployees.frm) is displayed.
2. IF clicked on Properties THEN
c. The new delivery form( frmDelivery.frm) will be displayed.
d. On creating a new delivery the new delivery form will be hidden
and the delivery order form will appear.
a. The selected delivery order is available to edit.
b. The edited delivery order will be updated in the database.
a. The selected delivery order is deleted.
b. The delivery order is removed from the database.
c. The current form is unloaded.
d. The MDI screen appears.
80
Screen Layout:
Form Code:
81
3.4.12 PAYROLL MANAGEMENT
Form Name: frmPayroll_New

File Name: frmPayroll_New.frm
Specification: This form enables user to create a new payroll slip for each
employee. It enables automatic calculation of EPF
contribution, Income Tax and SOSCO for each employee. It
also calculates the total amount of days the employee has
worked in the current month.
3. IF clicked on Calculate Payroll THEN

a. The user inputs are validated and all calculations are
performed and displayed.
2. IF clicked on Save THEN
a. The new Payroll generated by the system will be saved.
e. The payroll details will be updated in the database.
Screen Layout
82
Form Code:
Place Your Code Here. Do remember to put in comments that describe your code-
it goes a long way.
3.4.13 INVENTORY MANAGEMENT
Form Name: frmProduct_Browse
83
File Name: frmProduct_Browse.frm

Specifications: This form gives information about the inventory. It
also acts as list for creatin delivery orders and
purchase orders.
1. IF clicked on any of the Menu Control THEN

a. The Corresponding form will be displayed.
b. On completion the flow will be redirected to the inventory
window.
Screen Layout:
84
Form Code:
Test Results:
85
3.4.14 INVOICING
Form Name: frmInvoicing

File Name: frmInvoicing.frm
Specifications: This form provides for the automated invoicing for
the users of the software application suite.
2. IF clicked on Invoice THEN

a. The user inputs will be validated.
b. The invoice details are sent to the printer.
Screen Layout:
86
Form Code:
Test Results:
87
3.4.15 REPORT GENERATION

Form Name: frmReport_Main
File Name: frmReport_Main.frm
Specifications: This form enables the user of the software
application suite to get detailed reports for sales,
payroll, inventory transactions, consignment
transaction and products which are below the
reorder level.
3. IF clicked on any of the reports THEN

a. The main report page will be hidden.
b. The corresponding report will appear.
Screen Layout:
88
89
90
Form Code:
Inventory transaction form code

Test Results:
Consignment report form code:

Sales drill-down report form code

Payroll listing report form code:
3.4.13 STANDARD CODE MODULE
91
Module Name: BasicModules

File Name: BasicMods.bas
Module Code:
2.5 System Implementation
After rigorous and hectic coding and testing sessions this was considerable,
easy phase in our software development. By now we were on the tail of
92
Software Development Life Cycle. Here in this phase, we had to implement

the software at Ramlord Apparels.
Implementing software does not necessarily mean installing the software. It

means much more i.e. end user training. We provided comprehensive and
extensive three day end user training session to the employee of the company.
This was done so that employees can function independently irrespective of us
being there.
Implementation phase also involves a small, quick testing of the software on

the company computer machines. This is done just to verify and demonstrate
the software. Here the company was informed with the minimum Hardware
and Software prerequisites requirements for the [Project/Software System
Name Name]to function properly.
2.6 Cost Benefit analysis
93
By now, we have implemented the working module of our software –

“[PROJECT/SOFTWARE SYSTEM NAME NAME]”. Now, in this phase we
have to analyze how the software has benefited the company in terms of
finances (cost).
How our software can be a cost-saving mechanism for the company?
Here we have a hypothetical projected cost analysis sheet; for example.
• Traditionally to record transactions company hired un-skilled staff but

with limited computer functionalities to do this job. The department in
charge was responsible to record transactions and enter into log
book/registers.
• Department in charge was awarded with salary of Rs. 4,00,000 +

Bonuses.
• Now, with the new system implemented the company can save upto
more than 100% on humane power cost i.e. no dedicated staff is
required to do this job.
This can be summarized as follows:
94
OLD SYSTEM NEW SYSTEM

Entities: Entities:
• Person in charge • Computer

• Computer • Stationary
• Stationary (Log books/registers)
Cost: Cost:
• Person in charge : 4,00,000 (salary) • Electricity: 8000 p.a.

40,000 (bonus)
-------------------- • Stationary: 2000 p.a.
4,40,000
• Maintenance: 1500 p.a.
• Electricity: 2500 p.a.
• Maintenance: 1500 p.a.
• Stationary: 2000 p.a.
Cost : Rs. 4,82,000/- p.a. Cost: Rs. 11,500/- p.a.
Thus total amount saved per annum approximates to

4,82,000 – 11,500 = Rs. 4,70,500/-
Note:
• All figures in terms of INR.
• These are hypothetical representation, and does not account or guarantee of similar cost
structure.
• These figures are based on estimated projections.
95
3. Gantt chart
4. Future enhancements
96
We believe in the one liner “There is always an inch more to build”. This
means, our software can be enhanced, and will be enhanced further more. We
were bound by certain criteria such as time, money, syllabus permission like
professional talent and work experience.
But positively, without these bounding criteria, we would like to enhance this
software project and empower it with many more functionalities. Some
functionality our future enhancement includes.
• Integration with the web.

• Establishing two way communications between both the companies.
• Different forms of graphical representation other than bar graph
pie chart and line diagrams.
• Alarm option for minimum and maximum inventory transactions
and credit limits.
• Inclusion of strigenet security.
Our current project is a sincere effort to balance all the current limiting
criteria but we hope that we can add above functionalities to our current
project.
5. Organization profile
97
5.1 INTRODUCTION
Ramlord Apparels private limited company, was founded and by Mr.Ganesh

Dhanuka, Masters in International business, Monash University (Melbourne).
The company was established in 1978, the company has grown by leaps and
bounds and is now celebrating over 25 years of glorious presence in the
industry.
Ramlord Apparels is one of the leading manufacturers and exporters of textile

products like shirts, denims, trousers etc. The company is also one of very few
government recognized export house.
Ramlord Apparels has its offices spawned all across Mumbai, with five
regional offices, three R&D laboratories and four factories. It’s a
professionally managed private limited company, with over 500 employees.
In recognition of high priority Ramlord Apparels has always placed on quality

and has applied for ISO 9001 certification in early 2005. Company meets all
parameter requirements for ISO 9001 certification. It was awarded the
certification in September 2005.
Ramlord Apparels association is with some of the leading companies in the

world enables them to combine the best of ISO 9001 and GMP standards. Its
association with such companies has made it possible for them to achieve
quantum leap in their standards.
5.2 RECENT DEVELOPMENTS
98
Ramlord Apparels has set up a new corporate office at Nariman Point,

Mumbai and has also crossed rupees 32 million mark in turnover.
Ramlord Apparels significantly expanded the manufacturing base by acquiring

a factory in Kandivali (Mumbai). Its status as an export house has been
elevated to that of a trading house, a position enjoyed by very few textile
companies.
5.3 MISSION STATEMENTS
With liberalization of Indian Economy and increasing globalization, these

fields are the growth markets of the future. Ramlord Apparels has chosen to
be the partner in their growth – rather than a competitor – of nation and
multinational corporations, as a reliable, independent manufacturing source.
Ramlord Apparels has the capability to undertake various types of textile

companies.
Ramlord Apparels continuing endeavor is to get everything right: Its core

values, plants, processes, systems, people, product quality, manufacturing
costs and above all, the way they do business and build everlasting
relationship with their partners.
5.4 ENDURING RELATIONSHIPS
99
Since, the launch of the company, Ramlord Apparels have always worked
towards creating an organization which would allow relationships with
internationally renowned, quality driven clients to endure and evolve over the
years.
Today, Ramlord Apparels is an organization recognized, respected and sought

by these internationally renowned clients, not only for the quality and services
offered but also for the manner in which commitment and responsibilities are
discharged. Their clients can depend on them for their strict adherence to high
standards of quality, safety, environmental protection and delivery
commitments.
5.5 QUALITY
Of all the factors Ramlord Apparels considers most central to the success and
reputation of their company, quality lies at the very core. Hence, company
meets ISO 9001 standards recognition of the high priority they accord to
quality. Ramlord Apparels association with some of the leading companies in
the world market enables them to combine the best of ISO 9001 and GMP
standards.
Ramlord Apparels approach to the management and control of quality is total

and integrated.
Ramlord Apparels imposes a very exacting regime of systems, procedures,

checks, tests, analyses to monitor and control quality. No compromise is
allowed at any stage, from raw material procurement, production processes,
100
and finished products in strict compliance to specifications, to storage,

packaging and transportation.
5.7 EXPORT AWARD FROM GOVT OF

MAHARASHTRA
Ramlord Apparels was awarded the Export Award from Directorate of

Industries, Government of Maharashtra for 1999 – 2000, 2003-2004. The
trophy was presented on Nov 8, at a function at Hotel President, Mumbai, by
Dr. Patangrao Kadam Minister for Industries, Government of Maharashtra.
Mr. S. V. Wahalekar, Vice President and Company Secretary collected a
silver salver and certificate on the occasion. The function was well attended
by several leading industrialists and senior personnel from a wide range of
industries.
6. Vb Coding conventions
101
This part of document discusses common coding conventions and naming

techniques for the form design layout (front-end) i.e. for Visual Basic 6.0
6.1 NAME OF THE PROJECT
The name of the project should reflect the contents of the project and should
be saved with a “*.vbp” extension. The name could be more than 8 characters
long and a mixture of small case and upper case letters. They cannot include
any special symbols except for an underscore “_”.
Example: DataLogger.vbp
6.2 NAME OF THE MODULE
The name of the module should reflect the contents of the module. It should
be saved with a *.frm extension. They cannot include any special symbols
except for an underscore “_”.
6.3 NAMING FOR FORM ELEMENTS
• Form
102
The name of the form should reflect the contents of the form making it
easy to recognize. The first alphabet of the form should be capital letter
followed by small letters if the form name comprises of two words then
first letters of both the words should be capital. The form should be
saved with *.frm extension. They cannot include any special symbols
Example: frmTerminal.frm
• Command button
The command button should be named with a key word “cmd”
preceding to the name of the button making it easier to understand that
we are referring to a command button. The first letter must be capital.
They cannot include any special symbols except for an underscore “_”.
Example: cmdArchives
• Labels
The labels should be named with a keyword “lbl” preceding the name
of the label making it easier to understand that we are referring to a
label. The first letter of the label name after the keyword should be
capital. They cannot include any special symbols except for an
underscore “_”.
Example: lblStartLogging
• Textbox
The textbox should be named with a keyword “txt” preceding the name
of the textbox making it easier to understand that we are referring to a
textbox. The first letter of the frame name after the keyword should be
103

underscore “_”.
Example: txtTerm
• Frames
The frames should be named with a keyword “fra” preceding the name
of the frame making it easier to understand that we are referring to a
frame. The first letter of the frame name after the keyword should be
underscore “_”.
Example: fraItem
• Combo Box
The combo box should be named with a keyword “cmb” preceding the
name of the combo box making it easier to understand that we are
referring to a list box. The first letter of the frame name after the
keyword should be capital. They cannot include any special symbols
• Option Button
The Option Button should be named with a keyword “opt” preceding
the name of the combo box making it easier to understand that we are
referring to an option button. The first letter of the option button after
104
the keyword should be capital. They cannot include any special

symbols except for an underscore “_”.
Example: optOverFlow
• Picture Box
The combo box should be named with a keyword “pic” preceding the
name of the picture box making it easier to understand that we are
referring to a picture box. The first letter of the picture box name after
the keyword should be capital. They cannot include any special
symbols except for an underscore “_”.
Example: picLogo
6.4 NAMING FOR VARIABLES AND CONSTANTS
105
Identifiers must be meaningful. Choose its name that identifies its purpose.
Do not abbreviate names unless the meaning is very obvious. Do not use very
short identifiers. Precede each identifier with a lower case prefix that
specifies the data type. It is similar to the convention we have adopted for
naming form elements.
Example: Dim as string

Dim as integer
Capitalize each word of the name following the prefix. Never use all alphabets
in uppercase for its naming.
6.5 MENUS
While declaring menu name we follow the usual convention where before the
menu element name field we have a keyword “mnu” preceded by the name.
Example: mnuHangup
6.6 PROCEDURE
106
While writing functions and procedures we use he formal conventions i.e. the
function or procedure name should be such that it should reflect what the
function or procedure name is more than two words then each word should
begin with a capital letter.
Example: Private sub SendText.
6.7 FUNCTIONS
If the function name is more than two words then each word should begin with
a capital letter. No data type or object is linked with them hence they are
followed by no prefixes.
Example: Private Function Chartinit( )
107
7. Glossary
About box
A dialog box that contains information about a program.
Access key
The keyboard key corresponding to the underlined or highlighted letter in a

menu or dialog box. Pressing the ALT key and the access key activates the
menu or dialog box. Sometimes referred to as a hot key.
ASCII code
An acronym for American Standard Code for Information Interchange. It is a

code in which the numbers from 0 to 255 stand for letters, numbers,
punctuation marks, and other characters. ASCII code is standardized to
facilitate transmitting text between computers or between a computer and a
peripheral device.
Assignment statement
The methods for default assignment and initialization are “member wise
assignment” and “member wise initialization,” respectively. Member wise
assignment consists of copying one object to the other, a member at a time, as
if assigning each member individually. Member wise initialization consists of
copying one object to the other, a member at a time, as if initializing each
member individually. The primary difference between the two is that member
wise assignment invokes each member’s assignment operator (operator=),
whereas member wise initialization invokes each member’s copy constructor.
108
.bas file
Code in Visual Basic is stored in modules. There are three kinds of modules:
form, standard, and class.
Simple applications can consist of just a single form, and all of the code in the
application resides in that form module. As your applications get larger and
more sophisticated, you add additional forms. Eventually you might find that
there is common code you want to execute in several forms. You don't want to
duplicate the code in both forms, so you create a separate module containing a
procedure that implements the common code. This separate module should be
a standard module. Over time, you can build up a library of modules
containing shared procedures.
Boolean
Boolean variables are stored as 16-bit (2-byte) numbers, but they can only be
True or False. Boolean variables display as either True or False (when
Print is used) or #TRUE# or #FALSE# (when Write # is used). Use the
keywords True and False to assign one of the two states to Boolean variables.
When other numeric types are converted to Boolean values, 0 becomes False
and all other values become True. When Boolean values are converted to
other data types, False becomes 0 and True becomes -1.
Buffer
A temporary holding area in memory where information can be stored. Visual

Basic provides buffering in two locking modes: pessimistic buffering and
optimistic buffering. These choices determine when one or more records are
locked, and how and when they are released.
109
Class
A template or blueprint that defines the characteristics of an object and

describes how the object should look and behave.
Class module
class is a template from which an object is created. Code in a class module

describes the attributes and behavior of objects that are created from the class.
Although a class isn’t an object, it does have design-time properties that

define its attributes and events that define its behavior.
Code window
Use the Code window to write, display, and edit form, event, and method
code. You can open as many Code windows as you want, so you can easily
view, copy, and paste the code from different forms.
Command control
A control that is associated with a command. When you click the command
button at run time, the command associated with the button executes.
Common dialog box
A common dialog box is a system-defined dialog box that standardizes how

users perform complex operations that are common to most applications.
Windows CE supports the Color, Open, Save As and Print common dialog
boxes. The following screen shot illustrates a Print dialog box.
110
Me
The Me keyword behaves like an implicitly declared variable. It is

automatically available to every procedure in a class module. When a class
can have more than one instance, Me provides a way to refer to the specific
instance of the class where the code is executing. Using Me is particularly
useful for passing information about the currently executing instance of a
class to a procedure in another module.
Concatenation string
Call this member function to insert a single character or a substring at the

given index within the string. The index parameter identifies the first
character that will be moved to make room for the character or substring.
Constant
A numeric or string value that does not change. Constant expressions combine
constants and operators, but no variables, and evaluate to the same value
every time.
Data type
The attribute of a variable or field that determines what kind of data it can
hold. Visual Basic has these data types: Character, Currency, Date, Date
Time, Double, Float, Logical, Numeric, Integer, General, and Memo.
Declaration
The argument-declaration-list portion of a function declaration:
• Allows the compiler to check type consistency among the arguments

the function requires and the arguments supplied in the call.
111
• Enables conversions, either implicit or user-defined, to be performed

from the supplied argument type to the required argument type.
• Checks initializations of, or assignments to, pointers to functions.
• Checks initializations of, or assignments to, references to functions.
Design time
The mode of operation when an application is being created. At design time,

you build the components of your application and set their properties.
Enabled
This attribute describes if the given control is enabled or disabled. Most

controls have a gray disabled look. For some inert controls, changing this
attribute results in no visible change.
Event
An action, recognized by an object, for which you can write code to respond.
Events can be generated by a user action–such as clicking the mouse or
pressing a key–by program code, or by the system, as with timers.
Event Procedure
A general procedure tells the application how to perform a specific task. Once
a general procedure is defined, it must be specifically invoked by the
application. By contrast, an event procedure remains idle until called upon to
respond to events caused by the user or triggered by the system.
Focus
Focus is the ability to receive user input through the mouse or keyboard.
When an object has the focus, it can receive input from a user. In the
112
Microsoft Windows interface, several applications can be running at any time,

but only the application with the focus will have an active title bar and can
receive user input. On a Visual Basic form with several text boxes, only the
text box with the focus will display text entered by means of the keyboard.
The Got Focus and Lost Focus events occur when an object receives or loses
focus. Forms and most controls support these events.
Form
A container class. A collection of one or more pages that behaves like a

standard window or dialog box. A form contains controls for displaying and
editing data. Forms can be contained within a form set.
Form file
A form file with a .form extension that contains the code and control
information for a single file
Form module
Each form module contains event procedures — sections of code where you
place the instructions that will execute in response to specific events. Forms
can contain controls. For each control on a form, there is a corresponding set
of event procedures in the form module. In addition to event procedures, form
modules can contain general procedures that are executed in response to a call
from any event procedure.
113
Frame
A Frame control provides an identifiable grouping for controls. You can also
use a Frame to subdivide a form functionally—for example, to separate groups
of OptionButton controls.
General declaration section
The portion of code module used to declare variables that will be available
throughout that module.
Graphical user interface
Programs application containing icons, buttons, and menu bars.
Image
A control that allows you to include pictures on a form.
Index
A set of pointers that are logically ordered by the values of a key. Indexes
provide quick access to data and can enforce uniqueness on the rows in a
table. Indexes in Visual Basic are maintained in an index file.
Instance
An object-oriented programming term. An object created from a class

definition. Unlike a class, which is just a definition, an instance actually
exists as an object that can be used to perform tasks. For example, a text box
on a running form is an instance of the TextBox class.
114
Iteration
Iteration statements cause statements (or compound statements) to be

executed zero or more times, subject to some loop-termination criteria. When
these statements are compound statements, they are executed in order, except
when either the break statement or the continue statement is encountered.
Label
User-defined name you can attach to a specific version number of a file or

project.
Line continuation character
A space and an underscore is used in program code o indicate that a basic

statement ontinues on the next line.
Logical Operators
An operator that produces a logical result (true or false); sometimes called a

Boolean operator. The logical operators in Visual Basic are ( ) (expression
grouping), NOT or ! (negation), AND and OR (inclusive OR).
Loop
Specifies how many times a method or property will loop when activated. If
applied to a marquee, it specifies how many times the content of the marquee
should loop. If n=-1 or infinite, it will loop continuously.
115
Message box
Displays a message in a dialog box, waits for the user to click a button, and
returns a value indicating which button the user clicked.
Method Class
When you define a class for a tool information model, you specify the
interfaces that the class implements. For each of those interfaces, you specify
the members (properties, methods, and collections) that are attached to the
interface.
The definition of a method as a member of an interface does not result in the

method's implementation logic being stored in the Repository. However, it
does add the method name to the set of defined member names for that
interface. It also reserves the method's dispatch identifier in the set of defined
dispatch identifier values for the interface.
Module
A subset of the Windows CE operating system. Windows CE is structured as a

collection of modules. Each module is a self-contained subset of the Windows
CE operating system that can be used to construct a customized operating
system for a particular device.
Nested
A class can be declared within the scope of another class. Such a class is
called a “nested class.” Nested classes are considered to be within the scope
of the enclosing class and are available for use within that scope. To refer to a
nested class from a scope other than its immediate enclosing scope, you must
use a fully qualified name.
116
Option button
A small round button with a label next to it. The label may be text, an icon, or
a bitmap. Option buttons, also known as radio buttons, are usually grouped
together in a group box, representing a set of related, but mutually exclusive
options. When a user selects an option button, all other option buttons in the
same group are automatically unselected.
Project file
When you create a project workspace, a project workspace file

ProjectName.dsw is created to store information at the workspace level. Other
associated files are also created, including a project file (.dsp), for building a
single project, and a workspace options file (.opt).
Properties window
Lists the design-time properties for selected objects and their current settings.
You can change these properties at design time.
Public
Indicates that the Function procedure is accessible to all other procedures in

all scripts.
Startup
The Startup entry point function loads a resource DLL, returning a structure
containing a function table and a version number.
117
Textbox
A control that allows you to enter or view text in a form. Typically, text boxes
hold a single line of text.
Timer
A control used to control recurring events in your application. The timer is not
visible at run time.
Tool tip
A small rectangular pop-up window that displays a brief description of a

command bar button's purpose.
User interface
This section describes the user interface portion of the Microsoft® Windows®
installer. You can author a full graphical user interface by populating the
appropriate tables or you can choose to bypass the internal UI functionality
and use an external UI.
Validation
The process of checking whether entered data meets certain conditions or

limitations.
Variable
A location in the computer's memory where data is stored. You can change the
contents of a variable but its name and storage area are reserved for use until
you end the Visual Basic session or release the variable.
118

IT Project Documentation - Example

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

IT Project Documentation - Example

Enviado por

Direitos autorais:

Formatos disponíveis

DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM

We followed the professional approach of democratic decentralized and

Ramlord Apparels, which needed a quick, easy and customized computerized

Final milestone of our project was when we successfully developed

Our hard work was rewarded by company’s CLASS A certification. We thank

[PROJECT/SOFTWARE SYSTEM NAME NAME]

Ramloard Apparels is a company which has a business in textile industry

The company has given us their working of [Company Name] and we

Reports which will include detailed reports about inventory transactions,

We the undersigned, developers of this project [PROJECT/SOFTWARE

of our knowledge and assure the authentication of this document to our

YOUR PARTNERS NAME - IF ANY HARDIK

DEVELOPERS OF THE SOFTWARE APPLICATION SUITE

3. Software development life cycle

System Development Life Cycle (SDLC) is the overall process of developing

There are many different models

b. WATERFALL MODEL: OUR CHOICE

The Waterfall Model is the earliest method of structured system development.

The Waterfall Model consists of the following steps:

• Feasibility Study: It refers to the consideration of all aspects of the

• Systems Analysis: This step refers to the gathering of system

• System Design: Once the requirements have been collected and

• Coding: Also known as programming, this step involves the creation of

• Implementation: It includes deploying the software at the company. A

implement. Implementation also involves thorough end-user training to

3.1 Feasibility study

The overview of this phase can be summarized as follows.

3.1.1 UNDERSTANDING THE REQUIREMENTS

3.1.2 CURRENT SYSTEM

• Synchronize the transactions which he will be referring.

• Start entering the transactions in the journal/registers/ledgers.

• Select a format in which it has to be presented.

• As soon as the format is selected get it approved with the management

• Repeats step no. 2 and 3 till the journal/register/ledger is submitted for

• Optionally, for important transactions will have to enter these

• Optionally, for important reports will have to plot graphs of the

Tow copies of records are maintained, one to submit it to the management at

3.1.3 IDENTIFING “THE REAL PROBLEM”

As the current domain is manually driven, they have many limitations:

• While the department in charge records transactions of one department

• Unnecessary humane power is wasted in recording transactions, instead

• Retrieving transactions is tedious and time-consuming since recorded

• Even by using MS Excel, the transactions are to be entered manually.

• Optionally, for important processes and reports the graphs has to be

• Data transfer of recorded transactions across branch offices is a very

• Retrieving the information submitted for the top level management is a

• Detection of errors in data entry is difficult.

3.2 System analysis

This phase can be described as follows

3.2.1 UNDERSTANDING COMPANY

• Is a simple, easy to understand software interface.

• Enables generation of reports to get the summary.

3.2.2 PROPOSED SYSTEM OBJECTIVES

Our primary objectives of project include:

• Obtaining accounts and inventory control in real-time when

• Automatic real-time report generation when transactions are in

• Storing records by default in database.

• Providing tickers to the users which acts like a notice board.

3.2.3 THE SCOPE OF PROPOSED SYSTEM

In the proposed system we have tried to overcome every disadvantage of the

• A program capable of real time, offline data logging and report

• An interface for Real-Time Monitoring wherein we can directly view