TABLE OF CONTENTS

S.No. Particulars Page Nos. 2 3-4 5 6 7-10 11 11 12 17 18 19-21 22 22-25 26 27 28-30 30-33 34-35 36-37 38 39-41 42 43

1. Project Objective

2. Company Profile a. Objective b. Fields of Development 3. Companys Products 4. Understanding .Net Framework 5. Accounting a. Objectives b. Classification c. Some Important Terms 6. System Requirements a. Product Definition b. Processing Enviornment 7. SDLC(System Development life Cycle) a. Initial study b. Feasibility Study i. Introduction ii. Types of Feasibility c. System Requirement Specifications d. System Design i. Characteristics ii. DFDS e. System Testing i. Objectives ii. Test Information Flow iii. Basic Methods of Testing f. Implementation And Working i. Types of Implementation ii. Implementation Tools g. Maintenance i. Introduction ii. System Documentation

8. Screen Shots of the Project 9. Bibliography

44 69

PROJECT OBJECTIVE
As accounting is a very generalized field which is used in almost every organization like production, inventory control etc. Since transactions take place daily in almost all organizations where sale, purchase, flow of stock and finance takes place so recording of these transactions is a must. Firstly all the work was done manually, like maintenance of journal, ledger, trial balance, final accounting etc. which may even resulted in wrong calculations and unfair means of adjusting stock. Accounting systems are computerized to journalise, post and prepare reports faster and more reliably. Features of computerized accounting system Control : managers need control over operations. Internal controls are the methods and procedure used to authorize transactions and safeguard assets. Compatibility : A good system should be compatible with business operations, personnel and organizational structure. A system should conform to the particular needs of the business. Flexibility : A well designed system is flexible in accommodating changes without needing a complete overhaul. An accounting system may require changes in accordance to the business changes. Favourable cost/benefit relationship : To develop ,design and maintenance of system costs, money, thereby reducing the companys profitability .So managers strive for a system that offers maximum benefits at a minimum cost resulting into better decisions. Objectives of the project calculate accurately all the transactions complete and proper bill management maintain full records of stock record all the details about customers ,suppliers, salesman etc. prepare reports of all the transactions taking place daily just on one click

prepare final accounts at the end of each financial year to stop all the unfair means of recording the transactions and stock.

COMPANY PROFILE
Alamsoft Systems, Mohali is a Research and development based Company
offering end to end solutions. Company develops both Windows and Web Applications , Windows applications give more flexibility in needs and along with these Web application binds any company at a center place. It develops creative strategies and top-notch applications to help increase revenue, save resources, manage supply chain or enhance customer relationships. Its sole aim is to satisfy customer needs for quality products and services in information technology through well trained and motivated employees.

OBJECTIVE
MANAGEMENT OBJECTIVES To provide world-class information technology solutions and services to enable our customers to serve their customers better. PEOPLE OBJECTIVES To help people in the company's successes, which they make possible; to provide job security based on their performance; to recognize their individual achievements; and help them gain a sense of satisfaction and accomplishment from their work.

MISSION

"Together we create the enterprises of tomorrow to provide world-class information technology solutions and services to enable our customers to serve their customers better".

Business Empowerment (to the power n)

SOLUTIONS: The one stop shop solution center for all IT needs, customized to meet and scale with unique Business Needs. SERVICES: A range of value added services in IT infrastructure operations and management. STANDARDS: World Class Quality standards maintained for PPP (People, Processes & Performance). Alliance with global technology leaders. SAVINGS: We help find new ways to reduce costs & "do more with less" by maximizing the value of technology and personal resources, thereby reducing total cost of ownership(TCO). SATISFACTION: Complete Satisfaction for the customers through offering that enables one to maximize system uptime through rapid response and resolution services, thereby optimizing your IT investments

Fields of Development Web Application Development:

New website Development Website Redesigning E-commerce Shopping system E-commerce Integration Online Payment Integration Business Portal Community Portal

Custom Application Development:

Stand-alone Customized software Client/Server Based Development Web based software development

Flash Websites:
Custom Splash/Introduction page Multimedia CD Presentation

Web Design:
Visual look and feel of website 5

Logo for the website/company

COMPANYs PRODUCTS

Application Software
ERP Solution for School Management System Stock Inventory Cum Billing Software Payroll Management Software including TDS ERP Solution for Educational Academies Library Management System Examination System Contact Manager

Embedded Solutions
SMS Management System

Understanding .Net Frame Work

DEFINITION:
The .Net framework can be defined as a language neutral platform designed to provide a number of rich and powerful application development tools and technologies. It has an extensive class library that provides wide-ranging support for data access. .Net framework has an independent code execution and management environment called the Common Language Runtime (CLR) which ensures that code is safe to run, and provides an abstract layer on top of the operating system, which allows the elements of the .Net framework to run on many operating systems and devices.

THE .NET VISION:

The basic idea behind the development of the .Net framework is that a global broadband network will someday globally connect all devices and the software will become a service provided over this network. The .Net framework provides the foundation and the plumbing on which the Microsoft .Net vision is built. The vision is about having a global network and open standards like XML to make it easier for parties to exchange data and work together. Now devices will use common languages like XML over standardized or shared protocols such as HTTP

and these devices will be running a multitude of software on various operating systems. This is not limited to Microsoft but also to other operating systems such as sun, IBM. The .Net framework provides the tools and the technologies needed to write applications that can seamlessly and easily communicate over the Internet using open standards like XML and SOAP. It also aims at solving the various problems that are faced by developers while working on applications made using the windows DNA. It provides a solution to problems such as registering of components and shutting down applications in order to upgrade them.

BENEFITS OF USING .NET:

The windows platform is inherently complex and may pose several problems for programmers. However the .Net platform is used as it provides solutions to many such problems and offers an Internet centric platform.

The following are the benefits of using .Net platform: Multiple platform Support .Net platform has been designed keeping multiple platform support as a key feature. For version 2.0 this means that the code written using the .Net platform can run on all versions of Windows. i.e. Windows 98,95,NT,2000 and so on. Microsoft has included rich support for all the platforms. Also this code shall also work on any 64-bit processor that may be used by Microsoft later. It is also expected that .Net shall run on other platforms like UNIX also, however it is not for sure that all functionality will be available for the same. . Net as a clean start On the windows platform, the technologies available often depend on the programming language that they are written in, so they are very different. Depending on the chosen programming language, these technologies can be restrictive. The problem with this approach is that it makes the Windows platform harder to understand. Using .Net there is just one simple object oriented way of accessing the functionality of the .Net Framework.

. Net Framework

VB FORM

MFC

ASP

Windows API
(The best and most commonly used technologies being merged in .Net)

Performance . Net has been designed to provide great performance and scalability. For .Net to succeed, the companies must be able to migrate their applications and not suffer due to the way the CLR works. To ensure this CLR converts the code into native machine code. So the conversion can take step-by-step method and will make use of the given machines resources and processor features. As newer versions of the CLR are released and technologies like windows forms are released, each release will have a better performance and smaller memory footprints. Also .Net has succeeded in replacing completely the older technologies like COM with better and efficient design equivalents. At the heart of the .Net platform is the CLR.

.NET FRAMEWORK DRILL DOWN:

The .Net framework consists of four major areas: Application development technologies Class libraries

Base class libraries The Common Language Runtime

Application Development Technologies

. Net Framework

Class Libraries Base Class Libraries Common Language Runtime

(Description of the layered .Net Framework architecture)

The various layers can be explained in detail as: Application Development Technologies: .Net offers technologies for building web applications, providing many new features and a much cleaner programming model. The two main features are: Web Services:These are programmable business logic components that serve as black boxes to provide access to functionality via the Internet using the standard protocols such as HTTP. Web services are based on the application of XML called the SOAP (Simple Object Access Protocol) Windows forms:For developing standard GUI applications, the .Net Framework provides the window forms.

10

Window forms are an extensive class library that exposes the functionality of the Windows common Controls using the Object Oriented capabilities of .net Framework. Class libraries: The .Net Framework provides an extensive set of class libraries. This includes classes for: Data access: High performance data access classes for connecting to SQL server, ORACLE or any other database for which OLEDB or ODBC provider is available. Base Class Libraries: The base class library in the .Net framework is huge. It covers areas such as collections; thread support, code generation, IO, reflection and many more. The list of base class libraries is huge but can be looked in through the Wincv tool that is used to locate them. Common Language Runtime: The CLR proves to be one of the most radical tools use in the .Net Framework. It is a language neutral platform that converts code generated by all the languages in the .Net platform to a language called the (IL) Intermediate Language. This is further converted into the native machine language. The CLR enables the .Net framework to run on a number of different devices. It forms an intermediate layer between the operating system and the .Net Framework.

Accounting
Accounting is the art of recording, classifying and summarizing in a significant
manner in terms of money transactions and events which in part, atleast of a financial character and interpreting the results thereof.

Accounting is the process of measuring and recording the financial value of the assets
and liabilities of a business and monitoring these values as they change with the passage of time. When we refer to a business we could be referring to an individual, a company or any other entity for which accounting records are to be kept Objectives of accounting To ascertain whether the business operations have been profitable or not. 11

To ascertain the financial position of the business. To generate information. Systematic record of business transactions.

The organizational accounting system provides information in the form of ledger accounts maintained in the books of accounts. The additional information that is needed is obtained by deriving it from the information that is existing in the ledger accounts. Classification of accounting The ledger accounts maintained within an organizational accounting system are classified into three as Personal, Real and Nominal. Real Accounts Real accounts are related to tangible aspects. In general we can identify that all asset accounts are real accounts. Personal Accounts Personal accounts are related to persons and organizations. These are persons/organization which owe the organization or to whom the organization owes. In effect they either form creditors (liabilities) or debtors (assets). Nominal Accounts Nominal accounts are related to expenses, losses, incomes and gains. Since ascertaining profits or losses involves dealing with incomes, gains, expenses and losses we can conclude that all the nominal accounts together would give us the information relating to the profits or losses made by the organization.

Some Important Terms

Assets
The assets of a business are those things that belong to the business that have a positive financial value i.e. items that could be sold by the business in exchange for money. Examples of assets include land, buildings, vehicles, stock, equipment, rare gold coins, bank accounts with positive balances and money owed to the business by its debtors. Real accounts and Personal accounts are capable of being called assets. Any element (account) that is capable of being liquidated (that is capable of being converted to

12

cash by giving it away) indicates an asset. Machinery, Furniture, Cash, etc are real accounts that can be called assets. Debtors represent Assets Debtors represent the persons and organization who owe to the organization. They would clear their dues by paying out either in cash or in some other form. Thus Debtors get liquidated and as such can be called assets.

Liabilities
The liabilities of a business are those things that belong to the business but unlike assets have a negative financial value i.e. items that will require the payment of money by the business at some point in the future. Examples of liabilities include unpaid bills, unpaid taxes, unpaid wages, rusty motor vehicles, stock that has passed its use-by date, overdrawn bank accounts and money owed by the business to its creditors. All elements representing liabilities are Personal accounts. An element that is capable of being cleared by paying out indicates a liability. Creditors represent Liabilities Creditors represent the persons and organization to whom the organization owes. The organization would clear its due by paying them either in cash or in some other form. Thus creditors are cleared by paying out and as such can be called liabilities.

Equity
The equity of a business is defined as the value of the assets minus the value of the liabilities. In other words the equity is the financial value that would be left if all the assets were sold and the money from the sale was used to pay off all the liabilities. Another way of expressing this is to say that the equity is the amount of money that would be released if the business was to be wound up.

Accounting Period
Accounting Period is that period for which the organization ascertains the profit or loss. If the organization is trying to ascertain the profits made over a year, then the accounting period is a year. If it is trying to ascertain the profits made over a six months period, then the accounting period is six-months.

13

There are two aspects relating to an accounting period. The length of the period as well as the being/end dates of the period. These can be ascertained from the way the accounting period is stated. For example, where the accounting period of an organization is stated as From 1st July to 31st December, This implies that the length of the accounting period is 6 months. One year and starts on 1st January every year. This implies that the accounting period is from 1st January to 31st December and is one year long.

Final Accounts
Two main objectives of maintaining accounts are to find out the profit/loss made by the business at the end of a regular periodic interval and to ascertain the financial position of the business on a given date. Final accounts are prepared to achieve these objectives of accountancy. Trading and Profit /Loss Account and Balance Sheet are prepared to give the final results to the business, so these are collectively called as Final Accounts Trading and Profit and Loss Accounts To derive the information relating to profits from these nominal accounts a ledger account by name "Trading and Profit & Loss a/c" is prepared. Preparation of these ledger accounts requires us to think beyond just transferring the information in the nominal accounts into these accounts. Almost in all cases, we use two separate ledger accounts "Trading a/c" and "Profit and Loss a/c" to derive information relating to profits with a greater detail. [The more the information we need, the more the accounting heads we need to maintain]. Since all the nominal accounts have been dealt with in deriving the information relating to profits and we are left with only the real and personal accounts which represent either assets or liabilities we can conclude that all the real and personal accounts together give us the information relating to the position of the organization.

Balance Sheet To derive the information relating to the position of the organization from these real and personal accounts a statement by name "Balance Sheet" is prepared. However preparing the Balance sheet need us to think a bit beyond just listing out the information relating to the personal and real accounts in the statement.

14

The assets, liabilities and equity of a business are all financial measurements that relate to a particular point in time. The financial statement that is used to present this information is known as the balance sheet. The balance sheet is a statement of the assets, liabilities and equity of a business as they exist at a particular point in time. The relationship between the assets, the liabilities and the equity can be represented algebraically by what is commonly known as the accounting equation. If we use the letter A to represent the assets, the letter L to represent the liabilities and the letter P to represent the equity then the accounting equation is P=A-L This equation states that the equity is the value of the assets minus the value of the liabilities. This equation is more commonly written as A=L+P This equation states that the value of the assets is equal to the value of the liabilities plus the equity. This is just another way of saying the same thing. Because the equity is defined as the value of the assets minus the value of the liabilities then this equation is always true by definition. A balance sheet is commonly divided into two sections. One section shows the value of the assets and the other section shows the value of the liabilities and the equity. Each section will be broken down into more or less detail depending on the intended use of the balance sheet. Because the accounting equation is always true the totals of each of the two sections of the balance sheet should always be the same i.e. the balance sheet should always be in balance. The income of a business is the sum of those things that increase the value of the assets without any corresponding increase in the liabilities or any new investment by the owners of the business. Examples include revenue from the sale of goods, equipment or services supplied, rent or interest received and capital gains. The expenses of a business are those things that reduce the value of the assets without any corresponding reduction in the liabilities or any capital drawings by the owners. Examples include the cost of stock and raw materials, rent or interest paid, electricity bills, telephone, wages, taxes, dividends, depreciation and donations to charity. The income and expenses of a business are financial measurements that relate to a specified period of time rather than a specific point in time. The financial statement that is used to present this information is known as the income statement. The

15

income statement is a statement of the income and expenses of a business as they occur during a specific period. If we use the letter I to represent the income over a specified period of time and the letter E to represent the expenses over that same period we can represent the relationship between the assets, the liabilities, the equity, the income and the expenses by using a modified form of the accounting equation as follows A = L + P + (I - E) This equation states that the value of the assets is equal to the value of the liabilities plus the equity plus the excess of income over expenses. Another way of writing this equation is A+E=L+P+I This equation states that the value of the assets plus the expenses is equal to the value of the liabilities plus the equity plus the income. This is just another way of saying the same thing. However it is helpful to express it in this way when we come to consider the practice of bookkeeping below. The income statement is commonly divided into two sections in a similar fashion to the balance sheet. One section shows the total income and the other section shows the total expenses. Like the balance sheet each section will be broken down into more or less detail depending on its intended use. However unlike the balance sheet the totals of each of the two sections are unlikely to be the same. The difference will usually be shown as a separate item at the bottom of the income statement and if the total income exceeds the total expenses it will be given a title such as retained earnings, net profit or excess of income over expenditure. If the total expenses exceed the total income it will instead be called something like retained loss, net loss or excess of expenditure over income. Income and expenses are financial measurements that relate to the performance of a business during a specified period of time. For this reason the income statement is also known as the statement of financial performance. It describes the performance of a business during a specified period. It is sometimes also referred to as the profit and loss statement.

When is the information relating to profits & position collected/derived 16

Information needs vary from organization to organization. Even the information relating to profits and position would also be derived for such periods and on such dates respectively depending on the organizations need or this information. Period for which profits are ascertained The information relating to profits is something that is needed by the organization periodically. For what period do we try to ascertain profits . Do we think of profits made every day or over a week or over a month or over a six month period or over a year? This is dependent on the information needs of the organization. Though theoretically it is possible to derive this information's for any time period, conventionally it is derived for a year. That is in most cases, information relating to profits is derived over a year. We think of profits made over a year. Day on which position is ascertained The information relating to the position may be needed by the organization at many points of time. Theoretically this is also capable of being derived at any point of time we need it. However, conventionally it is derived at a point which indicates the end of the period for which the profits are ascertained. Say if we think of profits made for the period from 1st April 2005 to 31st March 2006, we think of deriving the position as on 31st March 2006.

17

SYSTEM REQUIREMENTS

PRODUCT DEFINITION
Computerized systems are organized by function, or task. Access to functions is arranged in terms of menus. In such a menu-driven system, one must first access the most general group of functions, called the main menu, then choose from one or more submenus until one reaches the final function one needed. The main menu is classified into three parts: Administration:- it includes all the entries of the master tables, these tables are rarely modified on daily basis. Transaction:- it deals with transaction tables which are updated regularly on daily basis Since the sale, purchase takes place on daily basis affecting the amount of stock owned. Reports:- reports provide the detailed as well as summarized information about the daily transactions ,a DayBook is created for that. Ledger, Profit/Loss Account, Trading Account, Balance Sheet are also created. Accounting systems are computerized to journalise , post and prepare reports faster and more reliably. Objectives of the project calculate accurately all the transactions complete and proper bill management maintain full records of stock record all the details about customers ,suppliers, salesman etc. prepare reports of all the transactions taking place daily just on one click prepare final accounts at the end of each financial year to stop all the unfair means of recording the transactions and stock.

18

PROCESSING ENVIORNMENT

Minimum Software Requirement

ASP.NET C# SQL Server 2005 HTML IIS 5.0 Microsoft Windows 2000

Minimum Hardware Requirement

CPU Configuration Pentium-4 processor 20/40 GB HDD 256 MB SDRAM 1.44 MB FDD CD ROM Super VGA Color Monitor Key board Mouse Printer

19

SDLC (System Development Life Cycle) Initial Study

INTRODUCTION
The first step in the Software Development Life Cycle (SDLC) is the preliminary investigation to determine the feasibility of the system. The purpose of the preliminary investigation is to evaluate project requests. It is not a design study nor does it include the collection of details to describe the business system in all aspect. Rather it is the collection of the information that helps committee members to evaluate the merits of the project request and make an informed judgment about the feasibility of the proposed project. The preliminary investigation should accomplish the following objective Determine the size of the project. Assess Cost and Benefits of alternative Approaches Determine the technical and operational feasibility of alternative approaches. Report the findings to management; with recommendations outlining the acceptance or rejection of the proposal.

INVESTIGATION PHASE
The investigation phase is also known as the fact-finding stage or the analysis of the current system. This is a detailed study conducted with the purpose of wanting to fully understand the existing system and to identify the basic information requirements. Various techniques may be used in fact-finding and all fact obtained must be recorded. A thorough investigation was done in every effected aspect when determining whether the purposed system is feasible enough to be implemented.

CONDUCTING THE INVESTIGATION

20

The data that the analysts collect during preliminary investigations are gathered through three primary methods: Reviewing organization documents Onsite Observation Conducting Interviews

PROPOSED SYSTEM
The proposed system handles all the faults of the existing system. In the proposed system everything is done online. Customers can get the best deal regarding their projects without visiting offices. Customers will post their complaint specifications through this unique method of handling complaints. Customers can also post any suggestions or whether their complaint has been handled or not.

CONSTRAINTS AND LIMITATIONS

The constraints and limitation within a system are the drawbacks that occur during the implementation of the system. These limitations and constraints can crop up in almost every system. The most important fact is to find a way to overcome these problems. Software design is the first of three technical activities Design Code Generation Test Those are required to build and verify the software. Each activity transforms information in manner that ultimately results in validated computer software. The design task produces a data design, an architectural design, an interface design and component design. The design of an information system produces the details that clearly describe how a system will meet the requirements identified during system analysis. The system design process is not a step by step adherence of clear procedures and guidelines. When I started working on system design, I face different types of problems; many of these are due to constraints imposed by the user or limitations of hardware and software available.

21

Some times it was quite difficult to enumerate that complexity of the problems and solutions thereof since the variety of likely problems is so great and no solutions are exactly similar however the following consideration I kept in mind during design phased.

DESIGN OBJECTIVES
The primary objective of the design is to deliver the requirements as specified in the feasibility report. These are the some of the objectives, which I kept in mind. Practicality The system is quite stable and can be operated by the people with average intelligence. Efficiency I tried to involve accuracy, timeliness and comprehensiveness of the system output . Cost It is desirable to aim for the system with a minimum cost subject to the condition that it must satisfy the entire requirement. Flexibility I have tried that the system should be modifiable depending on the changing needs of the user. Such modifications should entail extensive reconstructing or recreation of software. Security This is very important aspect which I followed in this designing phase and tried to covers the areas of hardware reliability, fallback procedures, and physical security of data.

CONCLUSION

22

From the initial study we concluded that the customers and Company were facing various kinds of problems and the proposed system is helpful in solving them.

Feasibility Analysis
INTRODUCTION WHAT IS A FEASIBILITY STUDY?
Prior to stating whether the system we have to develop is feasible or not we believe that we should emphasize on what is implied by the word Feasibility. Feasibility is the measure of how beneficial or practical the development of the system will be to the organization. It is a preliminary survey for the systems investigation. It aims to provide information to facilitate a later in-depth investigation. The report produced at the end of the feasibility study contains suggestions and reasoned arguments to help management decide whether to commit further resources to the proposed project. Having gone through all measures of feasibility we report to the management to figure out if the objectives of the new system are met. For e.g. - Is the system within the budget allowed for it? Will the organizations needs, be met by the new proposed system as Originally envisaged? If and when the objectives of the system are met and the new system is approved, then the more specific details in the proposal should be considered and approved. 23

TYPES OF FEASIBILITY
There are various measures of feasibility that helps to decide whether a particular project is feasible or not. These measures include Operational Feasibility Technical Feasibility Economical and Financial Feasibility

Operational Feasibility A proposed system is beneficial only if it can be turned into an information system that will meet the operational requirements of an organization. A system often fails if it does not fit within existing operations and if users resist the change.

Important issues a systems developer must look into are: Will the new system be used if implemented in an organization? Are there any major barriers to implementation or is proposed system accepted without destructive resistance? Compared to the semi-computerized system the chances of avoiding errors in a computerized system is much higher because the user need not stress himself unnecessarily resulting in recklessness. Unlike the semi-computerized system there would be backup data for all the information concerning the daily transactions occurred within the organization. Another important fact to be regarded is the security control, which is handled by the system. Since data regarding each Customer and the Organization is confidential, security is a key issue. Information falling into the wrong hands could jeopardize the entire organization. Unlike in semi-computerized systems the proposed system offers adequate control to protect the organization against fraud and embezzlement and guarantees the accuracy and Security of data and information. This is handled by the system providing individuals with separate login names and passwords. The new system is user-friendlier, which enables the end-user to complete his/her work efficiently and accurately with interest. After taking the above fact into consideration we can state the operating of the proposed system within the organization is feasible. In this phase of the feasibility study the following two main topics

24

 Technical Performance Aspect Acceptance within the organization Technical performance aspect is explained in the technical feasibility report and there is no new information is needed in this to explain it again, but as for the acceptance within the organization the following points are important and those are explained according to the topics Whether the system provides right information to the right place? In the current system which is the semi computerized system the information may be lost in the process of sending from one place to another. This is mainly due to human interaction in the process of the transferring information from one place to another. Whether the new system affects the current users in the system? The new proposed system will affect the users in the following areas Accuracy - Efficiency - Productivity - Robustness - Lesser time consuming

Technical Feasibility Based on the outline design of system requirements in terms of inputs, outputs, files, procedures and staff, the technical issues raised during technical feasibility include: Does the necessary technology exist to do what is proposed? Does the proposed equipment have the technical capacity to hold the data required to use in the new system? Adequate responses provided by the proposed system? Is the system flexible enough to facilitate expansion? Is there any technical guarantee of accuracy, reliability, ease of access and data security? The system developers task is to view needed capabilities in light of currently available technology. Since the existing system is semi-computerized it is clear to us that there is no efficiency in the use of technology within the organization. The solution is the implementing the new computerized system, which works hand in hand with high technology.

25

A database has to be maintained in order to update and backup data whenever a transaction occurs. To create databases we use SQL server. After taking the above facts into consideration we can state that the new proposed system is technically feasible. System Security System security is a vital aspect when it comes to developing a system. The system should ensure the facility of preventing unauthorized personnel from accessing the information and the data within the system. The system should provide total protection for each users information so that the integrity of data is sustained and also prevent hackers from hacking the system. The proposed system ensures the security and the integrity of data. This is done by providing a password login system for each authorized users. And for example the System Administrator has access to all kinds of information. By providing this facility information is properly managed and information is protected. For example the system administrators day to day tasks are lessened and easier because

he doesnt have to have a constant eye on the system and worry about hackers hacking the system. Economical and Financial Feasibility In making recommendations a study of the economics of the proposed system should be made. The proposed System must be justifiable in terms of cost and benefit, to ensure that the investment in a new/changed system provides a reasonable return. Cost-benefit analysis of information is complicated by the fact that many of the systems cost elements are poorly defined and that benefit can often be highly qualitative and subjective in nature. In our proposed system various costs are evaluated. Even though finding out the costs of the proposed project is difficult we and assume and estimate the costs and benefits as follows.

26

According to the computerized system we propose, the costs can be broken down to two categories. Costs associated with the development of the system. Costs associated with operating the system.

Software Requirement Specifications

The software requirement specification is produced at the culmination of the analysis task. The function and performance allocated to software as part of system engineering are refined by establishing a complete information description, a detailed functional description, a representation of system behavior, an indication of performance requirement and design constraints appropriate validation criteria, and other information pertinent to requirement. The introduction to software requirements specification states the goals and objectives of the software, describing it in the context of the computer based system. The Information Description provides a detailed description of the problem that the software must solve. Information content, flow and structure are documented. A description of each function required to solve the problem is presented in the Functional Description. 27

Validation Criteria is probably the most important and ironically the most often neglected section of the software requirement specification. Software requirement specification can be used for different purpose. Here are the major uses.

STATEMENT OF USER NEEDS

The main purpose of the product specification is to define the need of the products user. Some times, the specification may be a part of a contract sign between the producer and the user. It could also form part of the user manuals. A users needs are sometimes not clearly understood by the developer. If this is the case, a careful analysis involving many interactions with the user should be devoted to reaching a clear statement of requirements; in order to avoid possible misunderstandings. Sometimes, at the beginning of a project, even the user has no clear idea of what exactly the desired product is. Think for instance of user interface , a user with no previous experience with computer products may not appreciate the difference between , say menu driven interaction and a command line interface. Even an exact formation of system functions and performance may be missing an initial description produced by an inexperienced user. Specifications are also used as a reference point during product implementation. In fact, the ultimate goal of the implementation is to build a product that needs specification. Thus the implementers use specifications during design to make design decisions and during the verification activity to check that the implementation compiles with specifications.

System Design
INTRODUCTION:
System design is the process of developing specifications for a candidate system that meet the criteria established in the system analysis. Major step in system design is the preparation of the input forms and the output reports in a form applicable to the user. The main objective of the system design is to make the system user friendly. System design involves various stages as: Data Entry Data Correction Data Deletion Processing 28

Sorting and Indexing Report Generation System design is the creative act of invention, developing new inputs, a database, offline files, procedures and output for processing business to meet an organization objective. System design builds information gathered during the system analysis.

CHARACTERSTICS OF A WELL DEFINED SYSTEM

In design an efficient and effective system is of great importance to consider the human factor and equipment that these will require to use. System analyst must evaluate the capabilities and limitations of the personal and corresponding factors of the equipment itself. The characteristics associated with effective system operations are: Accessibility Decision Making Ability Economy Flexibility Reliability Simplicity Success is a new system pivots on its acceptance or non-acceptance by the organization. Personnel If the operating system is convinced that the new system will not benefit them, it appears one, and the system is in serious trouble. To overcome this resistance participation by operating personal during all phases of the changeover is necessary because they constitute the organization, which must use alive in with newly design system. An effective system produces not only information at the lowest cost pertinent and timely for making decision.

Data Flow Diagrams

In the DFD, we give names to data flows, processes, and data stores. Although the names are descriptive of the data, they do not give details. So the following the DFD, our interest is to build some structured place to keep details of the contents of data flow, processes, and data store. A data dictionary is a structured repository of data about data. It is a set of rigorous definition of all DFD data element and data structure 29

DFD Symbols In the DFD, there are four symbols, A Square defines a source (originator) or destination of system data. An Arrow identifies data flow- data in motion .It is pipeline through which information flows. A circle or a bubble (or a oval bubble) represents a process that transforms incoming data flow(s) into outgoing data flow(s) An open rectangle is a data store-data at rest , or temporary repository of data.

The following conventions were used in the data flow diagrams:

Processes are operations that are performed on data. The operations may include computations, decisions, and functions that edit, delete and produce new data. A Process is represented by a circle (oval) and is labeled with the operations it performs. Data stores are information sources (in the system the data store is the database). Boxes with lines on the vertical axes represent these. An Agent is a person, organization or entity external to the system that gives and receives information. Rectangular boxes are used to represent agents. Finally, Arrows represent either data being passed from one part of the system to another or methods used to access parts of the system. Arrows can be unidirectional or bidirectional (data flowing between processes).

DFD-Sales Transactions

30

Series

Sales

Voucher Transact ions

Sales

Customer

Salesman Stock Transacti ons

Voucher Transactions

Products

Stock Transactions

DFD Purchase Transactions

31

Series

Purchase

Voucher Transact ions

Purc hase

Supplier

Godown Stock Transacti ons

Voucher Transactions

Products

Stock Transactions

System Testing
32

INTRODUCTION
The purpose of system testing is to identify and correct errors in the candidate system. Testing is and important element of software quality assurance ad represents the ultimate review of specification, design and coding. The increasing visibility of the software as a system element and the cost associated with a software failure are motivated forces for well planned, through testing. System testing was conducted in order to detect errors and for comparing then the final system with the requirement specification reports, i.e. whether the system meets requirements. During testing the software was executed with the set of test cases and the output of programs for the test cases was evaluated to determine if the program is performing as it was expected to. Testing presents an interesting challenge for the software engineers attempt to build software from an abstract concept to an acceptable implementation. In testing engineer create a series of test cases that occurs when errors are uncovered. Testing is the process of executing a program for finding errors. A good test is one that has the high probability of finding an uncovered error. A successful error is one that uncovers undiscovered errors. The term error is used to refer the difference between actual output of the software and the current output. Fault is a condition that causes the software to fail to perform its required function. Software reliability is defined as a required function. Software reliability is defined as the probability that the software will not undergoes failures for a specified times under specified condition. Failure is the inability of a system or a component to perform a required function according to its specification. Different levels of testing were employed for software to make it error free, fault free and reliable.

UNIT TESTING
Unit testing was conducted first. Different modules of the software were tested against the specifications produced during design of the modules. Verification of the code produced during the coding phase was done. Each module was tested separately.

33

Unit testing focuses verification effort on the smallest unit of software design module. This uncovers errors within the boundary of a module. Unit testing is actually White box testing both the external things as well as the internal codes are tested. In testing, the interfaces are tested in order to ensure the proper flow of data in and out of the module. The boundary testing is done to ensure that the module keeps the limit of it. All independent paths are tested to ensure that all statements are tested at least once. At last the error path is also tested. Unit testing comprises the set of tests performed by an individual programmer prior to integration of the unit into a larger system. There are four categories of test that can be performed on a program unit. Functional Unit Performance Unit Stress Unit Structure Unit

SYSTEM TESTING
Then system testing was conducted. Here the entire software system was tested. The reference document used for this process was requirement document and the goal was to see if the software meets its requirements. System testing includes the thorough testing of the product. System testing is actually a series of different tests whose primary purpose is to fully exercise the computer-based system. The tests are recovery testing: this checks the recovery of the system when failure occurs. This is to ensure that there are recovery procedures for error occurrences. System testing involves unit testing, integration testing, acceptance testing. Careful planning and scheduling are required to ensure that modules will be available for integration into the evolving software product when needed. A test plan has the following steps: Prepare test plan Specify conditions for user acceptance testing Prepare test data for program testing Prepare test data for transaction path testing 34

 Plan user testing Compile/Assemble program Prepare job performance aids Prepare operational documents

OBJECTIVES OF TESTING
First of all objectives should be clear Testing as a process of executing a program with the intent of finding errors. To perform testing, test cases are designed. A test case is a particular made up of artificial situation upon which a program is exposed so as to find errors. So a good test case is one that finds undiscovered errors. If testing is done properly, it uncovers errors and after fixing those errors we have software that is being developed according to specifications. The above objective implies a dramatic change in viewpoint .The move counter to the commonly held view than a successful test is one in which no errors are found. In fact, our objective is to design tests that a systematically uncover different classes of errors and do so with a minimum amount of time and effort.

TESTING PRINCIPLES
Before applying methods to design effective test cases, software engineer must understand the basic principles that guide the software testing process. Some of the most commonly followed principles are: All test should be traceable to customer requirements as the objective of testing is to uncover errors, it follows that the most severe defects (from the customers point of view) are those that causes the program to fail to meet its requirements. Tests should be planned long before the testing begins. Test planning can begin as soon as the requirement model is complete. Detailed definition of test cases can begin as soon as the design model has been solidated. Therefore, all tests can be planned and designed before any code can be generated. The Pareto principle applies to software testing stated simply the Pareto principle implies that 80 percent of all errors uncovered during testing will likely be traceable to 20 percent

35

of all program modules. The problem of course, is to isolate these suspects modules and to thoroughly test them.

Testing should begin in the small and progress towards testing in large. The first tests planned and executed generally focus on individual modules. As testing progresses, testing shifts focus in an attempt to find errors in integrated clusters of modules and ultimately in the entire system.Exhaustive testing is not possible. The number of paths permutations for impossible to execute every combination of paths during testing. It is possible however to adequately cover program logic and to ensure that all conditions in the procedural design have been exercised. To be most effective, an independent third party should conduct testing. By most effective, we mean testing that has the highest probability of finding errors (the primary objective of testing). Software project management is an umbrella activity within software engineering. It begins before any technical activity is intimated and continues throughout the definition, development, and maintenance of computer software. Three ps 1 have a substantial influence on software project management people, problem, and process. People must be organized into effective teams, motivated to do high quality software work, and coordinated to achieve effective communication. The problem communicated from customer to developer, partitioned (decomposed) into its constitute parts, and positioned for work by the software team. The process must be adapted to the people and the problem. A common process framework is selected, an appropriate software engineering paradigm is applied, and a set of work is chosen to get the job done. The pivotal element in all software projects is people. Software engineers can be organized in a number of different team structures that range from traditional control hierarchies to Open paradigm team. A variety of coordination and communication techniques can be applied to support the work of the team. In general, formal reviews and informal person-to-person communication have the most value for the practitioners.

TEST INFORMATION FLOW

Testing is a complete process. For testing we need two types of inputs:

36

SOFTWARE CONFIGURATION
It includes software requirement specification, design specification and source code of program. Software configuration is required so that testers know what is to be expected and tested.

TEST CONFIGURATION
It is basically test plan and procedure. Test configuration is testing plan that is, the way how the testing will be conducted on the system. It specifies the test cases and their expected value. It also specifies if any tools for testing are to be used. Test cases are required to know what specific situations need to be tested. When tests are evaluated, test results are compared with actual results and if there is some error, then debugging is done to correct the error. Testing is a way to know about quality and reliability. Error rate that is the occurrence of errors is evaluated. This data can be used to predict the occurrence of errors in future.

TEST CASE DESIGN

We know, test cases are integral part of testing. So we need to know more about test cases and how these test cases are designed. The most desired or obvious expectation from the test cases is that it should be able to find most errors with the least amount of time and effort. A software product can be tested in two ways. In first approach, only overall functioning of the product is tested. Inputs are given and outputs ate checked. This approach is called black box testing. It does not care about the internal functioning of the product. The other approach is called white box testing. Here the internal functioning of the product is tested. Each procedure is tested for its accuracy. It is more intensive than black box testing. But for the overall product both these techniques are crucial. There should be sufficient number of tests in both categories to test the overall product. 37

BASIC METHODS OF TESTING WHITE BOX TESTING

White box testing is performed to reveal problems with the internal structure of a program. This requires the tester to have detailed knowledge of the internal structure. A common goal of white box testing is to ensure a test case exercises every path through a program. A fundamental strength that all white box strategies share is that the entire software implementation is taken into account during testing, which facilitates error detection even when software specification is vague or incomplete. The effectiveness or thoroughness of white box testing is commonly expressed in terms of test or code coverage metrics, which measure the fraction of code exercised by test cases.

BASIC PATH TESTING

It is a white box technique. It was proposed by Tom McCabe. These tests guarantee to execute every statement in the program at least one time during testing. Basic set is the set of all execution paths of a procedure.

BLACK BOX TESTING

Black box tests are performed to access how well a program meets its requirements, looking for incorrect or missing functionality. Functional tests typically exercise code with valid or nearly valid input for which the expected output is known. This includes concepts such as boundary values. Performance tests evaluate response time, memory usage, throughput, device utilization and execution time. Stress tests push the system to or beyond its specified limits to evaluate its robustness and error handling capabilities. Reliability tests monitor system response to representative user input, counting failures over time to measure or certify reliability. 38

Black box testing uncovers the following types of errors: Incorrect or missing functions Interface errors External database access Performance errors Initialization and termination errors

INTEGRATION TESTING
One of the most difficult aspects of software development is the integration and testing of large untested subsystems the integrated system frequently fails in significant ands mysterious ways, and it is difficult to fix it. Integration testing exercises several units that have been combined to form a module, subsystem or system. Integration testing focuses on the interfaces between units, to make sure the units work together. The nature of this phase is certainly white box, as we must have knowledge of the units to recognize if we have been successful in focusing them together in the module.

CONCLUSION
The system has been developed for the given condition and is found working effectively. The developed system is flexible and changes whenever can be made easy. Using the facilities and functionalities of .Net, the software has been developed in a neat and simple manner, thereby reducing the operators work. The speed and accuracy are maintained in proper way. The user friendly nature of this software developed in .Net framework is very easy to work with both for the higher management as well as other employees with little knowledge of computer. The results obtained were fully satisfactory from the user point of view. The system was verified with valid as well as invalid data in each manner. The system is run with an insight into the necessary modifications that may require in the future. Hence the system can be maintained successfully without much effort.

39

 Implementation and Working

Implementation is the stage in the project where the theoretical design is turned into the working system and is giving confidence to the new system for the users i.e. will work efficiently and effectively. It involves careful planning, investigation of the current system and its constraints on implementation, design of method to achieve the change over, an evaluation, of change over methods. A part from planning major task of preparing the implementation is education of users. The more complex system is implemented, the more involved will be the system analysis and design effort required just for implementation. An implementation coordinating committee based on policies of individual organization has been appointed. The implementation process begins with preparing a plan for the implementation for the system. According to this plan, the activities are to be carried out. Discussions may be regarding, the equipment which has to be acquired to implement the new system. Implementation is the final and important phase. The most critical stage is in achieving a successful new system and in giving the users confidence that the new system will work and be effective. The system can be implemented only after thorough testing is done and if it found to working according to the specification. This method also offers the greatest security since the old system can take over if the errors are found or inability to handle certain types of transaction while using the new system. At the beginning of the development phase a preliminary implementation plan is created to schedule and manage the many different activities that must be integrated into plan. The implementation plan is updated throughout the development phase, culminating in a

40

change over plan for the operation phase. The major elements of implementation plan are test plan, training plan, equipment installation plan, and a conversion plan.

TYPES OF IMPLEMENTATIONS
Implementation of a computer system to replace a manual system. Implementation of a new computer system to replace an existing system Implementation of a modified application to replace an existing one, using the same computer Successful implementation may not guarantee improvement in the organization using the new system, but improper installation will prevent it.

It has been observed that even the best system cannot show good result if the analysts managing the implementation do not attend to every important detail. This is an area where the systems analysts need to work with utmost care.

IMPLEMENTATION TOOLS
Training personnel Conversion Procedures Post-implementation review

TRAINING OF PERSONNEL
Even well designed system can succeed or fail because of the way they are operated and used. Therefore, the quality of training received by the personal involved with the system in various capacities helps or hinders and may even prevent the successful implementation of management information system. Those who are directly or indirectly related with the system development work must know in detail what must know in detail what their roles will be, how they can make efficient use of the system and what the System will or will not do for them. Both system operators and users need training.

SYSTEM OPERATOR TRAINING

41

Running of the system successfully depends on the personnel working in the Computer Centre. They are Responsible for providing the necessary support. Their training must ensure that they are able to handle all possible operations, both routine and extra-ordinary in nature. If the system calls for the installation of new equipment, such as new computer system, special terminals or different data entry machines, the operators training should include such fundamentals as how to turn the equipment on and use it, how to power off and a knowledge of what constitutes normal operations. The operators should also be trained on different type of malfunctioning, how to recognize them and what steps should also be taken whenever they arise.

USER TRAINING
User may be trained on use equipment, particularly in the case where, e.g. a microcomputer is in use and individual involved is both operator and user. In such cases, user must be given training on how to operate and user. In such cases, user must be given training on how to operator the system also. Questions that may be trivial to the analyst, such as how to turn on a terminal, how to insert a diskette into a micro-computer or when it is safe to turn off equipment with out danger of data loss are significant problems to new users who are not familiar. In most of the cases user training deals with the operation of the system itself, with proper attention given to data handling techniques. It is imperative that users be properly trained in methods of entering transaction, editing data, formulating inquiries, deleting and inserting of records. No training is complete without familiarizing users with simple systems maintenance activities. Weakness in any aspect of training may lead of awkward situation that creates user frustration and error.

CONVERSION METHODS
A conversion is the process of changing from the old system to the new one. It must be properly planned and executed. Four methods are common in use. They are Parallel Systems, Direct Conversion, Pilot System and Phase In method. Each method should be considered in the light of the opportunities that it offers and problems that it may create. In general, system conversion should be accomplished in shortest possible time. Long

42

conversion periods create problems for all persons involved including both analysts and users.

PARALLEL SYSTEMS
The most secure method of converting from an old to new system is to run both systems in parallel. This method is safest one because it ensures that in case of any problem in using new system, the organization can still fall back to the old system without the loss of time and money. The disadvantages of parallel systems approach are: It doubles operating costs. The new system may not get fair trial.

DIRECT CONVERSION
This method converts from the old system to new system abruptly, sometimes over a weekend or even overnight. The old system is used until a planned conversion day, when it is replaced by the new system.

PILOT SYSTEM
Pilot approach is often preferred in the case of the new system, which involves new techniques or some drastic changes in organization performance. In this method, a working version of the system is implemented in one part of the organization, such as a single work area or department.

PHASE-IN METHOD
This method is used when it is not possible to install a new system throughout an organization all at once. The conversion of files, training of personnel or arrival of equipment may force the staging of the implementation over a period of time, ranging from weeks to months.

43

POST IMPLEMENTATION REVIEW

After the system is implemented and conversion is complete, a review should be conducted to determine whether the system is meeting expectations and where improvements are needed. A post implementation review measures the systems performance against predefined requirement. It determines how well the system continues to meet the performance specifications.

Maintenance
INTRODUCTION
After a system has been executed and produced satisfactory results, its stored as a software package or in system library. The needs of an organization may change with time and a lot more may be expected from the system and this needs either development of a new system or modifications in the existing program. Modification in the system may also be required if it fails to working changed environments, which may be caused by the use of better machines. The system maintenance means continuous modification and updating of the system to meet the requirements of the users. Its certainly cheaper than developing a new system. Technical documentation plays an important role in the system maintenance. Maintenance is the enigma of system development. It holds the software industry captive, typing up programming resources. Analysts and programmers spend far more

44

time maintaining programs then they do writing them. Maintenance can be classified as corrective, adaptive or perfective.

MAINTAINENCE
Software system maintenance covers a wide range of activities, including correcting coding and design errors, updating documentation and test data and upgrading user support. It is the process of changing the system to maintain its ability to survive. The system design can adopt any of the under given system maintenance strategies. Corrective Maintenance The design software can be maintained by corrective maintenance that is concerned with fixing reported errors in the software. Coding errors are relatively cheap to fix as compared to design errors and requirement errors. The requirement errors are more expensive, as redesigning of the entire system is to fix them. Adaptive Maintenance The design software can be maintained by adaptive maintenance if case there is a need to change the system environment such as a different hardware platform or for using it with different operating system.

Predictive Maintenance The design system can be maintained by predictive maintenance if there is need to implement new functional requirements. These are generated due to the changing requirements of the software customers as their organization or business changes. Maintenance of the system follows the following steps

System Documentation
System documentation is a process that emphasizes on documentation the requirement, design, plan, code implementation and testing of the system as whole. In a product life cycle, there will be a number of documents like requirements specification design, documents, user manuals, release documents etc. that will be generated. The types of documentation that are covered under system documentation also include training material, user manuals, operations manual, and release document. The documentation will be reviewed and approved by concerned users of the documentation. The purpose of the system documentation process is to develop and maintain the documentation that will be used to install and operate the product.

45

This process also ensures that the documentation developed is synchronized with latest product release. Our product document typically consists of the following: Deliverable (file name size etc.): It includes the code after making changes in the original code. Test Summary Report: It includes the result generated by executing the test cases designed by us and the test cases given to us by the customer and transporter. List of all the corresponding changes made in the existing code and reason why the changes are necessary. These documents not only ensures that the system is well designed and is fully complaint with the needs of the user but also helps in further maintenance programmers of the software system. A well documented system helps the maintenance of the software by providing the maintenance programmers and insight.

SCREEN-SHOTS OF THE PROJECT

46

MAIN MENU SCREEN

47

ADMINISTRATION

48

49

Groups

50

Accounts

51

Products

52

Company

53

Sales Setup

54

Purchase Setup

55

Series
56

TRANSACTIONS
57

58

Sales

59

Purchase

60

Voucher Entry

61

Opening Stock

62

Item Search (Opening Stock)

63

Stock Adjustment

64

Creating Batch (Stock Adjustment)

65

66

Sales Return

67

REPORTS

68

Sales Summary Report

69

Purchase Summary Report

70

Accounts (Reports)

71

Day Book (Accounts Report)

72

Ledger (Accounts Report)

73

BIBLIOGRAPHY

Database Management System System analysis and Design SQL Server ASP.Net C# WEBSITES www.google.com

By Vipin C. Desai By Elias M. Awad By Microsoft Press By Wrox Publications By Balagurusamy

74