IT Project Documentation - Example
IT Project Documentation - Example
IT Project Documentation - Example
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 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.
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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.
2
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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.
2. Synopsis
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.
3
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
another company under its supervision [Company Name] which deals in the
hardware and software for computer systems.
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.
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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.
5
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
6
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
a. AN OVERVIEW
• Waterfall,
• Fountain,
• Spiral,
• Build and fix,
• Rapid prototyping,
• Incremental, and
7
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
8
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
9
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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 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
DOCUMENTATION ON MANAGERIAL CONTROL 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:
12
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
• Re-enters all the transactions into another register for storing purpose.
The current system at [Company Name] and Ramlord apparels is among one
of the traditional and manual ones.
13
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
14
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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.
Company was very clear in what they wanted and we had no problems in
understanding them. They required software which:
15
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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.
16
DOCUMENTATION ON MANAGERIAL CONTROL 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.
17
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
• Already recorded data can also be viewed in the form of reports and
data.
18
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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 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.
19
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
21
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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
22
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
1. frmSplash
2. frmMain
3. frmDataLogging
4. frmTerminal
5. frmGraphs
6. frmPortSettings
7. frmHelpSupport
8. frmHelp
9. frmOnlineSupport
10. frmAbout
1. frmSplash :
23
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
This form gives information about the company for which software is
developed.
24
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
2. frmLogin :
This form will provide the user to enter the software application suite. This
will add security to the software application suite.
Object Property Setting
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.
25
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
4.frmCustomer_New:
This form will allow the admin to add new customer.
Object Property Setting
26
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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)
27
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
This form will help the user see all the products. A user also see details of the
quantity available also location, reorder etc.
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
10. frmproduct_New
This form will help the user to add a new product.
cmbBrand Name
cmbBrand
11. frmpayroll_New
This form will gives detail information about the payroll it also has selected
option to select a particular employee
30
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
12. frmpayroll_Print
31
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
13. frmReport_Main
This form will gives the reports of all consignment,sales,payroll listing etc.
Object Property Setting
32
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
33
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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)
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
16. frmReport_consignment
This form will gives the reports of detail information about the consignment
transaction.
35
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
18.frmselectedforPO
Object Property Setting
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
19.frmstates.
This form will gives the detail information about the states following by its
country name.
38
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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.
Object Property Setting
txtaddress
xtaddress Name txtaddress
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
mnuoptions Name
22.frmtickers_new:
This form will add a new ticker in the ticker list
40
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
cmbdd
cmbuser Name
Name dd
cmbuser
Cmbmm
Cmbdd Name
Name mm
Cmbdd
cmbyyyy
Cmbmm Name
Name yyyy
Cmbmm
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
24frmuser_Add:
This form will add a new user in the system.
Object Property Setting
25.frmuser_main:
42
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
This form will allows the admin to see all the users it also has features of
add,remove & properties
26.frmuser_properties:
This form contains the properties of the user like which function should be
enable or disabled
43
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
27.frmadjusment:
This form will help the user to adjust the accouts of the customers.
44
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
28 .frmAdmin_logging:
Object Property Setting
45
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
29.frmAdmin_setings:
This form will allows the admin to do changes for employee and human
resources
Object Property Setting
Caption (blank)
46
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
30.frmCategory_browse:
This form will allows the user to add, edit the categories of products.
Object Property Setting
31frmConsignment_browse:
47
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
This form will show the consignment of the products. It also includes
quantity,reorder level and minimum amount of quantity available
48
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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
Object Property Setting
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
34.frmDelivery:
49
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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:
Object Property Setting
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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
51
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
38.frmemployees_New
This form will allows the administrator to add new employee in the
department
53
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
54
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Till now, system points were defined, programming language and resources
were discussed and also system design was confirmed with the company.
55
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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.
57
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Screen Layout:
58
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Form Code:
Place Your Code Here. Do remember to put in comments that describe your
code- it goes a long way.
Test Result:
The form is validated successful and does not consist of any errors.
59
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Screen Layout:
60
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
61
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Form Code:
Place Your Code Here. Do remember to put in comments that describe your
code- it goes a long way.
Test Result:
The form is validated successful and does not consist of any errors.
Specification: This form will allow the authorized user to change their
password.
62
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Screen Layout:
Form Code:
63
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Place Your Code Here. Do remember to put in comments that describe your
code- it goes a long way.
Test Result:
The form is validated successful and does not consist of any errors.
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.
64
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Screen Layout:
Form Code:
Place Your Code Here. Do remember to put in comments that describe your
code- it goes a long way.
Test Result:
The form is validated successful and does not consist of any errors.
65
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
66
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Screen Layout:
Form Code:
Place Your Code Here. Do remember to put in comments that describe your
code- it goes a long way.
67
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Test Result:
The form is validated successful and does not consist of any errors.
68
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Screen Layout:
Form Code:
Place Your Code Here. Do remember to put in comments that describe your
code- it goes a long way.
69
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Test Result:
The form is validated successful and does not consist of any errors.
Screen Layout:
70
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
71
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Form Code:
Place Your Code Here. Do remember to put in comments that describe your
code- it goes a long way.
Test Result:
The form is validated successful and does not consist of any errors.
Specification: This form enables user to get details of the delivery orders
received till date.
72
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Screen Layout:
73
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Form Code:
Place Your Code Here. Do remember to put in comments that describe your
code- it goes a long way.
Test Result:
74
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
The form is validated successful and does not consist of any errors.
75
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Screen Layout:
76
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Form Code:
Place Your Code Here. Do remember to put in comments that describe your
code- it goes a long way.
Test Result:
The form is validated successful and does not consist of any errors.
77
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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.
Screen Layout:
78
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Form Code:
Place Your Code Here. Do remember to put in comments that describe your
code- it goes a long way.
Test Result:
The form is validated successful and does not consist of any errors.
79
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Specification: This form enables user to get details of the employees and
edit the details and also provides for deleting and employee.
80
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Screen Layout:
Form Code:
81
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Place Your Code Here. Do remember to put in comments that describe your
code- it goes a long way.
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.
Screen Layout
82
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Form Code:
Place Your Code Here. Do remember to put in comments that describe your code-
it goes a long way.
83
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Screen Layout:
84
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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.
85
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
3.4.14 INVOICING
Screen Layout:
86
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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.
87
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Screen Layout:
88
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
89
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
90
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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.
Place Your Code Here. Do remember to put in comments that describe your
code- it goes a long way.
91
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Module Code:
Place Your Code Here. Do remember to put in comments that describe your
code- it goes a long way.
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
93
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
• 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.
94
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Cost: Cost:
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
3. Gantt chart
4. Future enhancements
96
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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.
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
5.1 INTRODUCTION
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.
98
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
99
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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.
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.
100
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
6. Vb Coding conventions
101
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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
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 “_”.
• Form
102
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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
except for an underscore “_”.
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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
capital. They cannot include any special symbols except for an
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
except for an underscore “_”.
• 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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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
105
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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.
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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.
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.
107
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
7. Glossary
About box
Access key
ASCII code
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
.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
109
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Class
Class module
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.
110
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Me
Concatenation string
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
111
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Design time
Enabled
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
The Got Focus and Lost Focus events occur when an object receives or loses
focus. Forms and most controls support these events.
Form
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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.
The portion of code module used to declare variables that will be available
throughout that module.
Image
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
114
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
Iteration
Label
Logical Operators
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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.
Module
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
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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
Properties window
Lists the design-time properties for selected objects and their current settings.
You can change these properties at design time.
Public
Startup
The Startup entry point function loads a resource DLL, returning a structure
containing a function table and a version number.
117
DOCUMENTATION ON MANAGERIAL CONTROL SYSTEM
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
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
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