All geek questions in one place

What considerations need to be considered when switching an application to support?

I will take on the role of supporting a complex application that is moving from the development team. This application is a sharepoint solution that connects to multiple (7) web services. The development team works almost immediately and will be available only for small questions.

I am new to this role, so I wonder what suggestions you have for me when I take on this big project. What are some considerations that need to be made to make the transition to support smooth and inaccurate?

I read the documentation, but I already see some gaps that need to be filled. The application is very (perhaps overly) customizable, and there is a lot of code entered. Code execution is the only way to gain an understanding of what is actually happening.

+3
source share
2 answers

It looks like your environment is already set up if you can debug the application, so the first thing I’m going to offer in a knowledge transfer situation. Some common things I get from developers before they leave:

  • A list of third-party components that the application uses, along with license information and website logins, if applicable.

  • , , , . , , .. , , , .

  • ​​ " " (.. , , , . , , , , , .

  • , , , , . .

, , , , , . , , , .

, , , ? , , , - -, , . // . , , .

, .

+2

( SharePoint), , .

, (IIS, ..), . , .

sys - SharePoint, . , , .

.

+1

Source: https://habr.com/ru/post/1747277/

More articles:


All Articles