英文軟件需求分析文檔模板SRS4.0

1、【精品文檔】如有侵權，請聯(lián)系網(wǎng)站刪除，僅供學習與交流英文軟件需求分析文檔模板SRS4.0.精品文檔.E-Store ProjectSoftware Requirements SpecificationVersion <4.0>Revision HistoryDateVersionDescriptionAuthor<04/13/07><1.0>SRS 1.0Group-1<04/15/07><2.0>SRS 2.0Group-1<04/15/07><3.0>SRS 3.0Group-1<04/16/07&g

2、t;<4.0>SRS 4.0Group-1Table of Contents1.Introduction51.1Purpose51.2Scope51.3Definitions, Acronyms, and Abbreviations61.4References61.5Overview62.Overall Description63.Specific Requirements73.1Functionality73.1.1Sell Configured to Ordered Products.73.1.2Provide comprehensive product details.73.

3、1.3Detailed product Categorizations73.1.4Provide Search facility.73.1.5Maintain customer profile.83.1.6Provide personalized profile83.1.7Provide Customer Support.83.1.8Email confirmation.93.1.9Detailed invoice for customer.93.1.10Provide shopping cart facility.93.1.11Provide multiple shipping method

4、s.93.1.12Online tracking of shipments93.1.13Provide online Tax Calculations103.1.14Allow multiple payment methods.103.1.15Allow online change or cancellation of order.103.1.16Allow Online Product reviews and ratings103.1.17Offer financing options.103.1.18Provide detailed sitemap.103.1.19Offer online

5、 promotions and rewards.113.1.20Online Purchase of products.113.2Usability113.2.1Graphical User Interface113.2.2Accessibility113.3Reliability & Availability113.3.1Back-end Internal Computers113.3.2Internet Service Provider113.4Performance123.5Security123.5.1Data Transfer123.5.2Data Storage123.6S

6、upportability133.6.1Configuration Management Tool133.7Design Constraints133.7.1Standard Development Tools133.7.2Web Based Product133.8On-line User Documentation and Help System Requirements133.9Purchased Components133.10Interfaces143.10.1User Interfaces143.10.2Hardware Interfaces143.10.3Software Int

7、erfaces143.10.4Communications Interfaces153.11Licensing Requirements153.12Legal, Copyright, and Other Notices153.13Applicable Standards154.Supporting Information15 Software Requirements Specification1. IntroductionThe introduction of the Software Requirements Specification (SRS) provides an overview

8、 of the entire SRS with purpose, scope, definitions, acronyms, abbreviations, references and overview of the SRS. The aim of this document is to gather and analyze and give an in-depth insight of the complete Marvel Electronics and Home Entertainment software system by defining the problem statement

9、 in detail. Nevertheless, it also concentrates on the capabilities required by stakeholders and their needs while defining high-level product features. The detailed requirements of the Marvel Electronics and Home Entertainment are provided in this document.1.1 PurposeThe purpose of the document is t

10、o collect and analyze all assorted ideas that have come up to define the system, its requirements with respect to consumers. Also, we shall predict and sort out how we hope this product will be used in order to gain a better understanding of the project, outline concepts that may be developed later,

11、 and document ideas that are being considered, but may be discarded as the product develops.In short, the purpose of this SRS document is to provide a detailed overview of our software product, its parameters and goals. This document describes the project's target audience and its user interface

12、, hardware and software requirements. It defines how our client, team and audience see the product and its functionality. Nonetheless, it helps any designer and developer to assist in software delivery lifecycle (SDLC) processes.1.2 ScopePrimarily, the scope pertains to the E-Store product features

13、for making Marvel Electronics and Home Entertainment project live. It focuses on the company, the stakeholders and applications, which allow for online sales, distribution and marketing of electronics.This SRS is also aimed at specifying requirements of software to be developed but it can also be ap

14、plied to assist in the selection of in-house and commercial software products. The standard can be used to create software requirements specifications directly or can be used as a model for defining a organization or project specific standard. It does not identify any specific method, nomenclature o

15、r tool for preparing an SRS.1.3 Definitions, Acronyms, and AbbreviationsConfigurationIt means a product which is available / Selected from a catalogue can be customized.FAQFrequently Asked QuestionsCRMCustomer Relationship ManagementRAID 5Redundant Array of Inexpensive Disk/Drives1.4 ReferencesThe r

16、eferences are:ü E-Store Structural Modelü E-Store Behavioral Modelü E-Store NFR Modelü Vision Draft 51.5 OverviewThe remaining sections of this document provide a general description, including characteristics of the users of this project, the product's hardware, and the func

17、tional and data requirements of the product.  General description of the project is discussed in section 2 of this document.  Section 3 gives the functional requirements, data requirements and constraints and assumptions made while designing the E-Store.  It also gives the user v

18、iewpoint of product.  Section 3 also gives the specific requirements of the product.  Section 3 also discusses the external interface requirements and gives detailed description of functional requirements. Section 4 is for supporting information.2. Overall DescriptionThis document contains

19、 the problem statement that the current system is facing which is hampering the growth opportunities of the company. It further contains a list of the stakeholders and users of the proposed solution. It also illustrates the needs and wants of the stakeholders that were identified in the brainstormin

20、g exercise as part of the requirements workshop. It further lists and briefly describes the major features and a brief description of each of the proposed system. The following SRS contains the detail product perspective from different stakeholders. It provides the detail product functions of E-Stor

21、e with user characteristics permitted constraints, assumptions and dependencies and requirements subsets.3. Specific Requirements The specific requirements are 3.1 FunctionalityIntroduction This subsection contains the requirements for the e-store. These requirements are organized by the features di

22、scussed in the vision document. Features from vision documents are then refined into use case diagrams and to sequence diagram to best capture the functional requirements of the system. All these functional requirements can be traced using tractability matrix. 3.1.1 Sell Configured to Ordered Produc

23、ts. The system shall display all the products that can be configured. The system shall allow user to select the product to configure. The system shall display all the available components of the product to configure The system shall enable user to add one or more componen

24、t to the configuration. The system shall notify the user about any conflict in the current configuration. The system shall allow user to update the configuration to resolve conflict in the current configuration. The system shall allow user to confirm the completion of current co

25、nfiguration3.1.2 Provide comprehensive product details. The system shall display detailed information of the selected products. The system shall provide browsing options to see product details.3.1.3 Detailed product CategorizationsThe system shall display detailed product categorizatio

26、n to the user.3.1.4 Provide Search facility.The system shall enable user to enter the search text on the screen.The system shall enable user to select multiple options on the screen to search.The system shall display all the matching products based on the searchThe system shall display only 10 match

27、ing result on the current screen.The system shall enable user to navigate between the search results.The system shall notify the user when no matching product is found on the search.3.1.5 Maintain customer profile.The system shall allow user to create profile and set his credential.The system shall

28、authenticate user credentials to view the profile.The system shall allow user to update the profile information.3.1.6 Provide personalized profileThe system shall display both the active and completed order history in the customer profile.The system shall allow user to select the order from the orde

29、r history.The system shall display the detailed information about the selected order.The system shall display the most frequently searched items by the user in the profile.The system shall allow user to register for newsletters and surveys in the profile.3.1.7 Provide Customer Support.The system sha

30、ll provide online help, FAQs customer support, and sitemap options for customer support.The system shall allow user to select the support type he wants.The system shall allow user to enter the customer and product information for the support.The system shall display the customer support contact numb

31、ers on the screen.The system shall allow user to enter the contact number for support personnel to call.The system shall display the online help upon request.The system shall display the FAQs upon request.3.1.8 Email confirmation.The system shall maintain customer email information as a required par

32、t of customer profile.The system shall send an order confirmation to the user through email.3.1.9 Detailed invoice for customer.The system shall display detailed invoice for current order once it is confirmed.The system shall optionally allow user to print the invoice.3.1.10 Provide shopping cart fa

33、cility.The system shall provide shopping cart during online purchase.The system shall allow user to add/remove products in the shopping cart.3.1.11 Provide multiple shipping methods.The system shall display different shipping options provided by shipping department.The system shall enable user to se

34、lect the shipping method during payment process.The system shall display the shipping charges.The system shall display tentative duration for shipping.3.1.12 Online tracking of shipmentsThe system shall allow user to enter the order information for tracking.The system shall display the current track

35、ing information about the order.3.1.13 Provide online Tax CalculationsThe system shall calculate tax for the order.The system shall display tax information for the order.3.1.14 Allow multiple payment methods.The system shall display available payment methods for payment.The system shall allow user t

36、o select the payment method for order.3.1.15 Allow online change or cancellation of order.The system shall display the orders that are eligible to change.The system shall allow user to select the order to be changed.The system shall allow user to cancel the orderThe system shall allow user to change

37、 shipping, payment method.The system shall notify the user about any changes made to the order.3.1.16 Allow Online Product reviews and ratingsThe system shall display the reviews and ratings of each product, when it is selected.The system shall enable the user to enter their reviews and ratings.3.1.

38、17 Offer financing options.The system shall display all the available financing options.The system shall allow user to select the financing option.The system shall notify the use about the financing request.3.1.18 Provide detailed sitemap.The system shall allow user to view detailed sitemap.3.1.19 O

39、ffer online promotions and rewards.The system shall display all the available promotions to the user.The system shall allow user to select available promotion.3.1.20 Online Purchase of products.The system shall allow user to confirm the purchase.The system shall enable user to enter the payment info

40、rmation.3.2 Usability3.2.1 Graphical User InterfaceThe system shall provide a uniform look and feel between all the web pages.The system shall provide a digital image for each product in the product catalog.The system shall provide use of icons and toolbars.3.2.2 AccessibilityThe system shall provid

41、e handicap access.The system shall provide multi language support.3.3 Reliability & Availability 3.3.1 Back-end Internal ComputersThe system shall provide storage of all databases on redundant computers with automatic switchover.The system shall provide for replication of databases to off-site s

42、torage locations.The system shall provide RAID V Disk Stripping on all database storage disks.3.3.2 Internet Service ProviderThe system shall provide a contractual agreement with an internet service provider for T3 access with 99.9999% availability.The system shall provide a contractual agreement wi

43、th an internet service provider who can provide 99.999% availability through their network facilities onto the internet.3.4 PerformanceThe product shall be based on web and has to be run from a web server.The product shall take initial load time depending on internet connection strength which also d

44、epends on the media from which the product is run.The performance shall depend upon hardware components of the client/customer. 3.5 Security3.5.1 Data TransferThe system shall use secure sockets in all transactions that include any confidential customer information.The system shall automatically log

45、 out all customers after a period of inactivity.The system shall confirm all transactions with the customers web browser.The system shall not leave any cookies on the customers computer containing the users password.The system shall not leave any cookies on the customers computer containing any of t

46、he users confidential information.3.5.2 Data StorageThe customers web browser shall never display a customers password. It shall always be echoed with special characters representing typed characters.The customers web browser shall never display a customers credit card number after retrieving from t

47、he database. It shall always be shown with just the last 4 digits of the credit card number.The systems back-end servers shall never display a customers password. The customers password may be reset but never shown.The systems back-end servers shall only be accessible to authenticated administrators

48、.The systems back-end databases shall be encrypted.3.6 Supportability3.6.1 Configuration Management ToolThe source code developed for this system shall be maintained in configuration management tool.3.7 Design Constraints3.7.1 Standard Development ToolsThe system shall be built using a standard web

49、page development tool that conforms to either IBMs CUA standards or Microsofts GUI standards.3.7.2 Web Based Product         There are no memory requirements         The computers must be equipped with web browsers such as Interne

50、t explorer.         The product must be stored in such a way that allows the client easy access to it.         Response time for loading the product should take no longer than five minutes.       

51、0; A general knowledge of basic computer skills is required to use the product 3.8 On-line User Documentation and Help System RequirementsAs the product is E-store, On-line help system becomes a critical component of the system which shall provide It shall provide specific guidelines to a user for u

52、sing the E-Store system and within the system. To implement online user help, link and search fields shall be provided. 3.9 Purchased ComponentsNot Applicable3.10 InterfacesThere are many types of interfaces as such supported by the E-Store software system namely; User Interface, Software Interface

53、and Hardware Interface.The protocol used shall be HTTP.The Port number used will be 80.There shall be logical address of the system in IPv4 format.3.10.1 User InterfacesThe user interface for the software shall be compatible to any browser such as Internet Explorer, Mozilla or Netscape Navigator by

54、which user can access to the system.The user interface shall be implemented using any tool or software package like Java Applet, MS Front Page, EJB etc.3.10.2 Hardware InterfacesSince the application must run over the internet, all the hardware shall require to connect internet will be hardware interface for the system. As for e.g. Modem, WAN LAN, Ethernet Cross-Cable.3.10.3 Software Interfaces1. The e-store system shall communicate w