↓↓↓↓ More related articles recommended ↓↓↓ More
Company administrative practice report
Banking practice report 1000 words
1000 word student service practice report.
Internship report of HR Commissioner 1000 words.
Practice report of finance major
▼ Summary of Front-end Development Practice Part I
Today, let's briefly talk about Struts+Spring+Hibernate above.
Struts stands for: presentation layer; Spring stands for: business logic layer; Hibernate stands for persistence layer. At present, they are the most used frameworks in Java Web programming and development. In fact, this distinction is to meet the needs of maintaining consistency between different departments in the process of software development. To put it simply, everyone writes code in a pattern, which can ensure that everyone can read the written program, and some basic things can be automatically generated for you without you typing one by one, thus realizing code reuse. This not only ensures readability, but also improves the development efficiency, thus reducing the cost. Struts is actually the concrete realization of Model 2 (Model 1) in Java MVC design pattern, while Spring realizes the centralized management of objects and even transactions (such as declarative transactions) by providing ICO (Control Inversion), and also introduces AOP (Object Oriented Programming), which is of course completely compatible with other frameworks. Hibernate is a middleware to realize the mapping between objects and relationships. As we all know, the mainstream database is still relational, but the object-oriented idea has been adopted in programming. How do programmers manipulate the data in the database like objects? Hibernate is such a framework. In the past, Java programmers used to deal with the database and write SQL statements through JDBC, but Hibernate completely changed all this. It was repackaged on JDBC and realized that the database could be operated without writing SQL statements.
It is worth reminding that these three frameworks are lightweight, non-invasive or low-invasive, unlike heavyweight frameworks like EJB, which can maximize the reusability of code.
▼ Summary of Front-end Development Practice Part II
In the past, I seldom did my own programs at school, and I knew nothing about software engineering. When I came to the company and started to contact with "large-scale" software development (in fact, it seems that there are very few internship projects now), I was really confused for a while. Compared with VSS, MVC, QA and CMMI, my ignorance of JAVA, JSP and XML is nothing to mention. Everyone didn't want to lose at the "starting point", so they tacitly worked overtime for two months.
When we first arrived, "enlightenment education" seemed very slow, and we often planned where to play. FLYSKY(20 and I (the only southern brothers among the 20 freshmen, from Software College) often go out to eat all kinds of snacks and taste the local flavor of various places, which is his habit. The training that started after that was not very sad. Teachers of JAVA, C++ and ORACLE speak very well, so that few of us can understand them. People are getting anxious. I read 10 almost every night.
"Sorry, man, I practiced." I bought a book "Thinking in JAVA" in February before I came, and I prepared JAVA when I understood it. Although C++ didn't go to class, he took a fancy to it intuitively and watched it for a while. As for ORACLE, although I don't understand it, after all, because I admire Yunfei's personality and professionalism, my SQL elective course is not in vain. The major is still a little "basic", and our self-study ability is not boastful, but basically maintained. But later, when I waited for Japanese class, I was completely confused: I have no language talent and my memory is seriously insufficient, so I have been particularly afraid of going to Japanese class. But I especially like the teacher's feeling of speaking, and she has always been very kind to me, so I still study very hard.
With the end of the training, we began to formally enter the project. From requirements analysis, outline design to detailed design, every detail of software development is touched step by step. The most unbearable thing is to write a "weekly report" every day and fill in your own labor results. Because of this, I have been notified by QA several times, and I am really depressed. In fact, I am very grateful for this institutionalized thing now. In some cases, the formation of good habits depends on coercion. After detailed design is the long-awaited coding, I thought I could finally do something "down to business". Looking back now, I know that coding only accounts for about 1/4 of the whole software development process, and other links are not as insignificant as I thought.
In fact, I didn't do well in coding, mainly because I didn't seriously understand the requirements and specifications at the stage of requirements analysis, and I went back to school to catch up with my old classmates at a critical time when coding. At that time, the project manager (PM) often told us, "Try your best if you have any questions, and don't ask me often.". Actually, PM is for us to brew it ourselves. Only by "holding back" and "holding back" can we have real gains when we encounter problems. My absence for three days happened to be a "leap" in everyone's technology/thinking. The solutions to many difficult problems are basically mature, and everyone's coding is close to 50%, so I feel a lot behind when I come back. There is also a problem with the machine in the middle of coding, and the environment can't keep up, which makes me more nervous and impatient and greatly affects my morale. Later, I used the overtime during May Day to complete my module and reached the first milestone. In fact, the experience from finding backwardness to catching up with overtime is also a milestone for me. Not only tested their own ability and psychological quality, but also proved their sense of collective responsibility and spirit of cooperation. I can ask others to help me catch up with the progress, but then I miss the opportunity to learn and I still can't do it when I encounter problems in the future; I can also bite the bullet and postpone the project, which will make my future life difficult. It is not my character to do so. Facts have proved that it is a good thing for me to resist the pressure and complete the task independently, both for the collective and for me personally.
▼ Summary of Front-end Development Practice Part III
Today, with the high development of science and technology, computers are playing an increasingly prominent role among people. As a computer language, learning C helps us to better understand and communicate with computers. Therefore, learning C language is particularly important for us.
During this week, our professional students studied C language program under the guidance of professional teachers. Before that, we had studied C course for a semester, and we had a certain understanding of it, but we only stayed within the scope of understanding and were still unfamiliar with many things. More often, we find it very difficult to use it. After all, everything is difficult at the beginning.
Because of the time, our practical class teacher did not give us a detailed introduction, but simply introduced several important practical exercises. Including program module processing, simple interface program, advanced interface program, program addition and modification, linear regression processing with program and drawing particle size distribution map with C language program.
Computer experiment is an indispensable practical link in learning programming language, especially C language, which is flexible and concise and needs to be mastered through programming practice. The learning purpose of programming language can be summarized as learning grammar rules, mastering programming methods and improving program development ability, all of which should be completed through full practical operation.
In addition to classroom teaching, learning C programming language must ensure that there is no less than classroom teaching hours of computer time. Due to the limitation of class hours, it is impossible to arrange too many unified computer experiments in the course, so I hope students can effectively use the opportunity of computer experiments in the course and master the ability of developing programs in C language as soon as possible, so as to lay a good foundation for further study. For this reason, we arranged 12 computer experiment according to the content and progress of classroom teaching. The purpose of course computer experiment is not only to verify the content of teaching materials and lectures, but also to check whether the program I have written is correct. The purpose of the computer experiment curriculum can be summarized as follows:
1. Deepen the understanding of classroom teaching content
There are many grammar rules about C language to be taught in class, which sounds boring and difficult to remember. It is not advisable to learn by rote. However, if we want to use C language as a tool to solve practical problems, we must master it. Through many computer exercises, I have a perceptual knowledge of grammar, deepened my understanding of it, and naturally mastered the grammar rules of C language on the basis of understanding. I think I have understood something in class, but I will find the deviation of my original understanding in computer practice. This is because most students are novices in programming and lack programming practice.
Learning C language can't stop at learning its grammar rules, but use the learned knowledge to write C language programs to solve practical problems. C language is used as a tool to describe the steps to solve practical problems, and computers help us solve problems. Only by using computers can we test whether we can master C language and whether our own programs can solve problems correctly.
Verifying whether your program is correct through computer experiments is probably the mentality of most students when they finish their teachers' homework. But in the field of programming, this is a traditional and wrong concept, which must be overcome. Because under the control of this kind of thinking, you may try to "cover up" the mistakes in the program instead of finding as many problems as possible. Compiling your own program and debugging it on your computer may lead to many unexpected situations. By solving these problems, you can gradually improve your understanding of C language and program development ability.
2. Be familiar with the program development environment and learn the operation method of computer system.
A C language program, from editing, compiling, linking to running, can only be carried out in a certain external running environment. The so-called "environment" is the hardware and software conditions of the computer system used. Only by learning to use these environments can we develop programs. Through computer experiments, I am familiar with the development environment of C language, laying a foundation for writing computer programs to solve practical problems in the future. At the same time, when you encounter other development environments in the future, you will soon learn to use the new system.
3. Learn computer debugging programs
Completing the program does not mean that everything is normal. A program that you think is foolproof may be troublesome when it is actually running on a computer. For example, the compiler detected many errors. Sometimes the program itself can run smoothly without grammatical errors, but the running result is obviously wrong. The compiler system provided by the development environment cannot find this kind of program logic error, so it can only rely on its own computer experience to analyze and judge the error. Program debugging is a highly technical job, and it is very important for beginners to master the program debugging method as soon as possible. Sometimes a small mistake takes you hours, and debugging experts can see the mistake at a glance.
& gt& gt& gt Next page, more exciting "Summary of Front-end Development Practice" var _ HMT = _ HMT || []; (function(){ var hm = document . createelement(" script ")； hm.src = "/hm.js？ 1 fc3c 5445 c 1 ba 79 CFC 8 B2 d 8 178 C3 C5 DD "； var s = document . getelementsbytagname(" script ")[0]； s.parentNode.insertBefore(hm，s)； })();