(Week 11) A06. IS Analysis & Design Management Information Systems

(1)

WKU / Management Information Systems / 2015-2-WKU-MIS-A06.pptx / Prof. Dr. SSL in IDEA+STEM of FP by C for LDV / pp. 1

•Course Code: 166137-01

•Course Name: Management Information Systems

•Period: Autumn 2015

•Lecturer: Prof. Dr. Sync Sangwon Lee

•Department: Economics

•University: WONKWANG

(Week 11)

A06. IS Analysis & Design

Management Information Systems

• 6.1. System Development Life Cycle and Project Management • 6.2. System Analysis

• 6.3. System Design

• 6.4. Software Automation Method

• 6.5. Repetitive Design-Coding-Test Method

(2)

• Characteristics of Information System (IS) • Variability for changeability

• System development life cycle (SDLC) • = System life cycle (SLC)

• Project management (PM)

• Tasks and end-products for each stage

6.1. System Development Life Cycle and Project Management

• 6.1.1. Types of Life Cycle • Waterfall model

• Sequential procedure of •①System planning •②System analysis •③Conceptual design

•④System evaluation and selection •⑤Detailed design

•⑥System implementation •⑦System maintenance • Spiral model

• Iterative procedure of •①System planning

②

(3)

• 6.1.2. Project Management (PM) • Stages of PM

•①Planning (e.g. COCOMO model, function point model) •②Organizing (e.g. PERT chart)

•③Controlling (e.g. GANTT chart) • Resources of PM

• Persons (e.g. project manager, system analyst, programmer, DBA) • Wares (e.g. hardware, software)

6.1. System Development Life Cycle and Project Management

• 6.1.2. Project Management (PM) (cont’d) • Automated tools of PM

• GANTT chart, bar chart • Prediction models of resource

• COCOMO(Constructive Cost Model) model

• MM(Man-Month) = 2.4 * KLOC(Kilo Line Of Code)^1.05 • DT(Development Time) = 25 * MM(Man-Month)^0.38 • Function point model

• FP(Function Point) = Count * Weight • Time box model

• PLT(Product Lead Time) = 90 days (Du Pont)

• PLT(Product Lead Time) = 7 days (Cambridge Technology)

(4)

• Systems Approach •①Defining problems •②Analyzing causes

•③Evaluating resolution alternative comparatively •④Selecting optimum and researching user-requirements • System Analysis (SA) in the Narrow Sense

•①Collecting reports •②Visiting and Interviewing

•③Drawing diagrams (e.g. DFD(Data Flow Diagram), ERD(Entity Relationship Diagram)) •④Prototyping

•⑤Holding JAD(Joint Application Design)

6.2. System Analysis

• 6.2.1. Feasibility Study (FS) • Linkage with business plan • PDM framework

• Production • Differentiation • Management • Problem vs. opportunity • Repeatability of FS • TELOS analysis

• Technical FS • Economic FS • Legal FS • Operational FS

(5)

• 6.2.2. Structured Analysis

• Principles of structured analysis • Abstraction

• Formality

• Divide and conquer • Hierarchical ordering • Data flow diagram (DFD)

• Components of DFD • Process • External agent • Data store • Flow

• Business process definition

• Business process procedure (e.g. structured English) • Business process policy (e.g. decision tree, decision table)

6.2. System Analysis

• 6.2.3. Object-Oriented Analysis (OOA) • Procedure of OOA

•①Discovering objects and classes

•②Defining characteristics (e.g. property, behavior) of each class •③Defining hierarchy among classes and message exchange •④Elaborating characteristics (e.g. property, behavior) of each class • Terminology

• Encapsulation • Instantiation • Hierarchy • Polymorphism

• Unified modeling language (UML)

• E.g. use case diagram, event trace diagram, event flow diagram, state transition diagram

(6)

• 6.2.4. Other SA • Prototyping

• Evolutionary development • JAD(Joint Application Design)