SHRI G.S.

INSTITUTE OF TECHNOLOGY & SCIENCE

(AN AUTONOMOUS INSTITUTION ESTABLISHED IN 1952)

DEPARTMENT OF COMPUTER ENGINEERING

A PORJECT REPORT ON

CLOTHES SHOP MANAGEMENT SYSTEM

submitted to
Miss Sonika Tiwary (Lecturer) (Dept. of comp. engineering

submitted by
Ashwanee Kumar Kushwah AB 34013 BE 3rd year

ACKNOWLEDGEMENT

We being the student of Shri GS Institute of Technology & Science convey our sincere thanks to Miss Sonika Tomar of our college for providing all the facilities required for making the project successful. We are having deep sense of gratitude to project co-ordinator Miss. Sonika Tomar Lecturer of Computer Department for providing us the guidance for this project work. Under his supervision and inspiring guidance this project was embarked upon, planned and executed. Her sincere suggestion helped us greatly in bringing out this work at its present shape.

I also want to thank my friend who encourages us for this project. By Gods grace and blessing of parents, we completed our project successfully.

TABLE OF CONTENTS

# Front Page # Acknowledgement # Content page with page no.:

1) Introduction a) Purpose (objective of project) b) Project Scope c) Developers Responsibilities 2) General Characteristics a) Product Functions Overview b) Users of Project c) General Assumptions 3) Specific Requirements a) Functional Requirements b) External Interface Requirements c) System Requirements: i) Software ii) Hardware d) Non-functional Requirements i) Reliability ii) Maintainability iii) Robustness iv) Security e) Feasibility Analysis i) Technical ii) Temporal

f) Use-Case Diagram g) DFD (level 0,1,2)

4) Design a) High level design(Structure chart) b) Detailed Design : (1) System Overview (2) Design Considerations (a) Assumptions (b) General Constraints (c) Goals and Guidelines (3) Architectural Strategies : (a) strategy-1 name or description (b) strategy-2 name or description (4) System Architecture (a) component-1 name or description (b) component-2 name or description (5) Policies and Tactics (a) policy/tactic-1 name or description (b) policy/tactic-2 name or description (6) Detailed System Design (a) module-1 name or description (b) module-2 name or description
5) Coding Principles (cares taken by you during efficient coding)

6) Testing : a) Test suit applied on unit testing & integration testing.

1. INTRODUCTION

1.1 Purpose (objective of project):

The objective of this system is to maintain the manual work of a clothes shop through the software. This software is helpful for maintaining the records of each clothes Item, customer, vender, employee. To reduce efforts and saving time of the admin, we use this software. To provide the easiest way to check stock of different goods according to different ways by this software.

1.2 Scope:
This project will help in the working of receive and delivered information by providing them an easy interface. as said also Without change there are no innovation, creativity for improvement. Those who initiate change will have a better opportunity to manage the change that is inevitable. So, Depending on the needs of the users of this project, more features and modules can be incorporated. It can be extended to work for internet with the help of making it web application. It can be extended to use for different users with more secure feature.

1.3 Developers Responsibilities:

The following points are to be kept in mind while developing the project: Use platforms that are easy to understand and compatible with most other platforms. It should be interactive and user friendly. Proper care should be taken to ensure that the databases are secure.

 It should be able to handle exceptional or erroneous situations decently and should not crash in case of wrong input, low memory etc. It should be convenient to use and flexible. It should be economically efficient. It should have minimum time and space overheads.

2. General Characteristics:2.1)Product Function Overview:Following functions are provided by this project: Searching availability of the items Booking of items Selling items to customers Buying items from industries Keeping track of sell and buy Keeping track of customers Arrangement of customers Providing extra facilities to regular customers Keeping track of shops profit and loss Keeping track of progress of the shop

2.2)Users of Project

ADMIN: The owner of the shop or anyone who is responsible for running the project i.e. entering values in database, updating the database etc. He also maintains the various accounts of Customers, Staff.

STAFF: A staff member who can check databases related to customers according to his/her designation. Also, can process a reservation.

External Interfaces
The Hotel Management System will use the standard input/output devices for a personal computer. This includes the following: Keyboard Mouse Monitor Printer

Identifying Performance Constraints

1. Hardware Constraints

The System will be placed on PCs throughout the hotel. Database-associated hardware (I/O) contention.

When data is being accessed to provide information that is required in a transaction, an I/O operation passes through the processor, the disk and other such devices. If any of these devices are overused, the time taken to access the data can increase significantly. Error rates also affect the usage and performance of the device. This, in turn, increases the time that the transaction takes to complete.

2. Software Constraints All databases for the Hotel Management System will be configured using Oracle 8i. These databases include hotel rooms and customers information. These can be modified by the end users. The room database will include the room numbers and if they are vacant or occupied. The customers information database will contain all the information of the customer such as first name, last name, number of occupants, assigned room, default room rate (may be changed), phone number, whether or not the room is guaranteed, credit card number, confirmation number, automatic cancellation date, expected check in date and time, actual check

in date and time, expected check out date and time, amount owed by customer, and abbreviated customer feedback.

3. Design Constraints These are the restrictions on the design of a system, or the process by which the system is developed. While the sources are varied, design constraints typically originate from one of three sources: Restriction of design options Conditions imposed on the development process, Regulations and imposed standards. Following are some of the design constraints:

Compatibility with existing systems: The application must run on both our new and old platforms.

Compatibility with the legacy database must be maintained

There may be many such sources and rationales, and the designers may have to accept them whether they like them or not. But it's important to distinguish them from the other types of requirements, for many of the constraints may be arbitrary, political, or subject to rapid technological change and might thus be subject to review or renegotiation at a later point.

User Requirements

Following are some of the user requirements: Friendly user interface. Ease of use: Can be understood by any layman who has not built the software. Design must not be complex. Software must be flexible for other technical development. Fast processing for better performance. Adaptable to changes.

Acceptance Criteria

Acceptance criteria represents specific and defined list of conditions that must be met before a project has been considered completed and the project can be accepted by the customer. Acceptance criteria can represent certain essential requirements that must be met by the final project, or specific conditions that must be met during the process.

Some of the acceptance criteria to followed in our project are:

Communication
The project provides adequate means by which admin can communicate with support staff, customer. This includes phone numbers and an email address. The number of support channels that should be available will depend on the nature of the use.

Ease of Use
The project is laid out clearly and is easy to navigate.

Information & Transparency

The project clearly describes the nature of its goods & services. It also provides information concerning its owners & operators.

Security
The project takes adequate measures to protect the details of its customers, staff and financial details of the customers.

Legality
The project and the admin do not break any local or international laws. This includes spam and copyright laws. The products & services are genuine.

Non Functional Requirements

A non-functional requirement is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. This should be contrasted with functional requirements that define specific behavior or functions. Non-functional requirements are often called qualities of a system. Some of the non-functional requirements supported by our project are: RELIABILITY: It ensures that the project is dependable or trustworthy. It indicates the degree to which the project consistent, that is, repeated measurements would give the same result. MAINTENABILITY: It is the ease with which the project can be maintained in order to correct defects, meet new requirements make future maintenance easier, or cope with a changed environment . ROBUSTNESS: It is the ability of the project to cope with errors during execution or the ability of an algorithm to continue to operate despite abnormalities in input, calculations, etc. SECURITY: The objective of project security includes protection of information from theft, or corruption, while allowing the information to remain accessible and productive to its intended users.

FEASIBILITY STUDY
Feasibility Analysis:
A feasibility study is conducted to select the best system that meets performance requirement. This entails an identification description of evolution of system, and selection of the best system for the job. A system requirement is defined by a statement of constraints, the

specified system, objective and a description of output .the analyst is then ready to evaluate the feasibility of candidate system to produce these outputs. Three key considerations are involved in our feasibility analysis: Technical Behavioral

Technical
Technical feasibility emphasizes on the hardware and software which are used. This project can be run on any configuration of computers. As a front end we have used java which is platform independent, so it can be run on any platform. And as a back end MySQL is more compatible with visual basic. In this manner our project is technically feasible.

Temporal Feasibility Study It is a measure of how well a proposed system solves the problems, and takes advantage of the opportunities identified during scope definition and how it satisfies the requirements identified in the requirements analysis phase of system development. The proposed system is temporally feasible.

Login
Keep
Venders information information

Customer

DESIGN CONSIDERATIONS: ASSUMPTIONS AND CONSTRAINTS We assume that project is accessed by staff and administrator and database access permission is given only to the administrator. The Customer is only provided with the receipt of bill in the shop. Booking is done only when the product is available. Check in can be done only in any case. Various Constraints are applied on the text boxes regarding maximum length of characters, format of data etc.

Following are strictly needed in development of the project

Software and hardware-:

Microsoft Visual Basic(6.O) Oracle 9 or upper Operating systems--: Operating system should be compatible with all the operations provided by the system. End-user characteristics -: End user must have a basic idea of the all application software to operate it in Convenient way. The system which uses the software to be developed should have a sufficient memory to keep the databases consistently and for future expands.

GOALS AND GUIDELINE The basic goal of the system is to maintain a shop in the way that the owner need not to invest much of his time for his shop still he/she can run it in a very successful way. We have tried much more automation for permorming various operations thus to increase reliability. Because machines are more reliable than human.s SYSTEM ARCHITECTURE

This section should provide a high-level overview of how the functionality and responsibilities of the system were partitioned and then assigned to subsystems or components. This system basically works on data centered architecture. We use a centered database in which all information regarding to customers, products, services and other necessary information are kept .This information is accessed frequently by other components.

1. A design must exhibit an architecture that (a) has been created using recognizable architectural styles or patterns (b) is composed of components that exhibit good design characteristics implemented in an evolutionary fashion 2. A design should be modular

(c)can be

3. A design should contain distinct representation of data, architecture, interfaces and components. 4. A design should lead to use of proper data structures and exhibit independent functional characteristics.

Policies and tacties Describe any design policies and tactics that do not have sweeping architectural implications i.e. they would not significantly affect the overall organization of the system and its high-level structures. Choice of which specific product to use (compiler, interpreter, database, library, etc. ...) *The protocol of one or more subsystems, modules, or subroutines *The choice of a particular algorithm or programming idiom (or design pattern) to implement *portions of the system's functionality *Plans for ensuring requirements traceability *Plans for testing the software *Plans for maintaining the software *Interfaces for end-users, software, hardware, and communications *Hierarchical organization of the source code into its physical components (files and directories). How to build and/or generate the system's deliverables (how to compile, link, load, etc. ...)

CODING PRINCIPLES:

1. Test as you write As much as possible, test your code as you write it. These tests will often be quick and easy ones, such as checking that the value of pi youre using is really what it should be, but if you perform these little checks while youre working on (and thinking about) that piece of code, youll save yourself a lot more effort having to come back later and fix bugs. Youll find that you can perform a lot of simple tests very quickly as you go along; once youre in the habit, you

really dont spend a lot of time doing it. But the time you save yourself later on can be considerable 2. Validate your data At some point, someone will feed garbage into your carefully crafted code. In fact, part of your testing should be feed garbage input into your code to check that it recognises it! If your code is validating the data it is given then it should be able to deal intelligently with this, even if intelligently means crash but tell the user what has gone wrong and why 3. Handle errors nicely Asserts are a great way of validating data and are very useful during development, however once a program is in the hands of the users you want your error handling to be a little nicer than stopping the program immediately. There is nothing more frustrating than a program that just dies without warning or explanation. Most modern languages have support for handling problems your code encounters using Exceptions. Exceptions are generated when something goes wrong and bubble up until they are caught and dealt with. The advantage of exceptions is that they can be used without your code having to pass around error-code results from function to function. 4. Keep It Simple The simpler your code is, the easier it is to construct and maintain. So, subject to the constraints of our objectives, the simpler you can make your code the better. This has a connection to premature optimisation because optimised code tends to be less simple. 5. Make your code unsurprising The principle of least surprise is that you should try to make your codes actual functionality as close as possible to the typical quick impression. Or, to put it another way, you should try to write your code so that it communicates its functionality accurately in a very short (pain-free) amount of time. This means doing things like picking informative variable/function names, writing informative (and succinct) comments, and making the layout easy to read. 6. Dont Repeat Yourself (DRY) Multiple representations are also a great way to generate bugs if you forget to change some of them. This also applies to code; dont repeat chunks of code that do the same thing have a single version and put it in a function.

TESTING: A test suite often contains detailed instructions or goals for each collection of test cases and information on the system configuration to be used during testing. A group of test cases may also contain prerequisite states or steps, and descriptions of the following tests. A test case in software engineering is a set of conditions or variables under which a tester will Determine whether an application or software system is working correctly or not.

TEST CASES:

Test cases for Login Window Login screen contain username, password, ok button and cancel button.