A Project Report on

Inventory Management Of
Raw Material

20011-12


M MA AJ JO OR R P PR RO OJ JE EC CT T S SU UB BM MI IT TT TE ED D F FO OR R T TH HE E D DE EG GR RE EE E O OF F
M M. .C C. .A A. . ( (M MA AS ST TE ER R O OF F C CO OM MP PU UT TE ER R A AP PP PL LI IC CA AT TI IO ON NS S) )
M MC CA A I II II I Y YE EA AR R ( (V VI I S SE EM ME ES ST TE ER R) )
S SE ES SS SI IO ON N: : 2 20 00 09 9- -1 12 2






Project Guide Submitted BY:
M MR R. . V VI IV VE EK K U UP PR RI IT T S SW WA AT TI I S SH HA AR RM MA A










ACKNOWLEDGEMENT

The present project is submitted to Sanghvi Institute Of Management And
Science, Indore under R.G.P.V., Bhopal for partial fulfillment of degree of
Master of Computer Application.
I being the student of SIMS, Indore convey my sincere thanks to Director Sir -
Dr. P.N. Goswami, H.O.D. - Prof. Vivek Uprit, for providing all the facilities
required for making the project successful.
I would like to take this opportunity to thanks Prof. Vivek Uprit my project guide
for providing me the guidance and whole suggestions helped in invaluably in
designing this project.
Last but not the least my thanks to all of them who directly or indirectly helps me
in completion of this project.

















CERTIFICATE

This is to certify that SWATI SHARMA (0837CA091048) student of MCA
Third year (6
th
Sem ). She has completed the major project work based on
curriculum. She has submitted the project report entitled Inventory
Management of Raw Material. for the partial fulfillment of Master of
Computer Application. She has submitted a satisfactory account of her work. We
wish her all the best for future.
Date: 25 /MAY/2012



---------------------- ------------------------
External Examiner Internal Examiner




















DECLARATION BY THE STUDENT

I hereby declare that this project titled (Inventory Management Of
Raw Material) submitted by me is based on actual work carried out by me.
Any reference to work done by any other person or institution or any
material obtained from other sources have been duly cited and referenced. It
is further to state that is work is not submitted anywhere else for any
examination.

Swati Sharma



Index

1. Introduction of client/organization
2. Problem Investigation
Introduction to Existing System
Goal & Need of project
Objective
Solution suggested

3. Theory of system
Concept of project
Various processes running


4. System analysis
Process model used
1.) Select model
2.) Advantage of select model
Limitations to current system
Introductions to proposed system
Merits of proposed system



5 Project Planning
Project Resources
Hardware & software requirements
Team organization
Specify the role in team.






6. Feasibility study




7. System Design
DFD
UML ( as per project requirement)

ERD
Data base design

8. Tools used and descriptions
Front end
Back end
Reason for tools selected

9. Implementation
Programming approach followed
Top Down Approach / Bottom Up Approach
Screen layouts
Forms Layouts
Reports Layouts
10. Testing
QA Plan
Testing
Objectives of testing methods
Testing methods


11. Maintenance

12. Conclusion
Conclusion and discussion
Limitations
Difficulties encountered during project

13. Bibliography
14. Future Scope of Project
C
CCH
HHA
AAP
PPT
TTE
EER
RR 1
11

COMPANY
PROFILE













IT Solutions is a company with commitment and passion for providing value to its
customers by enabling technology.
It is an Offshore Software Development specialist that
combines the definite bottom-line benefits of Offshore Outsourcing with its recognized expertise
in strategic global models that help it in providing reliable Outsourcing Software Development
Solutions. The services offered cover Custom Software Development, Application Development,
Web Application Development, Agile Software Development, Software Outsourcing, E-
commerce web site design, Web Marketing, Website Design and Software Maintenance. Our
goal is to deliver premium quality software development services and products while giving
unmatched value to enterprises worldwide at an affordable cost..
At EPSILON, we firmly believe that technology can create value
only if it helps organizations achieve their business objectives and sustained competitive
advantage. Epsilons focus is on helping companies strategize, plan and deploy cutting edge
technologies, with the overall purpose of contributing in realization of their business goals. As an
IT Consulting and Services firm, EPSILON offers services in the areas of ERP, e-Business, EAI,
Data warehousing, Quality Analysis and Testing.
EPSILON employees make a rich pool of talented, experienced
and technically proficient professionals, who provide clients with technology expertise,
execution capabilities and most importantly high levels of delivery. Epsilons management has
several years of proven experience in providing technology solutions and shaping IT initiatives
for large and mid size corporations.

Core Values
All EPSILON employees share a set of core values that characterizes our thoughts and actions.

Knowledge


Incessant endeavor to master the latest in technology and its application.

Collaborative efforts to accumulate share and apply knowledge.

Investment in training and knowledge building initiatives.

Customer Satisfaction

Earning customer satisfaction by delivering outstanding services, time after time.

Building trust and reliability by never letting the customer down.

Putting the customers interest as paramount by listening, understanding and aligning
objectives.

Growth


Focused pursuit of corporate as well as individual (professional and personal) growth.

Striving for excellence and exceeding expectations.

Achieving growth based on mutually beneficial relationships with customers and partners.


Address:-
Office address:
Abhay Prashal, "B" Wing, Race Course
Road, Indore- 452003
Ph: +91-731-3243542
Marketing office:
Patni Apartment, 160, S.P. Road
Begam Peth Secundrabad -500016
Ph: +91-40-32447340


Email IDs
email: info@epsilonitsolution.com
hr@epsilonitsolution.com






C
CCH
HHA
AAP
PPT
TTE
EER
RR 2
22


Problem Investigation



































2.1Introduction of Existing System

Existing System study reveals that all the booking was done manually on registers, which was
very tedious and error prone job. Searching and report generation was also not possible in the
existing system. Also the work of company was manually maintained. There was register or file
system in the Company.
Present mode of working is based on manual system in which the all the information is first
received and then entered in the register. It is very difficult job and time consuming also.
Moreover, the existing system is also dependent on employees, if the employees are absent; it
leads to problem and affects the business performance.

2.2Need of Project:-

Due to large volume of data, a lot of complexities are involved in maintaining, updating and
retrieving selected information.
As we know the manual processing is quite tedious, time
Consuming, less accurate in comparison to computerized processing. Obviously the present
system is not is exception consultant encountering all the above problems.
1. Time consuming.
2. It is very tedious.
3. All information is not placed separately.
4. Lot of paper work.
5. Slow data processing.
6. Not user-friendly environment.
7. It is difficult to found records due file
Management system.
8) Redundancy of data: - Due to improper maintenance of data, inconsistency is there which
leads to problem like duplication of data
9) Difficulty in updating the data:-Problem of updating data in the existing system since
everything is stored in registers and files. It is very difficult and time consuming to update data.
10)No integration or relation between the data: - Present system does not support any type of
data integrity.


2.3Objective
.
To perform a thorough analysis of working of the whole System.
To follow SDLC to develop the system.
To develop conceptual, logical and physical model for the system.
To develop Graphical User Interface (GUI) as per convenience of the user.
To implement the physical model, being tested as per the standards.
To document our efforts and analysis in a proper comprehensible manner.

Inventory too many small business owners is one of the more visible and tangible aspects of
doing business. Raw materials, goods in process and finished goods all represent various forms
of inventory. Each type represents money tied up until the inventory leaves the company as
purchased products.



2.4 Solution Suggested
Following facility are use to remove above problem-
1. Manually system changes into computerized
System.
2. Friendly user interface.
3. Time saving.
4. Save paper work.
5. Connecting to database so we use different type of queries, data report.
6. Give facility of different type of inquiry.
7. Formatted data.
8. Datas are easily approachable.










C
CCH
HHA
AAP
PPT
TTE
EER
RR 3
33


Theory of System





















3.1Concept Of Project



A Raw Material Inventory is a project for management raw materials used for constructing road,
buildings or architectural etc. In this project our purpose is managing the inventory that means a
complete list of items such as goods, raw materials in the construction. The entire stock of raw
materials and finished product.
In this project multiple warehouses are involved where our purpose is managing that how much
purchase, stock transfer from one warehouse to another warehouse, which can be in same and
external project. In warehouse management we manage about the warehouse that in multiple
cities and multiple project how much stock is purchased or transferred. Our main focus in project
is costing of raw materials, and calculates the complete cost of raw materials in stock.

This will help to construction of raw materials and warehouse management which are
involved in multiple cities in project. It is web based application that why it can be used
anywhere no restriction for place to use this application. In this project our purpose is managing
the inventory that means a complete list of items such as goods, raw materials in the
construction. In this project multiple warehouses are involved where our purpose is managing
that how much purchase, stock transfer from one warehouse to another warehouse, which can be
in same and external project.











3.2 Various Processes Running

There are many items in a departmental store, which are sold to contractor and
Purchased from Vendor. An order is placed by the Contractor-required details, which are
listed below:
Item name
Quantity
Price
The order processing executes, look up the stock of each item is available or not
then order fulfilled by Warehouse Incharege. The system periodically
checks the stock of each item if it is found below the reorder level then purchase order placed to
the vendor for that item, if the vendor is not able to supply whole order then rest of quantity
supplied by the another vendor.
After fulfilled the formalities, report give by the Project Leader to the Project Director.
My work area is to automate the above process or to generate a more efficient
system.











C
CCH
HHA
AAP
PPT
TTE
EER
RR 4
44


System Analysis




























4.1System Analysis

Analysis involved a detailed study of the current system, leading to specifications of a new
system. Analysis is a detailed study of various operations performed by a system and their
relationships within and outside the system. During analysis, data are collected on the available
files, decision points and transactions handled by the present system. Interviews, on-site
observation and questionnaire are the tools used for system analysis. Using the following steps it
becomes easy to draw the exact boundary of the new system under consideration:
Keeping in view the problems and new requirements
Workout the pros and cons including new areas of the system
All procedures, requirements must be analyzed and documented in the form of detailed data flow
diagrams (DFDs), data dictionary, logical data structures and miniature specifications. System
Analysis also includes sub-dividing of complex process involving the entire system,
identification of data store and manual processes.
The main points to be discussed in system analysis are:
Specification of what the new system is to accomplish based on the user requirements.
Functional hierarchy showing the functions to be performed by the new system and their
relationship with each other.
Function network which are similar to function hierarchy but they highlight the those
functions which are common to more than one procedure.
List of attributes of the entities - these are the data items which need to be held about
each entity (record)
Gather Information
Define the new system's requirements
Build prototypes for the new system
Prioritize requirements
Evaluate alternatives
Meet with management to discuss new options












Test Code Design Analysis
4.2 Processes Model Used

4.2.1WATERFALL MODEL

The waterfall model is a sequential software development model in which development is
seen as flowing steadily downwards (like a waterfall) through several phases.














SYSTEM
ENGINEERING
ANALYSIS
DESIGN
CODING
TESTING
MAINTANEN
CE
4.2.2Advantages of Waterfall Model

The waterfall model is the oldest and most widely used model in the field of software
development. There are certain advantages of the waterfall model, which causes it to be the most
widely used model as yet. Some of them can be listed as under.
Needless to mention, it is a linear model and of course, linear models are the most simple
to be implemented.
The amount of resources required to implement this model is very minimal.
One great advantage of the waterfall model is that documentation is produced at every
stage of the waterfall model development. This makes the understanding of the product
designing procedure simpler.
After every major stage of software coding, testing is done to check the correct running
of the code.


4.3 Limitation To Current System

As we know the manual processing is quite tedious, time
consuming, less accurate in comparison to computerized processing. Obviously the
present system is not is exception consultant encountering all the above problems.
1. Time consuming.
2. It is very tedious.
3. All information is not placed separately.
4. Lot of paper work.
5. Slow data processing.
6. Not user-friendly environment.
7. It is difficult to found records due file
management system.




4.4Introduction to Proposed System:-

The new system will automate the whole working of company. In this project we will retrieve
the information or update the information easily by the use of computer. .we can easily retrieve,
changed, updated or saved the information whenever we want.


Introduction:-
It is web-application designed with easy to user interface for the targeted audience.
This software is developed to reduce the manual labor of working staff. In this system we can
add or update the inventory of raw materials.
For security point of view the login window content password so that nobody can access the
records.

4.5Merits Of Proposed System
Proposed system provides lot of facility to the user to store information of the Books and it
provides information in quick time in a systematic manner. The processing time on the data is
very fast. It provides required data quickly to the user and also in specified manner to the user.
All the information of Books changes is given to the user and also the reports are also generated
according to the requirement of the user.

Today it is becoming very difficult to maintain record manually. This software system easily
does the job of maintaining daily records as well as the transaction according to the user
requirements.
Some advantages are:
User friendly software
Easy to record all data about the Books and its details.
It saves time of the user as well as prevent paper work
It provides the security to the database that is large amount of important data of the
hospital.
It provides more reliability for keeping information.



C
CCH
HHA
AAP
PPT
TTE
EER
RR 5
55

Project Planning






































5.1Project Resources


HARDWARE REQUIREMENT: -

The following showed configuration is of the machine in which the software will be developed:

Processor : Pentium dual core

Ram : 1 GB

Hard Disk : 160 GB

Display Card : Supporting 32- bit true color

Keyboard : Multimedia keyboard

Mouse : Optical

Modem : 56 KBPS/ADSL Broadband




















SOFTWARE REQUIREMENT: -


The following is the list of the software used in the development of the project:

Operating System : Windows XP SP3, Windows 7

Programming Language : C# .NET,ASP.NET

Integrated Development : Microsoft Visual Studio 2010
Environment

Browser : IE 8.0

Database : SQL Server 2008
CLIENT SIDE:- Any latest Web Browser




5.2 Team Organization



Role:-
My role in the project is
Project Director(Admin)
Warehouse Incharege.












C
CCH
HHA
AAP
PPT
TTE
EER
RR 6
66

Feasibility Study


















The feasibility study is the important step in any software development process. This is because
it makes analysis of different aspects like cost required for developing and executing the system,
the time required for each phase of the system and so on. If these important factors are not
analyzed then definitely it would have impact on the organization and the development and the
system would be a total failure. So for running the project and the organization successfully this
step is a very important step in a software development life cycle process.
In the software development life cycle after making an analysis in the system requirement the
next step is to make analysis of the software requirement. In other words feasibility study is also
called as software requirement analysis. In this phase development team has to make
communication with customers and make analysis of their requirement and analyze the system.
By making analysis this way it would be possible to make a report of identified area of problem.
By making a detailed analysis in this area a detailed document or report is prepared in this phase
which has details like project plan or schedule of the project, the cost estimated for developing
and executing the system, target dates for each phase of delivery of system developed and so on.
This phase is the base of software development process since further steps taken in software
development life cycle would be based on the analysis made on this phase and so careful analysis
has to be made in this phase.
Though the feasibility study cannot be focused on a single area some of the areas or analysis
made in feasibility study is given below. But all the steps given below would not be followed by
all system developed. The feasibility study varies based on the system that would be developed.
Feasibility study is made on the system being developed to analyze whether the system
development process require training of personnel. This help in designing training
sessions as required in later stage.
.
Is the system developed has scope for expanding or scope for switching to new
technology later if needed in ease. In other study is made to find the portability of the
system in future.
.
Is the cost of developing the system high or does it meet the budgeted costs. That is a cost
benefit analysis is made. In other words an analysis is made on cost feasibility of the
project. This helps in identifying whether the organization would meet the budgeted costs
and also helps the organization in making earlier and effective plans for meeting extra
costs because of the system development.
.
Analysis is made on what software to use for developing the system. This study and
analysis would help to choose the best implementation for system and the organization.
This feasibility study includes factors like scalability, how to install, how to develop and
so on. This feasibility study in short includes the analysis of technical areas. This analysis
helps the efficiency of the system developed to get improved. This is because by
choosing the correct technology by making analysis on the needs of system helps in
improving the efficiency of the system.
.
The above feasibilities are analysis which helps in development of the system. But the
scope of feasibility study does not end with this. Analysis or feasibility study also
includes the analysis of maintenance stage. In other words feasibility study is made to
analyze how one would maintain the system during maintenance stage. This helps sin
planning for this stage and also helps in risk analysis. Also the analysis helps in making
analysis about what training must be given and how and what all documents must be
prepared to help users and developers to face maintenance phase.
Advantages of making Feasibility study:
There are many advantages of making feasibility study some of which are summarized below:
This study being made as the initial step of software development life cycle has all the
analysis part in it which helps in analyzing the system requirements completely.
.
Helps in identifying the risk factors involved in developing and deploying the system
.
The feasibility study helps in planning for risk analysis
.
Feasibility study helps in making cost/benefit analysis which helps the organization and
system to run efficiently.
.
Feasibility study helps in making plans for training developers for implementing the
system.
.
So a feasibility study is a report which could be used by the senior or top persons in the
organization. This is because based on the report the organization decides about cost
estimation, funding and other important decisions which is very essential for an
organization to run profitably and for the system to run stable.








C
CCH
HHA
AAP
PPT
TTE
EER
RR 7
77

System Design












Design concept provides the software designer with a foundation from more sophisticated design
can be applied. Design is meaningful engineering representation of something that is to be built.
It can be traced to customers requirement and at the same time assessed for qualities against a
set of pre define criteria for good design.








7.1DFD





1
Project
Management
Process
Project Director
Project Leader
Warehouse Incharge
Full Control
Take Decision and
Manage Project
Manage Raw Materials














Project Director
Create Project
Manage Project
Product Management
Warehouse Management
Cost Management
Control Management
Purchase Management
Report Management
Supply Management
Stock Management
Vendor Management
Project Manager
Warehouse Incharge












Login
User_mgt
Project
Warehouse
Product
Vendor
Contractor
Stock_mgt
opt
Director
Text
opt
Warehouse Incharge
Text
opt
Project Leader
Text























7.3E-R Diagram

Vendor
Vname Address
Contact
Email
City
State
v_i d
Purchase Material
mi_det_id
Quantity
Price
Totalamt
Recieve
Warehouse
w_id
Email
Contact
State
wname
Address
City
mi _i d prod_id
unit_id
Issue
Contractor
Return
City
Address
c_id
Contact
Email
cname
State















7.4Database Design


TABLE NAME:- assign_proj






TABLE NAME: - city




TABLE NAME:- contractor detail






TABLE NAME:- contractor_material_detail




TABLE NAME:- material issue






TABLE NAME: - material_issue_details






TABLE NAME:- New contractor





TABLE NAME:- New Unit







TABLE NAME:- Order Detail














TABLE NAME:- Order Table





TABLE NAME:- product_mgt






TABLE NAME:- Project_contrctor















TABLE NAME:- project_mgt




TABLE NAME:- project product





TABLE NAME:- Role mgt







TABLE NAME:- state





TABLE NAME:- unit_mgt




TABLE NAME:- user_mgt








TABLE NAME:- vendor_mgt














TABLE NAME:- warehouse_mgt


















C
CCH
HHA
AAP
PPT
TTE
EER
RR 8
88

Tools used and Description



















8.1FRONT END ASP .NET

Introduction:-
ASP.NET, the next version of ASP, is a programming framework used to create enterprise-
class Web Applications. These applications are accessible on a global basis leading to efficient
information management. The advantage ASP.NET offers is more than just the next version of
ASP.
Implementation Technologies:
When the user types in the URL in the address field of the browser, a Web Server is
contacted to get the requested information. In the .NET Framework, IIS (Internet Information
Service) acts as the Web Server. The sole task of a Web Server is to accept incoming HTTP
requests and to return the requested resource in an HTTP response. The first thing IIS does when
a request comes in is to decide how to handle the request. Its decision is based upon the
requested file's extension. For example, if the requested file has the .asp extension, IIS will route
the request to be handled by asp.dll. If it has the extension of .aspx , .ascx, etc, it will route the
request to be handled by ASP.NET Engine.

The ASP.NET Engine then gets the requested file, and if necessary contacts the database
through ADO.NET for the required file and then the information is sent back to the Clients
browser. Figure shows how a client browser interacts with the Web server and how the Web
server handles the request from client





8.2 BACK END SQL SERVER 2008:-

SQL Server 2008 brings with it a vast of new features, graphical user interface (GUIs), and
management tools, many of which are converted:-
A completely GUI management tool called SQL Server Management Studio (SSMS), which
provides a single, interpreted environment for most management /administration
requirement.
A reporting framework (SQL Server Reporting Services, or SSRS) as an integral part of the
database.
Vastly improved and expanded SQL Server Integration Services, a tool for extracting,
transforming, and loading data

8.3 Why Tool Selected


WHY SQL SERVER?

Relational database: It is not manage only data but it manages their relationship too.
Space management: It provides scalability and flexibility to the system.
Open Connectivity: It provides uninterrupted access to the database. It is possible to work
with the information that resides in other data repositories as well as it allows storage of
data in Oracles database and access through other software like C#, SQL windows.
Security Mechanism: These mechanism control access to sensitive data by an assortment
of privileges.
Backup and Recovery: Oracle provides excellent Backup and Recovery Routines.
Backup creates secondary copy of data. Recovery restores a copy of data from that
Backup



Why ASP.NET :-
ASP.NET drastically reduces the amount of code required to build large applications
ASP.NET makes development simpler and easier to maintain with an event-driven, server-
side programming model
ASP.NET pages are easy to write and maintain because the source code and HTML are
together
The source code is executed on the server. The pages have lots of power and flexibility by
this approach
The source code is compiled the first time the page is requested. Execution is fast as the Web
Server compiles the page the first time it is requested. The server saves the compiled version
of the page for use next time the page is requested
The HTML produced by the ASP.NET page is sent back to the browser. The application
source code you write is not sent and is not easily stolen














C
CCH
HHA
AAP
PPT
TTE
EER
RR 9
99

Implementation


















9
99.
..1
11P
PPR
RRO
OOG
GGR
RRA
AAM
MMM
MMI
IIN
NNG
GG A
AAP
PPP
PPR
RRO
OOA
AAC
CCH
HH

9
99.
..1
11.
..1
11T
TTO
OOP
PP D
DDO
OOW
WWN
NN &
&& B
BBO
OOT
TTT
TTO
OOM
MM U
UUP
PP A
AAP
PPP
PPR
RRO
OOA
AAC
CCH
HH



Top Down:
You formulate the problem and solve it introducing simple operations, for instance, you need to
add 2 numbers. This is your problem which you have to solve.
You divide it in simpler problems. Remember in computer memory first additive, then second.
And then add it to each other and show result or save in another variable and show the result.
Top down approach is the most popular method in programming.






Bottom Up
This method is more complicated because it's not easy to formulate simple problems and end up
with a global problem. In most cases bottom up is reversed to top down approach.

















F
FFO
OOR
RR E
EEX
XXA
AAM
MMP
PPL
LLE
EE









9
99.
..2
22S
SSC
CCR
RRE
EEE
EEN
NN L
LLA
AAY
YYO
OOU
UUT
TTS
SS

9
99.
...
..2
22.
..1
11F
FFO
OOR
RRM
MMS
SS L
LLA
AAY
YYO
OOU
UUT
TTS
SS










































































9
99.
..2
22.
..2
22R
RRE
EEP
PPO
OOR
RRT
TT L
LLA
AAY
YYO
OOU
UUT
TTS
SS




















C
CCH
HHA
AAP
PPT
TTE
EER
RR 1
110
00

Testing
















10.1Software Testing.


Testing is vital to the success of the software. Testing of the s/w leads to uncovering of errors in
the software functional and requirements are met. Testing also provide a good indication of s/w
reliability as software quality as a whole. The result of the different phases of testing are
evaluated and then compared with the expected results. If the errors are uncovered they are
debugged and corrected.


Testing Techniques


Testing consists of the following steps:


Program Testing

System Testing

Performance Testing

Configuration Testing

Program Testing:


Test Objective: In this testing I ensure that program has no
syntax and logical error.
Technique:

Compiled the program and check the error.
Completion Criteria: 1. All planned tests have been executed.
2. All syntax error is removed.







System Testing:

Test Objective: Ensured that the meets the fundamental
requirement laid out in the requirement
specification.
Technique: Run the program and actual program is
compared with the expected one. In case of
discrepancy, the sequences of instruction are
traced to determine the problem.
Completion Criteria: 1. All planed test have been executed
2. All identified defects have been addressed

Note: This type of testing is based on black-box technique that are verifying that the
application conforms to the requirements by interacting with the application via the
user interface and matching the actual output with the expected output















Configuration Testing












N
N
N
o
t
e
:

Configuration Testing verifies the system on different software and hardware
specifications.




Performance Testing









T
h
e
Test Objective: Validation and verification done by me to know
that the system functions properly on all
supported software & hardware configuration,
described in requirement specification.
Technique: For each supported version of OS, run the
system for difference services released.
Testing is done for coexistence with other
popular pc application.
Completion Criteria: All test completed with expected results on
various combinations of hardware and software
combination detailed in the requirement
specification.
Test Objective: Validate system response time for designate d
business functions for the targeted no of current
users.
Technique: Used different clients each run test scripts to
place a load on the system.
Completion Criteria: Successful completion of test script with
expected results with expected response time.
this method of test design is applicable to all levels of software testing: unit, integration,
functional testing, system and acceptance. The higher the level, and hence the bigger and
more complex the box, the more one is forced to use black box testing to simplify. While
this method can uncover unimplemented parts of the specification, one cannot be sure that
all existent paths are tested


10.2 Software Quality Assurance.

Software Quality Assurance (SQA) is defined as a planned and systematic approach to the
evaluation of the quality of and adherence to software product standards, processes, and
procedures. SQA includes the process of assuring that standards and procedures are established
and are followed throughout the software acquisition life cycle. Compliance with agreed-upon
standards and procedures is evaluated through process monitoring, product evaluation, and
audits. Software development and control processes should include quality assurance approval
points, where an SQA evaluation of the product may be done in relation to the applicable
standards.

Software Quality Assurance Activities

Product evaluation and process monitoring are the SQA activities that assure the software
development and control processes described in the project's Management Plan are correctly
carried out and that the project's procedures and standards are followed. Products are monitored
for conformance to standards and processes are monitored for conformance to procedures.
Audits are a key technique used to perform product evaluation and process monitoring. Review
of the Management Plan should ensure that appropriate SQA approval points are built into these
processes.
Product evaluation is an SQA activity that assures standards are being followed. Ideally, the first
products monitored by SQA should be the project's standards and procedures. SQA assures that
clear and achievable standards exist and then evaluates compliance of the software product to the
established standards. Product evaluation assures that the software product reflects the
requirements of the applicable standard(s) as identified in the Management Plan.

The purpose of an SQA audit is to assure that proper control procedures are being followed, that
required documentation is maintained, and that the developer's status reports accurately reflect
the status of the activity. The SQA product is an audit report to management consisting of
findings and recommendations to bring the development into conformance with standards and/or
procedures.
Software testing is a critical element of software quality assurance and
represents the ultimate review of specification, design and coding. In fact, testing is the one step
in the software engineering process that could be viewed as destructive rather than constructive.
A strategy for software testing integrates software test case design methods into a well-planned
series of steps that result in the successful construction of software. Testing is the set of activities
that can be planned in advance and conducted systematically. The underlying motivation of
program testing is to affirm software quality with methods that can economically and effectively
apply to both strategic to both large and small-scale systems.



10.3 Scope of Testing.

In the scope testing section of the test plan, the testing team describes specifically
what you want youre testing to accomplish. For example, the objective of one team was to
migrate component by component, keeping the access control lists (ACLs) and Exchange
permissions intact. Another teams objective was to provide a means to measure network traffic
and observe server performance during specific directory service tasks.
Also, you need to define the scope of your testing by identifying what you will test and what you
will not. For example, you might limit your testing of client computer hardware to the minimum
supported configurations or to the standard configurations.



10.4 Types of Testing.



There are some important types of testing:


10.4.1 White Box Testing.


This type of testing ensures that
All independent paths have been exercised at least once
All logical decisions have been exercised on their true and false sides
All loops are executed at their boundaries and within their operational bounds
All internal data structures have been exercised to assure their validity.
To follow the concept of white box testing we have tested each form .we have created
independently to verify that Data flow is correct, All conditions are exercised to check their
validity, All loops are executed on their boundaries.


10.4.2 Black Box Testing.

Black box testing should make use of randomly generated inputs (only a test range should be
specified by the tester), to eliminate any guess work by the tester as to the methods of the function.
Black box testing takes an external perspective of the test object to derive test cases. These tests
can be functional or non-functional, though usually functional. The test designer selects valid and
invalid input and determines the correct output. There is no knowledge of the test object's internal
structure.
This method of test design is applicable to all levels of software testing: unit, integration,
functional testing, system and acceptance. The higher the level, and hence the bigger and more
complex the box, the more one is forced to use black box testing to simplify. While this method
can uncover unimplemented parts of the specification, one cannot be sure that all existent paths are
tested.

10.4.3 Regression Testing.

Each time a new module is added as a part of integration testing, the software changes, new data
flow part are established, new i/o may occur and new control logic is invoked. Regression is the
re execution of some subsets of tests that have already been conducted to ensure that changes
have not propagate unintended side effects.









Following are some test cases are used in this project:




















Test Case 3: Generate Report (Order)
Test 1:
Test Case: 1

1. Form Name : Log-In
2. Input for Testing : 1. Testing applied on each and every data field for validation
2. Validation while inserting data into the database.
3. Testing Apply : 1. All fields must be entered valid data otherwise <all fields
are required to fill otherwise it gives message>
2. Check Login ID. If login id is correct the user must login
successfully otherwise it should say go to Unauthorized User.
4. Test Result : Ok

5. Remedy : Is Not Required.
6. Alpha Testing Again : Tested Success Successfully.
Test Case: 2

1. Form Name : Project Assign
2. Input for Testing : 1. Testing applied on each and every data field for validation
2. Validation while inserting data into the database.
3. If integer is entered in place of String it should give an
exception.
3. Testing Apply : Input data and click on save button Add save properly
4. Outcome : It gives Exception.
5. Test Result : Ok
6. Remedy : Is Not required
7. Alpha Testing Again : Tested Success Successfully
Incorrect input: An empty requirement field. (Select Date)
Pass criteria: An appropriate error message should be displayed and the user
should not be able to generate a report.
Correct input: Enter(Select) Correct Date
Pass criteria: The user (admin) should be allowed to generate the report.
























UNIT TESTING

MODULE TESTING

SUB-SYSTEM
TESING

SYSTEM TESTING

ACCEPTANCE TESTING
Component Testing
Integration Testing
User Testing
C
CCH
HHA
AAP
PPT
TTE
EER
RR 1
111
11

Maintenance











Maintenance plays an important role in the life cycle of a software product. It is
Estimated that there are more than 100 billion lines of code in production in the world. As
Much as 80% of it is unstructured, patched and not well documented. Maintenance can
Alleviate these problems. This paper describes the nature of software maintenance, why it
is included in software development and how its carried out. It discusses the role of
Maintenance played in iterative, agile, component-based and open source development
Models.
Software Development has many phases. These phases include Requirements
Engineering, Architecting, Design, Implementation, Testing, Software Deployment, and
Maintenance. Maintenance is the last stage of the software life cycle. After the product
has been released, the maintenance phase keeps the software up to date with environment
Changes and changing user requirements.
The earlier phases should be done so that the product is easily maintainable. The
design phase should plan the structure in a way that can be easily altered. Similarly, the
Implementation phase should create code that can be easily read, understood, and
Changed. Maintenance can only happen efficiently if the earlier phases are done properly.
There are four major problems that can slow down the maintenance process: unstructured
code, maintenance programmers having insufficient knowledge of the system,
documentation being absent, out of date, or at best insufficient, and software maintenance
having a bad image. The success of the maintenance phase relies on these problems being
fixed earlier in the life cycle.
Maintenance consists of four parts. Corrective maintenance deals with fixing bugs
in the code. Adaptive maintenance deals with adapting the software to new environments.
Perfective maintenance deals with updating the software according to changes in user
requirements. Finally, preventive maintenance deals with updating documentation and
making the software more maintainable. All changes to the system can be characterized
by these four types of maintenance. Corrective maintenance is traditional maintenance
while the other types are considered as software evolution.
As products age it becomes more difficult to keep them updated with new user
Requirements. Maintenance costs developers time, effort, and money. This requires that
the maintenance phase be as efficient as possible. There are several steps in the software
maintenance phase. The first is to try to understand the design that already exists. The
next step of maintenance is reverse engineering in which the design of the product is
reexamined and restructured. The final step is to test and debug the product to make the
new changes work properly.
This paper will discuss what maintenance is, its role in the software development
process, how it is carried out, and its role in iterative development, agile development,
Component-based development and open source development.






C
CCH
HHA
AAP
PPT
TTE
EER
RR 1
112
22

Conclusion

















12.1CONCLUSION


The project Raw Material Inventory is for computerizing the working in a Centre. The
software takes care of all the requirements of an average beauty parloure & fitness
centre and is capable to provide easy and effective storage of information related to
customer that come up to the centre.


12.2LIMITATIONS


This project has following limitations:

It is not a large scale system.
Only limited information provided by this system.
User does not have rights to check the status.
This system has not facility online transactions.
Skilled Person can use only.









12. 3Difficulties Encountered During Project:

1) User may enter a wrong value on the Date and Year textbox. The page will not be posted until
correct value is entered.

2) User may enter invalid email id, for this also a validation has been used which checks the
entered email id with the standard form.










C
CCH
HHA
AAP
PPT
TTE
EER
RR 1
112
22

Bibliography


























BOOKS

The Complete Reference C#.NET
System Analysis And Design-Elian Awed
Rox Beginner Edition Tata McGraw Hill
The Complete Reference ADO.NET
(Have) HungryMinds-ASP.NET Bible


WEBSITES

www.google.com
www.wikipedia.com
www.msdn.com
www.LearnVisualStudio.com







C
CCH
HHA
AAP
PPT
TTE
EER
RR 1
113
33


Future Scope of Project


































FUTURE SCOPE


Development always changes to its current status


Implement FLASH Technology.
Implement online transactions.
Implement the facility of user accounts.