5. 資料流程圖 DFD
Circles: the process (or the function) that actually works
to transform inputs into outputs.
Curved lines: the data flowing into and out of the process.
Rectangular boxes: external agents that are sources or
recipients of data.
6. 文字化範本
External agents: those parties or systems that exchange information
with the project but over which your project has no control.
8. 實體關係圖 ERD
Entities: the uniquely identifiable people, things, or concepts whose information
is important to the business;
Attributes are distinguishing characteristics of the entity;
Relationships explain how the entities share data.
< (crow’s feet): multiple entities. Also a maximum value.
○: optional - a connection isn’t required. Also a minimum value of zero.
∣: single entry that can be used as both a minimum and a maximum value.
-
11. 流程分解圖
Parent processes : Processes that have processes underneath.
Child processes : Processes that report into another process.
Guidelines:
1. parent process, you must break it into at least two children;
2. All the child processes together must completely describe all the activities in
the parent process.
Top-down
12. 範例
Event-driven
Top-down: Start with the high-level processes (requirements).
Bottom-up: Think of all the detailed tasks have to do in the area of study (or
scope) and then find common groupings.
Event-driven: Think of all the triggers (directives that lead to a series of actions)
and the tasks that follow.
16. 工作流程圖類型
Swimlane: focuses on interactions between
organizational units
ANSI flowchart: 1970s first standard for
workflows
UML Activity: Unified Modeling Language
BPMN: Business Process Modeling Notation
Geographic diagrams: used in warehousing
and logistics
SIPOC: Primarily in Six Sigma. Supplier–Input–
Process–Output–Customer.
19. 用例
定義使用者 (Actor) 和系統之間的互動
組成
use case diagram
use case description
應用時機
紀錄使用者與系統的詳細互動
釐清使用者希望如何使用系統的描述
可以處理解決方案的範疇
識別解決方案的界面
20. 圖形範例
Automation boundary: Rectangle.
The system under discussion.
Actors: stick figures.
A resource interacting with the system
and can be a human or another
system.
Associations: line connection.
the actor is involved with the use case.
Use cases: ovals inside.
describe what they do.
22. 雛型
描述系統的使用者界面
使用考量
誰會使用屏幕 (screen)
開發團隊參與
有些雛形是用後即丟 (throwaways)
使用方式
Storyboards: how the various screens of a system interconnect
with one another.
Simulations: web pages that mimic the desired online
functionality and give the users the feel of how the finished
system will behave
Mockups: drawings of a screen or report layout with its
graphics, text boxes, buttons, menus, and options.
25. 使用者故事
故事格式
“As a <user>, I want <goal> so that <value>”
“In order to <value realized> as a <user>, I want
<goal>.”
範例
“In order for attendees to use my presentation as a
reference before and/or after my presentation (the
value) as a presenter (user), I want to provide a copy
of my presentation slides or handouts to the
attendees (goal).”
26. 範例
[user story] As a user, I want to reset my
password in the event that I forget it so that I
won’t get locked out.
[Task 1] reset password to temporary password
[Task 2] send email with temporary password
[Task 3] prompt user to change password after
logging in with temporary password.