Process Flow on Business Requirement

What is Process Flow In this session we want to show you how to capture business requirement especially the process flow. In the requirement mark-up language (RML), process flow discusses a business process that will be executed by people. Process flow show the activities to be performed. There are two types of process flow the first process flow is done by the people the second one is done by the system. The first process flow captures the original business process, while the second process flow captures the computer-based / software process flow. Represent Process Flow in a Diagram There are several diagrams that can be used to capture process flow: Business Process Model & Notation (BPMN) - http://www.bpmn.org/ Flowchart Diagram - https://en.wikipedia.org/wiki/Flowchart Activity Diagram - https://en.wikipedia.org/wiki/Activity_diagram Mind map - https://en.wikipedia.org/wiki/Mind_map What tools You can find a lot software. i recommend several software such as Mindjet Mind manager Microsoft Visio Draw.io Lucid chart X Mind So many medianet_width = "600"; medianet_height = "250"; medianet_crid = "858385152"; medianet_versionId = "3111299"; Some tips on Process Flow Sketch your process flow using a hand. This will help you understand the business process. Identify the actor for the process flow. Considering using swim lane for the process flow Is the process having multiple level? If yes, try to create several level diagrams from big picture (level 1), detailed picture (level 2), and more detail level (level 3) Running review with the customer to make sure the process is on shared vision     medianet_width = "600"; medianet_height = "250"; medianet_crid = "858385152"; medianet_versionId = "3111299";

Agile Modeling 101–Building Use Case Diagram

This Indonesian video will guide you the first step to capture system and actor requirement. This tutorial uses Visual Studio Modeling project as a part of ALM features in Visual Studio started from 2010 version. Here are some conclusions from this video Actor and Action are the main part of use case diagram Keep the diagram simple, eliminating the technical aspect such as extend or include, except you use this use case for technical communication between technical team only Kite level best for business use case, while sea level use case good for deep dive with the system requirement It will be great to split up use case diagram for one actor (the video join the entire users for simplicity purpose only) Use case will be explained further in Activity Diagram Enjoy this video,

Topics Highlights

Translate It

About @ridife

This blog will be dedicated to integrate a knowledge between academic and industry need in Application Lifecycle Management (ALM), ICT tips, and Software Engineering Research. Enjoy this blog and let's get in touch in any social media.

Xbox

Month List