1 / 28

An adaptive Sorting Feature for HOPE adaptive AHP and User Model Driven Approach

Team Think For You. An adaptive Sorting Feature for HOPE adaptive AHP and User Model Driven Approach. Outline. Introduction Process Requirements Engineering Architecture Detailed Design Testing Demo Extensibility Conclusions. Introduction.

woody
Download Presentation

An adaptive Sorting Feature for HOPE adaptive AHP and User Model Driven Approach

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. Team Think For You An adaptiveSorting Feature for HOPEadaptive AHP and User Model Driven Approach

  2. Outline • Introduction • Process • Requirements Engineering • Architecture • Detailed Design • Testing • Demo • Extensibility • Conclusions

  3. Introduction Too many options/config. settings in HOPE The Problem: Who’s Affected? Goals (How we solve the problem) • Capture multiple types of contextual info. about user’s past behavior • Sort options using a combination of captured info. • Display options in order of user’s most likely need

  4. Our Process • (Re)planning, Risk mitigation, issues resolution, SDM, tradeoff analysis, WBS, SVN • SW Dev. Process • Interleaving, Iterative (Agile) and Incremental • Fluid Teams(RE, Arch, DD, Implementation, QA) • 2 Iterations:

  5. Requirements (Analysis) – One Example

  6. Architecture Team TFY used Software Architecture Analysis Method (SAAM):

  7. Architecture Three options considered: • Delegate the responsibility of filtering things and actions to a module that wraps data access and updates statistics • Refactor existing architecture into a layered configuration, then extend business logic layer for context awareness • Map all the points of change in the current system to extend with context-sorting logic

  8. Architecture Candidate evaluation

  9. Architecture Candidate evaluation

  10. Architecture Static perspective UML component diagram

  11. Architecture Interaction perspective UML sequence diagram (for things and verbs after user clicks on sort button)

  12. Architecture Interaction perspective UML sequence diagram (for things and verbs after icon click event, upon icon selection)

  13. Detailed Design • Methodology • OO modeling, SDM, issue and conflict resolution • Scientific research • Design patterns • Adapter, Template, Strategy, Observer... • Design principles • High cohesion (single responsibility) and low coupling (data dependency)

  14. Detailed Design

  15. Detailed Design • Adapter

  16. Detailed Design

  17. Detailed Design • Template

  18. Detailed Design

  19. Detailed Design • Strategy

  20. Detailed Design

  21. Detailed Design

  22. Detailed Design

  23. Testing • Test plan • Criteria for testing completeness • SRS • Techniques: • Code Inspection • Scenario based white-box verification • detailed design sequence diagrams • Functional testing • Formal verification using Alloy model finder 

  24. DEMO

  25. Update • ...

  26. Sort

  27. Conclusion • Our Contributions to HOPE: • Use of contextual information to sort icons in order of user's most likely need • refactored HOPE code to make it more maintainable • formal model checking to test aspects of our model • design is easily extensible to allow for future addition of more types of contextual information as criteria in the sorting • Other Applications (Frequency and Time) • TV Listings • Music Playlist

  28. Questions? ?

More Related