1. Hestia: Aarthi Giridharan Govindarajan Panneerselvam Nirmal Chander Shesha Chandrika Moka Sriram Rajendran Suryanarayanan Ganesh Melarkode Vignesh Swaminathan Vinod Myll Mylsamy

2. Introduction to Context and KWIC (nirmal) // Functional Requirements (vinod) // Non-functional Requirements (chandrika) // Architectural Specification (Aarthi & sriram) // Demo (vignesh) // Traceability Matrix (govind) // What is special about us? (surya) ** References //

4. As information architect Peter Morville stated in his User Experience Design article years ago,”…we must strike a unique balance on each project between business goals and CONTEXT, user needs and behavior, and the available mix of content.”

5. Key Word In Context: The index is formed by sorting and aligning words within a sentence. This allows each word to be searchable alphabetically in the index. Input: An ordered set of lines Method: Any line is circularly shifted (repeatedly remove the first word and append it to the end) Output: All circular shifts of the line in alphabetically ascending order

6. Accept an ordered set of lines. Output all circular shifts in a sorted manner. Allow users to select the mode of search (AND/OR/NOT).

14. Available Options: Shared Data Architecture Implicit Invocation Architecture Pipe & Filter Architecture Abstract Data Type Architecture Our choice: Abstract Data Type (ADT) Architecture

15. Data is communicated between the components through shared storage Advantages- 1. Performance, space and time 2. Efficient data representation as same storage is shared 3. No copying of data Disadvantages- 1. Modifiability 2. Enhanceability 3. Reusability

16. Component integration based on shared data Interface to the data is more abstract than in shared data (like in ADT) Computations are invoked implicitly as data is modified based on active data model Drawback- Difficult to control the order of processing

17. Each filter processes the input data and output data Each filter can run whenever it has data on which to compute Data sharing between filters is strictly limited to that transmitted on pipes Drawback- Difficult to support on interactive system

18. Complex systems can be built as a collection of small autonomous interacting agents More flexible for changes

19. Changes to the data can be easily accommodated (the object using that data maintains the same input and output formats) Supports the reusability of existing classes and objects

20. Objects should know the identity of other objects It is difficult to control the exact ordering of modules called internally by these objects When the identity of the object changes it is necessary to modify all objects that invokes it  Advantages > Disadvantages = Optimal Solution

21. The style is suited for cases where the data representation is likely to change during the lifetime of the system Class concept allows us to relate similar objects and reuse code through the inheritance mechanism

22. Click Here!

23. I-FRIssues Functional Requirements Architectural Specification FR1Input VerificationModule Input verifies all FR2Sets of charactersModule input accepts all ASCII characters FR3Shifting each lineCircular Shift Module constructs circular shift of each line FR4Print only the alphabetized form Output Module outputs the alphabetized form

24. I- NFRIssues Non-Functional Requirements Architectural Specification NFR1Enhance abilitySystem can accept updates without problems NFR2PortabilityIt is non-platform specific NFR3UnderstandabilitySound user manual and good GUI makes the product easy to understand NFR4ReusabilityModules of the system can be easily reused. NFR5ResponsivenessThe system responses in few minutes. NFR6User – FriendlyGUI design is simple to use. NFR7Good PerformanceThe system runs with better performance. NFR8AdaptabilityThe system is modular to be easily maintained

25. Depending on context of time and resources we may choose to implement the following: Sorting based on user relevance (Example IMDB),  Method 1: Specifying the rules in the program (hard- coded),  Method 2: Specifying the rules in a Dashboard. Update our website to a better design

28. Lecture Notes Class Discussions Sample project files on Class Webpage Wikipedia: KWIC System UTD Wiki

29. Questions