真好,哈!
含有 ‘nccumis’標籤(tag)的文章們
usual word for quoting statements in papers
In 02 備忘錄、20 校園、22 研究方向、40 專業領域、博班生活 on 十月 25, 2008 at 1:39 上午Gramma:
Author_Name(Published_Year) + Words_of_Listing + Quote_Statement
Words_of_Listing
- point out
- mention
- indicate
- emphasize
- address
- present
- note
- discuss
從 Prof. Yu 上課之中整理出來的
NCCU MIS Seminar ~海角七號~ 網路行銷專題演講
In 02 備忘錄、20 校園、博班生活 on 十月 13, 2008 at 2:25 上午| From PhD_Seminar 08′ |
[ISDPM]上課筆記
In 02 備忘錄、20 校園、21 碩班課業、40 專業領域 on 五月 5, 2008 at 9:09 下午# 策略目標->行動->要定評估方式->反應達到目標與否。學校評鑑、政策研考也是一樣,要有明確的評估方式。
# critical success factors and end-means 方式去建立評估項目
## critical success factors 找 key person 來面談, 還可以使用 delphi(一致性、集中性) or focus group, AHP
## 意見要收斂,建立 stop rules
## AHP 會做到績效指標
# 規劃標與建置標不能同一組人,因為怕難的都不做;監審標,監工、審察、考核
# 規劃->分析->設計->執行->控制->評估、修改->完成
## 成本移轉與技術移轉都很重要
## 工作計劃書,工作說明
## 工作分解結構(work branch-down analysis)設計
## 組織分解結構(organization branch-down structure)設計
## 工作流程設計
## 專案工作排程,PERL+CPM (critical path method)
# key topic
## on time
## on budget (cost)
## full functionality (quality)
## user acceptance **
## favorable costs-to-benefits ratio
## low maintenance, modeling and documenting
## scalability
## integration with other systems
## minimal negative cross impacts
## reusability
# risk model = probability + impact, avoid, transfer and recovery
chapter 8
# PMBOK 的九大管理中,第一步都是 planing
# 在評估的方式:40%技術 20%管理 20%經費編列的合理性 5%簡報 15%過去資料
# 企劃書的規式與評審項目要對應
# element of project master plan, very good format!!
# vision > mission > objective
[ISDPM] 3/31 碩班上課
In 02 備忘錄、20 校園、21 碩班課業 on 三月 31, 2008 at 8:34 下午Review
- LAM 的意思
Today’s topic
- concurrency control: prevent dead lock.
- 不一定都會做到最高階的正規化
- 1NF 在解決 repeating groups, 用填值的方式
- 2NF 在解決 partial dependancies 部份相依(也是在處理 composite key 的問題, 多出來的欄位就是 composite entity)
- 3NF 在解決 transitive dependancies 遞移相依(JOB_CLASS ->決定 -> CHG_HOUR, 且造出 JOB_ID)
- BCNF 就是超過一個決定項的,就是 BCNF,
- 4NF, 解決 multi-value dependencies
- Data warehouse: 多面項、多維度的整合資料庫群
- Star schema: fact 出去依維度擴張,snowflake schema: 維度可以分得更細,fact constellation: 2 個以上。
[ISDPM] 3/24 碩班上課
In 02 備忘錄、21 碩班課業 on 三月 26, 2008 at 7:04 下午- 外部觀點與邏輯存取路徑(LAM), logic access map
- logical independence = program-data independence
- user view (external model), like form and screen (application level) -> internal model
- 表單畫面 -> 企業法則 -> 規類資料屬性 -> 定出 entities -> 找出 entities 的關係 -> 定義名稱 -> 定出 cardinality -> double check,
- composite entity -> composite key
- 由 user view 所設計的 internal model (04-16), 再依不同的 user view 切出,然導引程式編寫。LAM is from conceptual model mapping to difference user view
- DDL, DML, DCL
-
DDL – Data Definition Language: statements used to define the database structure or schema. Some examples:
- CREATE – to create objects in the database
- ALTER – alters the structure of the database
- DROP – delete objects from the database
- TRUNCATE – remove all records from a table, including all spaces allocated for the records are removed
- COMMENT – add comments to the data dictionary
- RENAME – rename an object
DML – Data Manipulation Language: statements used for managing data within schema objects. Some examples:
- SELECT – retrieve data from the a database
- INSERT – insert data into a table
- UPDATE – updates existing data within a table
- DELETE – deletes all records from a table, the space for the records remain
- MERGE – UPSERT operation (insert or update)
- CALL – call a PL/SQL or Java subprogram
- EXPLAIN PLAN – explain access path to data
- LOCK TABLE – control concurrency
DCL – Data Control Language. Some examples:
- GRANT – gives user’s access privileges to database
- REVOKE – withdraw access privileges given with the GRANT command
TCL – Transaction Control: statements used to manage the changes made by DML statements. It allows statements to be grouped together into logical transactions.
- COMMIT – save work done
- SAVEPOINT – identify a point in a transaction to which you can later roll back
- ROLLBACK – restore database to original since the last COMMIT
- SET TRANSACTION – Change transaction options like isolation level and what rollback segment to use
-
- **用 DDL 解決 DML 的問題,如:先定義 attribution,再定 entity;
- Jacobson’s requirement analysis: UML’s use case; Rumbaugh’s object modeling
- 查詢最佳化:時間、空間、運算子(如 join)->computational complexity
- cardinality 取定數量 1:3, connectivity 說要對誰處理
- 在 LAM 時就可以規劃出設計最佳查詢路徑


