Online Sales and Inventory Management System (SIMS)

An internet Sales and Inventory Management (SIMS) for a departmental store. This method can be used to store the details from the inventory, update the stock based on the sale details, generate receipts for sales, produce sales and inventory reviews periodically etc.

Programming
Task 1
a
b
a) Write a Java method to compute the average of five numbers
import java.util.Scanner;
public class Avg5 {
public static void main(String[] args) {
Scanner in = new Scanner(System.in);
System.out.print("Input first number: ");
int num1 = in.nextInt();
System.out.print("Input second number: ");
int num2 = in.nextInt();
System.out.print("Input third number: ");
int num3 = in.nextInt();
System.out.print("Input fourth number: ");
int num4 = in.nextInt();
System.out.print("Enter fifth number: ");
int num5 = in.nextInt();
System.out.println("Average of five numbers is: " +
(num1 + num2 + num3 + num4 + num5) / 5);
}
}
b) Write a Java method to count all words in a string.

import java.util.Scanner;
public class wordcount {
public static void main(String[] args)
{
Scanner in = new Scanner(System.in);
System.out.print("Input the string: ");
String str = in.nextLine();
System.out.print("Number of words in the string: " + count_Words(str)+"\n");
}
public static intcount_Words(String str)
{
int count = 0;
if (!(" ".equals(str.substring(0, 1))) || !(" ".equals(str.substring(str.length() -
1))))
{
for (int i = 0; i <str.length(); i++)
{
if (str.charAt(i) == ' ')
{
count++;
}
}
count = count + 1;
}
return count; // returns 0 if string starts or ends with space " ".
}
}
Task 2
Class Diagram

 Employee Table related to depart table.
 Department table related to Company table.
 Project table is related to company tables.
Task 3
a) In a maximum of 500 words, critically evaluate the principles of object oriented
programming.
In respect to implement the oriented programming, it has been considered that
predominant paradigm consist important role in Java to targeted. Along with this, it is probably
used in the different language by service providers (Bailie, Blank and Rajaravivarma, 2003).
Students of Java considered subjective programming which is used in the introductory courses.

Therefore, it allows to considered later introduction which needed for logical and functional
encoding. In this regard, OOP assists to launch students concepts towards the specification,
construction and resistant.
In this approach, it is has determines that functions are begun with the interfaces, classes
and considered with the OOP based programming. Therefore, it assists to look towards the
several lecturers that present outside teaching approach in the courses. Programs are also
compilation which are mainly connected with different students. It influences to the learning
outcomes and enthusiasm with interest which could be reached out with the program that assists
to look upon the important elements that are needed in the research. In addition to this,
introductory courses are also implemented ideas and object-orientated participants (Bailie,
Courtney and Tuohy, 2003). Programming and software are also creates growth which impact on
the learning. Therefore, it is important to look upon the encoding. Courses offered in the
university regarding Stuttgart and Encoding techniques in which study courses considered in
information management automative. In addition to this, it is also useful to focus on the using
outstanding activities in the education program that carried to implement software in German
universities.
In this aspect, major obstacles replaced with the Eiffel simply by Java. Therefore, it is
more patrictic in term of subject oriented.
For example, it is essential to have permanent method that is important for Coffee. This is
because all the methods are executed with everlasting main methods. Mian concept behind
carrying out program is Eiffel is required to be considered to be early (Janke, Brune and Wagner,
2015). When comparison is made with Eiffel, then Java does not have local support for contract.
This way, additional toolsare require to be applied. Two classes at Ulm and Stuttgart distinctly
differ are the scope. All the programming that are with Software Development (PSD) with
Stuttgart consists of four hrs lecture. Further, there are also two days tutorials with teaching
colleagues per week. All the programming Technique that are inside Ulm consists of two hours
lecture. Apart from this, it also has two period lecturer-guided tutorials. In addition to this, there
are only two additional hours of recommended tutorial per week are offered. Several topics like
the setup as well as the functional principle of a personal computer or data structures are
generally units of separate address courses at Ulm. This is considered to be the main reason these
units are not included here. When it is compared with Ulm, at Stuttgart, there are different type
of issues are discussed during a session. PSD at Stuttgart resembles are focused to computer
engineering (Bruegge, 1992). The aim of the course can be a broad introduction to the field about
computer science and at the very least to strike all simple topics. Hence, topics just like the
principles of computer hardware or maybe the complexity of algorithms may also be briefly
discussed.
b) In clear terms, explain your understanding of each of the following object-orientated
programming concepts:
i) Objects
This is considered to be the components for program that is able to perform certain
actions and it also has the capability to interact with other elements of program. Objects

are determined to be the basic units for object oriented programming. One of the example
that can be used is of a person (Cohen, 1987). It is a common expectations for a person to
have a name. Further, this is considered to be one of the property of a person. As per
some of the expectations that individuals have consists of driving or walking, etc. These
are stated to be the methods of the person.
ii) Classes
A class ide determined to be the blueprint of an object. As per individual perception,
class is considered to be concept. On the other hand, object is embodiment of that
concept. It is important for one to have a class before one can create object. This can be
understood with the help of an example. Suppose one person is willing to use a person in
program (Cooper, Dann and Pausch, 2003). In this context, it is required by the person to
describe them and by asking him/her to person something. This way, the person will
describe the individual and them they will show what they can do. Conducting person
will create an object for that particular person. This one is able to describe the person and
to make them person any type of activity with which they are comfortable with.
iii) Methods
In object, method is considered to be the oriented programming is a type of programming
that is related with class. Further, it is also considered to be the A method defines the
behavior of the objects that are created from the class. In another words, method is a set
of action which is object is able to perform in effective manner. In this context, binding is
stated to be association between class and method (Corbin and Strauss, 2008). In consider
the example, it can be stated that an object is a person that is created by making use of
person class. All the methods that are related with this class consists of various things like
driving and walking. There are situations in which methods are sometimes confused with
functions but they are distinct.
Task 4
Online Sales and Inventory Management System (SIMS)
ABSTRACT

An internet Sales and Inventory Management (SIMS) for a departmental store. This method can
be used to store the details from the inventory, update the stock based on the sale details,
generate receipts for sales, produce sales and inventory reviews periodically etc . This is 1
integrated system that contains both user component (used through salespersons, sales managers,
supply managers etc) and the administrative component (used by the managers for performing
admin degree functions such as adding brand new items to the inventory, altering the price of an
item etc).
This technique runs on multiple définitif, offers a GUI interface in order to its users and connects
to some common database(s).
Existing System:-
From the existing system the income can purchase the products only guide book nothing but he
went to typically the supermarket buying the goods with this no reliability after purchasing the
products some time returns is simply not allowed or if let every we need go to retailers return to
the goods it is time taking in process. In farmer nights online shopping sites not maintain the
almost all much products (Janke, Brune and Wagner, 2015). When we desire to purchase the
products redirect straight into different sites and buying in the event that the user need to
maintain just about all sites transaction. It is not easy to manage.
Proposed System:-
This particular project is to developed to have an online Sales and Stock Management
System (SIMS) for a chain store. This system can be used to store the facts of the inventory,
update the actual inventory based on the sale information, produce receipts for product sales,
generate sales and stock reports periodically etc . This really is one integrated system which has
both the user component (used by salespersons, sales administrators, inventory managers etc)
and also the admin component (used through the administrators for performing administrative
level functions such as including new items to the supply, changing the price of an item etc).
This system runs on several terminals, offers a GUI user interface to its users and links to
a common database(s).
MODULES:-
This project is aimed at developing an online Sales and Inventory Management System
(SIMS) for a departmental store.
The Project has the following modules
o Sales Manager

o Sales Person
o Inventory Manager
o Admin
1. A sales person should be able to
o login to the system through the preliminary screen of the system
o change the password after signing into the system
o see the actual status of the inventory, for example, whether a particular item can be
obtained or not etc.
o search for an item by typing the original letters (Jadud, 2005)
o enter the items bought by a customer and create a bill for the same (the expenses will
have a unique sale identification, date, time, item/quantity/price information etc)
o cancel the created bill, in case of error within entering the details, and make a new
one
o take back again an already sold product that is not satisfactory to the client (the shop
allows that) and produce a receipt for the similar
o inform the inventory office manager about the items that are not accessible, so that
they can be stocked
o inform the sales manager regarding any exceptions (such being an item is being
purchased, however it is not available in the system)
o get help about the program on how to use the different features from the system
2. The inventory manager should be able to
o login to the system/change his username and password after logging in and so on
o check the status from the inventory
o see the information from sales people about goods that are not available and need
being kept in the inventory
o validate the inventory against the income done in the previous day (whether the
items that are sold plus the change in the inventory to the corresponding items
match etc)
o generate inventory reports in the items category-wise, price-wise and so forth

o generate inventory-trends (like precisely how is coffee powder commodity
changing over the month)
3. The sales manager should be able to
o check how many bills have already been generated in the day thus far
o check how much money is transacted in the day so far
o check how many bills have been baulked so far in the day(due to help
wrong entry by the gross sales persons)
o check how many objects have been returned so far inside day
4. The administrator should be able to
o login to the system and transform his password after visiting in
o add new people to the system
o add brand-new items/categories to the inventory
SOFTWARE USED:
Language : C#.NET
Technologies : Microsoft.NET, ASP.NET, ADO.NET
Database : MS SQL SERVER 2005
IDE : Visual Studio 2008
Operating System : Microsoft Windows XP or Later Version
HARDWARE USED:
1.1.1. Processor : Pentium IV
1.1.2. Hard Disk : 2GB
1.1.3. RAM : 512MB
Use Case Diagram

Use Case Diagram

Use Case Diagram

Functional components of the project
Following is a list of functionalities of the system. More functionalities that you find appropriate
can be added to this list. And, in places where the description of a functionality is not adequate,
you can make appropriate assumptions and proceed.
There are registered people in the system (sales people working in the shop, inventory managers,
admin et al). Each one of them may have some exclusive privileges (admin, for example, could
create new users to the system whereas sales people cannot).
Requirements Specification (RS)
Following is a template for the RS document. Some example requirements are entered in to it to
show how to use the template. Make sure that you enter even the smallest/most trivial
requirements also. That would help in validating the system during testing.
No. Requirement Essential
or
Description of the
Requirement
Remarks

Desirable
RS1 The system should have a
login
Essential A login box should
appear when the system
is invoked.
The logins are
assigned by
the admin
RS2 The system should have
help screens
Essential Help about the various
features of the system
should be provided in
sufficient detail in a
Q&A format.
In addition to
the features of
the system,
the list of
sales people/
sales
managers etc
should also be
present.
RS3 The system should ‘lock’
the login id if wrong
password is entered 3
times in a row
Desirable This feature will
improve the robustness
of the application
Since the
application is
going to be
used only by
the people
inside the
shop, this
feature is not
essential.
However, if
time is there,
this will be
implemented.
RS4 The sales person should
be able to produce a bill
for the items bought by a
customer
Essential The sales person should
be able to find all the
items bought by the
customer (if not, there
should be some other
general way of entering
the details temporarily)
and find the price per
unit for each of the item
(some may be in
numbers, some may be
in kilograms etc)
This is a basic
requirement
which has
some
additional
requirements
like totalling
the amount etc
Manpower requirements
2 to 3 students can complete this in 4 – 6 months if they work fulltime on it.
Inventory/Sales/User Databases Fields Specification
A database to store the details about the items in the inventory should be designed. A unique
code should be given for each item in the inventory. This will be the key of the database.

A database to store the sales details should be there. The key for this database is the unique sale
id generated when producing the bill. Some example fields in this database are: the list of items
bought under the sale id (a maximum of up to 30 item codes can be there), the date and time of
the transaction, the total amount of the transaction, whether the customer paid by cash or card,
whether any item was returned later etc
A database to store the user details should be there. The key for this database is the user id. This
database will have the user details like his encrypted password, his leave/shift details etc.
Some example fields and the range of valid values for those fields for the inventory database are
given below. These need not be taken as such. They can be modified by the team
No. Field Name Range of valid values for
the field
Remarks
1 Item Id Any valid 5 digit number
(say, 00001 to 99999)
This is the key field of the database.
You can have some alphanumeric
characters in the beginning to show
the category of the item (‘VEG’
may mean the item is a vegetable,
for example)
2 Name of the
Item
Up to 25 characters in
length.
If a name exceeds 25 characters, the
first 25 characters are taken
3 Category of
the item
Any alphanumeric code
with a maximum of 5
characters
Some items might belong to more
than one category. In that case, they
are linked to the most appropriate
category.
4 Units in
which the
item is
measured
This can be a set of pre-
defined values such as
‘KG’, ‘Litter’, ‘Pieces’,
‘Meters’ etc
This should be modifiable by the
admin. (Bananas, for example, may
be bought per kg)
5 Number of
such units
available
currently in
the inventory
Any valid 5 digit number
(say, 00001 to 99999)
This will keep changing as and
when items are bought or returned.
6 Number of
such units that
were available
at close of the
previous day
Any valid 5 digit number
(say, 00001 to 99999)
This does not change normally,
during the day. However, the
inventory manager can change it if
he finds some manual error like a
bill is not made properly etc
High Level/Detailed Design (HLD/DD)
Overview of the system
Provide a block diagram depicting where the database will be located, where the application will
run etc. Also, provide details about the database server that is going to be used etc.
Design Components

Split the system into its design components. In this case, the components would be user-
verification, sale transaction handler, sale cancellation handler, trend generator for
inventory/sales, report generator for inventory/sales etc. For each of the components, provide
information in the following format. User-verification component is taken as the example.
Component one
User-verification
Purpose
This component will verify if the user who is trying to access the system is a valid user.
Test-Plan (TP)
The test-plan is basically a list of testcases that need to be run on the system. Some of the
testcases can be run independently for some components (report generation from the database,
for example, can be tested independently) and some of the testcases require the whole system to
be ready for their execution. It is better to test each component as and when it is ready before
integrating the components.
It is important to note that the testcases cover all the aspects of the system (ie, all the
requirements stated in the RS document).
No. Testcase Title Description Expected
Outcome
The
requireme
nt in RS
that is
being
tested
Result
1 Successful User
Verification
The login to the system
should be tried with the
login assigned by the
admin and the correct
password
Login
should be
successful
and the user
should enter
in to the
system
RS1 Passed
2 Unsuccessful
User
Verification due
to wrong
password
Login to the system
with a wrong password
Login
should fail
with an
error
‘Invalid
Password’
RS1 Passed
3 Unsuccessful
User
Verification due
to invalid login
id
Login to the system
with a invalid login id
Login
should fail
with an
error
‘Invalid user
id’
RS1 Passed
4 Successful sale
transaction
A customer buys
several items and
submits them for
A sales
receipt with
a unique id
RS4 Passed

billing. The sales
person gets each item,
calculates the quantity,
calculates the total and
produces a bill using
the system
and with
correct
details is
printed out.
The
inventory
and sales
databased
are modified
appropriatel
y
5
Steps to start-off the project
The following steps will be helpful to start off the project.
1. Study and be comfortable with technologies such as Java/Visual Basic, SQL server/MS-
Access etc. Some links to these technologies are given in the ‘Guidelines and References’
section of this document
2. Make a database of items/categories
3. Make a list of sales persons/managers/administrator who would be using the system
4. Create the front-page of the system giving a brief description about the system and a
login box
5. Create the help-pages of the system in the form of Q&A. This will help you also when
implementing the system
Create other sub-systems like error notification, screens for various functions (like purchase,
cancellation, return of items, admin pages etc)
Milestones and Timelines
Number Milestone
Name
Milestone
Description
Timeline
Week no.
from the
start
of the
project
Remarks
1 Requirements
Specification
Complete
specification of the
system (with
appropriate
assumptions)
including the database
design (for storing the
1-2 Attempt should be made to
add some more relevant
functionalities other than
those that are listed in this
document.
And, attempt should be made

items details). A
document detailing
the same should be
written and a
presentation on that be
made.
to present an overall view of
the system which makes
sense for the users of the
system.
2 Technology
familiarization
Understanding of the
technology needed to
implement the project.
3-4 The presentation should be
from the point of view of
being able to apply it to the
project, rather than from a
theoretical perspective.
3 High-level and
Detailed
Design
Listing down all
possible scenarios
(like searching for an
item, producing a bill,
cancelling a bill,
notifying about items
that are out of stock,
adding a new user,
adding a new item etc)
and then coming up
with flow-charts or
pseudocode to handle
the scenario.
5-7 The scenarios should map to
the requirement specification
(ie, for each requirement that
is specified, a corresponding
scenario should be there).
4 Implementatio
n of the front-
end of the
system
Implementation of the
main screen giving the
login, screen that
follows the login
giving various
options, screens for
sales persons/ sales
manager/ inventory
manager and the
administrator for the
various functions etc.
7-9 During this milestone period,
it would be a good idea for
the team (or one person from
the team) to start working on
a test-plan for the entire
system. This test-plan can be
updated as and when new
scenarios come to mind.
The test scenarios can be
grouped under the respective
user who would be
associated with it (producing
a bill, for example, can be
grouped under ‘sales
persons’ testcases)
5 Integrating the
front-end with
the database
The front-end
developed in the
earlier milestone will
now be able to update
the sales/inventory
database. Other
10-12

features like report
generation etc should
be functional at this
stage. In short, the
system should be
ready for integration
testing.
6 Integration
Testing
The system should be
thoroughly tested by
running all the
testcases written for
the system (from
milestone 5).
13-14 Another 2 weeks should be
there to handle any issues
found during testing of the
system. After that, the final
demo can be arranged.
7 Final Review Issues found during
the previous milestone
are fixed and the
system is ready for the
final review.
15-16 During the final review of
the project, it should be
checked that all the
requirements specified
during milestone number 1
are fulfilled (or appropriate
reasons given for not
fulfilling the same)
Conclusion
Shop Management System has some flows as well as limitation due to different specifications
and time constrain. Because application will be used on the computer systems so the end user
must have the fundamental knowledge of the computers. Presently only one item’ information
could be enter in the system at a time. The consumer has to enter information several items. The
system currently offers only one combination of username and password qualifications, every
user has to discuss same credentials. The lookup function only supports research using ID
number. The person has to get ID amount of customer, sales, purchase, item, or supplier to
search inside the system.
REFERENCES
Bailie, F., Blank, G. and Rajaravivarma, R., 2003. Java visualization using BlueJ. Journal of
Computing Sciences in Colleges, 18(3), pp.175-176.
Bailie, F., Courtney, M. and Tuohy, S., 2003. Objects First-does it work?. Journal of Computing
Sciences in Colleges, 19(2), pp.303-305.

Janke, E., Brune, P. and Wagner, S., 2015, May. Does outside-in teaching improve the learning
of object-oriented programming?. In Proceedings of the 37th International Conference on
Software Engineering-Volume 2 (pp. 408-417). IEEE Press.
Bruegge, B., 1992, October. Teaching an industry-oriented software engineering course. In SEI
Conference on Software Engineering Education (pp. 63-87). Springer, Berlin, Heidelberg.
Cohen, B., 1987. The education of the information systems engineer. Electronics and
Power, 33(3), pp.203-205.
Cooper, S., Dann, W. and Pausch, R., 2003, February. Teaching objects-first in introductory
computer science. In ACM SIGCSE Bulletin (Vol. 35, No. 1, pp. 191-195). ACM.
Corbin, J. and Strauss, A., 2008. Basics of qualitative research: Techniques and procedures for
developing grounded theory.
Janke, E., Brune, P. and Wagner, S., 2015, May. Does outside-in teaching improve the learning
of object-oriented programming?. In Proceedings of the 37th International Conference on
Software Engineering-Volume 2 (pp. 408-417). IEEE Press.
Jadud, M.C., 2005. A first look at novice compilation behaviour using BlueJ. Computer Science
Education, 15(1), pp.25-40.
Bailie, Blank and Rajaravivarma, 2003. Bailie, Courtney and Tuohy, 2003Janke, Brune and
Wagner, 2015Bruegge, 1992Cohen, 1987Cooper, Dann and Pausch, 2003Corbin and Strauss,
2008Janke, Brune and Wagner, 2015Jadud, 2005