Soft-tasking (a): self-introduction + 5 Q soft work

Self introduction


   Hello, I'm Jike (5) classes Zheng Jinhuai.

  Since the freshman sophomore detours, leading to now there is no clear technological direction. But, fortunately he participated in a teacher's project on "visual Q & A" in the field during the second year. There are teacher pointing, really a lot easier than his own trial and error. Today, looking at the students around, a two, three, four project experience, while spring and autumn trick move slowly approaching, the heart can not help but feel anxious.

  Anyway, the purpose of writing blog: In addition to technical review their knowledge, but also people who want to see the article be harvested. So today it seems borrowed recently from the book's words and encourage one another: "Your Story May not have have SUCH A Happy Beginning, But does not that you are the make the WHO It IS at The REST of your Story, the WHO you the Choose to BE. . " ( the beginning of your life story might not be happy, but this does not affect what kind of person you become. later in life the key way, how you choose to go.)

 

5 Q soft work:


  1. How will knowledge of software engineering classes learn to apply to the actual development process, in which what needs to be done?
  2. How to write a needs analysis documents, to avoid the demand of Party A and Party B project deviation?
  3. Less formal methods and formal methods What is the difference, whether in the development process have to use formal methods?
  4. Software engineering module independence is important, how to measure modules of high cohesion, low coupling?
  5. Whether the software unit testing just from module interface, local data structure, it is important to perform path, pathway and error handling the boundary conditions set out five areas that would be sufficient, or the need to consider something more?

Guess you like

Origin www.cnblogs.com/jinhuai/p/11493273.html