软件需求分析复习总结

一.名词解释

1．Requirements Management

Ans: A systematic approach to eliciting,documenting,organizing,and tracking changing requirements(Ensuring that your team identifies,builds,tests and documents the right system for your customer)

2．Root causes analysis

Ans: basic and contributing causes are discovered in a process similar to diagnosis of disease.

3．R equirements elicitation

Ans:Sometimes called requirements discovery,involves technical staff working with customers to find out about the application domain, the services that the system should provide and the system‟s operational constraints,and stakeholders.

4．R equirements Workshop

Ans:Gather all key stakeholders together for a short but intensely focused period,using an outside facilitator,brainstorming and Idea reduction and listing of possible features and attributes.

5．Domain Model

Ans:Domain model may be considered a visual dictionary of the noteworthy abstractions, domain vocabulary and information content of the domain.

6．High quality software

Ans: A software is good if it meets customers expectations:it is (at least) correct, reliable, maintainable, user-friendly ;the total cost it incurs over all phases of its life cycle is minimal.

7．Requirements classification

Ans:Functional requirements;Nonfunctional requirements;Design constraints. 8．R equirements baseline

Ans:The itemized set of features intented to be delivered in a specific version of the application.

二.简答题

1．L ist the six team skills of requirements management.

Ans: Analyzing the Problem.Team;Understanding User Needs.Team ;Defining the System; Managing Scope;Refining the System Definition;Building the Right System. 2．Describe the differences among user‟s Needs, Features and Requirements.

Ans: Needs are a service the system provides to fulfill one or more user needs; Features are A reflection of the business, personal, or operational problem that must be addressed in order to justify the use of a new system;

3．Describe the differences and relations between Domain Model and Class Diagram.

Ans:Domain model may be considered a visual dictionary of the noteworthy abstractions, domain vocabulary and information content of the domain, Domain mode is a representation of real-world conceptual classes,not of software components;A class diagram shows the existence of classes and their relationships in the logical view of a system.UML modeling elements in class diagrams:Classes and their structure and behavior;Association, aggregation, dependency, and inheritance