Web-based Front End for Kraken

1
Web-based Front End for Kraken

• Jing Ai
• Jingfei Kong
• Yinghua Hu

2
The Current System of Kraken

• An application for knowledge management
  implemented in Python.
• Allows to annotate documents, webpages, files and
  so on with metadata.
• Annotation files stored in both external native
  formats and the standard RDF format.
• The result of queries are generated in the form
  of HTML reports, with links to the original
  documents.
• It features conversational command line
  interface.

3
Proposed System

• A web-based front end for kraken
• User-friendly with GUI interface
• Authentication is provided for access control

4
Use Case
5
Project Overview

• The front end developed will have all the
  interfaces the original command line interfaces
  provides. 
• It will be in charge of  user  input and also the
  interaction with the engine. 
• Version control for various projects files will
  be handled by CVS.

6
Project Team Organization

• Members in the team
• Jing Ai ----------- project manager
• Jingfei Kong ----- documentation
• Yinghua Hu ------ testing
• Everybody will be a programmer also.
• Communication will be handled through email and
  scheduled face-to-face meetings.

7
Software Life Cycle

• In the beginning, rapid prototype
• Later, incremental model

8
Risks

• Experienced user may not like the interface we
  create.
• Learning curve should not be ignored due to
  unfamiliar tools.
• It could be possible that the product cannot be
  finished on time.

9
Objectives -- Test Plan

• Find as many errors as possible before the user
  of the software finds them
• Make sure that our software adheres very closely
  to the client requirements and specification
  document

10
Stopping Criteria -- Test Plan

• When an error or bug is encountered during the
  testing process, then further testing of the
  system will be stopped until the error is fixed.
• Only when all the intended test cases run
  successfully, we declare the software to be error
  free and is competent enough to be delivered to
  the client.
• Final testing will be done by the developers as
  well as the clients in the client working
  environment.

11
Test Cases -- Test Plan
Test Case Test Objective Test Description Expected Results
1 User Login User logins in the remote web-based kraken application located on the server The user logins in if his login name and password are in the system, while does not login in if not allowed
2 User Create Entry User inputs the description of a new entry The web browser jumps to the correct page that user desires
3 User Query User inputs the description of new query and click the query button The web browser displays the correct results in the new page