System Analyst, short guide

Transcript

1. SYSTEM ANALYST A PRACTICAL GUIDE TO BE A FALAHAH ONLINE LEARNING AT PHP.ID, 11 MAY 2020 Supported by : KK EINS – FRI- Telkom University
2. 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
3. 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
4. INTRODUCTION ❑A profession and its job description ❑Daily Activities ❑Skills Needed
5. 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/
6. 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
7. 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
8. SKILLS AND KNOWLEDGE ❑ MODELING THE SYSTEM ❑ TOOLS FOR MODELING ❑ REPORTING AND DOCUMENTATION
9. 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
10. 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
11. ABSTRACTION AND LEVELING – WORK AREA System analysis area Fernandez and Kuhrman, Artefact-based Requirement Engineering and its Integration into a Process Framework
12. 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
13. ABSTRACTION AND LEVELING – TOP DOWN APPROACH Generic model Specific model
14. ABSTRACTION AND LEVELING - DECOMPOSITION
15. ABSTRACTION AND LEVELING - DETAILED Class diagram Use Case diagram High level Detail level
16. ABSTRACTION AND LEVELING - DETAILED High level Detail level
17. MODELING APPROACH ❑STRUCTURED DESIGN ANALYSIS (SDA) ❑OBJECT ORIENTED ANALYSIS AND DESIGN (OOAD) ❑AGILE SOFTWARE DEVELOPMENT ❑…
18. MODELING APPROACH - SDA System Analysis and Design in a Changing World, Satziner, Jakson, and Burd, 2015
19. MODELING APPROACH - SDA FUNCTIONAL VIEW DATA VIEW DYNAMIC VIEW DATA FLOW DIAGRAM (DFD) ENTITY RELATIONSHIP DIAGRAM (ERD) PROCESS FLOW DIAGRAM
20. MODELING APPROACH – SDA – FUNCTIONAL VIEW CONTEXT DIAGRAM LEVEL 0 LEVEL 1 PROCES 3
21. MODELING APPROACH – SSA – DATA VIEW Entity Relationship Diagram (ERD) Table Relationship Diagram (TRD)
22. MODELING APPROACH - OOAD STRUCTURED DIAGRAM CLASS DIAGRAM BEHAVIOR DIAGRAM USE CASE DIAGRAM
23. MODELING APPROACH - OOAD - UML UNIFIED MODELING LANGUAGE
24. 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
25. 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
26. 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
27. 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
28. 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
29. 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.
30. MODEL MAPPING ❑ TRANSFORM MODEL INTO DESIGN USE CASE Class diagram Sequence Diagram UI
31. USING THE MODEL 1 2 3
32. 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.
33. TOOLS FOR MODELING – BUSINESS PROCESS MODEL BUSINESS PROCESS MODEL ❑ Standard : Business Process Model and Notation (BPMN) Joget.org Bonitasoft.com bizagi.com Tools
34. TOOLS FOR MODELING - BUSINESS PROCESS MODEL- JOGET Joget.org
35. TOOLS FOR MODELING – CASE TOOLS CASE TOOLS (Computer Aided Software Engineering) ❑ Set of software application programs, which are used to automate SDLC activities
36. TOOLS FOR MODELING – CASE TOOLS - CODE GENERATED TOOL
37. TOOLS FOR MODELING – CASE TOOLS- DATABASE GENERATED TOOLS Softwareideas.net/en/erd-tools
38. REPORTING AND DOCUMENTATION ❑ DOCUMENTATION OF THE MODEL ❑ WRITING THE REPORT
39. 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
40. 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
41. SDLC SYSTEM DEVELOPMENT LIFE CYCLE
42. SDLC - A STEP BY STEP APPROACH
43. SDLC - ACTIVITIES AND OUTPUT SYSTEM ANALYST PROJECT MANAGER BUSINESS ANALYST
44. 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
45. SDLC - #1 - REQUIREMENT ❑ Identify the problem ❑ Define the expected solution ❑ Identify the requirement ❑ Classify and prioritize the requirement ❑ Define the requirement
46. 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
47. 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
48. 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
49. 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.
50. 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
51. 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
52. SDLC - #2 – ANALYSIS – MODELING THE PROCESS • Menampilkan daftar dosen • Mengajukan proposal • Membuat janji bimbingan
53. SDLC - #2 – ANALYSIS – TOOLS ❑ Use case diagram ❑ Activity Diagram ❑ Class Diagram ❑ Entity Relationship Diagram ❑ HIPO Diagram ❑ ….
54. 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 ❑ ….
55. 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)
56. SDLC - #3 - DESIGN Design of: ❑ UI/UX ❑ Process ❑ Information Architecture ❑ Data Integration ❑ Security ❑ ….
57. SDLC - #3 - DESIGN - TOOLS ❑ Sequence diagram ❑ Wireframe ❑ Process Specification ❑ Class Diagram ❑ Storyboard ❑ ….
58. SDLC - #3 - DESIGN - OUTPUT ❑ User Interface Design ❑ Process Design ❑ Database design ❑ Report design ❑ Data integration design ❑ Security design ❑ …
59. 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
60. 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
61. SDLC - #4 - IMPLEMENT - OUTPUT ❑ Implementation Plan ❑ User manual ❑ Technical Guide of implementation ❑ Implementation Report
62. DELIVERABLES ❑ USER REQUIREMENT DOCUMENT ❑ FUNCTIONAL SPECIFICATION DOCUMENT ❑ SYSTEM DESIGN DOCUMENT ❑ IMPLEMENTATION DOCUMENT
63. USER REQUIREMENT DOCUMENT
64. FUNCTIONAL SPECIFICATION DOCUMENT
65. SYSTEM DESIGN DOCUMENT
66. IMPLEMENTATION DOCUMENT
67. CAREER PATH ❑ Course you can attend ❑ Book you need to read ❑ Where you can start ❑ Tips you need to know
68. 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
69. 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 ❑ …
70. 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
71. 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
72. 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
73. 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.
74. ❑ Gain approved by the stakeholder ❑ Delivered the output on time ❑ Supported by the client/user ❑ Business oriented result ❑ Repeat order A SUCCESSFUL SYSTEM ANALYST
75. Q & A
76. 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