Notes on Deliverables (unless otherwise directed by your instructor)

• Team Project Deliverables and Homeworks are due PRIOR TO NEXT CLASS (i.e. the week after they appear on the schedule).
• Your instructor will clarify the format and manner in which project deliverables are submitted (e.g. via dropbox, Wiki or other)
• Unless otherwise specified, all submission should be in .pdf format.
  

Project Inception

Ideas that Matter to You

For this activity, you will create a basic plan for the team project that you will work on throughout the semester.

As a team think about a problem that you wish you could solve, or a cause that you would like to support. Keep it real, make a difference. Here is a list of topics to help get you started:

• Climate change
• Cancer research
• Syrian refugees
• Volunteer work
• Pandemic response
• Mental health awareness
• World peace
• World hunger
• AI ethics
• ... Many more ...

Project Statement

The project description should state the name of the project, the motivation, the goals, and the intended users. The project description should be 1-2 paragraphs long. An example of a project description can be found here.

Notice the primary components/features of the statement. It is very direct, concise, and discusses the primary mission of the project.

Submission Instructions

Prior to next class, submit the completed project description as a .pdf to the team submission area in MyCourses.

Requirements

This week, your team will submit both your requirements document and your updated Trello board.

Project Requirements

Gathering requirements is a paramount step in the creation of any project. In this activity, you will create the requirements document for your team's project. Here is a sample requirements document that you may use as a starting point. Some things to note when creating a project's requirements:

• Be as clear and to the point as possible.
• Don't be concerned with how you will create something, focus more on what you should create.
• Don't invent requirements. When in doubt, ask the customer (in this case the customer is you, so you've lucked out.)
• Remember that an ounce of planning saves hours of wasted development time.

Trello Board

Project management and task planning is a central component for almost any software project. For your team's project, you will be using Trello as a project management tool. Throughout the course of the project, your team's Trello board show constantly change as tasks are created, executed and completed. This initial submission will provide your team with the ability to gain a foundational understanding of not only how to use Trello, but more important provide exposure to project management in software development.

In this submission you should:

• Ensure that each team member has a Trello account.
• Your team has a shared Trello board.
• In your team's Trello board you should:
• Create a card for each main activity.
• When relevant, assign each task to a team member.

Submission (team):

• Your team's requirements document.
• A link to your team's Trello board should be included in the requirements document. Please note, that for any submission, your instructor or TA may access your Trello board at any point after the due date. Therefore, please ensure that your Trello board is up to date at the time of submission.

The team-based assignment is due by the start of class next week and all documents should be submitted to the Project-Requirements area in Mycourses.

Modeling and Design

Teams will be allotted time to model their system with use cases, and create a digital mockup of their project using wireframes. Revisit your team Trello board. Update the tasks and plan who will be responsible for each task. Estimate the time it will take to finish each task.

Modeling and Design

1. Draw a use case diagram that depicts the users and their interactions with the system. You can share your diagram with the rest of your team.
2. Review the requirements document and the features of your product. Think of who will be using the system, and what actions potential users can take.
3. Create your UI mockup using Google slides. You are are encouraged to produce a well thought out design. The design should show the different screens you plan to build, and the elements on every screen e.g. text, buttons, and images. The design should also depict the navigation between the screens.

Submission (team):

• Use case diagram (pdf)
• Digital mockup
• Submit as a link in your use case diagram.
• Be sure to give your TAs access.

Use "Project - Design" submission area.

Project Presentation

Please review the Final Project presentation assignment.