From programmer to System analyst (turn)

People should be familiar with these two words, but the meaning contained in the word may not be particularly clear. First of all, it must be explained that programmers and system analysts do not exist who senior who is inferior to the difference, they are two professions, the requirements of professional skills are completely different. So it's wrong to say that a powerful programmer is a system analyst. Of course, the system analyst's skills require him to know how to write a program, but his focus is on how to cut a large project into small pieces that fit the individual, and then organize the small pieces. The responsibility of the programmer is to realize these small pieces better and faster.
Before this chapter, we were talking about the skills that a qualified programmer should have, and certainly not just that. The reason we're here to talk about system analysts is because our columns are called Software engineering, not programmers from getting started to being proficient.
Before we begin, we'll look at the author's insightful insights into analysis and design in the thinking in Java:
Analysis and Design
The object-oriented paradigm is a new and radically different way of thinking about programming, and many people begin to frown on how to construct a project. In fact, we can make a "good" design that leverages all the benefits that OOP offers.
Excuse me, here comes the word oop, which he means is the object of the face, although not mentioned before, but in the current world of OO concept, people should not be too unfamiliar to him. Here I give a brief explanation. In fact, I've been talking about the experience of writing a long time ago (what, teach us antiques, beat him!). , but the previous non-OO (process-based) software design approach is now rarely adopted internationally, so I'm talking about software design when all the concepts are based on OO. Even if the concept of OO is very simple, think about it, we learn C + + when the first use of the class is not some animals, squares, and so on, are examples of life, right. Oo is actually the way we look at the world. But the first because of the underdevelopment of computer technology, we have to use some very strange description to express our meaning, only so that the computer can understand, very stupid is not it. For example, we must use parameters, procedures, functions. So the software design method at that time is based on the process. Give a simple example to show the difference between OO design methods and process based design methods: a simple daily phrase-"I eat", the use of Oo method to express or "I eat", but if the process based on the description of the word will become "I eat (rice)" is not very awkward. If you think you have any questions about Oo, look at another topic under the Software Engineering column: "Thinking in Java appreciation"