Group1_Project_Plan - Project Plan Group: MultiType (Team...

Info iconThis preview shows pages 1–4. Sign up to view the full content.

View Full Document Right Arrow Icon
Project Plan Group: MultiType (Team 1) Members: Ryan Miller (Team Leader), Rodrigo Haragutchi, Azfar Khandoker, Yeong-ouk Kim, John Lima
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Table of Contents Purpose . . . . . . . . . . . 3 Background Information . . . . . . . . . 3 Subsystems and Planned Releases . . . . . . . 5 List of subsystems . . . . . . . . . 5 Build 1 . . . . . . . . . . 7 Build 2 . . . . . . . . . . 8 Build 3 . . . . . . . . . . 9 Risks and Challenges . . . . . . . . . 12 Tasks . . . . . . . . . . . 15 Build 1 . . . . . . . . . . 15 Build 2 . . . . . . . . . . 17 Build 3 . . . . . . . . . . 19 Cost Estimates . . . . . . . . . . 23 Team . . . . . . . . . . . . 24 Schedule and Milestones . . . . . . . . 25 Figure 1: Gantt Chart For Builds 1 and 2 . . . . . . 25 2
Background image of page 2
Purpose Our project will provide new functionality to an existing Integrated Development Environment (IDE), Eclipse, that will offer software developers the ability to edit the same source file simultaneously. The tool will facilitate collaboration on team projects in which editing the same file is a necessity. Currently, when working with version control systems, professional programmers follow a process of opening an editor, checking out a file, making modifications, committing and merging to a repository. Colleagues must then merge their files, often resulting in either inconsistent code and time wasted resolving issues. Student programmers may not use a repository, and rely on e-mail and instant messaging to send code for a team project. Our project aims to simplify and streamline these communication channels by combining the Eclipse environment with a real-time system to display changes. This will eliminate the need for a separate tool to share source code and will also increase productivity. Background Information Up to this point, our team has written a Problem Statement describing the problem our system will solve. On our own, we wrote a Domain Analysis document to determine our stakeholders and discuss competing software. We also wrote a Requirements Document outlining the functional and quality requirements. Finally, we completed a Design Document sketching out a high-level overview of our entire project and forming major decisions highlighted below: Creating a plug-in as opposed to a full editor, and using Eclipse as a platform for our plug-in (Issues 1 and 2) Using a client-server architecture instead of a peer-to-peer architecture (Issue 3) Our project’s primary stakeholders are software developers needing to collaborate on projects. Teams will no longer have to rely on time-consuming tools like merging within version control systems or traditional communication tools like e-mail or instant messaging. Existing projects that attempt to solve a similar problem:
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 4
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 02/21/2012 for the course CS 307 taught by Professor Staff during the Fall '08 term at Purdue University-West Lafayette.

Page1 / 25

Group1_Project_Plan - Project Plan Group: MultiType (Team...

This preview shows document pages 1 - 4. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online