Software Design Plan
docx
keyboard_arrow_up
School
Western Governors University *
*We aren’t endorsed by this school
Course
D480
Subject
Information Systems
Date
Dec 6, 2023
Type
docx
Pages
5
Uploaded by raeganmink
AEN1: Software Design
Software Design Plan
Software Design Plan
WGU Student ID
011476056
A. Business Case
1. Problem Statement
The bug in the software returns the wrong years of fiscal data when dealing with a company with more than 5 years of data. Instead of returning the data of the most recent 5 years instead the data from the first 5 years of the company is returned. 2. Business requirements
One business requirement is that the software returns the most recent years when the business is older than 5 years to create a loan profile. Another business requirement is that if younger than 5 years there will be forecast years. The existing app fails to meet these requirements because it is returning data from
the first 5 years of the companies inception as opposed to the 5 most recent years of company data. 3. In-scope action items
In order to resolve this ticket it is required that the code will be reprogrammed in order to return the correct years data. This directly meets the business requirement to return the most recent 5 years of data as opposed to what it is doing by returning the first 5 years. Another action item is to test the code to make sure that it does return the correct data in circumstances where the company is less than 5 years old. Refactoring the code may induce
changes that could effect what was working properly before. These test cases will help to ensure the forecasted years of data in the second listed business requirement are still valid.
4. Out-of-scope action items
An out of scope item that will not be addressed during this update will be updating the user interface to have separate GUIs for younger and older companies. The interface could be redesigned to make it easier to return the correct data and provide users with more information about what data is needed. This is out of scope because it does not directly deal with the problem of returning the wrong data in the
software. Another out of scope item is to update the database to store the data differently for easier access. Though storing data differently may make it easier to access the other years of the companies data, this is out of scope because it does not need to return or hold more than 5 years of data. PAGE 1
AEN1: Software Design
Software Design Plan
B. Requirements
1. Functional requirements
A functional requirement of this software is that it can determine the difference in action of what to do when dealing with a new company vs an older one. Because the newer companies require forecast data the application needs to be able to tell the difference between new and old companies. Another functional requirement of this software is knowing
the current date. The date is important in knowing what data to grab as the application should skip the current year and needs the data before. Another functional requirement is being able to generate a loan profile. Apart from collecting the proper data, the application should return a loan profile that the analysts can look at to determine if they would offer a loan. 2. Non-functional requirements
A non functional requirement of this software is that it will require an account to run. To keep
the website secure only valid customers and employees will be given account credentials. Another non functional requirement is that the application will run in less than 10 minutes. The loan profiles should not take a long time to create and should ensure the applications efficiency. Another non functional requirement is that the website should allow multiple users at once. The application should not shut down or get overloaded by multiple users or runs. C. Software Design
1. Software behavior
PAGE 2
AEN1: Software Design
Software Design Plan
A category of input is the application process. The intended response of this process is to obtain to obtain data from those who want a loan. In order to run the application a user should need a valid account created using an access token. This prevents random people from using the application and clogging the resources. An additional category of input is the financial data. This data helps to generate a solid loan profile. This data should be standardized through specific forms that are provided by the company or official documents.
All pieces of required data must be provided before submitting an application. This prevents companies from submitting false data or omitting data in order to obtain a loan. 2. Software structure
The software should be structured in an event driven architecture way. This allows the application to be run by multiple people at once. Because it is fairly a simple process involving obtaining data and returning a report it can be done simply in this way. The data of
one company doesn’t effect the run of another and they should be able to process separately at the same time. There will be related functions for creating and returning finished profiles, processing data, making calculations, and comparing to similar sized and structured companies in the same sector. There could be classes relating to each fiscal year with variables of data such as revenue, debt, size, etc.
D. Development Approach
1. Planned deliverables
A document that will be produced is the loan profile. In order to produce the profile the application will analyze the data and create several graphs and calculations to show past financial data and project future data. Software engineers will need to design these functions
to take data in and produce results. There will be a generation of a short report with all of these graphs and summaries of the incoming data. This document will be produced after running the application. Another deliverable is the application form. This form will be for the PAGE 3
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
AEN1: Software Design
Software Design Plan
customer to upload the needed data. This form will provide the data that is needed to do the
calculations and create the report. To create this, software engineers will create a webpage that has varying inputs that are required to be filled out before continuing. 2. Sequence of deliverables
The functions to do calculations and produce graphs should be done and tested first. This allows the engineers to figure out what the inputs need to be before creating the form. The report generation can be made simultaneously using sample data. Then the form to input the data can be made. After this all the deliverables can be tested together. 3. Development environment
The development environment for this project is using visual studio as an IDE. The IDE will allow the developers to write, store, and test the scripts. This makes it simple to connect all the separate entities together and to test certain scripts by themselves. For this project python will be used as a coding language as it is quick to develop in and has several packages with help for data generation and creation. An external dependency for this project
is a mySQL database that stores the data that is submitted. 4. Development Methodology
Agile will be used in order to develop this software. Agile allows multiple team members to focus on small individual pieces of the software such as specific functions or graphs in the report that need to be created can be worked on by developers. Also it allows people with different skillsets to work on things simultaneously. It also makes it very easy to add new features while things are being developed. The input form will be need to be developed after
the rest of the needs but this can still be done in Agile. Agile is a better choice than waterfall
because it does not have to be done linearly and can be developed more quickly. Rapid application development is not a good choice as it is more important to develop a great product as opposed to trying to rush it to be complete. PAGE 4
AEN1: Software Design
Software Design Plan
PAGE 5