Chapter One
1. How many processes are defined and divided into software processes?
Definition: A collection of activities, methods, practices, and improvements that people use to develop and maintain software and related products (such as software project plans, design documents, codes, test cases, and user manuals).
Management process, realization process, support process.
2. Three levels of software process definition?
Common software process, organization standard software process, project custom software process.
3. Definition of process specification?
It is a standard that explicitly stipulates or agrees on the process constituted by input/output and activities.
4. What are the main process models?
Software Capability Maturity Model (CMM), Capability Maturity Model Integration (CMMI), Individual Software Process (PSP), Team Software Process (TSP), IBM's Unified Process Management (RUP), Extreme Programming (XP), Microsoft Solutions Framework (MSF).
5. Five views of UML?
User model view, describing event-driven, use case scenarios from the user's perspective.
The structural model view, which analyzes data and functions from the inside of the system, is a static structural model.
Behavioral model view, dynamic collaboration relationship
The performance of the model view, the structure and behavior of the component system environment
Environment model view, showing the structure and behavior of the realized system environment
6. What is the definition of "object"?
It is any concrete or conceptual thing that occurs in the description of the software development process.
7. The definition and advantages of ABM?
Definition: It is a microscopic modeling method that describes a dynamic system acquisition process from details.
advantage:
ABM can catch unexpected phenomena. ABM describes dynamic systems or processes in a natural way. The ABM method is flexible.
Chapter two
1. Software process capability, definition of software process performance?
Software process capability: the inherent ability of the software process itself to produce products according to a predetermined plan. In other words, it is the degree to which the expected results can be achieved by following the software process.
Software process performance: indicates the actual result obtained by following the software process or the actual result of the software process execution.
2. Definition of software process maturity, characteristics of immature process, maturity standard?
Definition: Refers to the extent to which a specific software process is named and well-defined, managed, evaluated, controlled and produced actual results.
The characteristics of the immature process: The software process capability is low, and it is impossible to develop products that satisfy customers according to the predetermined plan. Process performance is invisible. It is difficult to estimate the schedule and budget, and it is difficult to predict the development schedule, cost and product quality. It is not possible to clearly know the standards for entering and leaving each stage of the software process. Passivity of the process, lack of initiative to change.
The standard of maturity: high software process capability. Predictability of software process performance. Standardize the software process. Consistency of the process. Richness, visibility, stability, and ability to develop continuously.
3. The four basic elements of CMM?
(1) Maturity model: It is a properly defined and specific platform aimed at achieving mature software process improvement. Five maturity levels provide the top-level structure of CMM.
(2) Key Process Area (KPA): The maturity level consists of several KPAs.
(3) Key practices: Each KPA is described by several key practices. Describes the infrastructure and activities that contribute the most to the effective implementation and standardization of KPA.
(4) Common characteristics: The key practices are classified into 5 common characteristics. Execution agreement, execution ability, execution activity, measurement and analysis, verification implementation.
4. The five levels of CMM?
Initial level, repeatable level, defined level, quantitative management level, optimization level.
third chapter
1. Execution agreement, definition of execution ability?
Execution agreement: It is the basis of the focus of the organizational process and the actions that the enterprise must take in order to ensure that the process is established and continues to function.
Execution ability: a prerequisite for the organization and project implementation of the software process. Execution ability generally refers to the provision of resources, assignment of responsibilities and personnel training.
2. Organization process definition and purpose, software process wealth definition?
Organizational process definition: refers to the organizational unit responsible for organizing software process activities (such as SEPG, software process group) to define the software process at the organizational level.
The purpose of the organization process: is to develop and maintain a set of software process wealth that is convenient for each project, improve the process characteristics across various projects, and accumulate a long-term useful process foundation for the software organization.
Software process wealth definition: It is important information such as process documents and data used to guide software projects that the organization obtains through accumulation in the software process improvement process.
3. Organization standard software process definition, project definition software process definition, tailoring process, guideline?
Organization standard software process definition: It is composed of some software process elements common to all projects in the defined organization.
Project definition software process definition: refers to the operational definition of the software process used in the project.
Tailoring process: It is used to help the project tailor the organization standard software process to form the project-defined software process.
Guidelines: Choose the life cycle, tailor according to project characteristics, clarify the objects that can be tailored, determine the factors to be considered for tailoring, and decide on tailoring based on risk.
4. What is an individual software process?
It is researched and developed for training well-trained software process engineers. It is used to control, manage, and improve the self-improvement process of personal working methods. It is a structural framework that includes software development forms, guidelines, and procedures.
5. TSP startup process, TSP workflow?
Start-up process: business objectives -> role assignment -> product development strategy -> overall plan -> quality objectives -> phased plan -> risk assessment -> preparation for management review -> management review -> evaluation of the start-up process
Work flow: product requirement description->strategy 1->plan 1->demand 1->design 1->implementation 1->test 1->post-maintenance 1->strategy 2->. . .
Chapter Four
1. Requirements development, requirements management definition?
Demand development: It is the activity process of demand collection, analysis and determination of research and development content for the development of products that meet the needs of users.
Demand management: unified demand confirmation, tracking and change control of the information developed by the demand.
2. Requirements change control process, and precautions?
chapter Five
1. The technical architecture of the software process?
2. The main software process mode?
Object-oriented software development process, component-oriented software development process, agile development process, software development iteration mode, software development parallel mode.
3. Three stages of process problem solving?
(1) The work result of the problem description stage is to propose goals, determine evaluation indicators and constraints.
(2) Analyze the research stage and propose various alternatives and predict the possible results once implemented.
(3) The final evaluation stage is to provide the decision makers with the evaluation and comparison results of each plan as a basis for judgment and choice.
4. What are the functions, differences and connections of verification, confirmation and testing? p115
Chapter 6 Chapter 7
1. Software configuration management definition, configuration definition?
Software configuration management: It is the management of software changes, which belongs to the software engineering process. It usually consists of corresponding tools, processes and methodology.
Configuration: The function or physical attributes of the final software product are clearly stated in the technical documentation. It includes all product features, content and related documents to be controlled.
2. The three most commonly used measurement methods? p134
(1) The code line method loc refers to all executable source code lines, including the deliverable work control language.
(2) Function point analysis method,
(3) Object point method of object-oriented software,
3. What are the important tools for risk identification?
Risk identification: divided into internal risks and external risks
Intrinsic risk: refers to the risks that the project team can control and influence, such as personnel appointment and dismissal and cost estimation.
External risks: Refers to risks beyond the control and influence of the project team, such as market changes and government actions.
Tools: Develop and compile the risk checklist for the project. The advantage of the checklist is to make the risk identification process shorter and faster and improve efficiency.
4. The purpose of the software project plan?
Guide the specific implementation of the project. The plan must be realistic and useful.
5. Work breakdown structure diagram? (WBS) p143
Compile requirements specifications, compile design documents, coding, testing, and acceptance.
6. The content and plan of the software quality policy?
The software quality policy is a document and a binding document that guides project personnel to better carry out software project work.
content:
Plan: A software plan is a specific plan for project quality management to achieve project quality policies and objectives.
The overall process is divided into: plan preparation, implementation, inspection and adjustment, and summary.
The purpose of the quality plan: to ensure that the quality standards of the project can be satisfactorily achieved. The key is to ensure that the project is completed on time during the project planning period, and to deal with the relationship with other project plans.
7. The purpose of the software review, the software review process, and the software review method? p157-159
Purpose: To find the shortcomings of the product during the review, so the investment in the review can reduce a lot of later rework. Through the review, the problem can also be recorded, and the problem is traceable.
process:
method:
8. The definition and best method of defect analysis? p163
Definition: It is necessary to collect defects generated during software development and operation, and classify and summarize the defect information.
The best way: use defect management tools in the software development process.
chapter eight
1. The core idea of IPD? p191 Integrated product development model IPD
(1) Product development is an investment decision.
(2) Innovation and development based on the market.
(3) Collaboration across departments and systems.
(4) Asynchronous development model.
(5) Reuse
(6) Structured process.