Store Management System

STORE MANAGEMENT SYSTEM
1
2
COMPANY PROFILE
ABOUT ORGANIZATION
An enterprise solution provider since 2001, Hex Business Software Solution is a dynamic
company supplying ERP solutions to the Small and Medium Enterprises in Delhi, NCR.
Since our incorporation, we have continuously enhanced our people skill and competence to
benefit our customers.
The company’s unique experience in providing ERP solutions to the SME segment, (i.e.
supplying ERP solutions to small enterprises first then growing to the medium size ) has
enable us to gain valuable insight not only to the needs and requirements of the customer but
Also the requirements of the customer but also the requirements of being a successful SME
Solutions provider.
The key factor of our success is our people. Our professional consultants comprise of highly
qualified and skilled individuals with many years of experience in business consulting and
implementation. Among them are qualified CPIMs (Certified in Production and Inventory
Management) and MCSEs (Microsoft Certified System Engineers) and MCA (Master Of
Computer Application).
CULTURE
 To always put our customer first.
 To continuously learn and knowledge sharing.
 To be honest, open, reliable and responsible in everything we do
3
WE DELIVER (PDCA):
 "Plan" develops an action plan to address customers' deliverables. Create
corresponding control points and parameters. A plan that is reviewed and agreed
by customer
 "Do" implement the define Plan
 "Check" collects information on control points and parameters. To compare actual

result to expected results.
 "Act" identifies corrective action(s). Analyze, identify, discuss and agree on
 The results and causes of any differences between expected and actual results.
Our Vision and Mission

Vision Statement
"Together we create the enterprises of tomorrow"
Mission Statement
“To provide world-class information technology solutions and services to enable our
customers to serve their customers better”
ERP Package is developed with the idea of a Modular Design, so that even if we
want to implement one area, we can do it without the rigidity of implementing all the
areas. The complete ERP Package is developed in VB6 and SQL Server 2000 and Seagate
Crystal Reports which are one of the world's best tools as on date. Our applications run
outstandingly in the Windows NT/Windows 2K.
ERP Features
 Extremely user friendly and no need for trained users.
4
 Caters to Multiple Companies, Multiple Divisions, Multiple Units and Multiple Stores.
 Reports as per Indian Conditions for all kinds of Statutory Records.
 Reports in the GUI (Laser/Ink Jet), Text (DMP), Grid, Graph Formats.
 Reports can be drilled down and its generating document.
 Reports can be sent as E-Mail attachment or Exported to Excel.
 Users can make their own menu with the help of Menu Designer.
 Data Security.
 Data integration and locking for error free working.
Our EMS (Enterprise Management System) ERP Package is ready to be implemented for
any manufacturing and trading company. We also provide Specific Customized Software.
Our ERP software solutions are widely recognized by numerous industrial units. Our aim
is to create easy and efficient Enterprise Resource Planning software solution that caters to
all the industries.
SERVICES
Hex Business Software Solutions offers comprehensive classroom training that
reengineers to customers' business operations.
WE DELIVER:
 On-site and off-site Training
 Training material and syllabus reengineered to individual customer
 Small classroom that allows trainer to provide full attention
 Experienced and knowledgeable trainers
5
IMPLIMENTATION
Hex Business Software Solutions experienced implementers with CPIM provides an
assured success in implementing in shortest time without compromising customer
objectives and goals.
WE DELIVER:
 Understand customers' needs and goals
 On-Site Implementation with step-by-step implementation procedures
 Mapped reengineered Site Assessment
 Flexibility and scalability implementation that best fit the customers' operations
 Working in aligned with customers' projected implementation schedule
SUPPORT
Hex Business Software Solutions with its Technical Support team who has excellent
product knowledge and many years of experience assures customers' are provided with
best service.
WE DELIVER:
 "Hot-Line" telephone, hand phone calls and emails support
 Remote Access to customer site over a secured WAN.
Contact Information: Address:
Mr. Deep Dua 5L/4,N.I.T Faridabad

CEO (Chief Executive Officer) HARYANA-121001
HEX BUSINESS SOFTWARE SOLUTIONS E_MAIL: hex_bss@yahoo.co.in
6
ORGANIZATION CHART
7
8
HARDWARE AND SOFTWARE REQUIREMENTS
Operating System And Software Used
The project has been developed using Windows XP Professional Operating System Microsoft
Corporation.
The Back- end software used is a SQL Server. All the tables are prepared under this . Insertion
and abstraction of data is done into and from this.
The Front – end software is a programming language VISUAL BASIC (6.0) from Microsoft
Corporation. This is used for interaction of the user with the database.
Minimum System Requirement
 MS WINDOWS 9X
 HARD DISK with minimum of 200 MB free space for full installation
 VGA or Higher Resolution Screen
 64 MB of RAM
Hardware Specification
Processor :
CPU : Pentium IV
Speed : 800 MHZ
9
VISUAL BASIC
Microsoft Visual Basic, the fastest and easiest way to create applications for Microsoft
Windows. Whether you are an experienced professional or brand new to Windows
Programming, Visual Basic provides you with a complete set of tools to simplify rapid
application development.
So what is Visual Basic ? The “Visual” part refers to the method used to create the graphical
user interface (GUI). Rather than writing numerous lines of code to describe the appearance and
location of interface elements, you simply drag and drop pre built objects into place on screen.
The “Basic” part refers to the BASIC (Beginners all-purpose symbolic instruction code)
language, a language used by more programmers than any other language in the history of
computing. Visual Basic has evolved from the original BASIC language and now contain several
hundred statements, functions and keywords, many of which relate directly to the Windows GUI.
Beginners can create useful applications by learning just a few of the keywords, yet the power of
the language allows professionals to accomplish anything that can be accomplished using any
other Windows Programming Language.
Whether your goal is to create a small utility for yourself or your work group, a large enterprise-
wide system, or even distributed applications spanning the globe via the Internet, Visual Basic
has the tools you need.
Data access features allow you to create databases and front-end applications for most popular
database formats, including Microsoft SQL Server and other enterprise-level databases.
ActiveX technologies allow you to use the functionality provided by other applications, such as
Microsoft Word Processor, Microsoft Excel Spreadsheet, and other Windows applications.
10
You can even automate applications and objects created using the Professional or Enterprise
editions of Visual Basic
Internet Capabilities make it easy to provide access to documents and applications across the
Internet from within the application.
Your finished application is a true .exe file that uses a run-time dynamic link library (DLL) that
you can freely distribute.
Visual Basic Editions
Visual Basic is available in three versions, each geared to meet a specific set of development
requirements.
The Visual Basic learning edition allows programmers to easily create powerful applications for
Microsoft Windows 95 and Windows NT. It includes all intrinsic controls, plus grid, tab, and
Databound controls.
The professional edition provides computer professionals with a full-featured set of tools for
developing solutions for others. It includes all the features of the learning edition, plus additional
ActiveX controls, including Internet controls, and the Crystal Report Writer. Documentation
provided with the Professional edition includes the Programmer’s Guide, Online Help, the
Component Tools Guide and the Crystal Reports for Visual Basic User’s Manual.
The Enterprise edition allows professionals to create robust distributed applications in a team
setting. It includes all the features of the Professional Edition , plus the Automation Manager,
Component Manager, Database Management Tools, the Microsoft Visual SourceSafe project-
oriented version control system, and more. Printed documentation provided with the Enterprise
11
Edition includes all Professional edition pieces, plus the Building Client/Server applications with
Visual Basic book and the SourceSafe User’s Guide.
SQL Server
SQL Server Enterprise Manager
Microsoft® Management Console (MMC) is a tool that presents a common interface for
managing different server applications in a Microsoft Windows® network. Server applications
provide a component called an MMC snap-in that presents MMC users with a user interface for
managing the server application. SQL Server Enterprise Manager is the Microsoft SQL
Server™ MMC snap-in.
SQL Server Enterprise Manager is the primary administrative tool for SQL Server and provides
an MMC-compliant user interface that allows users to:
 Define groups of SQL Server instances.

 Register individual servers in a group.
 Configure all SQL Server options for each registered server.
 Create and administer all SQL Server databases, objects, logins, users, and permissions in
each registered server.
 Define and execute all SQL Server administrative tasks on each registered server.
 Design and test SQL statements, batches, and scripts interactively by invoking SQL Query
Analyzer.
 Invoke the various wizards defined for SQL Server.
Creating and Maintaining Databases
Designing your Microsoft® SQL Server™ 2000 database structure involves creating and
maintaining a number of interrelated components.
12
Database component Description
 Databases contain the objects used to represent, manage, and access data.
 Tables Store rows of data and define the relationships between multiple tables.
 Indexes optimize the speed of accessing the data in the table.
 Views Provide an alternate way of looking at the data in one or more tables.
 Stored Procedures Centralize business rules, tasks, and processes within the server using
Transact-SQL programs.
 Triggers Centralize business rules, tasks, and processes within the server using special types
of stored procedures that are only executed when data in a table is modified.
Accessing And Changing Data
SQL Server Enterprise Manager includes a tool for designing queries interactively using a
graphical user interface. These queries are used:
 In views.
 In Data Transformation Services (DTS) Packages.
 To display the data in Microsoft® SQL Server™ tables.
Optimizing Database Performance

The goal of optimizing database performance is to minimize the response time for each query
and to maximize the throughput of the entire database server by minimizing network traffic, disk
I/O, and CPU time. Understanding how to design the logical and physical structure of the data,
tune queries, and configure Microsoft® SQL Server™ 2000 and the operating system can help
optimizes database performance.
13
Replication
Microsoft® SQL Server™ 2000 replication is the process of copying and distributing data and
database objects from one database to another and then synchronizing between databases for
consistency.
Using replication, you can distribute data to different locations, to remote or mobile users over a
local area network, using a dial-up connection, and over the Internet. Replication also allows you
to enhance application performance, physically separate data based on how it is used (for
example, to separate online transaction processing (OLTP) and decision support systems), or
distribute database processing across multiple servers.
Data Transformation Services
This section contains procedures for:
 Using Data Transformation Services (DTS) tools.

 Using DTS connections, tasks, transformations, and workflow elements to build DTS
packages.
 Managing packages.
Crystal Report 8.0

Crystal report 8.0 is stand-alone software. It is a software of Seagate Corporation which is
famous among the hardware maker. It is very powerful tools for generating reports and for
printout reports also. We can create report according to the result required. The report can be
presentable in pictorial form and printout can also be taken. Seagate Crystal Report 8.0 can be
interacted with Visual Basic 5.0 and Visual Basic 6.0. Through Visual Basic values can be sent
to the report generated in crystal report and the preview of report can be taken in the Visual
Basic software and print out of that can also be taken.
14
Purpose Of Report
Reports are management tools. There purpose is to help you quickly grasp the essential elements
and relationships found in raw data, to help you make effective decisions. For a report to be
effective, it has to present the correct data in a logical way. If it presents the wrong data, or if it
Presents the right data in haphazard manner, the report may slow the decision-making process or
may even encourage incorrect decisions.
The purpose statement helps you focus on your primary needs, and it gives the report both a
starting point and a goal. Here are some examples of purpose statements.
 The purpose of this report is to show monthly and year-to-date sales by sales representatives,
compare this year’s numbers to last year’s, and flag representatives whose sales figures do
not meet company standards.
 The purpose of this report is to show sales activity for each item in inventory, and to suggest
reorder quantities based on that activity.
Crystal Report And Back-End
Crystal reports come with front-end drivers to make it fully compatible with the ODBC system.
In addition, the Crystal reports package includes back end ODBC drivers that allow you to use
data stored in SQL Server.
Though Crystal Report is compatible with many popular database formats, you may be using a
DBMS that is not currently available through Crystal reports. Your DBMS may, however,
provide an ODBC driver that allows Crystal Reports to use your data through the ODBC system.
Adding Database To Report
Databases can be added to the Crystal Report. The number of databases added to report can vary
according to the need of the report required. But there must be linking between the
15
Databases/Tables i.e. there must be link between fields of two tables which belong to same
database or to the different databases.
Visual Linking Expert
We use the Visual Linking Expert to:
 Create smart links automatically between databases.

 Create new links.
 Update (modify) existing links.
 Delete existing links.
 Add new Databases/Tables to the report.
Design Tab
When working with Seagate Crystal Reports, you will probably use the Design tab more than
any other part of the program. The Design tab is the place you do most of the initial work when
creating a report. It designates and labels the various sections of the report. You can do the initial
formatting, place objects in the sections where you want them to appear, specify sorting,
grouping, and totaling needs, and so forth.
The Design tab provides a very efficient environment for designing a report because you work in
the tab with data representations, not with data itself. When a field is placed on the report, the
program uses a frame to identify the field on the tab; it does not retrieve the data. Thus, you can
add and delete fields and other objects, move them around, set up complex formulas, and more,
without tying up the computer or network resources needed to gather the data.
The report created in the Design tab is a kind of virtual report; it has the structure and
instructions for creating the final report, but it is not the report itself. To turn the Design tab
report into a final report or into a report that you can fine-tune, you "just add data." You do this
16
whenever you preview the report, print it, or output it in any other way. The actual data will now
appear in the report.
Design Tab Areas

Seagate Crystal Reports automatically create five areas in the Design Tab for new report.
 Report Header
This section is generally used for the report title and other information you want to appear at the
beginning of the report. It can also be used for charts and cross-tabs that include data for the
entire report.
 Page Header
This section is generally used for information that you want to appear at the top of each page.
This can include such things as chapter names, the name of the document, and other similar
information. This section can also be used to display field titles above the fields on a report.
 Details
This section is used for the body of the report, and is printed once per record. The bulk of the
report data generally appears in this section.
 Report Footer
This section is used for information you want to appear only once at the end of the report (such
as grand totals) and for charts and cross-tabs that include data for the entire report.
 Page Footer
This section usually contains the page number and any other information you want to appear on
the bottom of each page.
17
 Group Header
This section typically holds the group name field, and can be used to display charts or cross-tabs
that include data specific to the group. It is printed once at the beginning of a group.
 Group Footer
This section generally holds the summary value, if any, and can be used to display charts or
cross-tabs. It is printed once at the end of a group.
When a group, summary, or subtotal is added, the Group Header area appears directly above the
Details area and the Group Footer area appears directly below the Details area.
Preview Tab
To preview a report before printing it, click Print Preview on the Standard toolbar.
The program gathers the data, makes the necessary calculations, and displays the report in the
Preview tab. With the data in place, you can review the spacing and formatting of your report
and see the actual results of all your summaries, formula calculations, and record and group
selections.
In true WYSIWYG (What You See Is What You Get) fashion, you can work directly on this live
data, fine-tuning it until the report has the exact look you want.
Formula Field
Use the Formula Editor to create and edit formulas. The Formula Editor contains four main
windows.
Window Description of contents

Report Fields Report fields contain all database fields accessible for your
report. They also contain any formulas or groups already
created for the report.
Functions Functions are pre built procedures that return values. They
perform calculations such as average, sum, count, sin, trim,
18
and uppercase.
Operators Operators are the "action verbs" you use in formulas. They
describe an operation or an action to take place between two
or more values.
Changing the syntax from Crystal syntax to Basic syntax or vice versa will change the list of
functions in the Functions window as well as the list of operators in the Operators window. The
functions and operators differ from syntax to syntax.
Create a formula by double-clicking on any of the components listed in the Report Fields,
Functions, or Operators trees. When you choose a component, the required syntax is also
inserted. You can also manually enter a formula.
19
20
GANTT CHART
START DATE: 25 Dec, 2008
No. of weeks 4 8 12 16 20
Problem
Identification
Analysis
Data Base
Design
Designing of
Modules
Coding of
Modules
Testing &
Verification
Documentation
Phase
21
PERT CHART
The PERT chart follows:
3 6 9
10 d 20 d 14 d
2 5 8 11 12
1
10 d 8d 5d 5d 8d
4 7 10
d: represents the day require for particular task.
The numbers given the PERT CHART stands for the activities given below:
1. Starting of project
2. System Requirement Analysis & Feasibility Study
3. High Level Design
4. Procedural Design
5. Designing Input /Output Screens
6. Front-End Design
7. Back-End Design
8. Preparation of test cases, Scripts and Test data
9. Integration Testing
10. Acceptance Testing
11. Documentation
12. End
22
23
System Development Life Cycle
A system development life cycle is a logical process by which system analyst, software-
engineers, programmers, end-users build information-system and computer applications to solve
business problems and needs.
It is also called application development life cycle. The life cycle is essentially a perfect
management –tool to plan, execute and control system development projects. Systems
development life cycle defines the phases and tasks that are essential to system, development.
UNDERLYING PRINCIPLES OF A SYSTEM DEVELOPMENT
Get the users and the owners involved

The owner and user involvement is an absolute necessity for successful system development.
The users and owners must participate and proper agreement from the overall decision that may
effect them. The involvement of both will win the acceptance of new ideas and acknowledgeable
change.
Use the problem solving approach

The problem solving approach includes: -
 Study and understand the system problem and its contents.
 Define the requirement of a suitable solution.
 Identify the candidate solution and select the best alternative.
 Design and implement the solution.
 Observe and evaluate the solution impact and define the solution accordingly.
Here the system analyst should approach all projects using some sort of
problem solving approach.
24
Establish phases and activities

The life cycle consists of four phases: -
 System planning
 System requirement
 System feasibility
 System analysis
 System design
 System implementation
 System support
To understand system development, we need to recognize that a candidate system has a

life cycle, just like a living system or a new product. System analysis and design are keyed to the
system life cycle. The analyst must progress from one stage to another methodically, answering
key questions and achieving results in each stage.
We isolate and sequence these activities for learning purposes, but in real life they overlap
and are highly interrelated. For example, when the analyst is evaluating an existing operation,
he/she is probably thinking about an alternative way that would improve the system or
wondering whether a given piece of hardware would be critical cost item to consider for a
candidate system. Therefore, there can easily be overlap during any phase of cycle. Infact, it may
act as a basis for modifying earlier steps taken. We now describe each of these steps.
The traditional information system development cycle

 Understand the business problem or opportunity
 Develop an information system solution
 Implement the information system solutions
25
PHASES:
Initiation Phase
The initiation of a system (or project) begins when a business need or opportunity is identified. A
Project Manager should be appointed to manage the project. This business need is documented in
a Concept Proposal. After the Concept Proposal is approved, the System Concept Development
Phase begins.
System Concept Development Phase
Once a business need is approved, the approaches for accomplishing the concept are reviewed
for feasibility and appropriateness. The Systems Boundary Document identifies the scope of the
system and requires Senior Official approval and funding before beginning the Planning Phase.
Planning Phase
The concept is further developed to describe how the business will operate once the approved
system is implemented, and to assess how the system will impact employee and customer
privacy. To ensure the products and /or services provide the required capability on-time and
within budget, project resources, activities, schedules, tools, and reviews are defined.
Additionally, security certification and accreditation activities begin with the identification of
system security requirements and the completion of a high level vulnerability assessment.
Requirements Analysis Phase
Functional user requirements are formally defined and delineate the requirements in terms of
data, system performance, security, and maintainability requirements for the system. All
requirements are defined to a level of detail sufficient for systems design to proceed. All
26
requirements need to be measurable and testable and relate to the business need or opportunity
identified in the Initiation Phase.
Design Phase
The physical characteristics of the system are designed during this phase. The operating
environment is established, major subsystems and their inputs and outputs are defined, and
processes are allocated to resources. Everything requiring user input or approval must be
documented and reviewed by the user. The physical characteristics of the system are specified
and a detailed design is prepared. Subsystems identified during design are used to create a
detailed structure of the system. Each subsystem is partitioned into one or more design units or
modules. Detailed logic specifications are prepared for each software module.
Development Phase
The detailed specifications produced during the design phase are translated into hardware,
communications, and executable software. Software shall be unit tested, integrated, and retested
in a systematic manner. Hardware is assembled and tested.
Integration and Test Phase
The various components of the system are integrated and systematically tested. The user tests the
system to ensure that the functional requirements, as defined in the functional requirements
document, are satisfied by the developed or modified system. Prior to installing and operating the
system in a production environment, the system must undergo certification and accreditation
activities.
Implementation Phase
The system or system modifications are installed and made operational in a production
environment. The phase is initiated after the system has been tested and accepted by the user.
27
This phase continues until the system is operating in production in accordance with the defined
user requirements.
Operations and Maintenance Phase
The system operation is ongoing. The system is monitored for continued performance in
accordance with user requirements, and needed system modifications are incorporated. The
operational system is periodically assessed through In-Process Reviews to determine how the
system can be made more efficient and effective. Operations continue as long as the system can
be effectively adapted to respond to an organization’s needs. When modifications or changes are
identified as necessary, the system may reenter the planning phase.
Disposition Phase
The disposition activities ensure the orderly termination of the system and preserve the vital
information about the system so that some or all of the information may be reactivated in the
future if necessary. Particular emphasis is given to proper preservation of the data processed by
the system, so that the data is effectively migrated to another system or archived in accordance
with applicable records management regulations and policies, for potential future access.
SDLC Objectives
This guide was developed to disseminate proven practices to system developers, project
managers, program/account analysts and system owners/users throughout the DOJ. The specific
objectives expected include the following:
 To reduce the risk of project failure

 To consider system and data requirements throughout the entire life of the system
 To identify technical and management issues early
 To disclose all life cycle costs to guide business decisions
28
 To foster realistic expectations of what the systems will and will not provide
 To provide information to better balance programmatic, technical, management, and cost
aspects of proposed system development or modification
 To encourage periodic evaluations to identify systems that are no longer effective
 To measure progress and status for effective corrective action
 To support effective resource management and budget planning
 To consider meeting current and future business requirements
Key Principles
This guidance document refines traditional information system life cycle management
approaches to reflect the principles outlined in the following subsections. These are the
foundations for life cycle management.
Life Cycle Management should be used to ensure a Structured Approach to Information Systems
Development, Maintenance, and Operation.
29
SDLC FLOW DIAGRAM
System
Analysis
Design
Code
Testing
Maintenance
30
31
EXISTING SYSTEM
The present system is based on manual procedures involving the overall working of the system
or rather a non-system. There were various types of improper things happening in the industry,
which together led the industry towards downfall. The current scenario in the industry is that
they make entries manually in the registers or maintain the data in the Excel Sheet or in MS-
Access database which do not provide the answer to the queries that involve relationship amount
tables.
Accounting Vouchers are generated with the help of Tally which only provide maintenance of
the account details but do not provide scope and help for the various operations within the
industry.
LIMITATIONS OF EXISTING SYSTEM
The present system is based on manual procedures involving the overall working of the system
or rather a non-system. There were various types of improper things happening in the industry,
which together led the industry towards downfall. Some of these things were:
 Mismanagement of all the products (or parts) manufactured in the industry, this was
because of the fact that the parts were not even identified uniquely.
 Mismanagement regarding various types of tariff heads implied by government on

different types of products, where tariff head is a kind of duty paid to the government for
different products manufactured.
 Mismanagement regarding various parties or clients that are dealing with the given
industry and their different types of terms and conditions, because every client wanted to
32
deal with its own terms and conditions regarding what should be the payment terms, what
should be the delivery date and time, i.e., the delivery schedule.
 Mismanagement regarding various types of processes that are done onto different raw
materials to mold them into the finished components, because not every process is
required on every part rather there is a different process associated with each and every
part to convert into a finished product.
 Mismanagement regarding various types of parts that are going outside the premises of
the industry for some job work and then returning back to the company after being
modified, because when a part comes back after job work its identity changes.
 Mismanagement regarding the different types of challans made when the part is going
outside the industry’s premises for any reason other than sale.
 Delay in making Invoices when the finished component is ready to be dispatched as per
the sale schedule when the part is to be dispatched according to JIT (Just In Time).
33
PROPOSED SYSTEM (ERP)
ERP which stands for Enterprise Resource Planning, a business management system that
integrates all facts of a business including planning, manufacturing , sales , marketing. ERP
basically is the integration of all the departments in the enterprise. ERP is basically the demand
of modern business.
ERP systems are the management information systems that integrate and automate many of the
business practices associated with the operations or production and distribution aspects of a
company engaged in manufacturing products or services. It handles typically the manufacturing,
logistics, distribution, inventory, and shipping, invoicing and accounting for a company.
ERP systems are often called back office systems indicating that customers and the general
public are not directly involved. This is contrasted with front office systems like Customer
Relationship Management Systems that deal directly with customers or the e-Business systems
such as e-Commerce, e-Government Systems that deal with the suppliers or customers.
Our ERP project consists of around 110 modules like sale, purchase, production, accounting, job
order, masters etc. This project is basically made for manufacturing companies like Veegee
Enterprises (Faridabad), Rajhans Pressings Pvt. Ltd., Rajhans Industries Pvt. Ltd., YeeKay
Technocrat Pvt. Ltd. etc. Our project almost binds all the departments of the enterprise.
34
ERP (Enterprise Resource Planning)
Enterprise resource planning as a term derives from Material Resource Planning. Enterprise
resource planning systems (ERP) are management information systems that integrate and
automate many of the business practices associated with the operations or production aspects of a
company. These typically include manufacturing, logistics, distribution, inventory, shipping,
invoicing, and accounting. Enterprise Resource Planning or ERP software can aid in the control
of many business activities, like sales, delivery, billing, production, inventory management, and
Human Resource Management Systems.
They are often called back office systems indicating that customers and the general public are
not directly involved. This is contrasted with front office systems like customer relationship
management systems that deal directly with the customer.
ERP are cross-functional and enterprise wide. All functional departments that are involved in
operations or production are integrated in one system. In addition to manufacturing,
warehousing, and shipping, this would include accounting, human resources, marketing, and
strategic management.
In the early days of business computing, companies used to write their own software to control
their business processes. This is an expensive approach. Since many of these processes occur in
common across various types of businesses, common reusable software may provide cost-
effective alternatives to custom software. Thus some ERP software caters to a wide range of
industries from service sectors like software vendors and hospitals to manufacturing industries
and even to government departments.
35
ERP TOOL KIT
Effective forecasting, planning, and scheduling are fundamental to productivity–and ERP is a

fundamental way to achieve it. Properly implementing ERP will give you a competitive
advantage and help you run your business more effectively, efficiently, and responsively. This
toolkit is structured to support all the people involved in ERP implementation–from the CEO and
others in the executive suite to the people doing the detailed implementation work in sales,
marketing, manufacturing, purchasing, logistics, finance, and elsewhere.
This toolkit is not primarily about computers and software. Rather, its focus is on people–and
how to provide them with superior decision-making processes for customer order fulfillment,
supply chain management, financial planning, e-commerce, asset management, and more. This
comprehensive guide can be used as a selective reference for those, like top management, who
need only specific pieces of information or as a virtual checklist for those who can use detailed
guidance every step of the way.
Erp Also Includes
 Accounting software
 Manufacturing
 Marketing
 Management
 Information technology management
 Management information systems
 Supply chain management
 Material resource planning
 Human Resource Management Systems
36
ADVANTAGES OF ERP
The benefits from Enterprise Resource Planning are claimed to include:
 Lower inventory carrying costs.

 Lower ordering costs.
 Lower production costs.
 Lower accounting and record keeping costs.
 Lower transportation costs.
 Lower investment in equipment.
 Lower investment in plant.
 Lower investment in land.
 Reduced assembly-line down-times.
 More flexible production processes.
 More efficient lot sizes and scheduling.
 Reduced errors due to better coordination.
 The cost and efficiency improvements (mentioned above) could increase profitability or
increase market share (at a lower price)
 Reduced number of stock-outs.
 Reduced fulfillment times.
 Increase process transparency for the customer.
 Allow greater product customization, and thereby better match the exact needs of the
customer.
The customer satisfaction improvements (mentioned above) could increase sales volume,
increase sales revenue (due to a higher effective price, i.e. - no discounts), increase market share,
and increase profitability
37
DISADVANTAGES OF ERP
The limitations and pitfalls of the Enterprise Resource Planning are claimed to be:
 The systems can be very expensive to install and maintain some systems can be difficult to
use.
 The system is no better than the weakest link in the chain - a problem in one department or at
one of the partners will affect all the other participants.
If the ERP system is integrated with a supply chain management system, other potential
problems include:
 The system is vulnerable to a strike or labour problem at any one link in the chain.
 There can be transportation inefficiencies if small lots of product are transported several
times before reaching the consumer/user.
 Once a system is established, switching cost are very high for any one of the partners
(reduced flexibility and strategic control at the corporate level)
 The blurring of company boundaries can cause problems in accountability, lines of
responsibility, and employee morale
 There is a resistance to sharing sensitive internal information, information that may be
essential to the process.
 There are compatibility problems with the various legacy systems of all the partners.
38
39
Feasibility Study
A feasibility study is conducted to select the best system that meets performance requirement.
This entails an identification description, an evaluation of candidate system and the selection of
best system for he job. The system required performance is defined by a statement of constraints,
the identification of specific system objective and a description of outputs.
Feasibility study concerned with determining the cost effectiveness of various alternatives in the
designs of the information system & the priorities among the various system components. When
complex problems & opportunities are to be defined, it is generally desirable to conduct a
preliminary investigation called FEASIBILITY STUDY. Feasibility study is conducted to
obtain an overview of the problem & to roughly access whether the feasible solution exists prior
to committing substantial resources to an information systems development project. Feasibility
study involves investigating the information needs of the prospective end users & the objectives,
constraints, basic resource requirements, costs, benefits & Feasibility of a proposed project.
By intent, the Feasibility study is very rough analysis of the viability of the project. It is,
however, a highly desirable checkpoint that should be completed before committing more
resources.
 Do we have the business problem (or opportunity)?
 What is causing the problem?
 Would a new or improved information system help to solve the problem?
 What would be a feasible information system solution to our problem?
These are the questions that have to be answered in the systems investigation stage- the first step
preliminary study of the system in the system development process. This stage may involve
consideration of proposals generated by an information system planning process. The
investigation stage includes the screening, selection & preliminary study of proposed information
system solutions to business problems. The goal of feasibility studies is to evaluate alternative
systems & to propose the most feasible & desirable system for development.
40
STEPS IN FEASIBILITY STUDY
1) Form a project team and appoint a project leader.

2) Prepare system flow chart.
3) Enumerate potential candidate system.
4) Describe and identify characteristics of candidate system.
5) Describe and evaluate performance and cost effectiveness of each candidate
System.
6) Weight system performance and cost data
7) Select the best candidate system.
8) Prepare and report final project directive to management.
The key considerations in feasibility analysis are:

 Economic Feasibility
 Technical Feasibility
 Operational Feasibility
ECONOMICAL FEASIBILITY
It looks at the financial aspects of the project. It determines whether the management has enough
resources and budget to invest in the proposed system and the estimated time for the recovery of
cost incurred. It also determines whether it is worth while to invest the money in the proposed
project. Economic feasibility is determined by the means of cost benefit analysis. The proposed
system is economically feasible because the cost involved in purchasing the hardware and the
software is approachable. The personal cost like salaries of employees hired are also nominal,
because working in this system need not required a highly qualified professional. The operating-
environment costs are marginal. The less time involved also helped in its economical feasibility.
41
It was observed that the organization has already using computers for other purpose, so that there
is no additional cost to be incurred for adding this system to its computers.
The backend required for storing other details is also the same database that is Sql Server. The
computers in the organization are highly sophisticated and don’t needs extra components to load
the software. Hence the organization can implement the new system without any additional
expenditure. Hence, it is economically feasible.
The cost encompasses designing, installing and maintaining the system. It includes user training,
updating the physical facilities and documenting. System performance criteria are evaluated
against the cost effectively and also meet the performance requirements. The various costs and
benefits can be categorized into the following:
 Tangible and intangible cost and benefits.

 Direct and indirect costs and benefits.
 Fixed and variable costs and benefits.
 Savings versus cost advantages.
Once all the financial data has been identified and broken down into cost categories, it is
important to choose one of the evaluation methods. Prevalent among them are the following,
each with its own limitations and advantages:
1. Net benefit analysis.

2. Present value analysis.
3. Net present value.
4. Payback analysis.
5. Break-even analysis.
6. Cash-flow analysis.
42
TANGIBLE BENEFITS EXAMPLES
1) Decrease in information 1) Elimination of unnecessary

processing cost. documents.
2) Decrease in operating cost. 2) Reduction in inventory carrying

cost.
3) Decrease in required
investment. 3) Less spoilage, waste and idle
time.
4) Increase operational
efficiency.
INTANGIBLE BENEFITS EXAMPLES
1) Improved information 1) More timely and accurate

availability information.
2) Improved abilities in 2) Data mining.

analysis.
3) More timely service
3) Improved customer response.
services.
4) Improved employee morale.
TECHNICAL FEASIBILITY
Technical feasibility centers around the existing computer system (hardware/ software, etc.) and
to what extend it can support the proposed addition. This also involves financial considerations
to accommodate technical enhancements. If the budget is a serious constraint, then the project is
judged as not feasible.
43
The technical feasibility of the project can be evaluated by the fact that the organization is
currently in possession of IBM PC’s with their main database being Sql Server. However, since
an expansion is desirable; therefore; additional infrastructure does goes into buying additional
required PC’s and also since the fact that a change in the database is desired, installation of new
and authenticated software will be needed.
Technical feasibility can be demonstrated if reliable hardware and software capable of meeting
the needs of a proposed system can be acquired or developed by the business in the required
time. This is concerned with specifying equipment and software that will successfully satisfy the
user requirement. The technical needs of the system may vary considerably, but might include:
 The facility to produce outputs in a given time.

 Response time under certain conditions.
 Ability to process a certain volume of transaction at a particular speed.
 Facility to communicate data to distant locations.
We need to work with systems analysts and other end users to determine specific
information needs. For example, we need to determine what type of information they require;
what its format, volume, and frequency should be; and what response times are necessary.
Second, we must try to determine the information processing capabilities required for each
system activity (input, processing, output, storage and control) to meet these information needs.
We found in the earlier stages that the users were not satisfied with the way they are maintaining
the database because they didn’t have knowledge to maintain the database and to run a query
expert is required. So we proposed a new type of software completely developed in VB6.0 and
SQL SERVER2000. The advantage of this system is that it requires no other hardware and
software. The files developed in this language are easy to execute. And above all it is more user-
friendly. At this stage our main goal was to identify what should be done, not how to do it.
Finally, we tried to develop functional requirements. Functional requirements are end user
information requirements that are not tied to the hardware, software, network, data, and people
44
resources that end users presently use or might use in the new system. That is left to the design
stage to determine.
After examining technical feasibility, we give more importance to the configuration of the
system than the actual make of hardware. The configuration gives the complete picture about the
system’s requirements: ten to twelve workstations are required; these units should be
interconnected through LAN so that they could operate and communicate smoothly. They should
have enough speeds of inputs and output to achieve a particular quality of printing.
OPERATIONAL FEASIBILITY
The system will be used if it is developed well

 No major training and new skills are required as it is based data entry skills of the
operator.
 It will help in the time saving and fast processing and dispersal of user request and
applications.
 New product will provide all the benefits of present system with better performance.
 Improved information, better management and collection of the reports.
 User support.
 User involvement in the building of present system is sought to keep in mind the user
specific requirement and needs.
 User will have control over there own information. Important information such as pay-
slip can be generated at the click of a button.
 Faster and systematic processing of user application approval, allocation of IDs,
payments, etc. had greater chances of error due to wrong information entered by mistake.
Operational feasibility is the willingness and ability of the management, employee, customer,
suppliers and other to operate, use and support a proposed system. For example if the software
for a new system is too difficult to use, employees may make too many errors and avoid using it.
45
It is mainly related to human organizational and political aspects. The points to be considered
are:
 What changes will be brought with the system?

 What organization structures are distributed?
 What new skills will be required? Do the existing staff members have
these skills?
 If not, can they be trained in due course of time?
Generally project will not be rejected simply because of operational infeasibility but such
considerations are likely to critically affect the nature and scope of the eventual recommendation.
BEHAVIORIAL FEASIBILITY
People are inherent to change. In this type of feasibility check, we come to know if the newly
developed system will be taken and accepted by the working force i.e. the people who will use it.
46
47
PROBLEM ANALYSIS
Problem Recognition
Before starting the ERP project, the company was maintaining all the accounts in MS-ACCESS
or in TALLY. The system was good enough, but its working involves wastage of time. The
results achieved from this were too late. The process was also not full proof and not enough
storage space. Searching of old records use to take a lot of time.
Following were the main problem areas and limitation in the existing system that was
covered in the ERP project:
 Difficulty in Information Retrieval: As the data is very large, it is difficult to process

queries and becomes time consuming. Also, information retrieval is very difficult.
 Schedule Vs Supply: Schedule is mainly used in production, as it defines the time schedule
within which we have to supply the produced goods. Production is done with respect to the
time schedule provided by the company that places the order for production. The problem
related to this was that supply was not always according to the prescribed schedule.
Sometimes, dispatch was more than schedule and sometimes supply was less than schedule.
 Stock: As all the work was done manually, all the stock was placed under a single inventory
head. No proper location was maintained for different type of stock material. Thus proper
record for the stock material could not be maintained.
 Material-In Vs Material-Out: No records were maintained as such about how much stock
has been sent out for Job work and how much is received in return. This also led to the
payment for a particular Job work twice.
48
 Material Rejection: The Reason for Rejection of particular stock material was not known
which also sometimes led to the rejection of the correct stock material.
 Production: Due to non-availability of production data i.e. average production per hours,
efficiency ratio, and the company was not able to make proper plans for large-scale which
normally lead to over production and losses on investment in terms of stock.
 Difficulty in Maintenance Of Records: If multiple copies of the data is to be maintained

then it is difficult to keep track of records.
49
INTRODUCTION TO PROJECT
The Proposed project is customized software solution for the companies to maintain the stock at
the store. Proposed project will computerize all activities/facilities offered by the company to its
employees and customers.
Objective And Goals Of The Project

To develop software which automates all the aspects such as Sales, Purchase, Production,
Accounts, Job work for the Industries.
 Complete automation of the operations of the Sheet Metal Company.

 Increasing the speed of work.
 Decreasing the manual work while maintaining the reliability.
 Providing the facility like Data Warehousing.
 Maintaining consistent speed both at server as well as client side.
 Besides these operations, it must keep track of the resources of the company including
employees, machinery available.
About Project
Process of maintaining records for such a large service set up is quite cumbersome, time-
consuming and expansive to do manually. Besides, there are a lot of chances of human errors.
Due to these reasons only, a need is felt to develop computer-aided software which would be
comprehensive enough to quickly get all information and provide essential reports in desired
formats. This software will thus help the employees in different departments to get rid of the
burden of large number of data related to different sections. It overcomes all the limitations of
the manual system
50
51
I/O SPECIFICATION
PO No wise qty received and only

PURCHASE JOBWORK (OSP)
Accepted qty be added to store
Gives Detail of OSP
with Party name, Party
No.
PURCHASE
RETURN
Gives Invoice
No., Party Name
Gives PO No.
STORE GATE ENTRY
Issue Receive
WORK CENTER
52
53
FLOW DIAGRAM OF MATERIAL RECEIPT IN STORE

MODULE
START
STORE NAME
LOCATION NAME
GRN OF MATERIAL COMING

FROM OUTSIDE THE COMPANY
IS MATERIAL
FORWARD TO STORE
QUEUE? NO
B
Yes
SELECT THE STORE TYPE TO FORWARD
THE MATERIAL ACC TO MATERIAL TYPE
54
CONT…
A B
RECEIVE THE MATERIAL IN THE FORWARD THE MATERIAL

STORE DIRECTLY TO WORKCENTER
CHECK THE STOCK USING

REPORTS
STOP
55
FLOW DIAGRAM OF MATERIAL ISSUE IN STORE

MODULE
START
IS MATERIAL No
Yes
AVAIABLE IN
STORE?
PURCHASE THE MATERIAL FROM
OUTSIDE
FORWARD THE MATERIAL TO THE

Yes FOR PRODUCTION
WORK CENTER
No
IS THE PRODUCT
READY?
CHALLAN OUT THE MATERIAL
STOP
56
57
PROCESS MODELING
The technique of process modeling is used to describe the fact that the system consists of
various processes that work in conjugation to enable the system to work as a single unit. The
core of the model is the data dictionary while it is surrounded by the various other modeling
techniques. Data Flow Diagram (DFD) being one of those.
DFD serves two purposes:

1. To provide an indication of how data are transformed as they move through the system.
2. To depict the functions (and sub-functions) that transforms the data flow.
As information moves through the software, it is modified by a series of transformations. The

system accepts input in a variety of forms; applies hardware, software and human elements to
transform input into output in a variety of forms. Since DFD’s are a graphical technique that
depicts information flow, it is also known as data flow graph or bubble chart.
The DFD may be used to represent a system or software at any level of abstraction. In fact,
DFD’s may be partitioned into levels that represent increasing information flow and functional
detail. The basic notations used to create a DFD are illustrated below:
A producer or consumer of
External entity
Information that resides outside
The bounds of the system are to be
Modeled.
Process A transformer of information

(a function) resides within the
58
bounds of the system to be

modeled.
Data Object A data object; the arrowhead

Indicates the direction of the
Data flow.
Data store A repository of data that is to be

Stored for use by one or more
Processes; may be as simple as
A buffer or queue or as
Sophisticated as a relational
database.
The DFD may be used to represent a system or software at any level of abstraction. In fact,
DFDs may be partitioned into levels that represent increasing information flow and functional
detail.
59
CONTEXT LEVEL DFD
60
LEVEL-1 DFD
61
62
E-R Diagram for Store Module
63
64
About Project
Process of maintaining records for such a large service set up is quite cumbersome, time-
consuming and expansive to do manually. Besides, there are a lot of chances of human errors.
Due to these reasons only, a need is felt to develop computer-aided software which would be
comprehensive enough to quickly get all information and provide essential reports in desired
formats. This software will thus help the employees in different departments to get rid of the
burden of large number of data related to different sections. It overcomes all the limitations of
the manual system.
Project Will Have Following Blocks:
All the information that is used on a regular basis ad which does not rapidly change with time are
stored in Masters.
Store Master:-
The Module is not stand alone in itself but it is part of main project. It allows Users to define
various Stores such as Raw Material store, Finished Product store, Scrap store, Rg-1 Store,
B.O.P store.
Location Master:-
This block holds the information about the location of the store where the product is to be kept.
Example: Store Floor.
Inspection Parameter Master:-
This module records the name of the parameters on which the product is to be tested.
65
Employee Master:-
This block holds the information of the employees of the organization. Example: Name of
Employee, Department, Date of Joining etc.
Challan Out:-
This block holds the information of the material that is going out of the organization either for
sale or for job work.
GRN (Gate Receipt Note):-
This block makes the entry of the material that is coming in the organization either for
production or job work. After the GRN the material is passed to the store or directly to the work
center after inspection.
IMIR (Internal Material Inspection Report):-
When the material is received in the company then it is tested for its accuracy. If the material is
ok then it is forward to store or work center. Otherwise the line rejection of that material takes
place.
Line Rejection Voucher:-
The material that comes within the organization might not be up to the mark according to the
parameters assigned by the organization. Then that material is rejected and sent back using Line
Rejection Voucher.
66
Material Issue:-
Material that is in the store is issued to the different work centers depending upon the work that
has to be taken on the product. The details like the name of the work center, quantity of material
issued, name of the person to whom the material is issued etc. is noted in this block.
Material Receipt:-
The material that comes within the organization is received in the store using the material receipt
block of the project.
67
68
DATABASE DESIGN
DATA STRUCTURES
This part of the Design consist the overall database schema or we can say that tables which
consists various types of records. Tables of a database consists attributes, entities, and tupels for
storing and manipulating records.
Some of the tables are as follows:
Erp_Dbase_Employee_master
This table consists of the details of the employees in the organization.
69
Erp_Dbase_Location_Master
This table consists if the information regarding the location of the store.
Erp_Dbase_Challan_Out
This table makes the entry for the challan out of the material that is going out of the company.
70
Erp_Dbase_Store_Master
Erp_Dbase_GRN
This table is used to store the information of the gate entry of the material coming into the
company.
71
Erp_Dbase_Material_Receipt:
Erp_Dbase_Material_Issue:
72
Erp_Dbase_Line_Rejection_Voucher:
73
Erp_Dbase_IMIR:
74
75
STORE MASTER
The block is not stand alone in itself but it is part of main project. It allows Users to define
various Stores such as Raw Material store, Finished Product store, Scrap store, Rg-1 Store,
B.O.P store.
LOCATION MASTER
This block holds the information about the location of the store where the product is to be kept.
Example: Store Floor.
76
EMPLOYEE MASTER
This block holds the information of the employees of the organization. Example: Name of
Employee, Department, Date of Joining etc.
CHALLAN OUT
This block holds the information of the material that is going out of the organization either for
sale or for job work.
77
GRN(Gate Receipt Note)
This block makes the entry of the material that is coming in the organization either for
production or job work. After the GRN the material is passed to the store or directly to the work
center after inspection.
78
MATERIAL ISSUE
Material that is in the store is issued to the different work centers depending upon the work that
has to be taken on the product. The details like the name of the work center, quantity of material
issued, name of the person to whom the material is issued etc. is noted in this block.
79
MATERIAL RECEIPT
The material that comes within the organization is received in the store using the material receipt
block of the project.
IMIR (Incoming material Inspection Report)
When the material is received in the company then it is tested for its accuracy. If the material is
ok then it is forward to store or work center. Otherwise the line rejection of that material takes
place.
80
Line Rejection Voucher
81
82
DATA DICTIONARY
S.No Field Name Description

1 ACTIVE Indicates whether the current Process Sheet is
active
2 APPROVED Indicates whether the current record is
approved
3 AUTH_BY Gives the name of person who takes a decision
4 BATCH_NO Batch no to which part belongs
5 CONS Part Consumed
6 DAY Current Day
7 DECISION_TYPE Type of decision taken
8 DOC_PRINT Indicates whether the document has been
printed
9 DRAWING_NO Drawing no of the part
10 FILE_NAME Name of file
11 FWD_WC Name of Work Center to which the process
belongs
12 INSPECTION Indicates whether the inspection of the part is
required
13 LINK_ID Id of the Part to which a specific part attaches
itself
14 LOCATION Location of a machine or a store in a Work
Center
15 LOCKED_RECORD Indicates whether the record is allowed to be
changed
16 MATERIAL_FROM Source of material
17 MATERIAL_TO Destination of material
18 MAX_LEVEL Maximum Stock level allowed
19 MIN_LEVEL Minimum Stock level allowed
20 PACKING_SLIP Indicates whether the packing slip is required
21 PARENT Name of the parent of the part
22 PART_NAME Name of part
23 PART_NO Number of part
24 PARTY_NAME Name of party
25 PROCESS Name of process
26 PRODUCT_GROUP Name of group to which part belongs
27 PRODUCT_GROUP_ID Group Id of Product group
28 PRODUCTION_TIME_HR Production time of a part in hours
29 PRODUCTION_TIME_MIN Production time of a part in minutes
30 PUR_REJ_DECISION Rejection decision of the purchased items
32 QUEUE_NAME Name of the queue in a Work Center
33 RATE Rate
34 REASON Reason for a particular decision
83
35 REC_BY Name of person who recommended the

decision
36 RECORD_ID Record id
37 REJ_PPM Rejection part per million
38 REJ_PROCESS Name of process at which part is rejected
39 REJECTION_FLOOR Name of rejection floor of WorkCenter
40 REMARKS Remarks
41 REORDER_LEVEL Level of stock at which the part is to be
ordered again
42 REV_NO Revision No of the Process sheet
84
85
Stock at Store
This report shows the stock available in the particular store. Example consumable store, B.O.P
store etc.
86
Stock at Work Center
This report shows the stock available at various work centers.
87
Material Receipt
This report gives the information about the material received in the store and the related
information like quantity of the material received.
88
Part Wise GRN
This gives the details of the part wise GRN done in the organization.
89
IMIR Daybook
This report shows the details of the inspection done, material inspected and also the name
of the person who has performed inspection.
90
91
SYSTEM TESTING
The increasing cost of failures and mission critical nature of software has brought a
high focus on software testing in the development organization. Software testing has become the
most critical element in software quality assurance. Testing is the most important part and major
quality control measure in software development life cycle. Its basic function is to detect errors
in the software. During requirement analysis and design, the output is a document that is usually
textual and non-executable. The goal of testing is to uncover requirement, design, and coding
errors in the programs. The purpose of product testing is to verify and validate the various work
products via units, integrated units, and final product to assure that they meet respective
requirements.
Objectives of Testing
A clear objective is essential for the success of any task. A critical activity like software testing is
no exception. However, there is a common misconception that software testing is an activity to
prove the correctness of software. The reality however is that testing should be viewed more as a
“destructive” process than a “constructive” process of software development.
“The objective of testing is not to show the absence of defects, but to show their presence. Hence
any structured testing activity has to comply with this underlying objective.”
Testing In Software Product/Project Industry
Testing strategies are most often directly adaptable only to a project development organization
since they have evolved parallel to the software development life cycle (SDLC).Software
product development, involves continuous “maintenance”, which calls for more stringent
measures of quality control.
92
Product development involves maintaining the software products for the present customers and
developing future releases, incorporating additional features. There is a constant need for
correction and enhancements activities. ”Change” is hence permanent .Problems due to this
constantly changing scenario are like:
 Change without proper impact study creates havoc configuration management.

 Unplanned changes lead to old defects reappearing and fresh defects surfacing.
 Loss or change in original functionality of a given feature is also a common outcome of
unplanned defect rectification.
Since a software product services multiple clients, these problems take a heavy toll of client
confidence, credibility and a good client referral base. Hence we are likely to lose out on factors
which are the major marketing strengths of any software product.
To ensure that constant change does not affect product quality and performance, a means of
quality control has to be adopted which will streamline effecting changes and provides greater
control over maintenance activity. This calls for:
 Proactive problem identification and resolution.

 Generating results through pre-defined data
 Regression testing through recorded sequence of test steps for compression with expected
outcomes.
 Performance measure built into the test sequences to monitor performance of functional
features.
Here the System testing involved is the most widely used testing process consisting of five stages
as shown in the figure. In general, the sequence of testing activities is component testing,
integration testing, and then user testing. However, as defects are discovered at any one stage,
they require program modifications to correct them and this may require other stages in the
testing process to be repeated.
93
Unit
testing
Module
testing
Sub-system
testing
System
(Component testing) testing
Acceptance
testing
(Integration testing)
(User testing)
Effective Testing
Implementing software testing in a structured manner involves preparation of well designed test plans and
test cases for checking the functionality of the software. Though mechanisms like automation of test cases
for increasing the efficiency of testing are available, the critical success factor of effective testing lies in
the test plan in the test plan and test case design to meet the objective of testing.
94
Testing Objectives
The main objective of testing is to uncover a host of errors, systematically and with minimum
effort and time. Stating formally, we can say,
 Testing is a process of executing a program with the intent of finding an error.

 A successful test is one that uncovers an as yet undiscovered error.
 A good test case is one that has a high probability of finding error, if it exists.
 The tests are inadequate to detect possibly present errors.
 The software more or less confirms to the quality and reliable standards.
Types of Testing
Various types of tests carried out are as follows:
Unit testing
Unit testing focuses verification effort on the smallest unit of software i.e. the block. Using the
detailed design and the process specifications, testing is done to uncover errors within the
boundary of the module. All modules must be successful in the unit test before the start of the
integration testing begins.
In this project each service can be thought of a block. There are so many blocks like Challan Out,
Material Receipt, Material Issue, GRN, etc. Each module has been tested by giving different sets
of inputs. When developing the module as well as finishing the development, the module works
without any error. The inputs are validated when accepting them from the user.
Integration Testing
After unit testing, we have to perform integration testing. The goal here is to see if modules can
be integrated properly, the emphasis being on testing interfaces between modules.
95
In this project the main system is formed by integrating all the modules. When integrating all the
modules I have checked whether the integration effects working of any of the services by giving
different combinations of inputs with which the two services run perfectly before Integration.
System Testing
Here the entire software system is tested. The reference document for this process is the
requirements document, and the goal is to see if software meets its requirements.
Here entire ‘STORE’ block has been tested against requirements of project and it is checked
whether all requirements of project have been satisfied or not.
Acceptance Testing
Acceptance Testing is performed with realistic data of the client to demonstrate that the software
is working satisfactorily. Testing here is focused on external behavior of the system; the internal
logic of program is not emphasized.
Test cases should be selected so that the largest number of attributes of an equivalence class is
exercised at once. The testing phase is an important part of software development. It is the
process of finding errors and missing operations and also a complete verification to determine
whether the objectives are met and the user requirements are satisfied.
Testing Methodologies:
Any software product can be tested in one of two ways:
 White Box Testing

Knowing the internal working of a product tests can be conducted to ensure that an internal
operation performs according to specifications and all the components have been adequately
exercised. This approach is known as white box testing.
White box testing of software is predicted on close examination of procedural details. Providing
a test case that exercises specific set of conditions. Tests logical path in the software. The “State
96
of Program” may be examined at various points. To determine if the expected or asserted status
corresponding to the actual status.
Transaction Path Testing
The path of each transaction from origin to destination was tested for reliable results.
Module Testing
This was carried out during the programming stage itself. Individual applications were
tested at the time of coding and necessary changes were made there on to make sure the
modules in the program, is working satisfactorily as regards the expected output from the
module. All aspects of the programs were properly tested.
String Testing
After loading all the individual pages and forms of the site, testing was performed for each
one of the programs where the output generated by one program is used as input by another
program. This step was completed after making necessary changes whenever required.
 Black Box Testing

Knowing the specific function that a product has been designed to perform, tests can be
conducted that demonstrates each function is fully operational, at the same time searching for
errors in each function. This approach is known as black box testing.
Black box testing is done to uncover errors. They are used to demonstrate that software are
operational; the input is properly accepted and output is correctly produced and that integrity of
external information is maintained (e.g.: data files).A black box eliminates some fundamental
aspects of a system with little regard for internal for logical structure of the software.
97
System Testing
After module and string testing, the systems were tested as a whole system. Tests were
undertaken to check bundled modules for errors. The errors found in the coupled system as a
whole were corrected. This stage was important because it helped in eliminating the errors that
were occurring due to various platforms on different machines.
Output Testing
No system can be useful if it does not produce the required operation. For that purpose,
the output generated or displayed by the site under consideration was tested by matching it with
the format required by them.
User Acceptance Testing
User acceptance of a system is a key factor for the success of any system. The site under
construction was tested for user acceptance by constantly keeping in touch with the prospected
system users at the time of developing and making changes. Whenever required, this was done in
regard to the user satisfaction.
98
Test Case Design
Test case design focuses on a set of techniques for the creation of test cases that meet over all
testing objectives. In test case design phase, the engineer creates a series of test. Cases that are
intended to “demolish” the software that has been built.
TEST CASES DESIGNED

Test Cases for Login form
S.No Procedure Input Expected Output
1. A correct password Wrong Error message

and user Id must be “invalid user”
user Id
provided during login displayed and
entered
to proceed with the prompt to reenter
system user id and
password
2 A correct password Wrong Error message
must be provided password “incorrect
during login to entered Password”
proceed with the displayed and
system prompt to reenter
password
3 A correct password Right Appropriate page
must be provided password will displayed based
during login to on the user type i.e.
entered
proceed with the Admin or Normal
system user.
Test Cases for New User form

S.No. Procedure Input Expected Output
1. Fill the form with Existing Email Error message “User
required email Id Id Entered already exists.”
2. Fill the form with Email Id Error message
required email Id entered in “Invalid Format”
incorrect
99
format
3. Fill the form with the Blank Email-Id Error Message
required email Id “<field> can not be
left blank.”
Test Cases for User Registration form

S.No. Procedure Input Expected Output
1. Fill the Registration Incorrect Error message
form with required Password “Please enter correct
details password”
2. Fill the Registration Existing Error message
form with required Employee code “Employee with
details entered <employee code>
already exists.”
3. Fill the Registration Blank first Error Message
form with the details name “<field> can not be
except user Id left blank.”
4. Fill the Registration Incorrect date Error Message
form with the details of Birth ”Invalid Format”
except user Id
5. Fill the Registration Incorrect Pin Error Message
form with the details Code ”Please enter a 6-
except user Id digit Pin Code”
6. Fill the Registration Incorrect Error Message
form with the details email Id ”Please enter
except user Id emailed in specified
format”
7. Fill the Registration Blank Mobile Error Message
form with the details Number “<field> can not be
except user Id left blank.”
8. Fill the Registration Correct & User Registered.
form with required complete
details details
entered for
employee
100
Testing implementation
Executes test plans(generated test reports) after preparation of test cases and after making
appropriate changes in the code we execute the test cases. Execution of test plans is done in
accordance with project management plan. Test acceptance criteria for the functional tests in
measurable terms are specified in customer requirement specification. Say not more than x
number of problems of severity code A and Y problems of severity code B for acceptance of the
product under test. After running our test cases we run the test cases given by company for the
validation of the product.
101
102
IMPLEMENTATION
Implementation is a process that includes all those activity that to convert an existing system
(manual or existing) to new system. After the software is tested, we proceed to implementation
phase. Ideally the software should be completed and fully tested before implementation gets
under way but unless a package is being installed this seldom happens.
“Implementation involves placing the completed and tested system of hardware and software
into the actual work environment of the users.”
There are three type of implementation. This is the most important phase of system
Development Life Cycle where the actual implementation of designed system occurs.
First phase is the implementation of a computer system to replace a manual system, the problem
encountered are converting files, training users, creating accurate files and verifying printouts for
integrity.
Second phase is implementation of a new computer system to replace an existing system. This is
usually a difficult conversion. If not properly planned, there can be many problems. Some large
computer system has as long as a year to convert.
Third phase is when modified application is developed to replace an existing system using the
same computer. This type of conversions is comparatively easy to handle provided there are no
major change in the files.
Normally what happens is that parts of the system which are required for the file set-up are
completed first and this process gets under way. Conversion programs may also have to be
available which allow data from another system to be in setting up the files. Once this data is set
up it must be kept up-to-date and, thus, the first use is made of the new system. Period of parallel
running and when a decision is made to drop the old system may follow this.
103
At the time of implementation we need a lot of things like system documentation, user manuals,
procedure manuals, computer operating instructions and security procedures. Procedure should
be established to control all request for system and program changes.
So far, little intention has been paid to the problems conducting with user, and new methods need
to be developed. Once installed, applications are often used for many years. However, both the
organization and the users will change. And the environment will be different over weeks and
months too. Therefore, the application will undoubtedly be maintained. That is modifications and
changes will be made to this software, file or procedures to meet emerging user requirement.
Organization system and the business environment are in a continual change. In this sense
implementation is an ongoing process.
We have completed the testing of our system as much accurately as much we can. After the
testing we have implemented it on client site networking system. It is implemented successfully.
104
105
DOCUMENTATION
Documentation is the one of the most important aspect of our computer programming. Most
programmers, having written, tested and implemented a program are not too ready to move on to
their next with sense of relief. On the other hand, the users of programs complain all too
frequently that the documentation is incomplete. If the program does not have details, like input
for other user to a full understanding of the program, how to use it correctly. Mostly it is
produced at the end of the project.
All the software system should have a prodigious amount of associated documentation. The
documentation fills the several cabinets of the software developed. Documentation associated
with a software system has a number of requirements as:
 They should act as a communication medium between numbers of development team.

 There should be a system information repository to be used by maintenance.
 They should tell user how to used and administer the system.
106
107
USER MANUAL
The processing structure and a suitable methodology are necessary for successful
implementation of any application. Several users according to jobs assigned to them may operate
upon this application.
First of all the machine has to be booted. Now a user can use this package, on his/her machine.
The user has to have Windows 95 or above since the software is developed using Visual Basic
and SQL Server under Windows Environment. After the application is started the user sees the
Main Screen having a choice of menus on his/her screen.
The main screen has following menu on it :

 Masters
 Purchase Order
 Schedule
 Gate Entry
 Inspection Report
 Store
 Shutdown
On clicking of any of the menu item results in opening of the corresponding form for performing
various operations such as addition, deletion, and modification in the form. Some of the menu
items have further a sub-menu attached to it.
When the menu ‘Masters’ is clicked, a submenu giving following options:

 Account Group Master
 Account Master
 Product Group Master
 Product Master
108
 Inspection Parameter Master

 Store Master
 Location Master
 Employee Master
If the menu ‘Purchase Order’ is clicked, a submenu giving following options opens:
 Purchase Order
 Purchase Order Amendment
If the menu ‘Schedule’ is clicked, a submenu giving following options opens :

 Purchase Schedule
 Purchase Schedule Amendment
If the menu ‘Store’ is clicked, a submenu giving following options opens

 Material Receipt
 Material Issue
If the user selects the Shutdown menu, the screen takes you to out of the system environment.
109
110
SCOPE OF PROJECT
As the project covers all the aspects of a Sheet Metal Industry, it will automate its operations and
will increase the efficiency and quality of the work. It will help the employees in making their
work more reliable and fast.
Data and other valuable information can be handled more securely. As this project will keep
track of all the clients of the company and will keep full data of previous years, it will help in
analyzing the market graph of the company.
However good it may be but there is always a scope for improvement and modification. It is
likewise for this software as well .Though it broadly achieves what it was intended to do, still
these goals can be set a little higher. More functionality such as changed interface, improved
processing speed can be added to the present system to make it more versatile and perfect such
as Edit Save requires some extra time because of temp table concept. On the other hand in
critical phase like Invoice development and MRN we can’t involve more than one person to
work on the same time.
111
112
CONCLUSION
A successful package can only be developed if the developer has understood the nature of the
problem in a new manner and should not try to copy an existing solution as such. Most of the
times it is not possible to computerize the manual system completely and a few things are always
left out. This is true for public sector, as the format of the documents cannot easily be changed.
This leads to some limitations in application device. However, at the same time the advantages
that a computerized system offers cannot be ignored. Here few of the important advantages that
this system would be able to render are:
 Major advantage is increase in speed and efficiency of work.
 Eliminates the redundant information available in various fires.
 All the information shall be recorded unbiased and shall be according to the rules of business
and organization.
 The printed reports shall be available in the desired format easily understandable for the
employees concerned.
113
114
BIBLIOGRAPHY
 VISUAL BASIC : Mastering V.B, BLACK BOOK
 SQL SERVER : SQL SERVER 2000
115

Store Management System

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Store Management System

Uploaded by

Copyright:

Available Formats

STORE MANAGEMENT SYSTEM

 To continuously learn and knowledge sharing.

 To be honest, open, reliable and responsible in everything we do

 "Do" implement the define Plan

 "Check" collects information on control points and parameters. To compare actual

 "Act" identifies corrective action(s). Analyze, identify, discuss and agree on

Our Vision and Mission

 Extremely user friendly and no need for trained users.

 Training material and syllabus reengineered to individual customer

 Small classroom that allows trainer to provide full attention

 Experienced and knowledgeable trainers

 Understand customers' needs and goals

 On-Site Implementation with step-by-step implementation procedures

 Mapped reengineered Site Assessment

 Working in aligned with customers' projected implementation schedule

 "Hot-Line" telephone, hand phone calls and emails support

 Remote Access to customer site over a secured WAN.

Contact Information: Address:

Mr. Deep Dua 5L/4,N.I.T Faridabad

HARDWARE AND SOFTWARE REQUIREMENTS

Operating System And Software Used

Minimum System Requirement

Visual Basic Editions

SQL Server Enterprise Manager

 Define groups of SQL Server instances.

Creating and Maintaining Databases

Database component Description

Accessing And Changing Data

Optimizing Database Performance

Data Transformation Services

This section contains procedures for:

 Using Data Transformation Services (DTS) tools.

Crystal Report 8.0

Crystal Report And Back-End

Adding Database To Report

Visual Linking Expert

We use the Visual Linking Expert to:

 Create smart links automatically between databases.

Design Tab Areas

Window Description of contents

START DATE: 25 Dec, 2008

The PERT chart follows:

d: represents the day require for particular task.

System Development Life Cycle

UNDERLYING PRINCIPLES OF A SYSTEM DEVELOPMENT

Get the users and the owners involved

Use the problem solving approach

Establish phases and activities

To understand system development, we need to recognize that a candidate system has a

The traditional information system development cycle

System Concept Development Phase

Requirements Analysis Phase

Integration and Test Phase

Operations and Maintenance Phase

 To reduce the risk of project failure

SDLC FLOW DIAGRAM

LIMITATIONS OF EXISTING SYSTEM

 Mismanagement regarding various types of tariff heads implied by government on

PROPOSED SYSTEM (ERP)

ERP (Enterprise Resource Planning)

ERP TOOL KIT

Effective forecasting, planning, and scheduling are fundamental to productivity–and ERP is a

Erp Also Includes

The benefits from Enterprise Resource Planning are claimed to include: