The purpose of this final project is to take all the skills that you gained from the course and use them to create your own web site using Visual Studio 2017 C#, ASP, and .NET 4.6.
The actual project that you develop will involve finding a process, task, service or other “deliverable” that you can address with a website. It will also be crucial that your proposed website project is feasible in the time available.
There are several steps to this process that you will need to follow:
- Pick a task/process/service/“deliverable” that you can address with this particular programming and design/development environment and submit a proposal, outlining what your website project will do. Submit your initial proposal for approval.
- Storyboard your entire website interface (every page and every control within every page) with a focus on design and usability.
- Work out the logical and/or programming design of your website and controls.
- Submit #2 and #3 for approval before beginning any serious work on your website.
- Actually create your website, including all proper commenting and other documentation.
- Submit your Final Project Website by the prescribed deadline.
Brainstorm at least six (6) ideas that you would like to pursue for this project. Write them all down! What is going to be the focus of your project? Is there a particular task or type of task you would like to address with your application/site? Is there an area of interest you have that suggests possible projects(s)? Do you want a website that creates, manipulates, displays, or some combination? AGAIN, write down all the ideas you come up with or consider, but make sure your list includes at least six (6) ideas.
Before you begin any serious work, you will need to submit a brief but detailed proposal for your project. Make sure you are aware of the deadline for this submission. What you need to do in your proposal is very basic:
- List all the ideas (at least 6) that you brainstormed for Phase 0,
- Explain why and how you decided on the one specific project, which one out of 6, you will be describing in detail,
- Describe your proposed project in sufficient detail that the reader gets a very clear idea of your goal(s)
- Clearly explain why you think this would be a fun/useful/interesting website, and,
- Clearly explain why you are confident that you can successfully complete this project in the time allowed.
Once your Phase 1 is approved, you can begin the actual design of your website. The first question you need to deal with here is how best to “deliver” the functionality of your chosen task, process, or service using a website, consistent with user expectations and experience. Based on this you can sketch out what web pages you will need, what Controls and/or other visible features you will want to include, as well as the manner in which they relate to each other. You MUST consider how CSS will help you in your design. You should always keep in mind the basic principles of Design and Usability discussed at the beginning of (and throughout) this course. You will be asked to explain how your project addresses these principles as part of Phase 2 of this Project.
You must also clearly define what programming or logical elements you need to make your website a reality. You must have at least five (5) distinct “code-behind” or ASP.NET Controls in your Final Project. What functions and/or methods will you need to employ? What sorts of visible/invisible objects/controls will you need to use? What events will you need to handle and how? What external resources (images, data, sounds, movies, etc.) will you need your website to access and how? You are encouraged to “experiment” with some of your proposed logical features, but only insofar as they establish a “proof-of-concept” in your own mind. While 2a is where you address the visual design of your controls, 2b is where you address what it will take to make them DO what they need to do. BE SURE you clearly understand this cannot be a simple, HTML-only, “point-and-click” website. You MUST use C# and ASP and demonstrate your understanding and “mastery” of both.
Your website storyboards together with your logical design will represent your Phase 2 “formal proposal” for the Final Project. You do not have to wait for approval on this phase to begin working on your web pages, controls, etc., but it is in your own best interest to complete Phase 2 before you begin any serious work on the final application.
Now you are ready to actually create the website. Make sure to pace yourself - you do not want to do this all the night before.
Package your Final Project in a single file that can be submitted to Canvas. BE SURE that you include all appropriate comments in every .aspx and aspx.cs file that is part of your website AND a README.TXT file in the root folder that carefully describes what your website does and how it does it.
ALSO make sure to include two (2) files in the root folder. One should be a User’s Guide that carefully describes what your website does and how it does it for someone who has no idea what it is or how it works. While your design and use of “user knowledge” and “user expectations” should make this file redundant, we want you to create and include it anyway. Second, include a README.TXT file where you tell us, the evaluators, whatever we need to know to build, run and evaluate your project. This file will include any files we need to load, copy or otherwise manipulate, and anything else we need to know. We will read BOTH of these files BEFORE we build, run and evaluate your project website.
We will be collecting these various parts of the project in phases. The phases will be similar to the written MINI and larger work-based Assignments that you have been doing. Keep in mind that each Phase may take you more than the time you may have spent on these other assignments as they should be more involved.
This will be Step 1 from the General Description above. You will need to turn in a written document, created with a word processor (no handwritten submissions accepted) in hardcopy only with your name and email address. You should include all six (6) ideas (from Phase 0) that you thought of for this final project - with ONE (and only ONE) of your ideas clearly indicated as the one you have selected and are proposing as your final project. You want to include a clear description of the selected task, process, service, or “deliverable” that you want to address with your proposed website. Make sure that you clearly and specifically DO ALL OF THE FOLLOWING in your Phase 1 paper:
- List all the ideas (at least six (6)) that you brainstormed for Phase 0,
- Explain why and how you decided on the specific project (which idea of the 6 in #1) you will be describing,
- Describe your proposed task/process/service/“deliverable” and its website in sufficient detail that the reader gets a very clear idea of your goal,
- Clearly explain why you think this would be a fun/interesting/useful website,
- Clearly explain why you are confident that you can successfully complete this project in the time allowed.
This will be steps 2, 3, & 4 from the General Description above. You will need to have your entire set of storyboards for the project you are doing. Yes, this means you will actually draw or otherwise represent on paper the overall design and component relationships of your entire website, including every web page, every visible control, all navigational elements, etc. If you have any interactivity clearly show this in the storyboard. ALSO, you will need to turn in a written document component created electronically (not hand-written) with your name and email address that very clearly and precisely addresses the logic of how you intend to create the under-lying functionality of your entire project site using ASP/CSS/C#/Visual Studio 2017. Remember, you must have at least five (5) distinct “code-behind” or ASP.NET Controls in your Final Project. Again, be sure you discuss:
- What functions and/or methods will you need to employ for your controls to work?
- What sorts of visible/invisible “objects”/controls will you need to use?
- What events will you need to handle and how?
- What external resources (images, data, sounds, movies, etc.) will you need your website to access and how?, and
- How will your Project Design address.
- Anything else you deem appropriate to help the reader understand your project and your plan.
ALSO BE SURE TO CAREFULLY REVIEW THE PHASE 2 DESCRIPTION IN THIS DOCUMENT TO BE SURE YOU HAVE ADDRESSED ALL THE MAJOR REQUIRMENTS.
General Scoring Matrix: Storyboard/Design Component: 35 points, Logical/Technical Strategy Component: 35 points.
This will be steps 5 & 6 from the General Description above. You will submit your final completed project by the time above. BE SURE to submit your entire project folder/filesystem as a single ZIPPED file to Canvas. There is already a “Final Project” Assignment for each student to submit the project on Canvas. NOTE: Be sure your submission file is created with a WinZip-compatible tool or is a self-extracting archive file. No “.tar”, “.rar”, or “.7z” files please. If we can’t open it, we can’t grade it.
VERY IMPORTANT: UITS STRONGLY recommends using ONLY a wired connection for large file transfers to Canvas. They also STRONGLY suggest using on campus computers to further insure a successful upload. REMEMBER: Late submissions will NOT BE POSSIBLE, resulting in a score of 0 for Phase 3 and an “F” in the course.
This entire project counts for 45% of your final grade and will be evaluated on a 100-point scale.
The grading will be split into 70% for “the project” and 30% for “the design process.” Because the actual design and creation process you go through is very important to the final project I am including it as a major component of the overall grade. The design process score will be based upon the submissions you make for Phases 1 & 2. The project is what you will submit for Phase 3.
Phase 1 will be scored on a 30-point scale and Phase 2 will be scored on a 70-point scale and the two scores added together to calculate the “design process” part of your score. [NOTE the potential impact on your overall score if you fail to submit Phase 1 or Phase 2, you submit them late, or give either of them a sub-standard effort.]
Project grading will be based on the individual. We will not be grading on an absolute scale, but will take into account what you have shown us from the beginning, as well as how well you realized your pre-stated goals and how much of an improvement you may have made since then for your final project submission. This is designed to take into consideration the fact different students bring different levels of experience with them to this course.
Phase 3 will be scored on a 100-point scale. Your score will be a composite of the scores from the Instructor and the 2 UIs in this course. Here are the things that we will be looking for and the relative “weight” each will carry out of the 100 points for your actual submission. These 100 points for Phase 3 will then become 70% of your Final Project score.
- Consistency of Elements and Style (fits with stated goal/plan). (15)
- Provide Clear Navigation (fits with stated goal/plan). (10)
- Logical Grouping of Tasks (fits with stated goal/plan). (5)
- Prioritization of Visual Elements (fits with stated goal/plan). (5)
- Care for the User (consistency with expectations and experience of average user). (15)
- Effective use of available Mark-up and Programming objects/types (20) Effective use of events, functions, and methods (10)
- Clearly written mark-up and code (organization) (10)
- Clearly and properly commented code/file (5)
- Documentation (User’s Guide AND README.TXT) (5)
- Phase 1 (30 points) + Phase 2 (70 points) = up to 30 points of your OVERALL Final Project Score.
- Phase 3 (100 points) = up to 70 points of your OVERALL Final Project Score.
Your average out of this 100 points (30 + 70) = 50% of your A290/A590 OVERALL Final Grade.