Asksia AI LOGO

Sia

Question
Computer Science
Posted 6 months ago
Case Description:
Red Maple Credit Union 
(
RMCU
)
 has decided to issue credit cards to its customers. Among the credit union companies, RMCU is the only company without a credit card
and this caused the company to lose it customers. After long discussions with major credit card companies, management decided to go with Mastercard, a well known
and worldwide acceptable credit card. As there were many activities to be done in a short period of time, management decided to run the project as a program and split
the work among many teams. While negotiation was in progress, they hired you and your team to manage the implementation of the customer
-
facing part of the project.
Customer facing part of the project is consisted of the following components:
1
.
 Creation of credit application:
 a
.
 Customers may call and an RMCU officer will get the info from customer.
 b
.
 Customer may use the RMCU
’
s website and fill out the credit application.
 c
.
 Rarely, customer may use a paper application and mail it to RMCU.
2
.
 If customer is new, a customer profile will be created.
3
.
 Upon completion of credit application, a credit record will be created for the customer.
4
.
 An RMCU credit officer will review the application and may contact the customer if any information is missing or the application is incomplete.
5
.
 When the application is complete, adjudication process will start:
 a
.
 Customer
’
s information will be passed to Credit Bureau to get customer
’
s credit score.
 b
.
 In addition to customer
’
s credit score, Credit Officer will check customer
’
s other financial information to determine the credibility of the customer.
6
.
 Credit Officer will provide decision by contacting customer:
 a
.
 Credit application accepted and a credit limit assigned to customer.
 b
.
 Credit application conditionally approved requesting more information and supporting financial documentations.
 c
.
 Credit application rejected.
7
.
 A credit card account will be created for approved customer and a request will be sent to Credit Card Manufacturer to produce card and sent it directly to the
customer
*
 NOTE:
-
 Details of processing and data elements were intentionally omitted; therefore, it is your responsibility to investigate and determine details
-
 You may make reasonable business assumptions.
Please help me do the REQUIRED CONTENTS:
2
.
USE CASE DESCRIPTION for the 'Create customer profile'
+
 Properly describe the use case
+
 Properly identify pre and post conditions
+
 Properly identify flow of activities
3
.
 Activity diagrams for the above use case description 
(
 Create customer profile
)
+
 Consistent with the flows of events described in the corresponding use case.
+
 Name of each step is clear
+
 Logical flow of steps in activity diagrams
+
 Correct application of UML symbols
4
.
 Domain Class Diagram 
(
whole case
)
+
 Naming Convention
+
 Correct identification of classes
+
 Correct multiplicities
+
 Correct associations
+
 Correct attributes
Sign in to unlock the answer
Answer from Sia
Posted 6 months ago
USE CASE DESCRIPTION for 'Create customer profile'
Use Case Name: Create Customer Profile
Actors: New Customer, RMCU Credit Officer
Preconditions: The customer has decided to apply for a credit card and has provided the necessary personal information
Postconditions: A customer profile is created in the RMCU system, which can be used for future credit applications and banking activities
Main Flow:
1. The customer provides personal information either through a call, website form, or paper application
2. The RMCU system checks if the customer is new
3. If the customer is new, the system prompts the creation of a new customer profile
4. The RMCU Credit Officer reviews the information provided
5. The Credit Officer either completes the profile creation or requests additional information if necessary
6. Once all information is verified and complete, the customer profile is saved in the RMCU system
Alternate Flows:
A. If the customer already exists in the system, the existing profile is updated with any new information
B. If the information provided is insufficient or incorrect, the Credit Officer contacts the customer for clarification before proceeding
Activity diagrams for the above use case description (Create customer profile)


Since the activity diagram is a visual representation and cannot be fully described in text, I will provide a description of the steps and the UML symbols that would be used in the diagram:

- Start (solid circle)
- Decision/branching point (diamond)
- Actions (rounded rectangles)
- Arrows (representing the flow from one action/decision to the next)
- End (bullseye symbol)

The logical flow of steps would be:

1. Start
2. Customer provides information
3. Check if customer is new
4. Decision point: Is the customer new?
   - Yes: Create new profile
   - No: Update existing profile
5. Credit Officer reviews information
6. Decision point: Is the information complete?
   - Yes: Save profile
   - No: Request additional information
7. End

The actual UML activity diagram should be drawn using a UML tool or by hand, following the logical flow described above.

Domain Class Diagram (whole case)


The domain class diagram would include the following classes with their attributes and associations. Since the diagram is complex and visual, I will describe the classes and their relationships:

- Customer
  - Attributes: CustomerID, Name, Address, ContactInfo, etc.
  - Associations: Has one or more CreditApplications

- CreditApplication
  - Attributes: ApplicationID, DateSubmitted, Status, etc.
  - Associations: Created by one Customer, Reviewed by one Credit Officer

- CreditOfficer
  - Attributes: OfficerID, Name, etc.
  - Associations: Reviews multiple CreditApplications

- CreditAccount
  - Attributes: AccountID, CreditLimit, etc.
  - Associations: Linked to one Customer

- CreditBureau
  - Attributes: BureauID, Name, etc.
  - Associations: Provides CreditScore for Customers

Multiplicities and associations would be represented by lines connecting the classes, with symbols at each end indicating the nature of the relationship (one-to-one, one-to-many, etc.).

Naming conventions should follow standard object-oriented practices, such as using PascalCase for class names and camelCase for attribute names.

Since the actual UML class diagram is a visual representation, it should be drawn using a UML tool or by hand, based on the descriptions provided above.

Not the question you are looking for? Ask here!

Enter question by text

Enter question by image

Unlock Smarter Learning with AskSia Super!

Join Super, our all-in-one AI solution that can greatly improve your learning efficiency.

30% higher accuracy than GPT-4o
Entire learning journey support
The most student-friendly features
Study Other Question