FINAL Docu - Copy4

Product Information System
1.1 COMPANY OBJECTIVE

Aatmiya Technologies is a firm which works in different sectors. (I) Education (II) Development (III) Industrial Training EDUCATION DIVISION:AATMIYA COMPUTER CENTER Aatmiya is a computer center where all types of computer courses covered. Level 1 Basic, MS-Office, MS-Access Level 2 C, C++, Java, Oracle, Visual Basic Level 3 HTML, CSS, Java Script, VB Script, Photoshop, Dream weaver, Flash. Level 4 AutoCAD, Pro-E for Engineering students. We are authorized license user of Pro-E.Level 5 VB.net,Asp.net, PHP, SQL Server. Also, we give training to BCA, MCA, DCA, diploma & degree students on their college computer subjects. We have also successfully completed training to GOVERNMENT EMPLOYEES on course on computer concept (CCC) in 2008. C#, C#.net,
Parul Polytechnic Institute
Page 1
1.2 COMPANY HISTORY

OXFORD ENGINEERING INSTITUTE Oxford is a Engineering institute where all types of engineering students are studying their college subjects. Oxford Engineering covers all subjects of Diploma and Degree students of various branches such as CE, EC, IT, Civil, Electrical, Mechanical, Automobile, etc for all semesters. DEVELOPMENT DIVISION We are now introducing software as well as website development in live work. Software Development works in Front End : VB.Net SQL Server 2005 ASP.Net MS Access Database : Front End :Database :-
Website Development works in
INDUSTRIAL TRAINING We provide industrial training for final year students of BCA, MCA & diploma students. 1. 2. 3. C#.Net with MS Access or SQL Server. ASP.net with MS Access or SQL Server. VB.net with MS - Access or SQL Server.
Page 2
2.1 Project Profiles Product Information System:The software basically consists of the following parts or detail1 1. Product Status of Market. 2. Risk of new Product launching. 3. The details of the New Comer. 4. The Company of the New Comer. 1. Product Status of Market. It shows the All Details about Product which is In current Market. It shows the Market Value of the Product and Information related to the Product. 2. Risk of new Product launching. When new comer Launch the New product that time every product cant be success. This system decresease the failure Possibilities of new Product. 3. The details of the New Comer. It shows all details about new comer who use this system. For e.g. New comer no, new comer name and various other details. 4. The Company of the New Comer. It shows all Information about launching the new product of company. for e.g. Co. Product and other information. This software shall only give the Brief Information of the Launching the New Product in market and its market value.
Page 3
2.2 PROJECT DEFINITION:2.2.1 Problem Summary:When any new comer or company try to launch the new product in market that time each product cant successes in market or any company or new comer dont know about all information about product like market value etc. This is an industrial defined problem (IDP). This system gives the brief view about new product , position of product in market and competition of other companies of specific product. It shows the other company product which already in the market. It helps new comer to launch the product in market and helps to decrease the failure possibilities of product.
Page 4
Product Information System 2.2.2 DESCRIPTION:It is the problem to launch the new product in market. Whenever new comer or a company try to launch new product it require market value of product. Market value is helps to launch the product.5 When any new comer launch the product then he requires to know about the product and its status and for that some person or groups gives information about value of that product. And if the new comer is getting information of product from person or groups then many problems are arise. The person or group may not gives the proper information about product. The person or group may not have the proper information about the product. Or some
other reason. So this software is useful for the new comers for launching new product. To overcome all this problem for new comer because it pays money for new product launching otherwise his money is wasted. So our software will not only help the new comer but also the company of the comer to understand the new companys product information. Company and New comer can refer software and can launch product without taking help of person and group.
Page 5
2.3 GOALS &OBJECTIVES:GOALS: Positive competitiveness. No waste of time &money. Pure flow of business. Easy adaptiveness for the launch. Easy interaction with the product. Updates can be easily shared. Utilization of time. Scope of getting complete details of product. This method is fast & easy to understand. Reduced requirement of manpower Enables faster response to changing situations
Page 6
Product Information System OBJECTIVE:We aim to create software that shall support the following concepts:1) User Friendly:The proposed system is user friendly because the retrieval and storing of data is fast and data is maintained efficiently. Moreover the graphical user interface is provided in the proposed system, which provides user to deal with the system very easily. 2) Very less paper work:The proposed system requires very less paper work. As the details are already given in the software which user required. 3) Computer operator control:Computer operator control will be there so no chance of errors. Moreover storing and retrieving of information is easy. So work can be done speedily and in time. 4) Consumed less time and money:As the new comer use this system to launch the product easily and fast he consume time and money.
Page 7
2.4 SCOPE: During/After launching following problem may occur New Comer has no time for getting information in market. Group or Person may not give proper information. Not proper way to launch the Product. Because of the following problems the company as well as the new comer has New comer and the Company invest money for company product. Product has no scope for success in market. This system gives brief information about the new product which is launch by
to suffer.
the company.
Page 8
3.1 INTRODUCTION:This SRS describes the software functional and nonfunctional requirements for release of the Multi-level Marketing (MLM). This document is intended to be used by the members of the project team that will implement and verify the correct functioning of the system. Unless otherwise noted, all requirements specified here are high priorities and committed for the current release. They may be useful for troubleshooting/evaluating performance or may be useful to customers that want to know more information about how much data is being synched and how often it is occurring. Comparison with the Existing system used by the Client: The existing system is entirely based on the manual task. Existing system is based on Excel sheet, and all work is done by the computer operator, so they maintain files and folder to record all the details within a system. They maintain the information of employees in Excel sheet. Company has thousands of employees and products manufactured in a day and to provide service and maintenance is very difficult first they have to search for the Up line detail, and then for the Down line detail. The current system has lack of security and lots of other problems/limitations too.
Page 9
3.2 OVERALL DESCRIPTION:The hardware and software requirements described below are provided as general requirements. Individual factors to consider that can affect these requirements include: Server: Processor speed 1.8 GHZ (Recommended) Memory: 1 GB RAM (Recommended) Hard Disk: 120 GB (Recommended) Client: Processor Pentium 4 (Recommended) Memory: 256 MB RAM (Recommended) Software Interfaces Server: Development Tool: Visual studio 2005 Database server: SQL Server 2005 Technologies: VB.NET Number of servers involved and how they are configured. Number of users MLM implementation will support Performance of your servers and the local area network (LAN) MLM server system requirements
Hardware Interfaces
Page 10
3.3 SPECIFIC REQUIREMENTS:Hardware Requirements This phase of the software development process deals with a brief study of different hardware used in the computerized system. All the hardware needed here are generally the basic configuration of a typical office computer. A list of the hardware requirement used in the system given below: Minimum Configuration: To run the application software of the system in the computer the minimum configuration required is as below: 233 MHz Pentium processor or other compatible. Intel Chipset Motherboard. 512 MB-RAM. 11 GB Hard Disk. 4x Compact Disc drive or faster. 1.44 MB Floppy Disk Drive. Monitor. [640 x 480 Display] Keyboard. Mouse. Dot Matrix Printer.
Page 11
4.1 STUDY OF CURRENT SYSTEM:Currently there exists no system that provides training scope to the trainee .There are only seniors or some other persons that provide training to the trainee, those persons are selected by the company. Naturally there occurs a problem when the person appointed for giving training is not available for certain reasons. In that case the trainee doesnt get a scope of getting accustomed to the companys work for which he was recruited, means he doesnt get a clue of what work he is supposed to do. Similarly the existing system is based on Excel sheets, and all information about the employees is maintained by the computer operators, so they maintain files and folder to record all details within a system. They maintain the information of Employees in Excel sheet. Now consider a situation .An employee gives you a call for the fulfillment of some necessary resources in the production department. In doing so you will check for personal details and all other information of which employee had registered and from which department At that time you need to consult the required department in order to get the relevant information. In doing so you will have to wait till you get the required information and in turn you will make your Employee wait as well as the production will come to a halt, which isnt expected. The current system has lack of security and lots of other problems /limitations too.
Page 12
4.2 PROBLEMS &WEEKNESS OF THE CURRENT SYSTEM:We had a detailed study of the current system .And from these studies we found the following limitations in the current manual system

Data isnt available centrally. Maintaining record is difficult. Time consuming. Editing of data is a tedious job. No security of Data. Report generation is a monotonous task. Lack in efficiency. The person giving training may cannot teach or explain the fresher properly. May the person intensely dont teach the fresher in shear jealousy. May the person have load of work and cannot get time to teach the fresher. May the person can miss behave to the trainee and hurt his ego etc.
Page 13
4.3 PROPOSED NEW SYSTEM: Will help clearing miss-communication. Shall provide a scope for transfer of knowledge. Will test the trainees knowledge or dedication towards the given work. Transparency will be maintained. No types of partiality among the employees. A scope of receiving complete training by the fresher. Authentication or security can be maintained among the works done at different level .
Page 14
5.1 DATA DICTIONARY:The Data Dictionary of any system is an integral component of structure analysis, since data flow diagrams by themselves do not fully describe the subject under investigation about the system. A Data Dictionary is a catalog a repository of the elements in the system. These elements center on data and the way they are structured to meet user requirements and Banking System needs. This step of creating a data dictionary is simultaneous with the process of making data flow diagram(s). Here all the data fields in their respective tables are allotted so as to access these data in the system. The data tables are created in a back-end tool like Microsoft Access, Oracle, FoxPro, etc Here in the Company Item Info System we are using tables created in SQL Server 2005, as it is the back-end tool used in the system. The data dictionary consists of different major elements like Data Elements, Data Store [Tables Used], Data Flow, Processes and other External entities used in the system. The data dictionary stores details and description of these elements. It is developed during data flow analysis and assists the analysts involved in determining the system requirements. Analysts use data dictionary for the following important reasons:

To manage the details in large system. To communicate a common meaning for all system elements. To document the features of the system. To facilitate analysis of the details in order to evaluate the characteristics and
determine where system changes should be made.
To locate errors and omissions in the system. The data dictionary contains different types of descriptions for the data flowing through
the system: Data Elements is the most fundamental level, which is also considered as the building block for all other data in the system. It refers to all the different data used like fields, data
Page 15
Product Information System item, etc. to make the system fully functional irrespective to the table used in the system. Here all the different type of fields used to make table are written sequentially without referring to the tables. This process helps in the process of Normalization of tables. Next to Data Elements comes the Data storage which provides the information of where and how each data element is stored in which table and it also give information of any constraints if there. This step also gives knowledge of different data types used for different field and their size. All the normalized tables are showed in data storage. Data Flow stage shows the flow of data in the system. This step is can be already seen in the data flow diagrams above in this document. This step refers to all the data flow paths were transactions are done in the computerized system. The data flow step also includes different processes used in the system and it is followed by External Entities used in the system.
Page 16
1.
LOGIN:- (To Authenticate a User)

DATATYPE VARCHAR VARCHAR SIZE 50 50 DESCRIPTION To provide id to the user Table to authenticate users
FIELD NAME User_id User_password
This table shall provide the authentication details about the user like as above.
2. Product_Master
FIELD NAME product_type Product_id Product_name Company_Product Product_Description Product_Image Product_status Product_Turnover User_ratings DATATYPE Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Number SIZE 50 50 50 50 50 50 50 50 10 DESCRIPTION Type of the product ID of Product Name of the product Name of company Details of Product Image of Product Market Status of Product Net Turnover User Ratings
This table will provides the Details about Product. 3.New_Comer_Master FIELD NAME Comer_id Comer_name Comer_add Comer_Company Comer_contact Comer_gender DATATYPE Varchar Varchar Varchar Varchar Number Varchar SIZE 50 50 50 50 20 50 DESCRIPTION ID of New Comer Name of New Comer Address of new comer Company of New Comer Contact No of NewComer Gender of the NweComer
This table contain Details of New Comer.
Page 17
Product Information System 4.Company_Master FIELD NAME Company_name Company_Id Company_add Company_contect_no Company_turn_over Company_product DATATYPE Varchar Varchar Varchar Number Varchar Varchar SIZE 50 50 50 20 50 50 DESCRIPTION Name of Compny Id of Compny Address of Compny Contect number of Compny Net Turnover Name of compny product
This table contains details about company.
Page 18
Product Information System E-R Diagram:-
U s e_id r
U s e_p a s s w o rd r
L o g in C o m p n y ro d u c t _p P ro d u _ty p e ct U s e r re q u e s t fo r p ro d u c t P ro d u _n a m e ct P ro d u _id ct P ro d u _d e s c rip tio n ct R e q u e s t fo r p ro d u c t com pny P ro d u _ t c m a s te r P ro d u _st ta tu s e c C o m p a _id ny C o m p a _a d d ny C o m p a _tu rn v e r n y _o C o m p a _c o n te _n o ny ct C o m p a n y ro d u c t _p N ew om _c e r_m a s te r C o m e rs c o m p n y C om pany _m a s te r N e w P ro d u c t P ro d u _tu rn o v e r ct P ro d u _im a g e ct
C o m p a _n a m e ny
P ro d u _ra tin g s ct
C om er _id
C o m e r a m e C o m e r d d C o m e r o n te c t C o m e r o m p a n y C o m e r e n d e r _n _a _c _c _g
Page 19
FLOW OF PROCCESS:-
P ro d u c t i n fo rm a ti o n s y s te m
A d m in
U ser
P ro d u c ta s te r C o m _mr a s te rC o m p o n y s te r _m e _m a
P r o d u c ta s te r C o m p o n y s te r _m _m a
Page 20
5.2 DATA FLOW DIAGRAM:The Data Flow Diagrams are pictorial or graphical representation of the outline of the system. The Data Flow Diagram covers all the processes, which takes place during any transaction in the system. The Data Flow Diagrams are functionally divided into context level, first level, second level, third level data flow diagrams. There are six basic processes in the Company Item Info System and it is also having some sub processes. All the processes can be clearly understood by understanding of the Data Flow Diagram.
0-Level Diagram:
Admin
Pass data for verification
Response return
Product info system
Give list of product as required
Request for current product status in market
User
This shows the most initial step where the item head encounters his query for searching details.
Page 21
1 level Diagram:-
Adm in Pass Data for verification

Verify data 1
Login
Check Product Status 2
Product _M aster
Check for Update 3
Enter Product 3
Cum er m
_m aster
Check Com pany 3 Com pany _M aster
Response Return LogO ut 4
Request 1
U ser
This shows the initial step where the employee head encounters his query for searching the employee details.
Page 22
2 level Data Flow Diagram :-
Admin Add new 2.1
Product_Master
Delete 2.2
Comer_master
Edit 2.3
Company_master
Request 2.1
login
User
This shows the deletion, update, edit process performed by the admin department and how the updated data is being registered in the database. This also shows the detail about how user access the data from the database.
Page 23
6. TESTING & VALIDATIONS:Testing is software quality assurance activity. Which is a very important to work the system successfully and achieve high quality of software. The main objective of testing is to find yet an undiscovered error and at the same time checking the quality and reliability of system. Testing is the most essential part of developing software because it gives perfection to the software developed. By what a person is going to access data has to be unique for each and every user so that his privacy can be maintained in the system and no other user can access others information. The four stages in the testing Process are the following: UNIT TESTING Unit testing is a dynamic method for verification where the program is actually compiled and executed. It is one of the most widely used methods and the coding phase is sometimes called coding and unit testing phase. Unit testing involves executing the code with some test cases and then evaluating the results. The goal of unit testing is to test modules or units and not the entire software system. Unit testing is most often done by the programmer himself. MODULE TESTING A Module is a collection of dependent components such as an object class, procedures and functions. A Module encapsulates related components so that it can be tested without other system modules.
Page 24
6.1 SUB-SYSTEM TESTING

Sub-system tasting involves testing a collation of modules which have been integrated into Sub-systems. Note that sub-systems may be independently designed implemented the most common problem which arises in large systems is the interfacing of the sub-system. The Sub-system test process should therefore concentrate on the detection of interface errors by rigorous testing. System Testing System testing is probably the most important phase of complete testing cycle. This phase is started after the completion of other phases like Unit, Component and Integration testing. During the System Testing phase, non functional testing also comes in to picture and performance, load, stress, scalability all these types of testing are performed in this phase. By Definition, System Testing is conducted on the complete integrated system and on a replicated production environment. System Testing also evaluates that system compliance with specific functional and non functional requirements both. It is very important to understand that not many test cases are written for the system testing. Test cases for the system testing are derived from the architecture/design of the system, from input of the end user and by user stories. It does not make sense to exercise extensive testing in the System Testing phase, as most of the functional defects should have been caught and corrected during earlier testing Utmost care is exercised for the defects uncovered during System Testing phase and proper impact analysis should be done before fixing the defect. Sometimes, if business permits defects are just documented and mentioned as the known limitation instead of fixit. Progress of the System Testing also instills and build confidence in the product teams as this is the first phase in which product is tested with production environment. SubSystem testing can be one of the following five types: 1) 2) 3) White Box Testing Black Box Testing Interface Testing
Page 25
Product Information System 4) Alpha Testing
1.
White Box Testing
White box testing is very different in nature from black box testing. In black box testing, focus of all the activities is only on the functionality of system and not on what is happening inside the system. Purpose of white box testing is to make sure that Functionality is proper Information on the code coverage
White box testing can be performed at various level starting from unit to system testing. Only distinction between black box and white box is the system knowledge, in white box testing you execute or select your test cases based on the code/architectural knowledge of system under test. Even if you are executing integration or system test, but using data in such a way that one particular code path is exercised, it should fall under white box testing. 2. Black Box Testing Probably this is what most of us practice and is used most widely. This is also type of testing which is very close to customer experience. In this type of testing system is treated as close system and test engineer do not assume anything about how system was created. Only input for test engineer in this type of testing is requirement document and functionality of system which you get by working with the system. Purpose of black box testing is to Make sure that system is working in accordance with the system requirement. Make sure that system is meeting user expectation.
3. Interface Testing Interface Testing is concerned with both the Program specifications and Program implementation. This type of testing is particularly important for object oriented system. Parul Polytechnic Institute Page 26
Product Information System 4. Alpha Testing It is simulated or actual operational testing by potential users/customers or an independent test team at the developers' site. Alpha testing is often employed for offthe-shelf software as a form of internal acceptance testing, before the software goes to beta testing. It comes after alpha testing. Versions of the software, known as beta versions, are released to a limited audience outside of the programming team.
Page 27
7. USER MANUALS:Following are the intended users who are going to interact with the system. Users are classified and differentiated on the basis of their interaction with the system. Each user will have an access to the system based on the access rights/privileges or will be able to navigate through the system that are intended for them. Beyond that none will be able to access the features not anticipated for them.
LOGIN FORM: This is the main page of the whole system . This is used to authenticate the users who try to login in the system. The authenticated users are given valid User_ID and Password in order to
login the system and get the necessary details made available through this system NEWCUMER MASTER: The employee master is used to save the various important details regarding It holds all the personal details belonging to the particular employee working This shall include cum_id, cum_name, cum_contact_no, etc. the employee in that firm or the respected company.
PRODUCT MASTER: The Item master is used to save the various important details regarding the It holds all the personal details of the item such as the processing details of the This shall include pro_id,item_no,item_name, etc. Product manufactured by the company. Item at various levels or at various departments.
Page 28
8. INPUT OUTPUT SCREEN SHOTS:1. LOGIN FORM:-
This is the login form that determines the login ID and Password of the employee that aims to login in this system.The login form is basically used in order to provide authentification to the current users of this system. Only those having the valid user ID password will be able to login to this system. .
Page 29
2.NEW USER FORM:
This form add new user to the current system. This is provided in order to permit other users to use this system and thus fill this form to create an authenticated identity for the system. It shall ask for the some of the personal details of the user who is wanting to create his own login into the system.
Page 30
4. ITEM MASTER:-
This form gives the details of the product used in the market.
Page 31
9. LIMITATIONS & FUTURE EHANCEMENT:LIMITATION: This project is on platform of Visual Studio 2008 so, it is windows based applications. User cannot train himself online There can be limitation of searching more than one item, it is a work on multiple system.. The security provided by this software is not sufficient.
FUTURE ENHANCEMENT: In future we are aiming to convert this software as online software so that the trainee can train himself online. As software shall be online then multiple information can be fetched. In future we shall be introducing high security features like eye censors, finger print identification and etc.
Page 32
10. CONCLUSION:The initial study made it crystal clear that there was a desperate need in the market for the system. In addition to this, distinctive features have also been well taken care of .The features have been implemented satisfactorily and may meet the desired requirements as stated during the initial study. The Company Information system has been a way of minimizing the clerical work, which is almost a routine and consumes the most precious time. The Company Item Info System has been an attempt to help the user reduce the workload along with minimizing the paper works and saving time. Almost all the difficulties of feeding details manually have been removed by this system. Last but not the least we would like to welcome all the suggestions and other improvements, which the system shall require, so that it covers all the needs of the user who uses it anyway.
Page 33
BIBILOGRAPHY: Software Engineering Fundamentals. BY: All Benforooz and Frederick Judson. PC Software. BY.R.K Txily Black Book. Programming in VB.Net. BY MC Graw Hill Publication Administrators Guide to SQL Native 2008 BY: WOODY, BUCK
System Analysis & Design BY: SHELLY CASHMAN ROSENBLATT System Analysis And Design By : Sinn PL-SQL By: Ivan Byross Software Engineering By : Roger S. Pressman VB.NET 2005 by Wrox Publications
WEBILOGRAPHY:All about Microsoft controls in VB.Net http:/www.msdn.microsoft.com/ Wikipedia for various diagrams & testing methods http://cooltext.com/ K-state Research Exchange for sample in report writing http://krex.k-state.edu/dspace/handle/2097/959 Smart Draw for drawing all the Diagrams used in this report. http://www.smartdraw.com/
Page 34
Page 35

FINAL Docu - Copy4

Uploaded by

Copyright:

Available Formats

FINAL Docu - Copy4

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FINAL Docu - Copy4

Uploaded by

Copyright:

Available Formats

Product Information System

1.1 COMPANY OBJECTIVE

Parul Polytechnic Institute

Product Information System

1.2 COMPANY HISTORY

Website Development works in

Parul Polytechnic Institute

Product Information System

Parul Polytechnic Institute

Product Information System

Parul Polytechnic Institute

Parul Polytechnic Institute

Product Information System

Parul Polytechnic Institute

Parul Polytechnic Institute

Product Information System

Parul Polytechnic Institute

Product Information System

Parul Polytechnic Institute

Product Information System

Parul Polytechnic Institute

Product Information System

Parul Polytechnic Institute

Product Information System

Parul Polytechnic Institute

Product Information System

Parul Polytechnic Institute

Product Information System

Parul Polytechnic Institute

Product Information System

determine where system changes should be made.

Parul Polytechnic Institute

Parul Polytechnic Institute

Product Information System

LOGIN:- (To Authenticate a User)

FIELD NAME User_id User_password

This table contain Details of New Comer.

Parul Polytechnic Institute

This table contains details about company.

Parul Polytechnic Institute

Product Information System E-R Diagram:-

Parul Polytechnic Institute

Product Information System

Parul Polytechnic Institute

Product Information System

Product info system

Give list of product as required

Request for current product status in market

Parul Polytechnic Institute

Product Information System

Adm in Pass Data for verification

Check Product Status 2

Check for Update 3

Check Com pany 3 Com pany _M aster

Response Return LogO ut 4

Parul Polytechnic Institute

Product Information System

2 level Data Flow Diagram :-

Admin Add new 2.1

Parul Polytechnic Institute