某装配整体式单跨简支叠合梁，结构完全对称，计算跨度ι＝5.8m，净跨径ι＝5.8m，采用钢筋混凝土叠合梁和预制板方案，叠合梁截面如图4-2所示，梁宽b＝250mm，预制梁高h＝450mm，b＝500mm，h＝120mm，混凝土采用C30;叠合梁高h＝650mm，叠合层混凝土采用C35。受拉纵向钢筋采用HRB400级,箍筋采用HPB300级钢筋。施工阶段不加支撑。第一阶段预制梁,板及叠合层自重标准值q＝12kN／m，施工阶段活荷载标准值q＝10kN／m;第二阶段，因楼板的面层,吊顶等传给该梁的恒载标准值q＝8kN／m，使用阶段活载标准值q＝12kN／m。取a＝40mm。设计使用年限为50年，结构安全等级为二级。

施工阶段梁的最大内力设计值M(kN·m),V(kN)，与下列何项数值最为接近？

A:M＝119.5;V＝98.6 B:M＝119.5;V＝82.4 C:M＝109.4;V＝98.6 D:M＝109.4;V＝82,4

某一悬臂水池，壁高H＝1.5m，采用MU10烧结普通砖和M7.5水泥砂浆砌筑，如图6-9所示。水的荷载分项系数取1.2。砌体施工质量控制等级为B级，结构安全等级为二级。

试确定池壁底部的受弯承载力验算公式(M≤fW)，其左右端项，与下列何组数值最为接近？

A:6.75kN·m／m＜7.20kN·m／m B:5.63kN·m／m＜9.00kN·m／m C:6.75kN·m／m＜9.00kN·m／m D:5.63kN·m／m＜9.7kN·m／m

某砌体房屋采用墙下钢筋混凝土条形基础，基础尺寸如图6-12所示，墙体作用于基础顶面处的轴心的标准值为：永久作用F＝300kN／m，可变作用F＝136kN／m，其组合值系数为0.7，基底以上基础与土的平均重度为20kN／m。

试问，设计基础底板时采用的基础单位长度的最大剪力设计值V(kN),最大弯矩设计值M(kN·m)，与下列何项数值最为接近？

A:V＝224.3;M＝91.4 B:V＝219.3;M＝89.4 C:V＝224.3;M＝89.4 D:V＝219.3;M＝91.4

The purpose of the requirements definition phase is to produce a clear, complete, consistent, and testable (71) of the technical requirements for the software product.
During the requirements definition phase, the requirements definition team uses an iterative process to expand a broad statement of the system requirements into a complete and detailed specification of each function that the software must perform and each (72) that it must meet. The starting point is usually a set of high-level requirements from the (73) that describe the project or problem.
In either case, the requirements definition team formulates an overall concept for the system and the defines (74) showing how the system will be operated, publishes the system and operation concept documents, and conducts a system concept review (SCR) .
Following the SCR, the team derives (75) requirements for the system from the highlevel requirements and the system operations concept. Using structured or object-oriented analysis, the temn specifies the software functions and algorithms needed to satisfy each detailed requirements.

A:function B:definition C:specification D:statement

The purpose of the requirements definition phase is to produce a clear, complete, consistent, and testable (36) of the technical requirements for the software product.
During the requirements definition phase, the requirements definition team uses an iterative process to expand a broad statement of the system requirements into a complete and detailed specification of each function that the software must perform and each (37) that it must meet. The starting point is usually a set of high-level requirements from the (38) that describe the project or problem.
In either case, the requirements definition team formulates an overall concept for the system and then defines (39) showing how the system will be operated, publishes the system and operations concept document, and conducts a system concept review (SCR).
Following the SCR, the team derives (40) requirements for the system from the high level requirements and the system and operations concept. Using structured or object-oriented analysis the team specifies the software functions and algorithms needed to satisfy each detailed requirement.

A:producer B:customer C:specification D:analyser

The purpose of the requirements definition phase is to produce a clear, complete,consistent, and testable （71） of the technical requirements for the software product.During the requirements definition phase, the requirements definition team uses an iterative process to expand a broad statement of the system requirements into a complete and detailed specification of each function that the software must perform and each （72） that it must meet. The starting point is usually a set of high-level requirements from the （73） that describe the project or problem. In either case, the requirements definition team formulates an overall concept for the system and then defines （74） showing how the system will be operated, publishes the system and operations concept document, and conducts a system concept review(SCR). Following the SCR, the team derives （75） requirements for the system from the high level requirements and the system and operations concept. Using structured or object-oriented analysis, the team specifies the software functions and algorithms needed to satisfy each detailed requirement.

A:function B:definition C:specification D:statement

The purpose of the requirements definition phase is to produce a clear, complete, consistent, and testable （）  of the technical requirements for the software product.
During the requirements definition phase, the requirements definition team uses an iterative process to expand a broad statement of the system requirements into a complete and detailed specification of each function that the software must perform and each （）  that it must meet. The starting point is usually a set of high-level requirements from the （）  that describe the project or problem.
In either case, the requirements definition team formulates an overall concept for the system and the defines （）  showing how the system will be operated, publishes the system and operation concept documents, and conducts a system concept review (SCR).
Following the SCR, the team derives （）  requirements for the system from the highlevel requirements and the system operations concept. Using structured or object-oriented analysis,the team specifies the software functions and algorithms needed to satisfy each detailed requirements.

A:function B:definition C:specification D:statement

The purpose of the requirements definition phase is to produce a clear, complete, consistent, and testable (36) of the technical requirements for the software product.
During the requirements definition phase, the requirements definition team uses an interative process to expand a broad statement of the system requirements into a complete and detailed specification of each function that the software must perform and each (37) that it must meet. The starting point is usually a set of high level requirements from the (38) that describe the project or problem.
In either case, the requirements definition team formulates an overall concept for ’the system and then defines (39) showing how the system will be operated, publishes the system and operations concept document and conducts a system concept review (SCR) .
Following the SCR, the team derives (40) requirements for the system from the high level requirements and the system and operations concept using structured or object-oriented analysis. The team specifies the software functions and algorithms needed to satisfy each detailed requirement.

A:function B:definition C:specification D:statement

The purpose of the requirements definition phase is to produce a clear, complete, consistent, and testable (46) of the technical requirements for the software product.
During the requirements definition phase, the requirements definition team uses an iterative process to expand a broad statement of the system requirements into a complete and detailed specification of each function that the software must perform and each (47) that it must meet. The starting point is usually a set of high-level requirements from the (48) that describe the project or problem.
In either case, the requirements definition team formulates an overall concept for the system and then defines (49) showing how the system will be operated, publishes the system and operations concept document, and conducts a system concept review (SCR).
Following the SCR, the team derives (50) requirements for the system from the high-level requirements and the system and operations concept. Using structured or object-oriented analysis the team specifies the software functions and algorithms needed to satisfy each detailed requirement.

A:producer B:customer C:specification D:analyser

The purpose of the requirements definition phase is to produce a clear, complete, consistent, and testable (1) of the technical requirements for the software product. During the requirements definition phase, the requirements definition team uses an iterative process to expand a broad statement of the system requirements into a complete and detailed specification of each function that the software must perform and each (2)that it must meet. The starting point is usually a set of high-level requirements from the (3)that describe the project or problem. In either case ,the requirements definition team formulates an overall concept for the system and then defines (4) showing how the system win be operated, publishes the system and operations concept document, and conducts a system concept review(SCR). Following the SCR, the team derives (5)requirements for the system from the operations concept. Using structured or object-oriented analysis, the team specifies the software functions and algorithms needed to satisfy each detailed requirement.

A:function B:definition C:specification D:statement