Case Study Assignment - Part 3: GAA Information System Analysis

This case study assignment analyzes the GAA information system, providing a comprehensive overview of its design and functionality. The assignment includes various diagrams such as use case diagrams, class diagrams, activity diagrams, sequence diagrams, and state machine diagrams, which visually represent the system's components and processes. Detailed use case descriptions are provided for stakeholder registration and the payment process, outlining preconditions, postconditions, and alternative scenarios. The quality assurance statement assesses the system's design and diagrammatical models. The document also includes a bibliography of relevant software engineering resources, demonstrating the research and methodologies employed in the analysis. This assignment showcases the student's understanding of system design, software engineering principles, and the ability to apply these concepts to a real-world case study.

Running Head: CASE STUDY ASSIGNMENT - PART 3
Case Study Assignment - Part 3
[Name of the student]
[Name of the university]

2CASE STUDY ASSIGNMENT - PART 3
Table of Contents
Use Case Diagrams 3
Use Case Descriptions 3
Class Diagram 6
Activity Diagram 7
Sequence Diagram 8
State Machine Diagram 9
Quality Assurance Statement 9
Bibliography 10

3CASE STUDY ASSIGNMENT - PART 3
Use Case Diagrams
Figure 1: Use case diagram of GAA information system
(Source: Created by author)
Use Case Descriptions
Use Case ID: STAKEHOLDER_REGISTRATION
Use Case Registering Stakeholders

4CASE STUDY ASSIGNMENT - PART 3
Name:
Created By: Author Last Updated By: Author
Date Created: 11/1/2017 Date Last
Updated:
11/1/2017
Actor: Stakeholders
Description: Register a donor or stakeholder into the information system
for transferring or donate specified amount.
Preconditions: Stakeholder data must not store or register before as well as
the following data title, first name, last name, mobile phone
number, contact and address must be provided during
registration.
Post conditions: Stakeholders must accept and follow the registration terms
and conditions.
Priority: Normal
Frequency of Use: Once
Normal Course of
Events:
One
Alternative Courses: Login (if already registered)
Exceptions: Input validation error, wrong information provided
Includes: Non
Special Requirements: Non
Assumptions: This process is required whenever the stakeholder wants to
donate some amount for projects or programs. However, the
stakeholder may donate as an anonymous, where they do not
have to register themselves in this system.
Notes and Issues: Non.
Use Case ID: Payment
Use Case
Name:
Donate amount
Created By: Author Last Updated By: Author
Date Created: 11/1/2017 Date Last
Updated:
11/1/2017
Actor: Stakeholder
Description: The payment process is made by a stakeholder or donor. This
process includes many parameters from the stakeholder as
well as recipient. A payment process is proceeding by
stakeholder, powered by Exidebit and/or POLi.
Preconditions:  Stakeholders must select donation type, select region,
donation amount and/or registration/login.

5CASE STUDY ASSIGNMENT - PART 3
 Card payment include name on card, card number,
expiry date and CVV number.
Post conditions: NON
Priority: High
Frequency of Use: one-off, monthly or yearly
Normal Course of
Events:
Non.
Alternative Courses: Non.
Exceptions: Wrong payment information, insufficient balance, third party
technical failure.
Includes: Ezidebit, POLi
Special Requirements: Non
Assumptions: This process includes various transfer of amounts to the
recipient.
Notes and Issues: System failure or security issues must be noted.

6CASE STUDY ASSIGNMENT - PART 3
Class Diagram
Figure 2: Class diagram of GAA information system
(Source: Created by author)

7CASE STUDY ASSIGNMENT - PART 3
Activity Diagram

8CASE STUDY ASSIGNMENT - PART 3
Figure 3: Activity diagram of GAA information system
(Source: Created by author)
Sequence Diagram
Figure 4: Sequence diagram of GAA information system
(Source: Created by author)

9CASE STUDY ASSIGNMENT - PART 3
State Machine Diagram
Figure 5: State machine diagram of GAA information system
(Source: Created by author)
Quality Assurance Statement
The quality assurance statement defines an inspection of the GAA information system
and developed diagrammatical models of their information system. In this stander operating
procedure they have managed a donation system to the poorest or neediest communities. The
findings of this study is the use case diagram define the actors present in this system, a use case
description for developed use case diagram define details operations, a class diagram showing
the variables and method can include in this system. However, those are logical presentation of
that system, where activity, sequence and state machine diagram also support the system design.

10CASE STUDY ASSIGNMENT - PART 3
Bibliography
Arcuri, A. and Briand, L., 2014. A hitchhiker's guide to statistical tests for assessing randomized
algorithms in software engineering. Software Testing, Verification and Reliability, 24(3),
pp.219-250.
Bertolino, A., Blake, M.B., Mehra, P., Mei, H. and Xie, T., 2015. Software engineering for
internet computing: Internetware and beyond [guest editors' introduction]. IEEE Software, 32(1),
pp.35-37.
Bourque, P. and Fairley, R.E., 2014. Guide to the software engineering body of knowledge
(SWEBOK (R)): Version 3.0. IEEE Computer Society Press.
De Lemos, R., Giese, H., Müller, H.A., Shaw, M., Andersson, J., Litoiu, M., Schmerl, B.,
Tamura, G., Villegas, N.M., Vogel, T. and Weyns, D., 2013. Software engineering for self-
adaptive systems: A second research roadmap. In Software Engineering for Self-Adaptive
Systems II (pp. 1-32). Springer Berlin Heidelberg.
Juristo, N. and Moreno, A.M., 2013. Basics of software engineering experimentation. Springer
Science & Business Media.
Mall, R., 2014. Fundamentals of software engineering. PHI Learning Pvt. Ltd..
Rich, C. and Waters, R.C. eds., 2014. Readings in artificial intelligence and software
engineering. Morgan Kaufmann.
Wohlin, C., 2014, May. Guidelines for snowballing in systematic literature studies and a
replication in software engineering. In Proceedings of the 18th international conference on
evaluation and assessment in software engineering (p. 38). ACM.