[ISDPM]上課筆記

# 策略目標->行動->要定評估方式->反應達到目標與否。學校評鑑、政策研考也是一樣，要有明確的評估方式。
# 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] 4/7 碩班上課

get to know each other ^_^

Chapter 07

• 老師對不起，這天真的沒認真在上課
• 因為我的嘸蝦米壞了~ 上課都在reinstall 嘸蝦米

[ISDPM] 3/31 碩班上課

Review 

•  LAM 的意思
  • user view ->  ???  -> ER Model
  • 如果你是程式人員，給你個 LAM 你要怎麼做(下圖)
  • 
  • 寫的程式邏輯與 LAM 一致，也跟你說了 entity 的啟始點，及 entity 的對應關係。

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 碩班上課

Review

• 外部觀點與邏輯存取路徑(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

today Chapter 04

• 由 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

Chapter 5

• 查詢最佳化：時間、空間、運算子(如 join)->computational complexity
• cardinality 取定數量 1:3, connectivity 說要對誰處理
• 在 LAM 時就可以規劃出設計最佳查詢路徑

[ISDPM] 3/17 碩班上課

Review:

• IBM’s BSP
  • functions, processes, activities
  • tools: 2D matrices
• CSF
  • identify “GOAL”
  • critical factors that are essential to meeting objectives
  • find variables underlie these decisions, and how to measure
  • what information system can supply for these measure?
• E/M Analysis
  • Ends: system’s goal
  • Means: how to archive this goal
  • how to measure
• Mix CSF and E/M analysis
  • find out “GOAL”, defined critical success factor to objectives
  • find variables under objectives
  • using Means Specifications to migrate those variables into input and process
  • using efficiency measures and effectiveness  measure to evaluate means specifications

Today’s topic Chapter 3

•  需求階段可分成
  • user requirement: not very structure
  • user illustration 
  • system requirement: structure
• 三種需求 by science and engineering approach
  • 資訊需求：data, reports
  • 功能需求：一般如增、刪、修、查詢；資安功能需求…等
  • 作業需求：一系列的界面設計(網頁編排，I/O)與流程安排，提供給使用者操作。本作業需求必需支援組織流程。system operations.
• logical independence = program-data independence 
  •  政大資管所一定會考

Chapter 4

• 最小資料法則：所有需要的(資料)都已(被資料庫定義)包含，所有(被資料庫定義)包含的都是(拿來資料系統使用)需要的。而且需要被驗證。
• ER 出來的表，最少是 3rd 正規化的結果
• 使用 user requirements 來 verify E-R diagram 
• Business rules 如何在 E-R Diagram 中表現? using cardinality!
  • composite entity 是 E-R Diagram 掌控重心
  • 在 n:m 的實作，是以雙向的 1:n 來表現，中間是 composite entity
  • professor -> “teaches” -> class, connectivity 1:n, cardinality, 圈是 optional 可有可無
  • 上述的就是 cardinality

[ISDPM] 3/10 碩班上課

• top-down 與 button-up 之間的差別, 在 SDLC 的開發
• 所有系統開發法都是以 SDLC ，包括 原型法
  • {分析、設計、建置} -> {分析、設計、建置} -> {分析、設計、建置} refine 規格、架構
  • 讓使用者的議建及早進來
  • SDLC 只有一輪，原型則看 stoping rule {times, demean difference}
  • PSDLC, prototyping SDLC
• RAD: domain specified function modules ready, integrated platform, generating application to one application function
• EUD: providing user-friendly interface for administration units to generate reports, but not allow to update/change data structure (change/update must following by predefined biz process rules.)
• OOD: there are martin and Rumbaugh methods
  • (transit method) Martin: object structure analysis OSA, object behavior analysis OBA, class structure design CSD, methods design MD // how to identify object?
  • (application view)Rumbaugh’s Object Modeling Techniques, MOT: Analysis, Class, Object, Implementation; Object Model to Object diagram, Dynamic Model to state diagram, Functional Model to data flow diagram // how to analysis? by use cases: actors, functions, activities.
  • function will operate data within object
  • OOD’s relationship
    • inheritance(generalize and specialize), 
    • aggregation (composing), 
    • reference (implement interface) 
  • RDB’s relationship:
    • 1:n
    • n:1
    • n:m (ER Model)
    • inheritance, uninary, binary (EER Model) 
      
• HDM, slide pp. 25
  •  why hyper? v.s. linear space.
  • 從羅馬帝國開始談
  • there’s no conceptual model for information structure (using hyper concept!!!!)

資訊系統規劃, chapter 3 http://docs.google.com/Presentation?id=ddpk72gs_384gv482fg6

• SISP, strategic information system planning,
  • BSP, business systems planning, 高鐵
• functions, processes, activities.

[ISDPM] 3/3碩班上課

PPT: http://docs.google.com/Presentation?id=ddpk72gs_359dnxttpc9

* 方法 <-> 流程
(需求工程，Requirement Engineering；成本工程；某某工程，即用科學化、系統化的方法與流程)

* 規劃：

1. 就要談’可衡量的’目標及效益，KPI，找關建成功因素，再依其找到 end & means 及 weights (ex: AHP)
2. 範圍，誰用? 環境? 層級?
3. 需求分析、成本分析
4. 時間、人力、資源

* 分析

1. 資訊需求、功能需求、作業需求
2. 流程、功能、資訊、對象、目標、效益

* 設計
* 建置
* 操作
* 維護
* 控制
* 稽核

* 資訊服務業是創意產業

* 有趣的 Turban 版的 SDLC

* Prototyping

1. I/O prototyping, no db
2. function prototyping, only process
3. sub-sys prototyping, by functional dimension

* OOD, data/program independent by data behavior