CY ERP system project

  1. Objectives
  2. Contents
    1. Initiatives
    2. Strategies
    3. Tactics
    4. Stages
  3. Industry
    1. WordPress + Search = Knowledge management
    2. OA + Wechat approval and comments = Mobile OA
    3. Barcode at W01 / Sampling mgt / WIP transfer
  4. Approach
    1. Critical Success factors
      1. Top management commitment
    2. Barriers:
      1. Resistance to Change
      2. Inadequate management support
      3. Unrealistic or unclear expectations
    3. Stages
      1. Pre
      2. Post
      3. More value added
    4. Strategic
    5. Tactic
    6. Operational
  5. Research keywords
  6. Good reports
    1. Loading 完工入庫% with outstanding number
    2. Loading 完工入庫% with outstanding number (w/ WIP)
  7. References
    1. Academic sources:
    2. White papers / advices:
      1. Five Critical Success Factors for ERP Implementations. https://www.panorama-consulting.com/five-critical-success-factors-for-erp-implementations/
    3. What role does “Top Management” play in the Implementation? http://www.manufacturingpractices.com/FAQRetrieve.aspx?ID=37072
Advertisements
CY ERP system project

CC7173 – WK8 (21Nov2017)

  1. Contents – Summary
    • SQL DB concepts
      • stores data to a text file on an Android device
      • SQL language
      • Neither server-side nor client-side
      • without a database installation or administration
      • Latest version 2.0
      • Developed by SQLite Consortium
      • Goals: to be simple
      • No access control
    • How to use SQLite database
      • create a separate class for the database
      • name it DBHelper(DatabaseHelper)
      • must implement the SQLiteOpenHelper which provides various methods to interact with the database
        • public class DBHelper extends SQLiteOpenHelper {
        • }
      • DBHelper Class contains 2 very important methods; onCreate and onUpgrade
        • onCreate
          • method gets called when the database is created for the first time
            • @Override
            • public void onCreate(SQLiteDatabase db) {
            • // create students table
            •               execSQL(CREATE_TABLE_STUDENTS);
            •                                                }
          • ContentValuesallow defining key/value pairs. The key represents the table column name and the value represents the content corresponding to that column
          • Operations
            • Create table
            • Insert
            • Update
            • Delete
            • Read: A cursor points to one row at a time;
              • rawQuery(sql_statement, null);
              • if c!= null //not empty, move cursor to first;
              • moveToNext()
            • onUpgrade
            • ArrayList<>: read data to memory
          • Examples
            • Table Structure
            • Interface design
  1. Contents – Detailed
    1. Disadvantage of SQLite:
      1. High concurrency: reader / writer locks on the entire file;
      2. Huge datasets: DB file can’t exceed file system limit or 2TB;
      3. No access control;
    2. To add SQLite database connectivity in Android:
      1. create a separate class for the database, such as DBHelper(DatabaseHelper);
      2. Then, DBHelper class must implement the SQLiteOpenHelper which provides various methods to interact with the database
        1. public class DBHelper extends SQLiteOpenHelper { }
      3. Two critical methods in DBHelper class: onCreate and onUpgrade;
      4. onCreate
        1. gets called when the database is created for the first time;
        2. Tables would be created inside this method
        3. @Override

          public void onCreate(SQLiteDatabase db) {

          // create students table

          db.execSQL(CREATE_TABLE_STUDENTS);

          }

      5. onUpgrade
        1. allows you to upgrade your database
        2. update an existing databasedrop existing tables, and recreate it via the onCreate() method
  2. References
    1. SQLite Home Page. http://www.sqlite.org/
    2. SQLite Consortium. http://www.sqlite.org/consortium.html
  3. Follow-ups
CC7173 – WK8 (21Nov2017)

CC7174 – Book1

Fundamentals of Database Systems – 6/e – Navathe Elmasri

ANSI-SPARC 3 levels

  1. Contents – Summary
    1. Chapter 1 – Databases and Database Users
  2. Contents – Detailed
    1. Chapter 1 – Databases and Database Users
      1. 1.8 – When not to use a DBMS
        1. Simple and well-defined DB applications that are not expected to change;
        2. Real-time requirements for some application programs that may no be met because of DBMS overhead
        3. Embedded systems with limited storage capacity
          1. such as CAD tools used by mechanical and civil engineers have proprietary file and data management software;
          2. communication and switching systems that was made to run very fast for quick access and routing of calls;
          3. GIS implementation related to processing of maps, physical contours, lines and polygons;
    2. Chapter 2 – Database Environement
      1. Major aim of DB system: provide an abstract view of data;
        1. Modeling: Entities, attributes, relationships;
        2. Three-level ANSI-SPARC architecture
          1. ANSI-SPARC (The American National Standards Institute Standards Planning and Requirements Committee)
          2. External, Conceptual & Internal level;
            1. Separate each user’s view of the database
            2. Internal level:
              1. DBMS and the operating system perceive the data;
              2. physical representation of the database on the computer;
              3. describes how the data is stored in the database;
            3. Conceptual level:
              1. what data is stored in the database and the relationships among the data;
              2. community view of the database;
              3. seen by the DBA;
            4. External level:
              1. user’s view of the database;
              2. different views of the data;
            5. Physical data organization, such as storage media..
          3. Schemas, Mappings and Instances
            1. Database schema: overall description of the database;
              1. external schemas <> conceptual schema <> internal schema;
              2. DDL is used to specify the database schema
              3. DML is used to read and update the database
                1. procedural
                2. Nonprocedural: the user defines what is to be done, not how; such as 4GL;
          4. Data models and conceptual modeling
            1. Data model
            2. Object-based data models
            3. Record based data models
              1. relational data model
              2. network data model
              3. hierarchical data model
            4. Physical data models: how data is stored in the computer, such as record structures, record orderings and access paths; unifying model and the frame memory;
            5. Conceptual modeling
CC7174 – Book1