*PROJECT REPORT
ON
Tailoring Management
BY
Abdul Manan (104)*
Contents
DEDICATION 8
DECLARATION 9
Introduction 10
Introduction to C#: 10
Introduction to SQL server: 10
Introduction to our project: 10
Objectives: 11
2.1 EXISTING SYSTEM 11
Drawbacks of Existing System 11
2.1.1.1 Time Consuming 12
Space Consuming 12
Data Security is less 12
No Backup Facility of Data 13
Data Processing is Less 13
Work load on Individual 13
Not Easy to Search Data 13
Difficult to Maintain Data 14
3.1.1 Proposed a new System 14
3.1.2 Objective of the New System 14
3.1.3 Scope of the New System 14
3.1.4 Advantages of the New System 15
3.1.4.1 Less Cost 15
3.1.4.2 Less Time Consuming 15
3.1.4.3 Data Security 15
3.1.4.4 Data Processing 16
3.1.4.5 Dynamic Reports 16
3.1.4.6 Minimum Manpower 16
3.2 Requirement Analysis 16
3.2.1 Software Requirements 17
3.2.2 Hardware Requirements 17
3.2.3 End-User Requirements 17
3.2.4 Feasibility Study 18
3.2.4.1 Economical Feasibility Study 18
3.2.4.2 Technical Feasibility Study 18
3.2.4.3 Legal Feasibility Study 18
4.1 INTRODUCTION 19
4.1.1 Function Analysis and Modeling 19
4.1.2 Introduction Data Flow Diagram 20
4.1.3 Symbol TYPE 20
4.1.4 Types of DFD 20
4.1.4.1 Physical DFD 20
4.1.4.2 Logical DFD 20
4.1.5 Data Flow Diagram 21
4.1.5.1 DFD Level 0 21
DFD LEVEL ‘0’ 21
4.1.5.2 DFD Level 1 21
5.1 INTRODUCTION 23
5.1.1 Data Analysis and Modeling 23
5.1.1.1 DATA OBJECTS/ENTITIES 24
5.1.1.2 ATTRIBUTES 24
5.1.1.3 RELATIONSHIP 24
5.1.1.3.1 Degree of Relationship 24
5.1.1.3.2 Cardinality of Relationship 24
5.1.1.3.3 Modularity Relationship 24
Data Object Description of System/ Attributes of Entities 24
Attributes Of ShopInfo Table 24
5.1.2.2 Attributes of clientInfo Table 25
5.1.2.3 Attributes of login Table 26
5.1.2.4 Attributes of Pemaish Table 27
5.1.2.5 Attributes of Account Table 28
5.1.2.6 Attributes of invoice Table 28
5.1.2.7 Attributes of Order Table 29
5.1.2.9 Attributes of Specification Table 30
5.1.2.9 Attributes of ClothRateTable 31
5.1.3 Entity Relationship Diagram 32
Figure: 5.12 32
6.1 SYSTEM DESIGN 32
6.2 code design 33
6.3 INPUT DESIGN 35
6.3.1 Login 36
Figure 6.3.1 Login 36
6.3.2 User Setting 36
Figure 6.3.2 User Setting 37
6.3.3 Add Users 37
Figure 6.3.3 Adding User 38
6.3.4 Delete User 38
Figure 6.3.4 Deleting User 39
6.3.5 Change Password 39
Figure 6.3.5 Change Password 40
6.3.6 Password Recovery 40
Figure 6.3.6 Recovery Password 41
6.3.7 Main Form 41
Figure: 6.3.7 Main Form 42
6.3.8 Pemaish Form 42
Figure 6.8.1 Pemaish Confirm 43
Figure6.3.8 Pemaish Entry 44
6.3.9 View Pemaish Form 44
Figure 6.3.9a Figure 6.3.9b 45
Figure: 6.3.9c View Pemaish Form 46
6.3.10 Placing Order 46
Figure: 6.3.10 Placing Order Form 47
6.3.11 Order View Form: 47
Figure 6.3.11a 47
Figure 6.3.11b Quick order Retrieve Button 48
Figure: 6.3.11c Order View Form 48
Figure 6.3.11d Order Navigation 48
6.3.12 Invoice Form: 48
Figure: 6.3.12a Invoice default 49
Figure 6.3.12b invoice full payment Details 50
6.3.13 Shop Info Form 50
Figure: 6.3.13 Shop Info Form 50
6.4 OUT PUT DESIGN 50
6.4.1 Pemaish Report: 51
Figure: 6.4.1 51
6.4.2 Order Report: 51
Figure: 6.4.2 Order Print 52
6.4.3 Invoice Report: 52
Figure: 6.4.3 Invoice Report 53
7.1 Introduction 53
7.1.1 Software Development Process 53
7.1.1.1 Coding 53
7.1.1.2 Debugging 54
7.1.1.3 Testing 54
7.1.1.3.1 STEPS IN TESTING 54
a. Unit Testing 55
b. Integrated Testing 55
c. Sub System and System Testing 55
e. Black Box and White Box Testing 56
f. Stress Testing 56
7.1.1.3.2 TESTING STRATEGY 56
a. Code Testing 57
b. Specification Testing 57
7.1.2 SYSTEM EVALUATION 57
7.1.3 MERITS OF THE PROPOSED SYSTEM 57
7.1.3.1 Time Saving 58
7.1.3.2 Efficiency 58
7.1.3.3 Reliability 58
7.1.3.4 Accuracy 58
7.1.3.5 Usability 58
8.1 Introduction 59
8.1.1 Implementation Strategy 59
8.1.1.1 Proposed System Requirement 59
8.1.1.2 Language Selection 60
a) SQL Server 2008 60
b) C# 60
8.1.2 System Implementation 60
8.1.2.1 User Training 61
8.1.2.2 Change Over 61
a. Direct Approach 61
Advantages of Direct Conversion 61
b. Parallel Approach 61
c. Pilot Approach 61
Advantages of Pilot Conversion 61
8.1.2.3 Proposed Change Over 62
I begin with the name of Allah who is very gracious, most merciful and the mighty of all and with the name of his Prophet Hazrat Muhammad Sallallah-o-Alihe Wasallam, in the name of whom Allah bestowed me the thought, power, strength and health to complete this difficult task. This task stayed difficult yet without his guidance.
I would have not finished this report without the support of my parents, brothers and other family members who are always been there for me whenever I need them, the encouragement they give to keep me going and their love to empower me that never fails all the time.
I would also like to thank my supervisor Mr. Sadiq Shah, who has given me a chance to prove that I can do things on my own. He gave me a lot of positive perspective in this research. He has taught me things far more than my understanding. I thank him for suggesting and supporting me to do this research report. To you sir, I give you lots of thanks and respect.
At last, I would like to thank my colleagues and my friend who are very special to me. They help me building my character. I thank all of them from core of my heart of their help and support. I would have been far behind in life without their love and support. They are always with me and stand beside me whenever I need them. Thank You All Guys.
Abdul Manan
Abdul Maqsood
DEDICATION
“Dedication is not what others expect of you, it is what you give to others”
It is dedicated to an honorable Men and our national hero Dr. Abdul Qadeer Khan, who made Pakistan as first Muslim nuclear power, my loving parents, my brothers, my family members, my friends without whom I’m incomplete and most important to my country my Pakistan, who made my identity and made me able to lead my life of my own.
DECLARATION
We hereby declare that this software is neither as whole nor as a part has been copied out from any source. It is further declared that we have developed this software and accompanied report entirely on the basis of our personal efforts, under the sincere guidance of our supervisor. If any part of this software is proved to be copied out from any source or found to reproduction of someone else, we shall stand by the consequences.
Abdul Manan
Signature
Abdul Maqsood
_
Signature
Introduction
Introduction to C#:
During the development of the .NET Framework, the class libraries were originally written using a managed code compiler system called Simple Managed C (SMC). In January 1999, Anders Hejlsberg formed a team to build a new language at the time called Cool, which stood for "C-like Object Oriented Language". Microsoft had considered keeping the name "Cool" as the final name of the language, but chose not to do so for trademark reasons. By the time the .NET project was publicly announced at the July 2000 Professional Developers Conference, the language had been renamed C#, and the class libraries and ASP.NET runtime had been ported to C#.
Introduction to SQL server:
Microsoft SQL Server is a relational database management system developed by Microsoft. As a database, it is a software product whose primary function is to store and retrieve data as requested by other software applications, be it those on the same computer or those running on another computer across a network (including the Internet). There are at least a dozen different editions of Microsoft SQL Server aimed at different audiences and for workloads ranging from small single-machine applications to large Internet-facing applications with many concurrent users. Its primary query languages are T-SQL and ANSI SQL.
Introduction to our project:
In our project we use C# for the front end and SQL Server for databases.We make this software for Tailors Community in Pakistan. This software is Generic means this is not for a specific tailor. It can be used by all Tailors in the market. We tried our best to make it easy and friendly because in our society mostly peoples are illiterate and they can’t understand the English. Therefore mostly we use the regional words in our project. In market we visit many places and see there software which they are using currently for the data storage. These all are very complicated to understand. For that kind of software you have to hire a Technical person to operate that. Therefor we make such kind of interface that everyone can use it easily even a non-technical person can use it when properly trained, we make all the security checks on the software which a software have for their strong security.
Objectives:
Being An IT Students Our Aim is to Make People Life Easy through Latest Technologies,
And to Apply the Skill we have Learn So For.
Now Days New Technologies are Coming day by day and Life Style is Changing with time to time, and Why Not If change is improvement then it is Appreciated Almost Every Professional Field adopts new technologies with time ,
If it so then why not Tailor Community adopt new Technology and take benefit of it and get rid of Traditional Approach that they are using For Many Years,
Therefore we Come Across to provide them a Software to done their daily work operations easy and fast.
Doing a Brief Survey we came Across to Have a Software for Tailor Community to help them solve their Daily Work Problems easy and fast.
Smart Tailoring Management System (STMS) is Fully Functional Software Design for Tailors in KPK,
It Provide All Features That an Ordinary Tailoring Want to have to Full Fill Daily basis Work (Like Taking Measurements Placing Orders Printing Invoice) Easy and Fast, Because STMS is Design the Way that a Person Having very less and basic Knowledge of Computer Can easily Operate.
STMS Store Data about Client Cloth Measurement Once the Data Stored , then it Easy to Use for Further Operations Like Placing Order of Cloths and So On Through very Friendly User Interface That a STMS Provided.
2.1 EXISTING SYSTEM
The Existing system of the Tailoring Community is totally work on manual basis. All type of data is stored using papers and big size registers and it is very difficult to manage the data. This entire job is time and space consuming. Therefore after studying some type of difficulties and analyzing current system super store management agrees to replace the current system with new computerized system.
Drawbacks of Existing System
Following are the major drawbacks of the existing system
Time Consuming
Space Consuming
Data Security is less
No Backup Facility of data
Data processing is less
Work load increases on individual
Not easy to find Specific data
Difficult to Maintain data
Difficult to Update Record
Repetition of data
Data Redundancy
Not easy to find specific record
2.1.1.1 Time Consuming
The existing manual system is time consuming because it requires much time to search, add, update and delete record. The major drawback of this system comes in front when staff has to search some specific record on user requirement. It requires lot of time to search specific record from bundle of papers and registers. The newly proposed system solves this problem and time consumption become reduces for both student and employee.
Space Consuming
As in manual system all the record maintain using files and registers which require a lot of space to be placed. Also after 2 or 3 years it is difficult to save data at one place.
Data Security is less
As data saved in form of registers and files, it is difficult to make data security foolproof, also there is chance of misuse or misplace of any file or register. The security problems arise when there is fear that data can be used for some bad purpose because data security is much difficult when data entered on papers and make files to save data. The newly created software gives strong security and dominant all of above discussed problems.
No Backup Facility of Data
In manual system it is not possible to maintain data at more than one place, so backup facility is not given in manual system which increase the chance that if any record is misplaced it will not recover. If a Client wants to make data backup manually the financial expenditure become double and also data accuracy disturbed while making backup. So such a system is needed where backup can be made easily and data accuracy should be maintained, so newly developed system give facility of making backup and maintain data security strongly.
Data Processing is Less
In manual system data processing such as to add, delete, update or view record is not much easy and some time it become impossible. While processing a big problem is to collect whole data and to place it at one place and use it when needed. The new system will provide all these facilities to client in terms of cost, security and maintenance.
Work load on Individual
In manual system individual has to maintain many records individually which increase the burden of work on one person and also chances of errors and mistakes become increases.
In manual system when an individual has to perform more than one job such as to enter record, to collect other record and to maintain data than error chances become increase which may cause much problems in future, the new system will decrease error chances and decreases problems very much.
Not Easy to Search Data
In manual system data search of a specific Record is not ease to search. If data is stored in files and papers then to search specific record after gap of time become impossible for client.
Difficult to Maintain Data
In manual system environment data maintenance is much difficult for client, data may loss and can misuse by someone. To avoid this entire situation we developed new system where data maintenance is maximum and secure etc.
3.1.1 Proposed a new System
The new proposed system is computerized to overcome the existing System’s draw-backs. In proposed system electronic data processing methods are used to make system more efficient, more economical and error free.
3.1.2 Objective of the New System
Following objectives are required for the proposed system
The new system should less time consuming and more efficient.
It should provide maximum flexibility to handle any type of changes.
It should eliminate paper work to some extend.
It should provide maximum security to user.
The data stored should be consistent and error free.
The system should be user friendly and reliable.
It requires less resource to develop and update.
Repetition of data should be eliminated.
Data should be retrieved and update easily.
Certain checks are applied to avoid errors and mistakes.
3.1.3 Scope of the New System
The system can be used in central command environment where a single person can use the system and work as administrator. Administrator can perform the following action.
Admin can perform Data Manipulation Language (insert, update, delete) on all records.
Admin can perform Data retrieval Language (select) on all records.
Admin can perform Data control (transaction control) Language on all records.
3.1.4 Advantages of the New System
The proposed system has following major advantages which made it able to accept by Store management.
Less cost
Less time consuming
More efficient
Easy to use
More reliable
Increase data security
Easy to view record
Easy to update record
Data retrieved easily and fast
Give Backup facility
Provide facility of Dynamic Reports
Minimize need of manpower
Cost effective
3.1.4.1 Less Cost
The system should be less cost. It means it required a reasonable amount to develop and also need less amount when need to update, delete, search, add record. In existing system when user want to add record he/she has require stationery products like paper, pencil etc each day in big amount and this cost increases after a month or year, also when user want to update or delete some record then to search that record is difficult and after searching to update that record is totally impossible on same page and location. User requires new page or register to write newly updated record
3.1.4.2 Less Time Consuming
Less time consuming means that system require less time to load and require less time to made any transaction effectively .When user want to get long time ago record. It becomes very difficult and sometime impossible to fulfill his/her requirement. The newly created system gives the facility to search record on one click and save lot of time.
3.1.4.3 Data Security
The system should be secure .It means that data which is placed in database should be secure and avoid it from unauthorized use.
In manual system it is much difficult to save record of any person from unfair use and from environmental factors. The data may loss after one or two years. In newly created system there is lot of security from unfair use and from environmental factors. It is easy to save data for many years unless you want to save it.
3.1.4.4 Data Processing
Data processing should be consistent and reliable. It means that data can be viewed, update, delete, search and fetched easily.
In manual system we already discussed that it is not easy to add, delete, update and save record. Also when to search some record it become very difficult but proposed system gives all these facilities in no time and data processing become easy and speedy.
3.1.4.5 Dynamic Reports
Dynamic Reports feature gives the facility to generate, to view different types of data at runtime and on demand.
In manual system it is not much easy to see whole data of any entity at one time. If user want complete report of an entity he/she has to collect data from many places and register to make report. The newly created system gives the facility to get dynamic reports from where we get data and make Client Cloth Measurement, invoice or Order report with minimum time use.
3.1.4.6 Minimum Manpower
This System is Design for Single Person Means There One Person can Easily Operate, so there is No need to keep two or three Operator for this system to use.
3.2 Requirement Analysis
The requirement analysis based on following perspective
Software Requirement
Hardware Requirement
End-User Requirement
3.2.1 Software Requirements
The software requirement includes those requirements which are needed to develop specific application. The software required for the development of Smart Tailoring Management System software is as follows.
Window 7 / Other usual operating system
Microsoft SQL Server 2008 For Data Store
Visual Studio 2010 For Interface Design
C# For Programming the logic
MS word and MS Paint for documentation
3.2.2 Hardware Requirements
The hardware required to develop and run the specific application are as
Following.
Processor 1 GHZ minimum OR HIGHER
Ram 256MB Minimum
Minimum of 20 GB hard disk Space needed
3.2.3 End-User Requirements
Those requirements which are needed by end-user. End-user is such a Person who finally used the software. According to the Smart Tailoring Management requirements, the requirements for end-user are set as follow.
The System should Store Data about Client Cloth Measurement.
And some of the Client Bio Data to Make Search easy when needed
like CNIC, Mobile Phone No. , Name Address etc.
User-friendly Interface
Easy to use software
Can access the system completely Efficient
Terms Used in interface is user-friendly
3.2.4 Feasibility Study
Feasibility study is carried out to find whether project is feasible or not. In feasibility study developer checks whether project is feasible and fulfill the requirement of end-user. The following feasibility studies were carried out
Economical feasibility Study
Technical feasibility Study
Legal feasibility Study
3.2.4.1 Economical Feasibility Study
After estimating all the hardware and software requirement of the required application, the project is quite feasible and required amount of finance is available for the application.
3.2.4.2 Technical Feasibility Study
System meets all the technical requirements, run under specified hardware and software specification. It has no technical fault and compatible with different type of hardware and software.
3.2.4.3 Legal Feasibility Study
The tools used for the project are totally legal and are authorized to use for the specific tool.
4.1 INTRODUCTION
Chapter 3 discussed the working of proposed system in detail. This chapter is focused on the Functional Analysis and Molding. Here the system accepts inputs in variety of forms from external world, Applies h/w, s/w and human elements to transformed inputs to outputs, Produces outputs in a variety of forms to external world and DFD is graphical description of flow model requirements are determined for Functional Analysis And Molding. .
4.1.1 Function Analysis and Modeling
It is focuses on defining the main function of the system and then it’s
Detailed Functionality. The deliverable from functional analysis is DFD and the flow model is discussed as information is transformed as it flows through computer Based system
The system accepts inputs in variety of forms from external world.
Applies h/w, s/w and human elements to transformed inputs to outputs.
Produces outputs in a variety of forms to external world.
DFD is graphical description of flow model.
4.1.2 Introduction Data Flow Diagram
DFD is a graphical representation of flow model. It can represent a system at any level of abstraction. In fact DFD can be portioned into level that represents information flow and functional details. It provides both the functional and information flow model of a system. It therefore can be used to process modeling for the system.
4.1.3 Symbol TYPE
Process/transformed
Data store
Data flow
External Entity
4.1.4 Types of DFD
There are two types of Data Flow Diagram.
Physical DFD
Logical DFD
The definitions of logical and physical DFD’s of the system are described in the proceeding sections
4.1.4.1 Physical DFD
That type of DFD, which depicts the actual functions performed in that this is the blue print of already existing manual system.
4.1.4.2 Logical DFD
Manual system. This type DFD also contains such process which may not implemented in case of computer based system, so we may say a logical DFD shows the flow of information through the software system. It contains circles each of which shows a process in the software. The circles (processes) are connected with each other with the help of directed edges. The edges are assigned label which shows either the flow of data or control between software modules. Logical DFD serves as a guide for the programmer to design the software.
4.1.5 Data Flow Diagram
Data flow diagram is also called DFD. It is used to show the flow of information in form of diagram. The process shown by circle and different processes connect to each other by arrows. The direction of arrow show the direction of flow of information.
DFD is also called “Bubble Chart”. There are two types of DFD.
1. DFD Level 0
2. DFD Level 1
4.1.5.1 DFD Level 0
Zero Level DFD is also called context model, because it represents the entire software element as a single bubble indicated by incoming and outgoing arrows. Zero level describes the flow of data in application.
DFD LEVEL ‘0’
4.1.5.2 DFD Level 1
DFD is divided to further parts to describe each process briefly. At level one there is more than one bubble.
5.1 INTRODUCTION
Chapter 4 discussed the working of the DFD’s in detail. This chapter is focused on the data analysis and modeling. Here the Data objects/entities, Attributes of data objects and Relationships between data objects are determined for the data analysis and modeling.
5.1.1 Data Analysis and Modeling
It is the first activity in the analysis model. The following things are determined precisely in data analysis and modeling.
Data objects/entities
Attributes of data objects
Relationships between data objects
ERD is created from these three discussed above which is the graphical Representation of data analysis and modeling.
5.1.1.1 DATA OBJECTS/ENTITIES
Anything which have some properties (attributes) is called data object .The DOD incorporates the data object and all of its attributes.
5.1.1.2 ATTRIBUTES
Attributes are the properties of an object e.g., name of a candidate is an attributes of a candidate.
5.1.1.3 RELATIONSHIP
Relationship is a logical association between entity types. There are required for relationship.
Degree of Relationship
Cardinality of a Relationship
Modality of Relationship
5.1.1.3.1 Degree of Relationship
Degree shows that how many entity are participating in a relationship.
5.1.1.3.2 Cardinality of Relationship
Cardinality of a relationship shows that how many instances of one entity related to how many instances of other entity.
5.1.1.3.3 Modularity Relationship
Modality of relationship shows that either the relationship is mandatory or optional.
Data Object Description of System/ Attributes of Entities
Attributes Of ShopInfo Table
Figure: 5.1
5.1.2.2 Attributes of clientInfo Table
Figure: 5.2
5.1.2.3 Attributes of login Table
Figure: 5.3
5.1.2.4 Attributes of Pemaish Table
Figure: 5.4
5.1.2.5 Attributes of Account Table
Figure: 5.5
5.1.2.6 Attributes of invoice Table
Figure: 5.6
5.1.2.7 Attributes of Order Table
Figure: 5.7
5.1.2.9 Attributes of Specification Table
Figure: 5.9
5.1.2.9 Attributes of ClothRateTable
5.1.3 Entity Relationship Diagram
Figure: 5.12
6.1 SYSTEM DESIGN
System DESIGN is the process of defining the architecture, components, modules, interfaces, and data for a system to satisfy requirements. One could see it as the application of system theory to product development. there is some overlap with disciplines of system analysis, system architecture and system engineering if the broader topic of the product development” blends the perspective of marketing ,design ,and manufacturing into a single approach to the product development ,then design is the act of taking marketing information and creating the design of the product to be manufactured .system design is therefore the process of defining and developing system to satisfy specified requirements of the user .until the 1990s system design had crucial and respected rule in the data process industry .in the 1990s standardization of hardware and software resulted in the ability to build modular system .the increasing importance of software running on generic platforms has enhanced the discipline of software engineering.
Object-oriented analysis and design methods are becoming the most widely used methods for computer system design .the UML has become the standard language in object-oriented analysis and design .it is widely used for modeling software system and is increasingly used for high designing non-software systems and organization. System design is perhaps the most difficult of all phases because the proposed system is actually designed keeping in view the user and system requirements. System design presents specific information on design of input .output and file structure.
6.2 code design
A code can be defined as an abbreviation of the actual data, which occupies little space. Code play a vital role in entering correct data in short time .while accessing information the codes ate decoded within the program and the decoded information are displayed on the output device.
Login Table:
To log in the soft wear
Id Int
Username Varchar
Pass Varchar
Passtips Varchar
Question Varchar
Answer Varchar
Client info Table:
Client id Int
Name Varchar
Mobile Varchar
Address Varchar
Cnic Varchar
City Varchar
Invoice Table:
Invoice Id Int
Order Id Int
Client Id Int
Trasdate datetime
Order Table:
Order Id Int
Client Id Int
Currentdate date
Deliverydate date
Day to return Int
Numbers of clothes Int
Odrstatus Varchar
Pemaish Table:
Client Id Int
Pid Float
Lambi Float
Chatti Float
Tera Float
Collor Float
Asteen Float
Daman Float
Shalwar Float
Pancha Float
Setting Table:
Setid Int
Cloth rate Varchar
Specification Table:
Specification Id Int
Orderid Int
Doublesalai bit
Singlesalai bit
Ampatti bit
Doubledagga bit
Panjkaj bit
Waskatbtn bit
Vgalla bit
Collar bit
Side-jaib bit
Aambend bit
Halfbend bit
Kurta bit
Golkaf bit
Sadakaf bit
Sadapatti bit
Samny-jaib bit
Shalwarjaib bit
Sadaasteen bit
Others Varchar
Account Table:
Account Int
Clientid Int
Ordered Int
Total amount Int
Amountrece Int
Amountbal Int
Trandate datetime
Paid nvarchar
6.3 INPUT DESIGN
The data given to computer from external source is known as input and the manner in which it is given to computer is known as input design. A lot of care is required this step to consequence is wrong reports.
6.3.1 Login
When the System Start Login Form is Loaded, The User have to Provide Username and Password in Order to authenticate himself For Accessing the Application.
Figure 6.3.1 Login
6.3.2 User Setting
Down Right Side of Login Form there is a Link that would take you to User Setting
that Give you Complete Control Regarding Users. But you have to
Enter Admin Password First.
You can Add, Delete and Update Password as well as Recover Forgotten Password.
Figure 6.3.2 User Setting
6.3.3 Add Users
Admin Can Add User to the System.
We have the following field in Add user Tab of Setting.
a. User Name
b. Password
c. Confirm Password
d. Password Tip
e. Question Selection (To Recover Password When Forgot)
f. Answer
Figure 6.3.3 Adding User
6.3.4 Delete User
To Delete a User you have to first Provide Admin Password then Desire User
The relevant Password.
We have the following field in Delete Tab of User Setting form.
a. User Name to Delete
b. Concern Password
Figure 6.3.4 Deleting User
6.3.5 Change Password
To change Password you have to Provide User Name and Old Password,
Then you have to provide the Following Field.
a. New Password
b. Confirm Password
c. Question
d. Answer
Figure 6.3.5 Change Password
6.3.6 Password Recovery
To Recover Password User Must First Provide His Recovery Question (The Question Asked on Time of Creation of User).
Now Answer the Question Correctly and Accordingly.
Figure 6.3.6 Recovery Password
6.3.7 Main Form
Main form is used for access information about STMS. This is the main form of our project for Smart Tailoring management system. In this form links are being created so that we can easily move from this form to any other form where we want to go
a. User Login/Logout
b. Enter Pemaish
c. View Pemaish
d. Place Order
e. Retrieve Order
f. Quick Customer Search
g. Setting
h. Work Progress
i. Delivery
j. Shop Information
And all the reports and user management buttons are place on the main form.
Figure: 6.3.7 Main Form
6.3.8 Pemaish Form
This is Cloth Measurement (Pemaish) Entry Form Here User have to enter Pemaish of Customer.
We have the following field in class info form.
a. ID
b. Name
c. Mobile#
d. Address
e. City
f. CNIC #
g. Lambai
h. Chatti
i. Tera
j. Collar
k. Daman
l. Asteen
m. Shalwar
n. Pancha
o. Mura
p. Kandha
When all data entry process complete user have to press either ctrl+s short keys or directly from file menu option to save the record.
Before saving record the client has been provided with a Pemaish confirm form (Figure 6.8.1) because Pemaish is important data user must be careful to enter data.
Figure 6.8.1 Pemaish Confirm
Edit Button Will Enable form for Editing in case of any Data Entry Mistake
Save button will only save the record.
Where save and order Perform two action first it save the record then bring Place order Form.
Figure6.3.8 Pemaish Entry
6.3.9 View Pemaish Form
This form is used to Retrieve Store Pemaish of Existing Customer.
In Order to View Pemaish First Client must give a Search key either in Quick Search Figure 6.3.9a or Customer Search Popup figure 6.3.9b.
Figure 6.3.9a Figure 6.3.9b
Figure: 6.3.9c View Pemaish Form
6.3.10 Placing Order
By Provide Customer ID You can Place an Order for Customer,
This Form can be Access from Pemaish View (menu) Form as well As from Quick Button from Main Form.
a. Customer Id, Name, Mobile#, CNIC
b. Order Date (it Pick Automatic from System Date)
c. Days to Return
d. Delivery Date
e. Number of Cloth
f. Total Amount
g. Payment Type
h. Amount Received
i. Amount Balance
And Order Specification Detail at Right Side.
All you have to Just Provide Customer ID at the Top to Pick a Customer.
Figure: 6.3.10 Placing Order Form
6.3.11 Order View Form:
This form contains information about Order. You can Delete Order, Update Customer Pemaish from File Menu of Order View Form.
In Order to Retrieve Order you have to provide a Search key in Order Search Dialogue box (figure 6.3.11a) or Direct from Main Menu Undone Task Data Grid (figure 6.3.11b).you can Search an Order by:
1. ID
2. Name
3. Mobile number
4. CNIC
Figure 6.3.11a
Figure 6.3.11b Quick order Retrieve Button
Figure: 6.3.11c Order View Form
Once you Retrieve Order You Can Switch between Orders from Main Order View Form (Figure 6.3.11d)
Figure 6.3.11d Order Navigation
6.3.12 Invoice Form:
This form Provide Detail about Invoice by Default this form Provide two Buttons and Two Link,
Button Paid Will Transect Full Invoice No Due Left.
Button Not Fully Paid is for Half or not full Payment Transaction.
Link Click Here if not done is to Return It to Undone Task Data grid in case of Mistake
Show all Dues Link Provide Pervious Dues figure 6.3.12.1
Figure: 6.3.12a Invoice default
Figure 6.3.12b invoice full payment Details
6.3.13 Shop Info Form
This form Provide Shop Information.
It has the following fields:
a. Shop Name
b. Owner Name
c. Phone
d. Address
You can also set Per Suit Rate at the right side which is later used by the system.
Figure: 6.3.13 Shop Info Form
6.4 OUT PUT DESIGN
We have following Reports for output Design:
6.4.1 Pemaish Report:
This report gives information of Client Pemaish
Figure: 6.4.1
6.4.2 Order Report:
This report gives information of Order.
Figure: 6.4.2 Order Print
6.4.3 Invoice Report:
This report gives information of Invoice.
Figure: 6.4.3 Invoice Report
7.1 Introduction
This chapter is focused on the Testing and Debugging of the proposed system. Here the Coding, Debugging and Testing requirements are determined for the proposed system.
7.1.1 Software Development Process
After the completion of all steps including design, database creation and language selection, actual software development process starts.
This step includes following stages:
1. Coding
2. Debugging
3. Testing
7.1.1.1 Coding
For coding phase we choose C# and MS SQL Server 2008 for database creation where for designing interface we chosen Visual Studio 2010. In coding phase the developer gives lot of facilities while coding. It gives many built-in functions such as built-in triggers, event, procedure to run any function, facility of attach libraries where we can use same code in many place without writing it again and protect us from coping and pasting again and again.
7.1.1.2 Debugging
The tool selected for software development includes the facility of automatic debugging during compilation of code. While writing new code, functions, procedure, Alerts and other function such as adding, deleting and updating database table, debugging facility help us to avoid writing error code and malfunctions. So developer strong capability of debugging facility helps us to perform work in correct way.
Debugging is the process of removing errors from the software. Although debugging can and should be orderly process. The Debugging process begins with execution of test case. Results are assessed and a lack of corresponding between expected and actual performance encountered. In our debugging process several different errors were produced, those were successful.
7.1.1.3 Testing
System testing is an essential step for the development of a reliable and error free System. Testing is the process of executing a program with the explicit intention of finding errors i.e. making the program fail and test cases are devised with the purpose in mind. A test is set of data items that the system processes as normal input. A successful test is the one that finds errors.
The testing is considered as the backbone of software development .It is very important to check the software against different errors and Requirements.
Two main schemes of testing are followed
1. Static Testing
2. Dynamic Testing
7.1.1.3.1 STEPS IN TESTING
Different steps involved in testing phase to check errors, malfunctioning and requirements. The steps for software testing are as follow:
a. Unit Testing
b. Integrated Testing
c. Sub system and system Testing
d. Black Box and White Box Testing
e. Stress Testing
a. Unit Testing
Unit Testing is carried out to check developed software independently. In this step each module in developed system is tested one by one to find errors and to check its proper functioning.
The main advantage of this system is that we can check each module independently for any errors and correct these errors at first time. Also in this step we check that if there is any mistake in one module than it will not effect the other module.
We perform unit testing for our developed software and find no errors and each module in system works correctly.
b. Integrated Testing
In this step of testing, we test all module of the developed system simultaneously to check whether all modules are performing correctly while interacting with each other as well as required form launched when we call it.
We perform integrated testing for our system and found that all forms or block which are interlinked to each other are working correctly and required form call at any press.
c. Sub System and System Testing
In this step of testing we take multiple modules and start testing that whether they perform correct function while interacting to each other.
In this step it is seen that which type of error occur as compare to given requirements in analysis and design phase.
Two kinds of system testing are done
1. Functional Testing
2. Performance Testing
e. Black Box and White Box Testing
White-box testing also called glass-box testing that uses the control structure of the procedural design to derive test cases. Using white-box testing methods, the software engineer can derive test cases that grantee all independent paths within a module have been exercised at least once, execute all loops at their boundaries bounds, and exercise internal data structure to ensure their validity.
Black-box testing is also called behavioral testing that focuses on the functional requirements of the software. Black-box testing enables the software engineer to derive sets of input conditions that fully exercise all functional requirements for a program. It is a complementary approach that is likely to uncover a different class of errors than white-box methods.
Black-box testing attempt to find errors in following categories
1. Incorrect or missing functions
2. Interface errors
3. Errors in data structures or external data base access
4. Behavior or performance errors
5. Initialization and termination errors
f. Stress Testing
Stress testing executes a system in a manner that that demands resources in abnormal quantity, frequency, or volume.
A validation of stress testing is a technique called sensitivity testing. In some situation, a very small range of data contained may cause extreme and even erroneous processing or profound performance degradation. Sensitivity testing attempts to uncover data combination within valid input classes that may cause instability or improper processing.
7.1.1.3.2 TESTING STRATEGY
Two basic Testing Strategies are as follow
a. Code testing
b. Specification Testing
a. Code Testing
The code testing includes finding of errors, malfunctioning and mistakes. The logic of the program was tested using front page debugger environment. Code testing is most important step in software development because if there is error in coding than whole software work incorrectly.
b. Specification Testing
Specification Testing is conducted to check various conditions, to test the range of values expected including both valid and invalid data. It helps in finding discrepancies between the system and its original objective, current specification and system documentation. During testing phase, all efforts were made to remove programming bugs and minor design faults.
7.1.2 SYSTEM EVALUATION
After all testing steps system is evaluated against its actual requirement and find that all the function define in the software are performing correctly which complete our task to develop school software.
The system evaluation steps cleared that system which is developed for specific purpose fulfill its functionality in all terms including data entry, data deletion, data updation, also system evaluation proved that system can be modified with respect to future needs.
7.1.3 MERITS OF THE PROPOSED SYSTEM
After checking the new developed system by all means we find following some important merits in software:
1. Time Saving
2. Efficiency
3. Reliability
4. Accuracy
5. Use-ability
7.1.3.1 Time Saving
When we have test our system against its requirement it has been proved that the system saved a lot of time during adding data.
7.1.3.2 Efficiency
When data is entered, deleted, updated and retrieved using the developed system. We found that the system is working efficiently and correctly.
The software efficiency have been checked by finding some specific records from number of saved records. Its searching ability makes the system efficient and easy to use.
7.1.3.3 Reliability
The results produced by the new system are reliable and make data handling easy. It is confirmed that the system is working properly and at the time.
The system has less cost, its maintenance, data accuracy and data updation facilities makes it reliable to use by Tailors Community.
7.1.3.4 Accuracy
In the new developed system different validation checks are applied to make data accuracy possible and software show that it accuracy is maximum to meet requirement.
The data accuracy can be checked from other ways as well including data entry, its pupation, deletion, searching and when we want to make database backup.
7.1.3.5 Usability
The new developed system is easy to use and handle. A person who knows a little about computer can run the software easily and in correct manner.
The new system will provide assistance to new user who knows little about this software and guide new user through the system.
8.1 Introduction
This chapter is focused on the Implementation and Maintenance of the proposed system. Here the Proposed system Requirement and Language Selection are determined for the proposed system.
8.1.1 Implementation Strategy
According to initial study and design phase, we have to decide about the implementation strategy which includes application type, Language selection and proposed system requirements
1. Proposed system Requirement
2. Language Selection
8.1.1.1 Proposed System Requirement
According to the system requirement and end-user requirement, we have to select such tools which make such an interface that is user-friendly and helps to achieve the required goal.
The main requirement of user is that we make such software for their organization which provide maximum security, easy to operate, modifiable according to new needs, so we analyze many software development tools and found MS Visual Studio and SQL Server 2008 fulfill requirement fully so we choose that tool to make this system.
8.1.1.2 Language Selection
The selection of most suitable tool is important step in software development. So, such a language is chosen which is user friendly and platform independent.
We chose C# the For Coding Which is Advance and User Friendly.
a) SQL Server 2008
SQL Server is most frequently tool used to develop database application because it gives a lot of security to end-user and also it is user-friendly. SQL Server includes built-in tools which help much to develop application easily and it is most powerful tool Used to create database which maintain data accuracy and give high level of security. Each table made in database is referred as an entity. User can add, delete, and update data in SQL Server
b) C#
One of the most powerful and dominant feature of C# is that it Provide high level of security and data accuracy while Coding when user work in central or single user environment,
it’s Powerful Object Oriented Features Give it More Flexibity and Functionality.
8.1.2 System Implementation
Implementation is the final step towards the develop system. Those activities, which convert the old system to new one, are included Implementation. There may exist confusion to some extent, between these two Terminologies, conversion and implementation. Conversion is referred to as the significant and ardent relationship between old system and new one whereas the practical job of putting a theoretically designed system into practice is signified as implementation.
Implementation project involves the activities like planning and scheduling of implementation process, organizational planning and personnel administration, final system design and testing, establishment of old to new system. The most important and considerable process of implementation includes testing the system and conversion plan.
This phase starts with the acceptance of tested design to its satisfactory operation. After developing the software of “SMART TAILORING MANAGEMENT SYSTEM”, I wish to implement it.
8.1.2.1 User Training
Good systems fail due to improper use or if the users are not well trained. For the successful operation of the system, its entire user should set a proper training. For this purpose all the staff members of the training section were briefed about the working of new system. Moreover, one operation was given an opportunity to have a closer look at the operations and functions of new system.
8.1.2.2 Change Over
The testing system may be implemented using one of the following methods.
a. Direct Approach
b. Parallel Approach
c. Pilot Approach
a. Direct Approach
In this method, the old system is absolutely discarded. In this method of conversion a complete new system is introduced without any reference to the previous system. In case of failure of the new system the entire working system of organization may collapse.
Advantages of Direct Conversion
The chief advantage of this approach is the cost consideration as one system is dropped and the other is started, thus reducing the expenditures on payments to the working staff. No backup or temporary system cost is involved.
b. Parallel Approach
In this type of conversion, both the new and old systems are adopted concurrently for a specific period. Both the old and the new system process the current data simultaneously in order to check the results. When the organization if fully satisfied that the new system is providing the desired results. The old system is then entirely converted to the new system.
Advantages of Parallel Conversion
The old system is available as a back up in the event of the failure of the new system. The results obtained by the new system can be compared with the output of the old one. Changes and adjustments can be made with great ease.
User personnel can have time to become completely familiar with the new system.
c. Pilot Approach
In this method a working version of the system is implemented in one portion of organization, such as single work area or department.
This approach has the advantage of proving the correctness before full implementation of new system.
Advantages of Pilot Conversion
Failure of subsystem is not so harmful to remove its defects and recovery does not involve the change of the whole system.The outputs of the implemented sub systems are utilized before full system implementation.
8.1.2.3 Proposed Change Over
All the conversion methods have been considered. After through analysis, Parallel Conversion is recommended. The significant objections against the parallel conversion are the cost and additional workload.
However, the real advantage of this system is that in case of its failure, data is not lost because the old system still runs without any interruption. So the organizational work will not be affected.
The parallel method involves containing the former system for a certain period after the new system is put into operation. It will provide an opportunity to compare its results with those obtained by the previous method.
Both the direct and pilot conversion is not suitable for the proposed system, because for pilot conversion, the proposed system is not so vast as to fulfill the requirements of conversion approach. In case of parallel conversion, the old system will be available as a back up and the results produced can be compared to those of the old one.