D424 Software Engineering Capstone - Task 1

Your first step in D424 is to decide on a project idea and get approval from a course instructor. Approval cannot be handled over a phone call because we have to sign the form itself. It can only be handled through email. If you are developing a mobile app and are using Google Play for required deployment, it is recommended you sign up now for a developer account. Google's process can take anywhere from 1-3 days, however, we have noticed that sometimes it can take several weeks. To avoid an unexpected delay, we urge you to start that process now.

The Approval Process:

Complete the form and email it to your instructor.
The instructor will either approve it or request more information/send feedback for revisions.
Once the instructor emails your signed form, you will then submit it through Task 1 in the Course of Study as proof that your project has been approved by an instructor.

Please include app-type (mobile or web) and language for backend development. Leaving this information off your form will result in longer approval times.

Project Requirements

To qualify for approval, your app must be:

It should be a full stack web-based application or a mobile app. Plug-ins, applets, and desktop apps are not allowed.
C# students - if you are interested in modifying a desktop app into a web app, see this tutorial: Tutorial for Moving a Desktop App to a Razor MVC app
It must be hosted in the cloud.
Use a database that allows end users to insert, update, and delete data entries.

Download Approval Form

Explanation of Approval Form Fields:

INFORM INSTRUCTOR:

Potential use of proprietary company information: (Y/N)

Most students don't use proprietary company information. If you do choose to use a project built for work, you must mark this as 'Y'.

LANGUAGE(S):

List the major programming languages you'll use for your project.

Application Type:

Please mark whether it is a web app or a mobile app.

Project topic AND description:

Tell us what type of app (mobile, web-based).

Project purpose AND goals:

Tell us what your app will do.

If your version of the form has the words "predictive" and "descriptive", you can delete them. They have no relevance in the context of software engineering.

DESIGN and DEVELOPMENT:

Explain why the problem and software product you have proposed are worthy of study:

Any reasonable answer will do. This isn't really evaluated and any reasonable answer is accepted.

Projected outcomes and deliverables:

Any reasonable answer will do.

Estimated number of hours for the following:

Estimates are fine. This is meant as an exercise to consider how long it might take for each step of the process. You are not expected to meet these time estimates.

Planning and design
Development
Documentation
Total

Projected completion date:

Again, an estimate is fine.

IMPLEMENTATION and EVALUATION:

Describe how you will approach the execution of your project: A bulleted or numbered list highlighting the various steps you'll take is fine.

RELEASE FORM

You only need a release form if you are using proprietary information (code) from an employer or other source. If you aren't borrowing code, the approval form is the only thing you need to submit in Task 1. If you are using a project from work, which is the most common reason to use the release form, your employer will sign it. Its purpose is to show you have permission to use that code. You do not need to have a signed release form to use libraries.

If you have further questions on a project idea, please reach out to your instructor.