HOME > Employment Information: SE Jobs Employment information SE work Employee introduction Education and training Recruitment Q & A New graduate recruitment guidelines New graduate entry Company information session information Mid-career recruitment Employment information recruit When you hear "SE", what kind of person and what kind of work do you imagine? "Are you the one who develops programs for computers all day long? " No, I don't think I'm a person who does not develop programs, but only proposes systems to customers. ] , It may be an answer like this. Then, if we can negotiate with the customer, is it not necessary to develop the program? That alone does not stop SE. SE is not a sales engineer. Of course, even if you have only the ability to develop programs, you cannot say that you are an SE unless you have the ability to negotiate with customers. In TSR, it is not "SE = programmer". "Then, what kind of work does SE do? In a nutshell, the SE image we draw refers to the following people. "A person who can analyze the causes of customers' worries and problems, propose the optimum system for them, and embody them using computers." It is quite natural for companies to introduce computers in this era. is. It may be more difficult to find a company that does not have a computer. And as long as there is a computer, SE is an irreplaceable existence for a company. So what kind of knowledge does SE need? 1. Applications and basic knowledge for using computers Of course, you need to acquire programming skills, but if you are working on a network, you need to acquire knowledge on network construction, and if you are working on a database, you need to acquire knowledge on database construction and management. The knowledge required by each customer varies. The computer industry is a particularly fast-moving world. In fact, the computer knowledge I gained a year ago may no longer work at all. If someone neglects to study because they have a little more computer knowledge than others, they will soon be left behind. 2. Customer's business knowledge For example, if you are involved in a banking system, you will need to know the general terms of lending, how the loan works, and so on. If you are involved in a system in the construction field, you need a wide range of knowledge, such as knowledge of drawing creation, knowledge of process management work (cost, construction period, etc.), as well as general terms of the construction industry. We believe that by becoming familiar with our customers' business knowledge, we will be able to understand their concerns and problems for the first time and derive the best answer to them. 3. Ability to put together a system by making full use of them As mentioned above, even if you have only the ability to negotiate with customers or just the ability to develop programs, you cannot call it a true SE. Only after doing both is it called SE. So how do you actually get the job done? Understand what kind of business you want to computerize and summarize the requirements. We will summarize the basic policy and system concept for systematization. For example, when there is a request from a customer who wants to do the work that was previously done on the desk, such as organizing slips, on a computer, clarify at this stage what is needed to systematize these. Put. We will design the system to realize the contents organized in the requirements definition on the computer. In the above example, we will determine here what kind of input data is required to computerize slip arrangement, or what kind of screen etc. is required for the customer to perform smooth operation. .. Based on the design document, create a program so that it can be realized on a computer. Also called "coding". It is necessary not only to create a program blindly, but also to create a program that is easy to maintain. ■ Unit test Check whether the created function unit operates according to the design document. ■ Integration test Tests a program that links unit- tested functions. Here, we mainly test whether the data exchange between functions is successful. ■ System test After the integration test is completed, test whether the entire program is operating according to the design document. After testing, we will provide the customer with the completed system. We provide operational guidance to customers and maintenance work in the unlikely event of a system malfunction. We call those who can do these things "SE". "I can't do that! Of course, we cannot do this from the beginning. We were not "SE" from the beginning either. Everyone is "amateur" at first. But we have great seniors. And these people are all growing up to be called "professionals". If you are interested in TSR, why not work with us? Information security basic policy Privacy policy About the handling of personal information site map Copyright (c) Tokyo System Research Corp. All Rights Reserved.