1 / 10

P icture U sers M aking A rt Chat

P icture U sers M aking A rt Chat. An interactive communication tool. Operational Concepts. Problem Communication over the internet is difficult through one medium Many different clients do specific things Chat rooms Voice programs Pictures Drawing boards Solution

riva
Télécharger la présentation

P icture U sers M aking A rt Chat

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Picture Users Making ArtChat An interactive communication tool.

  2. Operational Concepts • Problem • Communication over the internet is difficult through one medium • Many different clients do specific things • Chat rooms • Voice programs • Pictures • Drawing boards • Solution • Create a program that combines those different mediums to emulate a face to face interaction • User Community • Anybody who communicates via the internet some examples include: • Teachers – for online classrooms • Businesses – online presentations • Teams - coordinating team strategy over the internet

  3. Goals and Non-goals • Goals • Create a single application where users can chat through different mediums such as text, voice, and pictures • Allow users to interact with the pictures. • A privilege system to moderate user interaction. • Create a client server architecture where each server can handle multiple users. • Non-goals • Not a picture editing software, our program will only support generic MSpaint type picture editing • Not a full featured text messaging client, it will not connect to AIM or MSN or any other network and will not include the buddy list feature or private messages • Not a media player, it will not feature any sort of video it will only support pictures and picture editing • Not a full featured collaborative application, will only support basic collaborative functionality through pictures (ie. It will not support collaborative MS word or document makers) • Will not allow users to transfer files to each other

  4. System Requirements • The program will feature: • A graphical user interface. • Text (chat) communication • Voice(chat) communication • A presentation window which: • Functions as a drawing pad (envision MSpaint). • Allows for the display of pictures and slides while retaining the tools of the drawing pad. • Privilege settings (i.e. if someone wants to limit the interactivity of other clients)

  5. Graphical User Interface

  6. Software Architecture • One central server with many clients • Server and client code will be written in Java due to the availability of Java Libraries • Challenges: • Handling all the user input and the networking protocols (network traffic) • Handling the microphone input and streaming • How many users to connect to the same server and room?

  7. Lifecycle Plan • Stakeholders: Users, student development team, professor. • Why is the system being developed? This program is being developed in order to complete the project assignment portion of CSE 403 and because it seems really cool. • What will be done, when? The actual time spent coding seems vague, so specifying dates is difficult. However, the chat, voice and drawing pad would be implemented first, allowing user input. Then these three parts would be integrated into the client program while the server program is coded. Finally, server/client interaction would be built into the software. • Who will do it? Where are they? Unknown at this time. • How will the job be done? Unknown at this time. • How much of each resource? 6-8 Team members, 9 weeks, a lot of caffeine and patience.

  8. Lifecycle Plan (continued)

  9. Feasibility Rationale • Assumptions: • Users want a program that fuses text chat, voice chat and drawing capability. • Java supports input from a mic and network connectivity. • That current tools are insufficient or non existent. • Risks: • The program has too much functionality to complete on time. • The team doesn’t have enough knowledge of networking, server/client interaction, and obtaining user input.

More Related