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

KWIC SYSTEM by Hestia

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 //

What are we going to talk about?

Keyword is : GAS

How important is CONTEXT ?

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.”

Why is CONTEXT important?

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 linesMethod: 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

The KWIC System

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).

Functional Requirements

FR 1: Accept an ordered set of lines

Define Delimite

rUse

Return Key

FR 2: Output all circular shifts in a sorted manner

Random Order

Alphabetical Order

Based on Frequency

FR 3: Allow user to select mode of search (AND/OR/NOT)

Radio Buttons

Enter Keywords

(+/-/!)

Individual Textboxes

Non Functional Requirements

Understandability

Portability

Enhance-able

Understandability Any user can easily navigate and use the system.

Resolution: Buttons and other UI items are properly labeled. In addition, proper instructions are included on the web page.

NF 1: Understandability

Enhance-able : Enhance-able can lead to mean the system is modularized and independent

Resolution: The system is developed using OO concepts. Addition of new features doesn’t affect other modules.

NF 2: Enhance-able

Portability : This feature enables the codebase to be reused instead of rewriting the code when moved to a new environment

Resolution: Used Object Oriented Style which allows modifiability and adaptability without affecting the other modules

NF 3: Portability

Available Options:Shared Data ArchitectureImplicit Invocation ArchitecturePipe & Filter ArchitectureAbstract Data Type Architecture

Our choice: Abstract Data Type (ADT) Architecture

Architecture Specification

Data is communicated between the components through shared storage

Advantages-1. Performance, space and time2. Efficient data representation as same

storage is shared3. No copying of data Disadvantages-4. Modifiability5. Enhanceability6. Reusability

Shared Data Architecture

Component integration based on shared dataInterface 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 modelDrawback-Difficult to control the order of processing

Implicit Invocation

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

Pipe and Filter

Complex systems can be built as a collection of small autonomous interacting agents

More flexible for changes

Why ADT?

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

Why ADT?

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

Disadvantages of ADT

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

Why did we still choose ADT?

DemoClick Here!

I-FR Issues Functional Requirements

Architectural Specification

FR1 Input Verification Module Input verifies all

FR2 Sets of characters Module input accepts all ASCII characters

FR3 Shifting each line Circular Shift Module constructs circular shift of each line

FR4 Print only the alphabetized form

Output Module outputs the alphabetized form

Traceability Matrix

I- NFR Issues Non-Functional Requirements

Architectural Specification

NFR1 Enhance ability System can accept updates without problems

NFR2 Portability It is non-platform specific

NFR3 Understandability Sound user manual and good GUI makes the product easy to understand

NFR4 Reusability Modules of the system can be easily reused.

NFR5 Responsiveness The system responses in few minutes.

NFR6 User – Friendly GUI design is simple to use.

NFR7 Good Performance The system runs with better performance.

NFR8 Adaptability The system is modular to be easily maintained

Traceability Matrix

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

Our Future Enchantments (- Why we are better)

Dashboard Feature

Example: IMDB

Lecture NotesClass DiscussionsSample project files on Class WebpageWikipedia: KWIC SystemUTD Wiki

References

Questions

Thank you