Function Analysis and Design


We can learn from software deveopment technologies.

Function Analysis and Design

We can learn from software deveopment technologies.

Rough analysis of current practice in getting 'from idea to product' may be described in 'software programming style' below. It is still a rough draft of what 'work' (duty statements) would be done by ทำไทยทำ (makeThaiMake) organization.

For those who are not familiar with this short-hand style of specifying (work) funcions of a 'system':
- data objects are in normal font
- methods are in italic
- objects in () are used in performing the method
- objects in [] are data items
- {} denote the defined closure (world) of the system. R
- Relationships with other organizations are shown in diagram.

 
makeThaiMake(){
  /* data structures */
  idea=[id, type, descript, ownerid, status[],...];
  report[idea, status[], assessed[],...];
  patent[id, idea, *stage[country,step,date,...]
 
  /* internal methods:: private, secured, version */
  register(idea[],...)==> DB:Ideas
  update(idea)
  archive(idea)
  modify(idea)

  /* external methods:: public, secured, version */
  checkCopyright(idea, K1data, K2DB, ...) ==> patent[]
  evaluate(idea, category, criteria[],...) ==> report[]
  raiseFund(idea, investorsList, ...) ==> portfolio[]
 
  make(idea,...) ==> product /* like software "make" */
  test(idea, *product,...) ==> *assessment[]
 
  setPrice(...)   /* from costs and market demand */
  package(...) ==> product    /* final product presentation */
  distribute(...) /* marketing and sales */
  fixBugs(...)
  upgrade(...) ==> better product
 
  ...
}

This is a simple but effective way of defining an overview of what an organization (system) must do to serve its purpose. (Software) Agents are then created and set out to perform these methods as required. Human organizations get set up very much in this way, but human agents are recruited to perform their 'duties statement' and the results reviewed to ensure complete and correct things have been done in given time.

NB. Software agents and robots are perceived more as 24/7 workers, reliable, uncomplaining, getting less expensive,... They could be marching in to replace human any day soon.

หมายเลขบันทึก: 486939เขียนเมื่อ 3 พฤษภาคม 2012 15:12 น. ()แก้ไขเมื่อ 21 มิถุนายน 2012 20:57 น. ()สัญญาอนุญาต: ครีเอทีฟคอมมอนส์แบบ แสดงที่มา-ไม่ใช้เพื่อการค้า-อนุญาตแบบเดียวกันจำนวนที่อ่านจำนวนที่อ่าน:


ความเห็น (0)

ไม่มีความเห็น

พบปัญหาการใช้งานกรุณาแจ้ง LINE ID @gotoknow
ClassStart
ระบบจัดการการเรียนการสอนผ่านอินเทอร์เน็ต
ทั้งเว็บทั้งแอปใช้งานฟรี
ClassStart Books
โครงการหนังสือจากคลาสสตาร์ท