Gas Agency

package requirement specification for BuzzyBUY. com (Online Shopping and auctioning Web Site) brisk by T competent of Contents 1. Introduction 2 1. invention 2 2. Document Conventions2 3. Intended Audience and Reading Suggestions2 4. Product Scope2 5. References 2 2. overall Description 3 1. Product Perspective3 2. Product Functions3 3. User Classes and Characteristics 3 1. Administrators 3 2. purchasers4 3. Sellers 4 4. Casual visitors4 4. anatomy and Implementation Constraints5 . User Documentation6 6. Assumptions and Dependencies6 3. External porthole Requirements6 1. User Interfaces6 2. Hardw argon Interfaces6 3. com go underer softwargon Interfaces6 4. Communication Interfaces7 4. System Features7 1. Listing7 2. nib Creation8 3. merchandising8 4. get8 5. Rating8 6. others8 5. some other Non Functional Requirements9 1. Performance Requirements9 2. Safety Requirements9 3. bundle Quality Attributes 9 4. logical argument Rules9 6. auxiliary A Glossary9 7. Appendix B Analysis Models10 1. Introduction 1. Purpose The purpose of this SRS is to specify the requirements of the web based package application buzzydeal. om, which is an online shop and command brass. The mental faculty to be developed is the first rendering of buzzy demoralise magnetic variation 1. 0. This Softw ar Requirements Specification provides a complete description of all the functions and specifications of buzzybuy version 1. 0 2. Document conventions IEEE standards use. prim wedge heel numbering system for sub topics based on the importance and antecedence of the matter. 3. Intended audience and class period suggestionsThe expected audience of this document is the faculty in charge of softw ar engineering lab for 6th semester Computer Science, NITK suratkal .It get out be used as a reference for grading in the lab for perpetual(a) semester of 2006. thither is no suggested reading to be done before departure through the document. 4. Product scope Buzzybuy. com is designed to flood on both(prenominal) any modern platform with GUI. It is assumed that the back end that leave be used for implementation is MySQL and the front end that will be used is PHP. 5. References 1. The applicable IEEE standards are published in IEEE standards collection, 2001 edition. 2. Software Engineering, A Practitioners approach, 6th edition. By Roger S Pressman. McGraw cumulation international. 2. Overall description 1.Product perspectiveThis is proposed to be an enhanced model of the resign day existing obtain and auctioning portals. Many flaws in the present online shopping portals havent been able to exploit the full potential of e-commerce market. The Software Requirements Specifications intends to identify the flaws in the current existing system and propose an choice or a solution to them. 2. Product Functions It consists of two modules 1. Customer module 2. Administrator module A node should have a drug exploiter explanation for carrying out transa ctions. Transactions include buying, sell and auctioning. Administrator provides the customer with an account embodying good registration procedures to prevent malpractices in the transactions. all visitor is allowed to browse through the product list, their prices and bidding procedures. get, selling and bidding procedures are unploughed transparent so that any user is able to go through the procedures. 3. User classes and characteristicsThere are 3 kinds of users for the proposed system 1. Administrators They stimulate user accounts and give it to the required customers. ? To educate consumers about Buzzybuys come in of products and indigenous services. They must provide rules for the transactions. ? They must maintain the web target and update the kindred making necessary changes at times. ? They must take care of the credential issues involved in the transactions. ? They must inform the users about their transaction positioning and lapse them updated about the pro gress 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 business. ? Keep place for advertisements in the website as a revenue generating option.The place has to be maintained and proper tilts done. ? Any failures in the system have to be detected and repaired. 2. Buyers They are the genuine customers of the website. They evict see the tilt, bid for various things, and also buy them to various payment options. 3. Sellers These are the people involved in selling their products through buzzybuy. They consider this as a virtual market place. They carry to be provided with proper advertisement place, and ratings of customers. The venders too are rated based on the feedback they get from previous transactions completed from customers.These feedback data are hard-boiled with great respect and are transparent to e genuinelyone. The sellers too value thi s real 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 need non have an user account. They can be rising 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 checking the genuineness of the buyer, which is not always workable. There can be auspices risks involved. The design constraints are that the browser at each place may not follow similar screen resolutions, browsers etc. This can lead to the website not having the shock absorber it is planned to have. as well as the rules of the land will prohibit certain items to be sold on the site. and then(prenominal) all those factors need to be filtered in. Also stora ge space constraints may come if the listing becomes too large. Hence a strong boniface needs to be chosen to drove the database. 5.User Documentation 1. Online user stand by with all the necessary help inevitable to use the site in a bulletin 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 now 3. External Interface Requirements 1. User Interfaces from each one part of the user interface intends to be as user kind as possible. The fonts and buttons used will be intended to be very fast and easygoing to load on web pageboys. The pages will 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, any seller, buyer or a quotidian visitor. Based on which the future pages will be loaded in a sequential manner. distributively listing page will have a rural area to put the bid, the product expand with photo etc. Each page also will have a research engine to search the products visible(prenominal) so that it is readily available and the user need not search for it. Each 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 role of web browser and resolution being used. A minimum of PIII system running at 733 MHz will be needed to run the modules. Normal modes of network modes used in Internet technology will be used. 3. Software Interfaces The incoming message mostly includes requests for a specific task, which on the course of the development will be decided in detail and dealt with in design specification document. The incoming messages from the messages will be converted to a specific format in the database language, th e processing do and the request served.The operations will be intended to be do as fast as possible. 4. Communications Interfaces The web server sustainment and other activities to be done using transfer transfer 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 far 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 particular subject is served. The relevant web pages are loaded and the particular database is initialized. 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, quality etc. Listing includes l isting 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. Action Software reaction User logs in the system The system authenticates User defines the reading to view System provides the necessary details as requested by the particular employee User views the information Table No 1. The table states a typical control passing in the system during logging in Listings will be made very fast and user friendly. Proper security is also a very pertinent point here. 2. Account creation This includes creating user accounts to each of sellers and buyers separately. This includes 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 details 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 sure of the price. The details of which will be kept in the user database. The details of his goods on selling list will be updated to him on a regular basis to his email id. The process of selling can include nigh bargaining too, but the details are yet to be survey of.The payment and feed back details are kept transparent. 4. BuyingThere are 4 ways of buying or intending to buy o Direct buying o Bidding o sort 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 constantly rated based on the feedback and the market behavior so that users observe secure about the system.These ratings are given based on a best po inter of five, the details of which are yet to be worked out. These ratings are intended to bring some trust and credibility to the concept of an online market. 6. some others accommodate funds 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 taken 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 without paying up. It is not always possible to check the postal addresses. Also during money transactions the unreliable networks may cause further problems. So such(prenominal) practices need to be avoided. 3. Software Quality Attribute The system is easy to load and light .It adds to the quality 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 sector Rules Nothing is above customer satisfaction. So the rules need to be kept flexible to meet user needs and preferences at different times. Other models can be applied but is beyond the scope of the team. . Appendix A Glossary 1. SRS Software requirement specification 2. GUI vivid user interface. 3. PHP Personal home pages 4. IEEE Institute of electrical and electronic engineers. 5. FTP File transfer protocol 6. SQL Structural query language. 7. Appendix B Analysis Models pic Central Processing server Listing Selling Buying Administration Administrator Casual visitor Seller Buyer Buyer Seller Casual visitor Administrator Administration Buying Selling Listing Central Processing server