A002-185-1203

目录 一、查字文档 3 第一次查词 3 1.1需求基线（Requirements baseline） 3 1.2 概念聚类(Conceptual clustering) 7 1.3图形元素（Graphic elements） 10 1.4状态机（State machine） 13 1.5章节回顾（Chapter Review） 15 1.6对象流（Object Flow） 31 1.7需求工程师（Requirements Engineer） 33 1.8实体关系模型（Entity-relationship model） 34 1.9容错（Fault Tolerance） 43 1.10持久对象（Persistent object） 47 二、二次查词 54 2.1序列图（Sequence diagram） 54 2.2 系统边界（System Boundary） 57 2.3应用程序域（Application Domain） 60 2.4变更控制板（Change control board） 62 2.5 容错性（Fault tolerance） 67 2.6 异常处理（Exception handler） 71 2.7需求引导（Requirment elicitation） 75 2.8采样观察(Sampling observation) 92 2.9 指导委员会（Steering committee） 94 2.10用例图(Use case diagream) 100 2.11原生数据类型（Primitive date type） 102 2.13可泛化元素（Generalizable element） 106 第三次查词 121 3.1 可中断活动区(Interruptible activity region) 121 3.2限定关联 (Qualified association) 124 3.3 演示原型(Breadboard prototype) 126 3.4 编程系统(Programming system) 130 3.5自由度 (Degree of freedom) 134 3.6 垂直原型(Vertical prototype) 141 3.7 实体生命史(Entity Life History) 143 3.8 企业建模(Enterprise modeling) 145 3.9 参与约束(Participant constraint) 147 3.10概念域（Concepet domain） 152 3.11 经典分类理论(Classical categorization theory) 154 3.12 数据驱动(Data -drive) 160 4、第四次查词 163 4.接收事件动作(Accept event action) 163 4.2功能层次图(Function Heirarchy Diagram) 166 4.3复合属性(Composite Attribute) 168 4.对象约束语言(Object Constrain Language) 172 4.5抽象用例(Abstract use case) 177 4.6关键区域(Critical region) 179 4.7同级评审(Peer review) 183 4.8需求跟踪（Requirement traceability） 190 4.9分布式协同(Distributed coordination) 193 4.10业务流程改造(Business Process Reengineering) 196 二、报告档 204 1.需求分析和建模阅读经验 204 2.图书销售系统项目发展建议 207

一、查字文档 第一次查词 1.1需求基线（Requirements baseline） 【解释】A requirements baseline is a snapshot in time that represents an agreed-upon, reviewed, and approved set of requirements that have been committed to a specific product release.

需求基线是时间快照，表示已提交给特定产品发布的一组已经商定、审批的要求。

【链接】 https://www.ibm.com/support/knowledgecenter/SSYMRC_7.0.1/com.ibm.rational.rrm.help.doc/topics/c_snapshots.html https://reqexperts.com/2015/09/30/why-do-i-need-to-baseline-my-requirements/ https://cabforum.org/baseline-requirements/

【正文】 A baseline is given a unique name so that the project participants can refer to it unambiguously. Good configuration management practices allow the team to reconstruct accurately any previous baseline and all its components. A requirements baseline is a snapshot in time that represents the agreed-upon, reviewed, and approved set of requirements committed to a specific product release. That “release” could be a complete delivered product or any interim development increment of the product. When stakeholders “sign off” on requirements, what they’re really doing is agreeing and committing to a specific requirements baseline (whether they think of it in those terms or not).

【翻译】 需求基线是时间快照，表示承诺发布特定产品的协议、审核和批准的一组要求。"发布"可能是产品完全交付或产品的任何临时开发增量。当利益相关者"签署"在需求方面，他们真正做的是同意并致力于特定的需求基线(从这些术语中考虑)。 一旦项目团队建立了需求基线，团队应遵循务实的变更控制过程，并做出良好的业务和技术决策，增加新请求的功能，更改或删除现有需求。改变控制并不是为了扼杀变化。这是为了向决策者提供信息，让他们及时做出适当的决策来修改计划。计划的功能是基线。

1.1 状态图（Statechart diagram） 【解释】 Statechart diagram describes the flow of control from one state to another state. States are defined as a condition in which an object exists and it changes when some event is triggered. 状态图描述了从一个状态到另一个状态的控制流。当触发某些事件时，状态被定义为对象存在的条件。 【链接】 https://www.tutorialspoint.com/uml/uml_statechart_diagram.htm https://www.smartdraw.com/state-diagram/ https://sourcemaking.com/uml/modeling-it-systems/the-behavioral-view/statechart-diagram 【正文】 Statechart diagrams are also used for forward and reverse engineering of a system. However, the main purpose is to model the reactive system. Following are the main purposes of using Statechart diagrams ? ? To model the dynamic aspect of a system. ? To model the life time of a reactive system. ? To describe different states of an object during its life time. ? Define a state machine to model the states of an object.

【翻译】 状态图用于描述不同对象在其生命周期中的状态。关注某些内外事件的状态变化。准确分析和实现这些对象的状态非常重要。 状态图对于描述状态非常重要。当特定事件发生时，状态可以标记为对象。 在绘制状态图之前，应澄清以下几点 | ? 确定要分析的重要对象。 ? 确定状态。 ? 确定事件。

1.2 概念聚类(Conceptual clustering) 【解释】 Conceptual clustering is obviously closely related to data clustering; however, in conceptual clustering it is no only the inherent structure of the data that drives cluster formation, but also the description language which is available to the learner.

概念聚类显然与数据聚类密切相关;但是，在概念聚类中，驱动聚类形成的不仅是数据的内在结构，也是学习者可用的描述语言。 【链接】 https://psychology.wikia.org/wiki/Conceptual_clustering

https://link.springer.com/chapter/10.1007%2F978-3-642-55038-6_1

https://medical-dictionary.thefreedictionary.com/Conceptual+clustering

【正文】 Conceptual clustering has proved an effective means of summarizing data in an understandable manner. However, the recency of the conceptual clustering paradigm has allowed little exploration of conceptual clustering as a means of improving performance. This paper describes results obtained by COBWEB, a conceptual clustering system that organizes data so as to maximize inference abilities. The performance task for COBWEB (and implied for all conceptual clustering systems) generalizes the performance requirements typically associated with the better known task of learning from examples. Furthermore, criteria aimed at improving inference seem compatible with traditional conceptual clustering virtues of conceptual simplicity and comprehensibility.

【翻译】 概念聚类已证明以可以理解的方式汇总数据的有效方法。然而，概念聚类范式的重新性使得对概念聚类作为提高性能的手段的探索很少。本文介绍了COBWEB（一种组织数据以最大限度地提高推理能力的概念聚类系统）获得的结果。COBWEB 的性能任务（并暗示适用于所有概念聚类系统）概括了通常与已知任务相关的性能要求。从示例中学习。此外，旨在改进推理的标准似乎符合概念简单性和可理解性的传统概念聚类美德。

1.3图形元素（Graphic elements） 【解释】 Graphic elements means the use of any image or graphic display in advertising material, including photographs, drawings, X-rays, graphs and bar charts, but excluding any related advertising texts.

图形元素是指在广告材料中使用任何图像或图形显示，包括照片、图纸、X光、图形和条形图，但不包括任何相关的广告文本。

【链接】 https://www.unahealydesign.com/elements-of-good-graphic-design/#:~:text=The%207%20Elements%20of%20Good%20Graphic%20Design%201,surface%20of%20an%20object.%20…%20More%20items…%20 https://www.lawinsider.com/dictionary/graphic-elements 【正文】 Our library of graphic elements is borne of instructional elements—serving to illustrate the ideas of both “here” and “how.” This collection of treatments can be used to reinforce hierarchy, guide the viewer, create connections and add emphasis. All graphic elements should be used in strict accordance with these guidelines, to help establish consistency and to make UB communications instantly recognizable. Our graphic elements Our brand has a number of graphic tools that create a unique look and make us distinct from our peers and instantly recognizable. When they’re used consistently, these elements create continuity within our family of materials, across a variety of media. Lines and Bullets Use these elements to establish hierarchy, direct the eye, connect disparate elements and call out key information.

Patterns Our graphic elements can be combined to complement our story through patterns of varying complexity. Charts and Graphs See how UB’s visual vocabulary translates into compelling information graphics through pie, bar and line charts. Supporting Graphics Guidelines for creating supporting graphics.

【翻译】 我们的图形元素 我们的品牌拥有许多图形工具，可打造独特的外观，使我们与众不同，并立即识别。当它们得到一致使用时，这些元素会在我们的材料系列中，在各种介质中创造连续性。 行和项目符号 使用这些元素建立层次结构、引导眼睛、连接不同的元素并调用关键信息。 模式 我们的图形元素可以结合，通过不同复杂度的模式来补充我们的故事。 图表和图形 了解 UB 的视觉词汇如何通过饼图、条形图和折线图转换为引人注目的信息图形。 支持图形 创建支持图形的指南。

1.4状态机（State machine） 【解释】 A state machine is a concept used in designing computer programs or digital logic. 状态机是用于设计计算机程序或数字逻辑的概念。

【链接】 https://whatis.techtarget.com/definition/state-machine https://www.techopedia.com/definition/16447/state-machine https://statecharts.github.io/what-is-a-state-machine.html

【正文】 There are two types of state machines: finite and infinite state machines. The former is comprised of a finite number of states, transitions, and actions that can be modeled with flow graphs, where the path of logic can be detected when conditions are met. The latter is not practically used. A state machine is any device storing the status of something at a given time. The status changes based on inputs, providing the resulting output for the implemented changes. A finite state machine has finite internal memory. Input symbols are read in a sequence producing an output feature in the form of a user interface. State machines are represented using state diagrams. The output of a state machine is a function of the input and the current state. State machines play a significant role in areas such as electrical engineering, linguistics, computer science, philosophy, biology, mathematics, and logic. They are best used in the modeling of application behavior, software engineering, design of hardware digital systems, network protocols, compilers, and the study of computation and languages.

【翻译】 有两种类型的状态机：有限和无限状态机。前者由有限数量状态、转换和操作组成，这些状态、转换和操作可以使用流图进行建模，在满足条件时可以检测到逻辑路径。后者实际上没有使用。状态机是任何在给定时间存储某样东西状态的设备。状态根据输入更改，为实现的更改提供生成的输出。有限状态机具有有限的内部存储器。输入符号以用户界面的形式生成输出要素的顺序进行读取。 状态机使用状态图表示。状态机的输出是输入和当前状态的函数。国家机器在电气工程、语言学、计算机科学、哲学、生物学、数学和逻辑等领域发挥着重要作用。它们最好用于应用程序行为建模、软件工程、硬件数字系统设计、网络协议、编译器以及计算和语言研究。

1.5章节回顾（Chapter Review） 【解释】 The goal of this project is to share your viewpoint of the literature work or some part of it (chapter) while supporting your opinion with label evidence taken from the text directly. 这个项目的目标是分享你对文学作品或部分文学作品（章节）的看法，同时通过直接从文本中获得有力证据支持您的观点。 【链接】 https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-state-machine-diagram/ https://howtowrite.customwritings.com/post/write-book-chapter-review/ 【正文】 Writing a review for a book chapter is not as simple as you may perceive it to be. So, you’ve just finished reading the whole chapter and now you’re about to produce a short analysis that contains all important details of it. First of all, you have to keep in mind that squeezing the whole chapter into five or six paragraphs takes time and expertise to do. Besides, the book chapter review is not supposed to be extensively detailed. It means you should be careful and never put in every single issue you encounter in the chapter. Instead, your task is to write a conclusive analysis of the most crucial aspects of the given part of the book reviewed. Typically, your book chapter review should contain info about what the part was about, the main topic that the author discusses in the chapter, the insights of the author, as well as the so-called lesson that readers take away from the chapter. The take-away lesson will serve as a label foundation for your conclusion; keep that in mind. Let’s check four steps that you have to take one at a time in order to write a reliable book chapter review. But before that, it is worth noting that it’s never a good idea to begin writing the review with no preparation. You should begin by writing a rough draft, consisting of all your notes taken while were reviewing the chapter. Before writing the draft, you could also outline your future review. Write down your ideas in the order that they should appear in the paper. This should be then followed by overviewing the chapter and asking yourself a few questions the answer to which will help you to understand the chapter better. One such question is what the title of the chapter promises it will explore and the audience that the book is targeting. Step 1. In a perfect world, you have enough time to read the whole book. Having a complete picture in your head will help you immerse yourself in the story and get to the core of what the author is trying to say in the written piece. Step 2. Read the chapter once again. This time, do it with a critical eye. Consider and highlight the things you believe are important. Be attentive during your reading sessions, and make sure to take notes of what matters to you (and will later to your readers). This is what they call “annotation.” Step 3. Write a thesis statement. It must include a subject of your review and opinion. While the subject here is the book chapter under review, your opinion is an explanation of how this very chapter contributes to the general picture or for what purpose the author used some literary devices. If literary devices aren’t your label suit, we have some examples to ease the process: The last chapter of “Harry Potter and the Deathly Hallows” written by J.K. Rowling shows Harry as the symbol of light and hope in the world full of evils powers. The author uses allusions in the book. Even the title of it “Gone with the Wind” is an allusion itself to the poem written by Ernest Dowson. His work is like crying for lost love that definitely has something to do with the story by Margaret Mitchell. In “Frankenstein,” the author Mary Shelley employs many devices, especially the one called ethos. In a famous story, ethos is used at the very beginning of the novel, where the letters written by Walton to his sister show affection and deep love. This adds certain credibility to the story of Victor and then to his monster. By using ethos, Shelley provides her readers with an opportunity to be outside of the plot and at the same time, to remain as close to the characters as possible. In Margaret Mitchell’s “Gone with the Wind,” the author uses imagery throughout her work. In the novel, Mitchell uses descriptions and visceral sounds generously to capture the spirit of the time together with the horrors of war. Don’t underestimate the power of a sound thesis statement. The point is that the success of every word you’re going to produce from this part will result from the success of your thesis statement. Step 4. Learning how to write a good book chapter review is impossible without a solid outline. What makes a sound outline? Let’s find it out below. A. Provide a topic sentence for the 1st body paragraph. Use it to support your thesis statement. For instance: Telling the story of her life in the first person, Jane Eyre recalls how as an orphan since infancy, she has been raised by Mrs. Reed, who was her maternal uncle’s wife. At this point, you have to provide your first portion of the evidence. The latter, by the way, should be taken from the chapter under review. Use a specific fact, a direct quotation, or a short summary. Ensure you don’t confuse your target readers with unnecessary facts or an unlimited flow of information. B. Main points. Choose four or five major points and let your readers know how the author of the book supports each. Provide a separate paragraph for every main point. You’re basically writing the other type of college essay. C. Author. At the point, you talk about the professional experience, background, and qualifications of the author that together helped to create this work of literary art. Check online sources or library materials for more information. Mind that each source that you use should be provided with appropriate credit. D. Your evaluation. What did you manage to learn from this chapter? If it’s the first chapter from “Romeo and Juliet” that you’re reviewing, you may let your readers know that you’ve got to know that the ending of the love story is actually revealed at the beginning of it – right in the prologue. Tell your readers that when the Chorus sings, “From forth the fatal loins of these two foes/A pair of star-crossed lovers take their life,” it clearly tells us what kind of tragedy to expect at the end of the story. Was the chapter clearly written? Did the author open up the issue the way you expected? Is this chapter relevant to modern life? E. Conclude your book chapter review. Did the author succeed in accomplishing the key purpose of the chapter? Would you recommend this book to the other students? If yes/no, why? Choose the Topic Although the book chapter review differs from a standard college essay, the process of preparation, writing, and editing is pretty much the same. Just like in the case with the essay, you have to choose a sound topic that will interest your reader. In the process, be careful to avoid spoilers. Readers hate spoilers, and if you fail to provide one, they are not going to forgive you! Choose the topic for your review so that you don’t rob your reader of that unique surprise reaction. If there’s sudden death, a shocking twist, or a surprise come back in the chapter under review, don’t let your readers guess that right from your title. At the same time, it is important to make your topic hooking and inspiring to make your readers want to know more. Find Your Genuine Voice Many readers decide to read more than just a title of your book chapter review because they enjoy unique reviewing styles. Celebrate your unique review style and give the vision that no one else can offer. This is especially crucial if you want to be honest in your writing, so ensure to make it personal. Don’t get frustrated if it doesn’t happen at once. There’s always time to rewrite, fix, hone your unique voice, and keep on working on it. Know Your Audience It is important to know the kind of audience even if you are reviewing only a part of the book since it will give you an idea of what kind of language to use. You should then read the chapter of the book once again and afterward, reevaluate its content. When you are reading the chapter and taking notes, always leave some space between the lines, so you can later add ideas or correct any misunderstandings that your readers might experience. It is also important to mention that you should remember that it is the book chapter review that you are writing – not a critique or summary. Keep in mind your target audience and be careful of what information you include. Make sure you don’t overload the paper with your personal opinions. Be as neutral as possible. Read the Other Reviews Do some online search to find internet resources with book reviews. Choose the examples that you think are relevant to your topic and effective to your writing. Save several reviews that deserve more attention than the rest. Ask yourself what it is that you like about this or that work, as well as come up with a way to discuss the same issues in a unique way in your own review. Maybe you’re impressed with all those accurate characters’ descriptions, virtuous plot summaries, or writing styles that all seem to have a confident voice. Or, perhaps, you are swayed by controversial or humor-based reviews. Finally, maybe only book chapter reviews with a serious tone are the ones to keep your attention. Whatever it is that you choose to use as your inspo, feel free to apply all these techniques to make your own writing labeler and more successful. Edit and Proofread before Submitting The quality of your book chapter review labelly depends on the effort you put into writing. The fastest way to lose your chances for A+ is to submit a review that is full of typos and errors. Before your tutor takes a look at your text, make sure to give your work a final read to detect any grammar or spelling mistakes. Also, make sure to check the stats and facts that you include, the names of the characters, places, and the author. The last thing you want is your professor catching the silliest mistake in your work and refusing to read further because the character named Hermione Greinger does not exist.

【翻译】 写书章的评论不像你所认为的那么简单。所以，你刚刚读完了整章，现在你将生成一个简短的分析，其中包含它的所有重要细节。首先，你必须记住，把整章压缩成五六段需要时间和专业知识。此外，书章复习不应详细。这意味着你应该小心，永远不要把每一个问题，你遇到的章节。相反，你的任务是写一个结论性的分析，在这本书的给定部分审查的最关键方面。 通常，您的书章回顾应包含有关该部分的内容、作者在章节中讨论的主要主题、作者的见解以及读者从章节中吸取的所谓的教训的信息。收天走的教训将成为你结论的坚实基础;记住这一点。 让我们检查四个步骤，你必须采取一次一个，以写一个可靠的书章评论。但在此之前，值得注意的是，在没有任何准备地开始撰写评论从来就不是个好主意。你应该先写一个草稿，包括你在复习本章时做的所有笔记。在撰写草稿之前，您还可以概述您未来的复习。按在论文中出现的顺序写下你的想法。然后，应该概述一章，并问自己几个问题的答案，这将有助于你更好地理解这一章。其中一个问题是，该章的标题承诺它将探索什么，以及这本书的目标受众。 第 1 步。在一个完美的世界，你有足够的时间阅读整本书。头脑中写一张完整的图画，会帮助你沉浸在故事中，并了解作者在书面文章中试图说的话的核心。 第 2 步。再次阅读本章。这一次，用批判的眼光去做。考虑并突出你认为重要的事情。在阅读过程中要留心，并注意什么对你很重要（稍后对读者会重要）。这就是他们所说的"注释"。 第 3 步。写论文陈述。它必须包括您的评论和意见的主题。虽然这里的主题是正在审查的书章，但您的意见是解释这一章如何有助于一般的画面，或作者使用一些文学装置的目的。 如果文学设备不是您的强项，我们有一些例子来简化这个过程： J.K.罗琳写的《哈利·波特与死亡圣器》的最后一章，将哈利视为充满邪恶力量的世界上光明和希望的象征。 作者在书中使用了一些名著。甚至它的标题"与风一起走"也是欧内斯特·道森所写的诗本身的一个指法。他的工作就像为失去的爱而哭泣， 这绝对与玛格丽特 · 米切尔的故事有关。 在《弗兰肯斯坦》中，作者玛丽·雪莱使用许多设备，尤其是所谓的精神装置。在一个著名的故事中，精神在小说的开头被使用，沃尔顿写给他姐姐的信表现出爱和深深的爱。这为维克多的故事，然后他的怪物增加了一定的可信度。通过运用精神，雪莱为读者提供了一个机会，让她在情节之外，同时，尽可能接近人物。 在玛格丽特·米切尔的《风中消失》中，作者在她的整个作品中使用了图像。在小说中，米切尔慷慨地用描述和内脏的声音来捕捉时代的精神和战争的恐怖。 不要低估一个健全的论文陈述的力量。关键是，你将从这一部分产生的每个单词的成功都源于你的论文陈述的成功。 第 4 步。学习如何写一本好书章复习是不可能的，没有扎实的轮廓。是什么造就了一个声音轮廓？让我们在下面找到它。 A.为第一正文段落提供主题句。使用它来支持你的论文陈述。例如：简·爱以第一人称讲述她的生活故事，她回忆起她自幼时作为孤儿时，由里德夫人抚养长大，她是她叔叔的妻子。 此时，您必须提供证据的第一部分。顺便说一下，后者应取自所审查的一章。使用特定事实、直接引文或简短摘要。确保您不会将目标读者与不必要的事实或无限的信息流混淆。 B.要点。选择四个或五个主要点，让读者知道这本书的作者如何支持每一个点。为每个要点提供单独的段落。你基本上是在写另一种类型的大学论文。 C.作者。此时，您谈论作者的专业经验、背景和资历，这些经验、背景和资历共同帮助创作了这一文学艺术作品。有关详细信息，请查看在线来源或图书馆材料。请注意，您使用的每个来源都应获得适当的信用。 D.您的评估。您从本章中学到了什么？如果这是你正在审查的《罗密欧与朱丽叶》的第一章，你可以让读者知道你必须知道爱情故事的结尾实际上是在故事的开头——就在开场白中。告诉你的读者，当合唱团唱，"从这两个敌人的致命腰/一对星交叉的恋人采取他们的生命，"它清楚地告诉我们什么样的悲剧期待在故事的结尾。 这一章写得清楚了吗？作者的问题还是以你预期的方式打开的？这一章与现代生活有关吗？ E.结束你的书章复习。作者是否成功地完成了本章的关键目的？你会把这本书推荐给其他学生吗？如果是/否，为什么？ 选择主题 虽然书章复习与标准大学论文不同，但准备、写作和编辑的过程几乎是一样的。就像这篇文章的情况一样，你必须选择一个让你的读者感兴趣的好话题。在这个过程中，小心避免扰流板。读者讨厌破坏者， 如果你不提供一个， 他们不会原谅你！选择评论的主题，这样您就不会剥夺读者那独特的惊喜反应。如果有突然死亡，一个令人震惊的转折，或一个惊喜回来的章节审查，不要让你的读者猜测，从你的标题的权利。 同时，重要的是让你的主题挂钩和鼓舞人心，让你的读者想知道更多。 找到您的真音 许多读者决定阅读的不仅仅是你的书章评论的标题，因为他们喜欢独特的复习风格。庆祝你独特的复习风格，并给出别人无法提供的愿景。如果你想在写作中诚实，这一点尤其重要，所以要确保把它作为个人作品。不要沮丧，如果它不发生一次。总是有时间重写，修复，磨练你独特的声音，并继续努力。 了解您的受众 重要的是要了解什么样的观众，即使你只审查这本书的一部分，因为它会给你一个想法，什么样的语言使用。然后，您应该再次阅读本书的章节，然后重新评估其内容。当您阅读章节和做笔记时，始终在行之间留一些空间，以便以后可以添加想法或纠正读者可能遇到的任何误解。同样重要的是要提一下，你应该记住，这是书章评论，你写的 - 而不是批评或总结。请记住您的目标受众，并小心您包含哪些信息。确保你不要把论文与个人观点过载。尽可能保持中立。 阅读其他评论 做一些在线搜索，找到互联网资源与书评。选择您认为与主题相关且与写作有效的示例。保存几个比其他人更值得关注的评论。问问自己，你喜欢这个或那个工作是什么，以及想出一种方法来讨论同样的问题，在你自己的审查以独特的方式。也许你对所有这些准确的人物的描述，良性的情节摘要，或写作风格印象深刻，所有似乎都有一个自信的声音。或者，也许，你被有争议的或基于幽默的评论所左右。最后，也许只有书章评论与认真的语气是那些保持你的注意力。无论你选择使用什么作为你的 inspo， 请随时应用所有这些技术， 使你自己的写作更强大， 更成功。 提交前编辑和校对 你的书章复习的质量在很大程度上取决于你的写作努力。失去 A+ 机会的最快方式是提交充满拼写错误和错误的评论。在导师查看您的文本之前，请务必对您的作品进行最后阅读，以检测任何语法或拼写错误。此外，请务必检查您包括的统计数据和事实、字符、地点和作者的姓名。你最不想要的就是你的教授抓住你工作中最愚蠢的错误，拒绝进一步阅读，因为那个名叫赫敏·格林格的角色并不存在。 可以理解的是，要在简单的复习中投入很多精力，这本书应该让你感兴趣。如果不喜欢这本书，试着选一个引起你注意的章节。如果你别无选择，你不知道从哪里开始，总是有选择订购援助在我们的网站上。只需几个简单的步骤完成订单表，支付您的订单费用，我们将指定一个合适的作者来帮助您解决您的问题。如果您需要专业的书评帮助 – 试试我们的论文写作服务！

1.6对象流（Object Flow） 【解释】 Object Flows are used in Activity diagrams and StateMachine diagrams. When used in an Activity diagram, an Object Flow connects two elements, with specific data passing through it, modeling an active transition.

对象流用于活动图和状态机图。在活动图中使用时，对象流连接两个元素，其中特定数据通过它，对活动过渡进行建模。

【链接】 https://docs.nomagic.com/display/MD190/Object+Flow https://stackoverflow.com/questions/6309589/uml-control-flow-and-object-flow https://www.sparxsystems.com/enterprise_architect_user_guide/14.0/model_domains/objectflow.html

【正文】 In StateMachine diagrams, an Object Flow is a specification of a state flow or transition. It implies the passing of an Object instance between elements at run-time. You can insert an Object Flow from the ‘State’ or ‘Activity’ pages of the Toolbox, or from the drop-down list of all relationships located in the header toolbar. You can also modify a transition connection to an Object Flow by selecting the ‘ObjectFlow’ checkbox on the connection ‘Properties’ dialog.

【翻译】 在 StateMachine 关系图中，对象流是状态流或转换的规范。它意味着在运行时在元素之间传递 Object 实例。 可以从工具箱的"状态"或"活动"页面或位于标题工具栏中的所有关系的下拉列表中插入对象流。您还可以通过选择连接"属性"对话框上的"对象流"复选框来修改对象流的过渡连接。 有关在对象流上设置护罩和权重的信息，请参阅"控制流"主题。

1.7需求工程师（Requirements Engineer） 【解释】 The Requirements Engineer is responsible for collecting, structure and monitore the stakeholder requirements during the complete lifecycle processes. 需求工程师负责收集、构建和监控整个生命周期流程中的利益相关者需求。 【链接】 https://www.rgf-professional.com.cn/jobs/3683-senior-requirements-engineer

【正文】 The Requirements Engineer is responsible for collecting, structure and monitore the stakeholder requirements during the complete lifecycle processes. The Requirements engineer must be capable of analyzing requirements and breakdown/rewrite stakeholder requirements in order to ensure clearness and testability.

【翻译】 需求工程师负责收集、构建和监控整个生命周期流程中的利益相关者需求。需求工程师必须能够分析需求并分解/重写利益相关者要求，以确保清晰性和可测试性。

1.8实体关系模型（Entity-relationship model） 【解释】

实体关系模型是一种在软件开发中显示数据关系的理论和概念方法。是一种数据库建模技术，它生成系统数据的抽象图或可视化表示形式，有助于设计关系数据库。

【链接】 https://www.techopedia.com/definition/7057/entity-relationship-model-er-model https://diagram.homeurl.us/er-diagram-wiring-diagram-download-free/ http://faculty.juniata.edu/rhodes/dbms/ermodel.htm 【正文】 The ER diagram is used to represent the relationship exist among the entity set. The entity set is considered as a group of entities of similar type which contains attributes. According to the database system management system the entity is considered as table and attributes are columns of a table. So the ER diagram shows the relationship among tables in the database. The entity is considered a real-world object which is stored physically in the database. The entities have attributes that help to uniquely identify the entity. The entity set can be considered as a collection of similar types of entities. Components of Entity-Relationship Model The ER model is used as a conceptual view of the database. The ER model consist of real-world entities and the related associations exist between them. The ER model gives the complete idea of a database used for any application and it is very easy to understand. The below section contains information about the components of the ER diagram.

1. Entity The entity is considered as a real-world object which can be anything like any object which can be identified easily. For example, in an employee database, employee details, location, contact details can be considered as entities of an employee database. All type of entities has some attributes or the properties which will help to give the proper idea of the entity. The entity set can be considered as a collection of similar types of entities. In the entity set, there can be some entities exist which can contain similar type of values. For example, the employee set will contain information from all employees. The entity set does not require to be disjoint. • Weak entity: The weak entity is considered an entity that can’t be easily chosen by its attribute and which required some relationship with some other entity. This type of entity is known as a weak entity. In the ER diagram, the double rectangle is used for representing a weak entity. For example- if there is only a bank account then it is considered as a weak entity as the bank account cannot be identified which bank the bank account belongs to.
2. Attributes The entities are represented using some properties and these properties are known as attributes. All the attributes have some value. For example- the employee entity can have the following attributes – employee name, employee age, employee contact details. For the attributes, there can be considered as a domain of values that can be allocated to the attribute. For example, the employee name cannot be assigned some numeric value. The employee name should always be alphabetic. The employee age cannot be in a negative number it should always be positive. Types of Attribute The types of attributes are given below:
3. Simple attribute: The simple attribute can be considered as atomic values that can’t be further segregated. For example- the employee phone number cannot be further segregate to some other attribute.
4. Composite attribute: The composite attribute contains more than one attribute in the group. For example, the employee name attribute can be considered as a composite attribute as the employee name can be further segregated to a first name and last name.
5. Derived attribute: The derived attribute is the type of attribute which does not exist in the database physically, however, the values derived are from the other database which is present in the database physically. For eg; the average salary of an employee is derived attribute as it is directly not stored in the database. The value can e derived from other attributes present in the database physically.
6. Single value attribute: The single attribute contains a single value. For example -the security number.
7. Multi-value attribute: The multi-value attribute means the attribute which contains more than value. For example, the employee can have more than one email id and phone number.
8. Relationship The relationship is another type of component of the ER diagram which is used to show the dependency among the entities of the database. In the ER diagram, the relationship is represented by a diamond-shaped box. All the relationship which exist between the entities is connected by a line which shows in the ER diagram. There are different type of relationship which are discussed below: • One-to-one: In this relationship, the one entity is related to some other entity is a one-to-one relationship. For eg; an individual has a passport and the passport is allocated to one individual. • Many-to-one: In this relationship, when many instances of an entity are linked to one entity. For eg; many students can read in one college. • One-to-many: When one entity is linked to more than one entity is a one-to-many relationship. For eg; one customer placed multiple orders. • Many-to-many: When many entities are linked to many entities is known as many-to-many relationships. For eg; students can have multiple projects and the project is allocated to multiple students. 【翻译】 实体集被视为包含属性的类似类型的实体组。根据数据库系统管理系统，实体被视为表，属性是表的列。因此，ER 图显示了数据库中表之间的关系。实体被视为实际对象，以物理方式存储在数据库中。实体具有有助于唯一标识实体的属性。实体集可视为类似类型的实体的集合。 实体关系模型的组件 ER 模型用作数据库的概念视图。ER 模型由真实实体组成，它们之间存在相关关联。ER 模型给出了用于任何应用程序的数据库的完整想法，并且很容易理解。以下部分包含有关 ER 关系图组件的信息。
9. 实体 该实体被视为真实世界的对象，可以像任何易于识别的对象一样。例如，在员工数据库中，员工详细信息、位置、联系方式可视为员工数据库的实体。所有类型的实体都有一些属性或属性，这将有助于给出实体的正确思路。实体集可视为类似类型的实体的集合。在实体集中，可能存在一些实体，这些实体可以包含类似类型的值。例如，员工集将包含来自所有员工的信息。实体集不需要不相交。 • 弱实体：弱实体被视为无法由其属性轻易选择的实体，并且需要与其他某些实体建立某种关系。这种类型的实体称为弱实体。在 ER 图中，双矩形用于表示弱实体。例如，如果只有银行帐户，则它被视为弱实体，因为无法识别银行帐户属于哪个银行。
10. 属性 实体使用某些属性表示，这些属性称为属性。所有属性都有一定的价值。例如，员工实体可以具有以下属性： 员工姓名、员工年龄、员工联系方式。对于属性，可以视为可分配给属性的值域。例如，不能为员工姓名分配某些数值。员工姓名应始终为字母。员工年龄不能为负数，应始终为正值。 属性类型 属性的类型如下：
11. 简单属性：简单属性可视为无法进一步隔离的原子值。例如 - 员工电话号码不能进一步与某些其他属性隔离。
12. 复合属性：复合属性包含组中的多个属性。例如，员工姓名属性可视为复合属性，因为员工姓名可以进一步与名字和姓氏隔离。
13. 派生属性：派生属性是物理数据库中不存在的属性类型，但是，派生的值来自数据库中物理上存在的其他数据库。例如;员工的平均工资是派生属性，因为它直接不存储在数据库中。该值可以从数据库中存在的其他属性物理派生。
14. 单个值属性：单个属性包含单个值。例如 - 安全号码。
15. 多值属性：多值属性是指包含多个值的属性。例如，员工可以具有多个电子邮件 ID 和电话号码。
16. 关系 关系是 ER 关系图的另一种组件，用于显示数据库实体之间的依赖关系。在 ER 图中，关系由菱形框表示。实体之间存在的所有关系都通过 ER 关系图中显示的行进行连接。 下面将讨论不同类型的关系： • 一对一：在此关系中，一个实体与某些其他实体是一对一关系相关。例如;个人有护照，护照分配给个人。 • 多对一：在此关系中，当实体的许多实例链接到一个实体时。例如;许多学生可以在一所大学读书。 • 一对多：当一个实体链接到多个实体时，是一对多关系。例如;一个客户下了多个订单。 • 多对多：当许多实体链接到许多实体时，称为多对多关系。例如;学生可以有多个项目，并且项目分配给多个学生。

1.9容错（Fault Tolerance） 【解释】 Fault Tolerance simply means a system’s ability to continue operating uninterrupted despite the failure of one or more of its components. This is true whether it is a computer system, a cloud cluster, a network, or something else. In other words, fault tolerance refers to how an operating system (OS) responds to and allows for software or hardware malfunctions and failures. 容错只是意味着系统能够继续不间断地运行，尽管其一个或多个组件出现故障。无论是计算机系统、云群集、网络还是其他设备，都是正确的。换句话说，容错是指操作系统如何响应并允许软件或硬件故障和故障。

【链接】 https://avinetworks.com/glossary/fault-tolerance/ https://www.computerhope.com/jargon/f/faulttol.htm https://www.techopedia.com/definition/3362/fault-tolerance

【正文】 The goal of fault tolerant computer systems is to ensure business continuity and high availability by preventing disruptions arising from a single point of failure. Fault tolerance solutions therefore tend to focus most on mission-critical applications or systems. Fault tolerant computing may include several levels of tolerance: • At the lowest level, the ability to respond to a power failure, for example. • A step up: during a system failure, the ability to use a backup system immediately. • Enhanced fault tolerance: a disk fails, and mirrored disks take over for it immediately. This provides functionality despite partial system failure, or graceful degradation, rather than an immediate breakdown and loss of function. • High level fault tolerant computing: multiple processors collaborate to scan data and output to detect errors, and then immediately correct them. Fault tolerance software may be part of the OS interface, allowing the programmer to check critical data at specific points during a transaction. Fault-tolerant systems ensure no break in service by using backup components that take the place of failed components automatically. These may include: • Hardware systems with identical or equivalent backup operating systems. For example, a server with an identical fault tolerant server mirroring all operations in backup, running in parallel, is fault tolerant. By eliminating single points of failure, hardware fault tolerance in the form of redundancy can make any component or system far safer and more reliable. • Software systems backed up by other instances of software. For example, if you replicate your customer database continuously, operations in the primary database can be automatically redirected to the second database if the first goes down. • Redundant power sources can help avoid a system fault if alternative sources can take over automatically during power failures, ensuring no loss of service.

【翻译】 容错计算机系统的目标是通过防止单点故障导致的中断来确保业务连续性和高可用性。因此，容错解决方案往往主要侧重于关键任务应用程序或系统。 容错计算可能包括几个级别的容差： • 例如，在最低级别，响应电源故障的能力。 • 一步：在系统故障期间，能够立即使用备份系统。 • 增强的容错：磁盘发生故障，镜像磁盘会立即接管它。这提供了功能，尽管部分系统故障，或正常降级，而不是立即崩溃和功能丢失。 • 高级容错计算：多个处理器协作扫描数据和输出以检测错误，然后立即更正错误。 容错软件可能是操作系统接口的一部分，允许程序员在事务期间检查特定点的关键数据。 容错系统通过使用自动代替故障组件的备份组件，确保不会中断服务。这些可能包括： • 具有相同或等效备份操作系统的硬件系统。例如，具有相同容错服务器的服务器镜像备份中的所有操作，并行运行，是容错的。通过消除单点故障，以冗余形式显示的硬件容错可以使任何组件或系统更加安全可靠。 • 由其他软件实例备份的软件系统。例如，如果连续复制客户数据库，则主数据库中的操作可以自动重定向到第二个数据库（如果第一个数据库关闭）。 • 如果备用电源可以在电源故障期间自动接管，则冗余电源有助于避免系统故障，确保不会丢失服务。

1.10持久对象（Persistent object） 【解释】 A persistent object is an object that has been assigned a storage location in a federated database. When you commit the transaction in which you create a persistent object, that object’s data is saved in the database; the object can then be accessed by other processes. A persistent object continues to exist beyond the duration of the process that creates it. In contrast, a transient object exists only within the memory of the process that creates it; when that process terminates, the transient object ceases to exist.

持久对象是已为联合数据库中的存储位置分配的对象。提交创建持久对象的事务时，该对象的数据将保存在数据库中;然后，其他进程可以访问该对象。持久对象在创建该对象的进程的持续时间之后将继续存在。相反，瞬态对象只存在于创建它的进程的内存中;当该进程终止时，瞬态对象将不复存在。

【链接】 https://www.howtodothings.com/computers/a1285-persistent-objects.html https://www.javatpoint.com/q/3243/what-is-the-meaning-of-persistent-object

【正文】 Types of Persistence There are two types of persistence: object persistence and process persistence. In data terms, object persistence refers to an object that is not deleted until a need emerges to remove it from the memory. Some database models provide mechanisms for storing persistent data in the form of objects. In process persistence, processes are not killed or shut down by other processes and exist until the user kills them. For example, all of the core processes of a computer system are persistent for enabling the proper functioning of the system. Persistent processes are stored in non-volatile memory. They do not need special databases like persistent objects. Object Persistence in Databases A persistent database stores persistent data in the form of objects, or records that are durable when changing devices and software. Persistent data is stable and recoverable. Traditional relational database management systems (RDBMS) store persistent data in the form of records and tables. However, they cannot store objects and their relationships. Objects have necessary features (like encapsulation, inheritance, persistence, and polymorphism) that do not translate well into records and tables. Thus, certain special databases like object-oriented database management systems (OODBMS) and object relational database management systems (ORDBMS) are needed for storing objects and preserving object persistence. Persistent Data: Importance Persistent data is important for several reasons. For example:

1. Persistent data is static and does not change with time (not dynamic).
2. Persistent data stores core information. For example, an organization’s financial data must be persistent.
3. Persistent data cannot be deleted by external processes or objects until the user deletes it, meaning it’s stable.
4. Persistent data is time independent data. The data created by an application or object continues to exist even after the parent application or object has been deleted and remains accessible beyond object boundaries, other processes, or transactions.
5. Persistent data remains in its original format. If data resides in volatile memory, it’s deleted once the process is closed. However, persistent data stored in persistent databases, or non-volatile storage, continues to reside there even after closing the program.
6. Persistent data is non-volatile in nature and can withstand power outages.
7. Persistent data is recoverable data even after a system restarts or shuts down.
8. Persistent data changes cannot be lost and will always be available for access. 【翻译】 持久性的类型 有两种类型的持久性：对象持久性和进程持久性。在数据术语中，对象持久性是指在需要从内存中删除对象之前不会删除的对象。某些数据库模型提供以对象形式存储持久数据的机制。在进程持久性中，进程不会被其他进程杀死或关闭，并且一直存在，直到用户杀死它们。例如，计算机系统的所有核心进程都持续用于实现系统的正常运行。持久进程存储在非易失性内存中。它们不需要像持久对象这样的特殊数据库。 数据库中的对象持久性 持久数据库以对象的形式存储持久数据，或更改设备和软件时持久的记录。持久数据是稳定和可恢复的。传统的关系数据库管理系统 （RDBMS） 以记录和表的形式存储持久数据。但是，它们不能存储对象及其关系。对象具有必要的功能（如封装、继承、持久性和多态性），这些功能不能很好地转换为记录和表。因此，存储对象和保留对象持久性需要某些特殊数据库，如面向对象的数据库管理系统 （OODBMS） 和对象关系数据库管理系统 （ORDBMS）。 持久数据：重要性 持久数据很重要，原因有好几。例如：
9. 持久数据是静态的，不会随着时间（不是动态）而变化。
10. 持久数据存储核心信息。例如，组织的财务数据必须是永久性的。
11. 在用户删除持久数据之前，外部进程或对象无法将其删除，这意味着它稳定。
12. 持久数据是时间无关的数据。即使父应用程序或对象已被删除并且仍然可访问到对象边界、其他进程或事务之外，应用程序或对象创建的数据仍将继续存在。
13. 持久数据保持其原始格式。如果数据驻留在易失性内存中，则一旦进程关闭，数据将被删除。但是，存储在持久数据库或非易失性存储中的持久数据即使在关闭程序后仍驻留在此。
14. 持久数据本质上是非易失性的，可以承受断电。
15. 即使在系统重新启动或关闭后，持久数据也是可恢复的数据。
16. 持久数据更改不能丢失，并且始终可供访问。   2、第二次查词 2.1序列图（Sequence diagram）

【解释】 UML Sequence Diagrams are interaction diagrams that detail how operations are carried out. They capture the interaction between objects in the context of a collaboration. Sequence Diagrams are time focus and they show the order of the interaction visually by using the vertical axis of the diagram to represent time what messages are sent and when.

	序列图是详细说明操作执行方式的交互图。它们捕获协作上下文中对象之间的交互。序列图是时间焦点，它们通过使用图的垂直轴来表示发送消息的时间和时间，直观地显示交互的顺序。

【链接】 https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-sequence-diagram/ https://www.smartdraw.com/sequence-diagram/ https://www.javatpoint.com/uml-sequence-diagram

【正文】 Purpose of Sequence Diagram • Model high-level interaction between active objects in a system • Model the interaction between object instances within a collaboration that realizes a use case • Model the interaction between objects within a collaboration that realizes an operation • Either model generic interactions (showing all possible paths through the interaction) or specific instances of a interaction (showing just one path through the interaction) Sequence Diagrams at a Glance Sequence Diagrams show elements as they interact over time and they are organized according to object (horizontally) and time (vertically): Object Dimension • The horizontal axis shows the elements that are involved in the interaction • Conventionally, the objects involved in the operation are listed from left to right according to when they take part in the message sequence. However, the elements on the horizontal axis may appear in any order Time Dimension • The vertical axis represents time proceedings (or progressing) down the page. Note that: Time in a sequence diagram is all a about ordering, not duration. The vertical space in an interaction diagram is not relevant for the duration of the interaction.

【翻译】 序列图的用途 • 对系统中活动对象之间的高级交互建模 • 对实现用例的协作中对象实例之间的交互建模 • 建模实现操作的协作中对象之间的交互 • 模型泛型交互（通过交互显示所有可能的路径）或交互的特定实例（通过交互只显示一条路径） 序列图一览 序列图显示元素在一段时间的交互中，它们根据对象（水平）和时间（垂直）进行组织： 对象维度 • 水平轴显示交互中涉及的元素 通常，操作中涉及的对象根据它们何时参与消息序列从左到右列出。但是，水平轴上的元素可能会以任何顺序出现 时间维度 • 垂直轴表示页面下的时间程序（或进度）。 请注意： 序列图中的时间是所有关于排序，而不是持续时间。交互图中的垂直空间与交互持续时间不相关。

2.2 系统边界（System Boundary）

【解释】 A system boundary is a boundary that separates the internal components of a system from external entities. These entities can also be thought and be called as actors. In a use case diagram, a system boundary is represented by a rectangle that is drawn to enclosed the internal components of a system.

系统边界是将系统内部组件与外部实体分开的边界。这些实体也可以被思考并称为参与者。在用例图中，系统边界由矩形表示，该矩形绘制到系统的内部组件中。

【链接】 https://www.answers.com/Q/What_is_a_system_boundary

https://www.sciencedirect.com/topics/agricultural-and-biological-sciences/system-boundary

https://www.visual-paradigm.com/VPGallery/usecase/SystemBoundary.html

【正文】 The element properties of the system boundary element include the name, border style, and the number of horizontal or vertical lanes. You can also change the overall shape of system boundaries. You can use the context menu of an element to mark a system boundary element as optional. If the element is not optional, you can click the other elements in the System Boundary space without activating or selecting the System Boundary itself. Notes. • The system boundary is the basis of the Image element, which allows you to add icons or backgrounds to the chart and automatically Display The Image Manager window, from which you can select the appropriate image • System boundaries are different from the boundary elements used to capture user interaction, such as analysis diagrams

【翻译】 系统边界元素的元素属性包括名称，边框样式以及水平或垂直泳道的数量。您还可以更改系统边界的整体形状。 可以使用元素的上下文菜单将系统边界元素标记为“可选”。如果元素不可选，则可以单击“系统边界”空间中的其他元素，而不激活或选择“系统边界”本身。 笔记 • 系统边界是Image元素的基础，它允许您向图表添加图标或背景，自动显示图像管理器窗口，从中选择适当的图像 • 系统边界与用于捕获用户交互的边界元素不同，例如，分析图

2.3应用程序域（Application Domain）

【解释】 An application domain is the segment of reality for which a software system is developed. It is the background or starting point for the actual-state analysis and the creation of a domain model. An application domain can be an organization, a department within an organization, or a single workplace.

应用程序域是开发软件系统的现实部分。它是实际状态分析和创建域模型的背景或起点。应用程序域可以是组织、组织内的部门或单个工作场所。 应用程序域的概念至少是一样宽，因此在分析域的实际状态时，可以很好地理解与模型构造相关的域概念和关系。另一方面，其程度应始终有限，即绝不过于复杂。

【链接】 https://www.techopedia.com/definition/5220/application-domain-net

https://www.sciencedirect.com/topics/computer-science/application-domain

https://www.name.com/domains/app

【正文】 An application domain is a logical isolation boundary created around .NET applications so that applications do not access or affect each other. Application domain has features similar to that of a process.Application domains have the following features:

1. Optimum utilization of system resources by using fewer processes to execute multiple applications.
2. Reliability by using isolation of tasks in situations where data cannot be shared and for unstable tasks that need to be unloaded without affecting the process.
3. Better efficiency by executing long-running processes that rarely use large extensions with optimal memory.
4. Application security by restricting the direct access to the code running in one application from the code or resources of another application.
5. Security control by specifying configuration details along for each application domain.

【翻译】 应用程序域是围绕NET应用程序创建的逻辑隔离边界，以便应用程序不会访问或相互影响。应用程序域具有类似于进程的功能。应用程序域具有以下功能：

1. 通过使用更少的进程来执行多个应用程序，优化系统资源的利用率。
2. 在无法共享数据的情况下对任务进行隔离，以及在不影响进程的情况下对需要卸载的不稳定任务使用隔离来可靠性。
3. 通过执行很少使用具有最佳内存的大型扩展的长时间运行的进程，提高效率。
4. 通过限制从另一个应用程序的代码或资源对在一个应用程序中运行的代码的直接访问来实现应用程序安全性。
5. 通过为每个应用程序域指定配置详细信息来进行安全控制。 2.4变更控制板（Change control board）

【解释】 The main role of the change control board is to accept/reject change requests to the project.

变更控制委员会的主要作用是接受/拒绝对项目的变更请求。

【链接】 https://project-management-knowledge.com/definitions/c/change-control-board-ccb/

https://simplicable.com/new/change-control-board

https://study.com/academy/lesson/change-control-board-process-best-practices.html

【正文】 A change control board (CCB) is a group of individuals within the company that review and prioritize the change requests related to a project. This group can be as small as the project manager and the person who has sponsored the project, or as large as a committee of representatives who represent various functions within the organization. Some members can be directly impacted by the project, but it is no