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

Slides:



Advertisements
Similar presentations
Key-word Driven Automation Framework Shiva Kumar Soumya Dalvi May 25, 2007.
Advertisements

1 Software Testing and Quality Assurance Lecture 21 – Class Testing Basics (Chapter 5, A Practical Guide to Testing Object- Oriented Software)
1 Problem Solving Abstraction Oftentimes, different real-world problems can be modeled using the same underlying idea Examples: Runtime storage, Undo operation.
Managing data Resources: An information system provides users with timely, accurate, and relevant information. The information is stored in computer files.
Designing the system Conceptual design and technical design
Lecture 23: Software Architectures
Design The goal is to design a modular solution, using the techniques of: Decomposition Abstraction Encapsulation In Object Oriented Programming this is.
Chapter 1 Introduction to Object- Oriented Programming and Problem Solving.
Presentation by: Martin Hoffman
Team 1 Lisa Anthony Luiza da Silva Erik Hayes Diana Tetelman.
1 CS115 Class 7: Architecture Due today –Requirements –Read Architecture paper pages 1-15 Next Tuesday –Read Practical UML.
Architectural styles and Case studies 1 | Website for Students | VTU NOTES | QUESTION PAPERS | NEWS | RESULTS.
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
Data Structures and Programming.  John Edgar2.
KWIC Project – Part 1 Mini-Project to Evaluate Architectural Patterns(Styles) Carl Chesser Ji Li EECS 761.
I. Pribela, M. Ivanović Neum, Content Automated assessment Testovid system Test generator Module generators Conclusion.
1 CMPT 275 High Level Design Phase Architecture. Janice Regan, Objectives of Design  The design phase takes the results of the requirements analysis.
CPSC 410: Software Architectural Style (Part I) By the end of this lecture, you will be able to: list various software architectural styles describe advantages.
1 On the Criteria To Be Used in Decomposing Systems into Modules by D.L.Parnas Dec presented by Yuanhua Qu for spring 2003 CS5391.
An Introduction to Software Architecture
 Explain the role of a system analyst.  Identify the important parts of SRS document.  Identify the important problems that an organization would face.
With Windows 7 Introductory© 2011 Pearson Education, Inc. Publishing as Prentice Hall1 Windows 7 Introductory Chapter 2 Managing Libraries Folders, Files.
Architecture styles Pipes and filters Object-oriented design Implicit invocation Layering Repositories.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Architectural Styles.
Lecture 2 Introductory Case Studies Topics Architectural Styles Key Word In Context (KWIC) Other Cases Studies Evolution of Software Engineering January.
ECE450 - Software Engineering II1 ECE450 – Software Engineering II Today: Key Principles of Software Architecture and Design (I) adapted from Dave Penny’s.
Design engineering Vilnius The goal of design engineering is to produce a model that exhibits: firmness – a program should not have bugs that inhibit.
SE: CHAPTER 7 Writing The Program
June 05 David A. Gaitros Jean Muhammad Introduction to OOD and UML Dr. Jean Muhammad.
Control Systems Design Part: FS Slovak University of Technology Faculty of Material Science and Technology in Trnava 2007.
Introduction CS 3358 Data Structures. What is Computer Science? Computer Science is the study of algorithms, including their  Formal and mathematical.
Editors And Debugging Systems Other System Software Text Editors Interactive Debugging Systems UNIT 5 S.Sharmili Priyadarsini.
Unit 2 Architectural Styles and Case Studies | Website for Students | VTU NOTES | QUESTION PAPERS | NEWS | RESULTS 1.
14.1/21 Part 5: protection and security Protection mechanisms control access to a system by limiting the types of file access permitted to users. In addition,
DATABASE MANAGEMENT SYSTEM ARCHITECTURE
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 13. Review Shared Data Software Architectures – Black board Style architecture.
Introduction to Information and Computer Science
SOFTWARE ARCHITECTURE FOR A KWIC SYSTEM TEAM: GLOBAL 14.
1 CS 311 Data Structures. 2 Instructor Name : Vana Doufexi Office : 2-229, Ford Building Office hours: By appointment.
“Architecture” The outcome of top-level design, reflecting principal design decisions Can (and should) be modified and updated Analogous to architecture.
Comparing Designs By Chris McCall. Comparing Designs A decision-making method for deciding between many designs for a single specification Provides a.
Lecture 21: Component-Based Software Engineering
Lecture VIII: Software Architecture
Chapter – 8 Software Tools.
Silberschatz, Galvin and Gagne ©2011 Operating System Concepts Essentials – 8 th Edition Chapter 2: The Linux System Part 2.
Keyword In Context Presented by Team 2 Francisco Soria Zhiyu Zhang Xuheng Xu Irene Peysakhov.
Presentation on Database management Submitted To: Prof: Rutvi Sarang Submitted By: Dharmishtha A. Baria Roll:No:1(sem-3)
Architectural Mismatch: Why reuse is so hard? Garlan, Allen, Ockerbloom; 1994.
IAY 0600 Digital Systems Design VHDL discussion Structural style Modular design and hierarchy Part 1 Alexander Sudnitson Tallinn University of Technology.
KWIC example The KWIC [key word in context] system accepts an ordered set of lines; each line is an ordered set of words, and each word is an ordered set.
Lecture 1 Data Structures Aamir Zia. Introduction Course outline Rules and regulations Course contents Good Programming Practices Data Types and Data.
Structural style Modular design and hierarchy Part 1
Object Oriented Programming
Containers and Lists CIS 40 – Introduction to Programming in Python
SOFTWARE DESIGN AND ARCHITECTURE
Introduction to Design Patterns
Structural style Modular design and hierarchy Part 1
Software Quality Engineering
Prepared by Charlie Meyer, May 2009
CYBERMINER WEB SEARCH ENGINE
Chapter 5 Designing the Architecture Shari L. Pfleeger Joanne M. Atlee
Lecture 1: Multi-tier Architecture Overview
An Introduction to Software Architecture
Introduction to Data Structure
CyberMiner Software Architecture Group
Final Project Presentation
PHASE 1 - PRESENTATION Presented By - Karthik Kannambadi Sridhar
Lecture 2b Introductory Case Studies
CS/SE ADVANCED SOFTWARE ARCHITECTURE AND DESIGN FALL 2015
Module Structure David Parnas Discusses “modularization”
Presentation transcript:

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

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

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

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

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

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

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

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

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

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

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

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

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

Click Here!

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

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

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

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

Questions