1. Team Think For You

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

3. Introduction 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 Too many options/config. settings in HOPE

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: IterationActivities 1Problem + Domain analysis POC with 1 usage stat. type (frequency) 22 usage stat. type (frequency + time of day) Adaptive AHP, integration and testing

5. Requirements (Analysis) – One Example

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

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

8. Architecture Candidate evaluation Criterion\OptionOption 1 Delegate Option 2 Refactor Option 3 Map Maintainability (e.g., understandability, ease of updating) +++-- Integrability (e.g., in terms of concurrent features under development) ++--+- Implementation Cost (e.g., time) +--- Extensibility (e.g. add, change, future growth) +++-- Configurability (e.g., add settings to control behavior of feature) ++ --

9. Architecture Candidate evaluation Criterion\OptionOption 1 Delegate Option 2 Refactor Option 3 Map Maintainability (e.g., understandability, ease of updating) +++-- Integrability (e.g., in terms of concurrent features under development) ++--+- Implementation Cost (e.g., time) +--- Extensibility (e.g. add, change, future growth) +++-- Configurability (e.g., add settings to control behavior of feature) ++ --

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.  Adapter

16. Detailed Design

17.  Template

18. Detailed Design

19.  Strategy

20. 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?