Skip to content
This repository has been archived by the owner on Aug 27, 2024. It is now read-only.

Commit

Permalink
Minor tweaks to project and publish
Browse files Browse the repository at this point in the history
  • Loading branch information
JHawk0224 committed Mar 28, 2024
1 parent 5d525fb commit bff5c4d
Showing 1 changed file with 20 additions and 6 deletions.
26 changes: 20 additions & 6 deletions content/homework/project.mdx
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Final Project
isReleased: false
isReleased: true
releaseDate: 2024-03-25T00:00:00-04:00
dueDate: 2024-04-25T17:00:00-04:00
auxiliaryDates:
Expand Down Expand Up @@ -74,13 +74,13 @@ The first stage is coming up with your app's user stories. User stories are a te

Here are some key steps to follow when creating user stories:

1. Identify your users
1. Identify your users:
Determine who your target audience is and what their needs and goals are. This will help you create user stories that are relevant and valuable to your users.
2. Write user stories from the user's perspective
2. Write user stories from the user's perspective:
Each user story should be written from the perspective of the user, using the format "As a [user], I want to [action], so that [benefit]". For example, "As a busy professional, I want to quickly add new events to my calendar, so that I can stay organized and on schedule."
3. Keep it simple and specific
3. Keep it simple and specific:
User stories should be concise and specific, focusing on one feature or functionality at a time. Avoid adding unnecessary details or technical jargon that may confuse the user or the development team.
4. Prioritize user stories
4. Prioritize user stories:
Determine which user stories are most important to your users and prioritize them accordingly. This will help you focus on the features that provide the most value to your users.

### Stage 2: Lo-fi Prototype
Expand All @@ -102,6 +102,20 @@ A Hi-Fi (high-fidelity) prototype is a more polished and detailed version of a p

It is usually developed through Figma or similar software, although some designers prefer to draw traditionally by hand. For the sake of the project, you are not required to have a hi-fi prototype, although it is highly encouraged and recommended.

### Milestone 1 Submission
Please provide the above sections in a PDF. For each of the above, you must include
1. Stage 1 - User Stories:
* your app's target audience group (user persona) along with a short paragraph describing your audience in relation to your service
* minimum of 5 user stories
* order of priority for the user stories (most important to least important)
2. Stage 2 - Lo-Fi:
* Clear scans of your Lo-Fi prototype, drawn on paper. Drawings must be clear and orderly. Do not draw squiggly lines.
* Include all of the screens of your app, along with arrows or any form of description of the navigation graph
3. Stage 3 - View Hierarchy Diagram:
* A View Hierarchy Diagram for each of your app’s screens
4. (OPTIONAL) Stage 4 - Hi-Fi:
* Link to your Figma design (or clear, crisp scans if drawn by hand)

## Requirements

As mentioned earlier, this app is very open ended. However, you will be required to include at least 2 concepts covered in the course including:
Expand Down Expand Up @@ -147,7 +161,7 @@ Some relevant course material:
* [Slides](https://www.seas.upenn.edu/~cis1951/lectures/09-data-persistence/slides.pdf)
* [Code](https://github.com/cis1951/lec9-code)
* Lecture 11: App Design & UX
* Slides TBD
* Slides TBA
* [Other Resources](https://www.seas.upenn.edu/~cis1951/resources/)
* [Course GitHub](https://github.com/cis1951)

Expand Down

0 comments on commit bff5c4d

Please sign in to comment.