You are on page 1of 12

INTRODUCTION

The modern industrial world is very much advanced in technology and competition in the world is intense. The user of a computer is provided with the HARDWARE and SOFTWARE, the two source of the computer. Much of the software will be programs which facilities the fast automatic management of the computer system resource. The Mobile Store Management System The Mobile Store Management System is one can go into almost required solution regarding the Mobile store. This software package provides guidance for all the mobile shop purpose, as a perfect guide, the current demand for such software became needful. This project will provide for computerization of a small enterprise whose main goal is to keep track on their inventory and billing process and wants to change from paper based transaction to computerized transaction.

1.1

Problem Definition

As the growing trend in InfoTech world of computers need of accuracy, perfectness, speed and high memory data storage is a must. Each and every problem must be solved with a least amount of time and energy. It is very difficult to maintain data record in the system as all the records are entered in the register or the respective record books. There are chances of the record books or files in which all the data is kept may be torn or wearied out or some other damages which results in the destroyed data. Also a problem occurs if the data file or register is misplaced. It is also difficult to maintain old files and registers which have data of past years which the owners had kept for future references. It is very time consuming process to write each and every entry in the database register. Also it takes a lot of time if all the entries are repeated.

1.2

Objective & Scope

The project could be implemented in an average sized organization. An average company will not be very keen on spending loads of money on ledgers. Whereas our project will greatly reduce the costs which is using common and cheap office items like database and desktop application. And also there is no requirement to store books or accounts. The data is directly stored in the database in the hard disk of the PC.

1.3

Existing System

Currently the organization doesnt have any software to store the records. All the records are manually stored on paper. This consumes a lot of time and energy. The records stored by the administrator manually sometimes have redundancy too. The data thus sometimes loses its meaning. The bill is also calculated manually thus there can be errors in bill generation too. They maintain several registers for recording the entry of daily transactions such as billing of the mobiles etc.

1.4

Proposed System
The manual system of Cell-on mobile store is to be computerized in order to overcome the problems which affect the existing manual system. Computerizing the existing system with the help of some programming language, database package ease the work of the system up to a great extent. Generally, there has been a criterion to work on any job or task for a specific purpose. Nobody works without detailed information about the particular task he is performing. Thus any transaction can be performed such as sale. In the new computerized system the basic and the initial first step is to ask for a specific user login name and password for it, thus it can also take care of data security, now after when the user enters the necessary details in the login name and password it checks for the correct password and allows the user of the system to enter the main page. As the user is inside the system, the first screen of the system should be a welcome message and a list of menus. These menus contain the options of Mobiles, Suppliers, and Bills etc. In each menu user can Add, Edit, Delete, Save and search any particular record.

1.5 Assumptions & Constraints


Assumptions The Mobile store management system shall be a stand-alone system running in a Windows environment. The system shall be developed using C++. The code should be free with compilation errors or system errors. The product must have an interface which is simple enough to understand.

Constraints The system must support the runtime files of C++ and must be able to run all the forms. Login and password is used for identification of user and there is no facility for the customers.

1.6 Introduction to System Requirements


The requirement analyst has to identify the requirements by talking to the clients and understanding and responding to their needs. Basic requirements from the system are: To make the process of handling data and records more simple. To reduce the manual work. To increase the speed of the work

Basic system requirements are: Functional Requirements Performance Requirements Design constraints imposed on implementation External interface Requirements

SOFTWARE REQUIREMENT SPECIFICATION


2.1 Introduction
The Software Requirement Specification is a document that describes the external requirement for any system. The Requirement analyst has to identify the requirements by taking to the clients and understanding their needs. The inputs are to be gathered from different resources, these inputs may be inconsistent. The Requirement phase translates the ideas in the minds of the clients into a formal document. Here the user needs are accurately specified. Requirement must be actionable, measurable and testable related to business need or opportunities and defined to a level of detail sufficient for system design. 2.1.1 Advantages of SRS An SRS establishes the basis for the agreement between the client and the developer on what the software product will do. SRS provides a reference for validation of the final product. A high-quality SRS is a prerequisite to highquality software. A high-quality SRS reduces the development cost. 2.1.2 Components of SRS The basic issues an SRS must address are Functional Requirements Performance Requirements Design constraints imposed on implementation External interface Requirements

2.2. Over all Description


2.2.1. Product Perspective The product will be developed completely independent and standalone. Each user will have to an individual copy of the product. Mobile shop collects and stores information about purchase, sales etc. and stores it in the database file which can be retrieved and used when ever needed and all the validations are performed during the entry of the data by the user thus ensuring that the user cannot leave the field empty which would cause problem later.

2.2.2. Product Function The different modules specified are used for the indentation purpose, to make transactions based on different criteria. This project includes graphical user interface with simple menus, which help the admin to input, process and retrieve data with ease. This project is designed to do the functionalities of mobile Store. It also describes mobile stock record, sales record, supplier information. 2.2.3. User Characteristics The user of this product is supposed to be fairly educated about the usage of the computers. He should understand how to store products and he should have knowledge about various products so that they could be saved. A person who has no knowledge of computers will find it difficult to understand the system. But with a little knowledge it will be very easy to handle the project. Admin: Admin collects and stores information about purchase, sales etc. and stores it in the database file which can be retrieved and used when ever needed and all the validations are performed during the entry of the data by the user thus ensuring that the user should not leave the fields blank which would cause problem later. 2.2.4. General Constraints 2.1.4.1 Log in validation Mobile store management system has Login Name and Password to enter into the system. If both are valid then only Admin is allowed to enter into system. 2.1.4.2 Validation for blank fields Mobile store management system doesnt allow the admin to leave any data field blank.

2.3. Specific Requirements


2.3.1. External Interface Requirement 2.3.1.1. User Interface TURBO C is used for user interface and for maintaining Database respectively. TURBO C is used as a front-end application. o Login o Mobile Add Mobile Details Edit Mobile Details Delete Mobile Details View Mobile Details Search Mobile Details o Bill Add Bill View Bills o Supplier Add Supplier Details Edit Supplier Details Delete Supplier Details View Supplier Details Search Supplier Details o Help 2.3.1.2. Hardware Interface The Hardware Requirements specify: Pentium 3 processor or higher Hard disk of 4GB capacity or more 512 RAM Standard output display Standard QWERTY keyboard

2.3.1.3. Software Interface The Software used for this project is TURBO C++ Compiler.

2.3.2. Functional Requirements


2.3.2.1. Module 1:- Login The Login module is used to perform login operation for the Admin to access the different functionalities of the software. 2.3.2.2. Module 2:-Mobile The Mobile module performs Add Mobile which is used to add mobile id, qty, color, model no, brand, wifi, camera, operating system, phone memory, screen size, Cost Price, Selling Price. Mobile Details can be edited if any changes are to be needed and can also be viewed. Another sub module is delete mobile that can be used to delete details of a particular mobile. 2.3.2.3. Module 3:-Supplier The Supplier module performs Add Supplier which is used to add Supplier id, phone number, name and address of the supplier. Supplier Details can be modified if any changes are to be needed and can also be viewed. Another sub module is delete supplier that can be used to delete details of a particular supplier. 2.3.2.4. Module 4:-Billing This module is used for making bills and viewing all the bills stored in the database. The bill includes the bill id, bill date and quantity and price of all the mobiles purchased by a customer.

2.3.3 Performance Requirements


Response time for a transaction - average: 250 milliseconds, maximum: 2 seconds. A transaction involves sending one question or receiving one response. Throughput an average of 4 transactions per second. Good working PC with all the requirements and should not be overloaded.

2.3.4 Design Constraints


The Mobile store management system shall be a stand-alone system running in a Windows environment. The system shall be developed using TURBO C. Turbo C is one of the earliest compilers for C and C++ programming language.

2.3.5 Logical Database Requirement


A database will be kept to store different functionalities of the software. This database will hold integers and floats as well as Boolean data. The information stored will be access at almost every possible interface with the user and by almost every internal system. The software will allow an Admin to store and recall values. These values will be stored in a database and will be accessed only if the Admin updates or requests a stored value. The input interface and the algorithm processor will access this database.

2.3.6 Software System Attributes


The coding is done with following characteristics in mind: Ease of design to code translation Code efficiency Memory efficiency Response time Maintainability Security Simple ease to understand code Efficient and consistent logic

2.4 Cost Benefit Analysis


Cost Estimation Cost Domains Hardware cost Software Development Requirement Gathering Analysis Design Development Testing Documentation Estimated Gross Total Cost of contingency (20 % of total estimates) Estimated Gross total Development Cost Cost Domains Hardware cost Software Development Requirement Gathering Analysis Design Development Testing Documentation Estimated Gross Total Actual Gross total Units/ Hours spent Cost/Rates per hours (rs) Sub Total (Rs.) Units/ Hours spent Cost/Rates per hours (rs) Sub Total (Rs.)

32 hrs 70 hrs 35 hrs 200 hrs 42 hrs 20 hrs

50 40 30 50 30 60

1,600 2800 1050 10000 1260 1200 17910 3582 21492

45 hrs 60 hrs 40 hrs 250 hrs 30 hrs 25 hrs

50 40 30 50 30 60

2250 2400 1200 12500 900 1500 20750 23800

Overrun Amount: (Actual Gross total- Estimated Gross Total): 23800-21492= 2308 Cash in Hand (Leftover amount of contingency): 3582- 2308= 1274 Benefits for the current year Estimated Cost of Application: Rs. 80/Estimated number of people who will purchase: 20 per / month Estimated amount that can be incurred: Rs. 1600/- per month Estimated amount incurred in 1 st financial year: 19200/-

PROJECT ANALYSIS AND DESIGN


3.1 Methodologies Adapted Detailed life Cycle of the Project
The general methodology in developing a system is involved in different phases which describe the systems life cycle model for developing software project. The concept includes not only forward motion but also have the possibility to return that is cycle back to an activity previously completed. This cycle back or feedback may occur as a result of the failure with the system to meet a performance objective or as a result of changes in redefinition of System activities. The basic WATERFALL MODEL is being used that is its stages. These are as follows:1. Requirement Analysis Phase 2. Design Phase 3. Development Phase 4. Coding Phase 5. Testing Phase 6. Implementation Phase 7. Post Implementation Phase EXPLANATION OF DIFFERENT STAGES OF WATERFALL MODEL REQUIREMENT ANALYSIS This phase includes the definition of the problem. In order to identify the problem: we have to know information about the problem the purpose of the evaluation for the problem to be known. To know the clients requirements and the objectives of the project, a questionnaire was prepared and the client was made to answer it. On the basis of the questionnaire, the problem is defined and evaluated. The SRS is made and requirement analysis is done. DESIGN Software design is a process through which the requirements are translated into are presentation of a software. The design of the system is in modular form i.e. the software is logically partitioned into components that perform specific functions and sub functions. The Design Phase leads to modules like Mobile, Billing and Suppliers which exhibit independent functional characteristics .These modules arent interconnected. It even leads to interfaces that reduce the complexity of the connections between modules and with that external environment. DEVELOPMENT The development phase includes choosing of a suitable s/w to solve the particular problem given the various facilities and the sophistication in the selected software gives a better development of the problem. Here the software was built using TC compiler. The data is stored in Database files for easier access.

CODING The coding phase is for retranslating the design of the system produced during the design phase into code in a given programming language which can be executed by a computer and which performs the computation specified by the design. We have used C++language and its basic concepts for coding the software system. TESTING Testing is done in various ways such as testing the algorithm, programming code, sample data debugging is one. Testing has been done by checking each and every module and also to check the validations. IMPLEMENTATION After testing is over project is implemented by providing training to the users and providing manuals so that they can be refreshed as and when needed. POST IMPLEMENTATION If any problem occurs after the implemented they are removed from time to time so that so that the users can work on the prepared system easily finally a satisfied user when all things are almost right.