市场营销计划书.doc

Thinking of Software EngineeringThe course named software engineering theory and practice provide a general introduction to software development and identify the important phases of any software project.For the time is limited and content in this book will be learned in other courses,we only learned three chapters of this book. Chapter one provides a general introduction to the field in order to give some sense of the magnitude and importance of software in todays world, the kinds of problems that make software development difficult, and an outline of how software development is undertaken. Chapter two provides more detail on the idea of a “software process”, that is, on the various stages software goes through, from the planning stages to its delivery to the customer and beyond. Different models of the process are introduced, and the types of project features for which each is most appropriate are discussed. Chapter four details how the problem to be solved by the system is defined. This chapter concentrates on the methods that are necessary to fully capture the customers requirements for the system, and how to specify them in a way that will be useful for future needs. Once the problem is sufficiently well understood, the system that solves it can be designed.After I learned these three chapters, I have been aware of software engineering in a certain extent.By learning the chapter one , I recognised the differences between computer science and software engineering and the characteristics of “good software”. In addition, I know what is a software engineer, what is meant by a systems approach to building software and understand why a systems approach is important. Software engineers use their knowledge of computers and computing to help solve problems. For problem-solving, software engineering makes use of analysis and synthesis. Software engineers begin investigating a problem by analyzing it, breaking it into pieces that are easier to deal with and understand. Once a problem is analyzed, a solution is synthesized based on the analysis of the pieces. To help solve problems, software engineers employ a variety of methods, tools, procedures and paradigms. It is meaningful for me to learn this chapter because the knowledge I have learned give me a outline of software engineering. From chapter two , I saw an overview of different types of process and life- cycle models. Besides , I acquainted several modeling techniques and tools as well as how organizing process activities can make development more effective. A process is a series of steps involving activities, constraints and resources that produce an intended output of some kind. A process usually involves a set of tools and techniques. Processes are important because they impose consistency and structure on a set of activities.At last ,I studied chapter four , I know it is necessary to elicit requirements from software customers, and the role of requirements in the software life-cycle as well as the types of requirements that should be included in a requirements document. And I realized it is important to remember that the purpose of requirements is to specify the problem that the system is intended to solve, leaving the details of the solution to the system designers.As far as I am concerned,the chapter two gave me a great impression ,especically the extreme programming (XP).The xp has twelve facets.(1) whole team, include on site user and coach. (2) planning game. (3) metaphor. (4) small releases. (5) testing.(6) simple design. (7) pair programming. (8) design improvement. (9) continuous integration. (10) collective code ownership. (11) coding standard. (12) sustacable pace. In this term , my classmates and I were divided into several groups to complete a small project, so that we can learn through practice how a project can be completed. My three teammates and I use several facets of the method of XP ,such as pair programming,collective code ownership , simple design and collective code ownership. We found a classroom and wrote the original code which include the definition of the class that we need in our programme on the blackboard then we took photos on the code in order to make room for other code. The code was written by the whole team when we were discussing how to design the programme.After discussing ,we started pair programming according to the code on blackboard and photos. Our two people sat in front of one computer, so that one can find the mistake that the other did not realize while coding. After one days work ,we copy all the code to each of our computer to try to continue coding next problem. Before we start coding , we have already agreed on the coding standard.For example,we used Hungarian nomenclature to name variables.As the saying goes knowledge starts with practice.This work was before we learned the XP, so I was very acceptable on the XP. In my opinion , I think the XP is veryuseful while developing a software and the process will be