搜题
问题详情
UML中关联是一个结构关系，描述了一组链两个类之间（40）关联。
A.不能有多个
B.可以有多个由不同角色标识的
C.可以有任意多个
D.的多个关联必须聚合成一个
未搜索到的试题可在搜索页快速提交，您可在会员中心"提交的题"快速查看答案。
收藏该题
查看答案
搜题
相关问题推荐
某企业职工关系EMP（E_no，E_name，DEPT，E_addr，E_tel）中的属性分别表示职工号、姓名、部门、地址和电话；经费关系FUNDS（E_no，E_limit，E_used）中的属性分别表示职工号、总经费金额和己花费金额。若要查询部门为"开发部"且职工号为"03015"的职工姓名及其经费余额，则相应的SQL语句应为:SELECT（ ）FROM（ ）WHERE（请作答此空）
A.1.jpg
B.2.jpg
C.1.jpg
D.2.jpg
A.1.jpg
B.2.jpg
C.1.jpg
D.2.jpg
The beauty of software is in its function, in its internal structure, and in the way in which it is created by a team. To a user, a program with just the right features presented through an intuitive and( 71 )interface is beautiful. To a software designer, an internal structure that is partitioned in a simple and intuitive manner, and that minimizes internal coupling is beautiful. To developers and managers, a motivated team of developers making significant progress every week, and producing defect-free code, is beautiful. There is beauty on all these levels.
Our world needs software--lots of software. Fifty years ago software was something that ran in a few big and expensive machines. Thirty years ago it was something that ran in most companies and industrial settings. Now there is software running in our cell phones, watches, appliances, automobiles, toys, and tools. And need for new and better software never( 作答此空 ). As our civilization grows and expands, as developing nations build their infrastructures, as developed nations strive to achieve ever greater efficiencies, the need for more and more Software( 73 )to increase. It would be a great shame if, in all that software，there was no beauty.
We know that software can be ugly. We know that it can be hard to use, unreliable, and carelessly structured. We know that there are software systems whose tangled and careless internal structures make them expensive and difficult to change. We know that there are software systems that present their features through an awkward and cumbersome interface. We know that there are software systems that crash and misbehave. These are( 74) systems. Unfortunately, as a profession, software developers tend to create more ugly systems than beautiful ones.
There is a secret that the best software developers know. Beauty is cheaper than ugliness. Beauty is faster than ugliness. A beautiful software system can be built and maintained in less time, and for less money, than an ugly one. Novice software developers don't understand this. They think that they have to do everything fast and quick. They think that beauty is( 75 ). No! By doing things fast and quick, they make messes that make the software stiff, and hard to understand, Beautiful systems are flexible and easy to understand. Building them and maintaining them is a joy. It is ugliness that is impractical. Ugliness will slow you down and make your software expensive and brittle. Beautiful systems cost the least build and maintain, and are delivered soonest.
A.happens
B.exists
C.stops
D.starts
Our world needs software--lots of software. Fifty years ago software was something that ran in a few big and expensive machines. Thirty years ago it was something that ran in most companies and industrial settings. Now there is software running in our cell phones, watches, appliances, automobiles, toys, and tools. And need for new and better software never( 作答此空 ). As our civilization grows and expands, as developing nations build their infrastructures, as developed nations strive to achieve ever greater efficiencies, the need for more and more Software( 73 )to increase. It would be a great shame if, in all that software，there was no beauty.
We know that software can be ugly. We know that it can be hard to use, unreliable, and carelessly structured. We know that there are software systems whose tangled and careless internal structures make them expensive and difficult to change. We know that there are software systems that present their features through an awkward and cumbersome interface. We know that there are software systems that crash and misbehave. These are( 74) systems. Unfortunately, as a profession, software developers tend to create more ugly systems than beautiful ones.
There is a secret that the best software developers know. Beauty is cheaper than ugliness. Beauty is faster than ugliness. A beautiful software system can be built and maintained in less time, and for less money, than an ugly one. Novice software developers don't understand this. They think that they have to do everything fast and quick. They think that beauty is( 75 ). No! By doing things fast and quick, they make messes that make the software stiff, and hard to understand, Beautiful systems are flexible and easy to understand. Building them and maintaining them is a joy. It is ugliness that is impractical. Ugliness will slow you down and make your software expensive and brittle. Beautiful systems cost the least build and maintain, and are delivered soonest.
A.happens
B.exists
C.stops
D.starts
网络系统中,通常把（）置于DMZ区。
A.网络管理服务器
B.Web服务器
C.入侵检测服务器
D.财务管理服务器
A.网络管理服务器
B.Web服务器
C.入侵检测服务器
D.财务管理服务器
Creating a clear map of where the project is going is an important first step.It lets you identify risks,clarify objectives,and determine if the project even makes sense.The only thing more important than the release plan is not to take it too seriously.Release planning is creating a game plan for your Web project（ ）what you think you want your Web site to be.The plan is a guide for the content,design elements,and functionality of a Web site to be released to the public,to partners,or internally.It also（ ）how long the project will take and how much it will cost.What the plan is not is a functional（请作答此空）that defines the project in detail or that produces a budget you can take to the bank.Basically you use a release Plan to do an initial sanity check of the project's（ ）and worthiness.Release Plans are useful road maps,but don't think of them as guides to the interstate road system.Instead,think of them as the（ ）used by early explorers-half rumor and guess and half hope and expectation.It's always a good idea to have a map of where a project is headed.
A.specification
B.structure
C.requirement
D.implementation
A.specification
B.structure
C.requirement
D.implementation
测试所报告的软件缺陷与错误中通常包含其严重性和优先级的说明，以下理解不正确的是（）
A.测试员通过严重性和优先级对软件缺陷进行分类，以指出其影响及修改的优先次序
B.严重性划分应体现出所发现的软件缺陷所造成危害的恶劣程度
C.优先级划分应体现出修复缺陷的重要程序与次序
D.在软件的不同部分，同样的错误或缺陷的严重性和优先级必须相同
A.测试员通过严重性和优先级对软件缺陷进行分类，以指出其影响及修改的优先次序
B.严重性划分应体现出所发现的软件缺陷所造成危害的恶劣程度
C.优先级划分应体现出修复缺陷的重要程序与次序
D.在软件的不同部分，同样的错误或缺陷的严重性和优先级必须相同