• A. Business Case:

• Problem statement:

Endothon Finance needs to launch a new web app to streamline the loan application process for small businesses. The web app should collect financial data for the previous five years of the business, excluding the current year. If a business is less than five years old, the web app should collect the most current years of financial data and a forecast for the remaining years.

Loan profiles created by the current web app are being returned with the first five fiscal years of financial data as opposed to the five most recent years. For example, if a business was established in 2000 and the current year was 2023, then the web app is incorrectly requesting historical financial data from 2000, 2001, 2002, 2003, and 2004.

• Business requirements: a. The web app should collect the correct financial data for each business, based on its age and industry.

b. The web app should provide a streamlined loan application process customized to each business.

c. The current web app fails to collect financial data for each business based on the requirement.For example, if a business was established in 2000 and the current year was 2023, then the web app is incorrectly requesting historical financial data from 2000, 2001, 2002, 2003, and 2004.

• In-scope action items: a. Develop logic for the web app to collect the correct financial data for each business based on its age and industry. b. Customize the loan application process for each business based on its details and financial data.
• Out-of-scope action items: a. Developing a machine learning algorithm to predict a business's creditworthiness based on its financial data, as it is not currently a requirement. b. Integrating with third-party accounting software, as it is not part of the current project scope.
• B. Requirements:
• Functional requirements: a. The web app should collect financial data for the previous five years of the business, excluding the current year. b. The web app should collect the most current years of financial data and a forecast for the remaining years for businesses less than five years old.
• Non-functional requirements: a. The web app should be easy to use and navigate for businesses of different industries and ages. b. The web app should be secure to protect sensitive financial data.
• C. Software Design:
• Software behavior: a. Business details, including age, industry, and the number of employees. Intended web app response: Determine the financial data collection requirements for the business and customize the loan application process accordingly.

• Software Structure:
• Associated constraints:None b. Financial data for the previous five years, excluding the current year. Intended web app response: Collect and store the financial data for each business. Associated constraints:None The intended design approach will segment the development and functionality of the web app elements into functions and classes to ensure modularity and ease of maintenance.
• D. Development Approach:
• Planned deliverables: a. User interface for the web app Steps: Conduct user research, create wireframes and mockups, design UI elements, and implement the UI using HTML/CSS. b. Backend logic for financial data collection and loan application customization Steps: Develop algorithms to determine financial data collection requirements and customize loan applications, and implement the backend logic using a programming language like Python. The planned sequence of deliverables will start with the UI design and implementation, followed by the backend logic implementation. This sequence is justified as it allows for user testing and feedback on the UI design before the backend logic is implemented.
• Development environment elements: a. Python programming language for the backend logic implementation. b. HTML/CSS for the UI design and implementation. c. MySQL database to store financial data. Expected software development approach: Agile methodology will be used to ensure flexibility and adaptability to changing requirements. This methodology was chosen over the waterfall methodology to allow for continuous feedback and iteration during development.
• E. Sources:None used.
• F. Professional communication:The response is written clearly and concisely with proper grammar and punctuation.

C2. SOFTWARE STRUCTURE Approaching Competence EVALUATOR COMMENTS: ATTEMPT 1 Approaching Competence The submission uses the "Software Design Plan" to outline the intended design approach, but the outline does not address how the intended design approach The submission states that the intended design approach will "segment the development and will segment the development and functionality of the web app elements regarding the functionality of the web app elements into functions and classes to ensure modularity and ease of proposed software structure of the web app. maintenance." However, an outline of how the intended design approach will segment the development and functionality of the web app elements is not apparent. D1. PLANNED DELIVERABLES Competent D2. SEQUENCE OF DELIVERABLES Competent EVALUATOR COMMENTS: ATTEMPT 1 Competent The submission uses the "Software Design Plan" to define a logical sequence of implementation for the deliverables in part D1 and justify the planned sequence of deliverables. The submission adequately defines a logical sequence of implementation for the deliverables. D3. DEVELOPMENT ENVIRONMENT Competent D4. DEVELOPMENT METHODOLOGY Approaching Competence EVALUATOR COMMENTS: ATTEMPT 1 Approaching Competence The submission uses the "Software Design Plan" to identify the expected software development approach to be used but does not explain each of the 2 given The submission identifies the software development approach that will be used, namely the Agile points. methodology. However, an explanation of how the chosen methodology informed the development planning process, including the sequence of deliverables outlined in part D2, is not observed