The Sherlock Project Purdue University, Department of Computer Sciences Sponsored by Tellabs, Inc. Doug Clark - Group Leader Tobey Pasheilich Raj Talwar Shahman Baluch Cengiz Bayazit

4/27/99Sherlock Project2 Overview The CS 406/407 class objectives The Sherlock Project –Description –Requirements and Purpose Achievements Work done last fall in CS 406 Work done in CS 407 Problems we faced Lessons Learned

4/27/99Sherlock Project3 The CS 406/407 Courses: Fundamentals of Software Engineering Setting: –Engineering a real software project –Group-based environment –Real-world problems –Client communications Benefits: –Interview and resume material –Teamwork and S.E. experience

4/27/99Sherlock Project4 The Project: Sherlock System and Human Resource Locator Description: –Graphical, client/server-based, platform- independent online query tool Uses: –Locates resources –Shows the physical location of objects

4/27/99Sherlock Project5 Motivation for Sherlock Makes it easy to find an employee’s information, such as or telephone Can be set up as a “kiosk” for visitors who are looking for an office or conference room Allows fast and visual management of resources Improves current system at Tellabs (glorified “grep”)

4/27/99Sherlock Project6 Sherlock Functional Requirements - Mike Connolly Scheduling system –Reserve conference rooms –Make appointments with other employees –Manage calendars and notify of changes Search system –Locate employee information and homepage –Perform complex searches for any resource

4/27/99Sherlock Project7 Map System –Locate any resources, provide current position and shortest route to destination –Locate closest resources of any type –Browse maps for all Tellabs facilities –Show complex search results on a map Administration –Users can change their own login and info –Administrators have basic access to directory information

4/27/99Sherlock Project8 Sherlock platform - LDAP (Netscape Directory Server) Lightweight Directory Access Protocol Derivative of X.500 Directory Fast, complex searching capabilities Hierarchical data store Authentication and security features Standardized API Distributed referrals

4/27/99Sherlock Project9 Sherlock Project Results Product Features –Intuitive, browser based interface –Complex searches –Customizable results display –Map browsing and resource location –User-level data modification –Sensible LDAP Schema and management tool

4/27/99Sherlock Project10 Features NOT achieved –All calendar and scheduling support –Shortest route on a map –Location of resources by relative distance –Paging service (easy to add) –Schema-level administration tool –SSL (easy to configure with certificates) Sherlock Project Results

4/27/99Sherlock Project11 CS 406 Team Members –Team 2 - Scott Freeman Eric Bowman Bill Craver Drew Michaels Eric Laabs Group A - Ben Foster –Team 1 - Tobey Pasheilich Doug Clark Tobey Pasheilich Rajiv Talwar Greg Ebert

4/27/99Sherlock Project12 Group A Experience Requirements - Confusion –UML, Rational Rose, LDAP, SSL, Apache, Cookies, CGI, Java Design Development –Difficulties/Growth The Design –CGI –Sherlock Server –Problems Prototype

4/27/99Sherlock Project13 CS 406 Team Members –Team 2 - Larry Lewis Valisha Bradford Andre Young Group B - Cengiz Bayazit –Team 1 - Shahman Baluch Mohammad Jawad Butt Usman Latif Fauzia Aslam Evan S. Ho

4/27/99Sherlock Project14 Group B Architecture

4/27/99Sherlock Project15 Group B Prototype Demo on Thursday December 10, 1998 Features Demonstrated – LDAP Functionality – Login,Add, Remove, Search Features Not Demonstrated – Map, SSL, Resource Data Types Language used in coding – Java (1.1) Other software packages used by the prototype : – Netscape LDAP JDK – Suitespot Server (3.xx)

4/27/99Sherlock Project16 CS 407 Re-design based on experience and research –Combination of each group’s work –Simplified approach –New tools and technologies Implementation of new design –Division of labor by component and process –Integration of components

4/27/99Sherlock Project17 Team Organization

4/27/99Sherlock Project18 Sherlock Design

4/27/99Sherlock Project19 CS 407 Product testing –Tests by component and by component dependencies –Periodic re-evaluation of LDAP schema Product delivery –Installation guide outlines all procedures for installing and maintaining Sherlock

4/27/99Sherlock Project20 Problems Faced During Development CS 406 –Too many people –Poor understanding of the problem statement –Unbalanced work distribution CS 407 –Combination different research backgrounds –Focus on understanding before design –Non-static development environment

4/27/99Sherlock Project21 Lessons Learned Teamwork and tolerance The need for quality software engineering methodology Project planning, time management, and how to set realistic expectations Hands-on experience with recent technologies

4/27/99Sherlock Project22