Team 0000E - Vision Document. Alex Kaufmann Danny Mathews Jeremy Colwick Justin Griffin Kevin Gillis

Transcription

1 Team 0000E - Vision Document Alex Kaufmann Danny Mathews Jeremy Colwick Justin Griffin Kevin Gillis

2 1.0 Introduction The purpose of this Vision Document is to describe the functionality of the program Chattorama in non-technical ways. It will help steer everyone who is involved in the project are on the same page and have a single goal to achieve. The purpose of the program Chattorama is to give users a slightly more robust chat messaging program, as it combines the cloud file sharing ability of a website such as Megaupload with the chatting capability and friend searching of a program such as AOL Instant Messenger. It will be built using Ruby as the programming language and Rails as the database language. Throughout this document we will take a look at the different software requirements, and break down the program further into more manageable pieces that can then be taken on by our software development team. 2 User Description 2.1 User/Market Demographics Although we prefer that our product is used by everyone, our key demographics are young adults and adults This age range contains the majority of computer users and users that would find our product the most useful. Both files sharing and social media are popular, but are rarely combined indicating the possible success of our product with our user base. 2.2 User Profiles User 1 - The average user who is computer literate, but lacks any tecchnical knowledge, needs a site that allows them to easily upload their files, share those files with his/her friends, and communicate with their friends. There are already file sharing sites available, but they lack any true social aspect, and there are social sites available, but they lack any file sharing aspect. The user must use two different sites in order to share files with his/her friends and risks breaking the Terms and Condintions of one of the sites by using the other. The user is successful when they can both communicate and share files with his/her friends on a single website with ease. 2.3 User Environment User 1 - The average user will use this product at home for personal use. Because of the vast ammont of file types, our product will need to compatiable with the majority of them. 2.4 Key User Needs User 1 Problem: There are no sites that combine both social media and file sharing in a

3 single, easy-to-use package. Solution: A site with an integrated text messager, and file server. 2.5 Alternatives and Competition Tixati is a torrent client that has both text messaging and link sharing, but the service relies on other file sharing sites and doesn't have a file server dedicated to the service BitTorrent has similar features to Tixati FileSocial.com allows user to share files over Twitter but doesn't provide their own social features. 3.0 Product Overview 3.1 Product Perspective This product is built to be independent and totally self sustained. 3.2 Product Position Statement This product is designed for home hobby use. This product is not targeted towards any company, government, or any type of use where security or confidentiality of information is a necessity. The reason this product is being designed is to provide a more opportune venue for organizations that need to build a structure around communication and distribution of files. Chattarama is a program that fulfills both of those needs in one program, combining file sharing and chatting much as mirc did back in the earlier part of the millennium but in a newer, sleeker, and easier to use form. 3.3 Summary of Capabilities Customer Benefit Feature Supported Users should be able to store friends list. Users should be able to have status. Users should be able to delete account. Multiple users should be able to join chat rooms. Users should be able to chat. Users should be able to log in and out. Users should be able to share files.

4 Users should be able to edit profile. Users should be able to view other profiles. 3.4 Assumptions and Dependencies All features that are included at this point are dependent on being able to do so coding with Ruby on Rails. If any of these features prove impossible to do using this programming language, then we will have to investigate alternative options. 4 Feature Attributes 4.1 Status Proposed: Features that are proposed include being able to have a secure connection. Approved: The features that have been approved by the team include the ability for file transfer and the ability to chat and create friends based on shared interests. Incorporated: We have not incorporated any features to the website at this time. 4.2 Priority Critical: The critical features include being able to chat with friends and being able to share files. Important: One feature that is important, but not necessarily, critical is the ability to create a friends list. A very good GUI would be very important is making this a successful application. Useful: We want to have a secured connection to our website in order to secure the privacy of the users information. 4.3 Effort The features that will require the most work include implementing the chat program and being able to implement the file system for our project. The login/logout system, the user profile system, and the friends list system should require a moderate amount of work. The feature that will take the least amount of work is the creation of a GUI. 4.4 Risk The features that will include the most risk is the file system and the chat system since these two features seem to be the ones with the highest amount of risk associated with the program. All other features will have at least a moderate amount of risk because of our lack of experience with Ruby on Rails. 4.5 Stability

5 The most important features will be pretty stable. The less stable features seem to be the ones that we are still debating on putting in. 4.6 Target Release We are going to be using agile development so this will depend on the amount of work that is done in a given period. 4.7 Assigned To We will not be using feature teams for this project since we are using agile development for this program. 4.8 Reason The reason we want to create a website that does file shring and chat is because there is not currently any website that does both of these things. We want to be able to create friends lists so that users will be able to communicate effectively to like minded people. We want the website to be secure in order to secure the privacy of our users.