software engineering error prone questions

Component-based software development emphasizes the use of reusable software "components" to design and build software systems, conduct qualification checks on required components, (C), and integrate them into new systems.
A. Scale measurement B. Data verification C. Adaptive modification D. Correctness test

Analysis of
component-based software development mainly emphasizes the reuse of existing software "components" when building a software system.Conformity inspection, adaptation and then integration into the new system。
The Unified Process Model is a "use-case and risk-driven, architecture-centric, iterative and incremental" development process that defines the different phases and their artifacts, with the Elaboration phase focusing on (B).
A. Initial activities of the project B. Requirements analysis and architecture evolution C. System construction, generation of implementation models D. Work on software submission, generation of software increments

The initial phase of analysis focuses onProject start-up activities. After the initial domain scope is understood in the elaboration phase , theRequirements Analysis and Architecture Evolution. build phase focussystem construction, resulting in a realization model. The handover phase focuses on the work on software delivery,generate software increments. The build phase runs the software andOngoing use of monitoring software, provide support for the operating environment, submit and evaluate defect reports and change requests.
If user requirements are not clear and often change, but the system scale is not too large and not too complex, then the (C) development method is most suitable. For problems in the field of data processing, if the system scale is not too large and not too complex, the requirements If the change is not large, the (/) development method is most suitable.
A, structured B, Jackson C, prototyping D, object-oriented

The prototyping method is most suitable when the analysis
requirements are not clear and the scale is not too large , and the less complex software in the field of data processing is suitable for development by the structured method .
A project team intends to develop a large-scale system, and has experience in related fields and similar-scale system development. Among the following process models, () is the most suitable for developing this project.
A. Prototype model B. Waterfall model C. V model D. Spiral model

The analysis
waterfall model is to specify the activities of the software life cycle as the basislinear orderA model of several stages connected, suitable for softwareneeds are clearsoftware project.
The V model is an evolution model of the waterfall model, which willtesting and analysisConducted in association with design, enhancedAnalysis and Designverification.
The prototype model is an evolutionary model, throughquick buildrunnable prototype system, and then according to the running processFeedback from users obtainedMake improvements.
Evolutionary models are particularly useful for softwareLack of demandAccurately know the situation.
The spiral model combines the waterfall model and the evolutionary model, addingRisk Analysis。
A software development process describes "who does it", "what to do", "how to do it" and "when to do it". RUP uses () to express "who does it".
A, role B, activity C, product D, workflow

Analyzing that
RUP has applied four important model elements of role, activity, artifact and workflow, in which the role expression "who does", product description"do what", activity statement "How to do it", workflow expression "when to do it”
The activity diagram of a software project is shown in the figure below, where the vertices represent the project milestones, the edges connecting the vertices represent the activities involved, and the numbers on the edges represent the duration of the activities (days), then the minimum time to complete the project is () days . Activity BD can be started late (/) days at most without affecting the overall project schedule.
A, 15 B, 21 C, 22 D, 24

Analyzing
the critical path is the longest path in the project plan . In layman’s terms, because the critical path is the longest, only when it is completed can the project be completed, so it is the most “critical”.
Activity diagram is a model that describes the interdependence of various work tasks in a project. Many important characteristics of the project can be obtained by analyzing the activity diagram, such as estimating project completion time, calculating critical paths and key activities , etc. According to the above figure, the critical path is calculated asABDGlKL, whose length is 22, the activities on the critical path arekey activity. The active BD is on the critical path, so the slack time is 0.
An activity diagram for a software project is shown below. The vertices in the graph multiple-choice question represent the project milestones, and the edges connecting the vertices represent the included activities, then the milestone (D) is on the critical path, and the relaxation time of the activity FG is (B).
A, 19 B, 20 C, 21 D, 24

Analysis
The earliest start time of active FG is day 18 and the latest start time is day 38, so the slack time is 20 days.
Scheduling using PERT diagrams, which cannot be clearly described (Parallelism between tasks), but it can be given which tasks are completed before other tasks can be started
"The software product must be able to respond to user requests within 3 seconds" belongs to (B) in the software requirements.
A. Functional requirements B. Non-functional requirements C. Design constraints D. Logical requirements

Analysis
Software requirements are the things that a software system must accomplish and the qualities it must possess. Software requirements includeFunctional Requirements, Non-Functional Requirements, and Design Constraintscontent in three aspects. Functional requirements are the functions that the developed software must have: non-functional requirements refer to the attributes or qualities that the product must have, such as reliability, performance, response time and scalability, etc.; design constraints usually impose some constraints on the solution illustrate. "Software products must be able to respond to user requests within 3 seconds" mainly expresses the response time of the software, which is a non-functional requirement.
() The software cost estimation model is a static univariate model for estimating the entire software system.
A. Putnam B. Basic COCOMO C. Intermediate COCOMO D. Detailed COCOMO

Analysis of
the basic model (Basic Model): is astatic univariate model, which calculates the software development effort as a function of the estimated lines of source code (LOC) as an argument. Intermediate Model : On the basis of calculating the software development workload with LOC as the function of the independent variable,Reuse involves products, hardware, people, projectsThe influence factors of other attributes are used to adjust the estimation of workload. Detailed Model (Detailed Model): includes all the characteristics of the intermediate COCOMO type, but when adjusting the workload estimation with the above-mentioned various influencing factors, it is also necessary to consider the impact on the software engineering process.analysis, designeffects of each step.
Software risk generally includes (C) two characteristics.
A. Firefighting and crisis management B. Known and unknown risks C. Uncertainty and losses D. Staff and budget

Analysis
Software risk generally includes two characteristics of uncertainty and loss , where uncertainty means that the risk may or may not occur; loss is the undesired consequence and loss that will be caused when the risk does occur. Firefighting and crisis management are unsuitable but frequently employed software risk management strategies. Known and unknown risks are one way of categorizing software risks. Staff and budget are factors that need to be identified when identifying project risks.
Risk prediction evaluates risk from two aspects, namely, the possibility of multiple-choice risk occurrence and (D).
A. The cause of the risk B. Risk monitoring technology C. Can the risk be eliminated D. The consequences of the risk

Analyzing
Risk Prediction from Risk OccurrenceLikelihoodand the riskconsequencesWhether it is serious or not, the risk is assessed in two aspects.
In the following statement about the Gantt chart of the schedule management tool, (D) is incorrect.
A. Can clearly express the start time, end time and duration of each task
B. Can clearly express the parallel relationship between tasks
C. Can not clearly determine the dependencies between tasks
D. Can clearly determine the impact on progress key tasks of

An analysis
Gantt chart is a simple horizontal bar chart that depicts project tasks relative to a calendar. The horizontal axis represents the calendar timeline, such as day, week and month, etc. Each bar represents a task, and the task names are listed vertically in the left column. The starting point and end point of the horizontal bar in the figure correspond to the time on the horizontal axis, respectively. Indicates the start time and end time of the task, and the length of the horizontal bar indicates the duration of the task. When multiple horizontal bars exist for the same time period in the calendar, it indicates concurrency between tasks. Gantt diagram can clearly describe each taskWhen does it start and when does it end, the progress of the task, andParallelism between tasks. But it does not clearly reflect the relationship between tasksdependencies, it is difficult to determine the key points of the whole project, nor can it reflect the potential part of the plan .
If the software project team adopts an active risk control method, (A) is the best risk control strategy.
A. Risk avoidance B. Risk monitoring C. Risk elimination D. Risk management and contingency planning

analyze
risk avoidancegive upor notloss-making activitiesor work. For example, to avoid the risk of flooding, factories can be built on higher ground with good drainage, which is a proactive risk control method. Risk monitoring refers to the monitoring of risks during the operation of the decision-making body.Full monitoring of development and changes, and adjust coping strategies as needed. Risk management refers to the affirmativeMinimize risk in risky environmentsmanagement process. We can transfer and avoid risks, but we cannot eliminate them .
In the hierarchical structure of the workload estimation model COCOMOⅢ, the estimation option does not include ().
A. Object point B. Function point C. Number of use cases D. Source code lines

Analyzing
the COCOMOI model also requires the use of size estimation information. There are three different size estimation options in the model hierarchy, namely:Object Points, Function Points, and Lines of Code。
Risks are usually prioritized according to ( ).
A. Risk impact B. Risk probability C. Risk exposure D. Risk control

Analysis
Risk is an unwanted event with negative consequences. Risk management is an important task of software project management. When carrying out risk management, the risk control strategy is determined according to the priority of the risk, and the priority is determined according to the risk exposure. risk exposure is aMetrics to Quantify Risk Impact,equalrisk impact multiplied by risk probability, the risk impact is the loss caused when the risk occurs. Risk probability is the likelihood of a risk occurring. Risk control is an important activity of risk management.
Among the requirements of an enterprise's financial system, the functional requirements are (A).
A. Employee salaries are paid at a specific time every month.
B. The response time of the system does not exceed 3 seconds.
C. The calculation accuracy of the system meets the requirements of financial rules
. D. The system allows 100 users and colleagues to query their own salaries.

Analysis
Software requirements include functional requirements and non-functional requirements . Functional requirements describe the required behavior in terms of required activities. It is a functional requirement to pay employees' wages at a specific time every month. The system's performance requirement is that the response time of the system should not exceed 3 seconds. The accuracy of the system's calculation accuracy meets the requirements of financial rules . The system can allow 100 users and colleagues to query themselves The salary is a performance requirement.

software engineering error prone questions

software engineering error prone questions

Guess you like