1

I find myself difficult to remembering the definitions of software engineering terms such as domain layer, entity object, busines logic and etc.

I mean when I read a definition of something let say the definition of "business logic" I find many other terms related to it in the definition that I don't know the meaning that make me to google it again and so on and it makes me confuse even more. it seems it is happening because I jump reading something "high level" and skip the basic.

so what I am asking is i would like to know the basics, I mean the orders which terms should i read first. should I read "business logic" first before "entity object" or ... and so on?

FYI i already know OOP concepts.

closed as too broad by 5gon12eder, gnat, TZHX, Jörg W Mittag, David Arno Feb 27 '17 at 9:15

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • When you look something up, do so with the narrow goal of understanding whatever it is you're reading. If you start looking up more and more, you'll never finish. – Brandin Feb 27 '17 at 7:32
  • Do not read on several resources at the same time. Pick on trusted resource and study and summarize it. Once you understand those notions from one single trusted resource, you will find other resources are repeating the same ideas in different manners because each one has his own way of thinking and explaining. – Billal Begueradj Feb 27 '17 at 8:02
  • can you guys suggest me source book/site to learn this from very beginning? – Kakashi Feb 27 '17 at 10:41
0

It is hard because you have no reference yet. You may be able to memorize the terms given enough effort but they probably won't mean anything to you. You need some real world examples to map them to. Once you recognize the concepts in a real piece of software and experienced the problems they address it will be much easier.

So instead of trying to memorize definitions, try to find example code for each term that appears hard to grasp and make sure you get it before moving on to the next.

Not the answer you're looking for? Browse other questions tagged or ask your own question.