The goal of the project is to work in a team of 5-6<\/u><\/strong>, and apply the concepts, techniques, and tools that you learn in this class to the development of an application in an iterative, incremental fashion. In the process, you will get practice assessing the quality of test cases, adding test cases by using systematic testing strategies, and using build tools (e.g., maven) to run a variety of testing tools and frameworks.<\/p>\n\n\n\n Do not use ChatGPT for this project. Disruptive team behavior will result in removal. Vulgar, crass, demeaning, condescending, etc, language, emojis, images, etc are unacceptable in all communication, verbal or online. Be professional and ethical.<\/p>\n\n\n\n Grading will involve both the process and the final products in each iteration.<\/p>\n\n\n\n The application involves building part of a project management system for a company to manage projects, workers, and their qualifications. The core logic will be implemented in Java and will have enums (e.g., ProjectSize and ProjectStatus) and classes (e.g., Worker, Qualification, Project, and Company). There will be controller classes (e.g., DBConnector and RestController). There will also be a front end using React and Javascript. There will be three sprints during which you will develop the functionality and systematically add test cases.<\/p>\n\n\n\n We posted a few short assignments in Canvas to gather information about your skillset, personality, GitHub username, and choice of project partner (only 001 students can choose a partner). You must submit your answers by Jan 23. This will let us form teams by the end of the first week of classes, and create GitHub teams and private channels in Microsoft Teams.<\/p>\n\n\n\n All your work for this project must be done in GitHub inside the CSU-CS415-Spring26 organization where we will create repos for each team. The repos will be accessed by the instructor and the GTAs for grading purposes. Activity in GitHub will be part of the process grade. You must start working from day one, and not procrastinate. You must follow the practices you learned in cs314 (e.g., regarding pull requests, frequently commit your work, etc).<\/p>\n\n\n\n Configure your GitHub username and email address on all systems you will use. If you have multiple GitHub usernames, use only the username you provided to cs415 and its associated email address for all work in this class unless you wish to work anonymously or use a pseudonym, and don’t want to get credit for your work in the class.<\/p>\n\n\n\n When you are adding or modifying code, good practice indicates that you work on multiple branches. Thus, you can freely create and remove branches. We recommend using pull requests and issues. All changes should be merged to main\/master.<\/p>\n\n\n\n Each team will generally have a few minutes to discuss in every lecture. Note that attendance is required in the lecture.<\/p>\n\n\n\n Outside of class, team communication must happen via Microsoft Teams. We will create private channels for each team inside the “CompSci CS415 Spr24” course team. Messages in the channels will be used for grading purposes.<\/p>\n\n\n\n The project will run from the second week of classes until the last week of classes. This lets us have three sprints, each about four weeks long (ignoring the gap caused by spring break). Here is a rough outline of what happens in each sprint. Details for each sprint will be available at the appropriate time.<\/p>\n\n\n\n
\n\n\n\n2. Project Topic<\/h2>\n\n\n\n
\n\n\n\n3. GitHub Usage<\/h2>\n\n\n\n
\n\n\n\n4. Teams communication<\/h2>\n\n\n\n
\n\n\n\n5. Sprints<\/h2>\n\n\n\n
\n