CSA Sprint #1 Checkpoint #1 Ideation Part A

jm1021 commented 10 months ago

Ideation Plans

The two trimester final project will be worked on in teams. Team will use this timeline for Teaching and JWT adds. Team will need to maintain their own Project Time for their features that correspond to CheckPoints in this calendar.

Teacher starters, generative AI code and 3rd party can be used. However, it needs to be cited, which is part of our ethical computing learnings. My recommendation is to use starter code from spring_portfolio and teacher_portfolio. That you and your group spend time refactoring code to be appropriate basis to start your project.

Ideation Requirements

These are guidelines to help you progress in both CSA CB curriculum and Data Structures Mira Costa requirements.

Picking Team and Project

Everyone is suppose to pick a project and team that shares their own interests. In picking team members, make sure you have common interests, common work habits, and common goals. Interests and purposes could align in college major, common classes, or common clubs.

Teacher will assist and encourage on great choices. Of course, a project that both teaches and has purpose will motivate the Teacher to observe that you are progress on his key indicators.

Frameworks, Rest API, and Database paradigm

Absolute requirement. The backend must be done in Java. Also, Java must have a central role in your project for managing Data and Data Structures. This includes use of Spring, REST services with Spring, Spring Security, JWT, JPA, and SQL.

Classroom common requirement. The frontend (FE) for user must be done in JavaScript and GitHub Pages. User Login and screens and designs will use SASS for style. There must be clear separation between CSS/Style and HTML/DOM.

Backend (BE) and Thymeleaf. The backend must have an administrative UI. The backend framework that you were given utilizes bootstrap, you can change this to any framework of your choice. To support backend design here is an [older project](To support backend design here is an older project)

Teacher expects that your program follows the REST API and Database paradigm. There must be evidence of this paradigm in your project, in multiple places.

Checkpoint #1 indicators

Teams will start projects with Brain Write/Ideation, Design Documents. Performing these tasks will help students work more effectively in teams. Indicators will be broken into two steps...

Checkpoint A. Plan/In Progress.

Elements of design are in progress by all team members
Evidence of design asset ownerships as show in list below

Checkpoint B Plan/Code ready

Well developed design assets
Issues in Table view with a 1st Sprint cycle lining up to #88
Consideration of individual JWT work

Design Assets

Get comfortable with the design step. Spend the time and effort to go from uncomfortable 'till you get start to get a little feel. Iteration starts with uncomfortable.

Use draw.io to do story mapping and test planning
Use tools to design screens before implementation is Figma or Canva or simple Markdown/HTML/CSS screens
Use draw.io to create uml activity
Use draw.io to create uml class 0r Use draw.io to draw entity relationship diagram