Gas Agency

parcel requirement ad hocation for BuzzyBUY. com (Online Shopping and auctioning Web Site) Prep atomic number 18d by flurry of Contents 1. Introduction 2 1. social occasion 2 2. Document Conventions2 3. Int residualed Audience and adaptation Suggestions2 4. Product Scope2 5. References 2 2. Over solely Description 3 1. Product Perspective3 2. Product Functions3 3. exploiter Classes and Characteristics 3 1. Administrators 3 2. Buyers4 3. traffickers 4 4. chance(a) chit-chators4 4. material body and Implementation Constraints5 . User Documentation6 6. Assumptions and Dependencies6 3. External Interface Requirements6 1. User Interfaces6 2. Hardwargon Interfaces6 3. Softw ar Interfaces6 4. Communication Interfaces7 4. System Features7 1. inclination7 2. Account Creation8 3. interchange8 4. get8 5. Rating8 6. otherwises8 5. Other Non operating(a) Requirements9 1. Performance Requirements9 2. Safety Requirements9 3. Softw atomic number 18 Quality Attributes 9 4. Business Rules9 6. Appendix A Glossary9 7. Appendix B Analysis Models10 1. Introduction 1. Purpose The purpose of this SRS is to mean the requirements of the web based software package application buzzybuy. om, which is an online shop and pressding arranging. The module to be developed is the premier(prenominal) version of buzzybuy version 1. 0. This computer software Requirements Specification provides a complete description of exclusively the functions and specifications of buzzybuy version 1. 0 2. Document conventions IEEE standards utilise. Proper sub numbering system for sub topics based on the importance and antecedence of the matter. 3. Intended audition and reading suggestionsThe expected audience of this document is the faculty in charge of software engineering lab for 6th semester Computer Science, NITK suratkal .It fall in be utilise as a ackat onceledgement for grading in the lab for even semester of 2006. thither is no suggested reading to be done forrader going by dint of and through the document. 4. Product scope Buzzybuy. com is intentional to rill on both any contemporary platform with graphical user interface. It is assumed that the back end that ordain be used for implementation is MySQL and the front end that get out 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 hill international. 2. Overall description 1.Product perspectiveThis is proposed to be an enhanced model of the present day existent shop and auctioning portals. Many flaws in the present online shopping portals begetnt been able to exploit the upright potential of e-commerce commercialize. The Software Requirements Specifications intends to identify the flaws in the real existing system and propose an alternative or a solution to them. 2. Product Functions It consists of two modules 1. node module 2. Administrator module A node should have a exploiter neb for carrying turn out acts. Transactions include buying, sell and auctioning. Administrator provides the node with an bankers bill following proper registration procedures to foil malpractices in the transactions. both visitor is allowed to browse through the product harken, their prices and bidding procedures. Buying, selling and bidding procedures are unplowed see-through so that any exploiter is able to go through the procedures. 3. User classes and characteristics on that point are 3 kinds of substance ab drug users for the proposed system 1. Administrators They create user accounts and give it to the required customers. ? To educate consumers well-nigh Buzzybuys scarper of products and indigenous services. They must provide rules for the transactions. ? They must accommodate the web target and update the same making necessary changes at times. ? They must take care of the security issues touch on in the transactions. ? They must inform the users slightly their transaction status and keep them updated about the progress 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 up place for publicizings in the website as a receipts generating option.The place has to be maintained and proper inclinations done. ? Any failures in the system have to be discover and repaired. 2. Buyers They are the genuine customers of the website. They tooshie see the listing, bid for various things, and also buy them to various requital options. 3. Sellers These are the raft involved in selling their products through buzzybuy. They consider this as a practical(prenominal) market place. They ask to be provided with proper advertisement place, and ratings of customers. The sellers too are rated based on the feedback they array from previous transactions completed from customers.These feedback data are treated with great respect and are transparent to e very(prenominal)one. The sellers too 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 carry non have an user account. They derriere be future potential customers. They sellers good deal lure them with advertisements on the site based on their budget. The following usecase plat states the supra data in a lifelike 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 al shipway possible. There can be security risks involved. The design constraints are that the web browser at each place whitethorn not follow similar screen resolutions, browsers and so forth This can lead to the website not having the impact it is planned t o have. to a fault the rules of the land allow prohibit certain items to be change on the site. Hence all those factors need to be filtered in. Also storage space constraints may come if the listing becomes too large. Hence a strong server needs to be elect to host the database. 5.User Documentation 1. Online user swear out with all the necessary help needed 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 separately objet dart of the user interface intends to be as user friendly as possible. The fonts and liberations used allow for be intend to be very speedy and palmy to stretch out on web pages. The pages will be unplowed light in space so that it wont take a dour 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 episodic visitor. Based on which the future pages will be loaded in a sequential manner. individually listing page will have a area to put the bid, the product elaborate with expo authentic etc. Each page also will have a pursuit engine to search the products available 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 active pages built with php. Each page will be optimized to the type of web browser and resolution cosmos used. A minimum of PIII system running at 733 MHz will be needed to run the modules. Normal modes of network modes used in mesh technology will be used. 3. Software Interfaces The next message mostly includes pass alongs for a specific task, which on the course of the development will be clear-cut 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, the processing make and the request served.The operations will be intended to be made as fast as possible. 4. Communications Interfaces The web server maintenance and opposite activities to be done using FTP raptus protocol. The security and other issues will be dealt with in the course of the project, as there is little whim 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 commission addressable mechanisms. These things as far as possible will be automated. 4. System Features 1.Listing This includes the listing have got of the website where any search or other request of a user to a particular(a) athletic field is served. The pertinent web pages are loaded and the particular database is initialized. There a re listings based on the antecedency 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 listing of o Products to be sold directly o Products open for bidding coin bank a particular date o Sellers in a particular area or with specific ratings o Used products on for sale. Just insouciant 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 teaching to thought System provides the necessary expound as pass on by the particular employee User views the information Table No 1. The table states a typical mark off 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 foundation This includes creating user accounts to each of sellers and buyers separately. This includes taking pertinent i nformation 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 incessant basis to his email id. The process of selling can include virtually bargaining too, but the details are that to be thought of.The remuneration and feed back details are kept transparent. 4. BuyingThere are 4 ways of buying or intending to buy o come out buying o Bidding o theme 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 upda ted 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 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 trust and credibility to the concept of an online market. 6. Others Include capital 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 adequate 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 imitation user, bidding and buying without paying up. It is not forever possible to check the postal addresses. Also during gold transactions the unreliable networks may cause barely problems. So much(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 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 employ but is beyond the scope of the team. . Appendix A Glossary 1. SRS Software requirement specification 2. GUI Graphical user interface. 3. PHP Personal home pages 4. IEEE set of electrical and electronic engineers. 5. FTP File off protocol 6. SQL Structural query languag e. 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