❶ 軟體設計師需要學習哪些課程！！
UI課程-麥子學院ui免費下載
鏈接:https://pan..com/s/11U6exLBWPCbZ570GpQihEQ
UI課程-麥子學院ui|第一階段：軟體設計基礎|第四階段：項目設計實戰及提升|第三階段|第二階段：設計理論基礎|09AE動效設計概論和實操|08玩轉sketch|07交互設計之原型設計|06交互設計基礎|05移動UI設計實戰|04移動ui設計實戰|03移動UI設計規范（下）|02移動ui設計規范|01流程圖|9.excel繪制甘特圖.mp4
❷ 什麼是MS sql 2000, ColdFusion, .NET, UML, JavaScript/AJAX, CSS/DHTML, 它們的關系
sql是MS出的大型資料庫，coldfusion是adobe公司的一個功能強大的應用開發平台，.net是MS出的web開發平台,js是sun公司的，css/dhtml是網頁的格式類型，CSS是指用來定義網頁樣式的一種言語，現在特流行
你問的這些基本都是web方面應用的
❸ 怎麼把STAR UML 導入 SQL
你要看他有沒有反向工程功能，能不能支持模型導入sql，比如trufun plato建模工具有支持正向工程的框架，也有支持資料庫建模，支持將資料庫表反向生成資料庫模型，也可以將資料庫模型正向生成資料庫表和視圖！
❹ 輸入SQL Server原代碼，就可以生成UML類圖，其他的UML圖也可以。急呀，請告知。
不能夠用源代碼生成UNL的類圖,不過可以在SQL Server中已有的表進行生成的，使用工具PowerDesigner來生成就行,有關PowerDesigner的資料你可以去網上找找,有很多的
❺ SQL SERVER資料庫報824錯誤怎麼解決
Hi黑暗ㄨ吠，
824錯誤，也就是所謂的軟IO錯誤，可以理解為SQL Server已經讀取到該頁，但通過計算CheckSum等值發現不匹配，因此SQL Server認為該頁已經被損壞。此錯誤與錯誤 823 類似，只是 Windows 不檢測這一錯誤。這通常表明 I/O 子系統中存在問題，例如磁碟驅動器存在故障、磁碟固件存在問題、設備驅動程序不正確等等。查找硬體故障運行硬體診斷以解決任何問題。也可以通過檢查 Microsoft Windows 系統和應用程序日誌以及 SQL Server 錯誤日誌以查看是否存在由硬體故障引起的錯誤。解決這些日誌中包含的所有與硬體相關的問題。如果存在持久性數據損壞問題，請嘗試改用其他的硬體組件來解決此問題。進行檢查以確保系統未啟用磁碟控制器上的寫緩存。如果您懷疑是寫緩存出現問題，請與硬體供應商聯系。最後，您可能會發現，切換到全新的硬體系統是解決問題的極佳途徑。此切換操作可能包括格式化磁碟驅動器和重新安裝操作系統。如果出現的問題與硬體無關，並且已知的干凈備份可用，則請從備份中還原資料庫。考慮將資料庫改為使用 PAGE_VERIFY CHECKSUM 選項。
另外你也可以通過用WINHEX分析SQL Server文件的結構並更正，再DBCC檢查
更多SQL Server 824錯誤信息參考下面鏈接http://www.uml.org.cn/sjjm/201212041.asp。
Thanks,
Ice fan
❻ 資料庫相關，UML類表轉化Sql的題目
要求你轉換成sql語句。可以找一個工具正向工程就可以生成sql語句，順便你可以學習一下sql。
推薦trufun kant studio，可以到trufun官網免費下載。
更多uml問題可以到idehub社區咨詢，有uml技術人員在線解答，軟體工程領域各類問題，包括需求管理、資料庫建模、uml分析設計等。
❼ UML是什麼，包括哪些內容
解釋：
1、 UML -----The Unified Modeling Language is a standard language for writing software blueprints.The UML may be used to visualize, specify, construct, and document the artifacts of a software-intensive system.
2、 Stereotype-----A stereotype is an extension of the vocabulary of the UML, allowing you to create new kinds of building blocks similar to existing ones but specific to your problem.
3、 Tagged value-------A taffed value is a property of a stereotype, allowing you to create new information in an element bearing that stereotype.
4、 Component--------A component is a replaceable part of a system that conforms to and provides the realization of a set of interfaces.
5、 Message-----A message is the specification of a communication among objects that conveys information with the expectation that activity will ensure
6、 Note-----A note is a graphical symbol for rendering constraints or comments attached to an element or a collection of elements.
7、 Constraints------A constraint is a textual specification of the semantics of a UML element, allowing you to add new rules or to midify existing ones.
8、 Interaction-----An interaction is a behavior that comprises a set of messages exchanged among objects in a set of roles within a context to accomplish a purpose.
9、 Action----An action is an executable computation that results in a change in state of the model or the return of a value.
簡答
1， UML中描述軟體體系結構的五種視圖及其內容？architecture view
@The use case view of a system encompasses the use cases that describe the behavior of the system as seen by its end users,analysts,and testers.
@The design view of a system encompasses the classes,interfaces,and collaorations that from the vocabulary of the problem and its solution.
@The interaction view of a system shows the flow of control among its various parts,including possible concurrency and synchronization mechanisems.
@The implementation view of a system encompasses the artifacts that are used to assemble and release the physical system.
@The deployment view of a system encompasses the nodes that form the system`s hardware topology on which the system executes.
2， 建模的四項基本原則？principles of modeling
*The choice of what models to create has a profound influence on how a problem is attached and how a solution is shaped.
*Every model may be expressed at different levels of precision.
*The best models are connected to reality.
*No single model or view is sufficient.Every nontrivial system is best approached through a small set of nearly independent models with multipe viewpoints.
3，如何建模系統的接縫？modeling the seams in a system
To model the seams in a system:
!!Within the collection of classes and components in your system,draw a line around those that tend to be tightly coupled relative to other sets of classes and components.
!!Refine your grouping by considering the impact of change,
. Classes or components that tend to change together should be grouped together as collaborations.
!!Consider the operations and the signals that cross these boundaries, from instances of one set of classes or components to instances of other sets of classes and components.
!!Package logically related sets of these poerations and signals as interfaces.
!!For each such collabotation in your system,identify the interfaces it requires from(imports) and those it provides to others(exports).You model the importing of interfaces by dependency relationships,and you model the exporting of interfaces by realization relationships.
!!For each such interface in your system,document its dynamics by using pre-and postcongitions for each operation, and use cases and state machines for the interfaces as a whole.
4.如何建模系統的需求？modeling the requirements of a system
To model the requirements of a system:
//Establish the context of the system by identifying the actors that surround it;
//For each actor,consider the behavior that each expects or requires the system to privide;
//Name common behaviors as use cases.
//Factor common behavior into new use cases that are used by others;factor variant behavior into new use cases that extend more main line flows.
//Model these use cases,actors,and their relationships in a use case diagram;
//Adorn these use cases with notes or constraints that assert nonfunctional;you may have to attach some of these to the whole system.
5如何利用製品圖建模物理資料庫？modeling a physical database by artifact diagrams
1. For simple CRUD(create, read, update,delete) operations,implement them with standard SQL or ODBC calls;
2. For more-complex behavior(such as business rules), map them to triggers or stored proceres.
Guidelines:
&Identify the classes in your model that represent your logical database schema.
&Select a strategy for mapping these classes to tables.You will also want to consider the physical distribution or your databases.Your mapping strategy will be affected by the location in which you want yout data to live on your deployed system.
&To visualize,specify,construct,and document your mapping,create an artifact diagram that contains artifacts stereotyped as tables.
&Where possible,use tools to help you transform your logical design into a physical design.
6如何對注釋建模？modeling comments
*Put your comments as text in a note and place it adjacent to the element to which it refers. You can show a more explicit relationship by connecting a note to its elements using a dependency relationship.
*Remember that you can hide or make visible the elements of your model as you see fit.This means that you don`t have to which it is attached are visible.Rather,expose your comments in your diagram only insofar as you need to communicate that information in that context.
*If your comment is lengthy or involes something richer than plain text,consider putting your comment in an external document and linking or embedding that document in a note attached to your model.
*As your model evolves,keep those comments that record significant decisions that cannot be inferred from the model itself,and-unless they are of historic interest-discardthe others.
7，如何建模邏輯資料庫模式？modeling a logical database schema
The UML`s class diagrams are a superset of entity-relationship(E-R) diagrams, a common modeling tool for logical database design.
To model a schema:
$Identify those classes in your model whose state must transcend the lifetime of their applications.
$Create a class diagram that contains these classes.You can difine your own set of stereotypes and tagged values to address database-specific details.
$Expand the structural details of these classes.In general,this means spencifying the details of their attributes and focusing on the associations and their multiplicities that relate these classes.
$Watch for common patterns that complicate physical database design,such as cyclic association and one-to-one associations.Where necessary,create intermediate abstractions to simplify your logical structure.
$Consider also the behavior of these classes by expanding operations that are important for data access and data integrity.In general,to provide a better sepatration of concerns,business rules concerned with the manipulation of sets of these objects should be encapsulated in a layer above these persistent classes.
$Where possible,use tools to help you transform your logical design into a physical design.
8，給出順序圖的步驟？modeling flows of control by time ordering
To model a flow of control by time dodering:
+Set the context for the interaction,whether it is a system, subsystems,operations,or class,or one scenario of a use case or collabotation;
+Set the stage for the interantion by identifying which objects play a role in the interaction.Lay then out on the sequence diagram from left to right,placing the more important objects to the left and their neighboring objects to the right;
+Set the lifeline for each object.In most cases,objects will persist through the entire interaction. For those objects that are created and destroyed ring the interaction ,set their lifelines,as appropritate,and explicitly indicate their birth and death with appropriately stereotyped messages;
+Starting with the message that initiates this interaction, lay out each subsequent message from top to bottom between the lifelines,showing each message`s properties, as necessary to explain the semantics of the interaction;
+If you need to visualize the nesting of messages or the points in time when actual computation is taking place, adorn each object`s lifeline with its focus of control;
+If you need to specify this flow of control more formally, attach pre-and postconditions to each message.
9，如何利用製品圖建模可執行程序的發布？modeling an executable release
To model an executable release:
#Identify the set of artifacts you`d like to model.Typically,this will involve some or all the artifacts that live on one node,or the distribution of these sets of artifacts across all the nodes in the system.
#Consider the stereotype of each artifact in this set.For most systems you`ll find a small number of different kinds of artifacts.You can use the UNL`s extensibility mechanisms to provide visual cues for these stereotypes.
#For each artifact in this set, consider its relationship to its neighbors.Most often,this will involve interfaces that are exported by certain artifacts and then imported by others.If you want to expose the seams in your system,model these interfaces explicity.If you want your model at a higher level of abstraction, elide these relationships by showing only dependencies among the artifacts.
❽ 什麼是時態資料庫、和傳統資料庫有什麼不一樣還有中間件和UML，誰能簡要介紹下
區別於傳統的關系型資料庫(RDBMS)，時態資料庫(Temporal Database)主要用於記錄那些隨著時間而變化的值的歷史，而這些歷史值對應用領域而言又 時態資料庫是重要的，這類應用有：金融、保險、預訂系統、決策支持系統等。
目前時態資料庫還沒有像如Oracle、SQL Server等大型關系資料庫那樣的產品。在當前時態資料庫技術尚未完全成熟的現狀下，DBMS提供商不會輕易把時態處理功能引入現有的DBMS中，因此，利用成熟的RDBMS資料庫，建立時態資料庫的中間件，在現階段是一個較好的選擇，因此就應運而生TimeDB和TempDB了。
中間件是一種獨立的系統軟體或服務程序，分布式應用軟體藉助這種軟體在不同的技術之間共享資源。中間件位於客戶機/ 伺服器的操作系統之上，管理計算機資源和網路通訊。是連接兩個獨立應用程序或獨立系統的軟體。相連接的系統，即使它們具有不同的介面，但通過中間件相互之間仍能交換信息。執行中間件的一個關鍵途徑是信息傳遞。通過中間件，應用程序可以工作於多平台或 OS 環境。
可擴展標記語言 (Extensible Markup Language, XML) ，用於標記電子文件使其具有結構性的標記語言，可以用來標記數據、定義數據類型，是一種允許用戶對自己的標記語言進行定義的源語言。 XML是標准通用標記語言 (SGML) 的子集，非常適合 Web 傳輸。XML 提供統一的方法來描述和交換獨立於應用程序或供應商的結構化數據。
❾ 各位老師：UML是什麼，主要是干什麼用的請簡單說明
UML統一建模語言，哎，這么寫的話根本不知道是什麼吧
我舉個例子吧，sql
uml跟sql一樣，是一種語言，它是用來建模的（實體、用例等），使用在設計領域的
而我們通常說的uml指的是uml工具
比如visio里可以建uml工程，rose可以建uml工程等等，很多工具都能（就像oracle，sql server都能建資料庫，用sql語言訪問）
❿ UML的類圖可以轉換成SQL嗎
從用例圖過渡到類圖，用例圖一般是分析項目功能的，類圖是項目實現。
從用例圖到類圖，沒有直接的轉換關系，一般都是根據開發經驗。