Medical Store management system

April 1, 2019 | Author: Mukesh Kumar Jasrotia | Category: Html, Cascading Style Sheets, Html Element, Feasibility Study, Hyperlink
Share Embed Donate


Short Description

Srs of medical store management system ....all about us...

Description

Medical Store Management System

A X-Window Lab Project Submitted   In partial fulfillment  For the award of the Degree

of  Bachelor of Technology  In Department of Computer of Computer Science & Engineering & Engineering (With specialization in software engineering)

Supervisor

Submitted By

Ms. Tanuja Rajput

Mukesh Kumar

Assoc. Professor

Enroll. No. –  CP10101408698  CP10101408698

Department of Computer of Computer Science & Science & Engineering Suresh Gyan Vihar University

Mahal, Jagatpura, Jaipur  1

CERTIFICATE

This is to certify that Project Report entitled Medical store(Online medical store management system) which is submitted by Mr. Mukesh Kumar in partial fulfillment fulfillment of the requirement for the award of B. Tech. degree in department of Computer science and Engineering is a record of the candidate(s) own work carried out by him / them under my/our supervision. The matter embodied in this thesis is original and has not been submitted for the award of any other degree.

Signature Name of Supervisor –  Ms. Tanuja Rajput Designation Date

2

DECLARATION

 I/We hereby declare that this submission is my/our own work and that, to the bes t of my/our knowledge and belief, it contains no material previously published or written by another person nor material which to a substantial extent has been accepted for the award of any other degree or diploma of the university or other institute of higher learning, except where due acknowledgment has been made in the text.

Signature  Name :- Mukesh Kumar  Enrolment No. CP10101408698 Date

3

ACKNOWLEDGEMENT

It is great pleasure to acknowledge the support of many people who have contribute to the successful completion of this project. This project would never have seen the light of the day without the help and guidance that I have received, I am profoundly grateful for the support, cooperation and valuable guidance extended by Ms. Tanuja Rajput . Also I Would like to sincere gratitude to Ms. Tanuja Rajput , Assistant Professor of Suresh Gyan Vihar University for his valuable advice and kind of encouragement as internal guide during the whole process from time to time. She always been a source of inspiration? Without their encouragement and help this project would not have materialized Last but not the least; we would like to express our sincere thanks to our Family member and our friends for their constant encouragement.

Signature  Name –  Mukesh  Mukesh Kumar  Enrolment No. CP10101408698 Date

4

Abstract Medical Shop Management System is an website project developed for medical shops. This system is a field concerned with purchasing pu rchasing and selling medicines, maintaining their inventory, generating sales invoices and generating reminders of expiry date about medicines. It requires more time and effort when all procedures are performed manually. Thus, in order to reduce time consumption and human effort the Medical Shop Management System application can be applied in medicals where manual procedure exists. The purpose of this  project is to reduce time consumption and human effort. This application provides user friendly interface as well.

5

INTRODUCTION

1.2 PROJECT DESCRIPTION

Pharmiz the complete medical shop management manage ment software is so designed as to ease the work load of medical shop professionals. The main feature includes invoicing, inventory and stock control, accounting, client and vendor management This software helps you to track all the profits, loss, profitable clients and  products of medical shop moreover it’s a medical shop accounting software. Flexible and adaptive software suited to medical shops or stores or pharmacies of any size. 1.3 PROJECT PROPOSAL

A transfer is a lateral move move to a position in the same classified pay range (classified (classified position) or to a position with comparable duties and responsibilities responsibilities (non-classified (non-classified positions). positions). Eligibility:All non-faculty employees are eligible for transfer after being employed in their present  position for atleast three months. months. In addition, addition, an employee must must have have been performing in a satisfactory satisfactory manner in his/her current job. Exceptions to the three month employment requirement may be authorized by the President on a case-by-case basis. Procedures:➢ ➢ ➢ ➢

Employees are considered as candidates for transfer in the following order or priority: Eligible employees in same department as the job opening Eligible employees in other departments who have requested a transfer Eligible employees being considered for lay-off due to a reduction in force

Employees desiring a transfer will submit a written request for transfer to his/her department head. The employee should identify the specific vacancy in which they are interested. The department head will forward the request to the Department of Human Resources for recommended action. The Department of Human Resources will determine whether the desired job or a suitable job opening exists. If If a suitable suitable job is available, the Department of Human Resources will will arrange for the employee's application to be reviewed reviewed by the department department in which opening opening exists. Employees will be allowed time time off with pay for job interviews related to transfers. transfers. The decision to effect the transfer will be made by the head of the department in which the job opening occurs. An employee who is transferred to a comparable job (lateral transfer) will continue to receive his/her existing rate of pay. 6



A person from any department should be able to



login to the system through the first page of the application using the guest login

Enter the details of the required required in the form available. This form form also captures the details like, name , contact no., and designation of the person. He/She can opt to transfer his employee for any job or if his/her request is very specific then he/she can submit his/her request. As soon as a transfer request /withdrawal /withdrawal /cancellation is made by the person, an automatic email should be sent to the employee transfer coordinator giving details about the employer .

Silent Features ➢ Menu driven, Key board and mouse navigation ➢ Paperless practice ➢ Improve efficiency, productivity ➢ Cost effective solutions ➢ Graphical User Interface with Context Sensitive Help ➢  No special training needed for using the system ➢ Anyone who don’t have accounting knowledge can use without any difficulty General Features ➢ ➢ ➢ ➢ ➢ ➢ ➢ ➢

Automatic importing of drug list Inbuilt account group and account ledgers Option for setting default company Keep address book / telephone directory for easy access Maintain customer relationship Incorporates Calculator with system Option for sending mail from Pharmiz itself Provides multi user environment

1.4 Module Description :

The campaigner contains the following modules:

7

Admin:  This Module provides functionality of managing of categories, sub-categories, and  products. This is first and most important module of metastock. This module has overall controlling of projects without it cannot be man age this software. Reviewer: This module provides functionality of managing to give the review of the product so that customer can understand more about the products. This module also can reply on the queries of product which get from customers side. Moderator:  This module provides functionality of managing user review, when Customer  purchase the product and give personal reviews on on that product, review of customer customer should not be globalised directly, At this place moderator will receive that reviews and after reading it will verify, if moderator verify that review, that review should be publish globally but if moderator rejected that review then should not be published globally. Vendor: This module is used by vendor, Vendors are that party who had product can add on this site so that customer can views. According to the product more than one vendor can be. All the  product related information will be uploaded by vendors. Customer: This module is used by customer, Customers are end user who will view the product and send enquiry on that product also can ask any personal queries. After viewing product can choose products.

8

CHAPTER 2 TECHNOLOGY OVERVIEW

2.1 HARDWARE REQUIREMENTS:

DEVELOPER’S: PROCESSOR 

:

2.0 GHZ AND ABOVE.



MEMORY

:

2 GB RAM.



HARD DISK 

:

80 GB HDD.



PROCESSOR 

:

2.0 GHZ



MEMORY

:

2 GB RAM



HARD DISK 

:

80 GB HDD

 NETWORK 

:

ACTIVE I NTERNET CONNECTION



USER’S:



AND ABOVE

2.2 Technology used: •

FRONT E ND

:



BACK E ND

:

HTML,CSS HTML,CSS

2.3 SOFTWARE REQUIREMENTS:

USER’S:

I NTERNET BROWSER (CROSS PLATFORM)

9

CHAPTER 3 FEASIBILITY STUDY 3.1 Feasibility Study

Feasibility studies are crucial during the early development of any project and form a vital com ponent in the development process. A feasibility study is a management-oriented management -oriented activity. It is a test of system proposal according to its workability, impact on the organization, ability to meet user needs and effective use of resources. A feasibility study is conducted to select the best system that meets performance requirement. This entails an identification description, an evaluation of candidate system and the selection of best system for the job. The system required performance is defined by a statement of constraints, the identification of specific system objective and a description of outputs. The document provide the feasibility of the project that is being designed and lists various areas that were considered very carefully during the feasibility study of this project such as Technical, Economic and Operational feasibilities.

The key considerations in feasibility analysis are as follows:

3.1.1 Economic Feasibility 3.1.2 Technical Feasibility 3.1.3 Operational Feasibility

It looks at the financial aspects of the project. It determines whether the management has enough resources and budget to invest in the proposed system and the estimated time for the recovery of cost incurred. It also determines whether it is worthwhile to invest the money in the  proposed project. Economic feasibility is determines by the means of o f cost c ost benefit analysis. The  proposed system is economically feasible because the cost involved in purchasing the hardware and the software are within approach. The personal cost like salaries of employees hired are also c 10

It is a measure of the practically of a specific technical solution and the availability of technical resources and expertise.

The system will be used if it is developed well then tackle the hindrances in its operation.





It will help in the time saving and fast proc essing and dispersal of user request and applications.  New product will provide all the benefits of present system with with better performance.



Improved information, better management and collection of the relevant data which is very helpful to users of the project.



Multi User support facilitate in smooth running of software.



User will have control over own information. Important information such as mail add ress cannot be publicly viewed.



Faster and systematic processing of user application approval, view ac ceptance and rejection facility. Hence the project will be operationally feasible also.



3.2 Behavioral Feasibility:

In this type of feasibility check, we come to know if the newly developed system will be taken and accepted by the working force i.e. the people who will use it. As the application has graphical user interface with suitable screen which help them a lot in navigation through the pages without concern of the backend processes. So the users must not have any problem in finding or searching the content from the site. Hence results in behaviorally feasible project 11

CHAPTER 4 LANGUAGE AND TOOLS TO BE USED 4.1 History

 markup language for creating web creating web Hypertext Markup Language (HTML) is the standard  markup  pages and  web  web applications. With applications. With Cascading  Cascading Style Sheets (CSS) and  JavaScript  JavaScript it forms a triad [3] of cornerstone technologies for the World the World Wide Web. Web.  Web browsers receive HTML documents from a web a web server or from local storage and render them into multimedia web pages. HTML describes the structure of a web page semantically page semantically and originally included cues for the appearance of the document. HTML elements are the building blocks of HTML pages. pag es. With HTML constructs, images constructs, images and other objects, such as interactive as interactive forms, may be embedded into the rendered page. It provides a means to create structured create structured documents by documents by denoting structural semantics structural semantics for text such as headings,  paragraphs, lists, links, lists, links, quotes  quotes and other items. HTML elements are delineated by tags, written using angle using angle brackets. Tags brackets. Tags such as and introduce content into the page directly. Others such as ... surround and provide information about document text and may include other tags as sub-elements. Browsers do not display the HTML tags, but use them to interpret the content of the page.

At its heart, HTML heart, HTML is a fairly simple language made up of elements, which can be applied to  pieces of text to give them different meaning in a document (is it a paragraph? is it a bulleted list? is it part of a table?), structure a document in to logical sections (does it have a header? hea der? three columns of content? a navigation menu?) and embed content such as images and videos into a  page. This module will introduce the first two of these, and introduce fundamental concepts and syntax you need to know to understand HTML. Getting started with HTML

Covers the absolute basics of HTML, to get you started —  we  we define elements, attributes, and all the other important terms you may have heard, and where they fit in to the language. We also show how an HTML element is structured, how a typical HTML page is structured, and explain other important basic language features. Along the way, we'll have a play with some HTML, to get you interested! What’s  in

the head? Metadata in HTML The head of an HTML document is the part that is not displayed in the web browser when the page is loaded. It contains information such as the page , page , links  links to CSS( to CSS(if if you want to style your HTML content co ntent with CSS), links to custom favicons, and metadata (which is data about the HTML, such as who wrote it, and important keywords key words that describe the document.) 12

HTML text fundamentals

One of HTML's main jobs is to give text meaning (also known as semantics), so that the  browser knows how to display it correctly. This article looks at how to use HTML HTML to  break a block of text up into a structure of headings and paragraphs, add emphasis/importance to words, create lists, and more. Creating hyperlinks

Hyperlinks are really important —  they  they are what makes the web a web. This article shows the syntax required to make a link, and discusses link best practices. Advanced text formatting There are many other elements in HTML for formatting text, which we didn't get to in the HTML the HTML text fundamentals article. The elements in here are less well-known, but still useful to know about. In here you'll learn about marking up quotations, quo tations, description lists, computer code and other related text, subscript and superscript, contact information, and more. Document and website structure

As well as defining individual parts of your page (such as "a paragraph" or "an image"), HTML is also used to define areas of your you r website (such as "the header", "the navigation menu", "the main content column".) This article looks into how to plan a basic website structure, and write the HTML to represent this structure. Debugging HTML Writing HTML is fine, but what if something is going wrong, and you can't work out where the error in the code is? This article will introduce you to some tools that can help you. 4.2 Css

a style sheet language used for describing the presentation the presentation of a Cascading Style Sheets (CSS) is a style [1] document written in a markup a markup language. language. Although most often used to set the visual style of  web  web pages and user interfaces written in HTML in HTML and  XHTML, the  XHTML, the language can be applied to any XML any XML document, including plain including plain XML, SVG XML, SVG and  XUL, and  XUL, and is applicable to rendering in speech, in speech, or  or on other media. Along with HTML and  JavaScript, CSS  JavaScript, CSS is a cornerstone technology used by most websites to create c reate visually engaging webpages, user interfaces for  web  web [2] applications, and applications, and user interfaces for many mobile applications a pplications.. CSS is designed primarily to enable the separation of presentation and content, including aspects such as the layout, the layout, colors,  colors, and   and  fonts.  fonts.[3] This separation can improve content accessibility, content accessibility, provide  provide more flexibility and control in the specification of presentation characteristics, enable multiple 13

HTML pages to share formatting by specifying the relevant CSS in a separate .css file, and reduce complexity and repetition in the structural content. Separation of formatting and content makes it po ssible to present the same markup page in different styles for different rendering methods, such as on-screen, in p rint, by voice (via speech based browser or  screen  screen reader), reader), and on Braille-basedt on Braille-basedtactile actile devices. It can also display the web  page differently depending on the screen size or viewing device. Readers can also specify a different style sheet, such as a CSS file stored on their own computer, to override the one the author specified. Changes to the graphic the graphic design of a document (or hundreds of documents) can be applied quickly and easily, by editing a few lines in the CSS file they use, rather than by changing markup in the documents. The CSS specification describes a priority scheme to d etermine which style rules apply if more than one rule matches against a particular element. In this so-called cascade, priorities (or weights) are calculated and assigned to rules, so that the results are predictable.

14

CHAPTER 5 SDLC 5.1 Model Used

There are various software paradigms, but we used Waterfall model (the linear sequential model), which states that the phases are organized in a linear order. The Waterfall model suggests a systematic, sequential approach to s/w development that begins at the system level and progresses through analysis, design, coding, testing, and maintenance and support

Requirement Document & Project Plan

 An aly si s Detailed Design

Design Programs

Coding Test Plan Reports & Manuals

Testing Installation Reports

Implementation

Maintenance

15

5.2 SYSTEM ANALYSIS

System analysis is an in  – depth depth of the end user information needs that produces functional requirements that are used as the basic for the design of the new system. System analysis traditionally involves detailed study of:➢

The information needs of the organization and end users like you.



The activities, resources, and outputs of the present system in a familiar manner.



The system capability requires to meet your information Need, and those of others staff member of the organization.

16

CHAPTER 6 LIFE CYCLE OF PROJECT

6.1 E-R DIAGRAM

In this model objects of similar structures are c ollected into an entity set. The relationship between entity sets is represented by a named E-R relationship and is 1:1(one to one), 1: N (one to many) or M: N (many to many) mapping from one entity set to another. The database structures, employing the E-R model is usually shown pictorially using entity relationship (E-R) diagrams. The E-R diagrams are useful in representing the relationship among entities. The following terms used in E-R Diagram:Entity:-An entity is a person, place, thing, event or concept about which information is recorded. Attribute:-Attribute gives the characteristic of the entity. In other words, every entity has some

 basic attribute that characterize it. Entity Type:-An entity type is defined as a collection of entities that have the same attributes. Relationships: One to One (1:1) One to many (1: N) Many to Many (N: N) Many to One (N: 1)

17

ER-Diagram :

18

6.2 Data Flow Diagram

Data Flow Diagram (DFD) is a graphical graphica l technique that depicts information flow and transfers that are applied as data moves from input to output. The DFD is also known as Data flow graph or a  bubble chart. The data flow diagram may may be used to represent a system or software at any level of

abstraction. In fact, DFD’s may be partitioned into levels that represent increasing information and functional detail. The basic notation to create a DFD is: ➢

A rectangle is used to represent an external entity, that is, a system element (e.g. hardware,  person and another program) or another



System that produces information for transformation by the software or receives information  produced by the software.



A circle represents a process or transform that is applied to data (or control) and changes it in some way.



An arrow represents one or more data items.



An open rectangle represents data store – stored stored information that is used by the software, i.e. temporary repository of data.

The simplicity of DFD notation is one reason why structured analysis techniques are most widely used .The data flow diagram for the current system is as given in the figure on the next page.

19

6.2.1 FlowChart

20

6.2.2 CONTEXT DIAGRAM(LEVEL DIAGRAM(LEVEL 0)

6.2.3 DATA FLOW DIAGRAM(LE DIAGRAM(LEVEL VEL 1)

21

6.2.4 DATA FLOW DIAGRAM(LEVEL DIAGRAM(LEVEL 2)

22

CHAPTER 7 7.1 Screen Shots 7.1.1 Home Page

23

7.1.2 Login Page

7.1.3 Signup Page

24

7.1.4 Store Page

7.1.5 Medicene Store page

25

7.1.6 Add Address Page

7.1.7 Payment Page

26

7.1.8 Order Confirmed Page

7.1.9 Treat ment form Page

27

7.1.10 Feedback Form Page

28

CHAPTER 8 TESTING AND MAINTENANCE

TESTING

Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design and coding. The purpose of product testing is to verify and validate the various work product viz. units, integrated unit, final product to ensure that they meet their respective requirements. 8.1 Testing Objectives: •

Testing is a process of executing a program with the intent of finding an error.



A good test case is one that has a high probability of finding an as-yet undiscovered error.



A successful test is one that uncovers an as-yet undiscovered error.



Live data is the actual data to be used in the proposed system.



Test data is previously designed sample input to achieve predictable results.

This process has two parts: 1) PLANNING: This involves writing and reviewing unit, integration, functional, validation and

acceptance test plans. 2) EXECUTION: This involves executing these plans, measuring, collecting data and verifying

if it meets the quality criteria. Data collected is used to make appropriate changes in the plans related to development and testing. The quality of a product or item can be achieved by ensuring that the product meets the requirements by planning and conducting the following tests at various stages. 8.2 Testing Techniques:

The techniques followed throughout the testing of the system are as under 1) BLACK -BOX TESTING Here we demonstrated :•

All the software functions are operational 29



Input is properly accepted, Output is correctly produced ,



The integrity of external information (e.g.: - a d atabase) is maintained.

2) WHITE-BOX TESTING

It is predicated on close examination of procedural details. Providing test cases that exercise specific sets of conditions and / or loops tests logical paths through the software. The “state of the

 program” may be examined at various points to determine if the expected of asserted status corresponding to the actual status. Control Structure Testing ➢

Boolean operator error



Boolean variable error



Boolean parenthesis error



Relational operator error



Arithmetic expression error

1) Loop Testing: Loops are the corner stone for the vast majority of all algorithms implemented in software. Loop testing is a white-box testing technique that focuses exclusively on the validity of loop constructs. Four different classes of loops: ➢

Nested Loops



Concatenated Loops



Unstructured Loops

2) Dataflow Testing: The dataflow testing method selects test paths of a program according to the location of definitions and uses of variables in the program.

30

8.3 Testing Strategies:

A strategy for software testing integrates software test case design methods into a well-planned series of steps that result in the successful construction of software. A software testing strategy should be flexible enough to promote a customized testing approach. ➢

UNIT TESTING: Unit testing begins at the vertex of the spiral and concentrates on each unit of

the software as implemented in the source code. The individual modules were tested during the development. Unit test cases and their results are submitted periodically during the development stage. ➢

INTEGRATION TESTING: Integration testing focuses on design and c onstruction of the software

architecture. After two or more product units are constructed, the development team, to test the interface between the integrated units, conducts integration testing. ➢

FUNCTIONAL TESTING: Functions are invariably related to one another & interact in the total

system. Each function is tested to see whether it conforms to related functions in the system. Each portion of the system is tested against the entire module both test & live data are used  before the entire system test was conducted. ➢

ACCEPTANCE TESTS: During this test we determine how users will use the system when pro-

cessing data or preparing reports. ➢

VALIDATION TESTING: This is where requirements established as part of software require-

ments analysis is validated against the software that has been constructed. ➢

SYSTEM TESTING: It is here the software and other system elements are tested as a whole.

Proper procedures are forced in the software for recovery as the software may fail in a variety of ways. Proper security attempts to verify that protection mechanisms built into a system will, in fact protect it from improper penetration. APPROACH FOR TESTING:

For unit testing, the modules are tested for correctness of logic applied and should detect errors in coding. Valid and invalid data should be created and the programs should be made to process this data to catch errors. For Example, in the Distance Learning System,

31



In the registration module while entering the data for user, one cannot go for password less than eight characters., so one should ensure e nsure that it should result in an error message.



All dates that are entered should be validated. No program should accept

For system testing, when unit tests are satisfactorily concluded, the system as a complete entity must be tested. At this stage, end-users and operators become actively involved in testing. While testing one should also test to find discrepancies between the system and its original objective, current specification and systems documentation. SOME COMMON TESTS ARE: ➢

Handling values in Primary Key fields.



Handling empty records.



Max length allowed in controls should match the database structure.



Handling special characters like ‘, #, %, $, {,}, [,], etc.



Handling of errors in modules as specified in the project specifications.



Use global error handling functions if there is any in the project.



Termination of activities while error should be monitored accordingly.



Keeping control of the application to self while unexpected errors



Raise errors and handle it as and when necessary.



Showing meaningful error messages as and when required.



Updating error log file with specific information on errors.



Use proper captions for error message dialog boxes.



Format of date should be as specified in the project specifications.



Showing default values in all sub forms as and when required.



Query handling within form.



Enabling and disabling of controls as and when required.



Showing complete data as and when required.

8.5 MAINTENANCE DESCRIPTION

This is an ongoing exercise after the system has been implemented. The real life would be never static. It is necessary to eliminate errors in the working system during its working life and to tune the system to any variations in its working environment. System planners must always plan for 32

resource availability to carry out these maintenance functions. Its requirements and objectives keep changing. So shall be the system, which has been designed primarily to meet those objectives. Thus the system analyst has to keep on carrying out changes and modification into the system, a stage called normally as system maintenance. CORRECTIVE MAINTENANCE

This pertains to the changes the software to correct defects. ADAPTIVE MAINTENANCE

Overtime, the original environment for which the web application was developed is likely to change. This maintenance results in modification to the software to accommodate changes to its external environment.

33

CHAPTER 9 LIMITATION AND CONCLUSIONS

9.1 LIMITATION ➢

 No direct interaction between user and administrator.



 No option to select other product which is not no t add ad d this site. Only added product Can be choose

➢ ➢

Cost of product can be vary v ary from customer to customer, no standard and fixed cost.  Need to internet connection to access these services.

FUTURE ASPECTS:

As software is used, the customer/user will recognize additional functions that will provide benefit. Perfective maintenance extends the software beyond its original functional requirements. It will  play very important role in construction site. SCOPE OF THE PROJECT

Since this system has been developed using object oriented programming, there are every chances of reusability of the codes in other environments and even different platforms. Also its  present features can be enhanced by some simple modifications in the code so as to use it in the changing scenario. Apart from reusability, the other features are —  ➢

Extensibility



Robustness



Understandability



Maintainability



Cost Effectivene

34

9.2 CONCLUSION

System was developed and fasted in steps. Once the design was finalized, the format of the output reports was set one by one after approval from the user department. System was first tested on the test data and then real data. Minor programming errors were identified and rectified. After rectifying the system was implemented successfully and accuracy was found.

After testing, our system “Learning Management System” we find that this system provide a lot of help to the user, and an d it is very beneficial for online mailing. After implementation of this we conclude that this is real client/server environment that are reachable all over the world. This system is fast as compared to other computerized system 9.3 Future SCOPE ➢

The future scope of this project would be an addition feature of Direct interaction with Product Company and all the CONCESSION and FREE extra product will be direct get to the Customers where in the real time conversation would be enabled.



It could also include a module through which outside users can access to some specific levels.



Add Video conferencing through directly customer support and product reviewers.



Enabling/Disabling Direct communication through Video Call.

35

Bibliography Websites: •

www.w3schools.com



www.csstutorial.net



www.yourhtmlsource.com



www.tutorialspoint.com



www.cssbasics.com

Books:  Au th or 

Mary Gillen Craig Grannell

Title HTML, Intermediate Skills & Drills

The Essential Guide to CSS and HTML Web Design

Eric Ray

HTML 4 for Dummies Quick Reference (Available Feb 1998)

Jennifer Niederst Robbins

Learning Web Designs

----------------------------------------------------THANKS---------------------------------------------------36

View more...

Comments

Copyright ©2017 KUPDF Inc.
SUPPORT KUPDF