This is an AI translated post.
[SI Developer Story] 08. Understanding Your Role in an SI Project During Initial Deployment
- Writing language: Korean
- •
-
Base country: All countries
- •
- Information Technology
0000-00-00 00:00:00
Select Language
Summarized by durumis AI
- A developer newly deployed to an SI project must understand the system construction goals and progress of the project after setting up the development environment. Especially, new developers may have difficulty understanding business logic due to their lack of experience.
- It is efficient to understand the overall development direction and required functions through proposals and RFPs, and to note down any unclear parts and ask questions all at once.
- You should focus on understanding the project atmosphere and content for about a month, preparing yourself to participate in full-fledged development afterwards.
SI Developer Story
#8. Initial Deployment of an SI Project - Understanding Your Work
Typically, developers, especially new hires, are likely to be deployed to a project when development has already begun.
On your first day, you will set up the development environment, get an IP address for network access, download the source code being developed, and set up your development environment. After that, you need to figure out what kind of system this project is building and how it has been built so far.
Experienced developers can, to some extent, understand the situation on their own based on their experience and only ask their mentor or colleagues for clarification on what they need. However, the situation is different for inexperienced newcomers.
They lack the knowledge of the source code of a different size than what they learned in school and the work, so it takes several times longer to understand the business logic. However, other developers are busy handling their own development tasks, so training in an SI is a dream. Therefore, you need to figure it out on your own to some extent, and the first thing you should do is check the proposal among the project documents.
The proposal is a document that suggests, "We will make this program for you." The proposal outlines the overall development direction and contains a summary of the system you want to build, so looking at the proposal will help you understand the overall framework.
Then, check the RFP to see what functions are required and understand the work of the system. If you don't understand anything in between, make a separate note and ask all at once when your senior seems free. If you ask questions one at a time, it will be annoying. You will spend about a month understanding the project atmosphere and contents, but after a month, you will be fully involved in development, so make sure you understand it during this period.
