1 / 47

Marvel Electronics Inc.

Marvel Electronics Inc. Team 1 Amit Nimse M Rajaul K Khan Shasank Bhandari Tonda Phillips Vikram Sitaram Kumar Unnikrishnan. Instructor: Dr. Lawrence Chung. AGENDA. Describing the requirement process followed for e-store project

jeffkmoore
Download Presentation

Marvel Electronics Inc.

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. Marvel Electronics Inc. Team 1 Amit Nimse M Rajaul K Khan Shasank Bhandari Tonda Phillips Vikram Sitaram Kumar Unnikrishnan Instructor: Dr. Lawrence Chung

  2. AGENDA • Describing the requirement process followed for e-store project • Outcomes of requirement process • Addressing issues of the Standish report • Questions and Answers CS 6361- Requirements Engineering - Course Project.

  3. User Requirement • Build a tower as tall as possible. • Time limit of 10 minutes. • Make it rigid. CS 6361- Requirements Engineering - Course Project.

  4. Requirement in action CS 6361- Requirements Engineering - Course Project.

  5. User Testing CS 6361- Requirements Engineering - Course Project.

  6. Final Result… Standish Report still prevails !!!!! CS 6361- Requirements Engineering - Course Project.

  7. Team Architecture CS 6361- Requirements Engineering - Course Project.

  8. Process Flow Business Driver Users Inception Reqmt’s Model Specification Knowledge Validation Validation Results Clarification Elicitation Problem Domain CS 6361- Requirements Engineering - Course Project.

  9. Actigram for Process CS 6361- Requirements Engineering - Course Project.

  10. Inception Phase. • Steps Undertaken: • Understanding Background and Problem Definition of e-store project. • Studying business objectives for the e-store project. • Analyzing scope of the project and feasibility of implementation. • . . CS 6361- Requirements Engineering - Course Project.

  11. Elicitation Phase Steps Undertaken: • Identifying Users and Stakeholders. • Participating in Brainstorming Session. • Identifying and Prioritizing Wants and Needs. • Generating Vision Document. CS 6361- Requirements Engineering - Course Project.

  12. Specification • Steps Undertaken: • Generate Business Models. • Functional and Non functional models for Software system. CS 6361- Requirements Engineering - Course Project.

  13. Business Models Steps Undertaken: • Identifying business actors, business entities and business workers in the current business of Marvel Electronics. • To depict the “To-Be” business model … • Business use case diagram. • Business class diagram. • Business activity diagram. • Business sequence diagram. • Identify different entities that are going to interact with the e-store. CS 6361- Requirements Engineering - Course Project.

  14. Business Model • Business Use Case Diagram. CS 6361- Requirements Engineering - Course Project.

  15. Business Model • Business class diagram. CS 6361- Requirements Engineering - Course Project.

  16. CS 6361- Requirements Engineering - Course Project.

  17. Business Model • Business Sequence Diagram (Purchase Product). CS 6361- Requirements Engineering - Course Project.

  18. Business Model • Business Sequence Diagram (Configure Product). CS 6361- Requirements Engineering - Course Project.

  19. E-store System Functional Model Steps Undertaken: • Use case analysis for e-store system. • Creating Structural Requirements model using class diagram. • Creating Behavioral Requirements model using sequence diagram and activity diagram. CS 6361- Requirements Engineering - Course Project.

  20. E-store functional model • Use Case diagram. CS 6361- Requirements Engineering - Course Project.

  21. E-store functional model • Class Diagram. CS 6361- Requirements Engineering - Course Project.

  22. E-store functional model • High level Sequence diagram. CS 6361- Requirements Engineering - Course Project.

  23. E-store functional model • Sequence diagram (Purchase Product). CS 6361- Requirements Engineering - Course Project.

  24. E-store functional model • Sequence diagram (Configure Product). CS 6361- Requirements Engineering - Course Project.

  25. E-store functional model. • Sequence diagram (Display product offerings). CS 6361- Requirements Engineering - Course Project.

  26. E-store Nonfunctional Model • Nonfunctional requirements identified in our e-store system: • Security *(6.1 – 6.3) • Usability *(6.4) • Availability *(6.5 , 9.2) • SIG is used to model above mentioned Nonfunctional requirements. [* Reference from Vision Document] CS 6361- Requirements Engineering - Course Project.

  27. Security    Data Storage Data Transfer      Secure Sockets Secure Session Confidentiality    E-store Nonfunctional Model • SIG (Security) CS 6361- Requirements Engineering - Course Project.

  28. Secure Session (cont.)    Session Timeouts Secure Cookies       Confirm Transactions Automatic Logoff Leave NO Passwords Leave NO Personal Data     E-store Nonfunctional Model • SIG (Security Cont…) CS 6361- Requirements Engineering - Course Project.

  29. Confidentiality (cont.)    Browsers Back-end Servers        Passwords Never Displayed Logoff Credit Card Number retrieved as last 4 digits only Passwords never displayed, only re-settable Restricted Access to authenticated Administrators Encrypted Database      E-store Nonfunctional Model • SIG (Security Cont…) CS 6361- Requirements Engineering - Course Project.

  30. Validation Phase • Communicating requirements models to stakeholders. • Using mock-ups to validate the requirements. CS 6361- Requirements Engineering - Course Project.

  31. Mock–ups Screen (Home Page) CS 6361- Requirements Engineering - Course Project.

  32. Mock–ups Screen (Create Account) CS 6361- Requirements Engineering - Course Project.

  33. Mock–ups Screen (After Logged-in ) CS 6361- Requirements Engineering - Course Project.

  34. Mock–ups Screen (Product View) CS 6361- Requirements Engineering - Course Project.

  35. Mock–ups Screen (Configure Product) CS 6361- Requirements Engineering - Course Project.

  36. Mock–ups Screen (Credit Card Payment ) CS 6361- Requirements Engineering - Course Project.

  37. Mock–ups Screen (View Order) CS 6361- Requirements Engineering - Course Project.

  38. Mock–ups Screen (Tracking Order) CS 6361- Requirements Engineering - Course Project.

  39. Incomplete Requirements Changing Requirements Lack of user involvement Addressed by user interaction and Traceability Addressed by Traceability Addressed by user interaction and Mock-ups Addressing issues in Standish Report. CS 6361- Requirements Engineering - Course Project.

  40. Traceability • Traceability Hierarchy Stakeholder Need traces Product Feature traces traces Supplementary Requirements Use Case CS 6361- Requirements Engineering - Course Project.

  41. Sample Traceability Brainstorming Session Vision Document Use case diagram Traceability matrix CS 6361- Requirements Engineering - Course Project.

  42. Traceability • A Traceability Matrix is used to trace requirements. • An element in a row that maps to an element in a column is marked by a ‘X’ at the intersection of that particular row and that particular column. CS 6361- Requirements Engineering - Course Project.

  43. Traceability The Traceability Matrices • User Needs - Features • Features - Use Cases • User Needs – Constraints Traceability Matrix CS 6361- Requirements Engineering - Course Project.

  44. Next steps • Refine Nonfunctional SIG models. • Finalize project deliverables. CS 6361- Requirements Engineering - Course Project.

  45. Conclusion Learning Objectives achieved - specify and follow a requirements engineering process – • to identify stakeholders (and other sources of requirements), elicit their needs and objectives, identifying and resolving conflicts. • to differentiate process requirements from product requirements • to manage changing requirements • to model structural, behavioral and non-functional requirements • to understand the derivation of architectural and design models from requirements specification • to validate requirements • to build a mock-up • to establish requirements traceability • to use a CASE or modeling tools to capture the requirements • to produce a clear, comprehensive and complete Software Requirements Specification • to understand the whys, what's and how's of a software system CS 6361- Requirements Engineering - Course Project.

  46. Q&A ? ?? ??? CS 6361- Requirements Engineering - Course Project.

  47. Thank You CS 6361- Requirements Engineering - Course Project.

More Related