The final project of this course involves building an independent application that accomplishes a specific kind of task. This application should provide some sort of service or functionality for solving a problem related to: Entertainment Data Management Record Keeping Sales Search Analysis For your mid-semester project, you need to turn in a prototype of this application that you will then refine during the second half of the semester. This prototype does not need full functionality, nor does it need to have a full user interface ready. But, it should have a general outline of what the final product will deliver. Expectations for the Code The scope of this assignment is very loose. That is because I want you to carefully consider what is within your own power to develop on your own within the remaining weeks of the semester. Each person in this class has vastly different experiences and practice with development. One of the goals of the course is to familiarize you with design strategies for long-term software development practices. The complexity and grandeur of your final project is less important than demonstrating that you understand the design strategies we are exploring in this course and that you are integrating them into your own professional practice as a computer scientist. That being said, there are some metrics you should follow to make sure your Mid-Semester Project receives full credit (10% of your total grade). Your program incorporates at least one of the design patterns we are discussing in class, or shows how it will incorporate one or more design patterns by the time the final version is due. Your program clearly demonstrates the kind of service it will provide and has some kind of functionality, even if partial, to test out that service. Even as a prototype, your program should contain JavaDoc-style comments to guide others through the design of the program and inform them of current functionality or planned functionality for future iterations. Your prototype must contain JUnit-style test files for the functional parts of your prototype. Don’t worry, we’ll be going over how to build these out in class if you’ve never seen them before. Additional Deliverables In addition to turning in your code, you will also need to submit a Project Roadmap that describes what has been completed already and what you are planning to implement by the end of the semester. This roadmap should contain the following: A description of what the completed project will be, its intended purpose, and planned audience. This should be at least a paragraph of information about the project, what its objectives are, and the imagined audience it is being built for. What service is it going to provide, and how? An outline of the project, including both completed and planned functionality. This can either be presented as a flow chart, a diagram, or some other visual representation. You could even use a gantt chart (https://en.wikipedia.org/wiki/Gantt_chartLinks to an external site.). Whatever this visual representation is, it should account for what is complete, what is in-progress, and what you want to work on implementing that you are still struggling with. It should demonstrate that you are thinking about how to wrap this prototype up within a timely fashion so that it is complete by the end of the semester. So, what are you turning in on October 31? Your prototype code, complete with JavaDoc comments and JUnit tests for each method that is working correctly A project roadmap document that contains all the requested information.
Discuss what you are planning to implement by the end of the semester.
October 24, 2023 Comments Off on Discuss what you are planning to implement by the end of the semester. best service Assignment-helpThe final project of this course involves building an independent application that accomplishes a specific kind of task. This application should provide some sort of service or functionality for solving a problem related to: Entertainment Data Management Record Keeping Sales Search Analysis For your mid-semester project, you need to turn in a prototype of this application that you will then refine during the second half of the semester. This prototype does not need full functionality, nor does it need to have a full user interface ready. But, it should have a general outline of what the final product will deliver. Expectations for the Code The scope of this assignment is very loose. That is because I want you to carefully consider what is within your own power to develop on your own within the remaining weeks of the semester. Each person in this class has vastly different experiences and practice with development. One of the goals of the course is to familiarize you with design strategies for long-term software development practices. The complexity and grandeur of your final project is less important than demonstrating that you understand the design strategies we are exploring in this course and that you are integrating them into your own professional practice as a computer scientist. That being said, there are some metrics you should follow to make sure your Mid-Semester Project receives full credit (10% of your total grade). Your program incorporates at least one of the design patterns we are discussing in class, or shows how it will incorporate one or more design patterns by the time the final version is due. Your program clearly demonstrates the kind of service it will provide and has some kind of functionality, even if partial, to test out that service. Even as a prototype, your program should contain JavaDoc-style comments to guide others through the design of the program and inform them of current functionality or planned functionality for future iterations. Your prototype must contain JUnit-style test files for the functional parts of your prototype. Don’t worry, we’ll be going over how to build these out in class if you’ve never seen them before. Additional Deliverables In addition to turning in your code, you will also need to submit a Project Roadmap that describes what has been completed already and what you are planning to implement by the end of the semester. This roadmap should contain the following: A description of what the completed project will be, its intended purpose, and planned audience. This should be at least a paragraph of information about the project, what its objectives are, and the imagined audience it is being built for. What service is it going to provide, and how? An outline of the project, including both completed and planned functionality. This can either be presented as a flow chart, a diagram, or some other visual representation. You could even use a gantt chart (https://en.wikipedia.org/wiki/Gantt_chartLinks to an external site.). Whatever this visual representation is, it should account for what is complete, what is in-progress, and what you want to work on implementing that you are still struggling with. It should demonstrate that you are thinking about how to wrap this prototype up within a timely fashion so that it is complete by the end of the semester. So, what are you turning in on October 31? Your prototype code, complete with JavaDoc comments and JUnit tests for each method that is working correctly A project roadmap document that contains all the requested information.