6.2.7.2 Use of HTML
If we want to make websites, there is no way around HTML. Even if we are using a program to create websites, such as Dream weaver, a basic knowledge of HTML can make life a lot simpler and our website a lot better. The good news is that HTML is easy to learn and use. HTML is used to make websites.
Hyper is the opposite of linear. In the good old days – when a mouse was something the cat chased – computer programs ran linearly: when the program had executed one action it went to the next line and after that, the next line and so on. But HTML is different – you can go wherever you want and whenever you want. For example, it is not necessary to visit MSN.com before you visit HTML.net.
Text is self-explanatory.
Mark-up is what you do with the text. You are marking up the text the same way you do in a text editing program with headings, bullets and bold text and so on.
Language is what HTML is. It uses many English words.
6.3 Implementation
Implementation means converting a system design into operational form. This phase is divided into 2 parts – database implementation and user interface implementation (code generation).
In the first part, the logical database design was implemented as the physical database design. All the data types were defined properly on each table. The relations among the tables were described by using primary key and foreign key concepts.
The second part was to generate code to insert business data to the database through user interface. This part includes the followings, to create user interfaces to insert, update and search and delete data and to generate different reports for the managements from those data.
6.3.1 Database Design and Table List
Data is the collection of facts which the most important factor in any organization. Data plays the most important role in business activities and day to day events.
Database design is the process of producing a detailed data model of a database. This logical data model contains all the needed logical and physical design choices and physical storage parameters needed to generate a design in a Data Definition Language, which can then be used to create a database.
A fully attributed data model contains detailed attributes for each entity. Now we discuss the database table-
6.3.1.1 Agent Information Table
The table name is agent_info. It contains agent’s information. It has ten data fields. id contains a unique number for every agent. loginId and pass are used for accessing the system.
6.3.1.2 Buyer Information Table
The table name is buyer_info. It contains buyer’s information. It has nine data fields. id contains a unique identification for distinct buyers. loginId and pass are used for accessing the system.
6.3.1.3 Order Information Table
The table name is orderinfo. It contains order’s information. It has seven data fields. orderNo contains a unique identification for every order.
6.3.1.4 Production Information Table
The table name is productioninfo. It contains product’s information. It has nineteen data fields. id contains a unique identification for every product. This table is used by admin/agent. Here agentId and orderNo are foreign keys.
6.3.1.5 Order Status Table
The table name is order_status. It contains order status information. It has six data fields. id contains a unique identification for every order status.
6.3.1.6 Washing Information Table
The table name is wash_info. It contains washing information. It has thirteen data fields.
6.3.1.7 Completed Product Table
The table name is product_detail. It contains product’s detail information. It has eight data fields. iid contains a unique identification for every product.
6.3.1.8 Transaction Information Table
The table name is transactioninfo. It contains transaction’s information. It has five data fields. id contains a unique identification for every transaction.
6.3.1.9 Shipment Information Table
The table name is ship_info. It contains shipment’s information. It has six data fields. shipid contains a unique identification for every shipment. This table is used by admin/agent. Here agentId and orderNo are foreign keys. Other attributes are dateTime, quantity and cost.
6.4 Implemented System
Our implemented system has different web page. Those web pages are used for showing different types of information. There is a page where a report is generated. This report shows daily production report between two dates. Three types of users can access this system. Some pages are described below-
6.4.1 Home Page
Home page used for showing the new and existing product picture and price. A user uses this web page for login. By clicking on the picture of the product we can see the detailed information like buyer information, fabric details, style details. The left side contains the main menu where homepage, buyer, product information, service, contact us and logout.
6.4.2 Buyer Registration Page
Buyer uses this page for his or her registration. Buyer information’s stored into the database table by this web page. Here information about Login id, Password, Full name, Address, Phone No., Email, Fax are entered. To confirm the registration, Register button is used. Without registration, buyer can not access this system.
6.4.3 Admin Information Page
Administrator can use this page to view all production information and production report. Here information about Create New Agent or Admin, Update Top Product, Daily Production Information, Order Status, Washing Information, Transaction Information, Shipping Information, Buyer Order View, Production are linked with different pages. Admin can register new agent or admin.
6.4.4 Daily Production Information
Daily product information’s are stored into the database table using this web page. Here information about Agent Name, Order No, Finished, ThreadCut, SnapButton, Pressing, Folding, PolyPacking, CartonComplete, StartDate, Cutting, Washing, Inspection, RegularHour, OvertimeHour, TotalWorker, NoReject are entered.
6.5 Conclusion
Here we discuss those tools (HTML, PHP, MySQL, Macromedia Dreamwaiver, CSS and Apache Server) which are used for implementing this system. We also discuss the database table and some web pages which are need for implementing this system.
TESTING
7.1 Introduction
Software testing is a critical element of software quality assurance and popular risk management strategy. Here, programmer compares the actual result with required result. Testing is the process to review of the specification, design and coding. In fact, testing is the one-step in the software engineering process that could be viewed as destructive rather than constructive [7].
7.2 Objectives of Software Testing
There are many objectives to test system:
- 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 as-yet undiscovered.
7.3 Testing Principle
To test software effectively, a software engineer must understand the basic principals that guide software testing. The testing principals are as follows:
- All test should be traceable, that is the objectives of testing should be uncovered basis on customer requirements.
- Test should be planned before testing begins.
- An independent third party should conduct test.
- Exhaustive testing is not possible.
7.4 Test Plan
The purpose of test planning is to provide the basis for accomplishing testing in an organized manner. If a test plan is comprehensive and carefully thought out, test execution and analysis should proceed smoothly [7].
A good test plan is one which:
- Has a good chance of detecting a majority of the defects.
- Is flexible.
- Is executed easily, repeatable and automatically.
- Defines the types of test objectives.
- Clearly defines the test objectives.
- Clarifies the test strategy.
- Is not redundant.
- Identifies the risk.
7.5 Execution Test Plan
Team members of the project will prepare the test plan. The following types of testing will be done for Product Management System:
7.5.1 Unit Testing
In computer programming, unit testing is a procedure used to validate that individual unit of source code is working properly. Unit testing is a software development process in which the smallest testable parts of an application, called units, are individually and independently scrutinized for proper operation. Unit testing is often automated but it can also be done manually. This testing mode is a component of Extreme Programming (XP), a pragmatic method of software development that takes a meticulous approach to building a product by means of continual testing and revision [7].
7.5.1.1 Benefit
The goal of unit testing is to isolate each part of the program and show that the individual parts are correct. A unit test provides a strict, written contract that the piece of code must satisfy. As a result, it affords several benefits.
7.5.2 Integration Testing
Integration testing, also known as integration and testing (I&T), is a software development process which program units are combined and tested as groups in multiple ways. Integration testing can expose problems with the interfaces among program components before trouble occurs in real-world program execution. Integration testing is a component of Extreme Programming (XP), a pragmatic method of software development that takes a meticulous approach to building a product by means of continual testing and revision [7].
There are two major ways of carrying out an integration test, called the bottom-up method and the top-down method.
7.5.2.1 Bottom-Up Integration Testing
Bottom-up integration testing begins with unit testing, followed by tests of progressively higher-level combinations of units called modules or builds.
7.5.2. 2 Top-Down Integration Testing
In top-down integration testing, the highest-level modules are tested first and progressively lower-level modules are tested after that. In a comprehensive software development environment, bottom-up testing is usually done first, followed by top-down testing [7].
7.5.3 Validation
The process of evaluating software during or at the end of the development process to determine whether it satisfies specified requirements.
In other words, validation ensures that the product actually meets the user’s needs, and that the specifications were correct in the first place, while verification is ensuring that the product has been built according to the requirements and design specifications. Validation ensures that ‘you built the right thing’ [22].
7.5.4 Verification
The process of evaluating software to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase. Verification ensures that ‘you built it right’ [22].
7.6 Software Quality Assurance
Software testing may be viewed as an important part of the Software Quality Assurance (SQA) process. In SQA, software process specialists and auditors take a broader view on software and its development. They examine and change the software engineering process itself to reduce the amount of faults that end up in defect rate. What constitutes an acceptable defect rate depends on the nature of the software. An arcade video game designed to simulate flying an airplane would presumably have a much higher tolerance for defects than software used to control an actual airliner. Although there are close links with SQA testing departments often exist independently, and there may be no SQA areas in some companies [23].
7.7 Conclusion
Software testing is the process used to measure the quality of developed computer software. A human being can make an error (mistake), which produces a defect (fault, bug) in the code, in software or a system, or in a document. For that region, testing is an important. Different types of testing are used in this project.
Critical ApprAisal
8.1 Introduction
Every system has some limitations or problems. Our systems also have some problems. In this chapter, we discuss those problems.
8.2 Limitation
Problems are everywhere. Normally garments industries are always busy with their work. So our data collection were delayed sometimes due to the business of the garments personnel.
We also have faced problems during the installation of XAMPP. Port no. 80 & 434 should not be busy during the activation of apache server. Also IIS sometimes conflicted with apache.
We found few troubles of designing this project because we are the new developers in the software field. We have also faced some problems during data analysis, database design, data normalization and in the time of making relationships among several tables.
Limitations of our system are listed below-
- IIS is not supported because of some function of PHP do not properly work in IIS server, we must use Apache server for our software.
- If buyer is illegal it’s can’t be verified, that is mail checking system is not used.
- To final an order for production there is needed buyer’s representative.
- This system only maintains the production side.
- Report can not be generated properly if the time format is not matched between database & PHP coding.
8.3 Conclusion
After completion our project, we get some problems. We faced some problems in installing the software, we used in implementation of the system. In the future, we will try to solve those problems.
9.1 Conclusion
There is no doubt that Online Application is most popular and important for all. Now a day, we depend on the Online for everything like job searching, advertising, buying goods etc.
Our proposed system is also online based. In the proposed system maintained full production sector. The combination of HTML, CSS and PHP are used for front end design and MySQL is used for back end. Apache server is used as a server. We think one day this “Online Garments Product Management System” will be a complete solution for the administrators. At first we collect the relevant data from the Opex Group, then we planed, designed architecture, made papers, observed the system and prepared database. Finally, we started the implementation phase and complete the project.
Mainly three kinds of user can access this software. Every user has to be registered first of all. Admin can access the whole system and can generate the production report, which shows the complete and running production information.
All of the users are benefited by the system. The administrator will get the maximum benefit from it. He can take any decision easily and quickly. Better control and security ensures data, reduce manpower, eliminate paper work and increase the efficiency of the daily work.
9.2 Suggested For Future Work
There are further more areas where the application can be developed to support the Opex Group. For example HR system and Accounts system can be developed and integrated with this application to get the better outcome. Different reports can be designed to retrieve data from the database as per the requirements. The requirements of the management changes over the time. So the application also need to upgrade every after certain time. The server side validation was not performed in this application which is mandatory in good programming practice.
Some more parts of this post-
A Report On Garment Industries Bangladesh (Part-1)
