Project Summary (i) Seven cases of crime

Most of the night to this summary, heart mixed with a variety of moods, ups and downs, so far, the whole project has finally ended, for such a can be and eight after eating potato chips, to see the film can be completed project, and finally evolved into a January consecutive overtime 105 hours of projects, have their own experience, also has the ability insufficient, writes down such a summary, lets oneself sink down the heart to reflect in the oneself's foot and the insufficiency, also hoped everybody may draw lessons from and the discussion.

First, project background:

I have a year work experience small rookie, colleague four years work experience, settled into the customer office three months development cycle ...

Second, Project introduction:

The common Office system, combined with workflow, unfortunately I did not see one of the highlights is what the content, has always thought that such a random treatment, nothing more than change check, add the form, their own definition of some common work classes to deal with it, Ok, that a tragedy version

Function Point example: fault-related, can complete the application of fault orders, the processing of fault orders, failure orders closed.

such as the failure to apply the page (breakdown) (a crime: the mindset), nothing more than doing it:

Add.aspx-> Failure Request page, complete the new contents of the fault list

Update.aspx-> Failure Single Status change page, complete the status of the fault order changes.

Close.aspx-> The process end of the fault single State, completing the life cycle of the failure order.

A page of various actions corresponding to the processing of Jane on it, colleagues do this, how simple, it seems that I eat potato chips, look at the raw material, do not have to work overtime, you can put this project lightly loose copy edit processing can be done, OK, take out the code generator, you are not five function points, solid layer, Write a content, directly design five tables, a smooth processing, the following months can play the past, think of a little excited look.

And colleagues assigned anything after the one weeks passed ....

Just as happily submitting the code, I was thinking about where to go to the movies tonight, customer business people came to ask the situation, I immediately and colleagues le Le Ha's demo code, business staff exclaim, wow, you write code speed is so fast, worthy of experienced personnel, but, I have to have different characters from this fault list to deal with, not anyone can do it. I had a cold sweat--!, at that time did not consider this question (a sin: self-righteous. Or I'll show you the new features when I'm done.

Five function points, the status of various documents corresponding to the role of the person, the process of processing is different, that the corresponding change in the code is ^&*&&*#@$_%$ () ..., at that time only thought is to change the code, we division of labor and one weeks past, Ok, The change is finished, I hard code, nothing more than if else more processing. (A sin: no repentance.) That's the end of the deal.

Finally can give the business sister demo, then the presentation of the appearance I was like this:

A process followed by a demonstration of the process,

Suddenly business sister raised a question, Yi, you These processes are written well, if the middle if the process of change

And then my mood turned out like this.

This one....... Brainwave, it seems that the previous cascade operation can be achieved through the operation of the node, through the next node, the next node can reach the cycle of processing, oh yeah~~~~~ is simply a form design to deal with this process changes. (A sin: not flexible)

----------------------------------------------------------------------------------in hard code coding