【正文】 d security requirements(7)Interface Requirements(8)Design constraint, , the data analysis system requirements(1)to build conceptual models:(2)image depicts the data structure and standardized data structure 3, the logical model derived 4, to amend the plan: the revaluation cost, schedule, , the prototype system to verify the correctness and the system meets the requirements.● requirements analysis principles:(1)must be able to express and understand the problem of data fields and function fields。Coding and unit testing。Overall(summary)design。Feasibility study。s operation and use of documents.● Software features:(1)software is a logical entity, rather than specific physical entity, so it has the abstract.(2)software is the people39。ve learning method is used to only focus on the code, rather than on theoretical knowledge as well as programming ideas ,and the program39。第一篇：軟件工程總結(jié)2As early as when I chose the software professional , I always think of software engineering is nothing but the code to from the process of code to realize the meaning and use all the code in software have always been a hard knock code to learn software development when haven39。t learning of software engineering ,I feel I39。s knowledge of software engineering point of this course summary as below : ● Software: Software is able to plete the intended function and performance of the executable puter program and the procedures required for the normal execution of data, coupled with the program39。s intelligence activities, the knowledge and technology transform into a product of information.(3)After software transform into the product, its production simply copy different from the hardware manufacturer.(4)the maintenance process more plex than hardware, and even lead to new errors.● Software crisis: refers to the process of software development and maintenance of a range of serious problems of a software crisis:(1)The sharp increase in software maintenance costs, a direct threat to the expansion of puter applications.(2)software production technology progress is slow.● Software Engineering: a guiding engineering disciplines of development and maintenance of puter software.● Software life cycle: from definition to a software development, use and maintain, until finallybeing abandoned, to undergo a long period of time, usually the software through this long period of time known as the life life cycle can be divided into the following stages: Problem Definition。Demand Analysis。Detailed design。Integrated Test。(2)by topdown, layer by layer deposition of the problem。s logical and physical views.● ● Requirements definition: A plete listing of everything the customer wants to Requirements specification: Restates the requirements as a specification of how the proposed achieve ,describing the entities in the environment where the system will be shall behave.● Software design task: to produce the software requirements analysis phase into a description of methods of representation with the appropriate software design matter what kind of software design, software design generally includes data design, architecture design, interface design and process design and so on.● Structured design methods: a streamoriented design methods, the central task is to use the DFD diagram shows the system model into a software architecture model to determine the software architecture and interfaces.● Data stream type: Data floworiented design methods to map the flow of information into a software architecture, information flow type determines the mapping flow has the following two types: transformation flow and transaction flow.● Structured analysis methods: Module: It is a entity with clearly defined input, output and physical characteristics of the input modules are essential to achieve the function, all outputs are generated : the program is divided into several modules, each module has a subfunction, these modules lumped together to form a whole, can plete the assigned functions, to achieve the requirements of the design: the largescale software in accordance with the principles laid divided into a smaller , relatively independent but interrelated and module independence, is the modular design of the important guiding : that is, characteristics of the nature of things out not to consider them in Hiding: The information contained in the module does not allow other modules do not need to call independence: the software system software requirements for each module involves only the specific subfunctions, while the rest of the system and software modules interface is : mark a module with all elements of the close of each : a software architecture is the interconnection between various modules within the measure of the : that software architecture to control the number of layers, it can often mark a system roughly the size and : within the structure of the software module on the same level of maximum : a module direct control(call)number of modules, fanout is too large means that the module is too plex, fanout is too small(for example, is always 1)is not : the number of higher level modules that directly call it, the greater the share of the fan module, the more the higher number of modules, which is good.● We can measure coupling along a range of dependence● The basic principles of software design: Modular。information hiding。s functionality to design test static analysis and dynamic 。adaptive maintenance。preventive maintenance.● Software maintainability: measure of the ease of software maintenance of a software said, depends on the maintainability of software the following properties: intelligibility, modifiability and testability.● Software configuration: Software life cycle, its various forms, various versions of the documentation and procedures in general.● Software Reengineering: reverse engineering, restructuring and other technology, a full understanding of the original software, based on the depos