System Prospectus- IE



Project:Aqua Duck/Online Merchandising Company (OMC)Team No.:Team 1Class:CSE 3310; Spring 2010 Module:System Requirements Analysis (SRA)Deliverable:SRA DocumentVersion:[1.2]Date:[05/03/2010]Contributors:Jason BeereJustin HundtJuan PlacenciaSandip ShresthaRevision HistoryVersion numberDateOriginatorReason for changeHigh level description of changes1.003/04/2010Team 1Initial draft1.104/01/2010Team 1Modificaions per Dr. Khalili’s requestProject Context Diagram: add order status & add reports Assumptions & Constraints: add credit card constraintDelivery & Schedule: rearrange table1.205/03/2010Team 1Design Change ModificationsSearch 2: removed display item IDShopping 1: remove modify shipping informationInventory Management 1: remove sort items by category; remove Item quantity (on order)Inventory Management 3: remove item quantity (on order)Checkout: remove checkout cancel for empty shopping cart during registration; remove more items order than availableSales Data: remove projected salesWebsite Management: remove on sale item flagCheckout UML: remove check login conditionTABLE OF CONTENTS TOC \o "1-4" \h \z 1. Introduction & Project Overview PAGEREF _Toc255473582 \h 32. Objectives PAGEREF _Toc255473583 \h 42.1 BUSINESS Objectives PAGEREF _Toc255473584 \h 42.2 SYSTEM Objectives PAGEREF _Toc255473585 \h 54. Systems Requirements PAGEREF _Toc255473586 \h 74.1 Requirements Overview PAGEREF _Toc255473587 \h 74.2 Login/Registration Requirements PAGEREF _Toc255473588 \h 74.3 Account Maintenance Requirements PAGEREF _Toc255473589 \h 84.4 Search Requirements PAGEREF _Toc255473590 \h 94.5 Shopping Cart Requirements PAGEREF _Toc255473591 \h 114.6 Inventory Management Requirements PAGEREF _Toc255473592 \h 124.7 Checkout Requirements PAGEREF _Toc255473593 \h 154.8 Sales Data Requirements PAGEREF _Toc255473594 \h 164.9 Website Management Requirements PAGEREF _Toc255473595 \h 175. Software Processes and Infrastructure PAGEREF _Toc255473596 \h 185.1 Hardware and Infrastructure PAGEREF _Toc255473597 \h 185.2 UML Diagrams PAGEREF _Toc255473598 \h 185.3 Conceptual Data Model – Database PAGEREF _Toc255473599 \h 235.4 Screen Shots PAGEREF _Toc255473600 \h 245.5 Test Plan PAGEREF _Toc255473601 \h 246. Assumptions and Constraints PAGEREF _Toc255473602 \h 256.1 Assumptions PAGEREF _Toc255473603 \h 256.2 Constraints PAGEREF _Toc255473604 \h 256.3 Out of Scope material PAGEREF _Toc255473605 \h 257. Delivery and Schedule PAGEREF _Toc255473606 \h 268. Stakeholder Approval Form PAGEREF _Toc255473607 \h 27Appendix: PAGEREF _Toc255473608 \h 281. Introduction & Project OverviewJ3S (Team 1) is partnering with Aqua Duck to come up with an online system to help Aqua Duck sell their merchandise online. The proposed system does not require any direct interaction between Aqua Duck’s customers and their company; all transactions will take place via this website. The system should be versatile and easy to change, so Aqua Duck can use the website to sell different merchandise at different times through the year. At this time, the system is designed to sell swimwear products. The proposed system should be up and operational by the first week in May 2010 in preparation for the summer shopping season, as long as the SRA is signed by the due date. J3S made additional recommendations in functionality, based on their previous experience and research, to Aqua Duck’s minimum set of requirements.2. Objectives2.1 BUSINESS ObjectivesThe following is a list of business objectives:Objective 1:Login – System will be password-protected accessible through customer and employee loginObjective 2:Account Maintenance – Customer may create, edit, and view personal account information. Customer may view order history. Customer and employee may change own passwordObjective 3:Search – Customer and employee may search for merchandiseObjective 4:Shopping Cart – Customer may add and manage items for purchaseObjective 5:Inventory Management – Authorized employee may create & cancel orders, manage inventory, and set up low inventory alertsObjective 6:Checkout – Registered customer can purchase items in shopping cart by providing payment and shipping informationObjective 7:Sales data – Authorized employee may view profits, sales, and financial dataObjective 8:Website management – Authorized employee may add and edit website content2.2 SYSTEM ObjectivesThe following is a list of system objectives:Objective 1: System will be web-basedObjective 2: System will support Mozilla Firefox 2.0+ and Microsoft Internet Explorer 6.0+ browsersObjective 3: Web server running Apache 2 and PHP 5.2Objective 4: Database server running MySQL 5.1Objective 5: System hosting will be later determined by team 13. Project Context DiagramA user may browse and surf the website prior to login, represented by the area outside the dotted boxes. However, the user is required to login to perform any action within dotted box. The box defines the outer limits of authority level available to customer and employee. The search functions represented on the diagram are the same and can be accessed before and after a user logs on.4. Systems Requirements4.1 Requirements OverviewA summary of the detailed requirements are specified below.4.2 Login/Registration Requirements4.3 Account Maintenance RequirementsThe system should provide easy user interface for the user to modify his/her account as per requirement. The basic functionality and requirements for account modification are enlisted below.4.4 Search RequirementsThe system should allow various options for searching items. The user should be able to search items by supplying relevant information on a search box provided by the system. Search result items will be displayed with item name, ID, color, size, and price. The requirements for the search functionality are:\s\s4.5 Shopping Cart RequirementsShopping cart allows a customer-end user to group items they wish to purchase. Items can be added, removed, or changed. Information on items and group can be shown, and when ready the user can pay for their items.4.6 Inventory Management RequirementsInventory management allows employees to see the number of items in stock, and modify the quantity. Employees may modify certain property fields like item name and sale price.\s\s4.7 Checkout RequirementsCheckout allows a customer-end user to purchase items in their shopping cart. After providing billing and shipping information, items are deducted from inventory and an order receipt is generated for the user.4.8 Sales Data RequirementsSales data may be easily viewed by an employee. Employee can login to review sales data. Employee should be able to assess current sales, projected sales & gross profit. Employee will be able to view data by order number, customer name, sales date, shipping/delivery date, and payment type. The basic functionality and sales data related requirements are:\s4.9 Website Management RequirementsEmployees and managers can log in to a special website to administer the website. Employees and manager may add items, update item properties, change the quantity of items in stock, put items on sale, create/edit/delete promotions, and change their own password. In addition, managers may create/delete employee & manager, change other users’ passwords, and change the website template.\s5. Software Processes and Infrastructure5.1 Hardware and InfrastructureIf the system is hosted by team 1, system will be hosted on an HP Pavillion running a virtual machine, labeled the primary host. The virtual machine will be running Ubuntu 9.10, which provides web-hosting and database services. A backup web host will be hosted on a Dell Inspiron, mirroring the primary host. Database will be backed up from the primary host to an external system. If the system is not hosted by team 1, the system will be hosted on a web service provider that will be determined at a later date.5.2 UML DiagramsFigure 1: Overall UML DiagramFigure 2: State Transition UML for LoginFigure 3: State Transition UML for Account MaintenanceFigure 4: State Transition UML for SearchFigure 5: Class UML for Shopping CartFigure 6: State Transition UML for Inventory ManagementFigure 7: State Transition UML for CheckoutFigure 8: Class UML for Sales DataFigure 9: Class UML for Website Management5.3 Conceptual Data Model – DatabaseThe database structure is being determined at this time. A tentative model that represents part of the database has been created. This portion represents the elements associated with a user on the system. Figure 10: Partial Database Model 5.4 Screen ShotsA framework that represents locations of major elements of the user interface is shown below. Each section is labeled with its intended functionality. This framework is tentative and may change.Figure 11: A Framework for Web Page Layout5.5 Test PlanA test plan will be provided at a later stage of the project.6. Assumptions and Constraints6.1 AssumptionsThe following is a list of assumptions:Ignore deliver details such as dealing with UPS and FedExOnly people older than 18 can orderSystem up-time requirements are not consideredSales outside the USA require credit cardCustomers must login to system prior to placing an orderIgnore contract negotiation and legal concernsUser will have compatible browser6.2 ConstraintsThe following is a list of constraints:Uptime percentage is not guaranteedDelivery date may change if additional requirements are added after SRA is signedCredit card validation ignored6.3 Out of Scope materialThe following is a list of “out of scope” material:Post Project maintenance is not covered7. Delivery and ScheduleTask/Milestone DescriptionAnticipated Start DateAnticipated End DateStatusCommentsPrepare Requirements and UML diagram2-2-20103-2-2010CompleteSRA document (Includes project objectives, Requirements and UML diagrams)2-2-20103-4-2010CompleteDeliverable will be the SRA document. All stakeholders agree on the content of the SRA by signing in section 8. Presentation of SRA3-2-20103-4-2010CompleteDatabase Design2-28-20103-16-2010In progressFramework3-4-20103-22-2010In progressHTML Storyboards3-4-20103-22-2010To be startedCoding Implementation3-16-20104-27-2010To be startedExternal Documentation (i.e. User Manual)3-30-20104-27-2010To be startedTest Data Entry4-15-20105-1-2010To be startedTest Plan DeliveryTBDTBDTBDFinal Milestone: project delivery5-6-20108. Stakeholder Approval FormStakeholder NameStakeholder RoleStakeholder CommentsStakeholder Approval Signature and DateBahram KhaliliDevelopment MgrMirza ElahiProject AssistantJason BeereDeveloperJustin HundtDeveloperJuan PlacenciaDeveloperSandip ShresthaDeveloperAppendix:None ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download