Contoh

3.
3 USE CASE DIAGRAM
Figure 3.1. Use case diagram
1
3.4 USE CASE SCENARIOS
3.4.1 Register Account
Use Case ID : UC-01
Use Case name : Register Account
Actor : User
Precondition :  User should not have an existing account in the

database.
Post Condition :  User create an account successfully.

 User must be able to login.
 User able to have an account with anonymous id.
Trigger : User click on the Register Button.
Main Success Scenario
1. User fills all information in the registration form.

2. User clicks on Register button.
3. System will add user into database and create an anonymous id.
4. System will display registration successful.
Extensions
1. User enters incorrect format in registration form.

2. User register with an id or username which exists in the database.
3. Registration form are not fill completely.
2
3.4.2 View Account
Use Case ID : UC-02
Use Case name : View Account
Actor : User, Admin
Precondition :  Account exist in the database.

 User and Admin log into the application.
Post Condition :  User and Admin can view own account details.
Trigger : User and Admin want to view own details.
1. User/Admin login into the application.

2. User/Admin click on their own profile.
3. User/Admin profile is shown.
Extensions
1. User or Admin is not log in.
2. Unauthorized user log in the account.
3
3.4.3 Update Profile
Use Case ID : UC-03
Use Case name : Update Profile
Actor : User
Precondition :  User is authorize user.

 User has the permission to update the profile.
Post Condition :  User profile is updated.
Trigger : User want to update/edit their own profile.
1. User view in their own profile.

2. User click on the button ‘Update/Edit’
3. User made changes in their profile details.
4. User click button ‘Update’ to confirm their changes.
5. System will change the details and store the latest detail in the database.
6. Changes made.
Extensions
1. User not able to update/edit their profile.
2. Unauthorized user update/edit the profile.
4
3.4.4 Create Chatroom
Use Case ID : UC-04
Use Case name : Create Chatroom
Actor : User
Precondition :  User is log in.
Post Condition :  Chatroom is created.
Trigger : User want to create chatroom.
1. User click on the ‘Create Chatroom’ button.

2. User fill in the details and able to invite others.
3. User click on confirm to create the chatroom.
4. Chatroom is created.
Extensions
1. User key in wrong user to invite.
2. User unable to create the chatroom.
5
3.4.5 Join Chatroom
Use Case ID : UC-05
Use Case name : Join Chatroom
Actor : User
Post Condition :  User join a chatroom.
Trigger : ‘Join Chatroom’ button is clicked.
1. User click on ‘Join Chatroom’ button.

2. User need to fill in the chatroom id to request join the chatroom.
3. User able to join the chatroom when request is approve.
Extensions
1. User being rejected to join the chatroom.
2. User find or key in the wrong chatroom id.
6
3.4.6 Send Message
Use Case ID : UC-06
Use Case name : Send Message
Actor : User
Precondition :  User is online.

 User send message to receiver.
Post Condition :  User message is send to other users.
Trigger : User want to send message to other users.
1. User click on the chatroom.

2. User write the message.
3. User click on the button ‘Send’.
4. Message is sent.
Extensions
1. User network is failed to connect.
2. User sent the message to the wrong user.
7
3.4.7 Receive Message
Use Case ID : UC-07
Use Case name : Receive Message
Actor : User
Precondition :  User is online.

 User able to receive message from others.
Post Condition :  User receive message from other users.
Trigger : User is online.
1. User is online.
Extensions
1. User is not the user to receive the message.
2. User got network issue.
3. User unable to receive message from other user.
8
3.4.8 Leave Chatroom
Use Case ID : UC-08
Use Case name : Leave Chatroom
Actor : User
Precondition :  User exist in the chatroom.
Post Condition :  User leave the chatroom.
Trigger : User want to leave the chatroom.
1. User click on the button ‘Leave Chatroom’.

2. User need to click confirm to leave the chatroom.
3. User able to leave the chatroom after click it.
4. System will erase user from the chatroom.
Extensions
1. User unable to leave the chatroom.
2. User account still exist in the chatroom after leave chatroom.
9
3.4.9 Upload Confession
Use Case ID : UC-09
Use Case name : Upload Confession
Actor : User
Precondition :  User is authorize user.
Post Condition :  Confession is upload in the confession board.
Trigger : User want to confess on the confession board.
1. User go to the confession board.

2. User click on upload.
3. User write their confession then click confirm upload.
4. Confession is uploaded.
Extensions
1. User does not go anonymous mode.
2. User upload failed.
10
3.4.10 Update/Comment Own Confession
Use Case ID : UC-10
Use Case name : Update/Comment Own Confession
Actor : User
Precondition :  User is the owner of the confession that confess in

the confession board.
Post Condition :  Update/Comment is create and post on user own

confession.
Trigger : User want to edit/update and comment on its own

confession.
1. User go to their confession.

2. If user want to update their confession,
2.1 User click on update.
2.2 User change or edit their confession.
2.3 After changes, user click on confirm to update their confession.
3. If user want to do comment on their confession,
3.1 User write the comment.
3.2 User click on the button ‘Post’.
3.3 User comment is post on the confession.
4. User confession is update.
Extensions
1. User unable to comment on own confession.
2. User unable to do changes in their confession.
11
3.4.11 View in the Confession Board
Use Case ID : UC-11
Use Case name : View in the Confession Board
Actor : User
Post Condition :  User able to view others confession in confession

board.
Trigger : User want to view the confession board.
1. User go to confession board.

2. All confession is shown in the confession board.
3. User click on the confession.
4. User can view the confession.
Extensions
1. No confession is shown when there is data store in the database.
2. User unable to click on the confession.
12
3.4.12 Comment in Confession Board
Use Case ID : UC-12
Use Case name : Comment in Confession Board
Actor : User

 User is not being blocked.
Post Condition :  Comment is written and post.
Trigger : User want to comment other people confession.
1. User go to confession board.

2. User click on the confession.
3. User write comment in the confession.
4. User post it in the confession.
5. User comment is post in the confession.
Extensions
1. User unable to post comment in the confession.
2. User comment in foul language.
13
3.4.13 Block User
Use Case ID : UC-13
Use Case name : Block User
Actor : Admin
Precondition :  User being report by other users.

 User break the rules.
 Admin has the permission to block.
Post Condition :  If Admin approve to block the user, user will be

blocked in a period of duration and warning is
given.
 If the user done the same for few time, block
permanently will be given.
 If Admin check the user is innocent, Admin will not
block the user.
Trigger : User being reported and confirm break the rules.
1. Admin login into admin account.

2. Admin receive report from other user.
3. Check the activity of the user.
4. If the user done for 0-3 times,
4.1 Admin click block in a period of time.
4.2 Choose the period of time.
4.3 Click confirm.
4.4 System will generate warning message to user.
5. If the user done more than 3 times,
5.1 Admin click block permanently button.
5.2 Click confirm.
5.3 Update status.
5.4 System will generate the block permanently message.
6. If the user is innocent,
14
6.1 Admin click reject button.
6.2 Click confirm.
6.3 System will generate message to user.
7. System will store the status.
Extensions
1. Admin block innocent user.
15
3.4.14 View User
Use Case ID : UC-14
Use Case name : View User
Actor : Admin
Precondition :  Admin is log in.

 Admin has the permission to view the user.
Post Condition :  Admin able to view user.
Trigger : Admin want to view user profile.

2. Admin has the authority to view the user.
3. Admin click on view user.
4. User details shown.
Extensions
None.
16
3.4.15 Add Permission
Use Case ID : UC-15
Use Case name : Add Permission
Actor : Admin
Precondition :  Admin has the authority to give permission.
Post Condition :  User gain permission from Admin.
Trigger : Admin give permission to the user.

2. Admin has the authority to give permission.
3. Admin click on the user.
4. Admin give permission.
5. System gave permission to the user.
Extensions
None
17
3.4.16 Generate Statistic/Report
Use Case ID : UC-16
Use Case name : Generate Statistic/Report
Actor : Admin
Precondition :  Admin has the authority to generate report.
Post Condition :  Statistic/Report generated.
Trigger : Admin want to view report

2. Admin click on report.
3. Admin choose the statistic/report want to generate.
4. System will get the details of the information.
5. System will generate the report.
Extensions
None
18
3.5 ACTIVITY DIAGRAMS
Figure 3.2: Register Account
19
3.5.2 View Account
Figure 3.3: View Account
20
Figure 3.4: Update Profile
21
Figure 3.5: Create Chatroom
22
3.5.5 Join Chatroom
Figure 3.6: Join Chatroom
23
3.5.6 Send Message
Figure 3.7: Send Message
24
Figure 3.8: Receive Message
25
Figure 3.9: Leave Chatroom
26
Figure 3.10: Upload Confession
27
Figure 3.11: Update/Comment Own Confession
28
Figure 3.12: View in the Confession Board
29
Figure 3.13: Comment in Confession Board
30
3.5.13 Block User
Figure 3.14: Block User
31
3.5.14 View User
Figure 3.15: View User
32
Figure 3.16: Add Permission
33
Figure 3.17: Generate Statistic/Report
34
Figure 3.17:
3.6 SEQUENCE DIAGRAMS

Figure 3.18: Register Account
35
3.6.2 View Account
Figure 3.19: View Account
36
Figure 3.20: Update Profile
37
Figure 3.21: Create Chatroom
38
3.6.5 Join Chatroom
Figure 3.22: Join Chatroom
39
3.6.6 Send Message
Figure 3.23: Send Message
40
Figure 3.24: Receive Message
41
Figure 3.25: Leave Chatroom
42
Figure 3.26: Upload Confession
43
Figure 3.27: Update/Comment Own Confession
44
Figure 3.28: View in the Confession Board
45
Figure 3.29: Comment in Confession Board
46
3.6.13 Block User
Figure 3.30: Block User
47
3.6.14 View User
Figure 3.31: View User
48
Figure 3.32: Add Permission
49
Figure 3.33: Generate Statistic/Report
50
3.7 CLASS DIAGRAM
Figure 3.34: Class Diagram
51
3.8 CONCLUSION
In conclusion, agile methodology is used in this proposed project as introduced in this
chapter where agile methodology can easily adapt changes using sprint. After agile
methodology, UML diagrams are illustrated in sections 3.3, section 3.5, section 3.6,
and section 3.7 which are the use case diagram, activity diagrams, sequence diagrams,
and class diagram. It is being used as a guide and reference when implementing the
system which can ensure the system are implemented in the workflow of each
diagram so that all requirement of the project system can be achieved.
52
REFERENCES
Adenowo, A. A., & Adenowo, B. A. (2013). Software engineering methodologies: a
review of the waterfall model and object-oriented approach. International Journal of
Scientific & Engineering Research, 4(7), 427-434.
Anwer, F., Aftab, S., Shah, S. M., & Waheed, U. (2017). Comparative analysis of two
popular agile process models: extreme programming and scrum. International Journal
of Computer Science and Telecommunications, 8(2), 1-7.
Clark-Gordon, C. V., Workman, K. E., & Linvill, D. L. (2017). College students and
Yik Yak: An exploratory mixed-methods study. Social Media+ Society, 3(2),
2056305117715696.
Coyner, Sandra C. and McCann, Peggy L. (2017) "Electronic Anonymous

Communications: Considerations for Higher Education Administrators," Journal of
Research, Assessment, and Practice in Higher Education : Vol. 2 : Iss. 1 , Article 5.
Di Lucca, G. A., & Fasolino, A. R. (2006). Testing Web-based applications: The state
of the art and future trends. Information and Software Technology, 48(12), 1172-
1186.
Flora, H. K., Chande, S. V., & Wang, X. (2014). Adopting an agile approach for the
development of mobile applications. International Journal of Computer Applications,
94(17).
Islam, R., Islam, R., & Mazumder, T. (2010). Mobile application and its global
impact. International Journal of Engineering & Technology (IJEST), 10(6), 72-78.
Kang, R., Dabbish, L., & Sutton, K. (2016, February). Strangers on your phone: Why
people use anonymous communication applications. In Proceedings of the 19th ACM
conference on computer-supported cooperative work & social computing (pp. 359-
370).
Koratana, A., Dredze, M., Chisolm, M. S., Johnson, M. W., & Paul, M. J. (2016,
March). Studying anonymous health issues and substance use on college campuses
with yik yak. In Workshops at the Thirtieth AAAI Conference on Artificial
Intelligence.
53
Leskovich, W. R. (2015, May). Yik Yak: a social media sensor. In Next-Generation
Analyst III (Vol. 9499, p. 949904). International Society for Optics and Photonics.
Mahalakshmi, M., & Sundararajan, M. (2013). Traditional SDLC vs scrum

methodology–a comparative study. International Journal of Emerging Technology
and Advanced Engineering, 3(6), 192-196.
Ma, X., Andalibi, N., Barkhuus, L., & Naaman, M. (2017, May). " People Are Either
Too Fake or Too Real" Opportunities and Challenges in Tie-Based Anonymity. In
Proceedings of the 2017 CHI conference on human factors in computing systems (pp.
1781-1793).
Moroney, L. (2017). The firebase realtime database. In The Definitive Guide to

Firebase (pp. 51-71). Apress, Berkeley, CA.
Northcut, K. M. (2015, July). Dark side or insight? Yik Yak and culture on campus.
In 2015 IEEE International Professional Communication Conference (IPCC) (pp. 1-
5). IEEE.
Ohyver, M., Moniaga, J. V., Sungkawa, I., Subagyo, B. E., & Chandra, I. A. (2019).
The comparison firebase realtime database and MySQL database performance using
wilcoxon signed-rank test. Procedia Computer Science, 157, 396-405.
Son H.H., Lan D.T.N., Hoang N.T., Tam D.M., Phuc P.T., Huong T.T. (2021) Mining
Students’ Topics of Interest and Innermost Feelings Through Confession Pages. In:
Russo D., Ahram T., Karwowski W., Di Bucchianico G., Taiar R. (eds) Intelligent
Human Systems Integration 2021. IHSI 2021. Advances in Intelligent Systems and
Computing, vol 1322. Springer, Cham. https://doi.org/10.1007/978-3-030-68017-
6_42
Van Casteren, W. (2017). The Waterfall Model and the Agile Methodologies: A
comparison by project characteristics. Research Gate, 2, 1-6.
Williams, G., & Mahmoud, A. (2018, August). Modeling user concerns in the app
store: A case study on the rise and fall of yik yak. In 2018 IEEE 26th international
requirements engineering conference (rE) (pp. 64-75). IEEE.
54
Wu, W. (2018). React Native vs Flutter, Cross-platforms mobile application
frameworks. Zammetti, F. (2018). React native: a gentle introduction. In Practical
React Native (pp. 1-32). Apress, Berkeley, CA.
Zammetti, F. (2018). React native: a gentle introduction. In Practical React Native

(pp. 1-32). Apress, Berkeley, CA.
55

Contoh

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Contoh

Uploaded by

Copyright:

Available Formats

3.

3 USE CASE DIAGRAM

Figure 3.1. Use case diagram

Use Case name : Register Account

Precondition :  User should not have an existing account in the

Post Condition :  User create an account successfully.

Trigger : User click on the Register Button.

Main Success Scenario

1. User fills all information in the registration form.

1. User enters incorrect format in registration form.

Use Case name : View Account

Actor : User, Admin

Precondition :  Account exist in the database.

Trigger : User and Admin want to view own details.

Main Success Scenario

1. User/Admin login into the application.

1. User or Admin is not log in.

2. Unauthorized user log in the account.

Use Case name : Update Profile

Precondition :  User is authorize user.

Post Condition :  User profile is updated.

Trigger : User want to update/edit their own profile.

Main Success Scenario

1. User view in their own profile.

1. User not able to update/edit their profile.

2. Unauthorized user update/edit the profile.

Use Case name : Create Chatroom

Precondition :  User is log in.

Post Condition :  Chatroom is created.

Trigger : User want to create chatroom.

Main Success Scenario

1. User click on the ‘Create Chatroom’ button.

1. User key in wrong user to invite.

2. User unable to create the chatroom.

Use Case name : Join Chatroom

Precondition :  User is log in.

Post Condition :  User join a chatroom.

Trigger : ‘Join Chatroom’ button is clicked.

Main Success Scenario

1. User click on ‘Join Chatroom’ button.

1. User being rejected to join the chatroom.

2. User find or key in the wrong chatroom id.

Use Case name : Send Message

Precondition :  User is online.

Post Condition :  User message is send to other users.

Trigger : User want to send message to other users.

Main Success Scenario

1. User click on the chatroom.

1. User network is failed to connect.

2. User sent the message to the wrong user.

Use Case name : Receive Message

Precondition :  User is online.

Post Condition :  User receive message from other users.

Trigger : User is online.

Main Success Scenario

1. User is not the user to receive the message.

2. User got network issue.

3. User unable to receive message from other user.

Use Case name : Leave Chatroom

Precondition :  User exist in the chatroom.

Post Condition :  User leave the chatroom.

Trigger : User want to leave the chatroom.