Topic: Integrated Inventory and POS

Course: Computer Science (unit 2)

Internal Assessment
Student Name: Ottor Mills
Candidate No: 100107_____
Centre No: 100107School: St Georges College
Teacher: Huntley Andrew
Year of Examination: 2016
Territory: Jamaica W.I.

TABLE OF CONTENTS
Page
Mark Scheme....................................................................................................................................
Definition of Problem.......................................................................................................................
Techniques of Analysis Used............................................................................................................
Context Level Diagram.....................................................................................................................
Level One Diagram...........................................................................................................................
Entity Relationship Diagram.............................................................................................................
Fact Finding Tools (a).......................................................................................................................
Fact Finding Tools (b).......................................................................................................................
Functional Requirements..................................................................................................................
Non-Functional Requirements..........................................................................................................
System Structuring............................................................................................................................
User Interface Design.......................................................................................................................
Screenshots........................................................................................................................................
Report Design...................................................................................................................................
Narrative...........................................................................................................................................
Pseudocode........................................................................................................................................
Sourcecode........................................................................................................................................
Screenshots........................................................................................................................................
Test Plans...........................................................................................................................................
Test Results........................................................................................................................................
Bibliography......................................................................................................................................

1-5

MARK SCHEME

1.

Specification of requirements

Definition of problem

[25]
(5)

Complete accurate description of the problem

Generally accurate description for the problem

Partially accurate description for the problem

Weak description for the problem

1-2

Techniques of analysis used

(5)

Sound and relevant techniques used

Mostly sound and relevant techniques

3-4

Techniques were partially sound and relevance was limited

1-2

Use of Data Flow diagrams and E-R diagrams

Data Flow Diagrams (DFD)

(9)
(3)

Context Level
flows.

Complete and accurate diagram of all relevant entities, data

Accurate diagram of most relevant entities, data flows.

3
2
1

Accurate diagram of few relevant entities, data flows.

Level 1 Diagram

Complete and accurate diagram of all relevant processes, data

flows and major data stores

(3)
3

Accurate diagram of most relevant processes, data flows and

major data stores
2
Accurate diagram of few relevant processes, data flows and
major data stores
1

Entity Relation Diagram (ERD)

Complete and accurate diagram of all relevant entities and

relationships.

(3)
3
2

Accurate diagram of most relevant entities and relationships.

1

Accurate diagram of few relevant entities and relationships

Functional and non-functional requirements

Functional Requirements

(3)

Complete and accurate description of all requirements

Complete and accurate description of most requirements

Complete and accurate description of few requirements

2.

(6)

Non Functional Requirements

(3)

Complete and accurate description of all requirements

Accurate description of most requirements

Accurate description of some requirements

Design Specification

System structuring
Complete and accurate diagram of all processes

[14]
(4)
4
2

Accurate diagram of most processes

Accurate diagram of some processes

Accurate diagram of few processes

2
1

design

User Interface design

Thorough analysis and appropriate justification of Interface

(2)
2
1

Report design

(2)

Appropriate and well implemented

Generally appropriate and satisfactorily implemented

Algorithm design

(3)

Appropriate and well implemented algorithm design

Generally appropriate algorithm design

General understanding of algorithm design

3.

Partial analysis and justification of Interface design

Choice of appropriate data structures

(3)

Appropriate and well implemented

Generally appropriate

Partially appropriate and implementation was limited

Coding and Testing

[15]

Code

achieves functionality

(5)

Code achieved some functionality (documentation, error

trapping, correct output, usability and reporting)

3-4

Code achieved functionality (documentation, error

trapping, correct output, usability and reporting)
-

Functionality was limited

1-2

Code

(5)

Code achieves all the design specifications

Code achieves most of the design specifications

3-4

Code achieves few of the design specifications

1-2

Test

4.

corresponds to design

plans

(5)

Test Plan with exhaustive data set

Test Plan with acceptable data set

3-4

Test Plan with minimal data set

1-2

Communication and Presentation

Communicates

information in a logical way using

correct grammar and appropriate jargon ALL of the time
information in a logical way using
correct grammar and appropriate jargon MOST of the time

[6]
5-6

Communicates

3-4

Communicates

information in a logical way using

correct grammar and appropriate jargon SOME of the time
1-2

TOTAL

60

Problem Statement
Topic: INVENTORY
A wholesale by the name of Chengs Wholesale is just being opened and requires an inventory
software due to the lack of inventory checking as well as a lack a lack of software with user friendly
features. Current off the shelf software does not fit their needs, such as being difficult to get
accustommed to. They require something simple and user friendly at the same time. The software that
they currently use lacks certain functions such as not being able to search a specific item with how
much are left in stock

Fact Finding Tools (a)

Questionare to employees
1) Does accounting errors affect the flow of business in the wholesale?
________________________________________________________________________
2) Are you cimputer literate or do you find it easy to use a computer system?
________________________________________________________________________
3) If the answer to the above question is no then do you think that you could use a simple non
graphical application that is easy on the eyes and gives instructions at each stage? Explain fully
_____________________________________________________________________________
_____________________________________________________________________________
______________________________________________________________
4) Does the business require a separate employee to handle accounting?
a) Yes
b) No. The Boss does it
c) No. A close individual to the boss does it
d) No. Other reason
5) If the answer above is yes, do you believe that this software can get rid of the accountant?
________________________________________________________________________
5b) Do you thing that removeing the accountant is a good thing?
________________________________________________________________________
6) How often do accounting errors arise in the business if it does?
________________________________________________________________________
7) Do you believe that this software can totally eliminate the issue of such errors?
________________________________________________________________________
________________________________________________________________________
8) If the answer above is yes explain why and suggest improvements or opinions if any
________________________________________________________________________
________________________________________________________________________
9) Do you believe that Chengs Inventory and POS can be used in other stores?
a) Yes
b) No
c) To some extent
Explain

_______________________________________________________________________
_____________________________________________________________
10) From your perspective, do you believe that anyone can use this software?
a) Yes
b) No
c) To some extent
Explain
____________________________________________________________________
__________________________________________________________

Fact Finding Tools (b)

Interview questions to the boss/manager

1) Do you believe this software is essential to the success of the business?

2) Why is it that you pay a software developer to produce a unique software rather than just
going out and purchasing one off the shelf?
3) You mentioned before that you need a software that is user friendly and can be easily
accustomed to, is it the case where you get new casheirs that often that this becomes really
important?
4) Since accounting is done by the program will additional software such as excel aid in this
area?
8

5) If this software is as user-friendly as you put if, how long do you think it will take before
new employees will be able to use it fluently?
6) Do you believe that your progrm will or can be used by ither businesses? If this is the case
will you plan to earn additional income from selling your program?
7) Would you consider the inventory system as a database or is that term too complex?
8) In the event where an employee or employees disdain the looks and overall layout of the
program, what would be your actions from there?
9) Could a virus alter data that the program has set, how secure is your program?
10) Can your program be edited to implement improvements or enhancements to increase
efficiency?

Data Analysis
Given the various problems, a complete analysis was done in order to draw possible solutions.
The main problem faced by the team at Chengs Wholesale and their current software is that the current
software lack certain functions which will be stated later, as well as being too difficult to get
accustomed to or not being user friendly. To identify the extent to which each problem affected the
business two fact finding tools were disbursed. 1) A questionnaire to be distributed among former (if
any) and current cashiers, after they have tried a demo of the program, which is to be filled out and
submitted from which it will be accessed, and 2) A list of questions were organized to be asked to the
boss/manager of the business to see any further specifications which he will desire.
What the current program used by the cashiers is lacking is that it cannot do an inventory search
to see if an item is in stock while doing a transaction. For example, say a customer orders three colas,
when there are only two in stock, the cashier can still enter the three colas into the transaction without
receiving any warning that there are only two left. They would then have to go over the list and correct
this, wasting valuable time. My solution is to run the inventory program alongside the pos program in
the same program so that functions can be written in the pos to check the inventory before adding the
10

item to the transaction list. If the quantity of the item requested is not available, then a message will
appear saying something like Only x amount of that item are currently in stock, would you like to reenter the quantity? which would save the cashier the hassle of going over the list to remove the item.
The accounting aspect of the business was also analyzed and it was decided that along with the
inventory, there should be a spreadsheet showing the flow of money, how much is spent and what it is
spent on. A question in the questionnaire in the fact finding tools was aimed at determining if the
accounts of the business was handled by the boss or if they hired an accountant to handle the accounts,
it was thought ahead that if it were the case where they had to hire an accountant that they would have
no need to because the spreadsheet would automatically handle all accounts, making this a bonus for
the business because it would save them the cost of hiring one.
User friendliness was a feature of the program that was also analyzed. Certain user interfaces
may be too much to absorb for the user in terms of layout. Instead of using a graphical interface this
program will use a menu driven one followed by tables to try and make the user experience as simple
and comfortable as possible.

11

Context Level Diagram

12

13

Level One Diagram

14

Functional and Non-Functional Requirements

Functional Requirements

Input:

Non-Functional Requirements

User Friendliness System can be

easily accustomed to by even the

The item attributes to be entered

most extreme computer novices.
into the inventory
1. Item Name
Some Employees have their own
2. Stock
3. Buying Price

account ID on the machine which

will be required to do an inventory
check.

4. Selling Price
Each account is unique to their
5. Sold

respective employee

6. Spoilt

15

Process:

A list of all items will be presented to

the inventory checker in a tabulated

Calculating the profit per unit sold

format making it effective
(equal to selling price minus buying
price), calculating profit (equal to
profit per unit sold times sold),
calculating loss (equal to buying
price times spoilt)

Output:
Table (inventory) showing all item
attributes as well as process outputs
in each column

ERD Diagram

16

System Structuring
17

User Interface Design

18

19

Screenshots

20

21

Report Design

22

Algorithm Design

23

Sourcecode

FINAL.c

24

Test Plans

25

Bibliography
1) http://www.stackoverflow.com

26