Aranea

Scott Clifford

Jerin Schneider

Kansu Dincer

By: The Conclave

Seattle Life

Diverse community Many different demographics Lots of events and opportunities Difficult to find these opportunities in the

many communities

Our Solution

Community driven network of information Ability to create an Arca

ar•ca |ahr-kuh|noun

a cell Key Principles:

The people, focused, efficient, it’s easy and enjoyable!

What we hope to offer

An efficient means of communicating with the Seattle community

Opportunities for promotion and communication of all sorts

A helpful environment for people to express themselves and get to know each other

Target Audience

Two primary targets: Advertisers or promoters Opportunity seekers

Features Essential:

Web tool for Arca, and user accounts High priority:

Web tool for reviews and suggestions, and a user friendly interface

Medium priority: Web tool for chatting about a specific Arca, and

keyword search capability Low priority:

Web tool for comments, and server generated suggestions

What makes us different than the rest?For example: CitySearch or NW Source

More interaction than one-way services Content determined solely by users Not simply an information source Unique and innovative features

Architecture Web interface – HTML and JavaScript Flat data files vs. full-blown database

Flat files with XML functionality C# applications to do bulk of the work ASP.net to act as the glue for these

parts

Tools: Visual Studio mainly Third-party HTML and JavaScript editors

Milestones

1) File system / Data storageRough features of web GUIUser Accounts

3) Web GUI completed Essential features completed

2) Polished web GUI Arca functionality in place

4) High priority features completed

5) Lower priority features

Allocation of Resources Project Manager

First Phase Two data storage developers/testers:

One full-time developer One part-time developer and part-time test

Four interface developers/testers: Three full-time developers One full-time tester

Rest of the Time Four full-time developers Two full-time testers

Feasibility

Assumptions: Ability to learn languages effectively Third parties such as Google and Mapquest Correct management of time requirements for

stages Risks

Any of the above don’t work out Incompatibility of skills and personalities Planned tools may prove insufficient