Scribd
Upload
3 views

Technical_Task_Modernization_Case_Studies

Uploaded by

okhogbe caleb
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
3 views

Technical_Task_Modernization_Case_Studies

Uploaded by

okhogbe caleb
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Technical task for blog articles

modlogix.com

Text Requirements
Read our Article/Blog Post Formatting Guidelines for copywriters and content managers.

3 Legacy Software Modernization Case Studies and 12


Lessons We’ve Learned

ICP: CTO, CEO, Product owner, Director of IT/IT Manager

Main goals of the article:


● Nurture the leads funnel
● Website exploration
● Form submission
We should write the article because:
● Software modernization is risky and costly process. The decision maker (our reader)
needs real proofs of software modernization effectiveness. The main pain – uncertainty
that these efforts will pay off.
Article’s usefulness/uniqueness is:
● Client’s expertise
Mention these articles:
● Why do companies choose software modernization
https://modlogix.com/blog/5-main-reasons-companies-move-to-the-cloud-environment/

● Software modernization threats and how companies can overcome them


https://modlogix.com/blog/3-common-mistakes-in-legacy-software-modernization/

● How to check your software modernization vendor


https://modlogix.com/blog/9-questions-to-validate-your-legacy-modernization-vendor-bef
ore-starting-the-cloud-migration-process/

Interlinking with other pages:

From the new page to the following URL Anchor


migrate from AngularJS to Angular https://modlogix.com/case-studies/migration-f
rom-angularjs-to-angular-11/
legacy software modernization approaches https://modlogix.com/blog/legacy-system-mod
ernization-approaches-practical-advice-on-de
aling-with-outdated-software/
.NET Framework to .NET Core migration How To Effectively Conduct A Legacy System
Integration
disadvantages of legacy systems Advantages And Disadvantages Of Legacy
Systems
legacy software modernization company https://modlogix.com/
examples of legacy modernization https://modlogix.com/case-studies/

Use unique meta tags


Title 3 Legacy System Modernization Success Stories and 12
Lessons We’ve Learned
Description Form description using keywords “legacy software
modernization”, and also:

● case studies.

Length: 100-150 characters (including spaces). Use the ✅


symbol between sentences to make the search engine listing
or ▶️

snippet appear more attractive.


H1 3 Legacy Software Modernization Case Studies and 12
Lessons We’ve Learned

Examples of quality articles:


● https://www.scnsoft.com/blog/practical-approach-to-legacy-system-modernization

● https://www.businesswire.com/news/home/20200528005186/en/74-Of-Organizations-Fai
l-to-Complete-Legacy-System-Modernization-Projects-New-Report-From-Advanced-Rev
eals
● https://modlogix.com/case-studies/migration-from-angularjs-to-angular-11/
● https://modlogix.com/case-studies/how-to-migrate-from-net-framework-to-net-core/
● https://modlogix.com/case-studies/webforms-to-azure-migration-case-study/

Recommendation for article content:


● Article volume should be minimum 800 words — maximum 1200 words.
● Article should be unique and answer as much as possible questions of the targeted
audience
● Using infographics, data statistics and other visual content improves article value and
helps to fully develop the article's topic.
● It’s better to write an article according to the article’s structure (plan). You may add your
own paragraphs. If there are any changes, make sure it improves user experience and
engagement.
● Keywords are colored and should be used in H2 subheadings the way they were written
unless there is a mistake that should be corrected

Article structure

H1 - 3 Legacy Software Modernization Case Studies and 12 Lessons We’ve


Learned

● In the introduction briefly describe what this article is about, what insights it contains or
what problems it solves, why readers should proceed reading, what value it contains.
● Or you can also use statistics:
o How many dead languages exist?
o How many companies use them in software products?
o The pace of modernization during the past years.

H2 – Case Study #1 Upgrading AngularJS to Angular 11 for an Enterprise-wide Web


Platform
https://modlogix.com/case-studies/migration-from-angularjs-to-angular-11/

● the final structure: Challenges, Solution, Results, Lessons Learned


● what technologies were used
● how long did the process take?
● what business problems and challenges we resolved by modernizing their software
● what lessons we learned from this project, create H3 subheadings for each lesson (tip:
find lessons in the Key Takeaways section but rewrite them a bit)
o H3: Lesson 1.1: Frameworks with the same roots can be utterly different, thus,
they must be approached differently
o H3: Lesson 1.2: Redesign the app in parallel if users and business context require
it
o H3: Lesson 1.3: Don’t be afraid to rewrite the app’s parts or the whole app
o H3: Lesson 1.4: Consultation with a professional software modernization company
ensures successful migration

H2 - Case Study #2 Migrating .NET Framework 4.7 Backend of the Large-scale Enterprise
System to .NET Core 3.2
https://modlogix.com/case-studies/how-to-migrate-from-net-framework-to-net-core/

● the final structure: Challenges, Solution, Results, Lessons Learned


● what technologies were used
● how long did the process take?
● what business problems and challenges we resolved by modernizing their software
● what lessons we learned from this project, create H3 subheadings for each lesson (tip:
find lessons in the Key Takeaways section but rewrite them a bit)
o H3: Lesson 1.5: Refactor, refactor, and refactor again
o H3: Lesson 1.6: Plan the migration in advance
o H3: Lesson 1.7: Thoroughly choose the proper substitutes for the existing
app’s libraries and components
o H3: Lesson 1.8: Avoid possible pitfalls during the migration from the very
beginning

H2 – Case Study #3 Cloud migration from ASP.NET Webforms to Microsoft Azure


https://modlogix.com/case-studies/webforms-to-azure-migration-case-study/

● the final structure: Challenges, Solution, Results, Lessons Learned


● what technologies were used
● how long did the process take?
● what business problems and challenges we resolved by modernizing their software
● what lessons we learned from this project, create H3 subheadings for each lesson (tip:
find lessons in the Key Takeaways section but rewrite them a bit)
o H3: Lesson 1.9: Calculate the cost of cloud migration beforehand
o H3: Lesson 1.10: Understand your workloads before selecting a cloud model
o H3: Lesson 1.11: Pay attention to the solution architecture in the cloud
o H3: Lesson 1.12: Adopt a comprehensive approach to development

Н2 - Final Thoughts
● Make a conclusion that companies can modernize their software without business
disruptions and extra risks. And as result, they can get the outstanding results that boost
ROI, cut costs, improve performance and productivity, reduce technical debt, and a lot
more. You just need to take the first step. What should it be? Take a free consultation
from true experts.

Core keywords
● legacy system modernization success stories
● legacy system modernization case studies
● case studies in legacy system modernization
● legacy software modernization case study
● legacy system modernization
● system modernization
● legacy systems modernization
● legacy software modernization
● software modernization

Additional keywords

● legacy application
● legacy system
● outdated
● software
● development
● developer
● company
● services
● provider
● vendor
● solution
● framework
● technology
● industry
● pitfall
● challenge
● issue
● data
● management

● process

You might also like