1 / 8

OpenSpace - Collaborative Art Game

OpenSpace is a collaborative art game where players work together to create art in a limited timeframe using a small and randomized set of strange artistic tools. It is designed for people who enjoy playing light-hearted games with a creative element, such as children and elder people. The game serves the purpose of entertainment and mild educational purposes, enhancing children's artistic abilities and promoting social interaction. The idea was inspired by Pictochat, iSketch, and Kidpix, creating a semi-competitive computer game. The system and software architecture include client/server functionalities and basic game modes for the illustrator and assistant. OpenSpace follows a hybrid lifecycle model, combining design-to-schedule and evolutionary prototyping. The project aims to release high-priority features first, while constantly gathering player feedback to improve and add low-priority features. The stakeholders include the development team, project managers, testers, and game players. The feasibility rationale identifies risks such as the difficulty of implementing custom server/client architecture and challenging image processing effects. However, overall feasibility suggests that OpenSpace will provide valuable practice in various aspects of software development and deliver an entertaining and creative outlet for game players.

alicef
Download Presentation

OpenSpace - Collaborative Art Game

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. OpEnSpaCe LCO Proposal Calvin Chin Mikiko Jama CSE403 Summer 06

  2. Operational Concept (what is it?) • What is it? -a collaborative art game in which players work together to create art in a limited timeframe with a small and randomized set of strange artistic tools • Who is our target customer? -people that enjoy playing light-hearted games with a creative element. ----example: children , elder people • For what purpose? - for entertainment and mild educational purposes example: can be an educational tools to enhance children's artistic abilities and social interaction • Where did we get the idea? - Pictochat , iSketch,and Kidpix mashed together into a semi-competitive computer game.

  3. System Requirement (How does Openspace Play?)

  4. System and Software Architecture ( How?)

  5. Lifecycle Plan 1(Who wants it? Who’ll support it?) • Which lifecycle do we chose? • A hybrid between the design-to-schedule and evolutionary prototyping model -High Priority Features: + Client/server + Basic game modes of illustrator and assistant -Low Priority Features: +Different effects (different kinds 0f pencils and brushes, music/sound • Why? -The fixed shipping date(the end of this quarter) -Easy to set a schedule -Ability to get constant feedback from players to improve features

  6. Lifecycle Plan 2(Who wants it? Who’ll support it?) • How do we approach? -The first cycle : do the high priority features Software concept, Requirement Analysis, Architectural Concept, coding, testing , release, feed back -The second+ cycles: modify features based on the feed back or add more low priority features coding , testing , (release, feed back) -Final release • Who are our stakeholders? -Stakeholders: Us (developers, project manager, testers) Game players including us! • Who is responsible for what? (assuming we have a team of four ) 1 project manager – the manager is a multitask player (he/she can be also dev, or tester) 3 developers – who switch from task to task

  7. Feasibility Rationale1(Can we really do this?) • Risks: - Custom Server/Client architecture is toodifficult to implement in the timeframe given. - Many image processing effects provided in game may be too difficult to implement. - Feedback may indicate issues with core components of Openspace, but we will not have time to go back and redesign them.

  8. Feasibility Rationale2(Can we really do this?) Overall Feasibility: Openspace will certainly not be an easy project, but it will provide practice with many aspects of software development, including realtime client/server architecture, graphical effects rendering, UI development, graphical and audio resource development, and the integration of all these components to create something that has only one purpose, and that is to provide entertainment and a creative outlet for game players.

More Related