System Analysis Phase Functional Decomposition Diagram FDD Unified

System Analysis Phase Functional Decomposition Diagram (FDD) Unified Modeling Language (UML) Prepared by Siti Dianah binti Abdul Bujang

Learning Outcome � Students should be able to: � Use FDD to business functions and processes � Describe the UML and examples of UML diagram � Develop effective documentation methods to use during systems development

Analysis Phase

Functional Decomposition Diagram (FDD) � function decomposition is the decomposing of a system into its component functions and processes as a way of managing complexity � they may be built using either a top down or a bottom up approach �a function decomposition model (or diagram) is used to represent the hierarchical decomposition and structure of the processes of a system � the decomposition of functions corresponds to levelling of processes in DFDs

Functional Decomposition Diagram (FDD) function process • • high-level set of related activities that are ongoing broad, generic activity consist of groups of related processes depth and scope of function decomposition diagrams depend on the size and complexity of the system represented • lower level activity that is repeatedly carried out

Functional Decomposition Diagram (FDD) � each function and process should have a unique name which indicates what it does ABC Sales System 1. Sell Products 2. Manage Inventory 3. Control Finance a top level function decomposition diagram

Functional Decomposition Diagram (FDD) Example Function Decomposition Diagram ABC Sales System 1. Sell Products 2. 1 Deliver Product 2. Manage Inventory 2. 2 Accept Delivery 3. Control Finance 2. 3 Check Stock levels functions and processes are further decomposed

Unified Modeling Language (UML) Modeling 1. Describing a system at a high level of abstraction a. A model of the system b. Used for requirements and specifications 2. Is it necessary to model software systems? Importance 1. Describing the system at abstract level to comprehend its complexity 2. Necessary to manage complexity 3. Good for quick understanding of the systems 4. Less chances of conflicting views b/w end-user and system designers

Unified Modeling Language (UML) § UML stands for “Unified Modeling Language” § It is a industry-standard graphical language for specifying, visualizing, constructing, and documenting the artifacts of software systems § The UML uses mostly graphical notations to express the OO analysis and design of software projects. § Simplifies the complex process of software design

Types of UML � Use Case Diagram � Class Diagram � Sequence Diagram � Collaboration � State Diagram

Use Case Diagram � � � Used for describing a set of user scenarios Mainly used for capturing user requirements Work like a contract between end user and software developers

Use Case Diagram Actors A role that a user plays with respect to the system, including human users and other systems. e. g. , inanimate physical objects (e. g. robot); an external system that needs some information from the current system. Use case A set of scenarios that describing an interaction between a user and a system, including alternatives. System boundary rectangle diagram representing the boundary between the actors and the system.

Use Case Diagram Association: communication between an actor and a use case; Represented by a solid line. Generalization: relationship between one general use case and a special use case (used for defining special alternatives) Represented by a line with a triangular arrow head toward the parent use case.

Use Case Diagram Include: a dotted line labeled <<include>> beginning at base use case and ending with an arrows pointing to the include use case. The include relationship occurs when a chunk of behavior is similar across more than one use case. Use “include” in stead of copying the description of that behavior. <<include>> Extend: a dotted line labeled <<extend>> with an arrow toward the base case. The extending use case may add behavior to the base use case. The base class declares “extension points”. <<extend>>

Use Case Diagram Include: a dotted line labeled <<include>> beginning at base use case and ending with an arrows pointing to the include use case. The include relationship occurs when a chunk of behavior is similar across more than one use case. Use “include” in stead of copying the description of that behavior. <<include>> Extend: a dotted line labeled <<extend>> with an arrow toward the base case. The extending use case may add behavior to the base use case. The base class declares “extension points”. <<extend>>

Use Case Diagram Boundary Use Case Actor Library System Borrow Employee Client Order Title Fine Remittance Supervisor • A generalized description of how a system will be used. • Provides an overview of the intended functionality of the system

Use Case Diagram

Report Analysis for Presentation 1. Introduction 2. Problem Statement 3. Objectives 4. Scope i. System Scope ii. User Scope 5. Project Significant 6. Methodology 7. Cost 8. Fact Finding i. Interview Presentation will be on 24/08/2016 (Thursday) ii. Questionnaire iii. Documentation Review / Literature Review iv. Observation v. Sampling vi. Research 9. Conclusion 10. References