软工导论分类整理

Click on the tags to get quick access to each part of the document.Arguments Definitions Comparisons•The nature of software applications can be characterized by their information content and determinacy.•The Linear Sequential Model is a reasonable approach when requirements are well defined.•The Prototyping Model is a useful approach when a customer cannot define requirements clearly•The Rapid Application Development Model is a high speed adaption of Linear Sequential Model.•The Increment Model is a good approach when a working core product is required quickly.•The Spiral Model includes project risks evaluation during each iteration. •Evaluation Model is considered the best approach because:•Timeline for developer modern software is getting shorter •Customers are more diverse•Changes to requirements happens more frequently (before delivery)•EM accommodates uncertainty better•EM allows delivery of partial solutions•EM reflects what really happens when complex systems are built•One of the most difficult parts of software requirement analysis is ensuring the developer understands what his customer needs. •Information flow represents the manner in which data change as each moves through the system.•Two types of problem partitioning in the requirement analysis are: horizontal and vertical•Views that are considered in software requirement analysis are: essential view and implementation view. EV should be the first to consider.•The state-transition diagram indicates how the system behaves as a consequence of external events.•A single word to summarize software design is "Quality".•The characteristic of a good design is that it implements all requirements in the analysis model.•The control hierarchy represents the organization of modules. •Software procedure focuses on processing details of each module individually.•To achieve high modularity of software components you need low coupling and high cohesion.•The relationships shown in a data model must be classified to show their cardinality and modality.•For purposes of behavior modeling, a state is an observable mode of behavior.•Data dictionary contains description of each software data objects.•In transition mapping, the first level factoring results in the derivation of the control hierarchy.•The implementers of the system create a system image.•A decision table is a graphical notation for depicting procedural detail. •Decision tables are used when a complex set of conditions and actions appears in a component.•A Programming Design Language (PDL) is a combination of programming constructs and narrative text.•The objective for software testing is to uncover errors.•One thing that black-box testing misses and white-box testing uncovers is the subtle logic errors.•Black-box testing categories: incorrect or missing functions, interface error, and performance errors.•Advantages of top-down integration testing: major decision points are tested early.Arguments Definitions Comparisons•Software is•instructions that when executed provides desired functions andperformances;•data structures that enables the programs to adequately manipulateinformation;•documents that describe the operation and use of the program.•Software crisis alludes to a set of problems encountered in the development and maintenance of computer software.•Existing software myths are:•Management myths•Customer myths•Practitioner's myths•Software engineering layers are:•Tools•Methods•Process•A quality focus•Generic phases of software engineering are:•Definition•Development•Maintenance•Cyclomatic Complexity is:•a software metric that provides a quantitative measure of the logicalcomplexity of a program•when used in the context of the basis path testing method, the valuecomputed for cyclomatic complexity defines the number of independent paths in the basis set of a program and provides us with an upper boundfor the number of tests that must be conducted to ensure that ll statement have been executed at least once.•Cyclomatic Complexity is computed in three ways:•The number of region of the flow graph correspond to the cyclomaticcomplexity;•Cyclomatic complexity, V(G) for a graph G is defined as V(G) = E - N + 2, where E is the number of flow graph edges and N is the number offlow graph nodes;•Cyclomatic complexity, V(G) for a graph G is defined as V(G) = P + 1, where P is the number of predicate nodes contained in the flow graph G. •Cohesion is a measurement of the relative functional strength of a module. •Coupling is a measurement of the relative interdependence among modules. •Cohesion is a qualitative indication of the degree to which a module focuses on just one thing•Coupling is a qualitative indication of the degree to which a module is connected to other modules and the outside world.•Modularity is the single attribute of softwares that allows a program to be intellectually manageable.•Levels of capability maturity model:•Initial•Repeatable•Defined•Managed•Optimizing•The software architecture of a program or computing system is•the structures of the system, which comprise software components•the externally visible properties of those components•the relationships among them•Unit Testing is the process of testing each software component individually using stub and/or drivers;•Prototyping Model description:•Developers and customers meet and define the overall objectives andidentify the requirements;•The Quick Design occurs, constructing the prototype;•The prototype gets evaluated by the customer and used to refinerequirements;•Iteration occurs and the prototype should be tuned into satisfy thecustomer's needs.•Three requirements Quality Function Deployment identifies: •Normal requirements•Expected requirements•Exciting requirements•Five phases of software requirement analysis•Problem recognition•Evaluation and synthesis•Modeling•Specification•Review•Basic guideline for FAST:•A meeting is conducted at a neutral site•Rules for preparation and participation are established•An agenda suggested that is formal enough to cover all important points and informal enough to encourage the free flow of ideas.•A facilitator that controls the meeting•A definition mechanism is used•Characteristics that all Design Methods would have:•A mechanism for the translation of analysis model into a designrepresentation;•A notation for representing functional functional components and their interfaces;•Heuristics for refinement and partitioning•Guidelines for quality assessment.•Concerns of design model:•Data•Architecture•Interfaces•Components•Four design models required for a complete specification of a design:•Data design•Architecture design•Interface design•Component-level design•The three interrelated pieces of information in data model•Data objects•Attributes•Relationships•Three primary objectives of the analysis model:•To describe what the customer requires•To establish a basis for the creation of a software design•To define a set of requirements that can be validated once the software is built•Data modeling elements represented in ER-D?•Data objects: any entity producing or consuming information •Attributes: data characteristics associated with a data object instance •Relationships: indicate manner in which data objects are connected•Elements in Analysis Model•Data dictionary•Entity-Relationships Diagram•Data Flow Diagram•State-Transition Diagram•Three characteristics that can serve as guidelines to evaluate design quality •Must implement all of the explicit requirements contained in the analysis model•Must be readable and understandable•Should provide a complete picture of the software•Three golden rules for user interface design•Place the user in control•Reduce the user's memory load•Make the interface consistent•Framework activities during UI development process•User, task and environmental analysis•Interface design•Interface construction•Interface validation•Four interface design issues•System response time•User help facilities•Error information handling•Command labeling•Three fundamental structured programming construct•Sequence•Condition•Repetition•Box Diagram characteristics•Functional domain is well defined and clearly visible as a pictorialrepresentation•Arbitrary transfer of control is impossible•The scope of local and/or global data can be easily determined •Recursion is easy to represent•Decision table is divided into four sections•The upper left-hand quadrant contains a list of all conditions•The lower left-hand quadrant contains a list of all actions that are possible based on combinations of conditions•The right-hand quadrants form a matrix that indicates conditioncombinations and the corresponding actions that will occur for a specific combination•Program Design Language advantages•Provides a fixed syntax of keywords•A free syntax of natural language that describes processing features •Data declaration facilities should be included•Sub-program definition and calling techniques that support various modes of interface description•Software testing order•Unit•Integration•Validation•System•Approaches to debugging•Backtracking•Brute force•Cause elimination•Four types of system tests•Recovery testing•Security testing•Stress testing •Performance testingArguments Definitions Comparisons•Software vs. hardware•Software is developed and engineered, not manufactured in the classical sense;•Softwares don't "wear out". They deteriorate;•Although software industry is tending to be component-based assembly, most of the softwares continue to be custom built.•Transaction center vs. transform center•Transaction Center converts an external information flow into one ofmany action paths inside the system•Transform Center maps the incoming external information intooutgoing external would information•Black-box testing vs white-box testing•Black-box testing involves testing the functionality of a softwarecomponent without knowing the details of its internal logic;•White-box testing involves testing the independent logic paths with fullimplementation knowledge.•Validation testing goals vs. acceptance testing goals•In validation testing, the test team seeks to ensure that each softwarefunction or performance characteristic conforms to its specification;•In acceptance testing, the test team needs to ensure that the softwareworks correctly for the intended user in his or her normal workenvironment.。