CSCI4910 – Summer 2014

Final Project and Presentation

Putting It All Together

In small groups of 3-4 people, develop a multi-page website/web application of your choosing. You may create a site for some purpose such as:

A club, organization, church, civic group, etc. to which someone in your group belongs

A business – real or conceptual

A great idea

A series of tutorials

Nature

Science

Sports

Gardening

Crafts

Fitness

Hobbies

Faith

Music

It should include most of the major features covered this term including but not limited to:

Common look-and-feel using Master Pages and Themes. Strive to make the appearance of the site colorful but tasteful, and include graphical elements (pictures, drawings, video clips, etc.) frequently to enhance the attractiveness of the site.

About page with information about the content members and their roles as well as about the project itself. Use the AssemblyInfo.cs appropriately.

Sitemap navigation using menus and breadcrumbs – if appropriate.

Multiviews and views - if appropriate.

Data-driven dynamic pages using databases and LINQ. Use lambda expressions if feasible.

Authentication and authorization using the ASP.NET support.

If there is a convenient way to utilize an existing web service naturally (say to provide current news, weather, business information such as stock market info or exchange rates, or other pertinent information), that would be a nice plus.

AJAX Controls, client-side execution

You may use MVC or MVVM for your application if you wish.

Adding features and making your application “mobile friendly” is a plus.

Deliverables

There are two primary deliverables. Please submit all in an appropriately named .zip folder via the OIT Drop Box by the date of the presentation.

  1. The project or projects that build and support the site in question delivered as was done with previous assigned projects. Be sure that the group and each person in the group are clearly identified in comments, cover pages, etc. without having to search for them. Also identify the role(s) that each participant played.
  2. A PowerPoint presentation in which all members of the group must participate (in a speaking role) in class. Each person in your group must have a speaking role, and the roles must be roughly of equal duration. Include the presentation's slides in the zipped file containing the projects that you submit. Target the total presentation for between 45-60 minutes. It should include a thorough demo of your website as well as the slide presentation. If you used any interesting features not previously discussed in class, please include a discussion of the feature(s), code needed, usage tips, and so forth.
  3. In the presentation be sure to
  • Introduce the team members (with a few personal comments if appropriate)
  • Introduce the project you did and introduce the prominent features and limitations
  • Demo the project including a discussion of ASP.NET features you included. Focus on “how to.”
  • Conclude with lessons learned, future plans (if any), and recommendations
  1. The purpose of the presentation is two-fold.
  • A presentation of your work (as you might deliver to a client) showing the interesting functionality of the application and design choices you made
  • A discussion of new features you discovered and used in the project, lessons learned (such as things you would have done differently if you had to start over and hints about how to do something that you had to dig a little to discover). For this, your PowerPoint presentation should take the form of instruction to the rest of the class.

Course Roster and Email Addresses

To facilitate your selection of and communications with your teammates, I have included a class roster with email addresses. Please select and contact your team ASAP. There are enough students registered for credit to create 4-5 teams. If someone you don’t know or don’t know well asks to join your team and if there is room for another person, please allow the requesting person to join your team. The team can select its own “leader”, and assign each member roles (e.g., design, coding, documentation, database support, etc.) within the project. When your team is complete please give the instructor a list of team members.

Baker, Landon Woodrow<>

Carroll, Caleb Baron<>

Cross, Bradley Scott<>

Ferguson, Jacob

Finke, Logan Michael<>

Gargett, Ross<>

Garner, Amos A<>

Giuffrida, Marc Anthony<>

Harmon, Phillip Andrew<>

Harris, Tommy Ray<>

Hawkins, Kimberly (Audit)

Lynn, John Wesley<>

McNeese, Brian Henry<>

Moradi-Nowghabi, Armin<>

Patel, Jaydeep<>

Patel, Kevin S<>

Query, Ryan James<>

Vance, Ranae A<>

Presentation Dates

Presentation dates are Tuesday and Thursday of the last week of the term. The teams to present on each day will be determined during class discussion.