Created By,
Research and Development section,
Department of Computer Science,
Virtual University of Pakistan
Table of contents:
Topics
1.
2.
3.
4.
5.
6.
7.
Page
no.
4
4
4
5
5
5
6
Page
|1
Whom to Contact?
This booklet provides comprehensive details to the students who are planning to
take Software development projects as their final projects. Therefore, such students
are advised to go through it in complete.
If any of the quires are unsatisfied even after having read the information given in
rest of the booklet then students should contact to concerned supervisor.
Page
|2
The development project is recommended for those students who have an aptitude
and interest (equally important) for development. Presence of analytical skills to
solve a problem is also highly requisite. If a student finds these ingredients in
himself/herself then deficiencies (to a certain extent) in the areas like programming,
data base and software engineering etc can be overcome but such a student will
have to put extra efforts (depending upon the deficiencies) to make his/her weak
areas stronger. As having ambitions only does not lead to the goal, one has to strive
for those ambitions to get them materialized.
4. Eligibility Criteria
No student below 1.75 Effective CGPA will be allowed to take the project title.
MCS/MIT Students must have completed 30 credit hours to become eligible for
taking the final project. So dont enroll in CS619 course or drop your cs619
course if you have earned less than 30 credit hours.
BSCS/BSIT Students must have completed 90 credit hours to become eligible
for taking the final project. So dont enroll in CS619 course or drop your cs619
course if you earned less than 90 credit hours.
6. Grading Policy
Students will be clearly communicated about the deliverables they need to submit
on specified dates. This is important to remember that each deliverable carries a
significant weightage so students are advised to take each deliverable very seriously
Page
|3
Next, each
provided.
offered
projects
detailed
information
Page
|4
is
Following are some sample games for you to get the basic
idea:
http://www.disney.co.uk/disney-games/play/wall-e/hidden-object/
http://www.hidden4fun.com/hidden-object-games/3035/House-ofTreasures.html
http://www.mindjolt.com/egypt-hidden-objects.html
[Note: The above links are just to get basic idea about following
requirements, make sure you know what type of application to
develop from Application Type heading under this project]
This is a single player game so only one actor i.e. Player, Following are
the required features of this project:
1. It should have at least 10 stages, and each stage should offer more
difficulty.
2. In start of each stage, the game will display a list of 10 objects to
find (this list can be simple text i.e. names of objects, or the shapes
of the objects).
3. The game application should actually have 20 to-be-required
required objects at each stage, but the player is required to find 10
objects. So the game will set the required 10 objects randomly
every time a stage is started.
4. When a player touches a required object, it should be removed
from required list (or it should be marked). It should also be
removed or marked from the picture.
5. It should be a time based game. Each stage should have a fixed
time to complete, or the time can be set according to difficulty
Page
|6
level i.e. time limit decreases a few seconds on each next level. If
the player is able to find all 10 objects within the specified time,
the game will move to next stage, Otherwise the game ends.
6. It should support 2 hints for each stage. When player touches hints,
the application will indicate one of objects that are still not picked
up by the player.
7. The application should be able to save game state when player
opts to save the game. The next time game is launched, it will
show options to Play New Game or Continue Last Game. On
choosing continue option, player should be able to resume the
game from last saved state.
Application Type
It will be a mobile application, you can pick any modern mobile OS
platform (e.g. Android, Apple, Windows Mobile etc)
Tools & Technologies
Any modern tool and technology set used for developing mobile games
based on the platforms discussed in Application Type.
Supervisor: Usman Waheed (usman.waheed@vu.edu.pk)
Application Type: Native Mobile Application
Possible Students: 1 to 2
Page
|7
Example of Volume
Controller
Page
|9
Example of Sound
graph
There should be options for the tuning of sound effects with each
volume controller for each sound file. (User would be able to
optimize the bass, stereo, and other audio effects).
Page
| 10
2.0 Purpose:
New Stock program for control and monitoring of Stock Receipts,
Transfers, Consumption and Physical Count and discrepancies. This
Page
| 11
program should be simple and helpful not only to the Store Keeper
to handle the daily issues and request for production but also to the
supervisor/area controller for monitoring of stock quantities and cost
well before the production.
3.0 Scope:
The general process will be starting from requisition to Receiving
Goods, Transfer in, Transfer
Out, Consumption of goods, getting closing stock and taking the
physical stock. Inventory will be based on Stock Card and Stock Sheet,
Stock card is transaction details of one item and stock sheet will be
transaction details of all items. Maintaining and tracking the daily stock
movement in an efficient way, so that it can be audited any time and
data can be exported in required format.
4.0 Aim & Objective of the project
The main aim of this project is to provide a better system to the sites to
handle all their daily stock related activities digitally. So that the stock
can be managed at the individuals sites and then data can be exported
and sent to head office for consolidation and upload stock transactions
into our ERP system. So, that the performance of the sites can be
monitored and can be audited as well. Also To produce a simple, yet
suitably effective user friendly interface and a system that is easily
maintainable, efficient and practical.
The proposed system should have the following
objectives to be achieved.
Offline application
User Friendly Environment, Easy to use
Lesser data size and Space with low system spec. requirement
Easy searching and data entry option
Data templates for reusability
Fast information Retrieval
Less man power literacy requirement
Accuracy of data with Accountability
Data import export Facility
5.0 Overview
5.1 Existing System:
Currently CSSC (Catering Support Service Company) is
using excel based application called Stock Program.
5.2 Drawbacks:
Size of data is huge which cant be emailed.
Query based Reporting not available.
Require lot of Technical support.
Unable to consolidate data of different sites.
Unable to export data in required formats.
Due to multiple linked excel sheets, maintaining fixed file path is difficult.
Problem while changing file names and path.
Difficult to create more sheets because of long formulas.
Unable to track Purchase Discrepancies
Unable to do Requisition Consolidation
Page
| 12
6.0 Plan:
As per the business process Purchase dept. is central and doing purchases
centrally, located in head office for all the multiple projects. While, the
purchase order will be processed in head office and copy will be sent to the
projects and suppliers. Project will received items and will maintain their
stock using stock program and will be exported and sent to the head office
periodically by using mediums like: flash drive, email. Where all the projects
data will be consolidated and analyzed by the concerned. Based on that data
the projects stock, daily cost and man-days will be extracted. And necessary
actions will be taken. The consolidation will be done in three layers 1.
Projects i ndividually 2. Area Wise 3. Company wise. Ultimately the required
data will be exported and uploaded into the main ERP system.
7.0 Requirement Specifications:
7.1
General
Overview:
Head office will send exported data of updated items master list along with
the projects list to all the projects who will import it into their system for use.
User must select Number of person he needs to cook food for and the menu
items. System shall calculate the requirement based on number of persons.
And shall check for the available stock. Accordingly the requisition will be
generated by the system.
User will receive stock through supplier or warehouse and will log the
quantities and unit price, expiry date (not mandatory for all items) of the
item. User can also transfer stock to another project store (called Transfer
out) with quantity and amount. User can also receive stock from another
project store (called Transfer In) with quantity and amount. User will enter
the stock consumption in the system to get daily closing stock.
This all movement in stock will result into
following:
a.
Maintaining Stock
Sheet. b.
Maintaining Stock Card.
c.
Per many day cost (if user have served 200 people in a day with
cooked food. It will be divided on the food material consumed cost per
day).
d.
Control of stock.
e.
Stock movement tracking.
f.
Multiple dimensional Reports, soft will be exported to be
sent to head office. g.
Performance analysis
h.
Consolidation of multiple stores data at head office.
i.
Summary reports with different aspects. (Req, Purchases,
Transfers, Project wise summary)
j.
system should show fast moving and slow moving items based on
consumption pattern in a defined period.
Page
| 13
k.
should have option to lock Date or week (user should not be able
to enter back dated trans. But supervisor or admin. Can have
access to do so.)
Page
| 14
CSP STOCK
Opening Qty.
Closing Stock
Consumption
Requisitions
Reciepts
Transfer Out
Transfer In
No. of Man-days
Historical Analysis
of Requisition
Using Templates
Generate
Requisition
Cook will raise daily internal store requisition will submit for Supervisor
approval. Based on number of man-days, Menu and available stock. Internal
Store requisition can be same as per the previous days so using saved
templates functionality (or copy) user will create internal store requisition. At
the end of the day those items will be considered as consumed. After final
approval of requisition it will be sent back to the project that will upload their
approved requisition. Versions of requisitions can be maintained in the
system, to see how much they requested and how much was approved. But
older version will not be active to use. Receiving of material will be as per the
latest version.
Page
| 15
Project A
Store
Store Keeper
Create Requisition
NO
Sent to
Supervisor for
Approval
Yes
Area Manager
No
Yes
Verification of
Requirement by
Operations Auditor
No
Yes
Operations
Manager
No
Yes
Purchase Dept.
Supplier
Purchase Order
Process
Central
Warehouse
Delivery of Goods
by Supplier or
Warehouse
Item No.
XYZ-00001
Item
name
ABC Item
Uni
t
KG
Previou
s
period
Consump
50
OnHand
Sto
ck
Order
Qty.
62.50
Additio
nal
Qty
.
2.5
7.4 Receipts:
Goods Delivered by
Supplier at Project
Store or Central
WH
Physical Checking
of Good
Expiry Date
Checking
Quantities and
Prices to be
matched with Doc.
Generate Goods
Receive Note
(GRN) Doc.
7.5 Transfer
In:
Goods Delivered by
Project using Inter
Transfer
Physical Checking
of Good
Expiry Date
Checking
Quantities and
Prices to be
matched with Doc.
Transfer In Process
7.6 Transfer
Out:
While transfer note report shall be sent along with the delivery.
Based on Req.
Prepare Transfer
Note
Collecting Good
Expiry Date
Checking
Quantities and
Prices to be
matched with Doc.
Total
Order
Qty
.
65
7.7 Consumption:
As per 2.1 the goods daily internal store requisition will be
theoretically same as consumption.
Project will request whatever he needed to be consumed daily not
more. The adjustments can be done by area controller at the end
of the week for variances.
7.8 Closing Stock:
System will generate the closing stock based on all inventory
transactions details, of opening balance, purchases, transfers and
consumptions, which is called stock Card and Stock sheet Reports.
System should highlight the near expiry items so that it becomes
significant that there is a stock which is going to expire during a
defined period. E.g.; in next two weeks.
Closing Stock = Opening Balance + Purchases + Transfer in Transfer Out
Consumption
7.9 Physical Stock:
Weekly store keeper will take stock count of all the items with expiry date
log. And will send report to head office.
8.0 Tools and Technology:
1. This software should be developed using SQL Server Express database. This
shall be developed as desktop application only which will be used at our
multiple projects as well as at head office (for consolidation of all projects data
using import export functionality).
2. User should login using their login credentials and system should also keep
login history.
3. There could be scenarios where one user using one computer can do
transactions for two projects. System should also be able to handle
that.
4. There will be three levels of use of this software a. individuals
Project b. Area Office c. Operations Dept.
9.0 Attachments:
For the business requirement understanding the following detailed document may
be provided.
1. CSSC Stock Structure
2. Item Coding Structure
3. CSSC Item Coding Procedure
4. Item Master List
5. Projects Name List
6. Existing Stock Program with data
7. Existing Stock program Procedure
STOCK ITEMS
INVENTORY
Date: 3/10/2014
FOOD
(F)
Level 1: Group
Chilled
(C)
Level 3: Catergory
Juices/Drinks
(01)
with Type/Flavour
Juice Apple
NON FOOD
(N)
Dry
(D)
Frozen
(F)
Oils/Fats
(01)
Sea Food
(01)
Expendables
(E)
Disposable
(D)
Cleaning
(C)
ASSETS
(A)
Level 5: Brand/Origin
Nada/KSA (0)
Level 6: Packing/Size
24x330 ML (0)
Level 7: Price
New Price (00)
New Price (01)
New Price (02)
####
0101
Page
|8
STOCK ITEMS /
INVENTORY
Level 1: Group
FOOD
(F)
Expendables
(E)
Date: 3/10/2014
NON FOOD
(N)
Disposable
(D)
Cleaning
(C)
ASSETS
(A)
Stationary
Printing
Materials
Uniform
Repair &
Maint.
Furnitures/
Equipments
Vehicles
Level 3: Catergory
Paper Prod.
Plastic Prod.
Aluminium Prod.
Chemical
Non-Chemical
Food
Container
Round
Level 5: Brand/Origin
Nada/KSA (0)
Level 6: Packing/Size
24x330 ML (0)
Level 7: Price
New Price (00)
New Price (01)
New Price (02)
####
0101
Fixtures
Computer /
Peripherals
Group
Sub-Group
Category
Level 1
Level 2
Level 3
FOOD
Chilled
(C)
Frozen
Dry
(F)
(D)
15
16
17
18
19
20
22
23
24
25
26
27
28
NON-FOOD
(F)
2
3
4
5
6
7
8
9
10
11
12
13
14
21
Item Name
(include
s
Level 4
Condiments
Cereals
Pulses
Flour
Rice
Spices/Nuts (includes Herbs)
Spices/Nuts (includes Herbs)
Tea & Coffee
Pasta
Oils/Fats (includes Ghee)
Preserves/Pickles
Vegetables
Fruits
(01)
(02)
(03)
(04)
(05)
(06)
(07)
(08)
(09)
(10)
(11)
(12)
(13)
Juices/Drinks
Dairy Products
Bread
Bakery Items
Sea Food
Meat (includes processed meat)
(14)
(15)
(16)
(17)
(18)
(19)
(N)
Cleaning Products
(C)
Chemicals
Cleaning Supplies
(01)
(02)
Disposables
(D)
Paper Products
Plastic Products
Other Products
(03)
(04)
(05)
P a g e | 10
29
30
(G)
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
Gas Cylinder
Gas Tank
Heating Fuel (includes
charcoal)
(06)
(07)
(08)
Expendables
(E)
Crockery
Cutlery
Pots/Utensils
Linens
(09)
(10)
(11)
(12)
Stationary
(S)
Files/Folders
Office Supplies
Writing Instruments
Printing materials
(13)
(14)
(15)
(16)
Uniforms
(U)
Clothing
Footwear
PPE (safety equipments)
(17)
(18)
(19)
(R)
Vehicles Fuel
(20)
Vehicles Repairs
Repairs & Maintenance
(21)
(22)
48
49
50
51 ASSETS / FF&E
52
53
54
55
56
57
58
59
60
61
Equipments/Appliances
(E)
Electrical
Others
(01)
(02)
Furniture/Fixtures &
office Equip.
(F)
Furniture
(03)
Fixtures/Fittings
Computers
Printers/Fax/Copiers
Miscellaneous
(04)
(05)
(06)
(07)
Antivirus License
(08)
Software/Licenses
(S)
P a g e | 11
62
(09)
63
64
65
66
67
68
69
70
71
72
73
Microsoft Licenses
(10)
(12)
(13)
Vehicles
(V)
Lease Vehicles
Owned Vehicles
(14)
(15)
(B)
Leased Land/Building
Owned Land/Building
(17)
(18)
P a g e | 12
A master list of all the items with the new coding has been prepared by Account
dept. which should be used at all the projects.
1.2
As per the coding structure the accounts shall allocate the items code to all
the stock/inventory items upon the request of Procurement before making the
purchase order if the master list dont have any item in it or there is a new item
arrival.
1.3
The Items structure consist of 7 levels named Group, Sub Group, Category, Item
Name + (Type/Flavor), Brand/Origin, Packing/Size, Price Respectively.
1.4
Level 1 and 2 will be one digit alpha type. Whereas Level 3 will be two digit
numeric type. And Level 4 will consist of four digit numeric type. Concatenating
two digits of item name and two digits of Type/Flavor. Level 5, 6, 7 will be
three digit numeric type. So, the total length of the code will be 17 digits
alphanumeric.
Example
FC1401010010010
00
Level 1
Food
(F)
Chilled
(C)
Level
4
Category
Item Name
+
(Type/Fla
vor)
Juices
Juice Orange
(14)
(0101)
Non-Food
(N)
Frozen
(F) Dry
C
(D)
Group
1.5
Level 2
Sub
Group
Level 3
01
010
1
Level 5
Level 6
Level 7
Brand/Ori
gin
Packing/Si
ze
Price
Nada
(001)
24x1
(001)
(000)
00
1
00
1
000
While making the purchase order Purchase should use the appropriate item
code, if there is a new brand, size, type, or price, a new item must be created. To
Page |
13
get the new item code the item request form shall be used and sent to the
accounts dept. after inter department approval. A responsible person in Account
will make sure that the requested item does not exist in the system. If true he
will create a new number for the new item.
1.6
Purchase Department shall prepare the purchase order and send approved copy to
the projects for their information either from central office or from vendor.
1.7
The printed purchase order will consist of Item code, at the time of deliveries
project must verify the items with the P.O. and it must match. If not project must
contact back to the purchase dept.
1.8
New master list of items with codes will be provided updated at the projects by
inventory controller, as and when there is change in the master list.
1.9
Once the items are received at the store/warehouse in-charge must be enter data in
Stock Program with the item codes. All the receipts, transfers and consumptions
must carry the item code. The local cash purchases will also go in to the appropriate
groups and will follow the same coding structure. If code for the locally purchased
item is not available, project shall get the code from procurement as per the
procedure and enter into the stock program. Refer to stock program procedure.
1.10
Purchase department shall follow the same new item creation procedure form to
get the new codes for the LCP items from accounts and inform the new created
item codes to the project for their stock program update.
1.11
The purchases done without preparation of P.O must also be stopped. Purchase
dept. shall also ensure to enter all the records in the ERP system as and when
purchase is occurred.
1.12 Once all the items transactional data and invoices are entered in stock program, the
project shall send the data in fash drive on weekly basis to the central office
Accounts Dept as such.
1.13 Accounts dept. shall enter the all GRN in the system first, after preparation of GRN
accounts shall make the Trade Purchase Voucher (TPV) in the system.
1.14 From the projects the data will be coming on weekly basis and Account department
will copy it to the server and extract the consumption and transfer details from it and
upload to the ERP system.
Record Keeping:
1.
2.
3.
New items form shall file kept in Purchase Department after the approval.
Accounts department shall update the master list of items with the codes and will
update the projects and stock program.
Projects shall enter all the items with their relevant code.
Purpose
Page |
14
CSSC has introduced new excel based STOCK CONTROL PROGRAM for
control and monitoring of Consumption & Stock (food, disposables,
cleaning, Gas). This program is simple and is helpful not only to the Store
Keeper to handle the daily issues for production but also to the
supervisor/area controller for monitoring of cost well before production.
2.
Scope
This procedure is developed to get effective results from this program and
must be followed by all relevant personnel.
3.
Responsibilities
3.1 Accounts & I.T Department shall be responsible for implementing
the Program at the projects and should arrange training to the project
staff whenever necessary.
3.2 The Store keepers, Project Supervisors and Area Controllers shall be
fully responsible for maintaining and implementing this Program at
projects.
3.3 The Cost Controller/Operations Auditor is responsible for monitoring of
per man-day cost on daily basis.
4.
Procedure
4.1 Chef/Cook shall prepare Internal Store Requisition (I.S.R), verified by Project
Supervisor.
Time: One day before Production-Preferably between 10.00 A.M to 12.00 P.M
4.2 The Store Keeper shall receive the I.S.R for issuance by 3.30 P.M
4.3 The Store Keeper shall verify the availability of items and shortage (if any) shall
be conveyed to
Chef/Cook & Supervisor for necessary alterations/arrangements.
4.4 Any additional requirement of material by Chef/Cook during food preparation
shall only be made through I.S.R duly approved by the Supervisor.
4.5 In case, after the initial issue, any additional Man-days are intimated by the
camp boss, a separate
I.S.R shall be prepared for material issuance.
4.6 The Store Keeper shall enter the data on Store Req. in the Stock Program
prior to issuing the material.
4.7 Project supervisor shall verify the cost of consumption and if/when satisfied
shall authorize the issue.
4.8 The project Supervisor shall communicate the per man-day cost (one day
before) to the Area
Page |
15
Page |
16
4.9 Upon receipt of the daily food cost, Operations Manager, in consultation with
the Operations
Auditor shall review the cost for each project and take corrective
actions, if any.
4.10 The store keeper will issue materials strictly in accordance with the approved
I.S.R.
4.11 Issue timings must be displayed and strictly followed. The Stores shall remain
locked outside these hours. Any violation shall be penalized.
4.12 A master list of all items along with code numbers will be provided; the user
shall use the same.
4.13 The required fields will be entered in the following format:
Project
ALL CAPITAL
(e.g. VILLAGE)
Name:
LETTERS
Month of:
Month and Year.
(i.e. March
2014)
Date:
dd/mm/yy
(i.e. 01/03/14)
Item No:
100056
Name:
ALL CAPITAL
(e.g. RICE)
LETTERS
Packing: should
be entered in abbreviation of maximum three CAPITAL
LETTERS (e.g. PKT, BTL,
KG)
Size:
e.g. 1x12
Expiry Date:
dd/mm/yy
(i.e. 01/03/14)
Quantity: Format predefined (user just need to enter)
Price:
Format predefined (user just need to enter)
4.14 The data folder will be copied on to the provided USB fash drives and will be
transferred to Head
Office on weekly basis via area office.
4.15 Project Supervisor will be the custodian of the USB fash drive, and will
keep it in a safe/secure place. Once a week it will be given to the store
keeper to copy the data for sending to Central Office.
4.16 Only the following personnel shall be authorized to access the computer and
stock
Program:
4.15
4.15
4.15
4.15
4.15
4.15
4.15
4.17 A log book will be maintained in projects as well as Central Office for dispatch
and receipt of USB
Page |
17
Page |
18
Page 19 of 32
4.19 Before input of man-days, all meals should be converted into Mandays. (No. of meals/3)
4.20 The manual preparation of Transfer Note and Goods Received
Note (GRN) shall be continued as usual.
4.20 The Project will maintain record by creating two folders. One for
Weekly Data and second for
Monthly Data in Drive D.
4.21 Supervisor should verify the input data on daily basis and Area
controller on frequent basis for any errors/mistakes and variances.
4.22 Project will keep the data for at least three months in their
computer.
4.23 At the end of each week, the whole program folder will be copied in
Weekly Data folder and
renamed with respective week end date.
4.24 At month end, the whole program folder will be copied in both
folders i.e. Weekly Data and
Monthly Data.
4.25 After copying the month end folder, delete this folder from drive
C and copy/paste blank folder from drive D or E.
4.26 Copy/paste the closing stock of previous month in the newly
copied blank folder as opening stock of current month.
4.27 Folder/file/sheet in this program must never be deleted.
5.
Records
Page 20 of 32
5.3 All data received from projects shall be verified by the Area
Controller and the cost per man-day for the week shall be
reported on prescribed format.