Project Report 2

www.kashipara.in

CANDIDATE’S DECLARATION

We declare that final semester report entitled “Inventory Control” is our own work

conducted under the supervision of the external guide, Project Guide at .

Submitted to :

Computer Department,Rajkot

http://www.kashipara.in/

Inventory Control www.kashipara.in

COLLEGE CERTIFICATE

ACKNOWLEDGEMENT

College of information technology www.kashipara.in 2



The presented project is a result of our humble effort to put forward our caliber, which

could not be possible to get present shape without the faculty members, colleagues and

our guide.

First, We are sincerely thankful to, Director of College, Rajkot for giving us permission

to undergo training and always looking to provide great training to students in any case,

motivates to do something extra-ordinary. He provides us very friendly environment in

the institute.

At the moment of submitting this report, we seize the opportunity to express our heartfelt

gratitude towards our esteemed guide,. for this entire piece of work. Their guidance has

been so sublime as to render it possible for us to build this work with a feeling of pride.

We are also thankful to for providing me all the required information.

We feel gratitude in thanking the all staff members of College of Information

Technology, Rajkot.

PROJECT ABSTRACT




Here we have developed a project on Inventory Control to reduce the

effort for manage a stock.

By using our project any customer or user can manage his stock so our

project can be very help full for all the customer or user.

We have added many forms and function which makes project user friendly

and easy to understand.

We have tried to add that type of controls and functions which can be easily

understand the whole project easily by any technical person.




TABLE OF CONTENTS

TITLE PAGE No

CANDIDATE DECLARATION 01CERTIFICATE 02ACKNOWLEDGEMENT 03ABSTRACT 04CONTENTS 051. INTRODUCTION

1.1 Project Summary 071.2 Purpose : Goals & Objectives 071.3 Scopes 081.4 Technologies and Literature Review 081.5 Advantages of system 09

2. PROJECT MANGEMENT2.1 Project planning and scheduling 112.2 Risk Management 142.3 Estimation 17

3. PROJECT REQUIREMENS STUDY3.1 User Characteristics 213.2 Constraints 22

4. SYSTEM ANALYSIS4.1 Requirements of New System 244.2 Feasibility Study 264.3 Requirements Validation 274.4 Data dictionary 28

4.5 Main Modules of New System 294.6 Selection of Hardware and Software 29

5. IMPLEMENTATION PLANNING AND DETAILS5.1 Implementation Environment 325.2 Security Feature 325.3 Coding Standards 32

6. SCREEN SHOTS 337. CONCLUSION AND DISCUSSION 408. BIBLIOGRAPHY 42




1. INTRODUCTION




1.1 PROJECT SUMMARY

Inventory Control is a very user friendly project. In this project user can easily

understand and fill up the Inventory. In this project there are various types of forms are

there like sell form, buy form in which user can insert his Inventory, Needs & facilities

then upload his inventory.

In this project all the forms which user want to fill up its totally easy to understand. So in

any way user is not disturbed or not confuse at all, anyone can easily fill up Inventory.

it’s totally user friendly.

1.2 PURPOSE

GOALS & OBJECTIVES

The Purpose of the project is very clear that user can manage his inventory easily.

User can see stock of all inventory.

The Main Goal of this project is to provide an very faster inventory management.

The goal of my project is that I want my project totally user friendly project and I

hope I get success. When I make the project I kept one thing in my that when user

can not have an accounting knowledge so there are not any kind of confusion are

there , any one which is technical person apart from the technical field and non

technical person both type of person are easily understand about the fields and

easily handle it.

It saves lots of time , now a days there is a fast process world any one can work

fastly so, this project help that people who are working in inventory organization.

So, Inventory Control is a Desktop application made in the C#.Net. So with the

help of this project user can manage inventory.




1.3 SCOPES

Inventory Control is a totally Desktop application made in C#.Net. With the help of

this project a user are manage inventory. this process is a very fast process and

accurate also.

As we know that Inventory Control is a Desktop application. So user which is

operate this software little knowledge of computer they can understand easily.

1.4 TECHNOLOGIES AND LITERATURE REVIEW OF PAST

WORK/SYSTEM

1.4.1 TECHNOLOGY

Front end: C#.Net

Back end: SQL Server 2005

CLINT SIDE SCRIPTING

C#.NET

C#.NET combines unprecedented developer productivity with performance, and

reliability.

Developer Productivity

1. Flexible Language Options

C#.NET lets you leverage your current programming language skills. Unlike classic

ASP, which supports only interpreted VBScript and JScript, .NET now supports more

than 25 .NET languages giving you unprecedented flexibility in your choice

of language.




2. Rich Class Framework

Application features that used to be hard to implement, or required a 3rd-party

component, can now be added in just a few lines of code using the .NET Framework.

The .NET Framework offers over 4500 classes that encapsulate rich functionality like

XML, data access, file upload, regular expressions, image generation, performance

monitoring and logging, transactions, message queuing, SMTP mail, and much more!

Increased Reliability

Memory Leak, Deadlock and Crash Protection: .NET automatically detects and

recovers from errors like deadlocks and memory leaks to ensure your application is

always available to your users.

1.5 ADVANTAGES OF PROPOSED SYSTEM

This system has technically high approach.

It can also stop the repetition of the work.

Any technical expert can operate the system smoothly.

It is really times saving system.

It also provides the work satisfaction to the staff.




2. PROJECT MANAGEMENT




2.1 PROJECT PLANNING & SCHEDULING

2.1.1 Project Development Approach

To solve actual problems in an industry setting, a software development strategy must be

incorporated that encompasses the process, methods and tools for software engineering.

This strategy is often referred to as Software Process Model or Software Engineering

Paradigm. A software process model for software engineering is chosen based on the

nature of project and application, the methods and tools to be used and the controls and

deliverables that are required.

Among them, we have chosen a very popular one, The Classical System Development

Life Cycle Model or the Waterfall Model. This approach is classically thought of as a set

of six interrelated activities that make up the entire system development life cycle.

Water Fall Model:

This is also called Classic Life Cycle Model or Linear Sequential Model or Software

Development Life Cycle Model (SDLC). This model has the following activities:

1. System Information Engineering and Modeling

2. Software Requirement Analysis

3. System Analysis and Design

4. Code Generation

5. Testing

6. Maintenance




1) System/Information Engineering and Modeling

As software development is large process so work begins by establishing requirements

for all system elements and then allocating some subset of these requirements to

software. The view of this system is necessary when software must interface with other

elements such as hardware, people and other resources. System is the very essential

requirement for the existence of software in any entity. In some cases for maximum

output, the system should be re-engineered and spruced up. Once the ideal system is

designed according to requirement, the development team studies the software

requirement for the system.

2) Software Requirement Analysis

Software Requirement Analysis is also known as feasibility study. In this requirement

analysis phase, the development team visits the customer and studies their system

requirement. They examine the need for possible software automation in the given

software system. After feasibility study, the development team provides a document that




holds the different specific recommendations for the candidate system. It also consists of

personnel assignments, costs of the system, project schedule and target dates.

The requirements analysis and information gathering process is intensified and focused

specially on software. To understand what type of the programs to be built, the system

analyst must study the information domain for the software as well as understand

required function, behavior, performance and interfacing. The main purpose of

requirement analysis phase is to find the need and to define the problem that needs to be

solved.

3) System Analysis and Design

In this face, the whole software development process, the overall software structure and

its outlay are defined. In case of the clients/server processing technology, the number of

tiers required for the package architecture, the database design, the data structure design

etc are all defined in this phase. After designing part a software development model is

created. Analysis and Design are very important in the whole development cycle process.

Any fault in the design phase could be very expensive to solve in the software

development process. In this phase, the logical system of the system product is

developed.

4) Code Generation

In Code Generation phase, the design must be decoded into a machine-readable form. If

the design of software product is done in a detailed manner, code generation can be

achieved without much complication.

5) Testing

After code generation phase the software program testing begins. Different testing

methods are available to detect the bugs that were committed during the previous phases.

A number of testing tools and methods are already available for testing purpose.




6) Maintenance

Software will definitely go through change once when it is delivered to the customer.

There are large numbers of reasons for the change. Change could happen due to some

unpredicted input values into the system. In addition to this the changes in the system

directly have an effect on the software operations. The software should be implemented

to accommodate changes that could be happen during the post development period.

2.1.2 Project Plan

Project planning includes description of project tasks, activities and functions, dependencies, resource requirements and a detailed schedule. This activity results in the software project management plan for the Matrimonial Project.

Schedule of Project

Analysis=2 weeks Designs=3 Weeks Coding=5 Weeks Testing=2 Weeks

(Week-wise project Planning)

2.2 RISK MANGEMENT

2.2.1 Risk Identification

Technical Risks

Technical risks threaten the quality and timeliness of the software to be produced. If a

technical risk becomes a reality, implementation may become difficult or impossible.

Technical risks identify potential design, implementation, interface, verification, and

maintenance problems.




Business Risks

Business risks threaten the visibility of the software to be built. Business risks often

jeopardize the project or the product. Candidates for the top five business risks are

(1) Building an excellent product or system that no one really wants.

(2) Building a product that no longer fits into the overall business strategy for the

company

(3) Building a product that the sales force doesn’t under stand how to sell

(4) Losing the support of senior management due to a change in focus or a change

in people and

(5) Losing budgetary or personnel commitment.

Product Size

Risks associated with the overall size of the software to be built or modified.

Process definition

Risks associated with the degree to which the software process has been defined and is

followed by the development organization.

2.2.2 Risk Analysis

Risk Table.


Risks Category Probability Impact

Delivery deadline will be tightened BU 50% 2End-Users resist system BU 40% 3Customer will change requirements PS 80% 2Technology will not meet exceptions TE 30% 1Staff Inexperienced ST 30% 2Lack of training on tools DE 80% 3Less reuse than planned PS 70% 2



Category: Impact values: BU - Business impact 1 - catastrophic

PS - Product Size 2 - critical TE – Technology to be built 3 - marginal

DE – Development Environment 4 - negligible ST – Staff size and experience

In any software the analysis part is the most important part. In risk

management the programmer or software developer can think seriously

about the risk like what kind of risks are there in the project if the risks are

solvable or not or what is the solution or which way he or she can solve the

risk this the main things comes into the analysis part . if this part is good

means developer can analyze the risk so there is a no chance of risk and if

possibly risk is come so it is easily solve

So if developer or programmer can analyze about the risks related to their

project there is a no or less chance of errors and make a nice project. So

risk analysis is the good part to remove the risk or prevent your project to

future risks.

2.2.3 Risk Planning

To assist the project team in developing a strategy for dealing with risk, an effective

strategy must consider three issues:

Risk avoidance.

Risk Monitoring.

Risk management and contiguous planning

Risk Mitigating

Meet with current staff to determine causes for turnover

Mitigate those causes that are under our control before the project starts.

Once the project commences, assume turnover will occur and develop techniques

to ensure continuity when people leave.

Organize project teams so that information about each development activity is

widely dispersed.




Define documentation standards and establish mechanisms to ensure that

documents are developed in a timely manner.

Assign a backup staff member for every critical technologist.

Risk Monitoring

General attitude of team members based on project pressures.

The degree to which the team has jelled.

Interpersonal relationships among team members.

Potential problems with compensation and benefits.

The availability of jobs within the company and outside it.

RMMM Plan

A risk management strategy can be included in the software project plan or the risk

management steps can be organized into a separate Risk Mitigation, Monitoring and

Management Plan.

The RMMM plan documents all work performed as part of risk analysis and is used

by the project manager as part of the overall project plan.

2.3 ESTIMATION2.3.1 Effort Estimation

Today software is the most expensive element of virtually all computer-based systems.

For complex, custom systems, a large cost estimation error can make the difference

between profit and loss. Cost overrun can be disastrous for the developer.

Too many variables-human, technical, environmental, political-can affect the ultimate

cost of software and effort applied to develop it. However, software project estimation

can be transformed from a black art to a series of systematic steps that provide estimates

with acceptable risk.




To achieve reliable cost and effort estimates, a number of options arise:

Delay estimation until late in the project.

Base estimates on similar projects that have already been completed.

Use relatively simply decomposition techniques to generate project cost and effort

estimates.

Use one or more empirical models for software cost and effort estimation.

The COCOMO Model

Like all estimation models for software, the COCOMO models require sizing

information. Three different sizing options are available as part of the model hierarchy:

object points, function points, and lines of source code.

Like functional points, the object point is indirect software that is computed using counts

of the number of

(1) Screens (at the user interface),

(2) Reports,

(3) Components likely to be required to build the application.

Once complexity is determined, the number of screens, reports, and components are

weighted according to Table above. The object point count is then determined by

multiplying the original number of object instances by the weighting factor in table above

and summing to obtain a total object point count. When component based development or

general software reuse is to be applied, the percent of reuse (%reuse) is estimated and the

object point count is adjusted:

NOP = (object points) X [(100 - %reuse) / 100]

Where NOP is defined as new object points. To derive an estimate of effort based

on the computed NOP value, a “productivity rate” must be derived. Table below

presents the productivity rate




PROD=NOP / person-month

For different levels of developer experience and development environment

maturity. Once the productivity rate has been determined, an estimate of project

effort can be derived as

Estimated effort = NOP/PROD




3. PROJECT REQUIREMENT STUDY




3.1 USER CHARACTERISTICS

The user must have basic knowledge of the Computer. User must be familiar with all the

application whose documents are used in the system. The user must be familiar with

these computer based system and their operations done in the system.

HARDWARE REQUIRMENTS

Hardware Minimum Requirement

CPU Speed 1 GHz

RAM 512 MB

Hard-disk Space 20 GB

SOFTWARE REQUIRMENTS

Software RequirementOperating System Window XP or more

Internet Explorer(Front End)

IE 6 +

Tools Visual Studio 2008 SQL Server 2005 MS.NET Framework 3.5

Technology C#.Net

C# Scripting LanguageDocumentation Tools MS Word 2007

Rational Rose




3.2 CONSTRAINTS

Every project has to follow some constrain throughout its lifecycle. Following are the constraints identified that must be followed during the development of my system.Time Constraints: The project should be developed and implemented within the time limit of two months.Personal Constraints: The constraints imposed by the skills possessed by the member for the development. I had to learn C#.NET and then implement the system.3.2.1 Reliability Requirements

The system should be reliable enough in the following areas:

Integrity of data should be maintained, requiring the atomicity of transactions

Loss of data should be minimized

Integrity of the system should be maintained, requiring a tight login security so that only the authorized used is allowed to perform a transaction.

3.2.2 Safety and Security Consideration

Without log into Login Form user cannot access the application.

The database is on centralized server so only authorized user can use this database.




4. SYSTEM ANALYSIS




4.1 REQUIREMENTS OF NEW SYSTEM

The system must be authorized.

The system must be accessible to account branch of company.

The system must be able to store inventory.

Advanced Searching facilities must be included.

The system should be convenient and work according to the Company

Requirements.

Requirement Analysis

In Requirement analysis, we met to the company head and project guide. We

discussed about their requirements and the problems they are facing with existing

system.

Fact Finding Technique

During requirement determination phase, the system analyst has to find out how

the current system works and what is expected from a new system. For that it is

required to spend considerable time in talking with users and gathering all

relevant information on the project.

Information Sources

Main sources of information are:

User of the system.

Documents used in the organization.

Procedure manuals and rulebooks, which specify how various activities,

are carried out in the organization.

Various reports used in the organization.




Analysis of actual data

The data collected during the fact finding study and included in data flow and

decision analysis documentation are examined to determine how well the system

is performing and whether it will.

Meet the organization’s demand.

Reliability

Reliability could be defined as an extend to which application can be perform its

intended function with required precision. It is evaluated by measuring the

frequency and severity of failure and the ability to recover from failure. Thus the

application should be as reliable as possible to overcome the failure and recover

from it.

Maintainability

The application to be developed should be easily maintained and should locate

undiscovered error and fix them as soon as possible. For maintenance of the

application the contact number of the application provider would be given to the

end user to resolve the queries.

Portability

Portability means an effort to transfer the application from one hard ware and/or

software system environment to another. Our application is to be developed in

C#.Net, so the application can be install on various Windows Platform but

the .Net framework needs to be installed.

Efficiency

The application should make optimal use of system resources. Also the runtime

performance of the system should be considered.




Maintenance

Software maintenance applies to following phases in the existing program

Change in software due to errors.

Change in software because the software must be adapted to accommodate

changes in its external environment.

Change in software when the customer requires functional or performance

enhancements.

4.2 FEASIBILITY STUDY

4.2.1 Does the system contribute to the overall objectives of the organization?

As from the feasibility study that we carried out, we can say that the system

contributes to the over all objectives of the organization for which the system is being

developed.

An important outcome of the preliminary investigation i.e. after defining the scope of

the project, the determination that the system requested is feasible or not is required

to done.

4.2.2 Can the system be implemented using the current technology and within the given cost and constraints?

The system has been developed using the current technologies and maintaining the

given specification and the requirements by the organization.

From the study of Economic Feasibility we can say that the system that has been

developed can be implemented with the given cost and constrains.

From the study of Technical Feasibility, the system developed can be implemented

using the current technologies.




4.2.3 Can the system be integrated with other systems that are already in place?

As said earlier that this is a system of managing the pre- production and post-

production process.

So this is a system that can be used separately. So from the study Operational

Feasibility we can say that it has been developed in such way that it can be integrated

with other system and also with the current system that is already in place. But as this

system varies with the type of organization so it definitely depends on the type of

organization with whose system the new system can be integrated.

4.3 REQUIREMENTS VALIDATIONS

It means that the developed software is as per requirement or not? Simply stating

whatever we are doing is right or wrong as per requirements?

Here we check each and every requirement and compare with our product and that it

satisfies the user need.




Class Diagrams

Figure 4.3 System Class Diagram

4.4Data Dictionary

Data is the key to the overall system design and must be structured to meet the user

requirement. The collection of structured data builds up data dictionary, which is an

important tool in data flow analysis. The complete set of data definitions provides the

basis of the data dictionary. It facilitates cross-referencing and assessment of the

implication of changes. Each data item is uniquely identified by its definitions but

referred by different name at different tables.

College of information technology www.kashipara.in

Inventory Control

Login form

User & Password

Inventory Information

show inventory.

Show sell inventory.

Show buy inventory.

Insert details()

Update details()

Delete details()

28



4.5 MAIN MODULES OF NEW SYSTEM

System Administration

In this module, we have developed different functions for Administrators. Admin can

update or delete any details. He can also add, delete new items or details in database

4.6 SELECTION OF HARDWARE AND SOFTWARE AND JUSTIFICATION

C#.NET 2008

I was often surrounded by anti-Microsoft stories and propaganda. However, when I heard about .NET, I decided I wanted to know more and that the best way to do that was to learn at the source.

As I got into the technology and the company, what I found was more than a little surprising. The .NET Framework, the C# language, ASP.NET, and SQL Server are sophisticated and technically beautiful achievements

The platform developers made, and that the resulting system helped to substantially improve my productivity as a developer. I also found the Microsoft engineering teams to be wonderfully bright, creative, and–perhaps most surprising of all.

SQL server 2005

SQL Server 2005 released in October 2005, is the successor to SQL Server 2000.SQL Server 2005 introduced "MARS" (Multiple Active Results Sets), a method of allowing usage of database connections for multiple purposes.

SQL Server 2005 introduced DMVs (Dynamic Management Views), which are specialized views and functions that return server state information that can be used to monitor the health of a server instance, diagnose problems, and tune performance.

SQL Server 2005 introduced Database Mirroring, but it was not fully supported until the first Service Pack release (SP1). In the initial release (RTM) of SQL Server 2005, database mirroring was available, but unsupported. In order to implement database mirroring in the RTM version, you had to apply trace flag 1400 at startup. Database mirroring is a high availability option that provides redundancy and failover capabilities at the database level. Failover can be performed manually or can be configured for




automatic failover. Automatic failover requires a witness partner and an operating mode of synchronous (also known as high-safety or full safety).The main unit of data storage is a database, which is a collection of tables with typed columns. SQL Server supports different data types, including primary types such as Integer, Float, Decimal, Char (including character strings), Varchar (variable length character strings), binary (for unstructured blobs of data), Text (for textual data) among others. The rounding of floats to integers uses either Symmetric Arithmetic Rounding or Symmetric Round Down (Fix) depending on arguments.Microsoft SQL Server also allows user-defined composite types (UDTs) to be defined and used. It also makes server statistics available as virtual tables and views (called Dynamic Management Views or DMVs). In addition to tables, a database can also contain other objects including views, stored procedures, indexes and constraints, along with a transaction log. A SQL Server database can contain a maximum of 231 objects, and can span multiple OS-level files with a maximum file size of 220 TB. The data in the database are stored in primary data files with an extension .mdf. Secondary data files, identified with a .ndf extension, are used to store optional metadata. Log files are identified with the .ldf extension.

4.6.1 Hardware

The hardware selected for development for this project is given below:

CORE 2 Duo processor

1 GB RAM

80 GB Hard Disk




5. IMPLEMENTATION




5.1 IMPLEMENTATION ENVIRONMENT

By applying the implementations and above analysis we have created Web Applications

in Asp.net and SQL database. That is very to operate.

The interrelated database of SQL server 2005 is connected to Asp.net.

5.2 SECURITY FEATURE

Inventory Control is developed in C#.NET and the backend is SQL Server 2005

database which provides maximum security. Security is a key feature of SQL

Server 2005, which provides confidentiality, integrity, and availability of mission-

critical data. User authentication feature in Inventory Control provides authentication so that

any unauthorized user can not use this application.

5.3 CODING STANDARDS

Code conventions are important to programmers for a number of reasons:

60% of the lifetime cost of a piece of software goes to maintenance

Hardly any software is maintained for its whole life cycle by original author.

Code convention improves the readability of the software, allowing engineers to

understand new code more quickly and thoroughly.

If you ship your source code as product, you need to make sure it is as well

packaged and clean as any other product you create.




6.SCREEN SHOT AND USER MANUAL




=>Login




=>Add




=>Buy




=>Sell




=>Show Buy




=>Show Sell




7. CONCLUSION AND DISCUSSION




CONCLUSION

This Desktop application provides easy way to manage Inventory. This application

developed is designed in such a way that any further enhancements can be done with

ease.

This application is going to be used for our company to easily manage document. So, we

are very happy to develop this desktop application as it provides all the requirements of

our company.




Bibliography

BOOKS :

Programming in C# a primer

By: E Balagurusamy

Publication: Tata McGraw Hill

Software Engineering

By: Sommerville

Publication: Low Price Edition

MySQL Server 2005(e-book)

By: Ken Henderson

Publication: Addison-Wesely Professional

WEB REFERENCES:

www.futurismtechnologies.com

www.codeproject.com

www.en.wikipedia.org



http://www.en.wikipedia.org/

http://www.codeproject.com/


www.google.com



Project Report 2

Documents

project user friendly

user friendly project

project guide

project help

project planning

rajkot inventory control

project summary1

project mangement