现代软件工程2014年期中考试参考答案.doc

现代软件工程2014年期中考试参考答案一. abbcd babde ccadd cbccd 二. 1. software engineering: The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software; that is, the application of engineering to software. (2) The study of approaches as in (1).2. The principle of information hiding implies that modules only share information with each other on a need to know basis to achieve some specific software function. Hiding enforces the procedural constraints to both the module procedural detail and any data structures local to the module.3. Inception phase (customer communication, planning, use-case creation)Elaboration phase (creation of analysis and design models)Construction phase (translates design model into software components)Transition phase (software transferred from developer to end user for acceptance testing)Production (on-going monitoring and support of software during active use) 4. Capacity Maturity Model Integration (CMMI)The CMMI assesses each process area against specific goals and practices and rates each one in six capability levels. They are: Level 0: Incomplete, Level 1: Performed, Level 2: Managed, Level 3: Defined, Level 4: Quantitatively managed. Level 5: Optimized.5. Software Architecture: the structure or structures of the system, which comprise software components, the externally visible properties of those components, and the relationships among them.三. 1. Software is developed, not manufactured. Software does not wear out, but it can deteriorate when changes are made. Most software is custom built, not assembled out of components.2. The pros and cons of prototyping model are: Pro: evaluated by user and used to refine requirements; Con: the first system built is barely usable; unrealistic expectations from the customer; the performance issueThe spiral model combines the iterative nature of prototyping with the systematic control found in the linear sequential model 3. The waterfall model is appropriate for projects with the following characteristics: (1) the problem is well understood (requirements are well-defined); (2) the delivery date is realistic; (3) its unlikely that major changes in requirements will be requested as the project proceeds. Otherwise, waterfall model cannot be used. 4.Inception: establish a basic understanding of the problem, the people who want a solution, the nature of the solution that is desired, and the effectiveness of preliminary communication and collaboration between the other stakeholders and the software team.Elicitation: elicit the requirements from all stakeholders. Elaboration: create an analysis model that identifies data, function, and behavioral requirements. Negotiation: agree on a deliverable system that is realistic for developers and customers.Specification: create a document to specify the detailed description of all aspects of the software to be built before the project is to commence.Requirements validation: examine the specification looking for errors in content or interpretation, areas where clarification may be required, missing information, inconsistencies, conflicting requirements, or unrealistic requirements.5.Class name identifies the data object uniquely.Responsibilities are the attributes and operations for the class.Collaborators are those classes required to provide a class with information needed to complete a responsibility.四1. The UML is the standard language for visualizing, specifying, constructing, and documenting the artifacts of a software intensive system.The following UML diagrams are useful for analysis modeling .Use-case diagram: a collection of user scenarios that describe the thread of usage of a system.Activity diagram: a diagram to supplement the use case by providing a graphical representation of the flow of interaction within a specific scenario.Class diagram: a type of static structure diagram that describes the structure of a system by showing the systems classes, their attributes, operations (or methods), and the relationships among objects.State diagram: a diagram to represent active states for each class and the events