1 / 9

Software Requirements Specification Jeremy Brudvik Jeffrey Carlson Felix Chu Mohamed El-Zohairy

Software Requirements Specification Jeremy Brudvik Jeffrey Carlson Felix Chu Mohamed El-Zohairy Cian Malone Daniel Otero Roger Wong. Outline. Software Toolset Group Dynamics Advertisements Use Cases UI Prototype. Software Toolset. Back-end JSP Java Apache Tomcat JSTL Database

tareq
Download Presentation

Software Requirements Specification Jeremy Brudvik Jeffrey Carlson Felix Chu Mohamed El-Zohairy

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software Requirements Specification Jeremy Brudvik Jeffrey Carlson Felix Chu Mohamed El-Zohairy Cian Malone Daniel Otero Roger Wong

  2. Outline Software Toolset Group Dynamics Advertisements Use Cases UI Prototype

  3. Software Toolset • Back-end • JSP • Java • Apache Tomcat • JSTL • Database • MySQL • UI • AJAX • CSS • JavaScript • Testing • Apache JMeter • JUnit • BugZilla • Dev Environment • Eclipse • CVS • Communication • Wiki • Mailing List

  4. Group Dynamics • Meetings • Weekly “All-Hands” Meetings • Sub-team Meetings • Flexibility of roles • Decisions • Requirements win • …then leads • …then PM • …then democracy • Jeremy: Development Lead • Jeff: Documentation Lead • Felix: Usability Lead • Mohamed: Project Manager • Cian: Database Lead • Daniel: User Interface Lead • Roger: Test Lead

  5. Advertisement • Query-targeted • No results • With results • Content-targeted • Profile • Posted items • Browsed items

  6. Use Cases

  7. Use Cases • Use Case 4: Searching for an item using Advanced Search • Primary Actor: User (Member/ Non-member). • Goal in Context: User searches for and item through the system and examines relevant results. • Scope: The WeTrade System. • Level: User. • Precondition: None. • Stakeholders: • User: Wants to search for an item as fast as possible • Other users with listed items: Wants others to find their items • Advertisers: Wants many items so user stays on page. • WeTrade: Wants users to find all items that match. • Minimal Guarantees: No other system features will be affected by searches. • Success Guarantees: All relevant listings will be included in search results. • Trigger: User wants to look for an item. • Main Success Scenario: • User enters search parameters and submits a request. • System returns the relevant results.

  8. Use Cases Extensions: 1a. If user is non-member, s/he must specify local. 1b. User enters one or more invalid parameters, or excludes a required field. 1bi. System responds with error message, requests corrected input. 1c. Dynamic webpage fails to generate search fields correctly. 1ci. User frustration will occur. 1d. System overloads with excess traffic and… 1di. System rejects request, sends user an error message. 1dii. System delays request, shows user a loading animation. 1e. User navigates to another site while entering information. 1ei. System saves field information in case s/he returns. 2a. System finds no relevant results. 1ei. System responds with message and provides a new search form. 2b. User wants to investigate one of the listings. 2bi. Go to View Item 2c. System fails to respond correctly. 2ci. [What should be done here?] Priority: High. Frequency of Use: High. Channel to Primary Actor: Website. Open Issues: What should be done under system failure? How will the advanced search form be different for members and non-members? How can we save commonly used information so the user doesn’t have to repeat it every time? Perhaps using cookies?

  9. UI Prototype

More Related