Final Project Document Presentation Integrated Chat System Team

1
Final Project DocumentPresentationIntegrated
Chat SystemTeam 4December 2, 2003Professor
Peter Clarke
Phase 1 Melissa Betancourt Programmer Eric Guer
ra Time Keeper Ovide Mercure Team Leader Joshu
a Tomlinson Diary Keeper
Phase 2 Melissa Betancourt Team Leader Eric Gue
rra Diary Keeper Ovide Mercure Time Keeper Jos
hua Tomlinson Secretary
Phase 3 Melissa Betancourt Programmer Eric Guer
ra Programmer Ovide Mercure Time Keeper Joshua
Tomlinson Team Leader, Diary Keeper
2

• Purpose of the System
• Simplifies existing chat program concepts
  adapting
  
• them for use in inter-corporate communication
  (AOL
  
• AIM, Yahoo Instant Messenger).
• The ICS system allows corporations the ability
  to
  
• restrict one-to-one communication to their
  local area
  
• network (LAN).

Scope of the System The internal components o
f the ICS system are the server and the clien
t programs. The ICS users are the actors inv
olved with the use cases and are outside the
boundaries of the system.
3
ICS Use Case Diagram
4
Functional and Non-Functional Requirements
Use Case ID ICS01 Log In Scenario
Actor ICS User Pre-conditions 1. ICS s
erver chat client process
must be running. Description 1. Use cas
e begins when the Log-in window
pops open and requests the users name and
p
assword. 2. The use case ends when the logi
n is
successful and the users client contact list
w
indow is displayed.
5

• Post-Conditions
• 1. The chat server will update all
  appropriate
  
• user contact
  lists to indicate the user has
  
• logged in.
• Decision Support
• Frequency Once a day per end user.
• Criticality High.
• Allows the connection of the chat client
• to the server.
• Risk Medium.
• Implementing the use case employs standard
• intranet based technology.
• Nonfunctional Requirements

6
Use Case ID ICS04 Send Message
Scenario Actor User Pre-Conditions
1. User and other user are both logged on to
the system.
2. Chat Window was initiated. 3. Chat
Window is activated. Description 1. Use
case begins when user types a message
into the message
text area. 2. Once the user presses the send
button, a message is sent to the server.
3. Use case ends when the system echoes the
message on the users
conversation text area.
7

• Post-Conditions
• 1. The Message is displayed on the other
  users
  
• Chat Window.
• Decision Support
• Frequency At least once every time the user
  logs on.
  
• Criticality High.
• Allows communication.
• Risk Medium.
• Implementing the use case employs standard
• intranet based technology.
• Non-Functional Requirements
• Response time of the ICS Server
• ICS systems ease of use

8
Client-Server Architecture
9
Minimal Class Diagram
Client Subsystem
Communication Subsystem
Server Subsystem
10
Use Case Initiate Chat Window
11
System Test Case 1 forInitiate Chat Window
12
System Test Case 2 forInitiate Chat Window
13
Questions?