This action might not be possible to undo. Are you sure you want to continue?
com (Online Shopping and auctioning Web Site)
Performance Requirements 5. User Classes and Characteristics 3 2. Communication Interfaces System Features 4. Overall Description 2.3.6. External Interface Requirements 3.5.1. Hardware Interfaces 3.3.2.com . Administrators 2. Intended Audience and Reading Suggestions 2 1.1. Design and Implementation Constraints 2.2.3. Sellers 2. Assumptions and Dependencies 6 3.4.1. Product Functions 2. References 2. Page 2 of 10 Software Requirement Specification –BuzzyBuy.1.3. 6. Software Interfaces 3. Buying 4. User Documentation 2. User Interfaces 22.214.171.124.1.3. Introduction 2 1.2.3. Listing 4.4.4. Account Creation 4. Document Conventions 1.5. Purpose 2 1. Safety Requirements 5. Product Scope 1.1. Business Rules Appendix A: Glossary Appendix B: Analysis Models Table of Contents 2 2 2 3 3 3 3 4 4 4 5 6 6 6 6 6 7 7 7 8 8 8 8 9 9 9 9 9 9 10 8 4. Software Quality Attributes 5.2.3. Rating 4. Product Perspective 2. Selling 4.2. 5.3.4. 7.6.4. Buyers 2. Casual visitors 2.1. Others Other Non Functional Requirements 5.5.3.
0. By Roger S Pressman.1. Product scope: Buzzybuy. McGraw hill international. This Software Requirements Specification provides a complete description of all the functions and specifications of buzzybuy –version 1.com . A Practitioner’s approach.2. The expected audience of this document is the faculty in charge of software engineering lab for 6th semester Computer Science.3. 2001 edition.4.0 1. 1. The applicable IEEE standards are published in “IEEE standards collection”. It is assumed that the back end that will be used for implementation is MySQL and the front end that will be used is PHP.Introduction: 1.1.com. The module to be developed is the first version of buzzybuy –version 1. NITK suratkal . both any modern platform with GUI. Page 3 of 10 Software Requirement Specification –BuzzyBuy. Document conventions: IEEE standards used.com is designed to run on 1. Intended audience and reading suggestions: 1. References: 1.It will be used as a reference for grading in the lab for even semester of 2006. Software Engineering. 6th edition. 1. Purpose: The purpose of this SRS is to specify the requirements of the web based software application buzzybuy.126.96.36.199. Proper sub numbering system for sub topics based on the importance and priority of the matter.There is no suggested reading to be done before going through the document. which is an online shopping and bidding system.1.
selling and bidding procedures are kept transparent so that any user is able to go through the procedures.com . • Administrator provides the customer with an account following proper registration procedures to prevent malpractices in the transactions. Customer module 2.3. 2.1.2. selling and auctioning. Product perspective: This is proposed to be an enhanced model of the present day existing shopping and auctioning portals. • Buying. Product Functions: • It consists of two modules 1. They must maintain the website and update the same making necessary changes at times.2. • Transactions include buying. They must take care of the security issues involved in the transactions. Overall description 2. Page 4 of 10 Software Requirement Specification –BuzzyBuy. Many flaws in the present online shopping portals haven’t been able to exploit the full potential of e-commerce market. 2. They must inform the users about their transaction status and keep them updated about the progress through emails. They must provide rules for the transactions. Administrator module • A customer should have a user account for carrying out transactions. • Any visitor is allowed to browse through the product list. their prices and bidding procedures. Administrators: They create user accounts and give it to the required customers. To educate consumers about Buzzybuy’s range of products and indigenous services.1. The Software Requirements Specifications intends to identify the flaws in the current existing system and propose an alternative or a solution to them.3. User classes and characteristics There are 3 kinds of users for the proposed system 2.
Buyers: They are the genuine customers of the website. They need to be provided with proper advertisement place. These feedback data are treated with great respect and are transparent to everyone. Sellers: These are the people involved in selling their products through buzzybuy.com . They must receive feedbacks from their customers or any users about their system and act upon the relevant ones. Keep place for advertisements in the website as a revenue generating option. Page 5 of 10 Software Requirement Specification –BuzzyBuy. They need not have an user account. They sellers can lure them with advertisements on the site based on their budget. The sellers too are rated based on the feedback they get from previous transactions completed from customers. 2. The place has to be maintained and proper listings done. The sellers too value this very highly. They can see the listing. and also buy them to various payment options. Look up at all the legal issues involved with the business. They can be future potential customers.4. Any failures in the system have to be detected and repaired. They consider this as a virtual market place. and ratings of customers. They just visit to see the listing and too see the products. 2.3.3. bid for various things. 188.8.131.52. Casual visitors: These people don’t come to the site on specific intensions of buying or selling.
com . which is not always possible. Hence all those factors need to be filtered in.The following usecase diagram states the above data in a graphical form: Casual visitor Central Processing server Listing Selling Seller Buying Administrator Buyer Administration Fig 1 Usecase Diagram for BuzzyBuy 2. • The design constraints are that the browser at each place may not follow similar screen resolutions. This can lead to the website not having the impact it is planned to have. Design and Implementation Constraints • The main constraint here would be the checking the genuineness of the buyer. Page 6 of 10 Software Requirement Specification –BuzzyBuy. • Also the rules of the land will prohibit certain items to be sold on the site. Hence a strong server needs to be chosen to host the database. browsers etc. • Also storage space constraints may come if the listing becomes too large.4. There can be security risks involved.
Problem addressable forms 2. A minimum of PIII system running at 733 MHz will be needed to run the modules. External Interface Requirements: 3. Normal modes of network modes used in Internet technology will be used. 184.108.40.206. which on the course of the development will be decided in detail and dealt with in design specification document.5. The staring page will ask the user what kind of a user is he. The pages will be kept light in space so that it won’t take a long time for the page to load.1. Online user help with all the necessary help needed to use the site in a bulletin format.2. Hardware Interfaces: A web server will be used to host the WebPages and the database management system.5. Each listing page will have a area to put the bid. Software and database specification 2.5. User Documentation: 2. Each button will have an online help link to help the user in understanding the process. Most pages will be dynamic pages built with php.4. Each page will be optimized to the type of web browser and resolution being used. The incoming Page 7 of 10 Software Requirement Specification –BuzzyBuy.com . 2. 2. Assumptions and Dependencies None as per now 3. buyer or a casual visitor. Each page also will have a search engine to search the products available so that it is readily available and the user need not search for it. The fonts and buttons used will be intended to be very fast and easy to load on web pages. User Interfaces: Each part of the user interface intends to be as user friendly as possible.1. the product details with photo etc. Details of rules and regulation to sellers as well as buyers. either seller.2.6.3. Based on which the future pages will be loaded in a sequential manner. Software Interfaces: The incoming message mostly includes requests for a specific task.5. 3.
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. price. This is actually the listing of web pages to the users by time of selling. 3. The operations will be intended to be made as fast as possible. the processing made and the request served. There will other communication interfaces with the users of the site with site-specific email.messages from the messages will be converted to a specific format in the database language. 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. forms and complaint addressable mechanisms.The table states a typical control passing in the system during logging in Software reaction The system authenticates System provides the necessary details as requested by the particular employee Page 8 of 10 Software Requirement Specification –BuzzyBuy. 4.System Features 4. These things as far as possible will be automated. as there is little idea as to how these things work to our team as per now. o Just casual listings of random things o Payment options to buy or sell. quality etc.4. deadline. The pertinent web pages are loaded and the particular database is initialized. There are listings based on the priority as by user preferences. The security and other issues will be dealt with in the course of the project.com . Action User logs in the system User defines the information to view User views the information Table No 1. Communications Interfaces: The web server maintenance and other activities to be done using FTP transfer protocol.
2. costs involved. The security of the account also should be dealt with. This includes taking pertinent information from them and then initializing the database. Each of these details are kept in the user account where he is kept updated about all his moves. legal issues. The process of selling can include some bargaining too.4. The details of which will be kept in the user database. Others: Include money transactions.5.Listings will be made very fast and user friendly. the details of which are yet to be worked out. Account creation: This includes creating user accounts to each of sellers and buyers separately. 4. Buying: There are 4 ways of buying or intending to buy o Direct buying o Bidding o Group buying o Tracking The details of which will be dealt with in the design specification. Page 9 of 10 Software Requirement Specification –BuzzyBuy. 4. These ratings are intended to bring some trust and credibility to the concept of an online market. 4. Or else he can keep it for a bidding process where he is not sure of the price. The details of his goods on selling list will be updated to him on a regular basis to his email id. 4. Ratings: Each products. business models used etc pertinent issues but won’t be seen in detail in the document as the things are beyond the reach of the design team. Selling: Here the seller can list his/her things on his /her quoted price.6. 4. These ratings are given based on a best pointer of five.3. but the details are yet to be thought of. The payment and feed back details are kept transparent. Proper security is also a very pertinent point here. 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. regional tastes. buyers and sellers are constantly rated based on the feedback and the market behavior so that users feel secure about the system.com .
Software Quality Attribute: The system is easy to load and light . availability. Other models can be applied but is beyond the scope of the team. reliability.2. and must be ethical.4. So the rules need to be kept flexible to meet user needs and preferences at different times.com . Page 10 of 10 Software Requirement Specification –BuzzyBuy. correctness. flexibility. 5. 6.5. FTP: File transfer protocol SQL: Structural query language. They have to follow the legalities of the land. 6. 6. interoperability. 6.6. portability. SRS: Software requirement specification GUI: Graphical user interface. There could be possible misuse of the system by bogus user. robustness. 5.3.2. Other Nonfunctional Requirements: 5. It is not always possible to check the postal addresses. 5.It adds to the quality and usability of the system. Safety Requirements: Suitable safety has to be taken while allowing a product to be sold on buzzybuy. Also during money transactions the unreliable networks may cause further problems. PHP: Personal home pages IEEE: Institute of electrical and electronic engineers. 6. Business Rules: Nothing is above customer satisfaction.1. Appendix A: Glossary 6. Performance Requirements: As stated before.5. Some others quality considerations such as adaptability.3. So such practices need to be avoided. bidding and buying without paying up. testability. maintainability. and usability will also be very seriously taken to consideration. reusability. 6.1.4.
com . Appendix B: Analysis Models Casual visitor Central Processing server Listing Selling Seller Buying Administrator Buyer Administration Page 11 of 10 Software Requirement Specification –BuzzyBuy.7.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.