1 / 8

Intro to the CS4240 Project

Intro to the CS4240 Project. Slides from Oct. 14 2010. Project Deliverables. The project will have four deliverables A deployed working system, with supporting artifacts (build scripts, unit tests, etc.) A design document (description and reflection)

keahi
Download Presentation

Intro to the CS4240 Project

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. Intro to the CS4240 Project Slides from Oct. 14 2010

  2. Project Deliverables • The project will have four deliverables • A deployed working system, with supporting artifacts (build scripts, unit tests, etc.) • A design document (description and reflection) • A demonstration and presentation to the instructor or TA. • Project artifacts stored in a version control system (Redmine) showing all team members worked on the project over time.

  3. Project Topic • You can choose your own topic, or some provided topics will be given. • The following requirements must be met: • It must be based on an extensive existing codebase (any significant open source project, Tomcat, .NET, a plugin for Eclipse, Firefox, Chrome, etc). • It must be something that can be appreciated/understood by those not on the team • It can’t overlap a course-project etc. done for another course. • The team must use a set of SW tools • Using third party libraries is a Good Thing To Do • Code must be developed by multiple people • Everybody must contribute to all parts (i.e. nobody only does documentation)(continued on next page)

  4. Project Topics • Requirements related to design: • The project should have a significant architecture (e.g. a high-level design) • Ideally you should be able to use design patterns appropriately • You will need to document your design (UML, words) • You will need to describe design alternatives and pros and cons for your design choice • Bottom line: You will have a design description and reflection document that demonstrates aspects of your knowledge of SW design

  5. Approval: I must approve your project topic and outline • Ideas for topics: Forum on Collab site • Shop your ideas to seek team members • Suggest for others. (Good ideas for others rewarded) • Submit ideas by email to me • If you have team members or needs, include that

  6. Teams • Team size: 3 is ideal • Two is possible, but I may add someone to your team • Four will only be OK if scope of project is larger (e.g. two halves)

  7. Provided Projects • I’ll provide some ideas for projects if you can’t think of something or find a project • One will involve Tomcat • Likely a plug-in (perhaps Eclipse) • Others from the forum?

  8. Dates • Decide project topic and team within two weeks • Oct. 28 • Mid November: interim report • Final deliverables: last day of class • Demos may go into exam week. Flexible.

More Related