System Analyst, short guide

Slide 1

Slide 1 text

SYSTEM ANALYST A PRACTICAL GUIDE TO BE A FALAHAH ONLINE LEARNING AT PHP.ID, 11 MAY 2020 Supported by : KK EINS – FRI- Telkom University

Slide 2

Slide 2 text

FALAHAH falahah@telkomuniversity.ac.id flash-note.com linkedin.com/in/falahah EXPERIENCES 1993-2000 System Analyst and Project Manager, Computing Center, PT Dirgantara Indonesia 2000-2008 Freelance project manager for IS Development 2008-Now IS Lecturer Telkom University 2015 -Now IT Governance Consultant (Pemkot Bandung, Pemrov DKI, BPOM, KPPPA, BNI Life, etc) IS lecturer/researcher, IT Governance Consultant ABOUT ME

Slide 3

Slide 3 text

Job Description OVERVIEW INTRODUCTION A profession, job description, skill needed, daily activities SKILL AND KNOWLEDGE System modeling, tools, reporting and documentation SDLC Requirement, analysis, design, implementation DELIVERABLE Requirement and analysis document, design document, implementation report CAREER PATH Courses, books, education, certification & training

Slide 4

Slide 4 text

INTRODUCTION ❑A profession and its job description ❑Daily Activities ❑Skills Needed

Slide 5

Slide 5 text

WHO IS A SYSTEM ANALYST? A professional who is *): ❑ familiar with computer systems, programming, technical architecture and platform ❑ help company analyze and implement new IT solution or improve existing ones Job Description A PROFESSION AND ITS JOB DESCRIPTION JOB DESCRIPTION ❑ Analyzes business situation ❑ Identify opportunity for improvement ❑ Design an IS to implement the improvement *)https://thebusinessanalystjobdescription.com/systems-analyst/

Slide 6

Slide 6 text

Technical Skills / knowledge: ❑ Tools for modeling (CASE-Tool, UML) ❑ Hardware ❑ Software and programming ❑ Networking ❑ Database and its implementation ❑ Software/data security requirement Soft Skills: ❑ Abstractions skill ❑ Team work ❑ Interpersonal skills ❑ Oral and written skill ❑ Planning and negotiation ❑ Initiative and self confident ❑ Fast learner. SKILL NEEDED

Slide 7

Slide 7 text

Job Description DAILY ACTIVITIES ❑ User requirement ❑ System Specification/design ❑ Meeting resume ❑ Testing/implementation report ❑ End-user ❑ Operator ❑ Technical Support ❑ Supervisor/manager/director ❑ Document ❑ Report ❑ user manual ❑ Procedures/policy. READING INTERVIEWING PRESENTING WRITING ❑ Kickoff meeting ❑ Progress meeting ❑ Focus group discussion ❑ System Implementation

Slide 8

Slide 8 text

SKILLS AND KNOWLEDGE ❑ MODELING THE SYSTEM ❑ TOOLS FOR MODELING ❑ REPORTING AND DOCUMENTATION

Slide 9

Slide 9 text

MODELING THE SYSTEM ❑ ABSTRACTION AND LEVELING ❑ MODELING APPROACH ❑ MODEL MAPPING ❑ USING THE MODEL Model : describe the real world into a model, that consist of object and its interaction

Slide 10

Slide 10 text

ABSTRACTION AND LEVELING ❑ representing essential features without including the background details or explanations. ❑ is used to reduce complexity and allow efficient design and implementation of complex software systems. Abstraction ❑ Describe or explain the complex system into hierarchical approach ❑ Remove complexity and lets the audience focus on the point of interest. Leveling

Slide 11

Slide 11 text

ABSTRACTION AND LEVELING – WORK AREA System analysis area Fernandez and Kuhrman, Artefact-based Requirement Engineering and its Integration into a Process Framework

Slide 12

Slide 12 text

ABSTRACTION AND LEVELING – HIERACHICAL VIEW VIEW Business view Technical view Cloud view kite view Ocean view fish view Clam view Writing effective use cases, Alistair Cockburn, 2000

Slide 13

Slide 13 text

ABSTRACTION AND LEVELING – TOP DOWN APPROACH Generic model Specific model

Slide 14

Slide 14 text

ABSTRACTION AND LEVELING - DECOMPOSITION

Slide 15

Slide 15 text

ABSTRACTION AND LEVELING - DETAILED Class diagram Use Case diagram High level Detail level

Slide 16

Slide 16 text

ABSTRACTION AND LEVELING - DETAILED High level Detail level

Slide 17

Slide 17 text

MODELING APPROACH ❑STRUCTURED DESIGN ANALYSIS (SDA) ❑OBJECT ORIENTED ANALYSIS AND DESIGN (OOAD) ❑AGILE SOFTWARE DEVELOPMENT ❑…

Slide 18

Slide 18 text

MODELING APPROACH - SDA System Analysis and Design in a Changing World, Satziner, Jakson, and Burd, 2015

Slide 19

Slide 19 text

MODELING APPROACH - SDA FUNCTIONAL VIEW DATA VIEW DYNAMIC VIEW DATA FLOW DIAGRAM (DFD) ENTITY RELATIONSHIP DIAGRAM (ERD) PROCESS FLOW DIAGRAM

Slide 20

Slide 20 text

MODELING APPROACH – SDA – FUNCTIONAL VIEW CONTEXT DIAGRAM LEVEL 0 LEVEL 1 PROCES 3

Slide 21

Slide 21 text

MODELING APPROACH – SSA – DATA VIEW Entity Relationship Diagram (ERD) Table Relationship Diagram (TRD)

Slide 22

Slide 22 text

MODELING APPROACH - OOAD STRUCTURED DIAGRAM CLASS DIAGRAM BEHAVIOR DIAGRAM USE CASE DIAGRAM

Slide 23

Slide 23 text

MODELING APPROACH - OOAD - UML UNIFIED MODELING LANGUAGE

Slide 24

Slide 24 text

MODELING APPROACH - OOAD - UML – USE CASE ❑ Describe set of ACTIONS that should perform ❑ Consist of USE CASE (action) and ACTORS BUSINESS USE CASE SYSTEM USE CASE

Slide 25

Slide 25 text

MODELING APPROACH - OOAD - UML – ACTIVITY DIAGRAM ❑ Describe how activities are coordinated to provide a service ❑ Can be done at different level of abstraction HIGH LEVEL ACTIVITY DIAGRAM LOW LEVEL ACTIVITY DIAGRAM

Slide 26

Slide 26 text

MODELING APPROACH - OOAD - UML - SEQUENCE DIAGRAM ❑ Describe an interaction by focusing on the sequence of messages that are exchanged ❑ Show the corresponding occurrence specifications on the lifelines SEQUENCE DIAGRAM WITH FRAGMENT SEQUENCE DIAGRAM

Slide 27

Slide 27 text

MODELING APPROACH - OOAD - UML - CLASS DIAGRAM ❑ Show structure of the designed system at the level of classes and interfaces ❑ Show their features, constraints and relationships MVC Class Diagram Class diagram

Slide 28

Slide 28 text

MODELING APPROACH - OOAD - UML - COMPONENT DIAGRAM ❑ Describes the organization and wiring of the physical components in a system. ❑ Illustrate the structure of arbitrarily complex systems

Slide 29

Slide 29 text

MODELING APPROACH - OOAD - UML – DEPLOYMENT DIAGRAM ❑ specifies the physical hardware on which the software system will execute. ❑ determines how the software is deployed on the underlying hardware. ❑ maps software pieces of a system to the device that are going to execute it.

Slide 30

Slide 30 text

MODEL MAPPING ❑ TRANSFORM MODEL INTO DESIGN USE CASE Class diagram Sequence Diagram UI

Slide 31

Slide 31 text

USING THE MODEL 1 2 3

Slide 32

Slide 32 text

TOOLS FOR MODELING Software for modeling the system ❑ Business Process Model (BPM): modeling the process for higher lever abstraction, consist of actor, process and data/information needed ❑ CASE Tools : Computer Aided Software Engineering Toos, helps us modeling and designing system for lower level abstraction.

Slide 33

Slide 33 text

TOOLS FOR MODELING – BUSINESS PROCESS MODEL BUSINESS PROCESS MODEL ❑ Standard : Business Process Model and Notation (BPMN) Joget.org Bonitasoft.com bizagi.com Tools

Slide 34

Slide 34 text

TOOLS FOR MODELING - BUSINESS PROCESS MODEL- JOGET Joget.org

Slide 35

Slide 35 text

TOOLS FOR MODELING – CASE TOOLS CASE TOOLS (Computer Aided Software Engineering) ❑ Set of software application programs, which are used to automate SDLC activities

Slide 36

Slide 36 text

TOOLS FOR MODELING – CASE TOOLS - CODE GENERATED TOOL

Slide 37

Slide 37 text

TOOLS FOR MODELING – CASE TOOLS- DATABASE GENERATED TOOLS Softwareideas.net/en/erd-tools

Slide 38

Slide 38 text

REPORTING AND DOCUMENTATION ❑ DOCUMENTATION OF THE MODEL ❑ WRITING THE REPORT

Slide 39

Slide 39 text

Detail Description about model ❑ Process Specification (Data Flow Diagram) ❑ Data Dictionary (Entity Relationship Diagram) ❑ High Level Use Case (Use Case Diagram) ❑ Pseudocode (lowest level activity diagram) MODEL DOCUMENTATION Data dictionary High Level Use case pesudocode

Slide 40

Slide 40 text

A System Analyst should be able to write the report about ❑ System Development Document (User Requirement, System Specification, System Design, etc) ❑ Minutes of Meeting ❑ Progress of System Development ❑ Requirement tracking history and changes ❑ … WRITING THE REPORT

Slide 41

Slide 41 text

SDLC SYSTEM DEVELOPMENT LIFE CYCLE

Slide 42

Slide 42 text

SDLC - A STEP BY STEP APPROACH

Slide 43

Slide 43 text

SDLC - ACTIVITIES AND OUTPUT SYSTEM ANALYST PROJECT MANAGER BUSINESS ANALYST

Slide 44

Slide 44 text

SDLC – JOB OF A SYSTEM ANALYST 1 2 3 4 Identify and define the requirement Define system specification Define system design (external and internal design) Prepare Implementation plan, supervise implementation Requirement Analysis Design Implement CODING Monitor the coding process, validate the result TESTING Prepare the testing plan, monitor the testing and check the result User Req Document System Spesification Document Design Document Implementation Document Test plan, test report User manual, technical guide Analyze business problem Identify opportunity for improvement Design system to implement the improvement Assure that the implemented system match with requirement

Slide 45

Slide 45 text

SDLC - #1 - REQUIREMENT ❑ Identify the problem ❑ Define the expected solution ❑ Identify the requirement ❑ Classify and prioritize the requirement ❑ Define the requirement

Slide 46

Slide 46 text

SDLC - #1 – REQUIREMENT – IDENTIFY THE PROBLEM ❑ Define PROBLEM STATEMENT ❑ Identify the stakeholder ❑ Gain support from the stakeholder ❑ Write or draw the model of problem area

Slide 47

Slide 47 text

SDLC - #1 – REQUIREMENT – IDENTIFY THE PROBLEM Story: Bagian purchasing kesulitan menelusuri status dokumen purchase order (PO) yang sudah diserahkan kepada vendor, apakah sudah selesai seluruhnya, atau masih ada pengiriman yang belum tuntas, atau ada barang reject dan belum diganti. Status ini tercatat pada bagian gudang dan berita acara penerimaan barang tidak dapat diakses oleh bagian purchasing. Problem Statement: Bagaimana agar bagian Purchasing dapat: ❑ Menelusuri progress PO ❑ Mengetahui status PO ❑ Mengakses data PO secara realtime Stakeholder ❑ Bagian Purchasing ❑ Bagian Gudang ❑ Vendor Data/Information ❑ PO ❑ Status_PO ❑ Berita acara penerimaan ❑ Pengiriman

Slide 48

Slide 48 text

SDLC - #1 – REQUIREMENT – EXPECTED SOLUTION AND REQ INTEGRATED PROCUREMENT SYSTEM: 1. CREATE PO 2. NOTIFY VENDOR 3. PROCESSING PO 4. TRACKING PO STATUS 5. NOTIFICATION FOR RECEIVING MATERIAL 6. CLOSING PO The system should be able to: 1. Plan and Creating PO 2. Sending PO to vendor and send notification 3. Processing PO if confirmed by vendor 4. Show PO status as vendor process the order 5. Display all receiving material document in warehouse and connecting its into PO document 6. Sending notification if any reject stuff in receiving material. 7. …. 8. …. 9. Sending notification through mobile app 10. Export PO report into pdf 11. Query for selective period 12. …. Functional Requirement Non Functional Requirement Proposed Solution The Requirement

Slide 49

Slide 49 text

SDLC - #1 – REQUIREMENT – FUNCT AND NON FUNC REQ. FUNCITONAL REQUIREMENT: Describe the expected functions that should exist on the system or delivered by the system so its can solve the problem. NON FUNCTIONAL REQUIREMENT: Additional features that will support the main function of the system.

Slide 50

Slide 50 text

SDLC - #1 – REQUIREMENT – MAPPING Existing process List of problem Proposed solution Functional Requirement Proses bimbingan tugas akhir • Dosen susah ditemui • Sulit menentukan topik • Sulit mencari dosen pembimbing yang tepat Sistem bimbingan online • Menampilkan daftar dosen • Mengajukan proposal • Membuat janji bimbingan

Slide 51

Slide 51 text

SDLC - #2 - ANALYSIS ❑ Identify the process ❑ Define the process that would be implemented ❑ Identify and refine functional and non functional system specification ❑ Define system specification, which include functional specification, data specification and/or security specification

Slide 52

Slide 52 text

SDLC - #2 – ANALYSIS – MODELING THE PROCESS • Menampilkan daftar dosen • Mengajukan proposal • Membuat janji bimbingan

Slide 53

Slide 53 text

SDLC - #2 – ANALYSIS – TOOLS ❑ Use case diagram ❑ Activity Diagram ❑ Class Diagram ❑ Entity Relationship Diagram ❑ HIPO Diagram ❑ ….

Slide 54

Slide 54 text

SDLC - #2 – ANALYSIS – OUTPUT ❑ Functional and non functional specification ❑ Data specification, data model, data architecture ❑ Hardware/software support ❑ Data integration ❑ User specification and authority ❑ System security specification ❑ ….

Slide 55

Slide 55 text

SDLC - #2 – ANALYSIS – CHECKLIST Check if your functional specification: ❑ Traceability (Can be mapped into requirement) ❑ Concise (Clear and understandable) ❑ Feasible (Realistic by the constraint) ❑ Complete (Cover everything necessary) ❑ Verifiability (verified and validated by the stakeholder)

Slide 56

Slide 56 text

SDLC - #3 - DESIGN Design of: ❑ UI/UX ❑ Process ❑ Information Architecture ❑ Data Integration ❑ Security ❑ ….

Slide 57

Slide 57 text

SDLC - #3 - DESIGN - TOOLS ❑ Sequence diagram ❑ Wireframe ❑ Process Specification ❑ Class Diagram ❑ Storyboard ❑ ….

Slide 58

Slide 58 text

SDLC - #3 - DESIGN - OUTPUT ❑ User Interface Design ❑ Process Design ❑ Database design ❑ Report design ❑ Data integration design ❑ Security design ❑ …

Slide 59

Slide 59 text

SDLC - #3 - DESIGN - CHECKLIST Check if your design: ❑ Can be traced back into functional specification ❑ Has discussed and validated with programmer ❑ Feasible to implement by programmer ❑ Consist of all aspect in system specification

Slide 60

Slide 60 text

SDLC - #4 - IMPLEMENT Preparing Implementation Plan ❑ Checking user manual and technical guide for implementation ❑ Preparing initial data ❑ Preparing implementation environment ❑ Analyze and define User access and authority ❑ Preparing user training (if necessary) Supervising and reporting implementation activities ❑ Supervising implementation team ❑ Write implementation report

Slide 61

Slide 61 text

SDLC - #4 - IMPLEMENT - OUTPUT ❑ Implementation Plan ❑ User manual ❑ Technical Guide of implementation ❑ Implementation Report

Slide 62

Slide 62 text

DELIVERABLES ❑ USER REQUIREMENT DOCUMENT ❑ FUNCTIONAL SPECIFICATION DOCUMENT ❑ SYSTEM DESIGN DOCUMENT ❑ IMPLEMENTATION DOCUMENT

Slide 63

Slide 63 text

USER REQUIREMENT DOCUMENT

Slide 64

Slide 64 text

FUNCTIONAL SPECIFICATION DOCUMENT

Slide 65

Slide 65 text

SYSTEM DESIGN DOCUMENT

Slide 66

Slide 66 text

IMPLEMENTATION DOCUMENT

Slide 67

Slide 67 text

CAREER PATH ❑ Course you can attend ❑ Book you need to read ❑ Where you can start ❑ Tips you need to know

Slide 68

Slide 68 text

CAREER PATH – COURSES YOU CAN ATTEND Coursera.org ❑ Software development lifecycle specialization ❑ Software design and architecture specialization ❑ Requirements Engineering: Secure Software Specifications Specialization Udacity ❑ Software development process ❑ Software analysis and testing edX ❑ UML Class Diagrams for Software Engineering ❑ Software Engineering Essential

Slide 69

Slide 69 text

CAREER PATH – BOOKS YOU CAN READ BOOKS ❑ System Analysis and Design, Denis, Wixom and Roth, 2012 ❑ Modern System Analysis and Design, Hoffer, George, Valacich ❑ System Analysis and Design, Kendall & Kendall ❑ Applying UML and Pattern, Larman ❑ Object Oriented Analysis and Design for Information System, Wazlawick ❑ …

Slide 70

Slide 70 text

CAREER PATH – EDUCATION? IF YOU ❑ Have excellent written and verbal communication ❑ Know both business and technology ❑ Love reading business and economic news ❑ Act as informal tech support for your friends EDUCATION ❑ No specific academic background ❑ Mixing between IT and business ❑ Course in technical writing and business communication ❑ Basic knowledge in IT, programming and management

Slide 71

Slide 71 text

CAREER PATH – CERTIFICATION & TRAINING CERTIFICATION ❑ Certified Analytics Professional (CAP) (www.certifiedanalytics.org/for_profes sionals.php ❑ 7 domain analytic process: business problem framing, analytic problem framing, data , methodology selection, model building, deployment, lifecycle management TRAINING ❑ Start join your first team as internship analyst ❑ Try to become technical writer to improve your writing skill ❑ Take a part on writing system requirement or system specification ❑ Presentation skill

Slide 72

Slide 72 text

CAREER PATH – HOW LONG AND HOW MUCH? How much the salary? Average : $ 93.000/year (Int) IDR 7000K – 22.000K/month (Ind) How long it takes to be a system analyst? 3 – 5 YEARS WORKING AS PROGRAMMER OR SOFTWARE DEVELOPER Programmer Software developer System analyst

Slide 73

Slide 73 text

CAREER PATH – TIPS ❑ Learn more about business process ❑ Start from beginner, start as a project technical writer. ❑ Attending discussion for practicing your analytical and structural thinking. ❑ Draw conceptual models for improving your abstraction skill ❑ Upgrade your technical skill for supporting your knowledge on suggesting or recommending solution for the users.

Slide 74

Slide 74 text

❑ Gain approved by the stakeholder ❑ Delivered the output on time ❑ Supported by the client/user ❑ Business oriented result ❑ Repeat order A SUCCESSFUL SYSTEM ANALYST

Slide 75

Slide 75 text

Q & A

Slide 76

Slide 76 text

THANK YOU Thankyou for all person that support me: for giving a chance to share this material ◂ SAG Research Laboratory – FRI – Telkom University for supporting me delivering this content ◂ yudi_utomo for giving suggestions and input while preparing this contents KK EINS – FRI- Telkom University