Analysis

Slide 1: System Analysis

Slide 2: Components of Requirements Elicitation CRM/HR/… Knowledge of general area Understanding of specific where system is applied customer problem to be solved Understanding of how Detailed understanding of systems interact and contribute specific stakeholder needs to overall business goals and constraints 2 Source: Kotonya and Sommerville, Requirements Engineering, Wiley, 1998

Slide 3: Relationship of Model Domain Model 1. Identify Actors Sale 1 Captured-on 1 ... Register ProductCatalog ... 2.Identify business/system process timeStamp ... ... 3.System use case modeling domain concepts 4.Conceptual Modeling Use-Case Model : System Process Sale : Cashier Proce make ss 1. Customer system NewSale () Cashier Sale arrives ... events enterItem 2. Cashier makes (id, quantity) ... new sale. conceptual 3. ... classes in the domain Use Cases System Sequence Diagrams Use Case Diagrams inspire the names of some use-case software Design Model realization with classes in the interaction : Register : ProductCatalog design diagrams makeNewSale() create() : Sale enterItem(id, quantity) spec := getSpecification( id ) addLineItem( spec, quantity ) ... the design classes Register ProductCatalog discovered while designing UCRs ... 1 1 ... can be makeNewSale () summarized in getSpecification(...) : ProductSpecification class diagrams enterItem(...) ... ... 3

Slide 4: Analysis patterns in the software development process Analysis Design Patterns Patterns Data Structure Patterns 站在巨人的肩膀 ... 4

Slide 5: Entity Relationship Diagram-UDM Direct selling Sales Own Territory Selling thru. Channel Sales Manage Agent Own Territory Delivered thru. Channel Sales Own Territory Distribute Agent 5

Slide 6: Extended Entity Relationship Diagram 1 Sales Own Territory Distribute Agent 2 Sales Manage Agent Own Territory 3 哇 ! It’s Stakeholder OO… Owner Own Territory Agent Manage Sales n..0 6

Slide 7: Q&A 7