The document discusses system analysis, defining it as the study of people, data, processes, and technology in organizational contexts. It emphasizes the importance of analyzing user needs and introduces concepts like use cases and features, with practical examples related to transaction systems. The author, Muhammed Nabil, shares insights from his experience and provides guidance on essential skills for aspiring analysts.

1. System analysis, the definition you
don’t know … Yet!!

2. “Dive into real life”

4. What is Analysis ? Really
OOP, The thing they don’t teach
you @ School.
What, Why and Why not?
Hands on Example
How to be an Analyst ?

7. Muhammed Nabil

8. System Analyst

9. +6 Years

12. B.Sc. in Computer Science

13. M.Sc. in Information system

14. What is system analysis ?

15. To know that!!

16. What is a System ?!
Isn’t That old ?!!!

17. An information system (IS) is
an arrangement of people
data, processes, and
information technology that
interact to collect, process,
store, and provide as output
the information needed to
support an organization.

18. Yes
People
WAllah
El
People

19. Client
Stakeholders
PM
End Users
Developers
QE/A

20. 11.8
%
12.8%
Incomplete Requirements
12.3%
7.5
%
Lack of Executive Support
15.9%
13%
13.9%
* THE STANDISH GROUP REPORT 2007

21. 44.4%
42.8%

23. Yea Yea they are people

27. What is system analysis ?

28. Analyzing people needs

29. Basics of Object Oriented Programming

30. Encapsulation
Inheritance
Abstraction
Polymorphism

31. Responsibilities…

32. Doing
Knowing

33. Where are we going ?

34. Impact and Gap analysis

38. Responsibilities…

39. What, Why and Why not?

40. Functional
Dynamic
Static
Solution View

43. Functional View

44. Static View

45. Dynamic View

46. “80% of your object modeling needs can be
satisfied with 20% of the notation”
- Scott Ambler

47. What Should I use ?

49. Hands on Example

50. A woman without her man is nothing
A woman without her. Man is nothing
A woman, without her man is nothing

52. What is a Feature ?
“A condition or capability to which a system must
conform”

53. Q: Is features enough ?!
A: Yes ..
When you are a Tailor

55. What is a Use Case?
“A sequence of actions a system performs that yields an
observable result of value to a particular actor. ”

56. Use Case contain :
Use Case Name
Brief Description
Flow of Events
• Basic Flow
• Sub-Flows
• Alternative flow
Special Requirements
Precondition
Post condition
Extension point

58. Alternative :
“Necessitating a choice between mutually
exclusive possibilities”
Webster
Extension:
“Act of expanding in scope; making
more widely available “
Webster

59. Example

61. Withdraw Features
• A withdrawal transaction asks the customer to choose a type of account to
withdraw from (e.g. checking) from a menu of possible accounts, and to
choose a dollar amount from a menu of possible amounts. The system
verifies that it has sufficient money on hand to satisfy the request before
sending the transaction to the bank. (If not, the customer is informed and
asked to enter a different amount.) If the transaction is approved by the
bank, the appropriate amount of cash is dispensed by the machine before
it issues a receipt. (The dispensing of cash is also recorded in the ATM's
log.)
• A withdrawal transaction can be cancelled by the customer pressing the
Cancel key any time prior to choosing the dollar amount.

63. Give it a try ?!!

64. Use Case Name Withdraw amount
Use Case ID WA-01
Trigger Customer selects to withdraw money
Precondition The user is identified as authenticated through his PIN number
Basic Flow 1. System displays available accounts type according to the customer
ID.
2. Customer select specific accounts.
3. System displays default amounts.
4. Customer select specific amount.
5. System verifies the ATM has sufficient money.
6. System verifies with the bank that the account has sufficient
money.
7. System approve transaction, dispense amount
8. Customer retrieve amount and Card
9. System generate receipt.
Alternative Flow 5.1 ATM doesn’t have enough money, display message and go to step 4
6.1 Customer balance not enough, display message and go to step 4
8.1 Customer didn’t retrieve card and money on time, Hold the card
and the amount and display message and produce receipt
Post condition Transaction status recoded in the system

65. How to be an Analyst ?

66. Analytical Skills
Problem solver
Excellent communication Skills
UML+
Programming experience
Documentation skills
starter
Self-

67. Questions ?

68. Mohamed.alsaid@gmail.com
http://analystinside.blogspot.com
@Muhammed_Nabil