Download Algorithms in Business Problems: A Case Study of a Coffee Shop Ordering System and more Assignments Programming Languages in PDF only on Docsity!
ASSIGNMENT 1 FRONT SHEET
Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 1: Programming Submission date 15/04/2021 Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name Há» Ngá»c KhĂĄnh Student ID GCS Class GCD0901 Assessor name HoĂ ng NhÆ° VÄ©nh Student declaration I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism. I understand that making a false declaration is a form of malpractice. Studentâs signature Khanh Grading grid P1 M1 D
ï Summative Feedback: ï Resubmission Feedback:
Grade: Assessor Signature: Date: Lecturer Signature:
- I. INTRODUCTION
- II. ALL ABOUT ALGORITHMS
- Definition of algorithms
- Algorithms in every field
- Algorithms from simple problems
- III. BUSINESS PROBLEMS
- Definition of business problems
- Step by step to solve a business problem..................................................................................
- Solve business problems by algorithms
- IV. DEMONSTRATE APPLICATION
- Code breakdown
- Code execution
- Software Development Life Cycle
- V. EVALUATE PROBLEM
- Problem application
- Test plan & test cases
- VI. CONCLUSION
- Figure 1: COMPARISON OF THE TWO DEFINITION TABLE OF FIGURES AND TABLES
- Figure 2: FLOWCHART OF CHECKING PRIME NUMBERS PROBLEM
- Figure 3: FLOWCHART OF CAFE'S BUSINESS PROBLEM
- Figure 4: LIBRARIES AND VARIABLES
- Figure 5: DECLARATION AND SCREEN DISPLAYING
- Figure 6: SWITCH...CASE CONDITION STATEMENT
- Figure 7: SCREENSHOT NO.1
- Figure 8: SCREENSHOT NO.2
- Figure 9: SCREENSHOT NO.3
- Figure 10: SOFTWARE DEVELOPMENT LIFE CYCLE
- Table 1: TEST CASES
I. INTRODUCTION In this report, I will mainly discuss about the business problems which I am definitely going to bypass in the future when I have a stable job at a company. As this report is going, I will be researching on business problems and algorithms which will be made to help solve the problem. Along with that, examples and critical thinking technique as well as problem solving methodologies will be appeared to give a hand in those problems may occur in the carrer. Furthermore, the algorithms in those business problems will be demonstrated through examples of procedural programming to comprehend more about algorithms and base on that to improve better for the upcoming programming projects. II. ALL ABOUT ALGORITHMS
1. Definition of algorithms
Algorithm is simply comprehended as a set of step to achieve a goal, which is easily confusing with the meaning of something else. The specific definition should be a set of mathematical instructions or rules that, especially if given to a computer, will help to calculate an answer to a problem or given to somebody to specifically follow the instrutions better. Besides, this method of giving detailed instructions is also a way to educate children. This definition also goes with the Procedural Programming algothms which I will mention later in the next section. The differences of the two definitions will be demonstrated below by a humble how-to-make-tea. Figure 1 : COMPARISON OF THE TWO DEFINITION
Figure 2 : FLOWCHART OF CHECKING PRIME NUMBERS PROBLEM III. BUSINESS PROBLEMS
1. Definition of business problems
Business problems are simply comprehended as realistic problems from daily life which need implementing in a product. Beside, business problems are hugely mistaken with logical coding, which is completely wrong and should be appeared in holistic view. On the other hand, with the help of algorithms, business problems are implemented in a software product which is highly difficult in logic. For instance, a large number of tech businesses face the issue of trial users falling meaning the users take trials but do not come back to become paying users. This is a business problem. As well as, the problem of taking thousands and millions of orders on mobile shipping app per day is also the one that companies fear to face if they wanted to create their own application.
2. Step by step to solve a business problem
Step 1: Challenge your assumptions: companies have one common mistake of creating problems as they think AI can solve them easily. By talking with customers and receiving feedback from them, a company can identify the best solution for specific problems, in this case, solutions mean technologies. Step 2: Consider all solution: Once having the problem, leaders and managers should view the problem in the AI perspective, which means Machine Learning and base on that to identify all solutions and technologies to go to the next step. Step 3: Find all data: When evaluating all options, a preliminary evaluation of available data should be carried out and whether there are sufficient data to train machine learning algorithms effectively. This step can go wrong if step 1 and 2 were not properly completed. From the problems and the solutions, managers and leaders should find all information around that problem and data that may help to create the solution. By successfully completing previous steps, the manager will be able to speak to the data scientist on a solid basis and ensure that the whole team works towards a solution which provides the greatest benefit to its customers. Step 4: Identify the best algorithm: Once all the data have been compiled and some pre-processing processes have been performed, supervisors can help decide the algorithm that fits the best. Managers need not know the particulars or names of algorithms, how they perform and so on. Instead, only an appropriate error level in performance and the algorithm description level are required. The value of model explanation must also be determined by leaders. Customers do not want to know if the bank picked a suspicious transaction, but it can be very important to understand why their loan application was refused by an algorithm. By learning the expectation of consumers and how they communicate with the effects of an algorithm, managers can considerably boost the consumer service, eliminating issues with non-explicable and imprecise algorithms.
3. Solve business problems by algorithms
In this section, I will be focusing on giving out one or two business problems and the best algorithms demonstrated by flowcharts. I will mainly talk about the problem of calculate the cost of one specific table in a random café. I will give out many options as the user would take their needed option. So the program will take the order and calculate on how much that table needs to pay. The café will have 5 types of coffee, which are black coffee (2$), brown coffee (2$), latte (3$), espressco (4$) and
IV. DEMONSTRATE APPLICATION
1. Code breakdown
In this section, I will break down the whole program and explain briefly on each part of the program. In the first part, I declare all the variables that I might need which include the request and the 5 variables which signify the amount of 5 types of coffee. Figure 4 : LIBRARIES AND VARIABLES Next up, I calculate the number of cups and how much they cost individually. Then the sum will be declared to sum up the cost of the whole table. Following is the screen displaying for the request. Figure 5 : DECLARATION AND SCREEN DISPLAYING
In the part, I showed the switchâŠcase condition statement which will execute at the right value. And also this part is the end of the doâŠwhile iteration statement. Figure 6 : SWITCH...CASE CONDITION STATEMENT
2. Code execution
After bringing on the code breakdown, in this section, I will show the result of every test case to see if the program functions fine or need optimizing. Figure 7 : SCREENSHOT NO.
Figure 10 : SOFTWARE DEVELOPMENT LIFE CYCLE Stage 1: Planning. This involves estimating labour and material costs, developing a schedule with target deadlines, and forming project teams and establishing a leadership framework. Stage 2: Analysis. This is considered part of planning to determine what the application is supposed to do and its requirements. Stage 3: Design. This models the operation of a software programme Among the concept elements are: architecture, user interface, platforms, programming, communications, security and prototype. Stage 4: Implementation. This is the actual program writing. A small project may be written by a single writer, while a large project may be divided and worked on by several teams. Stage 5: Testing and integration. It is important to validate an application before releasing it to consumers. Many of the testing, such as security testing, can be automated. Stage 6: Maintenance. The production cycle is nearly complete at this stage. The application has been completed and is being used in the market. Users find mistakes that were not discovered during testing during this process. These mistakes must be corrected, which can result in new production cycles.
V. EVALUATE PROBLEM
1. Problem application
To sum up everything that has been stated so far, all of the basic conditions successfully fulfilled and enforced by the problematic requires. In addition, separate test cases were required for the software to ensure that it did not work incorrectly, or that it did not yield unintended outcomes. Although several defects have occurred during the implementation phase, the software will in future be improved and upgraded. Going through the business problem, the code breakdown and the result of code execution. I think itâs time to make a deeper analysis and evaluate the problem even more. With the help of algorithms, it genuinely helps create a habit which I never think about, that constructs a solid plan of step by step solutions that can slowly make coding ideas appear. Furthermore, drawing schedules helps generate theories for challenges, like: flowcharts or user diagrams. Combined with all this, they allow me to seamlessly code the software using lightning bolt designs and ideas.. From that, the solution came out to be exactly as the definition of algorithms. Beside, the switch...case condition statement and the do...while iteration statement played great role of taking orders repeatedly. I consider that the taking orders application can be better if I have more experience of coding. In summary, the program generally fulfilled the needs of the specified business problem. All the options worked perfectly well, so no debugging was necessary. Although nothing is all right, I thought this program already has a few secret bugs, and this programme will be stronger as a result too. I know nothing very well.
2. Test plan & test cases
Everything couldnât go well if I donât have a specific test plan in order to adjust the code base on the expected result and the actual result. Also, measures of achievement are demonstrated below.
- Menu-based application: functions well, no infinite loop or error in the result.
- Result: being given out with good visual and customer-friendly
- Data type: make sure that the order variable is using the right data type which wonât cause any problem during
- Test cases: Black coffee: 2 Brown coffee: 1 Latte: 3 Espressco: 2 Cappuchino: 1
