个人作业——A002-185-2513-吴光华

浅浅的花香味﹌ 2023-01-01 07:56 103阅读 0赞

软件建模与分析专题报告  
课程名称 需求分析与建模 班级 18软件工程5班  
实验名称 专题报告 教导教师 董瑞生  
姓名 吴光华 学号 1814080902513 日期 2020年12月20日

目录  
1.单词查找 4  
1.01Requirements baseline（需求基线） 4  
1.02abstract class（抽象图） 4  
1.03action sequence（动作顺序） 4  
1.04activity graph（活性图） 4  
1.05aggregate（聚合） 4  
1.06architecture（建筑学） 4  
1.07argument（论点） 4  
1.08artifact（人工制品） 4  
1.09association class（关联类） 4  
1.10boolean expression（布尔表达式） 4  
1.11component diagram（组件图） 5  
1.12collaboration diagram（协作图） 5  
1.13interaction diagram（交互作用图） 5  
1.14internal transaction（内部交换图） 5  
1.15interative development（互动发展） 5  
1.16logical view（逻辑视图） 5  
1.17model element（模型元素） 5  
1.18multiple classification（多重分类） 5  
1.19multiple inheritance（多重继承） 5  
1.20n-ary association（n元关联） 5  
1.21action sequence（动作顺序） 6  
1.22aggregate\[class\]（总计） 6  
1.23delegation（代表团） 6  
1.24domain（领域） 6  
1.25dynamic classification（动态分类） 6  
1.26context model（上下文模型） 6  
1.27decision table（决策表） 6  
1.28functional requirement（功能需求） 6  
1.29quality requirement（质量需求） 6  
1.30disjoint substate（不相交状态） 6  
1.31distribution unit（配电装置） 6  
1.32inheritance（继承） 6  
1.33interatction diagram（互交图） 7  
1.34metaclass（元类） 7  
1.35parameter（参数） 7  
1.36participates（参与） 7  
1.37recelver（接收器） 7  
1.38reference（参考） 7  
1.39schema（架构） 7  
1.40stimulus（刺激） 7  
1.41supplier（供应商） 7  
1.42transient object（暂时对象） 7  
1.43tagged value（标记值） 7  
1.44synchronous action（同步作用） 8  
1.45swimlane（泳道） 8  
1.46submachine state（子机状态） 8  
1.47stereotype（模式化） 8  
1.48scenario（脚本） 8  
1.49refinement（改良） 8  
1.50dynamic classification（动态分类） 8  
1.51generalizable element（概化元素） 8  
1.52interface inheritance（接口继承） 8  
1.53modeling conventions（建模约束） 9  
1.54Persistent Objects（持久性对象） 9  
1.55use-case diagram（用例图） 9  
1.56view projection（视图投影） 9  
1.57business reengineering（企业重组） 9  
1.58class hierarchy（类层次结构） 9  
1.59defect density（缺陷密度） 9  
1.60changeability（可变性） 9  
1.61configuration（配置） 9  
1.62context diagram（上下文关系图） 9  
1.63correctness（正确性） 10  
1.64dataflow diagram（数据流图） 10  
1.65effectiveness（有效性） 10  
1.66effciency（效率） 10  
1.67entity relationship diagram（实体关系图） 10  
1.68fault tolerance（容错） 10  
1.69Glossary（词汇表） 10  
1.70hommony（不恰当） 10  
1.71inspection（检查） 10  
1.72maintainability（可维护性） 10  
1.73priority of a requirement（需求的优先级） 10  
1.74process verb（过程动词） 11  
1.75prototype（原型） 11  
1.76Redundancy（冗余） 11  
1.77requirements analysis（需求分析） 11  
1.78requirements elictation（删除需求） 11  
1.79requirements sqpecification（需求规格） 11  
1.80security（保护措施） 11  
1.81semantics（含义） 11  
1.82synonym（同义词） 11  
1.83traceability of requirements（需求的可塑性） 11  
1.84validation of requirements（需求的确认性） 11  
1.85verifiability of requirments（需求的可验证性） 11  
1.86view（看法） 12  
1.87viewpoint（观点） 12  
1.88walkthrough（走读） 12  
1.89version of an entity（实体） 12  
2.需求分析与建模读书心得 12  
3.我对项目的发展建议 13

1.  单词查找  
    1.01Requirements baseline  
    A  baseline for a set of  requirements.

1.02abstract class  
A class that cannot be directy instantiated. Contrast:concerte class.

1.03action sequence  
An expresssion that resolves to a sequence of actions.

1.04acitivity graph  
A special case of a state machine that is used to model processes involving one or more classifiers. Contrast: statechart diagram.

1.05aggregate  
A class that represents the “whole” in an aggregation relationship. See:aggregation.

1.06architecture  
The organizational structure of a system. An architecture can be recursively decomposed into parts that interact through inferfaces,relationships that connect parts, and constraints for assembling parts. Parts that interact.

1.07argument  
A binding for a parameter that resolves to a run-time instance.Synonym:actual parameter.Contrast:parameter.

1.08artifact  
A piece of information that is used or produced by a software development process.An artifact can be a model, a description, or software.

1.09association class  
A model element that has both association and class properties. An association class an be seen as an association that also has properties, or as a class that also has association properties.

1.10boolean expression  
An expreession that evaluates to a boolean value.

1.11component diagram  
A diagram that shows the organizations and dependencies among components.

1.12collaboration diagram  
A diagram that shows interactions organized around the atructure of a model,using either classifiers and associations or instances and links.Unlike a sequence diagram, a collaboration diagram shows the relationships among the instances. Sequence diagram and collaboration diagrams express similar information, but show it it in different ways.

1.13interaction diagram  
A generic term that applies to several types of diagrams that emphasize object interactions. These include: collaboration diagrams, sequence diagrams, and activity diagrams.

1.14internal transaction  
A transition signifying a response to an event without changing the state of an object.

1.15interative development  
Iterative development, also known as iterative incremental development or iterative evolutionary development, is a software development process opposite to the traditional waterfall development. It makes up for some weaknesses in the traditional development method and has higher success rate and productivity.

1.16logical view  
The logical view provides a hierarchical view of a project’s structure. With the logical view, users can create and customize the diagrams in their projects with meaningful categorization by adding domain-specific view(s).

1.17model element  
An element that is an abstraction drawn from the system being modeled. Contrast: view element.

1.18multiple classification  
A semantic variation of generalization in which an object may belong directly to more than one class. See: dynamic classification.

1.19multiple inheritance  
A semantic variation of generalization in which a type may have more than one supertype. Contrast: single inheritance.

1.20n-ary association  
An association among three or more classes. Each instance of the association is an n-tuple of values from the respective classes. Contrast: binary association.

1.21action sequence  
An expression that resolves to a sequence of actions.

1.22aggregate\[class\]  
A class that represents the "whole"in an aggregation (whole-part)relationship.

1.23delegation  
The ability of an object to issue a message to another object in response to a message. Delegation can be used as an alternative to inheritance. Contrast: inheritance.

1.24domain  
An area of knowledge or activity characterized by a set of concepts and terminology understood by practitioners in that area

1.25dynamic classification  
A semantic variation of generalization in which an object may change type or role. Contrast: static classification.

1.26context model  
A model describing a system in its context.

1.27decision table  
A tabular,systematic representation of a complex decision that depends on multiple criteria.

1.28functional requirement  
A requirement concerning a result of behavior that shall be provided by a function of a system(or of a component or service).

1.29quality requirement  
A requirement that pertains to quality concern that is not covered by functional requirements.

1.30disjoint substate  
A substate that cannot be held simultaneously with other substates contained in the same composite state. See: composite state. Contrast: concurrent substate.

1.31distribution unit  
A set of objects or components that are allocated to a process or a processor as a group. A distribution unit can be represented by a run-time composite or an aggregate.

1.32inheritance  
The mechanism by which more specific elements incorporate structure and behavior of more general elements related by behavior. See generalization.

1.33interatction diagram  
A generic term that applies to several types of diagrams that emphasize object interactions. These include: collaboration diagrams, sequence diagrams, and activity diagrams.

1.34metaclass  
A class whose instances are classes. Metaclasses are typically used to construct metamodels.

1.35parameter  
The specification of a variable that can be changed, passed, or returned. A parameter may include a name, type, and direction. Parameters are used for operations, messages, and events. Synonyms: formal parameter. Contrast: argument.

1.36participates  
The connection of a model element to a relationship or to a reified relationship. For example, a class participates in an association, an actor participates in a use case.

1.37recelver  
The object handling a stimulus passed from a sender object. Contrast: sender

1.38reference

1.  A denotation of a model element. 2. A named slot within a classifier that facilitates navigation to other classifiers. Synonym: pointer.

1.39schema  
In the context of the MOF, a schema is analogous to a package which is a container of model elements. Schema corresponds to an MOF package. Contrast: metamodel, package.

1.40stimulus  
The passing of information from one instance to another, such as raising a signal or invoking an operation. The receipt of a signal is normally considered an event. See: message.

1.41supplier  
A classifier that provides services that can be invoked by others. Contrast: client.

1.42transient object  
An object that exists only during the execution of the process or thread that created it.

1.43tagged value  
The explicit definition of a property as a name-value pair. In a tagged value, the name is referred as the tag. Certain tags are predefined in the UML; others may be user defined. Tagged values are one of three extensibility mechanisms in UML. See: constraint, stereotype.

1.44synchronous action  
A request where the sending object pauses to wait for results. Contrast: asynchronous action.

1.45swimlane  
A partition on a activity diagram for organizing the responsibilities for actions. Swimlanes typically correspond to organizational units in a business model. See: partition.

1.46submachine state  
A state in a state machine which is equivalent to a composite state but its contents is described by another state machine.

1.47stereotype  
A new type of modeling element that extends the semantics of the metamodel. Stereotypes must be based on certain existing types or classes in the metamodel. Stereotypes may extend the semantics, but not the structure of pre-existing types and classes. Certain stereotypes are predefined in the UML, others may be user defined. Stereotypes are one of three extensibility mechanisms in UML. See: constraint, tagged value.

1.48scenario  
A specific sequence of actions that illustrates behaviors. A scenario may be used to illustrate an interaction or the execution of a use case instance. See: interaction.

1.49refinement  
A relationship that represents a fuller specification of something that has already been specified at a certain level of detail. For example, a design class is a refinement of an analysis class.

1.50dynamic classification  
Dynamic classification also known as “dynamic typing” deals with the capability of changing the “object classification”. The object may vary its classification in its existence. For example, the below diagram shows the dynamic classification of person’s job.

1.51generalizable element  
A generalization is a binary taxonomic (i.e. related to classification) directed relationship between a more general classifier (superclass) and a more specific classifier (subclass).

1.52interface inheritance  
Interface inheritance is nothing but the implementation of interfaces. A class may implement any number of interfaces.

1.53modeling conventions  
Modeling conventions can be a great way for aspiring models to gain exposure and get discovered.

1.54Persistent Objects  
When using the DPL, you store data in the underlying JE databases by making objects persistent. You do this using Java annotations that both identify the type of persistent object you are declaring, as well as the primary and secondary indices.

1.55use-case diagram  
A UML use case diagram is the primary form of system/software requirements for a new software program underdeveloped. Use cases specify the expected behavior (what), and not the exact method of making it happen (how).

1.56view projection  
The View Projection tool (also called the Project from View tool) creates a UV map of the currently selected polygons based on their visibility in the 3D viewport. The final UV map reflects the selected polygons as they appear in the viewport, itself, similar to taking a photograph of them.

1.57business reengineering  
Business process reengineering is a crucial element in the agenda of many large as well as small companies in many industries, with manufacturing and banking/ finance being the leading sectors. It allows organizations to view their business processes from a fresh perspective in order to understand how to redesign them to improve the way they work.

1.58class hierarchy  
As in taxonomy, the classifications of species, a class hierarchy in computer science is a classification of object types, denoting objects as the instantiations of classes inter-relating the various classes by relationships such as “inherits”, “extends”, “is an abstraction of”, “an interface definition”.

1.59defect density  
Defect Density is the number of defects confirmed in software/module during a specific period of operation or development divided by the size of the software/module. It enables one to decide if a piece of software is ready to be released.

1.60changeability  
The adegree to which an artifact enables a required modification of the artifact.

1.61configuration  
A consistent set of logically coherent units. The usits are individually identifiable artifacts or parts of artifacts in at most one version per unit.

1.62context diagram  
1.A diegram matic representation of a context model.2.In Structured Analysis, the conext diagram is the root of the dataflow diagram diagram hierarchy.

1.63correctness  
The degree to which the information contained in an artifact is provably true.

1.64dataflow diagram  
A diagram modeling the functionality of a system or component by processes, data stores and data flows. Incoming data flows trigger processes which then consume the received data, transform them, read/wirte persistent data held in data stores and then produce new data flows which may be intermediate results that trigger other processes or final results that leave the system.

1.65effectiveness  
The degree to which something actually happens in the way it ought to happen.

1.66effciency  
The degree to which a result is achieved with minimum consumption of resources.

1.67entity relationship diagram  
A graphic representation of an entity-relationship model.

1.68fault tolerance  
The capability of a system to continue normal operation despite the presence of faults.

1.69Glossary  
A collection of dfinitions of terms that are relevant in osme domain. Frequently, a glossary also contains cross-references, synonyms, homonyms, acronyms, and abbreviations.

1.70hommony  
A term looking identical to another term, but having a different meaning.

1.71inspection  
A kind of review where the artifact under review is inspected by a group of experts according to given criteria. The experts’findings are then collected and consolidated.

1.72maintainability  
The ease with which a softwqre system can be modified to correct faults or adapt the system to changing needs.

1.73priority of a requirement  
Documents the importance of a requirement in comparison to other requirements according to given criteria.

1.74process verb  
A verb characterizing the required action in a requirement written in natural language.

1.75prototype  
1.In manufacturing: a piece which is built prior to the start of mass production.

1.76Redundancy  
Multiple occurrence of the same information or resource.

1.77requirements analysis  
1.Analysis of elicited requirements in order to understand and document them.

1.78requirements elictation  
The process of seeking, capturing and consolidating requirements form available requirements sources. May include the re-construction or creation of requirements.

1.79requirements sqpecification  
A systematiclly represented collection of requirements, typically for a system or compoent, that satisfies given criteria.

1.80security  
The capability of a system to protect its data and resources against unauthorized use and its legitimate users against denial of aervice.

1.81semantics  
The meaning of a sign or a set of signs in a langusge.

1.82synonym  
A word having the same meaning as another word.

1.83traceability of requirements  
The ability to trace a requiremment back to its origins,forward to its implementation in design and code, to requirements it depends on. Origins may be stakeholders, documents, rationale,etc.

1.84validation of requirements  
The process of checking wheter documented requirements match the stakeholders’needs.

1.85verifiability of requirments  
The degree to which the fulfillment of a requirement by an implemented system can be checked,e.g., by defining acceptance test cases, measurements or inspection procedures.

1.86view  
An excerpt from an artifact, containing only those parts one is currently interested in.

1.87viewpoint  
A certain perspective on the requirements of a system.

1.88walkthrough  
A kind of review where the author of an artifact under review walks a group of experts systematically throungh the artifact. The experts’findings are then collected and consolidated.

1.89version of an entity  
If an entity exists in multiple, time-ordered occurrences, where each occurrence has been created by modifying one of its predecessors, every occurrence is a version of that entity.

1.  需求分析与建模读书心得  
    我在单词查找中有挺多的收获，因为在Enterprise Architect中，该软件中的所有功能都是英文命名，如果不认识英文单词这些专业术语，那么我们将很难把软件建模与分析这门课程学好，所以我们要积极主动的把这些专业术语学好，但是学会专业术语是远远不够的，需要理解术语的意思，这样我们才算是真的把它学懂。  
    我看我在前期查找的单词，大部分都是老师在前半学期的作业中，我们也要了解EA中各个功能图的作用，在了解功能图的过程中，我遇到了很多不理解的单词，这些单词单词不理解，我们很难到掌握并理解功能图的作用，那么查找单词势在必行，因为我的英语基础比较薄弱，所以我在查找的过程采用了双管齐下的方法，在外网查一遍，在百度翻译一遍，这样做也让我更好的理解单词的原意，这些都是前期我们的遇到的问题，和我们的解决方案。到了我课程的后半段，老师开始让我们实践操练，让我们的功能图和小组项目相结合进行建模。我开始是有些措手不及的，一个是认为自己的积累还是太少了，另一个是理解功能图的作用到结合项目建模，首先要理解功能图，然后要对项目进行分析，最后才是进行建模设计，这看似简单，事实上却增加了很大的难度。回到单词查询的上，我们对功能图进行了解，查找翻译，但这不是大头，遇到单词最多不懂得地方是在设计建模时，我们很多时候不知道图的组件或工具应该使用那个，这些都代表着什么意思，这些才是真正困扰着我的地方，使得我需要不断地查阅单词资料，同样采用双管齐下的方法，最后再完成设计建模。  
    以上是我在建模遇到的问题，然后针对这些问题问题，我去进行单词查找，最后一一解决的过程。  
    在单词查找的过程，也是我对需求分析与建模的过程，我们要了解到要从什么方向对项目分析，那么我们确定了分析方向后，要对项目的需求进行分析，对项目分析后我们最后才进行建模。在课程的后半段老师要求我们结合项目进行分析建模，我刚开始做的很慢，几乎要花费一个下午的时间，有三个原因：第一个是我对项目的了解不够深入，其实就是需求不明确；第二个是我对EA的使用不太熟练；第三个是我在设计建模的时候多次进行单词查询。但是付出的时间总是和收获成正比，我在之后的作业中，设计建模都一次比一次快，并且考虑的更加周全，分析的更见透彻，通过最后的几次作业，我对需求分析和建模有更加深入的了解，也觉得学习这门课程非常的实用，它可以从多个方面对项目进行分析，同时对项目的实现具有指导意义。
2.  我对项目的发展建议  
    我通过对绿小萝项目的建模分析，我认为绿小萝的业务过于的单一，即便是它在界面或者是系统上进行非常多的优化，也不能改变它功能单一的缺点。要想改变这一不足的情况，建议对绿小萝的业务进行拓展。  
    在业务的拓展上，我认为有两个方向是也行的。第一个，因为我们原来的业务是去除甲醛，提倡健康环保，那么我们可以从绿色环保这一点，在页面上向用户推销绿色、健康、环保的装修材料，而这些产品来自于其他公司的，绿小萝在销售中承担着代理销售的作用，不过这会使得绿小萝的系统功能更加复杂，需要实现同某宝中的部分功能。总的来说，我认为利大于弊，可以让绿小萝的业务多样化。第二个，为绿小萝的业务就是去除用户装修时残留在新房中的甲醛，这里我们也可以拓展装修设计的平台，为用户提供各种各样的装修设计方案，或者装修风格，还有用户也可以自主联系设计师，告诉他想要的设计风格，最后设计师再提供设计方案。在这其中室内装修设计师可以是绿小萝长期聘请的，也可以是短期的，不过该业务的功能实现在于为用户与设计师提供一个很好的对话平台，其中用户和设计师是一对一，而设计师和用户则是一对多，同时要有回复提示等功能。