Recently students often find my chat, I hope that they indicate the direction, the problem I do not banker, and they just say that my learning process, much more to say, feel the need to write it down. Although the history of relatively ordinary, but maybe allow them to inspire, to me, it is a natural growth record.
Start junior year to start learning "software engineering", to teach us clearly remember Dr. just returned to the US, and later he became the school's leading university, when he took our "Discrete Mathematics" teaching him personally impressed, but he granted the course, I just remember the "waterfall model" and his teaching in English, and even exam papers are also in English.
Hung up during the first junior college exam, so to stay in the school summer holidays, a little frustrating, but it feels particularly fortunate college he began the project team to implement the system, I successfully use this time to participate in a great influence on my development group, met my instructor far-reaching impact, he did not talk much, just schedule tasks, inspection tasks, organizational learning, of course, concerned about our growth. Now, I have a little book record when his arrangements, he told us to find a job safety. Since I was in the first group of students through the CET, it is natural to become a leader, naturally take on more tasks, while beginning to learn how to assign tasks to team members, collect feedback, test results, provide guidance to students, I I want these to become a teacher later laid the foundation.
At that time, we have developed the project "Lake Hengyang campus teaching financial management system," the scene is impressive: a teacher from a customer that came back, took out a thick tread certificate class form, so we began a long drawn "data window" work. Then use the tools of Sybase, Inc. PowerBuild, but now, PB has become history.
In this project, I am familiar with the "data window", "SQL statements" and with "messagebox" for debugging, but also independently undertake the help documentation to make the whole system work personally think that fairly well, making this part of the document to help guide The teacher let me follow directly supervised learning school girl. The instructor will offer me a thesis topic is about "component-based software reuse," At that time, I was responsible for "progress bar" reuse, Yes, that program took too long to prevent the progress of the user closes the application article. Now, I almost forget that time graduated from the design, but I remember the "component-based software reuse," the words, this time, I still do not know and software engineering have much of a relationship.
Talking really started to feel the soft work, it should be in graduate school, tutor of companies involved in the project process. To participate in this project as very lucky, waiting time is allocated relatively short, at the beginning will be able to follow the domain knowledge is very rich, very full experience in project development project manager needs to start doing research, we stayed together for two months, and the user side, user is monopoly, a colleague of their information department every day, and we work together, but basically he is playing the game the way we answer the questions and arrangements meet business meeting, and we are always busy break. Remember, every morning I was always the first to the office, while finishing the task of the day before yesterday, while we wait, the project manager will usually start the day after ten minutes discussing the stock market and the morning news, morning time basically everyone discuss, as the only female project, discussion and understanding of their natural work record undertaken by me, of course I am also happy to undertake this work makes me a more profound understanding for rational article, let me become more familiar with the company's business. During the noon lunch break, I began to organize the morning session, in order to facilitate the afternoon we can work separately as I began to sort out, although very hard, but very fulfilling, meaningful, so let's do lunch because waste a lot of time to repeat the discussion . Two months, we completed the business of making all prototypes, needs confirmation participated in two meetings, since I began to recall knowledge learned to work when soft starting college, I began to realize: the original, the university seriously study the contents, will impress in my mind, but, in my mind they are one by one point, the actual project development is the increase they are extracted, the possibility of being combined, and once extracted, combined, extracted again the possibility will be greatly improved; originally, I was going through a needs analysis; originally, the company developed software also has many forms: when the company is planning to buy a secondary development of software to be a give users, who knows mention the basket is not easy, ultimately reinvent the wheel, time, cost and human resources are wasted, and good stop in time, so we appeared; the original understanding of the business processes, but also familiar with the field of knowledge, but also very important, if we can take advantage of domain knowledge of business process reengineering overtaken information it is also very good; the original, we painted all the figures And is used to confirm user requirements, it can be regarded as a prototype model; originally, the waterfall model document-driven mentioned, in fact, is very helpful for beginners.
After the requirements analysis, returned to the company, the project manager took us to complete the design of the database, and require departments to do the UI interface design, his work is handed over to the project manager, project manager left me with the impression that: rigorous , conscientiously, with the typical image of programmers. From him, I saw the work breakdown structure and Gantt charts, schedules and our arrangements, he arranged to complete the task every day, checkin configuration repository, written daily, I felt enriched abnormal, I found I did not have time to think any other problems, including a feeling I was not needed. From him, I have found that writing code is a set of specifications within, and he adjusted the code is looked particularly uncomfortable, partly because of this, he was demanding for us, the members of the project team called the most feared by his name, this means that a meal swearword. With the door around me, a boy, after each was called, will flick the body, it can be more shake, more often called to. Fortunately, I have not been scolded, although I'm afraid, but I fear the rigorous transformation in the code of the code.
This project uses .net technology, the development of which lasted nearly a year, and today still maintain use. When I left for personal reasons, the project has not completely finished, although members of the project team flow is normal, but to ensure that the work of the project, I made an application one month in advance, recording the presence of all my unfinished task questions to the project manager, he was very pleased, and very easy to let me leave. By now, over the past ten years, he still remember me, I want to share when leaving EIR should play little role.
This, I began to realize that software engineering is a system work, as if touched a little edge, but does not seem to.
Unconsciously, I wrote a lot, but there are many not finished, of course, far from the finish of the day, this is just the beginning, the follow-up will continue to record ......