Project Document
Project Document
Project Document
1.0
Acknowledgement
As a team member, I cordially thank my project leader Subhamoy Ghosh (PL), Bipru Thakur (DPL), Sujoy Majumder, Nisanta Buxi, Debmalya Ghosh, Kallol for their active participation, complete sincerity, and full dedication and generous co-operation in the making of this project.
We are grateful to Dr. Nirmalya Bhattacharya Mr. Manas kumar Dev Mr. Sutanu Sinha Mr. Debashish Nandi : : : : Principal & project in Charge Faculty, Department of Computer Science Faculty, Department of Computer Science Faculty, Department of Computer Science
Without their humble help and guidance it would have really difficult for us to make this project a good success. It would also be selfish on our part if we do not thank the people who lend their thoughts, ideas and valuable suggestion during the course of our design and development of the project and giving us an ample scope to learn about the usefulness and making of software in the IT field.
(Project Leader)
2.0
This application helps in keeping the track of bulk amount of record for easy access, retrieval and systematic maintenance of a companys selling of products among the client. Our softw are not only time but also re duce the Burdon of maintained the record physic ally. Feasibility Analysis: Feasibility analysis involv es the follow ing From a project team and appoint a project leader Prepare system flow chart Enumerate potential candidate system Describe and identif y characteristic s of candidate system Describe the evaluate performance as well as cost effectiv e of each candidate system Weight system performance and cost data Select the best candidate system Prepare and report project directiv e to management
Three key considerations are involved in the feasibility analysis. They are: 1. 2. 3. Technical Operational Economic
Problem Analysis
Validation
Validated SRS
Client Distribution
3.1
Introdu ction:3.1.1
Project Overview : Todays world is running w ith a great speed and concept of existence is most important everywhere. In this great struggle of keeping existence, the whole society is in the glorious proceeding just getting COMPUTERIZATION as the only tool. Computerization w ith its newer and newer solution, has given the modern of great success and victory. Basically this system is built in that w ay that it is suitable for any enterpris e. Transactions will be too much easier using this system. It keeps all the tracks of the creditors, retailers, distributors as well as of the sales and the damages stocks and stores them in the database permanently. The databases are also flexible. The addition & deletion is also done automatically. So this ystem provides less overhead for the user. Below Level Aw areness: From various surveys it has found that through about the use of computer to control a companys stock is much easier and faster than previous manual controlling the stock system. Indian Scenario: Business society and government cannot afford to ignore the digital society just because its current impact is difficult to measure. Privacy and Security: Privacy and security are other concern; Sales Monitoring & Inventory Control System is trusted mechanism for privacy and security. This mechanis m must provide for security, confidentially, authentic ation and non-repletion. The key to Success: Focusing on exis ting customer, creditor, retailer, dis tributor, which is, luring prospect, cementing a long term business relationship. Visionary leadership Business pragmatism and IT. Product Enabling Sales Monitoring & Inventory Control: A lot of products like Books, Music CDs, computer etc that today are in physical form w ill actually become digital products. And that makes partic ularly exciting because its not only sales a product but maintain the stock also. Theme of the Project: Our project is based on SALES MONITORING & INVENTORY CONTROL strategy manufacturing company who supply / dis patch products to those customers (clients) who pay a minimum demanded advance to the company. To implement this mechanism w e use Oracle as backend for database table. In this project we use number of Java classes to transform data from client side to database and vice-versa. Mechanism of the project is that authoriz ed user can login to main platform to maintain the total process. After login, the logged user w ill have all rights to do w ork w ithin this platform related w ith the project. Managing Quality: All work is a process There are four absolute of quality that guide our effort to operate, manage and improve our work process. All work is a process: Every job w e do is a process, a series of actions that produces a result. These results are products are services that satisfy the need and desires of our customers. To meet our customers expectation, we need first to identif y their requirements. The FOUR absolutes of quality: The four absolute of quality are the principles we used to operate, manage and improve our job process:
They provide the answers to four very important questions about quality: How do we define quality? How we can make quality? What standard do we use for our performance? How can we measure quality?
1.
DEFINITION : What is quality? Almost everyone has an option. Some say quality means Excellence other say Goodness or Beauty. Quality is defined as Conformance to requirements. Any product, service, or process that confirms to its requirements is a quality product, servic e or process. If the requirements are not met, we have nonconformance.
2.
System : One w ay to ensure quality is by apprais al or inspection. As a result of inspection, we make a decision .Either the w ork conforms or it does not. But inspecting just to sort the good form the bad does not help us to improve. To improve quality we need policies and systems that are based the principle of prevention. Prevention involves communicating, planning, proofing, and w orking in a w ay that elements opportunities for non-conformance.
3.
The performance Standard: To make this commitment, w e need a performance standard that everyone can understand. That standard is called ZERO DEFECTS. Conventional performance standards for quality can be summed up by the phrase thats close enough Zero defects are a commitment to meet all requirements for our work the first time and every time. So w e believe that our project should meet most of the requirements of the users and itself a successful standard quality project.
4.
Measurement: Sometimes w e say we are paying more for quality, that quality better or worse, up or down, good or bad, or in line w ith industry standard. The best way to measuring quality is to calc ulate what it costs to do things wrong. This measurement is called price of non-conformance (PONC).
PONC activities include : Reprocessing Expediting Unplanned servic e Computer returns Dow ntime Rew ork Return
So, PONC is the price of waste. In the time of forming our project, we consider and analysis all the above steps and queries for managing quality.
3.1.2
Objective :Sales Management helps to faster transaction between customer & company. In this case business transaction cost became lesser. In this case business ordering cost als o became lesser. In this case client as well as company saves their valuable time. In this case total cost of business of company comes down. Client gets the facility to choose the maximum number of item w ith minimum effort. Through this client is able to purchase or sale anything at anytime if the stock permits!
Major Work Activities:Phases Requirement Analysis Design Coding Testing Documentation Description Deciding features to be included and examination the feasibility Designing system architecture and creating user interface Creating a database, connectivity and coding of modules Testing and debugging of modules and integrating them, final performance testing Submission of final reports, finalizing the project report and hence complete documentation
3.2
Project Delivery Report:Follow ing are the project deliverable: Source code Installation CD SRS Test Plan User Help
3.3
Project Output: The output of employee the Linear Sequential Model is not just final program and the documentation to use it. There are a number of intermediate outputs that must be produce. For the successful completion of the project, the follow ing are required --- Requirement Analysis Document Project Management Plan System Requirement Specification System Design Document Detail Design Document Test Plan & Test Report Final Code
3.4
Project Organization:3.4.1
Processes Model: In order to solv e a problem, a Software engineer must incorporate a development strategy that encompasses the processes, the method and tool, layers and general phases. This strategy is referred to as a processes mod el, or software engineering paradigm. The processes model appropriate for this project Stock Management and Inventory Control System is the Linear Sequential Model
Delivery
Maintenance
STOCK MANAGEMENT AND INVENTORY CONTROL SYSTEM The Phase of the Module can be classified as:
Index 1. Phase Requirement Determination What is done during Phase Determination to be meeting by system being contemplated Draw an understandable plan of what the system w ill provide the output. Determine needs and priority by consensus among the end- user Taking into account available resource such as human, computer, time and money. Find whether specified requirement End Set of requirement and their priorities. Detailed specification of information to be provided Feasibility document specif ication recourses need and availability. Expected cost vs. benefit of the system Functional specif ication budget time schedule. Physical requirements such as storages and processor Hardw are configuration disks space, CPU pow er Logical design of program database and test plan Evolution report w ith suggestion for improvement Evolution report w ith suggestion for improvement Improvement system containing modification and maintenance
2.
3.
Feasibility Analysis
4.
Obtain functional specif ication based on revis ed user requirement and feasibility analysis
5.
Determine Hardw are requirement for the system Logical system of program, design of database, test & implementation plane Writing programs, creating database, testing program and operation plans documenting system. Training user data conversion if needed Find out from user if system meet their needs Changing system, adding or deleting features of satisfying user needs.
6.
System Design
7.
System Implementation
8.
9.
3.4.2
--
1. Subhamoy Ghosh (PL) 2. Bipru Thakur (DPL) 3. Sujoy Majumder 4. Nisanta Buxi 5. Debmalya Ghosh 6. Kallol
3.5
Managerial Process:3.5.1 Management Objective & Priority:The main goals of software management plan are as follows: To ensure smooth execution of project The end product deliver on the time unique effective tool & method The method need the quality requirements of the respective company
3.5.2
Assumption & Dependences : Availability of recommended & hard work on time Each developer is capable of completing dales or assign task on time otherw is e he or she volunteer to take the commitment of the task Potential changes on a degree w ill be indicate configured control are & not be Project review will be taking place Team member are communicating w ith each other 7 each have responsible understanding of ones project element as a hole The exit criteria of a project are depended of finial exemption testing the project closing date is extended may be based on exception report as recusal from product management. If the bugs are identify the expectation testing the project closing date is extended may be based on expectance report as receiv ed from product management. Follow ing are the constancy for the successful combination of the project Time require of competition project Resource needed to completing project
Software requirement: Microsoft Windows XP Microsoft Word Java Oracle Hardw are Requirement: Minimum Pentium IV Processor 1.8 GHz. Minimum 512MB Ram Display Device Input device Printer
3.5.3
Risk M anagement:Risk Category Shortage of Technic al Manpow er 6 Insufficient business knowledge 9 Unclear requirement Risk Maintenance Plane Maintenance Buffer of Extra Resources Define the project Conduct cross Training Session Ensure that multipurpose has assign of Key Project Area Have team building session Rotate job among team member Keep extra recourses as backup Proper documentation of individual work Define performance criteria clearly review by client Define standard up to be followed to meet performance criteria Stimulate or prototype performance of criteria traction Conceder a phase of delivery? Provide training in new technology Externally driven decision forced on the project Outline disadvantages with the supporting fact or data & negotiate w ith the person responsible to forcing the decis ion Increases instruction with the client & ensure a adequate know ledge transfer Organized domain know ledge training Stimulate business trusting & get it approved Negotiate a better schedule Identify a personal task Negotiate client on actual effort Identify areas that can be automated Set proper exception w ith client Plan ached for link load Use experience logic to make some assumption & keep the client information to about signoff Develop prototype to get the requirement to review the client Obtain signoff initial requirement speciation as client Convince the client to the changes the requirement changes Negotiate payment on actual report
Sl No
Risk 5
Unrealistic Schedule
10
3.5.4
Monitoring & Controlling are alw ays & important issue for develop the project. The major particular point on whic h monitoring & controlling on project is based on are as follows Monthly project review meeting headed by the group leader took place to ensure smooth execution of the project Project leader design a project schedule for the team member to follow . Which will continue a follow up an instruction & report? The scientific ally design schedule & instruction sheet for the team member that contain the forget work to be achieved effort put individual team member & others reach team member. The project team leader did the frequent tracking & updating in the project schedule. The project leader used to give the instruction for the proper implement of the schedule changes that where necessary in the schedule made under the guidance of the project leader. The 4th night project status report was sent by the project leader to the concern person in the order to inform the progress of project. Technical Processes: Method: This project is designed using JAVA as the front end tool and ORACLE (Database) as the back end tool Tools: The tools are command Button, labels, combo box, check box, text area etc. Techniques: Different type of data base accessing and code handling and authentication are used.
3.5.5
Effort Estimation:-
Effort estimation report prepaid to track the amount of time consumes to develop the project ( Stock Management and Inventory Control System). The report categorized the no of activity, the starting date & finishing date The Start Date: The Finish Date: Activity RA PMP SRS SDD CODING TESTING RA PMP SRS SDD No of Person 6 6 6 6 6 6 = = = = 29th August, 2009 27th November, 2009 Days 8 10 4 10 40 8
st
Start Date 1 September 2009 11th September 2009 16th September 2009 25t September 2009 2nd November 2009 17th November 2009
th
Finish Date 10 September 2009 15th September 2009 24th September 2009 1st November 2009 16th November 2009 22nd November 2009
Requirement Analysis Project Management Plan System Requirement Specification System Design Document : 2.5 months : 4 hours/day : 290 hours
3.6
Method: This project is designed using JAVA as the front end tool and ORACLE (Database) as the back end tool Tools: The tools are command Button, labels, combo box, check box, text area etc. Techniques: Different type of data base accessing and code handling and authentication are used.
The structured system analysis design is used to develop the system . Tool is used to : Support the prescribed set of steps to go ahead to goal and completion of development of software .
10
3.7
3.8 Reuse: -- The involvement of reusability features for the project itself or any of the project modules or its containing part is not applicable. 3.9 Traceability Matrix:-Configuration Item Identification GC/<APN>/RA/D/C1 GC/<PN>/PMD/D/C1 GC/<PN>/SRS/D/C1 GC/<PN>/SDD/D/C1 Copy Hard Soft File File File File C:/MP C:/MP C:/MP C:/MP
Sl NO 1 2 3 4
Date of Release 01st September 2009 10th September 2009 15th September 2009 25 September 2009
th
3.10
Status Report:Project Status Report: 01 Project Name : - Stock Management and Inventory Control System Period of reporting : - 1st September to 10th September SI NO 1. Activity Name Requirement Analysis Project Management Plan P: Planed Problem Faced: NA Duration P| A 8 8 Starting Date P| A 1st September 2009 11th September 2009 1st September 2009 11th September 2009 Finishing Date P| A 10th September 2009 10th September 2009 Status D
2.
10
10
D: DONE
E: E XECUTING
Project Status Report: 02 Project Name : - Stock Management and Inventory Control System Period of reporting : - 11th September to 24th September SI Duration Starting Date Finishing Date Activity Name NO P| A P| A P| A th th Project 11 11 15th 15th 1. Management 10 10 September September September September Plan 2009 2009 2009 2009 th th th System 16 16 24 24th 2. Requirement 4 4 September September September September Specific ation 2009 2009 2009 2009 25t 25t System Design 3. 10 10 September September Document 2009 2009 P: Planed Problem Faced: NA A: Actual Problem Resolving: NA D: DONE
Status D D
E E: E XECUTING
11
Project Status Report: 03 Project Name : - Stock Management and Inventory Control System Period of reporting : - 25th September to 1st November SI NO 1. 2. Activity Name System Design Document CODING Duration P|A 10 40 10 40 Starting Date P|A 25t 25t September September 2009 2009 2nd 2nd November November 2009 2009 Finishing Date P|A 1st 1st November November 2009 2009 ----Status D E
D: DONE
E: E XECUTING
Project Status Report: 04 Project Name : - Stock Management and Inventory Control System Period of reporting : - 2nd November to 16th November SI NO 1. Activity Name Duration P|A 40 40 Starting Date P| A 2nd November 2009 2nd November 2009 Finishing Date P|A 16th November 2009 16th November 2009 Status
CODING
D: DONE
E: E XECUTING
Project Status Report: 05 Project Name : - Stock Management and Inventory Control System Period of reporting : - 17th November to 22nd November SI NO 1. Activity Name TESTING P: Planed Problem Faced: NA Duration P| A 7 7 Starting Date P| A 17th 17th November November 2009 2009 Finishing Date P| A 22nd 22nd November November 2009 2009 D: DONE Status D E: E XECUTING
12
Client Distribution
4.1
Project Overview :-
Todays world is running w ith a great speed and concept of existence is most important everywhere. In this great struggle of keeping existence, the whole society is in the glorious proceeding just getting COMPUTERIZATION as the only tool. Computerization w ith its newer and newer solution, has given the modern of great success and victory. Basically this system is built in that w ay that it is suitable for any enterpris e. Transactions will be too much easier using this system. It keeps all the tracks of the creditors, retailers, distributors as well as of the sales and the damages stocks and stores them in the database permanently. The databases are also flexible. The addition & deletion is also done automatically. So this ystem provides less overhead for the user. Below Level Aw areness: From various surveys it has found that through about the use of computer to control a companys stock is much easier and faster than previous manual controlling the stock system. Indian Scenario: Business society and government cannot afford to ignore the digital society just because its current impact is difficult to measure. Our project is based on SALES MONITORING & INVENTORY CONTROL strategy manufacturing company who supply / dispatch products to those customers (clients) who pay a minimum demanded advance to the company. To implement this mechanism w e use Oracle as backend for database table. In this project we use number of Java classes to transform data from client side to database and vic e-versa. Mechanism of the project is that authorized user can login to main platform to maintain the total process. After login, the logged user will have all rights to do work within this platform related w ith the project.
4.2
Objective:Sales Management helps to faster transaction between customer & company. In this case business transaction cost became lesser. In this case business ordering cost als o became lesser. In this case client as well as company saves their valuable time. In this case total cost of business of company comes down. Client gets the facility to choose the maximum number of item w ith minimum eff ort. Through this client is able to purchase or sale anything at anytime if the stock permits!
4.3
Major W ork Activities:Sl. No. 1. 2. 3. 4. 5. Phases Requirement Analysis Design Coding Testing Documentation Description Deciding features to be included and examination the feasibility Designing system architecture and creating user interface Creating a database, connectivity and coding of modules Testing and debugging of modules and integrating them, final performance testing Submission of final reports, finalizing the project report and hence complete documentation
13
Table: USERLOGIN: FIELD NAME USERNAME PASSWORD DATA TYPE TEXT TEXT DESCRIPTION VARCHAR2, 10 DIGITS VARCHAR2, 10 DIGITS
Table: CREDITORMASTER FIELD NAME CREDITORID CREDITORNAME CREDITORADDRESS CONTACTNO DATA TYPE TEXT TEXT TEXT TEXT DESCRIPTION VARCHAR2, 5 DIGITS VARCHAR2, 20 DIGITS VARCHAR2, 40 DIGITS VARCHAR2, 10 DIGITS
Table: RETAILERMASTER FIELD NAME RETAILERID RETAILERNAME RETAILERADDRESS CONTACTNO DATA TYPE TEXT TEXT TEXT TEXT DESCRIPTION VARCHAR2, 5 DIGITS VARCHAR2, 20 DIGITS VARCHAR2, 40 DIGITS VARCHAR2, 10 DIGITS
Table: DISTRIBUTORMASTER FIELD NAME DISTRIBUTORID DISTRIBUTORNAME DISTRIBUTORADDRESS CONTACTNO DATA TYPE TEXT TEXT TEXT TEXT DESCRIPTION VARCHAR2, 5 DIGITS VARCHAR2, 20 DIGITS VARCHAR2, 40 DIGITS VARCHAR2, 10 DIGITS
Table: CATEGORY FIELD NAME CATEGORYID CATEGORY_NAME DATA TYPE TEXT TEXT DESCRIPTION VARCHAR2, 5 DIGITS VARCHAR2, 20 DIGITS
14
Table: SUBCATEGORY FIELD NAME SUBCATEGORYID SUBCATEGORY_NAME DATA TYPE TEXT TEXT DESCRIPTION VARCHAR2, 5 DIGITS VARCHAR2, 5 DIGITS
Table: STOCK FIELD NAME CATEGORYID SUBCATEGORYID QTY UNITPRICE PURCHASEDATE PURCHASEID DATA TYPE TEXT TEXT TEXT TEXT DATE TEXT DESCRIPTION VARCHAR2, 5 DIGITS VARCHAR2, 5 DIGITS VARCHAR2, 4 DIGITS VARCHAR2, 4 DIGITS VARCHAR2,10 DIGITS VARCHAR2,5 DIGITS
Table: SALES FIELD NAME BILLNO BILL_DATE CATEGORYID SUBCATEGORYID RETAILERID QTY_SOLD UNIT_PRICE DATA TYPE TEXT TEXT TEXT TEXT TEXT TEXT TEXT DESCRIPTION VARCHAR2, 5 DIGITS DATE VARCHAR2, 40 DIGITS VARCHAR2, 10 DIGITS VARCHAR2, 10 DIGITS VARCHAR2, 10 DIGITS VARCHAR2, 10 DIGITS
Table: DAMAGEDRET URN FIELD NAME RETURN_DATE RETAILERID AGAINST_BILL_NO CATEGORYID SUBCATEGORY QTY_RETURNED DATA TYPE TEXT TEXT TEXT TEXT TEXT TEXT DESCRIPTION VARCHAR2, 5 DIGITS VARCHAR2, 20 DIGITS VARCHAR2, 40 DIGITS VARCHAR2, 10 DIGITS VARCHAR2, 10 DIGITS VARCHAR2, 10 DIGITS
15
Client Distribution
Feasibility Study
Feasibility analysis involves eight steps:1. Form a project team and appoint a project leader. 2. Prepare system flowchart. 3. Enumerate potential candidate system. 4. Describe and identif y characteristic s of candidate systems. 5. Describe and evaluate performance and cost effectiveness of each candidate system. 6. Weight system performance and cost data. 7. Select the best candidate system. 8. Prepare and report final project directive to management. Three keys considerations are involved in the feasibility analysis: 1) Technical 2) Operational 3) Economic 1) Technical Feasibility: - It specifies whether the proposed solution in the project is possible to be implemented using available hardware and softw are. 2) Operational Feasibility: - It considers the factor that how it could be changed for future requirements and the operational factors of the computer. 3) Econom ic Feasibility: - It defines the measurement cost effectiv eness of the project: (A). Direct Cost (B). Indirect Cost
ECONOMIC FEASIBILITY OF THE PROJECT:1). Initial cost for development is not so high since a machine required configuration is available in the instruction. 2). S/W for back-end and front-end are also readily available.
COST-BENEFIT ANALYSIS
The development of any project is to be done keeping in mind the cost and benefits associated with any project. A project will not be Viable if its costs exceed its benefits. Thus cost-benefit analysis is very critical for every project. As w ith every project the need for cost-benefit analysis was als o felt w ith project. A suitable analysis has been outlined below . COSTS: Cost associated w ith project may be classified as analysis costs, development costs, testing and pilot costs, implementation costs, training Costs, system maintenance cost and other related costs. For finding out the total costs involv ed with this project we div ide the costs as under:1. Hardw are and Software. 2. Development Charges (calculated as per man-hours utilized) 3. Training Cost (calculated as per no. of personal trained) 4. System Implementation and maintenance costs. 5. Stationary Charges. 6. Other Pre and Post Implementation costs. 7. Of the above except 3 and 4, all are direct costs and their value can be found out very specific ally. For other costs, the cost can be found out by taking the general rate paid to the development staff. Benefits:The benefits of this system have already been enumerated. Let us now discuss them one by one:1. Initial costs for development are not so high since a machine w ith required configuration and software for back-end and front-end are available. 2. This system w ould help to simplify the various important operations of a Library management system. Thereby it reduces the consumption of time and energy which are very valuable. Finally w e can conclude that benefits are much more than the costs associated w ith this project. Hence the project is viable and worthy of being developed.
16
Feasibility Study
Design
Maintenance
17
Creditor
Retailer
Distributor
Stock
Creditor Database
Retailer Database
Di stributor Database
Stock Database
CategoryID, name
Subcategory
Category
Category Database
Sub-Categor y Database
Sales
Damaged Return Database
Bill_Date, price
Damaged Return
Sales Database
18
6.2
Table: CREDITORMASTER FIELD NAME CREDITORID CREDITORNAME CREDITORADDRESS CONTACTNO Table: RETAILERMASTER FIELD NAME RETAILERID RETAILERNAME RETAILERADDRESS CONTACTNO Table: DISTRIBUTORMASTER FIELD NAME DISTRIBUTORID DISTRIBUTORNAME DISTRIBUTORADDRESS CONTACTNO Table: CATEGORY FIELD NAME CATEGORYID CATEGORY_NAME Table: SUBCATEGORY FIELD NAME SUBCATEGORYID SUBCATEGORY_NAME Table: STOCK FIELD NAME CATEGORYID SUBCATEGORYID QTY UNITPRICE PURCHASEDATE PURCHASEID DATA TYPE TEXT TEXT TEXT TEXT DATE TEXT DESCRIPTION VARCHAR2, 5 DIGITS VARCHAR2, 5 DIGITS VARCHAR2, 4 DIGITS VARCHAR2, 4 DIGITS DATE VARCHAR2,5 DIGITS DATA TYPE TEXT TEXT DESCRIPTION VARCHAR2, 5 DIGITS VARCHAR2, 5 DIGITS DATA TYPE TEXT TEXT DESCRIPTION VARCHAR2, 5 DIGITS VARCHAR2, 20 DIGITS DATA TYPE TEXT TEXT TEXT TEXT DESCRIPTION VARCHAR2, 5 DIGITS VARCHAR2, 20 DIGITS VARCHAR2, 40 DIGITS VARCHAR2, 10 DIGITS DATA TYPE TEXT TEXT TEXT TEXT DESCRIPTION VARCHAR2, 5 DIGITS VARCHAR2, 20 DIGITS VARCHAR2, 40 DIGITS VARCHAR2, 10 DIGITS DATA TYPE TEXT TEXT TEXT TEXT DESCRIPTION VARCHAR2, 5 DIGITS VARCHAR2, 20 DIGITS VARCHAR2, 40 DIGITS VARCHAR2, 10 DIGITS
19
6.2.2
DTC DESCRIPTION:
This system does not have any specific DTC, The user can create tables according to one need and hence it can be said that the data said that the data structure is dynamic. 6.2.3 DESIGN
DATA FLOW DIAGRAM: Graphical description of a systems data and how the process transforms the data is know n as Data Flow Diagram. A DFD models is a system using by using external entities from w hic h data flows to a process which transforms the data and creates output data flows whic h go to other processes or external entities or data store. Stored data may also flow or a process as input. LOGICAL & PHYSICAL DFD:DFD that specify various logical processes performed on the data, i.e. typed of operations performed is called logical DFD. It specifies what the system does and not how it does. A physical DFD specifies how the systems requirements are implemented. It is drawn during the system design phase. It is a good starting point and involves operational task and techniques. A logical DFD is derived from physic al DFD. At first step, an entire system connects all the data sources with proper direction of flow data. This DFD is called Context Level DFD or Zero level DFD. In the follow ing steps the entire system is broken into several sub-systems. The DFD that contains more than one process is referred to as Level 1, Level 2 and so on.
SYMBOLS USED IN DFD: To construct a DFD the follow ing system are used: 1. Functional System 2. External entity symbol 3. Data flow symbol 4. Data store symbol A data store : any stored data but w ith no reference to the physic al method of the physical method of storing A data flow : identifies flow of data An external entity: source or destination of date. which is external to the system
20
USER
DATABASE
21
22
UserLogIn.java:
This is the User login page in which a valid username and password is needed to log in into th system. Only a valid user canl go to the main page of Sales Monitoring and Inventory Control System. Th password field is edited with a * for the security purpose.
23
//UserLogIn.java import java.sql.*; import java.awt.*; public class UserLogin extends java.awt.Frame { public UserLogin() { initComponents(); centre(); } public void centre() { Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize(); int x = (int) (screenSize.getWidth() / 2 - getWidth() / 2); int y = (int) (screenSize.getHeight() / 2 - getHeight() / 2); setLocation(x, y); } pri vate void initComponents() { label1 = new java.awt.Label(); button1 = new java.awt.Button(); button2 = new java.awt.Button(); te xtField1 = new java.awt.TextField(); te xtField2 = new java.awt.TextField(); label2 = new java.awt.Label(); label3 = new java.awt.Label(); label5 = new java.awt.Label(); label6 = new java.awt.Label(); setAlwaysOnTop(true); setBackground(new java.awt.Color(153, 204, 255)); setBounds(new java.awt.Rectangle(300, 300, 300, 300)); setCursor(new java.awt.Cursor(java.awt.Cursor.DEFAULT_CURSOR)); setIconImages(null); setMinimumSize(new java.awt.Dimension(400, 250)); setResizable(false); setTitle("User Login"); addWindowListener(new java.awt.event.WindowAdapter() { public void windowActivated(java.awt.e vent.WindowEvent evt) { formWindowActivated(evt); } public void windowClosing(java.awt.event.WindowEvent evt) { e xitForm(evt); } }); setLayout(null); label1.setFont(new java.awt.Font("Dialog", 1, 24)); label1.setText("User Login"); add(label1); label1.setBounds(140, 50, 130, 30); button1.setBackground(new java.awt.Color(204, 204, 204));
24
25
26
XYZEnt.java:
This is the main page of Sales Monitoring and Control System. Here a logged user can do different tasks .
27
//XYZEnt.ja va import java.awt.*; import java.util.*; public class XYZEnt e xtends java.awt.Frame implements Runnable { Thread t, t1; public void start() { t = new Thread(this); t.start(); } public void run() { t1 = Thread.currentThread(); while (t1 == t) { Calendar cal = new GregorianCalendar(); String hour = String.valueOf(cal.get(Calendar.HOUR)); String minute = String.valueOf(cal.get(Calendar.MINUTE)); String second = String.valueOf(cal.get(Calendar.SECOND)); label1.setText(hour + ":" + minute + ":" + second); try { t1.sleep(1000); } catch (InterruptedException e) { } } } public XYZEnt() { initComponents(); centre(); //centers this form on screen start(); } pri vate void initComponents() { label1 = new java.awt.Label(); label2 = new java.awt.Label(); menuBar1 = new java.awt.MenuBar(); menu1 = new java.awt.Menu(); menuItem1 = new java.awt.MenuItem(); menuItem2 = new java.awt.MenuItem();
28
29
30
31
32
// Variables declaration
33
34
CreditorMaintenence.java:
User can keep the record of Companys creditor in creditor maintenance part.
35
//CreditorMaintenence.java import java.sql.*; import java.awt.*; public class CreditorMaintainanace extends java.awt.Frame { public CreditorMaintainanace() { initComponents(); centre(); } public void centre() { Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize(); int x = (int) (screenSize.getWidth() / 2 - getWidth() / 2); int y = (int) (screenSize.getHeight() / 2 - getHeight() / 2); setLocation(x, y); } pri vate void initComponents() { label1 = new java.awt.Label(); label2 = new java.awt.Label(); label3 = new java.awt.Label(); te xtField1 = new java.awt.TextField(); te xtField2 = new java.awt.TextField(); te xtField3 = new java.awt.TextField(); label4 = new java.awt.Label(); button1 = new java.awt.Button(); te xtArea1 = new java.awt.Te xtArea(); label5 = new java.awt.Label(); button3 = new java.awt.Button(); label6 = new java.awt.Label(); te xtField4 = new java.awt.TextField(); setAlwaysOnTop(true); setBackground(new java.awt.Color(153, 204, 255)); setBounds(new java.awt.Rectangle(300, 200, 0, 0)); setMinimumSize(new java.awt.Dimension(570, 470)); setResizable(false); setTitle("Creditor Maintainance"); addWindowListener(new java.awt.event.WindowAdapter() { public void windowActivated(java.awt.e vent.WindowEvent evt) { formWindowActivated(evt); } public void windowClosing(java.awt.event.WindowEvent evt) { e xitForm(evt);
36
37
38
39
RetailerMaintenence.java:
User can keep the record of Companys retailer in retailer maintenance part.
40
//RetailerMaintenence.java import java.sql.*; import java.awt.*; public class RetailerMaintainance extends java.awt.Frame { public RetailerMaintainance() { initComponents(); centre(); } public void centre() { Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize(); int x = (int) (screenSize.getWidth() / 2 - getWidth() / 2); int y = (int) (screenSize.getHeight() / 2 - getHeight() / 2); setLocation(x, y); } private void initComponents() { label1 = new java.awt.Label(); label2 = new java.awt.Label(); label3 = new java.awt.Label(); te xtField1 = new java.awt.TextField(); te xtField2 = new java.awt.TextField(); te xtField3 = new java.awt.TextField(); label4 = new java.awt.Label(); button1 = new java.awt.Button(); te xtArea1 = new java.awt.Te xtArea(); label5 = new java.awt.Label(); button3 = new java.awt.Button(); label6 = new java.awt.Label(); te xtField4 = new java.awt.TextField(); setAlwaysOnTop(true); setBackground(new java.awt.Color(153, 204, 255)); setBounds(new java.awt.Rectangle(300, 200, 0, 0)); setMinimumSize(new java.awt.Dimension(575, 440)); setResizable(false); setTitle("Retailer Maintainance"); addWindowListener(new java.awt.event.WindowAdapter() { public void windowActivated(java.awt.e vent.WindowEvent evt) { formWindowActivated(evt); } public void windowClosing(java.awt.event.WindowEvent evt) { exitForm(evt); } });
41
42
43
44
DistributorMaintenence.java:
User can keep the record of Companys distributor in distributor maintenance part.
45
//DistributorMaintenence.java import java.sql.*; import java.awt.*; public class DistributorMaintainanace extends java.awt.Frame { public DistributorMaintainanace() { initComponents(); centre(); } public void centre() { Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize(); int x = (int) (screenSize.getWidth() / 2 - getWidth() / 2); int y = (int) (screenSize.getHeight() / 2 - getHeight() / 2); setLocation(x, y); } pri vate void initComponents() { label1 = new java.awt.Label(); label2 = new java.awt.Label(); label3 = new java.awt.Label(); te xtField1 = new java.awt.TextField(); te xtField2 = new java.awt.TextField(); te xtField3 = new java.awt.TextField(); label4 = new java.awt.Label(); button1 = new java.awt.Button(); //button2 = new java.awt.Button(); te xtArea1 = new java.awt.Te xtArea(); label5 = new java.awt.Label(); button3 = new java.awt.Button(); label6 = new java.awt.Label(); te xtField4 = new java.awt.TextField(); setAlwaysOnTop(true); setBackground(new java.awt.Color(153, 204, 255)); setBounds(new java.awt.Rectangle(300, 200, 0, 0)); setMinimumSize(new java.awt.Dimension(600, 470)); setResizable(false); setTitle("Distributor Master Maintainance"); addWindowListener(new java.awt.event.WindowAdapter() { public void windowActivated(java.awt.e vent.WindowEvent evt) { formWindowActivated(evt); } public void windowClosing(java.awt.event.WindowEvent evt) {
46
47
48
49
AddNewCategory.java:
User can add new category of product into category database using this form. Step to be followed to get this form as follows: Master Maintenance > Item Group Master Maintenance >Add New Category.
50
//AddNewCategory .java import java.sql.*; import java.awt.*; public class AddNewCategory e xtends java.awt.Frame { /** Creates new form AddNewCategory */ public AddNewCategory() { initComponents(); centre(); } pri vate void initComponents() { label1 = new java.awt.Label(); button1 = new java.awt.Button(); te xtField1 = new java.awt.TextField(); button2 = new java.awt.Button(); label2 = new java.awt.Label(); label3 = new java.awt.Label(); te xtField2 = new java.awt.TextField(); label4 = new java.awt.Label(); setBackground(new java.awt.Color(153, 204, 255)); setMinimumSize(new java.awt.Dimension(400, 200)); setTitle("Add New Category"); addWindowListener(new java.awt.event.WindowAdapter() { public void windowClosing(java.awt.event.WindowEvent evt) { e xitForm(evt); } }); setLayout(null); label1.setFont(new java.awt.Font("Dialog", 1, 16)); label1.setText("Add New Category"); add(label1); label1.setBounds(120, 30, 150, 25); button1.setLabel("Save"); button1.addActionListener(new java.awt.event.ActionListener() { public void actionPerformed(java.awt.event.ActionEvent evt) { button1ActionPerformed(evt); } }); add(button1); button1.setBounds(230, 150, 43, 24); te xtField1.addMouseListener(new java.awt.event.MouseAdapter() { public void mouseClicked(java.awt.event.MouseEvent evt) { textField1MouseClicked(evt); } });
51
52
53
DeleteCategory.java:
User can delete category of product from category database using this form. Step to be followed to get this form as follows: Master Maintenance > Item Group Master Maintenance >Delete Category.
54
//DeleteCategory.java import java.sql.*; import java.awt.*; public class DeleteCategory extends java.awt.Fram e { public DeleteCategory() { initComponents(); centre(); } public void centre() { Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize(); int x = (int) (screenSize.getWidth() / 2 - getWidth() / 2); int y = (int) (screenSize.getHeight() / 2 - getHeight() / 2); setLocation(x, y); } pri vate void initComponents() { button1 = new java.awt.Button(); choice1 = new java.awt.Choice(); button2 = new java.awt.Button(); label1 = new java.awt.Label(); label2 = new java.awt.Label(); label3 = new java.awt.Label(); te xtField1 = new java.awt.TextField(); label4 = new java.awt.Label(); setBackground(new java.awt.Color(153, 204, 255)); setMinimumSize(new java.awt.Dimension(380, 210)); setTitle("Category Deletion"); addWindowListener(new java.awt.event.WindowAdapter() { public void windowActivated(java.awt.e vent.WindowEvent evt) { formWindowActivated(evt); } public void windowClosing(java.awt.event.WindowEvent evt) { e xitForm(evt); } }); setLayout(null); button1.setLabel("Ok"); button1.addActionListener(new java.awt.event.ActionListener() { public void actionPerformed(java.awt.event.ActionEvent evt) { button1ActionPerformed(evt); } }); add(button1); button1.setBounds(170, 160, 60, 24); choice1.addMouseListener(new java.awt.event.MouseAdapter() { public void mouseClicked(java.awt.event.MouseEvent evt) { choice1MouseClicked(evt); }
55
56
57
AddNewSubCategory.java:
User can add new Sub-category of an existing product Category into Sub-category database using this form. Step to be followed to get this form as follows: Master Maintenance > Item Group Master Maintenance >Add New Sub Category.
58
//AddNewSubCategory.java import java.sql.*; import java.awt.*; public class AddNewSubCategory extends java.awt.Frame { public AddNewSubCategory() { initComponents(); centre(); } pri vate void initComponents() { label1 = new java.awt.Label(); label2 = new java.awt.Label(); label3 = new java.awt.Label(); label4 = new java.awt.Label(); choice1 = new java.awt.Choice(); te xtField1 = new java.awt.TextField(); te xtField2 = new java.awt.TextField(); button1 = new java.awt.Button(); button2 = new java.awt.Button(); label5 = new java.awt.Label(); setBackground(new java.awt.Color(153, 204, 255)); setMinimumSize(new java.awt.Dimension(400, 260)); setTitle("Add New SubCategory"); addWindowListener(new java.awt.event.WindowAdapter() { public void windowActivated(java.awt.e vent.WindowEvent evt) { formWindowActivated(evt); } public void windowClosing(java.awt.event.WindowEvent evt) { e xitForm(evt); } }); setLayout(null); label1.setFont(new java.awt.Font("Dialog", 1, 14)); label1.setText("Add New Sub-Category"); add(label1); label1.setBounds(110, 40, 170, 23); label2.setText("Category"); add(label2); label2.setBounds(10, 100, 60, 20); label3.setText("Sub-Category ID"); add(label3); label3.setBounds(10, 130, 94, 20); label4.setText("Sub-Category Name"); add(label4); label4.setBounds(10, 160, 120, 20);
59
60
61
DeleteSubCategory.java:
User can delete sub-category of product from subcategory database using this form. Step to be followed to get this form as follows: Master Maintenance > Item Group Master Maintenance >Delete Sub Category.
62
//DeleteSubCategory.java import java.sql.*; import java.awt.*; public class DeleteSubCategory extends java.awt.Frame { public DeleteSubCategory() { initComponents(); centre(); } public void centre() { Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize(); int x = (int) (screenSize.getWidth() / 2 - getWidth() / 2); int y = (int) (screenSize.getHeight() / 2 - getHeight() / 2); setLocation(x, y); } pri vate void initComponents() { label1 = new java.awt.Label(); label2 = new java.awt.Label(); label3 = new java.awt.Label(); choice1 = new java.awt.Choice(); choice2 = new java.awt.Choice(); button1 = new java.awt.Button(); button2 = new java.awt.Button(); te xtField1 = new java.awt.TextField(); label4 = new java.awt.Label(); label5 = new java.awt.Label(); setBackground(new java.awt.Color(153, 204, 255)); setMinimumSize(new java.awt.Dimension(400, 280)); setTitle("Delete Sub-Category"); addWindowListener(new java.awt.event.WindowAdapter() { public void windowActivated(java.awt.e vent.WindowEvent evt) { formWindowActivated(evt); } public void windowClosing(java.awt.event.WindowEvent evt) { e xitForm(evt); } }); addMouseMotionListener(new java.awt.event.MouseMotionAdapter() { public void mouseMoved(java.awt.event.MouseEvent evt) { formMouseMoved(evt); } }); setLayout(null); label1.setFont(new java.awt.Font("Dialog", 1, 16)); label1.setText("Delete Sub-Category"); add(label1);
63
64
65
66
AddStock.java:
to maintain the stock of XYZEnterprise, its badly needed to keep the information about stock during addition / deletion of stock. Here we are going to add a new product of existing category or sub-category to stock database.
67
//AddStock.java import java.sql.*; import java.awt.*; public class AddStock extends java.awt.Frame { /** Creates new form AddStock */ public AddStock() { initComponents(); centre(); } public void centre() { Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize(); int x = (int) (screenSize.getWidth() / 2 - getWidth() / 2); int y = (int) (screenSize.getHeight() / 2 - getHeight() / 2); setLocation(x, y); } pri vate void initComponents() { label1 = new java.awt.Label(); label2 = new java.awt.Label(); label3 = new java.awt.Label(); choice1 = new java.awt.Choice(); choice2 = new java.awt.Choice(); label4 = new java.awt.Label(); label5 = new java.awt.Label(); te xtField1 = new java.awt.TextField(); te xtField2 = new java.awt.TextField(); label6 = new java.awt.Label(); te xtField3 = new java.awt.TextField(); button1 = new java.awt.Button(); button2 = new java.awt.Button(); label7 = new java.awt.Label(); te xtField4 = new java.awt.TextField(); label8 = new java.awt.Label(); setBackground(new java.awt.Color(153, 204, 255)); setMinimumSize(new java.awt.Dimension(450, 380)); setResizable(false); setTitle("Add Stock"); addMouseListener(new java.awt.event.MouseAdapter() { public void mouseEntered(java.awt.event.MouseEvent evt) { formMouseEntered(evt); } }); addWindowListener(new java.awt.event.WindowAdapter() {
68
69
70
71
72
DeleteStock.java:
73
Category Deleted
//DeleteStock.java import java.awt.*; import java.sql.*; public class DeleteStock extends java.awt.Frame { public DeleteStock() { initComponents(); centre(); } public void centre() { Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize(); int x = (int) (screenSize.getWidth() / 2 - getWidth() / 2); int y = (int) (screenSize.getHeight() / 2 - getHeight() / 2); setLocation(x, y); } pri vate void initComponents() { label1 = new java.awt.Label(); label2 = new java.awt.Label(); label3 = new java.awt.Label(); te xtField2 = new java.awt.TextField(); choice1 = new java.awt.Choice(); label4 = new java.awt.Label(); button1 = new java.awt.Button(); button2 = new java.awt.Button(); choice2 = new java.awt.Choice(); label5 = new java.awt.Label(); setBackground(new java.awt.Color(153, 204, 255)); setMinimumSize(new java.awt.Dimension(350, 250)); setResizable(false); setTitle("Delete Stock"); addWindowListener(new java.awt.event.WindowAdapter() { public void windowActivated(java.awt.e vent.WindowEvent evt) { formWindowActivated(evt); } public void windowClosing(java.awt.event.WindowEvent evt) { e xitForm(evt); } }); addMouseMotionListener(new java.awt.event.MouseMotionAdapter() { public void mouseMoved(java.awt.event.MouseEvent evt) { formMouseMoved(evt); } }); setLayout(null);
74
75
76
77
UserMaintenence.java:
This will help to add a new user to be an authorized user. Data will be added to the UserLogin database.
78
//AddNewUser.java import java.sql.*; import java.awt.*; public class AddNewUser extends java.awt.Frame { public AddNewUser() { initComponents(); centre(); } public void centre() { Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize(); int x = (int) (screenSize.getWidth() / 2 - getWidth() / 2); int y = (int) (screenSize.getHeight() / 2 - getHeight() / 2); setLocation(x, y); } pri vate void initComponents() { label1 = new java.awt.Label(); te xtField1 = new java.awt.TextField(); te xtField2 = new java.awt.TextField(); label2 = new java.awt.Label(); label3 = new java.awt.Label(); button1 = new java.awt.Button(); button2 = new java.awt.Button(); setAlwaysOnTop(true); setBackground(new java.awt.Color(153, 204, 255)); setBounds(new java.awt.Rectangle(300, 300, 300, 300)); setIconImages(null); setMinimumSize(new java.awt.Dimension(400, 200)); setResizable(false); setTitle("Adding New User"); addWindowListener(new java.awt.event.WindowAdapter() { public void windowClosing(java.awt.event.WindowEvent evt) { e xitForm(evt); } }); setLayout(null); label1.setFont(new java.awt.Font("Dialog", 1, 16)); // NOI18N label1.setForeground(new java.awt.Color(0, 0, 0)); label1.setText("Add New User"); add(label1); label1.setBounds(150, 40, 110, 25); add(textField1); te xtField1.setBounds(110, 90, 200, 20); add(textField2); te xtField2.setBounds(110, 120, 200, 20); label2.setFont(new java.awt.Font("Dialog", 1, 12)); // NOI18N label2.setText("User ID"); add(label2); label2.setBounds(30, 90, 60, 20); label3.setFont(new java.awt.Font("Dialog", 1, 12)); // NOI18N label3.setText("Password");
79
80
Sales.java:
This form appears in Transaction menu of XYZEnterprise main page which keeps track of the data sold & stores in sales database.
81
//Sales.java import java.sql.*; import java.awt.*; public class Sales extends java.awt.Frame { static int qoh1, qoh2, qoh3; public Sales() { initComponents(); centre(); } public void centre() { Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize(); int x = (int) (screenSize.getWidth() / 2 - getWidth() / 2); int y = (int) (screenSize.getHeight() / 2 - getHeight() / 2); setLocation(x, y); } pri vate void initComponents() { label1 = new java.awt.Label(); label2 = new java.awt.Label(); label3 = new java.awt.Label(); button1 = new java.awt.Button(); button2 = new java.awt.Button(); button3 = new java.awt.Button(); te xtField1 = new java.awt.TextField(); te xtField2 = new java.awt.TextField(); label4 = new java.awt.Label(); label5 = new java.awt.Label(); choice1 = new java.awt.Choice(); choice2 = new java.awt.Choice(); checkbox1 = new java.awt.Checkbox(); choice3 = new java.awt.Choice(); label6 = new java.awt.Label(); label7 = new java.awt.Label(); choice4 = new java.awt.Choice(); te xtField3 = new java.awt.TextField(); label8 = new java.awt.Label(); label9 = new java.awt.Label(); label10 = new java.awt.Label(); te xtField4 = new java.awt.TextField(); te xtField5 = new java.awt.TextField(); checkbox2 = new java.awt.Checkbox(); choice5 = new java.awt.Choice(); choice6 = new java.awt.Choice();
82
83
84
85
86
87
88
89
90
91
92
93
DamagedReturn.java:
This form is in Transaction menu of XYZEnterprise main page which keeps information about returned product.
94
//DamagedReturn.java import java.sql.*; import java.awt.*; public class DamagedReturn extends java.awt.Frame { public DamagedReturn() { initComponents(); centre(); } public void centre() { Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize(); int x = (int) (screenSize.getWidth() / 2 - getWidth() / 2); int y = (int) (screenSize.getHeight() / 2 - getHeight() / 2); setLocation(x, y); } private void initComponents() { label1 = new java.awt.Label(); label2 = new java.awt.Label(); label3 = new java.awt.Label(); label4 = new java.awt.Label(); label5 = new java.awt.Label(); te xtArea1 = new java.awt.Te xtArea(); button1 = new java.awt.Button(); button2 = new java.awt.Button(); button3 = new java.awt.Button(); te xtField4 = new java.awt.TextField(); te xtField5 = new java.awt.TextField(); label6 = new java.awt.Label(); choice1 = new java.awt.Choice(); label7 = new java.awt.Label(); choice2 = new java.awt.Choice(); choice3 = new java.awt.Choice(); setAlwaysOnTop(true); setBackground(new java.awt.Color(153, 204, 255)); setMinimumSize(new java.awt.Dimension(600, 400)); setResizable(false); setTitle("Damaged Stock Return"); addWindowListener(new java.awt.event.WindowAdapter() { public void windowActivated(java.awt.e vent.WindowEvent evt) { formWindowActivated(evt); } public void windowClosing(java.awt.event.WindowEvent evt) { e xitForm(evt); } }); setLayout(null); label1.setText("Bill No.");
95
96
97
98
HelpContents.java:
This part of Sales helps user to know about the software in details. This is represents the over all steps which are to be done through this software. This is used to show about the project,project coordinator and development team name.
StartPage.java:
About.java:
99
//HelpContent.java import java.awt.*; public class HelpContents extends java.awt.Frame { public HelpContents() { initComponents(); centre(); } public void centre() { Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize(); int x = (int) (screenSize.getWidth() / 2 - getWidth() / 2); int y = (int) (screenSize.getHeight() / 2 - getHeight() / 2); setLocation(x, y); } pri vate void initComponents() { te xtArea1 = new java.awt.Te xtArea(); label1 = new java.awt.Label(); setAlwaysOnTop(true); setBackground(new java.awt.Color(153, 204, 255)); setBounds(new java.awt.Rectangle(0, 0, 0, 0)); setMinimumSize(new java.awt.Dimension(470, 320)); setResizable(false); setTitle("Help Contents"); addWindowListener(new java.awt.event.WindowAdapter() { public void windowClosing(java.awt.event.WindowEvent evt) { e xitForm(evt); } }); setLayout(null); te xtArea1.setBackground(new java.awt.Color(204, 255, 255)); te xtArea1.setEditable(false); te xtArea1.setFont(new java.awt.Font("Dialog", 0, 13)); // NOI18N te xtArea1.setText(" This \"Stock Management & Inventory Control System \" is prepared with\n some basic options that is needed in any transaction. It checks for proper \n user ID to Login into th system.It can also add a new user after successful \n login.It can also add Creditor,Distributor,Retailer details to the database,\n It can also keep track on the transactions i.e. sales & returns of damage\n stocks.\n\t\tThe system keeps track of the items purchased as \n well as sold by a trading company. This includes various master mainten-\n ance modules, including inventory management and transaction entry.\n Various reports are also generated to aid the management in its decision \n making process. "); add(textArea1); te xtArea1.setBounds(10, 80, 440, 200); label1.setFont(new java.awt.Font("Dialog", 1, 16)); label1.setText("Help Contents"); add(label1);
100
Start Page
//StartPage.java import java.awt.*; public class HelpStartPage extends java.awt.Frame { public HelpStartPage() { initComponents(); centre(); } public void centre() { Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize(); int x = (int) (screenSize.getWidth() / 2 - getWidth() / 2); int y = (int) (screenSize.getHeight() / 2 - getHeight() / 2); setLocation(x, y);
101
102
About
//About.java import java.awt.*; public class HelpAbout extends java.awt.Frame { public HelpAbout() { initComponents(); centre(); } public void centre() { Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize(); int x = (int) (screenSize.getWidth() / 2 - getWidth() / 2); int y = (int) (screenSize.getHeight() / 2 - getHeight() / 2); setLocation(x, y); } pri vate void initComponents() { te xtArea1 = new java.awt.Te xtArea();
103
104
105
Testing:Introduction:
Testing is approved of executing a program w ith the explicit intention of finding error, i.e. making the program fail. Testing is a complex processes. In order to make this processes simpler, the testing are broken into smaller activities.
Techniques:
Testing means the processes of analy zing the softw are item to detect the different between existing or required condition and evaluate the features of the software item. Through testing of the system before release of the software needs to be done to vide the various test case and modes so that the software becomes devoid of bugs uses minimum space requirement as w ell as minimum time to perform. The test cases were selected before hand with expected result defined and actual result recorded for comparison. The selection of test cases is done vide White Box Testing techniques to check internal programming logic and effic iency vide Black Box Testing techniques to check softw are requirement fulfillment w ith intention of finding maximum number of errors with minimum effort of time. Although test case are design by considering the cyclomatic complexity, conditional test, still the software code is not in its optional form, as all other possible alternative parts in the software are not consider. At the integration level, software to the third party tests, which further enhance the software optimality and efficiency.
The follow ing flow graph methodology was used while testing the software:
Here each circle represents one or more non-branching procedural language or source code Statement in flow graph. While performing condition testing, domain-testing methodology was selected. While performing loop testing, simple loops concatenated loops, nes ted and unstructured loops were tested thoroughly.
Test Characters:
A A A A good test has a probability of finding an error. good test is not redundant. good test should be best of breed. good test should be neither too simple nor too complex.
106
8.2
Test Plan:-
Testing means the processes of analyzing software item to detect the difference betw een the exis ting and required permission and to evaluate of the software item. Once test plan and the test case are completely designed, different of testing starts.
Unit Te sting:
The unit testing is performed to test the validity to the individual units. This is done in the coding phase w ith the interactive testing maintain uniformity throughout the screen. screen. Specific Test: This testing is done on the functional part of the object in the General Testing: This testing is performed on the interface design to
Integration testing:
to the desired benchmarked. When the integration test phase is stared the interface between the modules are tested. System Testing: It incorporates the performance stress testing so as to meet the product criteria w ith respect Recovery Test: It test the response of the system to the presence of the faults, or loss of power, devic es, services, data, etc. the system is subjected to the loss of the mentioned resources in order to check if the system recover satisfactory. Security Test: It is carried out to ensure the security of the SRS document and prevent unauthorized access. Stress Test: It is know n as endurance testing. It evaluates system performance when it is stressed for short period of time. Perform ance Test: It is carried out to check whether the system meets the nonfunctional requirement identified in the SRS document. Test case Generation: provides with an outright failure or whether some of the expected result of the test were actually observed.
Validation Testing:
Tests were performed to find conformity with the requirement. Plans and procedure were designed to ensure that all functional requirements are satisfied. Alpha Test: The alpha test is conducted at the developer site by a customer under the control of the developer. Beta Test: In Beta testing the developer system is to be tested by the user or customer for whom the system is developed.
8.3
Test Log:Testing Phase Component Function to be tested Checked w hether the method returns the expected value Checked w hether all the method are running properly Checked the w hole system is working according to the user requirement Scheduled 17th November, 2009 19th November, 2009 Actual Date 17th November, 2009 19th November, 2009 Comment Properly Working
Integrated Testing
Properly Working
System Testing
Properly Working
107
9.0
User Manual:-
USER :
A user will not able to log into the system without any ID & PASSWORD. User have to turn the system off properly otherwise bad data or sudden crash may occur to the system. No keyboard shortcuts are provided.
Q. IT IS NOT ACCEPTI NG ME AS A US ER? A. YOU MAY HAVE FORGOTTE N THE ID & PASSWORD. YOU ARE ENTE RING INVA LID OR INCORRECT PASSWORD O R YOU MAY CHECK ON THE CAPS LOCK B UTTON TO BE OFF OF THE KEYBOARD. OR ASK THE SYSTEM USER FOR ID & PASSWORD.
108
Conclusion
Todays world is running with a great speed and concept of existence is most important everywhere. In this great struggle of keeping existence, the whole society is in the glorious proceeding just getting COMPUTERIZATION as the only tool. Computerization with its newer and newer solution, has given the modern of great success and victory.
Computerization is a new vision, new challenge to modern world. It is a tools to develop and prosper to a decide level in terms of efficiency and productivity.
Computerization makes the whole business process faster, simple and easy to operate. Now any type of queries and transaction can be done within a fraction of second. There are a lot of scope for modification, cancelling and structured way on maintaining stock management. This process will save lot of time, give satisfaction, ensure effective management and lastly high security. So we have the confidence that the project Stock management and inventory control system will give the complete satisfaction to user as well as to the enterprise.
109
Bibliography
Books referred: Herbert Schildt JAVA 2 complete reference. Website Referred: Wikipedia and Google search on java,jdbc for some help and reference.
110
SIGNATURE
This is to certify that the project entitled Stock management and Inventory Control System has been prepared according to the regulation of degree of Bachelor in Computer Application (BCA) under West Bengal University of Technology (WBUT). The project is being submitted by student of BCA 3rd year 1st semester, George College (Affiliated to WBUT) have fulfilled the requirement for submission of this project. 1. 2. 3. 4. 5. 6. Subhamoy Ghosh (PL) Bipru Thakur (DPL) Sujoy Majumder Nisanta Buxi Debmalya Ghosh Kallol Chakraborty
The whole procedure has been carried out under my supervision. I have gone through the project & have seen that it is fulfilling the requirement of minor project under WBUT.
111
Project Report:
______________________________________
112