Difference between revisions of "Software project proposals"

From Knowledge Kitchen
Jump to navigation Jump to search
(Submission)
(Tags: Mobile edit, Mobile web edit)
m (For whom?)
 
(3 intermediate revisions by the same user not shown)
Line 4: Line 4:
  
 
Write a proposal for a software product you would like to pursue for the majority of the semester.  Make it obvious, interesting, and make the need for it sound convincing.
 
Write a proposal for a software product you would like to pursue for the majority of the semester.  Make it obvious, interesting, and make the need for it sound convincing.
 +
 +
Please do not write more than 2 paragraphs.
  
 
== What to include ==
 
== What to include ==
Line 14: Line 16:
 
Who will this software be for?  These people are your end-users or customers.
 
Who will this software be for?  These people are your end-users or customers.
  
Do not make software for imaginary users who do not exist - you must have real people as your initial end-users.  Tell us who they are.  For example, ask local business, a campus office, a professor, or friends or family - but find someone with whom you can discuss your software and have them test it periodically.
+
Do not make software for imaginary users who do not exist - you must have real people as your initial end-users.  Tell us who they are.  For example, is it for a particular type of business, mass consumer, a campus office, a professor, or friends or family, or ... people just like you.
  
The end-user will help refine the specifications, provide feedback (to you) over the course of the project, and do acceptance testing at the end. They may also reject compromises that might seem reasonable to you and will help you prioritize the features.
+
Understanding who your end-users are, and ideally speaking with some along the way, will help you refine your designs to be suitable for your audience, and understand whether you have succeeded at the end or not.
  
 
=== How? ===
 
=== How? ===
Line 22: Line 24:
  
 
=== Scope ===
 
=== Scope ===
A brief (one paragraph) justification that the proposal is neither too easy nor too ambitions for a group of approximately 4 or 5 programmers to undertake in one semester.
+
A brief justification that the proposal is neither too easy nor too ambitions for a group of approximately 4 or 5 programmers to undertake in one semester.
  
 
==Submission ==
 
==Submission ==
Submit your assignment as a message to the Professor on Slack by the due date indicated on the schedule. The message should have the following format:
+
Submit your assignment as a message to your private assignments Slack channel by the due date indicated on the schedule. The message should have the following format:
  
 
  Product proposal: <Your Project Title>
 
  Product proposal: <Your Project Title>

Latest revision as of 18:23, 7 September 2019


Overview

Write a proposal for a software product you would like to pursue for the majority of the semester. Make it obvious, interesting, and make the need for it sound convincing.

Please do not write more than 2 paragraphs.

What to include

Your proposal must focus on the product's value proposition, including answers to the questions below. Keep it thorough but concise. Do some research on how to effectively write a product proposal before submitting.

What and why?

What software system would you like to build this semester, and why? Include a description of what problem the system would solve and why this is important.

For whom?

Who will this software be for? These people are your end-users or customers.

Do not make software for imaginary users who do not exist - you must have real people as your initial end-users. Tell us who they are. For example, is it for a particular type of business, mass consumer, a campus office, a professor, or friends or family, or ... people just like you.

Understanding who your end-users are, and ideally speaking with some along the way, will help you refine your designs to be suitable for your audience, and understand whether you have succeeded at the end or not.

How?

A description of what the system will do from an end-user's perspective. Be as complete as necessary to fully explain the system, but do not worry about technical implementation - this will be developed in subsequent work.

Scope

A brief justification that the proposal is neither too easy nor too ambitions for a group of approximately 4 or 5 programmers to undertake in one semester.

Submission

Submit your assignment as a message to your private assignments Slack channel by the due date indicated on the schedule. The message should have the following format:

Product proposal: <Your Project Title>
<Your Name>
<Your NYU Net ID>
<Your Proposal>

Your proposal should be written in plain text with no formatting. Please do not send an attachment and by all means please do not post a video of yourself explaining your idea on YouTube.

What happens next

I will select a subset of the proposals that I think will be the most interesting and appropriate for this course. These will be published to the class (without the names of the proposers). Your next assignment will be to rank your favorites. I will then make team assignments based on this information and the answers you have provided to the previous introductory questionnaire.

If your proposal is selected, you are guaranteed to be part of that team.


What links here