FW migration plan

Get Started. It's Free
or sign up with your email address
FW migration plan by Mind Map: FW migration plan

1. estimate

1.1. merging FW

1.1.1. 16d

1.2. parts

1.2.1. activity_log + runable_log + single_use_link 5d

1.2.2. lookup + content 6d

1.2.3. quickbooks 2d

1.2.4. white labels 5d

1.2.5. companies 4d

1.2.6. locations 6d

1.2.7. user + messages 4d

1.2.8. vendor components 3d

1.2.9. decision tables 3d

1.2.10. vendor+ package + service + price adjustments 6d

1.2.11. applicants + prospects 5d

1.2.12. reports 3d

1.2.13. application 7d

1.2.14. payments + invoices 6d

1.2.15. online application 3d

2. intro

2.1. Most Frameworks consist from layers

2.1.1. Model

2.1.1.1. holds business logic

2.1.1.2. handles data storing

2.1.2. View

2.1.2.1. represents data to user

2.1.3. Controller

2.1.3.1. analyses request choosing which movel to Run and which View to show as responce

2.2. currently we have

2.2.1. about 30-40% of controllers holds business logic

2.2.2. there are places where view decides what model to run

2.2.3. i.e. we have messy layers

3. plan

3.1. moving site entry point from Kohana to Symfony

3.2. rewrite models

3.2.1. starting from less complex

3.2.2. moving logic into models

3.2.3. adding validation

3.3. rewrite views

3.3.1. declaring which variables view needs

3.4. rewriting controllers

3.4.1. creating alternate entry point for Symfony controllers

3.5. removing Kohana

4. profit

4.1. +20% to development speed

4.2. site speedup

4.2.1. due to better design and resource handling

4.3. Symfony has LTS

4.3.1. 5 years w/o major version update