My Summer Internship Experience: Gaining Knowledge and Skills internshipReferencesIntroductionSo first of all let me give you a summary of the experience job description given to me by SAP, in my opinion the first half of the job description given by SAP is slightly vague and there are a lot of buzzwords in the description, obviously used to grab the reader's attention. The main responsibility of the SAP CoE (Center of Expertise) is to provide customers with the necessary support and assistance to help them run their business better, this would involve assisting them with any issues regarding software purchased from SAP, e.g. example, issues with SAP Analytics Cloud (SAC). During my summer internship, I will play a supportive and participating role in the team's success. By working here, I will be able to take advantage of the different employees here who would be considered experts/more experienced in the areas that interest me. Plus, unlike some other internships, this one offers a salary. as well as free lunch/dinner every day. Depending on the team I am placed on, I would have the opportunity to gain valuable experience in several areas, including:Say no to plagiarism. Get Custom Essay on “Why Violent Video Games Should Not Be Banned”?Get Original EssayS/4HANA – Enables Businesses to Implement Digitally Using Enterprise Resource Planning (ERP) Software.Internet objects - Using SAP software, I will be able to learn how SAP faces the digital world and how they connect sensors, devices and businesses. SAP HANA – An in-memory platform that helps customers organize their information in real time. Above I have summarized/paraphrased the job description given to me by SAP. Now I will give you my description of what my internship entailed. So, first of all, my official job title is CoE Support Engineer on the Analytics team. As a member of the Analytics team, I would be expected to use various software including SAP Analytics Cloud and S/4HANA as well as participate in any required/optional training/workshops that would deepen my knowledge of SAP software. In addition to this, I attended meetings of different kinds, the majority were focused on SAP Analytics Cloud. Any questions or requests I have I should report to my mentor (who changed throughout the internship) or my manager. The goal of my internship within the Analytics team was set by my manager, he wanted the other intern and myself to be as close as possible to the SAP Analytics Cloud experts within six months. He wanted us to be the people you could go to if you needed any level of help with SAP Analytics Cloud and, reflecting on the internship, that was really the goal. Description of the internship company What is SAP? SAP (Systems, Applications and Products) is a multinational company based in Germany that focuses on ERP (Enterprise Resource Planning) software. Simply put, SAP helps other businesses run their own businesses more efficiently, smoother and simpler, which means businesses will save money. To give an idea of what SAP is all about, I'm going to outline some of the awards SAP won in 2018. Awards won include: “BCG listed SAP as one of the most innovative companies of 2018! » SAP wasrecognized by CV Magazine as “Best Enterprise Software Company for 2018” “SAP has been named one of the most trusted companies in the world by Forbes 2018!” Mentioned above, this is a taste of the many awards SAP won in 2018. Before my internship, it gave me the impression that SAP would be an exciting, dynamic and friendly place to work and I didn't like it. I was certainly not wrong. Who is SAP? “In 1972, five IBM engineers in the AI department in Germany had a vision of the technology's commercial potential. Starting with one customer and a handful of employees, SAP set out on a path that would not only transform the world of information technology, but also forever change the way businesses do business. These five entrepreneurs were: Dietmar Hopp, Klaus Tschira, Hans-Werner Hector, Hasso Plattner and Claus Wellenreuther. SAP had a simple vision, which was to provide "standard application software for real-time data" and this vision must have come true because even at the end of their first year, "SAP employs nine people and generates 620,000 DM (Deutsche Mark) in revenue.” To have generated 620,000 in turnover with 14 employees in total is very impressive. Currently, SAP is stronger than ever and continues to grow. From introducing new products like S/4HANA in 2015 and SAP Leonardo in 2017 to using their status and resources to make the world a better place, examples: In 2016, “SAP was the first multinational technology company to receive the global economic dividends for Gender Equality Certificate" and in 2017, "SAP has committed to becoming carbon neutral in its operations by 2025", it is inspiring to see a company like SAP trying to make a difference in society and fight against climate change. SAP? SAP has more than “218 offices worldwide,” including Germany, Ireland, the United States, China and India. Let's talk about what SAP sells as a product. SAP sells ERP. I explained what ERPs are and what they do earlier, but I want to give a specific example, SAC (SAP Analytic Cloud), the main software I have worked with. SAC is “a simple cloud solution…. Machine learning and built-in artificial intelligence help you uncover deep insights, simplify access to critical information, and enable informed decision-making. SAP Analytic Cloud is made up of three main pillars: Business Intelligence, Augmented Analytics and Planning. In the next section, I'll talk more about my work with SAC and other software I used during my internship.Summary of my summer internshipOverall, I feel like I accomplished a lot during my internship. The way I'm going to show you is first by outlining the different missions that I was given, then the secondary tasks that I was given, I'll discuss them then. The first official assignment I was given was based on SAC and the title. One of the tasks was to design/develop a document that would show any employee interested in the subject matter how to import a live connection from SAP BW (Business Warehouse) to SAC. This was a group project assigned to Sean and I (Sean being the other intern who joined the team), by our mentor Michelle. As I worked on a few group projects in college and did teamwork at my part-time job I had in 2018, I was confident that I would be able to work well with him. So this task involved sharing the work between us and of course completing the tasks that we had both assigned to each other. I have been researching and experimenting with SAC by watchingvideos about data connections in SAC or just playing with the software myself. Eventually, I found several tutorials created by SAP that show you how to set up a live or import connection step by step. So we were finally able to complete the task and then we had to write a document demonstrating step by step how to create a live connection, we included screenshots to make it easier to follow. The second official mission was given to Sean and I, once again, by our mentor Michelle. The task was to design a PowerPoint presentation based on administration in SAC. During a certain period of my internship, my team held enablement sessions every Friday, where a team member would take an aspect of SAC and create a presentation about it to show the rest of the team . We decided to divide the work and so I had to create slides on: the content library, the SAC mobile app, best practices for performance and general administration in SAC. So, most of this mission was all about research and very little experimentation. For the Content Library and General Administration, I was able to access it on the SAC platform. The Content Library contains end-to-end business scenarios that customers and employees can use, while the General Administration tab contained general settings about the software that could be changed, for example: System configuration, notifications and Appearance were all tabs in the General Administration section. . Once we both completed our assigned work, we had to cooperate to create a complete PowerPoint presentation containing both of our slides. Later that week we both presented in front of the entire team and overall it was a great success. The third official assignment was given to Sean and I by the Analytics team leader and it involved us in researching and experimenting with time series forecasting. . Time series forecasting is a predictive scenario where you predict future values of your data, based on previous values. So, to start, I mainly researched what a time series forecast was. I wanted to understand the subject before experiencing it. On SAC there is a feature that allows you to create time series forecasts and this is where I did most of my research. To begin, you need to create a set of input data on which to base all your predictions. Once this is created, you need to decide which variable you want to make predictions for. There are other additional features that you can also modify. Once this is done, you need to train the model as a practical run to see if you are happy with the values, and then you can output the result as a new dataset. I found this particularly interesting because I find machine learning to be challenging and I see it as something that will be huge in the future. The fourth official mission was given to me by the manager of all CoE interns, David. He wanted the groups of trainees to demonstrate everything they had learned by giving a short presentation to himself, another member of management and the other trainees in the group. So, this may seem simple, but I found it to be a lot of pressure since I was the only one in this group representing the Analytics team and their product, SAC. So, to prepare for this, I spentreviewed everything I had learned about SAC up to that point, such as models, stories, data connections, administration in SAC, and time series forecasting. I managed to make the presentation successfully, but I made a few mistakes with the software and along the way I made the presentation, but I learned from those mistakes. Overall, David was satisfied with my presentation. So most of the time I had to go find my own work to do and the following is an example of one of those occasions. The fifth official mission was given to me by my mentor Michelle. She was currently creating a PowerPoint demo that she would offer to customers experiencing difficulty with certain SAC features. She wanted me to research and play with the functionality of the analytics apps as well as the Smart Predict functionality that can be found on SAC. Analytics apps are a feature that allows you to create and display your data like graphs and tables, but they also allow you to add additional functionality, such as adding a button to a graph that brings up a pop-up of the chart in detail, all in one. place. Smart Predict can predict future values, events or trends, not just numerical values as in time series forecasting. The sixth and my favorite mission is the one I voluntarily applied for. The CoE intern manager, David, sent an email to each intern regarding opportunities to participate in a project (one of many) that required certain members. The one I applied for needed: two Business Analysts, a SCRUM Master, four Developers and a Developer Lead. I applied and got the job as one of the business analysts. So overall, the project required a lot of meetings, whether team meetings or, for me, meetings between Business Analysts. One of the big tasks that the other business analyst and I had to accomplish was determining what core features were prioritized, what features needed to be included. Since we had received the basic functionality beforehand, this was quite easy to do. With these basic features, we had to translate them from words into use case diagrams. The module I took at college was extremely useful as I had learned this method as part of the module. We first made these use case diagrams on a whiteboard, but after discussion with the developers, we translated them into wireframes. To create the wireframe prototypes, we used a publicly available web application called “Build”. We continued to repeat the process of meeting with developers to receive feedback not only on our prototypes, but also on any updates or changes they wanted to make to the project design. At the end of the project we presented it in front of David and Paul (CoE Ireland Manager) and both were very impressed with our efforts. I will now discuss the secondary tasks that I completed during my internship. First, I completed several mandatory and optional online training courses like “How to Manage Conflict in the Workplace.” I attended classroom training courses like SAPTEC and HANA, which taught me general knowledge about SAP and some details about their products. I attended events organized by the intern committee, such as going to the Conrad Hotel to attend an all-day national intern meeting which included games, a panel of senior SAP members, variouslectures on interesting topics and a dinner. Another event that I was particularly interested in was the 3D printing workshop, as I have always wanted to see a 3D printer and the 3D printing process. I attended several presentations by people on my team on certain SAC features which deepened my knowledge of SAC. Some topics in these sessions included discussing the Digital Boardroom functionality available on SAC as well as general tips and tricks for working with SAC or even just how to get started with the software. Looking back, I feel like I accomplished a lot during my internship. If I were to repeat the whole experience, I feel like I would do my best to acquire more practical work and less theory-focused work. Since doing the internship I have discovered an interest in software testing, so I would have liked more work centered around that and perhaps more projects based on that earlier in the internship.Summary knowledge acquired during my internshipI will divide this into two sections: Technical Knowledge Acquired and “Soft Skills” Acquired. Technical Knowledge I wasn't sure what type of technology I would be able to use. I had imagined myself sitting at a desk, writing code from nine to five, but that wasn't the case. Instead, most of the knowledge acquired was gained by experimenting and completing assignments on various SAP products (mainly SAC), participating in the various mandatory and optional training courses like SAPTEC and HANA and taking on the role of a business analyst in the major project in which I participated. I want to start by talking about the knowledge gained from the work I've done as a business analyst. First of all, I learned the true meaning of what a Business Analyst is and the tasks that would be involved in this role. A Business Analyst acts as a mediator between the company and the software. It's their job to provide quality assurance, testing, user interface design and use cases. It's their job to tell developers what to build and what to prioritize. The first task we did was to create use case diagrams. I had made them in college, but seeing them used for their intended purpose in the workplace was fascinating to see. The other business analyst also knew about use case Diagrams but his icon for each use case was slightly different which was peculiar to see. The first piece of technology we used to create prototype versions of the use case diagrams was “Build”. Until then, construction was something, I had never been used to doing everything that was done, it was a completely new experience. The software reminded me a lot of the wireframing tool I used in second year called “Balsamiq Mockups 3”. However, in Build, because SAP had some form of relationship with Build, we had access to wireframes based on wireframes. software used by SAP and therefore, creating use case diagrams was much easier for us and allowed us to visualize our idea in a more meaningful way. The main thing I learned from this was how the use case diagram I learned in college was translated into a real-world situation. The whole process was really eye-opening and I really enjoyed it and made me think about being a business analyst as a possible future career. I want to talk about the knowledge I have gained from the work I have done onthe SAC platform. This is the main software I used during the internship. I first want to talk about stories and patterns in SAC. A story allows you to visualize your data in tables, graphs, charts, and other elements to demonstrate your business purpose. A template can be based on several things: a story you previously created, a file on your computer, or it can just be a completely blank template. A template is like a story but allows you to add additional functionality (it's more flexible than a story). The predicative scenarios on the SAC platform were probably the feature that interested me the most. Predictive scenarios will receive data about a system or object and, with the data it contains (historical and current data), create hypotheses around it. There are three types available on the SAC platform: time series forecasting, classification and regression. I have already explained time series forecasting. Classification involves predicting membership in categories and regression involves predicting numerical values based on fluctuations in correlated variables. Next comes planning in SAC. Planning in SAC involves a template that you can modify at will, by adding or changing percentages or numbers in the cells, the software will automatically adapt/update anything affected by these numbers. Finally, Analytic Applications is very similar to “Build” and Balsamiq Mockups 3, but it gives you a blank canvas on the SAC platform where you can import your stories and models and add additional functionality to them. For example, you can drag and drop objects like buttons and text fields and add them to your story. In addition to the two topics I talked about above, I gained a lot of knowledge from several other minor things. The face-to-face training at the beginning where I discovered HANA (In-memory, relational database), SAPTEC (Basic principles of certain SAP products) and ABAP (Programming language created by SAP), were full of knowledge and information to learn. Another major source of knowledge was the Power Hour sessions. Power Hour sessions were typically global virtual presentations that anyone from SAP could participate in. The sessions would be led by a person who would spend the next hour explaining a certain topic. For example, some topics included: cyber psychology, technical interview workshop, sessions on new companies joining SAP. My favorite was the Machine Learning Power Hour for several reasons, it was relevant, it's something I'm personally interested in and it would prepare me for fourth grade because there is a module on Machine Learning. I have to say that the technical aspect of the knowledge I acquired was very specific to SAP. I have mainly used SAP software, which means that to take full advantage of the experience and knowledge gained, it would be ideal for me to work at SAP, as many companies do not use SAP software at all. However, I feel some aspects of the technical knowledge gained may be transferable, such as the work I did as a business analyst which included extensive experience in testing and creating use case diagrams. I now have a good amount of experience creating charts, graphs and other visual aids as well as light experience with predictive technologies. I hope that all these experiences combined will help me in some way during the coursefrom fourth grade and beyond.Soft Skills LearnedThe first major soft skill I learned and improved was my teamwork skills. For most of the internship, I worked within a group, whether it was working on an assignment with a fellow intern on my team, or working with a group of interns from different teams on a project or work as a complete team. employees on time. Looking back on my internship, I only had one assignment, which gave me a great opportunity to improve and refine my teamwork skills. Teamwork skills include several other different skills such as: communication skills, cooperation skills, and patience. I will be able to review each one and give examples of how I used these skills and improved them. Communication in the workplace is extremely important. I used it every day during my internship. I think communication was very important throughout my internship because it allowed me to work well with others and be productive with others. Cooperation in the workplace is equally important. Throughout my internship, I observed and experienced many benefits of cooperation with my colleagues. Because everyone is working together toward the same goal, the task at hand is accomplished more quickly. Additionally, because it usually involves working with more than one person, tasks are distributed within the group, so employees (including managers) have more time to complete their own tasks and spend less time managing conflicts due to unclear communication. I think patience is a quality that I probably wouldn't have thought about before the internship. I think this is one of the most important qualities you should have if you work in a team. Patience allows you to think before acting, especially in intense situations. Patience also creates a more helpful and kinder work environment. Instead of lashing out at someone for something they did wrong, thus leading to hostility between employees, patience allows you to step back and address the situation and perhaps, instead of lashing out, give constructive criticism. This is something I have witnessed many times in my workplace, especially in terms of the patience of full-time employees with interns. There were several occasions where I was constantly struggling trying to complete an assignment given to me by my manager and each time he was more than happy to help me and direct me to online resources as well as pointing out my mistakes and reinforcing, which I should do instead. Overall, I'm very passionate about being patient when working with others, and working at SAP has reinforced this thought. One important thing I learned regarding teamwork skills is that not everyone is a team player, so not everyone wants to communicate and cooperate with each other. others and be patient with each other. Some members of my team would try to make you believe that they wanted to cooperate with you on a project, but you would soon realize it was all in their minds. What I'm talking about now is something I didn't experience during the group project last semester but something I've experienced since I came here, only with specific people and I have the feel like this is something vital that I learned about people in general and it made me realize that I was toowelcoming and indulgent. This is the reality of the workplace, you are bound to encounter people who try to manipulate either the team or certain employees into believing that they are the reason the work is done or that they know everything. I have seen that these people also tend to be very jealous of others, especially if they are not involved in the work you are doing. I think overall this is an important aspect to highlight when it comes to teamwork because I feel like there isn't enough awareness of it, which is why these people tend to get away with it. I learned and improved my general sense of responsibility. Honestly, before embarking on the internship, I never thought that responsibility would be one of the things I would learn. I have had responsibilities in the past, with my small part-time job and being part of the group project last semester, but during this internship, I feel like I understand the true meaning of responsibility. Throughout the internship, I was given several responsibilities in the form of projects ranging from mildly challenging to difficult. Here are some examples: My very first assignment, looking back, was a very small and minor assignment, but it still came with an incredible amount of responsibility. The document I was going to write would have to be one hundred percent accurate to be useful. The document was a step-by-step guide to establishing a live connection on SAC that would be used by employees and customers who use SAC and so it was a lot of pressure. The way I handled responsibilities throughout the internship changed at first. At first, I was incredibly nervous and anxious about my colleagues giving me assignments because I was afraid I wouldn't be able to complete them. . Also, at first I thought that since this was my mission, I should try to get as little help as possible. Compare this time to the end of the internship, where I can't wait to work on new missions. If I run into problems now, I know I can count on my colleagues to help me however they can. My view of responsibility has evolved over the past six months and I am sure it will be of great help when it comes to fourth year and final year project responsibility. Reflecting on my training during 'an internshipSome principles of computer science Science was reflected by my placement, including: Keep in mind: this is just a sample. Get a personalized article from our expert writers now. Get a custom essay Complexity: Determines the speed of a process and places that speed into a classification (e.g. O(1), O(n), O(log(n))). SAP delivers software products to customers, who must fulfill their purpose quickly and accurately while sacrificing as little as possible. Customers work with SAC and therefore it must be simple, easy to use and fast. However, sometimes, when creating a model, for example, the software crashed or the loading times from one screen to another were long. It was interesting to see how SAP tried to solve these kinds of problems by providing communication and support directly to the customer via Skype, the computer or sometimes in person, as well as providing updates on their software. Modeling: Whether it's an idea about how to approach a problem that you can visualize in your head or an idea that you can project onto paper, modeling involves thinking about the concept of the problem. This was reflected in a few different ways: Working with SAC, which required me to take requirements in words and translate them into a literal model (like a/

Essay / My Summer Internship Experience: Gaining Knowledge and Skills internshipReferencesIntroductionSo first of all let me give you a summary of the experience job description given to me by SAP, in my opinion the first half of the job description given by SAP is slightly vague and there are a lot of buzzwords in the description, obviously used to grab the reader's attention. The main responsibility of the SAP CoE (Center of Expertise) is to provide customers with the necessary support and assistance to help them run their business better, this would involve assisting them with any issues regarding software purchased from SAP, e.g. example, issues with SAP Analytics Cloud (SAC). During my summer internship, I will play a supportive and participating role in the team's success. By working here, I will be able to take advantage of the different employees here who would be considered experts/more experienced in the areas that interest me. Plus, unlike some other internships, this one offers a salary. as well as free lunch/dinner every day. Depending on the team I am placed on, I would have the opportunity to gain valuable experience in several areas, including:Say no to plagiarism. Get Custom Essay on “Why Violent Video Games Should Not Be Banned”?Get Original EssayS/4HANA – Enables Businesses to Implement Digitally Using Enterprise Resource Planning (ERP) Software.Internet objects - Using SAP software, I will be able to learn how SAP faces the digital world and how they connect sensors, devices and businesses. SAP HANA – An in-memory platform that helps customers organize their information in real time. Above I have summarized/paraphrased the job description given to me by SAP. Now I will give you my description of what my internship entailed. So, first of all, my official job title is CoE Support Engineer on the Analytics team. As a member of the Analytics team, I would be expected to use various software including SAP Analytics Cloud and S/4HANA as well as participate in any required/optional training/workshops that would deepen my knowledge of SAP software. In addition to this, I attended meetings of different kinds, the majority were focused on SAP Analytics Cloud. Any questions or requests I have I should report to my mentor (who changed throughout the internship) or my manager. The goal of my internship within the Analytics team was set by my manager, he wanted the other intern and myself to be as close as possible to the SAP Analytics Cloud experts within six months. He wanted us to be the people you could go to if you needed any level of help with SAP Analytics Cloud and, reflecting on the internship, that was really the goal. Description of the internship company What is SAP? SAP (Systems, Applications and Products) is a multinational company based in Germany that focuses on ERP (Enterprise Resource Planning) software. Simply put, SAP helps other businesses run their own businesses more efficiently, smoother and simpler, which means businesses will save money. To give an idea of what SAP is all about, I'm going to outline some of the awards SAP won in 2018. Awards won include: “BCG listed SAP as one of the most innovative companies of 2018! » SAP wasrecognized by CV Magazine as “Best Enterprise Software Company for 2018” “SAP has been named one of the most trusted companies in the world by Forbes 2018!” Mentioned above, this is a taste of the many awards SAP won in 2018. Before my internship, it gave me the impression that SAP would be an exciting, dynamic and friendly place to work and I didn't like it. I was certainly not wrong. Who is SAP? “In 1972, five IBM engineers in the AI department in Germany had a vision of the technology's commercial potential. Starting with one customer and a handful of employees, SAP set out on a path that would not only transform the world of information technology, but also forever change the way businesses do business. These five entrepreneurs were: Dietmar Hopp, Klaus Tschira, Hans-Werner Hector, Hasso Plattner and Claus Wellenreuther. SAP had a simple vision, which was to provide "standard application software for real-time data" and this vision must have come true because even at the end of their first year, "SAP employs nine people and generates 620,000 DM (Deutsche Mark) in revenue.” To have generated 620,000 in turnover with 14 employees in total is very impressive. Currently, SAP is stronger than ever and continues to grow. From introducing new products like S/4HANA in 2015 and SAP Leonardo in 2017 to using their status and resources to make the world a better place, examples: In 2016, “SAP was the first multinational technology company to receive the global economic dividends for Gender Equality Certificate" and in 2017, "SAP has committed to becoming carbon neutral in its operations by 2025", it is inspiring to see a company like SAP trying to make a difference in society and fight against climate change. SAP? SAP has more than “218 offices worldwide,” including Germany, Ireland, the United States, China and India. Let's talk about what SAP sells as a product. SAP sells ERP. I explained what ERPs are and what they do earlier, but I want to give a specific example, SAC (SAP Analytic Cloud), the main software I have worked with. SAC is “a simple cloud solution…. Machine learning and built-in artificial intelligence help you uncover deep insights, simplify access to critical information, and enable informed decision-making. SAP Analytic Cloud is made up of three main pillars: Business Intelligence, Augmented Analytics and Planning. In the next section, I'll talk more about my work with SAC and other software I used during my internship.Summary of my summer internshipOverall, I feel like I accomplished a lot during my internship. The way I'm going to show you is first by outlining the different missions that I was given, then the secondary tasks that I was given, I'll discuss them then. The first official assignment I was given was based on SAC and the title. One of the tasks was to design/develop a document that would show any employee interested in the subject matter how to import a live connection from SAP BW (Business Warehouse) to SAC. This was a group project assigned to Sean and I (Sean being the other intern who joined the team), by our mentor Michelle. As I worked on a few group projects in college and did teamwork at my part-time job I had in 2018, I was confident that I would be able to work well with him. So this task involved sharing the work between us and of course completing the tasks that we had both assigned to each other. I have been researching and experimenting with SAC by watchingvideos about data connections in SAC or just playing with the software myself. Eventually, I found several tutorials created by SAP that show you how to set up a live or import connection step by step. So we were finally able to complete the task and then we had to write a document demonstrating step by step how to create a live connection, we included screenshots to make it easier to follow. The second official mission was given to Sean and I, once again, by our mentor Michelle. The task was to design a PowerPoint presentation based on administration in SAC. During a certain period of my internship, my team held enablement sessions every Friday, where a team member would take an aspect of SAC and create a presentation about it to show the rest of the team . We decided to divide the work and so I had to create slides on: the content library, the SAC mobile app, best practices for performance and general administration in SAC. So, most of this mission was all about research and very little experimentation. For the Content Library and General Administration, I was able to access it on the SAC platform. The Content Library contains end-to-end business scenarios that customers and employees can use, while the General Administration tab contained general settings about the software that could be changed, for example: System configuration, notifications and Appearance were all tabs in the General Administration section. . Once we both completed our assigned work, we had to cooperate to create a complete PowerPoint presentation containing both of our slides. Later that week we both presented in front of the entire team and overall it was a great success. The third official assignment was given to Sean and I by the Analytics team leader and it involved us in researching and experimenting with time series forecasting. . Time series forecasting is a predictive scenario where you predict future values of your data, based on previous values. So, to start, I mainly researched what a time series forecast was. I wanted to understand the subject before experiencing it. On SAC there is a feature that allows you to create time series forecasts and this is where I did most of my research. To begin, you need to create a set of input data on which to base all your predictions. Once this is created, you need to decide which variable you want to make predictions for. There are other additional features that you can also modify. Once this is done, you need to train the model as a practical run to see if you are happy with the values, and then you can output the result as a new dataset. I found this particularly interesting because I find machine learning to be challenging and I see it as something that will be huge in the future. The fourth official mission was given to me by the manager of all CoE interns, David. He wanted the groups of trainees to demonstrate everything they had learned by giving a short presentation to himself, another member of management and the other trainees in the group. So, this may seem simple, but I found it to be a lot of pressure since I was the only one in this group representing the Analytics team and their product, SAC. So, to prepare for this, I spentreviewed everything I had learned about SAC up to that point, such as models, stories, data connections, administration in SAC, and time series forecasting. I managed to make the presentation successfully, but I made a few mistakes with the software and along the way I made the presentation, but I learned from those mistakes. Overall, David was satisfied with my presentation. So most of the time I had to go find my own work to do and the following is an example of one of those occasions. The fifth official mission was given to me by my mentor Michelle. She was currently creating a PowerPoint demo that she would offer to customers experiencing difficulty with certain SAC features. She wanted me to research and play with the functionality of the analytics apps as well as the Smart Predict functionality that can be found on SAC. Analytics apps are a feature that allows you to create and display your data like graphs and tables, but they also allow you to add additional functionality, such as adding a button to a graph that brings up a pop-up of the chart in detail, all in one. place. Smart Predict can predict future values, events or trends, not just numerical values as in time series forecasting. The sixth and my favorite mission is the one I voluntarily applied for. The CoE intern manager, David, sent an email to each intern regarding opportunities to participate in a project (one of many) that required certain members. The one I applied for needed: two Business Analysts, a SCRUM Master, four Developers and a Developer Lead. I applied and got the job as one of the business analysts. So overall, the project required a lot of meetings, whether team meetings or, for me, meetings between Business Analysts. One of the big tasks that the other business analyst and I had to accomplish was determining what core features were prioritized, what features needed to be included. Since we had received the basic functionality beforehand, this was quite easy to do. With these basic features, we had to translate them from words into use case diagrams. The module I took at college was extremely useful as I had learned this method as part of the module. We first made these use case diagrams on a whiteboard, but after discussion with the developers, we translated them into wireframes. To create the wireframe prototypes, we used a publicly available web application called “Build”. We continued to repeat the process of meeting with developers to receive feedback not only on our prototypes, but also on any updates or changes they wanted to make to the project design. At the end of the project we presented it in front of David and Paul (CoE Ireland Manager) and both were very impressed with our efforts. I will now discuss the secondary tasks that I completed during my internship. First, I completed several mandatory and optional online training courses like “How to Manage Conflict in the Workplace.” I attended classroom training courses like SAPTEC and HANA, which taught me general knowledge about SAP and some details about their products. I attended events organized by the intern committee, such as going to the Conrad Hotel to attend an all-day national intern meeting which included games, a panel of senior SAP members, variouslectures on interesting topics and a dinner. Another event that I was particularly interested in was the 3D printing workshop, as I have always wanted to see a 3D printer and the 3D printing process. I attended several presentations by people on my team on certain SAC features which deepened my knowledge of SAC. Some topics in these sessions included discussing the Digital Boardroom functionality available on SAC as well as general tips and tricks for working with SAC or even just how to get started with the software. Looking back, I feel like I accomplished a lot during my internship. If I were to repeat the whole experience, I feel like I would do my best to acquire more practical work and less theory-focused work. Since doing the internship I have discovered an interest in software testing, so I would have liked more work centered around that and perhaps more projects based on that earlier in the internship.Summary knowledge acquired during my internshipI will divide this into two sections: Technical Knowledge Acquired and “Soft Skills” Acquired. Technical Knowledge I wasn't sure what type of technology I would be able to use. I had imagined myself sitting at a desk, writing code from nine to five, but that wasn't the case. Instead, most of the knowledge acquired was gained by experimenting and completing assignments on various SAP products (mainly SAC), participating in the various mandatory and optional training courses like SAPTEC and HANA and taking on the role of a business analyst in the major project in which I participated. I want to start by talking about the knowledge gained from the work I've done as a business analyst. First of all, I learned the true meaning of what a Business Analyst is and the tasks that would be involved in this role. A Business Analyst acts as a mediator between the company and the software. It's their job to provide quality assurance, testing, user interface design and use cases. It's their job to tell developers what to build and what to prioritize. The first task we did was to create use case diagrams. I had made them in college, but seeing them used for their intended purpose in the workplace was fascinating to see. The other business analyst also knew about use case Diagrams but his icon for each use case was slightly different which was peculiar to see. The first piece of technology we used to create prototype versions of the use case diagrams was “Build”. Until then, construction was something, I had never been used to doing everything that was done, it was a completely new experience. The software reminded me a lot of the wireframing tool I used in second year called “Balsamiq Mockups 3”. However, in Build, because SAP had some form of relationship with Build, we had access to wireframes based on wireframes. software used by SAP and therefore, creating use case diagrams was much easier for us and allowed us to visualize our idea in a more meaningful way. The main thing I learned from this was how the use case diagram I learned in college was translated into a real-world situation. The whole process was really eye-opening and I really enjoyed it and made me think about being a business analyst as a possible future career. I want to talk about the knowledge I have gained from the work I have done onthe SAC platform. This is the main software I used during the internship. I first want to talk about stories and patterns in SAC. A story allows you to visualize your data in tables, graphs, charts, and other elements to demonstrate your business purpose. A template can be based on several things: a story you previously created, a file on your computer, or it can just be a completely blank template. A template is like a story but allows you to add additional functionality (it's more flexible than a story). The predicative scenarios on the SAC platform were probably the feature that interested me the most. Predictive scenarios will receive data about a system or object and, with the data it contains (historical and current data), create hypotheses around it. There are three types available on the SAC platform: time series forecasting, classification and regression. I have already explained time series forecasting. Classification involves predicting membership in categories and regression involves predicting numerical values based on fluctuations in correlated variables. Next comes planning in SAC. Planning in SAC involves a template that you can modify at will, by adding or changing percentages or numbers in the cells, the software will automatically adapt/update anything affected by these numbers. Finally, Analytic Applications is very similar to “Build” and Balsamiq Mockups 3, but it gives you a blank canvas on the SAC platform where you can import your stories and models and add additional functionality to them. For example, you can drag and drop objects like buttons and text fields and add them to your story. In addition to the two topics I talked about above, I gained a lot of knowledge from several other minor things. The face-to-face training at the beginning where I discovered HANA (In-memory, relational database), SAPTEC (Basic principles of certain SAP products) and ABAP (Programming language created by SAP), were full of knowledge and information to learn. Another major source of knowledge was the Power Hour sessions. Power Hour sessions were typically global virtual presentations that anyone from SAP could participate in. The sessions would be led by a person who would spend the next hour explaining a certain topic. For example, some topics included: cyber psychology, technical interview workshop, sessions on new companies joining SAP. My favorite was the Machine Learning Power Hour for several reasons, it was relevant, it's something I'm personally interested in and it would prepare me for fourth grade because there is a module on Machine Learning. I have to say that the technical aspect of the knowledge I acquired was very specific to SAP. I have mainly used SAP software, which means that to take full advantage of the experience and knowledge gained, it would be ideal for me to work at SAP, as many companies do not use SAP software at all. However, I feel some aspects of the technical knowledge gained may be transferable, such as the work I did as a business analyst which included extensive experience in testing and creating use case diagrams. I now have a good amount of experience creating charts, graphs and other visual aids as well as light experience with predictive technologies. I hope that all these experiences combined will help me in some way during the coursefrom fourth grade and beyond.Soft Skills LearnedThe first major soft skill I learned and improved was my teamwork skills. For most of the internship, I worked within a group, whether it was working on an assignment with a fellow intern on my team, or working with a group of interns from different teams on a project or work as a complete team. employees on time. Looking back on my internship, I only had one assignment, which gave me a great opportunity to improve and refine my teamwork skills. Teamwork skills include several other different skills such as: communication skills, cooperation skills, and patience. I will be able to review each one and give examples of how I used these skills and improved them. Communication in the workplace is extremely important. I used it every day during my internship. I think communication was very important throughout my internship because it allowed me to work well with others and be productive with others. Cooperation in the workplace is equally important. Throughout my internship, I observed and experienced many benefits of cooperation with my colleagues. Because everyone is working together toward the same goal, the task at hand is accomplished more quickly. Additionally, because it usually involves working with more than one person, tasks are distributed within the group, so employees (including managers) have more time to complete their own tasks and spend less time managing conflicts due to unclear communication. I think patience is a quality that I probably wouldn't have thought about before the internship. I think this is one of the most important qualities you should have if you work in a team. Patience allows you to think before acting, especially in intense situations. Patience also creates a more helpful and kinder work environment. Instead of lashing out at someone for something they did wrong, thus leading to hostility between employees, patience allows you to step back and address the situation and perhaps, instead of lashing out, give constructive criticism. This is something I have witnessed many times in my workplace, especially in terms of the patience of full-time employees with interns. There were several occasions where I was constantly struggling trying to complete an assignment given to me by my manager and each time he was more than happy to help me and direct me to online resources as well as pointing out my mistakes and reinforcing, which I should do instead. Overall, I'm very passionate about being patient when working with others, and working at SAP has reinforced this thought. One important thing I learned regarding teamwork skills is that not everyone is a team player, so not everyone wants to communicate and cooperate with each other. others and be patient with each other. Some members of my team would try to make you believe that they wanted to cooperate with you on a project, but you would soon realize it was all in their minds. What I'm talking about now is something I didn't experience during the group project last semester but something I've experienced since I came here, only with specific people and I have the feel like this is something vital that I learned about people in general and it made me realize that I was toowelcoming and indulgent. This is the reality of the workplace, you are bound to encounter people who try to manipulate either the team or certain employees into believing that they are the reason the work is done or that they know everything. I have seen that these people also tend to be very jealous of others, especially if they are not involved in the work you are doing. I think overall this is an important aspect to highlight when it comes to teamwork because I feel like there isn't enough awareness of it, which is why these people tend to get away with it. I learned and improved my general sense of responsibility. Honestly, before embarking on the internship, I never thought that responsibility would be one of the things I would learn. I have had responsibilities in the past, with my small part-time job and being part of the group project last semester, but during this internship, I feel like I understand the true meaning of responsibility. Throughout the internship, I was given several responsibilities in the form of projects ranging from mildly challenging to difficult. Here are some examples: My very first assignment, looking back, was a very small and minor assignment, but it still came with an incredible amount of responsibility. The document I was going to write would have to be one hundred percent accurate to be useful. The document was a step-by-step guide to establishing a live connection on SAC that would be used by employees and customers who use SAC and so it was a lot of pressure. The way I handled responsibilities throughout the internship changed at first. At first, I was incredibly nervous and anxious about my colleagues giving me assignments because I was afraid I wouldn't be able to complete them. . Also, at first I thought that since this was my mission, I should try to get as little help as possible. Compare this time to the end of the internship, where I can't wait to work on new missions. If I run into problems now, I know I can count on my colleagues to help me however they can. My view of responsibility has evolved over the past six months and I am sure it will be of great help when it comes to fourth year and final year project responsibility. Reflecting on my training during 'an internshipSome principles of computer science Science was reflected by my placement, including: Keep in mind: this is just a sample. Get a personalized article from our expert writers now. Get a custom essay Complexity: Determines the speed of a process and places that speed into a classification (e.g. O(1), O(n), O(log(n))). SAP delivers software products to customers, who must fulfill their purpose quickly and accurately while sacrificing as little as possible. Customers work with SAC and therefore it must be simple, easy to use and fast. However, sometimes, when creating a model, for example, the software crashed or the loading times from one screen to another were long. It was interesting to see how SAP tried to solve these kinds of problems by providing communication and support directly to the customer via Skype, the computer or sometimes in person, as well as providing updates on their software. Modeling: Whether it's an idea about how to approach a problem that you can visualize in your head or an idea that you can project onto paper, modeling involves thinking about the concept of the problem. This was reflected in a few different ways: Working with SAC, which required me to take requirements in words and translate them into a literal model (like a/

Navigation

« Prev 1 2 3 4 5 Next »

Get In Touch