Home > Articles > Programming > Java

  • Print
  • + Share This
This chapter is from the book

3.3 CUSTOMER-ACCOUNT MANAGEMENT

What. book_icon.jpg Many businesses use accounts to track the credits and debits that a customer makes within a given context of dealing with that business. Rental businesses often use accounts to keep track of rentals and returns. Telephone companies use accounts to track credits and debits for telecommunications services. Financial institutions use accounts in perhaps the widest variety of contexts: checking, savings, loans, and various combinations.

Scope. Customer-account management begins with an application and ends with account transactions.

Steps. First, accept a customer-account application. Second, evaluate the application. Third, approve or reject it. Fourth, if accepted, generate a new customer account. Fifth, make customer transactions, recording debits, credits, or both.

Links. Post account transactions (accounting management).

Mirror images. In customer-account management, we establish and maintain accounts so we can track and present on-going business activity from a customer's perspective. In accounting management, we establish and maintain accounts to track the overall business financially, organized as specified by management, by a regulatory authority (in some countries), or both.

Components. The components within customer-account management are (Figure 3-26):

  • Customer-account application
  • Customer account
  • Customer-account transaction
03fig26.jpg

Figure 3-26 Customer-account management.

Moment-intervals. The main moment-intervals for customer-account management are (Figure 3-27):

  • Customer-account application, linked via customer account to
  • Customer-account transaction
03fig27.jpg

Figure 3-27 Summary in pink.

Interactions. The components work together to get things done. An example of inter-component interaction, "rate an applicant," is shown in Figure 3-28. A sender asks a yellow applicant to rate itself. It gets its credit rating (an attribute value; credit rating could be a pink moment-interval, and credit-rating agency could be a yellow role; yet if all we care about is the current value, then that adds model complexity we don't need).

03fig28.jpg

Figure 3-28 Rate a customer-account applicant.

Also note the attribute in application, credit rating at time of application. Although applicant has its credit rating, that credit rating might change over time. Perhaps we are not interested in how those values change (pink moment-interval) yet we do need to keep the value at the time of the application. That's what the "credit rating at the time of application" attribute is all about.

The same party participating as an applicant in this context might already be an account holder, a different role. So an applicant asks its green party (in the party component) to get its account holder. As shown in the relationship-management component, a role may be a grouping of other roles. So an applicant role might be a collection of other role-players acting together as an applicant group.

A party returns its yellow account holder (or a null, if no account holder exists).

A yellow applicant asks a yellow account holder to rate itself. The account holder then iterates across its collection of accounts, asking each one to calculate its average daily balance and to calculate its average daily volume (for example, the average daily amount of money flowing in and out of an account).

Expansion. One could expand this compound component by adding methods to scan current account features and suggest additional ones (telephone companies seem very good at this). One could also expand it with financial-service account details (fees, special instructions, discounts, and inter-institution transfers).

3.3.1 Customer-Account Application

03fig29.jpg

Figure 3-29 Customer-account application component.

Customer-account application. A pink customer-account application links to three yellow roles: customer-account applicant, application approver, and an organizational entity responsible for accounts (for example, a bank or some other financial institution).

A customer-account application links to a blue customer-account description, indicating the kind of account the application is for. A customer-account application also links to two collections of blue customer-account feature descriptions, selections (of optional features) and additions (of features above and beyond those normally offered for this kind of customer account).

A blue customer-account description links to two collections of customer-account feature descriptions, required features and optional features.

A blue customer-account feature description links to other customer-account feature descriptions, linking to sub-features, "must combine with" features, and "cannot combine with" features.

Before and after. For customer-account application, the subsequent pink moment-interval is customer transaction (via a green customer account).

Methods. Key methods include: make customer-account application, check compatibility of features, generate account, and assess quality of resulting accounts.

Interactions. The "check compatibility of features" sequence is shown in Figure 3-30. (Note: invoke this method after adding or removing a number of features; invoking it with each add or remove results in too many transient errors.) A sender asks a pink customer-account application to check the compatibility of its features. It asks its customer account description, representing the kind of account, to check the compatibility of selected and additional features (passed along as arguments). Finally, a customer-account description interacts with its customer-account feature descriptions, checking for compatibility, including "must combine" and "cannot combine" constraints.

03fig30.jpg

Figure 3-30 Check compatibility of features.

3.3.2 Customer Account

03fig31.jpg

Figure 3-31 Customer-account component.

Customer account. A green customer account links to two yellow roles, customer-account holder and organizational entity responsible for accounts (derivable via the customer-account application). It also links to one or more blue customer-account feature descriptions.

Before and after. For customer account, the preceding pink moment-interval is customer-account application. The subsequent pink moment-interval is customer-account transaction (two collections: "all" and "current reporting period").

Methods. Key methods include: make customer account, calculate average daily balance, and calculate average daily volume (the flow in and out of an account).

Interactions. The "calculate average daily balance" sequence is shown in Figure 3-32. A sender asks a green account to calculate its average daily balance. It asks each of its "current reporting period" pink transactions for its date and its total, determines the result, and returns it to the sender.

03fig32.jpg

Figure 3-32 Calculate average daily balance.

3.3.3 Customer-Account Transaction

03fig33.jpg

Figure 3-33 Customer-account-transaction component.

Customer-account transaction. A pink customer-account transaction links to three yellow roles: customer-account holder (derivable, via customer account), organizational entity responsible for accounts (derivable,via customer account then customer application), and facility as business location (the location where a given customer-account transaction takes place). It also links to pink customer-account transaction detail(s).

Customer-account transaction detail. A pink customer-account transaction detail specifies a credit (with a positive amount) or a debit (with a negative amount). A customer-account transaction detail links to a green customer account.

Before and after. For customer-account transaction, the preceding pink moment-interval is customer application (via a green account). The subsequent pink moment-interval is an accounting posting of the transaction.

Methods. Key methods include: make customer-account transaction and calculate average customer-account transaction.

Interactions. The "calculate average customer-account transaction" sequence is shown in Figure 3-34. A sender asks a yellow facility as business location to calculate its average customer-account transaction. It asks each of its pink customer-account transactions to calculate its total. A transaction then gets its total and returns it (if a buffered value is present); otherwise it (re)calculates the total by asking each of its pink transaction details for its amount, and then returns the total. Finally, a facility as business location totals it all, gets the number of transactions, calculates the average, and returns the result to the sender.

03fig34.jpg

Figure 3-34 Calculate average customer-account transaction.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020