Gas Agency

softw ar package fatality judicial admission for BuzzyBUY. com (Online Shopping and auctioning web Site) Prep atomic number 18d by Table of limit 1. Introduction 2 1. Purpose 2 2. Document Conventions2 3. Int suppressed Audience and in phase angleation Suggestions2 4. carrefour Scope2 5. References 2 2. Over altogether description 3 1. Product Perspective3 2. Product Functions3 3. drug mappingr Classes and Char causeeristics 3 1. executives 3 2. Buyers4 3. sellers 4 4. unconcerned visitants4 4. rule and Implementation Constraints5 . User Documentation6 6. Assumptions and Dependencies6 3. orthogonal Interface Requirements6 1. User Interfaces6 2. Hardw ar Interfaces6 3. package Interfaces6 4. Communication Interfaces7 4. System Features7 1. Listing7 2. Account Creation8 3. Selling8 4. buying8 5. Rating8 6. otherwises8 5. varied Non Functional Requirements9 1. Performance Requirements9 2. Safety Requirements9 3. parcel Quality Attri only ifes 9 4. Business Rules9 6 . extension A Glossary9 7. appendix B abbreviation Models10 1. Introduction 1. Purpose The purpose of this SRS is to characterize the requirements of the web based softwargon act buzzybuy. om, which is an online shopping and complotding administration. The module to be developed is the first variation of buzzybuy version 1. 0. This Softw atomic number 18 Requirements Specification provides a recognize description of all the functions and specifications of buzzybuy version 1. 0 2. Document conventions IEEE standards used. straight-laced sub be corpse for sub topics based on the importance and priority of the matter. 3. Intended audience and reading suggestionsThe expected audience of this muniment is the faculty in charge of software engineering lab for 6th semester entropy processor Science, NITK suratkal .It result be used as a reference for grading in the lab for even semester of 2006. Thither is no suggested reading to be done sooner going through the document . 4. Product compass Buzzybuy. com is designed to run on both(prenominal) either modern platform with GUI. It is faux that the rearwards end that go out be used for implementation is MySQL and the front end that ordain be used is PHP. 5. References 1. The applicable IEEE standards are published in IEEE standards exhibition, 2001 edition. 2. Software Engineering, A Practitioners approach, 6th edition. By Roger S Pressman. McGraw cumulus international. 2. Overall description 1.Product perspectiveThis is proposed to be an enhanced model of the present sidereal day existing shopping and auctioning portals. Many flaws in the present online shopping portals keep backnt been able to exploit the full latent of e-commerce grocery. The Software Requirements Specifications intends to identify the flaws in the true existing ashes and propose an alternate or a solution to them. 2. Product Functions It consists of two modules 1. Customer module 2. executive module A customer sho uld put one over a exploiter describe for carrying come forth performances. Transactions include buying, selling and auctioning. Administrator provides the customer with an account happening neat registration procedures to prevent malpractices in the achievements. any visitor is allowed to browse through the merchandise list, their prices and command procedures. get, selling and bidding procedures are kept transparent so that any drug user is able to go through the procedures. 3. User classes and characteristics in that respect are 3 kinds of users for the proposed system 1. Administrators They create user accounts and give it to the tamp customers. ? To educate consumers almost Buzzybuys divagate of increases and indigenous services. They mustiness provide rules for the minutes. ? They must maintain the web point and update the same make necessary changes at fourth dimensions. ? They must take care of the armamentage issues affect in the transactions. ? They must inform the users nigh their transaction status and keep them updated about the boost through emails. ? They must receive feedbacks from their customers or any users about their system and act upon the relevant ones. ? Look up at all the legal issues involved with the short letter. ? restrict place for advertizements in the web put as a revenue generating option.The place has to be maintained and proper leanings done. ? Any fai stimulates in the system stick out to be detected and repaired. 2. Buyers They are the genuine customers of the website. They buttocks see the inclination, bid for dissimilar things, and also buy them to various payment options. 3. Sellers These are the race involved in selling their products through buzzybuy. They encounter this as a virtual market place. They get hold of to be provided with proper advertisement place, and ratings of customers. The sellers as considerably as are rated based on the feedback they get from previous tr ansactions perfect from customers.These feedback data are treated with not bad(p) respect and are transparent to e realone. The sellers similarly value this very highly. 4. Casual visitors These people dont come to the site on specific intensions of buying or selling. They just visit to see the listing and too see the products. They inquire not moderate an user account. They elicit be future potential customers. They sellers can lure them with advertisements on the site based on their budget. The following usecase diagram states the above data in a graphical form pic Fig 1 Usecase Diagram for BuzzyBuy 4. Design and Implementation Constraints The main constraint here would be the subdueing the genuineness of the buyer, which is not ever possible. There can be security risks involved. The design constraints are that the browser at each place may not follow similar screen resolutions, browsers and so on This can lead to the website not having the disturb it is planned to ha ve. Also the rules of the land leave behind prohibit certain items to be sell on the site. Hence all those factors need to be filtered in. Also storage lieu constraints may come if the listing becomes too large. Hence a strong host needs to be chosen to host the database. 5.User Documentation 1. Online user help with all the necessary help needed to use the site in a publicise format. 2. Problem addressable forms 3. Software and database specification 4. Details of rules and regulation to sellers as well as buyers. 6. Assumptions and Dependencies None as per directly 3. External Interface Requirements 1. User Interfaces for each one part of the user interface intends to be as user friendly as possible. The fonts and buttons used impart be think to be very fast and blowzy to load on web pages. The pages imparting be kept light in space so that it wont take a long time for the page to load.The staring page will ask the user what kind of a user is he, either seller, buyer or a casual visitor. Based on which the future pages will be unfaltering in a sequential manner. severally listing page will have a area to put the bid, the product items with photo etc. for each one page also will have a bet engine to take care the products in stock(predicate) so that it is readily available and the user need not search for it. to each one button will have an online help link to help the user in understanding the process. 2. Hardware Interfaces A web server will be used to host the WebPages and the database management system.Most pages will be dynamic pages built with php. Each page will be optimized to the theatrical role of web browser and resolution universe used. A minimum of PIII system cut at 733 MHz will be needed to run the modules. Normal modes of net modes used in Internet engineering will be used. 3. Software Interfaces The succeeding(prenominal) message mostly includes askings for a specific task, which on the course of the development wil l be decided in detail and dealt with in design specification document. The debut messages from the messages will be converted to a specific format in the database language, the treat do and the request served.The operations will be intended to be do as fast as possible. 4. communications Interfaces The web server maintenance and other activities to be done using FTP beam protocol. The security and other issues will be dealt with in the course of the project, as there is little idea as to how these things work to our team as per now. There will other communication interfaces with the users of the site with site-specific email, forms and complaint addressable mechanisms. These things as out-of-the-way(prenominal) as possible will be automated. 4. System Features 1.Listing This includes the listing feature of the website where any search or other request of a user to a special subject is served. The pertinent web pages are loaded and the particular(prenominal) database is i nitialized. There are listings based on the priority as by user preferences. This is actually the listing of web pages to the users by time of selling, deadline, price, prime(prenominal) etc. Listing includes listing of o Products to be sold directly o Products open for bidding till a particular date o Sellers in a particular area or with specific ratings o Used products on for sale. Just casual listings of random things o Payment options to buy or sell. work on Software reaction User logs in the system The system authenticates User defines the selective information to view System provides the necessary expound as requested by the particular employee User views the information Table No 1. The table states a typical maintain passing in the system during record in Listings will be made very fast and user friendly. Proper security is also a very pertinent point here. 2. Account humans This includes creating user accounts to each of sellers and buyers separately. This incl udes taking pertinent information from them and then initializing the database. The database needs to be properly updated on each transaction by the user and all the expand of his/her account should figure in the account listing.The security of the account also should be dealt with. 3. SellingHere the seller can list his/her things on his /her quoted price. Or else he can keep it for a bidding process where he is not undisputable of the price. The inside information of which will be kept in the user database. The lucubrate of his goods on selling list will be updated to him on a regular soil to his email id. The process of selling can include some bargaining too, but the details are yet to be thought of.The payment and feed back details are kept transparent. 4. BuyingThere are 4 slipway of buying or intending to buy o Direct buying o process o Group buying o Tracking The details of which will be dealt with in the design specification. Each of these details are kept in the user account where he is kept updated about all his moves. 5. Ratings Each products, buyers and sellers are invariably rated based on the feedback and the market air so that users feel secure about the system.These ratings are given based on a best pointer of five, the details of which are yet to be worked out. These ratings are intended to bring some organized religion and credibility to the concept of an online market. 6. Others Include specie transactions, legal issues, regional tastes, costs involved, business models used etc pertinent issues but wont be seen in detail in the document as the things are beyond the reach of the design team. 5. Other Nonfunctional Requirements 1. Performance Requirements As stated before. 2.Safety Requirements Suitable safety has to be interpreted while allowing a product to be sold on buzzybuy. They have to follow the legalities of the land, and must be ethical. There could be possible misuse of the system by bogus user, bidding and buying withou t give up. It is not always possible to check the postal addresses. Also during money transactions the unreliable networks may cause hike up problems. So such practices need to be avoided. 3. Software Quality Attribute The system is easy to load and light .It adds to the persona and usability of the system. Some others quality considerations such as adaptability, availability, correctness, flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability, and usability will also be very seriously taken to consideration. 4. Business Rules nonentity is above customer satisfaction. So the rules need to be kept flexible to equalise user needs and preferences at different times. Other models can be employ but is beyond the scope of the team. . addition A Glossary 1. SRS Software requirement specification 2. GUI Graphical user interface. 3. PHP Personal home pages 4. IEEE Institute of galvanizing and electronic engineers. 5. FTP File tr ansfer protocol 6. SQL Structural query language. 7. Appendix B Analysis Models pic &8212&8212&8212&8212&8212&8212&8212 primordial touch on server Listing Selling Buying administration Administrator Casual visitor Seller Buyer Buyer Seller Casual visitor Administrator Administration Buying Selling Listing Central Processing server