First we task one needs to be completed and I have to submit it on my side before we can do task 2. The project has to be approved in task 1 before task 2 can commence.
Software Development Capstone Topic Approval Form The purpose of this document is to help you clearly explain your capstone topic, project scope, and timeline. Identify each of these areas so that you will have a complete and realistic overview of your project. Your course instructor cannot sign off on your project topic without this information. Note: You must fill out and submit this form. Space beneath each number will expand as needed. Any cost associated with developing the application will be the responsibility of the student. INFORM MENTOR: Potential use of proprietary company information: (Y/N) ANALYSIS: 1. Project topic AND description: 2. Project purpose/goals: DESIGN and DEVELOPMENT: 1. Application Type (select one): · Mobile (indicate Apple or Android) · Web · Stand-Alone 2. Programming/development language(s) that you will use: 3. Operating System(s)/Platform(s) that you will use: 4. Database Management System you will use: 5. Estimated number of hours for: i. Planning and Design: ii. Development: iii. Documentation: iv. Total: 6. Projected completion date: IMPLEMENTATION and EVALUATION: 1. Describe how you will approach the execution of your project: · This project does not involve human subjects research and is exempt from WGU IRB review. STUDENT SIGNATURE __________________________________ By signing and submitting this form, you acknowledge any cost associated with development and execution of the application will be the responsibility of the student. COURSE INSTRUCTOR’S NAME: __________________________________________________________________ COURSE INSTRUCTOR APPROVAL DATE: REQUIREMENTS Your submission must be your original work. No more than a combined total of 30% of the submission and no more than a 10% match to any one individual source can be directly quoted or closely paraphrased from sources, even if cited correctly. The originality report that is provided when you submit your task can be used as a guide. You must use the rubric to direct the creation of your submission because it provides detailed criteria that will be used to evaluate your work. Each requirement below may be evaluated by more than one rubric aspect. The rubric aspect titles may contain hyperlinks to relevant portions of the course. Tasks may not be submitted as cloud links, such as links to Google Docs, Google Slides, OneDrive, etc., unless specified in the task requirements. All other submissions must be file types that are uploaded and submitted as attachments (e.g., .docx, .pdf, .ppt). A. Complete the attached "Software Development Capstone Topic Approval Form." Include a signature and date from your course instructor to indicate that this form has been approved. B. Complete the attached "Capstone Waiver" after choosing the option that applies to your capstone project and digitally signing it where applicable. C. Acknowledge sources, using in-text citations and references, for content that is quoted, paraphrased, or summarized. D. Demonstrate professional communication in the content and presentation of your submission. File Restrictions File name may contain only letters, numbers, spaces, and these symbols: ! - _ . * ' ( ) File size limit: 200 MB File types allowed: doc, docx, rtf, xls, xlsx, ppt, pptx, odt, pdf, txt, qt, mov, mpg, avi, mp3, wav, mp4, wma, flv, asf, mpeg, wmv, m4v, svg, tif, tiff, jpeg, jpg, gif, png, zip, rar, tar, 7z Requirements Task 1 INTRODUCTION This task is the design, development, and implementation of the software application that was approved by a course mentor. Your work for this task will not be evaluated until the appropriate forms from Task 1 have been submitted and evaluated. REQUIREMENTS Your submission must be your original work. No more than a combined total of 30% of the submission and no more than a 10% match to any one individual source can be directly quoted or closely paraphrased from sources, even if cited correctly. The originality report that is provided when you submit your task can be used as a guide. You must use the rubric to direct the creation of your submission because it provides detailed criteria that will be used to evaluate your work. Each requirement below may be evaluated by more than one rubric aspect. The rubric aspect titles may contain hyperlinks to relevant portions of the course. Tasks may not be submitted as cloud links, such as links to Google Docs, Google Slides, OneDrive, etc., unless specified in the task requirements. All other submissions must be file types that are uploaded and submitted as attachments (e.g., .docx, .pdf, .ppt). You must use the rubric to direct the creation of your submission because it provides detailed criteria that will be used to evaluate your work. Each requirement below may be evaluated by more than one rubric aspect. The rubric aspect titles may contain hyperlinks to relevant portions of the course. A. Write a comprehensive summary that addresses the following requirements: • the business problem or opportunity you are solving for, including a description of the customers and why this application will fulfill their needs • existing gaps in the software application you are replacing or modifying (if applicable) • the software development life cycle methodology you use to guide and support software development activities • deliverables associated with the applied software development life cycle methodology • the plan for implementation of your software solution, including the anticipated outcomes from this development • the methods for validating and verifying that the developed software application meets the requirements and subsequently the needs of the customers • the programming environments and any related costs, as well as the human resources that are necessary to execute each task in the development of the software application • a projected timeline including milestones, start and end dates, duration for each milestone, dependencies, and resources assigned to each task B. Design and develop a fully functional software application that addresses your identified business problem or organizational need. Include each of the following attributes as they are the minimum required elements for the application: • one of the following application types: mobile, web, or stand-alone application • code including inheritance, polymorphism, and encapsulation • search functionality with multiple row results and displays • a database component with the functionality to securely add, modify, and delete the data • ability to generate reports with multiple columns, multiple rows, date-time stamp, and title • exception controls • validation functionality • industry appropriate security features • design elements that make the application scalable • a user-friendly, functional GUI C. Create each of the following forms of documentation for the application you have developed: • a design document including a class diagram and design diagram • a test plan for a unit test, including screenshots • the results of the unit test based on the provided test plan, including screenshots • source code and executable file • link to where web app is hosted with HTML code (if applicable) • user guide for setting up and running the application for maintenance purposes • user guide for running the application from a user perspective D. Acknowledge sources, using in-text citations and references, for content that is quoted, paraphrased, or summarized. E. Demonstrate professional communication in the content and presentation of your submission. File Restrictions File name may contain only letters, numbers, spaces, and these symbols: ! - _ . * ' ( ) File size limit: 200 MB File types allowed: doc, docx, rtf, xls, xlsx, ppt, pptx, odt, pdf, txt, qt, mov, mpg, avi, mp3, wav, mp4, wma, flv, asf, mpeg, wmv, m4v, svg, tif, tiff, jpeg, jpg, gif, png, zip, rar, tar, 7z