Pharmacy Management System 3o1q3q

CHAPTER - 1 1. INTRODUCTION 1.1 DOTNET The .Net frame work is a comprehensive platform that can be a little difficult to describe. It has been described as a Development Platform an execution environment and the operating system among other things. In fact in some aside from embracing the web, Microsoft .NET acknowledges and responds The framework's Base Class Library provides a large range of features including interface, data

access, database

connectivity, cryptography, web

application development,

numeric algorithms, and network communications. The class library is used by programmers, who combine it with their own code to produce applications. Programs written for the .NET Framework execute in a software environment that manages the program's runtime requirements. Also part of the .NET Framework, this runtime environment is known as the Common Language Runtime (CLR). The CLR provides the appearance of an application virtual machine so that programmers need not consider the capabilities of the specific U that will execute the program. The CLR also provides other important services such as security, memory management, and exception handling. The class library and the CLR together constitute the .NET Framework.

1

C# DOT NET

C# is a multi-paradigm programming language encoming imperative, declarative, functional,

generic,

object-oriented (class-based),

and component-oriented programming

disciplines. It was developed by Microsoft within the .NET initiative and later approved as a standard by Ecma (ECMA-334) and ISO (ISO/IEC 23270). C# is one of the programming languages designed for the Common Language Infrastructure. C# is intended to be a simple, modern, general-purpose, object-oriented programming language. Its development team is led by Anders Hejlsberg. The C# language is disarmingly simple, with only about 80 keywords and a dozen built-in data types, but C# is highly expressive when it comes to implementing modern programming concepts. C# includes all the for structured, component-based, object-oriented programming that one expects of a modern language built on the shoulders of C++ and Java. The C# language was developed by a small team led by two distinguished Microsoft engineers, Anders Hejlsberg and Scott Wiltamuth. Hejlsberg is also known for creating Turbo Pascal, a popular language for PC programming, and for leading the team that designed Borland Delphi, one of the first successful integrated development environments for client/server programming. At the heart of any object-oriented language is its for defining and working with classes. Classes define new types, allowing you to extend the language to better model the problem you are trying to solve. In C# everything pertaining to a class declaration is found in the declaration itself. C# class definitions do not require separate header files or Interface Definition Language (IDL) files.

2

1.2 SQL SERVER:

SQL often referred to as Structured Query Language, is a database computer language designed for managing data in relational database management systems (RDBMS), and originally based upon relational algebra. Its scope includes data insert, query, update and delete, schema creation and modification, and data access control. SQL was one of the first languages for Edgar F. Code’s relational model in his influential 1970 paper, "A Relational Model of Data for Large Shared Data Banks" and became the most widely used language for relational databases. The SQL language is sub-divided into several language elements, including: •

Clauses, which are in some cases optional, constituent components of statements and queries.

•

Expressions which

can

produce

either scalar values

or tables consisting

of columns and rows of data. •

Predicates which specify conditions that can be evaluated to SQL three-valued logic (3VL) or Boolean (true/false/unknown) truth values and which are used to limit the effects of statements and queries, or to change program flow.

•

Queries which retrieve data based on specific criteria.

•

Statements which may have a persistent effect on schemas and data, or which may control transactions, program flow, connections, sessions, or diagnostics.

3

•

SQL statements also include the semicolon (";") statement terminator. Though not required on every platform, it is defined as a standard part of the SQL grammar.

1.3 CASE TOOLS 1.3.1 Use Case Diagram A use case corresponds to a sequence of transactions, in which each transaction is invoked from outside the system (actors) and engages internal objects to interact with one another and will the system’s surroundings. The description of a use case defines what happens in the system when the use case is performed. In essence, the use-case model defines the outside (actors) and Inside (use case) of the system’s behavior. Use cases represent specific flows of events in the system. The use cases are initiated by actors and describe the flow of events that these actors set off. An actor is anything that interacts with a use case: It could be a human , external hardware, or another system. An actor represents a category of rather than physical . Several physical s can play the same role. For example, in of a Member actor, many people can be of a library, which can be of a library, which can be represented by one actor called Member. A use-case diagram is a graph of actors, a set of use cases enclosed by a system boundary, communication associations between the actors and the use cases, and generalization among the use-cases. 1.3.2Sequence Diagram:

4

Sequence diagram are easy and intuitive way of describing the behavior of a system by viewing the interaction between the system and its environment. A sequence diagram shows an interaction arranged in a time sequence. It shows the objects participating in the interaction by their lifelines and the messages they exchange, arranged in a time sequence. A sequence has two dimensions: the vertical dimension represents time, the horizontal represents different objects

1.3.3 Collaboration:

Collaboration is a recursive process where two or more people or organizations work together in an intersection of common goals — for example, an intellectual endeavor that is creative in nature by sharing knowledge, learning and building consensus. Most collaboration requires leadership, although the form of leadership can be social within a decentralized and egalitarian group. In particular, teams that work collaboratively can obtain greater resources, recognition and reward when facing competition for finite resources. Collaboration is also present in opposing goals exhibiting the notion of adversarial collaboration, though this is not a common case for using the word. Structured methods of collaboration encourage introspection of behavior and communication. These methods specifically aim to increase the success of teams as they engage in collaborative problem solving. Forms, rubrics, charts and graphs are useful in these situations to objectively document personal traits with the goal of improving performance in current and future projects.

1.3.4 Class:

5

A class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that describes the structure of a system by showing the system's classes, their attributes, and the relationships between the classes. The class diagram is the main building block in object oriented modeling. They are being used both for general conceptual modeling of the systematic of the application, and for detailed modeling translating the models into programming code. The classes in a class diagram represent both the main objects and or interactions in the application and the objects to be programmed. In the class diagram these classes are represented with boxes which contain three parts: A class with three sections. •

The upper part holds the name of the class

•

The middle part contains the attributes of the class

•

The bottom part gives the methods or operations the class can take or undertake

In the system design of a system, a number of classes are identified and grouped together in a class diagram which helps to determine the statically relations between those objects. With detailed modeling, the classes of the conceptual design are often split in a number of subclasses. In order to further describe the behavior of systems, these class diagrams can be complemented by state diagram or UML state machine. Also instead of class diagrams Object role modeling can be used if you just want to model the classes and their relationships.

1.3.5 Activity: Activity diagrams are graphical representations of workflows of stepwise activities and actions with for choice, iteration and concurrency. In the Unified Modeling Language,

6

activity diagrams can be used to describe the business and operational step-by-step workflows of components in a system. An activity diagram shows the overall flow of control. Activity diagrams are constructed from a limited repertoire of shapes, connected with arrows. The most important shape types:

•

Rounded rectangles represent activities.

•

Diamonds represent decisions.

•

Bars represent the start (split) or end () of concurrent activities.

•

A black circle represents the start (initial state) of the workflow.

•

An encircled black circle represents the end (final state).

•

Arrows run from the start towards the end and represent the order in which activities happen.

Hence they can be regarded as a form of flowchart. Typical flowchart techniques lack constructs for expressing concurrency. However, the and split symbols in activity diagrams only resolve this for simple cases; the meaning of the model is not clear when they are arbitrarily combined with decisions or loops.

7

CHAPTER – 2 2. SOFTWARE AND HARDWARE REQUIREMENT 2.1 SOFTWARE REQUIREMENT

•

Operating System

: Windows XP

•

Front End

: C#.NET

•

Back End

: Sql Server

•

Word Processor

: MS-Word

2.2 HARDWARE REQUIREMENT •

Processor

: Intel® dual-Core(TM)

•

RAM

: 1 GB

•

Hard Disc

: 120 GB

•

Key Board

: Standard 101/102 keys

•

Mouse

: Microsoft Mouse or compatible pointing device

8

CHAPTER - 3 3. SYSTEM DESIGN 3.1 DATA FLOW DIAGRAM



Exit

Enter into Website

Homepage

Registratio n

Stock details

Bill Transaction 9

Purchasing

Report

Stop

3.2 CASE TOOLS DIAGRAM

3.2.1 Use case Diagram

10

3.2.2 Sequence Diagram

11



new stock detail

purchase detail

bill trancation

stock return

to be enter the new reg

to maintain the stock detail use to be purchase the product

re enter

provided the bill

stock some time return

other information

3.2.3 Collaboration Diagram

12

about

5: re enter

3: use

bill trancation

stock detail



2: to maintain the stock detail 1: to be enter the new reg

6: provided the bill

4: to be purchase the product

purchase detail

7: stock some time return

stock return

8: other information new

3.2.4 Class Diagram

13

about

14

3.2.5Activity Diagram

15

enter the new

false

stock detail

purchase detail

bill trancation

stock return

bill bacup

CHAPTER - 4

16

4. MODULE DISCRIPTION Modules: 4.1 4.2 Registration 4.3 Stock detail 4.4 Bill transaction 4.5 Purchasing 4.1 The module is used to grant access to other modules only for the authorized people on giving valid name and . 4.2 Registration module accepts the name and for existing and validates it. For new create a . This module will allow the to buy and enjoy the accessibilities if they have an (-Id & ) .only can access have permission to change the . When s have no earlier they can create an through . 4.3 Stock details In the stock detail module the availability of stock is checked by entering the code. If the stock is available it shows the stock detail otherwise it does not show the details. If stock is not available it can be purchased. Stock detail displays icode, iname, iprice, quantity, here the availability of stock, quantity, prices are checked.

17

4.4 Bill detail In this module the bill detail are shown. Whenever the bill no is entered it shows the product to de bought by the customer. It is very useful for resales of product and also to check the bill details of the certain customer. 4.5 Purchasing This module will give the information that s to buy a fresh product or to sell a second hand product. Also it shows the icode, inumber, unit price, quanity, and amount. It will also give bill detail in it.

CHAPTER - 5 5. IMPLEMENTATION 18

5.1 Database Tables Stock detail.cs

Bill truncation.cs

19

Purchase detail.cs

5.2 TESTING

20

Testing is the name given to the checking and analysis process that ensure that the software conforms to its specification. In this project few testing techniques were applied at different stages of the project so as to test the performance of the project. The testing activity can be carried at the implementation to that the project behaves as intended by the designers. During these activities the software reliability was checked to a large extent. The successful testing process must confirm that the system is free of defects and is ready to use. 5.2.1 MODULE TESTING It is a process of testing the system module, what are all the inputs given and what all are outputs produced and whether they are required. Here after completing each module a testing was performed.

5.2.2 SYSTEM TESTING System testing is a series of different tests whose primary purpose is to exercise the computer-based system. It also tests to find discrepancies between the system and its original objective, current specification. The requirements of our project were analyzed and a test activity was performed whether the system has the necessary software to run this project. If not then the software is then installed into the system and the project will be implemented on it. 5.2.3 INTEGRATED TESTING This is a very important testing process in any project. This testing mainly focuses on the combination of several parts of the project and making it to work. Here this testing activity was done at the end of the project and based on the results of this testing the output will be determined. 5.2.4 WHITE BOX TESTING

21

White Box Testing focus on the program control structure. Test cases are derived to ensure that all statements in the program have been executed at least once during testing and that all logical conditions have been exercised. Basic Path Testing, a White Box technique, makes use of program graphics to derive a set of linearly independent tests that will ensure coverage. Condition and data flow testing further exercise program logic and loop testing complements other white box techniques by providing a procedure for exercising loops of varying degrees of complexity.

5.2.5 BLACK BOX TESTING Black Box test are designed to validate functional requirements without regard to the interval working of the program. This technique focuses on the information domain of Software, deriving test case coverage. Equivalence partitioning divides input domain into Classes to data that are likely to exercise specific software function.

A classical system testing problem is finger pointing. This occurs when a defect is uncovered and one system element developer blames the other for the problem. In order to avoid this scenario the following measures are adopted. •

Error handling paths are designed that test all information coming from other elements of the system.

•

A series of tests are conducted that stimulate bad data and other potential errors at the software interface.

•

The result of the tests is recorded to use as evidence if finger point does occur.

22

•

Participate in the design of system tests to ensure that the software if adequately tested.

TEST RESULT The listed tests were conducted at various development stages. Throughput was conducted .the errors were debugged. The integration testing will be performed once the system is integrated. The results were and analyzed and alternations were made. The test results proved positive and henceforth the application is feasible and the test is approved.

23

5.3 CODING

Purchase detail. Cs

private void button1_Click(object sender, EventArgs e) { try { //int txtamt1 = Convert.ToInt32(txtqty.Text) * Convert.ToInt32(txtuni.Text);

// txtamt.Text = txtamt1.ToString(); //txtamt.Text =Convert.ToInt32 (txtuni.Text)/100 * Convert.ToInt32(txttax.Text); decimal p, q, z, m, j, a, f; if (txtuni.Text =="") { // MessageBox.Show("Enter the Purchase Price", MessageBoxButtons.OK, MessageBoxIcon.Exclamation); MessageBox.Show("You must Enter a Purchase Price.", "Purchase Entry Error", MessageBoxButtons.OK, MessageBoxIcon.Exclamation); txtuni.Focus (); } p = decimal.Parse(txtuni.Text);

if ((txtsell.Text) == "") a = decimal.Parse(txttaxper.Text) * a; // txttaxamt.Text = System.Convert.ToString(z).ToString();

24

txttaxamt.Text = z.ToString();

int d; string s2 = txttaxamt.Text; d = s2.LastIndexOf("."); // string ssa = s2.Substring(0, d + 2); // txttaxamt.Text = ssa; // MessageBox.Show(d.ToString()); if (d==d ) { string ssa = s2.Substring(0, d + 3); txttaxamt.Text = ssa; } else { txttaxamt.Text = z.ToString(); }

// txttaxamt.Text = FormatException(a, "#,###.##"); // Label8.Text = Format(count, "#,###.##")

int n; string s1 = txtpri.Text; n = s1.LastIndexOf("."); //MessageBox.Show(n.ToString()); 25

if (n == n) { string sss = s1.Substring(0, n + 3); txtpri.Text = sss; }

else { txtpri.Text = m.ToString(); }

// txtpri.Text = sss;

txtmrpp.Text = f.ToString();

int k; string s = txtmrpp.Text; k= s.LastIndexOf("."); // string ss = s.Substring(0, k+ 3); // txtmrpp.Text = ss; if (k == k) Decimal ded; ded = (x) - Decimal.Parse(txtded.Text);

//

txttotamt.Text = x.ToString();

txttotamt.Text = ded.ToString();

26

} catch (Exception ex) { MessageBox.Show("YOU MUST ENTER THE FORMAT 0.00",ex.Message); } }

Stock detail.cs

private void button4_Click(object sender, EventArgs e) { try { decimal p, q, z, m, j, a, f; if ((txtsell.Text) == "") { //MessageBox.Show("Enter the Sell Price"); MessageBox.Show("You must Enter a Sell Price.", "Sell Entry Error", MessageBoxButtons.OK, MessageBoxIcon.Exclamation); txtsell.Focus(); }

j = decimal.Parse(txtsell.Text); q = 100; a = j / q; // MessageBox.Show(z.ToString()); 27

if (txttaxper.Text == "") {

MessageBox.Show("You must Enter a Tax Percentage.", "VAT Entry Error", MessageBoxButtons.OK, MessageBoxIcon.Exclamation); txttaxper.Focus();

} else { // z = decimal.Parse(txttaxper.Text) * z; a = decimal.Parse(txttaxper.Text) * a;

txttaxp.Text = System.Convert.ToString(a).ToString();

int v; string v1 = txttaxp.Text; v = v1.LastIndexOf("."); // string vv = v1.Substring(0, v + 3); // txttaxp.Text = vv; if (v == v) 28

{ string vv = v1.Substring(0, v + 3); txttaxp.Text = vv; }

else { txttaxp.Text = System.Convert.ToString(a).ToString(); }

//

m = p + z;

f = j + a; //

txtpri.Text = m.ToString();

txtmrpp.Text = f.ToString();

int k; string s = txtmrpp.Text; k = s.LastIndexOf("."); // string ss = s.Substring(0, k+ 3); // txtmrpp.Text = ss; if (k == k) { string ss = s.Substring(0, k + 3); 29

txtmrpp.Text = ss; }

else { txtmrpp.Text = f.ToString(); }

} }

catch (Exception ex) { MessageBox.Show("YOU MUST ENTER THE FORMAT 0.00 ", ex.Message); txtbat.Focus(); } }

30

5.4 Screen Shots

.cs

31

Main.cs

32

Stockdetail.cs

33

Bill trancation.cs

34

Purchase detail.cs

35

Stock return.cs

36

CHAPTER - 6 6. CONCLUSION

The project “pharmacy management “was designed successfully and it was executed with successful database connectivity. As the project has cs.net as the front end and SQL as the back end, it has been tested through the system testing of each and every module. The five different modules which has been individually connected with database. The customer can buy products through the pharmacy management, and payment is also carried out through the payment system which is very useful for the customers. We can also check the current status of the stock which is updated for each and every second.

37