****INSTRUCTIONs **** Need to identify ONE Case Problem that most business have

Need to identify ONE Case Problem that most business have. Then need to describe how to effectively implement/ deploy the solution to the company. Along with writing a word document NEED to provide a programming code ***PHP CODE*** that will be solution to the problem. I have below attached two EXAMPLES WITH IMAGES on what and how I need.
This second phase of the capstone project will focus on the second and third use cases which were developed in CSIS 474. This portion of the project further highlights the utility of the model, view, controller design pattern, as each use case is built using almost identical functions, which provides a clear path for the system to completion. This phase of the process also served as a time to refine and polish the existing portions of the system which were developed in the first phase of the project.
During this deployment phase of the capstone project, use cases two and three were the areas of focus. For this package tracking system, these use cases include a page which in future will only be accessible by employees. On this page will be the ability to enter new packages into the system via the front end user interface (See Appendix), which then send the information through the servlet controllers, and then finally stored in the embedded database for future use. The third use case is the ability for employees to create a user account (See Figure 2), which will in future allow them to enter a hub specific account. There has also been considerable effort during this phase to clean up existing code and patch any issues found during testing.
Project Solution
Beginning from where the first use case left off, the first step in the development of the functionality for the second use case began with the existing view web page which is used for entering new packages into the database. After making several alterations to the form fields in the JSP document to better suit the intended data model (See Figure 1), the next step of the process was to create the CreatePackageServlet (See Figure 5), which would intercept the HTTP POST request from the package creation form, assign each field to a variable and then send these variables to the PackageTableDao (See Figure 6), which houses all database functions related to the existing packages database table (See Figure 7). This class establishes connection to the database and then performs a SQL insert command using the field variables as parameters (See Figure 8). Upon the completion of the update, a message is passed from the CreatePackageServlet (See Figure 9) to the JSP web page which announces the success of the operation to the user (See Figure 10).
The process for the development of the third use case began at the view web page for the employee account creation page (See Figure 2). After editing the form fields (See Figure 4) to suit the newly developed employeeAccounts database table (See Figure 11), the form data is sent to the EmployeeAccountDao class (See Figure 12) which performs a query using the email entered by the user, to check if that entry is already in existence in the database (See Figure 13). If the email is found in the database, an error message is returned to the view, which prompts the user to try a new email or log in (See Figure 15). If the email does not exist in the database, a SQL insert statement inserts the user data into the database (See Figure 8).
Biblical Worldview
The refinement of existing processes and the adherence to a chosen framework for the development of this process falls in line with how we as Christian’s are put to a higher standard by the Lord. Many times in the Bible, God commands us to hold ourselves to a higher standard in our personal and professional lives. As Colossians 3:17 states; “And whatever you do, in word or deed, do everything in the name of the Lord Jesus, giving thanks to God the Father through him (English Standard Version, 2001, Colossians 3:17).”
UAT Results Report
In the first phase, several system tests were developed in order to gauge the usability and performance of this system. These tests included several mundane operations including inputting several types of inputs in differing rates of succession. In this testing, an issue was discovered in regards to database connection. That issue had to do with connections to the database being left open, which would cause an error when a new connection was attempted. This issue was remedied by closing all connections to the database right after use.
ASC Engineered Solutions is implementing technology using a mobile application to help increase productivity, reduce human error, and grow revenue. While use case one focused on the initial GUI and the warehouse submenu, use cases two and three focused on the accounting and sales departments. Both functions are ideal for limiting human error by calculating sales tax and finding the margin from a sale. Often, these tasks are done using pen and paper, in the employee’s head, or through a standard calculator. Creating specific functions for these tasks can help reduce errors and help improve workflow. While challenges were faced, the DevOps team was able to implement both use cases successfully and is slowly working towards a fully functional application that is usable to everyone within the company. UAT application results are compared to other mobile applications along with a development plan followed by a conclusion, references, and an appendix.
Keywords: ASC, application, use case, calculator
ASC Engineered Solutions has realized that technology is mandatory for any modern company. Even if these technological advancements seem little, they will likely produce a snowball-like effect, meaning an increase in technology will coincide with an increase in revenue. This application will eventually reach workflow functionality. However, ASC Engineered Solutions desires that the application is built slowly to ensure employees realize the importance of the program. Babak and Kozanoglu state that digital transformation is changing organizational structure due to the use of technology (Babak and Kozanoglu, 2020). A slow rollout will help ensure that ASC Engineered Solutions executives also see that technology can help improve workflow. If the application does not catch on with basic functionality, there is little to no reason to spend money on unused resources.
ASC Engineered Solutions application base layer will be built on three use cases that show how technology helps in everyday tasks. In the last use case, lead time was considered along with the GUI to create a flowing program that anyone could use. This means that most of the frontend development has been accomplished, leading to backend development to create functions that apply to a vast number of employees. To showcase this application to everyone at ASC, accountants, and the sales force will be the focus for these functions. Use cases two and three will be considered and developed during this phase of the capstone project to further expand this new application.
Use Case Number Two
Use case number two revolves around the accounting department using Pennsylvania and Texas sales tax to figure out the pricing in a wide amount of ways. Accountants factor in taxes daily for incoming and outgoing pipe fittings. The initial idea was to create text boxes for users to enter numeric numbers to find these taxes. While this seemed like the correct way to develop this use case, a simple and easier solution was found. A calculator that has buttons to automatically factor these taxes, six and six-point two five percent, to reduce the amount of error a user could cause. Accountants are confidently skilled with a standard calculator layout with likely years of expertise. Adding two new buttons that replace functions that are often unused helps speed up anyone employed at ASC. Once pivoted to a calculator-like style, it was decided to implement a full-standard calculator that can produce correct inputs from the user but also add sales tax buttons for convince.
Use Case Number Three
Use case number three focuses on the sales force, which often deals with a vast number of questions regarding satisfactory margin gain and loss. Some other companies purchase through several vendors to guarantee the lowest-priced item and to keep their margins high. Having a set bare minimum margin for acceptable pricing can help the sales team negotiate with clients. Currently, this is being done either through quick calculations in an employee’s head or through pen and paper. Human error occurs regularly and creates sales that are razor-thin or that can lose money for ASC. While humans are error-prone, technology is error resistant and can produce correct outputs every time. Users will be able to type into the application two numbers and receive the correct information within seconds, reducing errors and speeding up the process.
Project Solution
Splitting the project solution into two sections, the tax calculator is created in a visual and logical format. All buttons allow the user to interact by pressing onscreen to produce a number in the EditText field. All twenty buttons are restricted within their constraint layout for ease of scalability. This means that regardless of the user’s screen, all information will fit within it. The constraint layout is constrained to the edge of a screen, while all buttons are constrained to the edge of another button or the constraint layout. This all means that scalability can happen effortlessly without the user noticing. A design restriction put onto this XML layout is to ensure that rotation does not occur through android:screenOrientation=”portrait” in the XML manifest to mimic the feel of a true calculator.
In the backend, the calculator has multiple different functions that actively listen for input. Each button the user interacts with activates a function to add a single number to the update function. This update function is reflected through TextView each time a button is pressed. Before calculations, both the × and ÷ are replaced with * and / to successfully evaluate the equation. When the equals button is pressed, it calls the import method org.mariuszgromada.math.mxparser to calculate the results The update function is then called once again to update the TextView with the solution. It should be mentioned that the TextView box only allows numeric numbers to reduce any errors in the application.
Use case three’s solution is like use case one with slight changes. Information is typed into the two EditText boxes that will only accept numeric values. If one, or both, of the boxes, are not correctly filled a toast message will appear to the user letting them know that a user error has occurred. Once both boxes are correctly filled out, the calculate button will take this information to the backend of the application. These numeric numbers will be converted to strings through the getString and toString methods. Then the strings will go through parseInt and be converted to integers that are ready to be evaluated. To find the profit margin, the program takes the profit divided by the revenue and then times it by one hundred. After the calculation to complete, the integer is converted to a string and sent to the user’s TextView box right above the calculate button.
Challenges Faced
Use cases two and three were far easier compared to the first use case. The scope and understanding of this project are better known compared to two weeks ago. By far the biggest challenge of this phase was setting up the calculator GUI. As Android Studio is new to the DevOps team, constraints are hard to work with and very unforgiving. One small misclick can send all the previous buttons into an abyss. Thankfully the undo button exists, as dozens of undo clicks occurred during the hours creating this GUI. After constructing all the buttons, labeling became another headache to deal with. The DevOps team, myself, did not realize how many functions are taken for granted and never thought about them from a developer’s perspective. After all the buttons were placed and labeled, understanding mariuszgromada.math.mxparser created another hardship. Overall, the calculator has been by far the biggest challenge compared to the other two use cases.
Biblical Worldview
During this phase of the capstone, simplicity was key in performing these tasks. Matthew 19:24 states “Again I tell you, it is easier for a camel to go through the eye of a needle than for a rich person to enter the kingdom of God” (ESV). Complicated processes are like threading a camel through an eye of a needle. Often a small step is forgotten, and the entire process is ruined as if threading a needle. A simpler option is available for most things, just as believing Jesus to be one’s, own personal savior. The idea, of trusting God with all your heart and soul, is often seen as a confusing idea for many unbelievers. Matthew 18:4 states “Whoever humbles himself like this child is the greatest in the kingdom of heaven” (ESV). It is truly a simple process and shows that simplicity is key. Like an onion, there are many layers to both Christianity and application development, but simplicity is key for both new users. Explaining Christianity or a program’s function in depth can lead potential new users astray or worse. It is vital that users understand how a process works, but not be overwhelmed with options when they first begin.
User Acceptance Testing (UAT) Results
During the UAT report a wide range of users interacted with the ASC application. These tests asked users to move throughout the application and interact with all functions developed so far. One issue that some users had while testing the application was that the main menu buttons and font were too small. The DevOps team has increased these buttons using the android:textSize=”28sp” so that users can read all buttons across the application. One other major requirement that must function is the application itself. Su states that all android applications should ensure that fail-stop crashes be eliminated to maintain a competitive edge (Su et al., 2022). No crashes have occurred after implementing these two new use cases.
Benchmarks are a way of viewing a new application and comparing it to other applications that follow industry standards. The focus of the ASC applications is on using electronic devices to perform daily tasks in a time-effective manner. All applications should have a clear use with a defined user base along with error handling and the ability to run on a wide number of devices.
Take for example the mobile application Slack, which helps employees interact with others quickly and effortlessly. The application has a clear user base, can handle user errors, and runs on almost any device. While the ASC application is not in any way near the level of impressiveness compared to Slack, it gives a good benchmark for comparison’s sake. ASCs application has a clear purpose along with a defined user base, can handle user error, and works regardless of the android device being used.
Deployment Plan and Report
For an application to be fully deployed, a list of questions must be created to answer basic questions that coincide with the work breakdown structure. First, three phases will help create a structure for each task and ensure that the progress of development is on track. A report in Excel is also used to show what tasks have been completed that parallel the WBS to ensure that users are happy with the finished product. Included in the system design life cycle is the deployment phase which helps ensure that the application, or product, is ready for all users. Sugiandi and Kerlooza state that SDLC “is a framework that provides structured sequential processes in the development of information systems” (Sugiandi & Kerlooza, 2018). Without creating and following a deployment and report plan, the ASC’s application would have no guidance for a complete product.
The ASC application is moving along quickly and becoming better well-defined and usable through each use case. Use cases two and three have been completed and tested to help both the accounting and sales departments. These functions will help both departments in daily tasks that will help improve their workflow. Not only will these functions help speed up the process, but they will also create a more accurate output consistently. Both functions were viewed in detail to show that over six hours of work have been completed for each use case. While the layout of buttons posed a challenge for the DevOps team, the calculator has turned out to look and digitally feel like its physical counterpart. This was all done to help simplify the process and compared it to the simplicity of the Christian faith. Even though both are simple at face value, there are layers and layers of complex ideas and logical reasoning for both. UAT results and benchmarks were considered along with a development plan. The ASC application is steadily improving with each new function to create a worthwhile experience for all employees at ASC Engineered Solutions