5. Tasks of architect
Come up with plan how to build application
Find solutions to common problems
Detect new problems during development
Making decisions that have strong impact
Helping and consulting developers
Having overview of system at all levels
6. Challenges
Making complex things work together as one
Learning all the time to gain better understanding of software
development and the nature of systems
Finding and working out new patterns that can be used also
in future projects
Having good understanding of your play-ground
7. One thing ...
„You don’ born to be architect – you grow to architect,
it is long and hard road“
13. What is model in MVC?
„Model in MVC can be any class that is used to carry data from
controller to view. It’s up to you to define the structure and meaning of
model.“
14. Some suggestions
Good model performs no operations when view is rendered
Keep models simple
Don’t put business or data logic to model
Don’t use business objects as models or part of models
15. Mapping
Mapping can be done:
manually
by writing some code to automate the process
using third-party tools
I prefer AutoMapper
17. Why to extend UI?
To avoid adding working code to views
To keep views smaller at size
To avoid repeating same output logic in views
Best extensions can be gathered to library for future projects
19. Why not dependencies?
Tightly coupled coe – hard to test and manage
Replacing parts of system is not easy
Unit testing is hard if not possible
Lost flexibility (run system in conceptually different environments)
20. What dependencies to break?
Access to data (repositories, data context)
Application services layer
Access to file storage
Access to network resources
Logging