Software Requirements Specification for E-Business Srt Str - Case Study Example

Software Requirements Specification For SRS (Е-Businеss Sроrt Stоrе) Prepared by Table of Contents 1.Introduction 3 1.1Purpose 3 1.2Document Conventions 3 1.3Intended Audience and Reading Suggestions 3 1.4Project Scope 4 1.5References 4 2.Overall Description 5 2.1Product Perspective 5 2.2Product Features 6 2.3User Classes and Characteristics 6 2.3.1User/buyer 6 2.3.2Customer service 7 2.3.3Inventory 7 2.3.4E-store 7 2.3.5Shipping department 7 2.3.6Guru 8 2.3.7Sales department 8 2.3.8Vendor 8 2.4Class diagram 8 2.5Operating Environment 10 2.6Design and Implementation Constraints 11 2.7User Documentation 11 2.8Assumptions and Dependencies 11 3.System Features 12 3.1System Feature 1 12 3.1.1Buyer Use Cas 12 3.1.2Description and Priority 13 3.1.3Stimulus/Response Sequences 14 3.1.4Functional Requirements 14 4.External Interface Requirements 14 4.1User Interfaces 14 4.2Hardware Interfaces 15 4.3Software Interfaces 15 4.4Communications Interfaces 16 5.Other Nonfunctional Requirements 16 5.1Performance Requirements 16 5.2Safety Requirements 17 5.3Security Requirements 17 5.4Software Quality Attributes 17 6.Other Requirements 17 Revision History Name Date Reason For Changes E-business sports store 09/28/13 First draft 1. Introduction 1.1 Purpose This SRS is a description on the major speculations and requirements of sports center store. It gives explanations on the functional features involved in development of the sports center store design constraints, scheduling, interface details, and other related considerations such like performance characteristics. This SRS is planned for the E-business store to organize for its scheduling to raise the owner’s performance, cluster management, job scheduling and provide useful grid resources. 1.2 Document Conventions The given requirements in this report, stated otherwise should be taken and assumed as being in the project scope providing all relevant requirements in the project and as being of high priority 1.3 Intended Audience and Reading Suggestions Testers, developers, stakeholders, project manager as well as the project team are the main audience that is intended. Generally, the intended audience should read on the purpose, scope, system features, and general overview that relate to this document. 1.4 Project Scope The sports center store scheduler is destined to serve as an additional means to scheduling, resource management, and queuing. The scheduler offers an economy that is market based to drive a self-management scheduling time management and not to include performance consideration. Hence, sports center store aims at providing quality of service controlled economy using a cluster of computing. Sports Centre store in this project is only to manage the successive and parallel functionalities that are adaptable in developing a heterogeneous system cluster. According to the mechanism used in this system users will have an option to interact and bargain with each other, which provides an environmentally friend grid computing. This system is more specially designed to appropriate editors to deal and convey information to the relevant group of reviewers to manage the online purchasing as well as maintain the website as public as possible. In addition, the software is made to alleviate communication between viewers, reviewers, authors, and the editor, through a variety of messaging either email or test messages. Moreover, the system is set to be in a configurable location where the system forms are easily accessible for maintenance. of these forms is configurable via the application’s maintenance options. 1.5 References [1] Michael, J. & Michael, J. J., (1995). Software requirements & specifications: a lexicon of practice, principles, and prejudices. London: ACM Press. books.google.co.ke/books?isbn=1464967601[accessed of 09/26/2013) [2] Ashton, Q., (Jan 9, 2012). Issues in Innovation, Indicators, and Management in Technology: 2011Edition. Georgia: Scholarly Editions. [3] Karl, E. W., (2009). Software Requirements. Massachusetts: O'Reilly Media. 2. Overall Description 2.1 Product Perspective In general, sport center store will be solely online, thus it shall include all features that the business will requires for its users to have easy access. Thus, when searching the desired product the user will have an option to follow up their preferred product. Overall the system has different sections that include different asset optimization in all levels of business management. As a matter of fact, it would be necessary to include the overall systemic other pages such like tweeter, Facebook, youtude, linkedin and any other source of managerial data information. A specific product will define the overall efficiency in the system. 2.2 Product Features The e-business sports center store focuses on quality online sales of the sports commodities that provide satisfaction to the customers. These products should be complete, easy to track, reliable products, high quality, versatile and utilizes resource in tracking. 2.3 User Classes and Characteristics In this SRS it includes different classes of users: 2.3.1 User/buyer Basically this is the buyer who has the purchasing power. Characteristics Have the option to register as a buyer in the e-store; They can apply for the order, credit, and option to add to cart, can check order status; Request for advice, can customize their page depending on the product they need to purchase; and They pay for the purchased product prior to delivery. 2.3.2 Customer service Provides services to the customer in finding what they want to purchase They varnish the customers with the reliable information on how to get advice, support, return item and find store. 2.3.3 Inventory This provides the list of items in the store and provides the customers with: Update on search catalog, give the customer with purchase inventory, comparing items, return item and get item details. 2.3.4 E-store The e-store has verification for customers, customers can request support, assist the customers to find store, registration, provides the customer with purchase data, and other customer-product related options. 2.3.5 Shipping department This class provides services in item shipment, checking shipment information, checking availability of the item, and receives item. 2.3.6 Guru In this class, the customers get advice, and the guru has provision for customer advice and customizes the e-store. 2.3.7 Sales department The sales department checks the customer credits, update ads, track the order, return the item and customize the product details as per the customer request. 2.3.8 Vendor They buy items and restock the e-store 2.4 Class diagram The diagram below is presentation of high class level of an e-store for the e-business sports center store. The diagram gives a relationship between a number of different departments, including the store, and the customer or the user. Each department has its specific functions with the e-store has having a maximum of the activities that play across it. Figure 2: Class diagram 2.5 Operating Environment The sport Centre store business has a number of actors as well an additional active cooperating system. The authors, the reviewers or readers of the business provisions have an access from online using internet as the main source of communication with not power to control the system. On the other hand, the editors have a direct access to the system and have full control of the system directly. Precisely, the system has a link that is existing to provide an historical society about the business. This is available at the in the web publishing system and it has two components, the article manager and an online journal, the two uses domain classes in making the explanation more clear. 2.6 Design and Implementation Constraints When designing the system, system developers are likely to face changes and constraints corporate policies that relate to E-business websites. In regard to this, the developers will have to deal with hardware limitations provided there in the system. Not only will the developers face the challenges in hardware but they will have language issues, since many users use different languages.in setting up the database interface, the business owners will have to meet the customer’s requirements while planning on the design conventions as well as the standards required in programing. 2.7 User Documentation The sports center store will have a user agreement page, where the customers will have free access to user manuals, tutorials on how to purchase and on-line help to the customers. There are purchase agreement documents as well as requirements of purchase and customer relations agreement with the seller. 2.8 Assumptions and Dependencies Generally, the sports Centre store will purely rely on past E-business stores. Thus it is assumed that there will be less competition in the market considering that, this store is one of its types and has a variety of products form different manufacturers for different users. Additionally, it is assumed that the business will have a smooth customer flow throughout. The sports center store being online it will mean it has to focus on applying internet connection continuously. Thus the system will require an external server where connection cannot be terminated or altered. Therefore, it will have to outsource third party internet providers who will ensure smooth running of the business. However, the business must rely on the online management to control the customer flow as well watch the phising activities on the website. 3. System Features 3.1 System Feature 1 3.1.1 Buyer Use Cas 3.1.1.1 Use case: buy product Diagram: Description The buyer has to access the online store to make and order and purchase his/her product. . Step-By-Step Description Prior to using this case the buyer ought to have an internet connection and be in the access window of the e-business store to view the products. 1. The buyers selects the search option; 2. The buyer enters the keywords option for the product to purchase; 3. The buyer selects the product to purchase from the list of the available products in the store; 4. The buyer check the purchase agreement form; and 5. The buyer places an order on the product to purchase. 3.1.1.2 Send Recommendation use cases: Use case: deliver the product This use case extends the Update Article use case. Diagram: Brief Description The seller ensures safe delivery of the product to the customer. Step-By-Step Description Prior to delivery, the seller should have already accessed the e-business store to confirm the delivery details to allow the seller to deliver the product purchased. 3.1.2 Description and Priority The customer has to determine how to prioritize his/her purchase schedule. Thus, the products are placed as of high, medium, or low priority when making the purchase, giving it a scale of relativity. 3.1.3 Stimulus/Response Sequences The client (customer) will need to get the product purchase agreement that guarantees safe delivery of the purchased products. Hence, the system will provide such a provision to allow the customer to read the agreement on the terms of purchase and delivery of the product. 3.1.4 Functional Requirements The terms of agreement between the buyers must be precise and clearly stated to avoid conflict in business between the two as well as loss of trust from the buyer to the seller. Considering the sports center store as an online shop, there will be different opinions from the buyers, which will either build or destroy the business. 4. External Interface Requirements 4.1 User Interfaces Basically, the sports center store website will be user friendly for all the users to have an easy access to the options provide. The only constraints that the customer may experience are the procedure to follow and how to complete with different provisions as provided in the mode of payment. There will be user manual provided in the download option to help the buyer on how to complete a single purchase and the requirements prior to making an order. This will include help options, keyboard shortcuts, error messages and display options (figure 5). Figure 4: user interfaces 4.2 Hardware Interfaces Customers using the system will need to have basic knowledge on the hardware usage as well as software applications and how they are used in different environments. When purchasing the products, the buyer will have to confirm the language to use and the operating system that the software is used. Thus, for the customer, to have control on the system device they will need to learn about the device types used in the system, nature of the data and how the system will accommodate different software interface. 4.3 Software Interfaces When using this version (e-business store application version 1.10), it will be easy to use it Windows NT, 98, xp, vista, 7, and linux, and other operating system. It has simple interface from installation offline, although it will require internet connection for connection and activation to view the store. In addition, it will have to include all user documents that the client will require visit prior to making any move to start a purchase from the store. This software interface will be set to include all the possible options and search engine optimization features to aid the customer in making any transaction. 4.4 Communications Interfaces The interfaces provided there in the software are set to have all messaging options ranging from basic HTML, HTML, and free text to serve the customers efficiently and effectively. When the customer requires more information there will be a need to use FTP of HTTP options to relay more information that the customer may deem necessary to acquire the information. In data transfer, there will always be secure transmission between the customer and the seller through secure communication system. 5. Other Nonfunctional Requirements 5.1 Performance Requirements Essentially, the customer needs will have to be met by ensuring that: Any transaction will not take longer than 10 seconds; Any transaction will be secure and the customer will have to create a user account to receive and authentication code; For quality service all products purchased will be delivered to the customer within a maximum of 72 hours of dispatch; Customer is free to enquire about the transportation details on the product purchased; and The seller or buyer will be liable for conveying the transaction codes to the third party. 5.2 Safety Requirements For the e-business transaction to succeed the customer and the seller will have to comply with the regulations against money fraud. Therefore, the client will need to provide specific identify information that will be used to identify their location. The customer will have to agree to the set terms of delivery of the products. 5.3 Security Requirements The e-business store webpage will have to use more data security options against hacking and internet scam. Information on any transitions from the customers must remain intact and as a secret to the third party. 5.4 Software Quality Attributes If possible the business should adopt the customer service chatter that is: 1. Adaptable to the customer requirements; 2. Available on request to serve and deliver to the customer; 3. Ready to provide correct information the customer; 4. Flexible to serve the customer demands regardless of time and place; 5. Provide portable products to the customers; 6. Be consistent in providing usable information to the customer; and 7. Able to maintain the information as updated as possible However, the customer should be able to comprehend to any information provide there in the store, and be at a position to understand all the set terms purchase agreement. 6. Other Requirements Customers can access the store by searching the E-business sports store from any search engine and be at a position to acquire the relevant information that may deem necessary in purchasing of the products. Customers should provide identity information that will not threaten the delivery of the purchased products from the store. Appendix A: Glossary Terms used: SRS software requirement specifications User Id: identity of the user User password: password that the user requires to login to the system Appendix B: Analysis Models Figure 1: is a clear analysis on the system information and the deliverables from the system Figure 3: defines an analysis on how the buyer and seller interact from search to delivery of the products. Figure 5, is an analysis on how the user interface appears in the entire system Appendix C: Issues List Pending decisions: - there is a need to plan on the mode on delivery to the customer in different locations. Information required: - there is yet a research to determine the user information from varying locations as their preferences in such locations Conflicts: - there is a conflict between the developers and the management on the basis of maintenance security and operation of the business. Should the webpages be compromised, who is responsible for the damage caused? Read More