Aseproj

INF207-E/205/2006
INF207-E
OBJECT-ORIENTED CONCEPTS
DEPARTMENT OF SYSTEMS DEVELOPMENT
SCHOOL OF COMPUTING
UNISA
TUTORIAL LETTER 205 FOR INF207-E

Solution to Assignment 5
inf207@osprey.unisa.ac.za
http://osprey.unisa.ac.za
TABLE OF CONTENTS
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Nota aan Afrikaanssprekende studente
.............................................. 3
Tutorial matter that you should have received to date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

I have lost / did not receive certain study material! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
How do I download study material or access the discussion forum? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
.................................................................. 4
Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
INF207-E/205
Introduction
Nota aan Afrikaanssprekende studente
NOTA AAN AFRIKAANSSPREKENDE STUDENTE

Hierdie studiebrief bevat n bespreking en n moontlike oplossing vir Werkopdrag 3. Aangesien die
voorgeskrewe boek en die studiegids in Engels is, verskaf ons die antwoorde ook in Engels. Indien u
enige probleme met die Engels ondervind, kontak asseblief een van die dosente.
Tutorial matter that you should have received to date
INF207-E/101/2005
General information, study programme, exam admission & assignments
INF207-E/102/2005
Contact Information
INF207-E/201/2005
Discussion of Assignment 1
INF207-E/202/2005
INF207-E/203/2005
INF207-E/204/2005
INF207-E/205/2005
Discussion of Assignment 5 (This tutorial letter)
I have lost / did not receive certain study material!

Call the Despatch Department and request a copy of the particular tutorial matter;
OR
Download a copy of the material from the module Web page. The username and password for the download
area is available in your COS-ALL/301/2006.
PLEASE DO NOT CALL/EMAIL LECTURERS IF YOU DO NOT HAVE THE STUDY MATERIAL. WE
CANNOT PROVIDE IT.
How do I download study material or access the discussion forum?

Please refer to your INF207-E/101/2006, INF207-E/201/2006 or COSALL/301/2006 tutorial letters.
ASSIGNMENT 5
Due Date: 17 July 2006
Maximum credits: 100
Marks: 100
Study Letter 101 (this letter)
Study Letter 501
SCHACH : Chapters 1-10
Please use a word processor to do this assignment.
Turn to Appendix A in the prescribed book, the Chocoholics Anonymous project.

1) Perform the requirements workflow of the Chocoholics Anonymous project.
[50]
2) Perform the analysis workflow of the Chocoholics Anonymous project.
[50]
Solution
1) Requirements Workflow of the Chocoholics Anonymous Project
The initial glossary of the Chocoholics Anonymous project is depicted below:
Accounts payable
Money ChocAn is obligated to pay to providers for services they

have rendered
Chocolate
A food prepared from ground roasted cacao beans that is truly

delicious but can be addictive.
Chocoholics
Anonymous
(ChocAn)
Electronic
An organization dedicated to helping people addicted to

chocolate in all its glorious forms.
fund
(EFT)
transfer
An automated process by which funds are transferred from one

bank account to another. In the case of ChocAn, funds are
transferred on a weekly basis to the bank accounts of the
individual providers.
Invalid number
A number that identifies a member who is inactive or a number

that is not in the information system.
Member number
A 9-digit number that uniquely identifies each member of
INF207-E/205
5
ChocAn.
Member status
Active, Inactive, Suspended.
Magnetic tape
A data storage medium where the EFT data are kept.
Member suspended
The member number is valid but the member has not paid his or
her dues
Provider
An individual who provides services to paying members of

ChocAn, including dietitians, internists, and exercise specialists.
Provider directory
A directory that holds the service codes, descriptions of the

services, and the amount to be paid for each service.
Provider number
A 9-digit number that uniquely identifies each ChocAn provider.
Provider status
Active, Inactive.
Provider type
Internist, Dietitian, Exercise Specialist.
Service code
A 6-digit number that uniquely identifies a service provided to a

member.
(For example, 598470 denotes a session with a
dietitian.)
Validation
The process of checking that the members number is correct

and that the member has paid all dues currently owed.
Visit
An occasion on which a consultation, exercise session, or other

service is provided to a member.
Initial ChocAn glossary
ChocAn
Information
System
Maintain
Member
Maintain
Provider
Verify
Member Status
Add Visit
Member
Provider
Print Member
Report
Print Provider
Report
include
Print Manager
Report
Figure 1. Use-case diagram for ChocAn.
Print EFT
Report
The use case Maintain Member combines use cases Add Member and Update Member, and similarly for
Maintain Provider. The use-case diagram is shown in Figure 1. Descriptions of the use cases appear in
Figures 2 through 8.
Brief description:
The Maintain Member use case enables a provider to enter new member data or update existing
member data given by the member.
Step-by-step description:
1.
The provider enters or updates data given by the member:

Name
Address
City
State
ZIP code
Date of last payment
Status (Active, Inactive, Suspended)
Figure 2. Description of the Maintain Member use case for ChocAn.

Brief description:
The Maintain Provider use case enables a provider to enter new provider data or update existing
provider data.
1.
The provider enters or updates provider information including:

Name
Address
City
State
ZIP code
Type (Internist, Dietitian, Exercise Specialist)
Status (Active, Inactive)
Figure 3. Description of the Maintain Provider use case for ChocAn.
INF207-E/205
Brief description:
The Verify Member Status use case enables the provider to validate a members status by
entering the member number into the system.
1
The provider enters the member number that is to be validated.
2.
The ChocAn information system informs the provider regarding the member status.
Figure 4. Description of the Verify Member Status use case for ChocAn.
Brief description:
The Add Visit use case enables a provider to enter details of a members visit into the ChocAn
information system.
1.
The provider enters the member number.
The ChocAn information system checks whether the member number is valid. If so, the
provider enters his or her provider number.

3.
Then information is written by the ChocAn information system to a file, including:

Current date and time
Date of visit
Provider name, number, and type
Member name and number
Service code, name, and description of visit
Additional comments
Figure 5. Description of the Add Visit use case for ChocAn.
Brief description:
The Print Member Report use case enables a member to receive a list of all the services provided
to that member during the current week.
1.
The ChocAn information system prints a report of all visits by each member during the
current week, including:

Member name, number, address, city, state, ZIP code.
For each service provided:
Date of service
Provider name
Service name
Figure 6. Description of the Print Member Report use case for ChocAn.
Brief description:
The Print Provider Report use case enables a provider to receive a list of all the services
provided by that provider during the current week.
1.
The ChocAn information system prints a report of services provided by each provider during
the current week, including:
Provider name, number, address, city, state, ZIP code.
Date of service
Date and time data received from computer
Service code
Fee to be paid
Total number of consultations with members
Total fee for the week
Figure 7. Description of the Print Provider Report use case for ChocAn.
INF207-E/205
Brief description:
The Print EFT Report enables the ChocAn information system to print a list of funds to be
transferred to the providers bank accounts.
1.
The ChocAn information system prints the EFT report including:

Provider name and number
Amount to be transferred to providers account
Figure 8. Description of the Print EFT Report use case for ChocAn.
Brief description:
The Print Manager Report use case enables a ChocAn manager to print the Accounts Payable
report summarizing the fees to be paid for the current week and the total number of visits to
providers.
1.
The ChocAn information system prints a report including:

The name of every provider to be paid for the current week
The number of consultations each provider had
His or her total fee for the week
The total number of providers who had visits that week
The total number of consultations for the week
The overall fee total
Figure 9. Description of the Print Manager Report use case for ChocAn.
The initial business model includes all the use cases of Figure 1, together with their descriptions.
The initial requirements include all the use cases of Figure 1, together with their descriptions.
10
2) Analysis Workflow of the Chocoholics Anonymous Project
In this solution, subheadings are underlined.
Scenarios for the use cases of Figure 1 appear in Figures 10 through 19.
A provider wishes to add a new member.
1.
The provider enters new member information:

Member name
Member address
Member city
Member state
Member ZIP code
Date last paid
Member status (Active, Inactive, Suspended)
2.
The system displays a message that the member has been successfully added.
Figure 10. First scenario of the Maintain Member use case of the ChocAn information system.
A provider wishes to modify current member information.

1.
The provider locates the current member record by searching by member name or member
number.
2.
The provider edits the member information:

Member name
Member address
Member city
Member state
Member ZIP code
Date last paid
3.
The system displays a message that the member information has been successfully modified.
Figure 11. Second scenario of the Maintain Member use case of the ChocAn information system.
11
INF207-E/205
A provider wishes to add a new provider.

1.
The provider enters new provider information:

Provider name
Provider address
Provider city
Provider state
Provider ZIP code
Date last paid
Provider type (Dietitian, Internist, Exercise Specialist)
Provider status (Active, Inactive, Suspended)
2.
The system displays a message that the provider has been successfully added.
Figure 12 First scenario of the Maintain Provider use case of the ChocAn information system.
A provider wishes to modify current provider information.

1.
The provider locates the current provider record by searching by provider name or provider
number.
2.
The provider edits the provider information:

Member name
Member address
Member city
Member state
Member ZIP code
Date last paid
3.
The system displays a message that the provider information has been successfully modified.
Figure 13. Second scenario of the Maintain Provider use case of the ChocAn information system.
1.
A provider enters a member number to verify member status
2.
The system determines whether the member is active, inactive, suspended, or not found.
Figure 14 Scenario of the Verify Member Status use case of the ChocAn information system.
12
A member visits a provider.
1.
The provider enters the member number to verify member status.
2.
The system determines that the member is active.
3.
The provider enters his or her provider number.
4.
The system determines that the provider is active.
5.
The provider enters the date of the visit.
6.
The name and number of all services available from that provider are displayed on the screen
by the system.
7.
The provider enters the service number for that visit.
8.
The system displays the corresponding service.
9.
The provider verifies that the service selected is correct.
10. The provider enters optional comments.

11.
The system stores the visit information:

Current date and time
Date of visit
Service code
Fee charged for service
12. The system displays a message that the visit has been successfully added.
Figure 15. Scenario for the Add Visit use case of the ChocAn information system.
13
INF207-E/205
A ChocAn manager wishes to print a member report.

1
The ChocAn information system prints a report of all visits by each member during the
current week, including:

Member name, number, address, city, state, ZIP code.
Date of service
Provider name
Service name
Figure 16. Scenario for the Print Member Report use case of the ChocAn information system.
A ChocAn manager wishes to print a provider report.

1

Provider name, number, address, city, state, ZIP code.
Date of service
Date and time data received from computer
Service code
Fee to be paid
Total number of consultations with members
Total fee for the week
Figure 17. Scenario for the Print Provider Report use case of the ChocAn information system.
A ChocAn manager wishes the EFT report to be printed.
1
The ChocAn information system prints the EFT report including:

Provider name and number
Amount to be transferred to providers account
Figure 18. Scenario for the Print EFT Report use case of the ChocAn information system.
14
A ChocAn manager wishes to print a manager report.
1

The name of every provider to be paid for the current week
The number of consultations each provider had
His or her total fee for the week
The total number of providers who had visits that week
The total number of consultations for the week
The overall fee total
Figure 19. Scenario for the Print Manager Report use case of the ChocAn information system.
Candidate entity classes are determined using noun extraction.
Description of information system in a single paragraph:
For a monthly fee, members of ChocAn are entitled to unlimited visits to providers. The services
of the providers include those of internists, dietitians, and exercise experts. Reports are
printed each week regarding members, providers, and the overall fees payable to providers.
Identify the nouns: For a monthly fee, members of ChocAn are entitled to unlimited visits to providers.
The services of the providers include those of internists, dietitians, and exercise experts. Reports are
printed each week regarding members, providers, and the overall fees payable to providers.
With regard to the nouns in the previous paragraph, internist, dietitian, and exercise expert could be
treated two ways. First, they could be considered subclasses of Provider Class. Second, they could be
considered attributes of Provider Class. For simplicity, we adopt the second choice, noting that it is
easier to add subclasses than to remove them. Also, fee, ChocAn, report, and week are abstract nouns.
This leaves Member Information Class, Visit Information Class, Provider Information Class, and
Service Information Class as the candidate entity classes.
Now comparing scenarios 10 and 11 with scenarios 12 and 13, it is clear that we need to declare a class
Person Information Class as a superclass of Member Information Class and Provider Information Class.
[A hint in this regard is given to the student in Appendix ABoth providers and members have name,
number, address, city, state, and ZIP code attributes].
INF207-E/205
15
The initial class diagram is shown in Figure 20.
ChocAn
Application Class
Person
Information Class
Service
Information Class
Visit
Information Class
Member
Information Class
Figure 20. The initial class diagram for the ChocAn information system.
The initial boundary classes are:

ChocAn Interface Class
Get Input Class
Member Report Class
Provider Report Class
EFT Report Class
Manager Report Class
The initial control classes are:
Maintain Member Class
Maintain Provider Class
Request Service Class
Provider
Information Class
16
Add Visit Class
Create Reports Class
The initial statechart is shown in Figure 21.
quit
selected
ChocAn Information System Loop
maintain member
selected
maintain provider
selected
member status
selected
add visit
selected
print reports
selected
Maintaining
Member
Maintaining
Provider
Modify or add
provider information
Verifying
Member Status
Verify status of
member
Adding
Visit
Printing
Reports
Mdify or add member

information
Add visit
information for
member
Figure 21. The initial statechart of the ChocAn information system.
Print member,
provider (EFT), or
manager report
INF207-E/205
17
The member provides

data for the provider
to enter
Get
Input
Class
Member
ChocAn
Interface
Class
Provider
Figure 22.
Maintain
Member
Class
Member
Info
Class
Class diagram showing the classes that realize the Maintain Member and Verify
Member Status use cases of the ChocAn information system.
The member provides

to enter
: Get
Input
Class
3: Supply new
member data
4: Return new
member data
Member
1: Select Add
Member option
Provider
Figure 23.
8: Display acknowledgment
: ChocAn
Interface
Class
2: Transfer
selection
5: Add new
member
7: Send acknowledgment
: Maintain
Member
Class
: Member
Info
Class
A collaboration diagram of the realization of the scenario of Figure 10 of the

Maintain Member use case of the ChocAn information system.
Use case Maintain Member:
18
The class diagram is shown in Figure 22.
Consider the scenario of Figure 10, the first scenario of the Maintain Member use case. The collaboration
diagram is shown in Figure 23, the flow of events in Figure 24, and the corresponding sequence diagram in
Figure 25.
The provider enters data provided by the new member (13). The ChocAn information system
is updated accordingly (45). An acknowledgment is displayed (68).
Figure 24. The flow of events of the realization of the scenario of Figure 23 of the Maintain Member use
case of the ChocAn information system.
Member
Provider
: ChocAn Interface
Class
: Maintain Member
Class
: Get Input
Class
: Member Info
Class
1: Select Add
Member option
2: Transfer selection
3: Supply new
member data
4: Return new
member data
Data provided
by the member
for the provider
to enter
5: Add new member

8: Display
acknowledgment
Figure 25.
A sequence diagram equivalent to the collaboration diagram of

Figure 23. The flow of events is therefore as shown in Figure 24.
INF207-E/205
19
The member provides

to enter
: Get
Input
Class
3: Supply modified
member data
4: Return modified
member data
Member
1: Select Modify
Member option
Provider
Figure 26.
2: Transfer
selection
: ChocAn
Interface
Class
5: Modify
member data
: Maintain
Member
Class
: Member
Info
Class
A collaboration diagram of the realization of the scenario of Figure

11 of the Maintain Member use case of the ChocAn information
system.
The provider enters modified data provided by the member (13). The ChocAn information
system is updated accordingly (45). An acknowledgment is displayed (68).
Figure 27.
The flow of events of the realization of the scenario of Figure 23 of the

Now consider the scenario of Figure 11, the second scenario of the Maintain Member use case. The
collaboration diagram is shown in Figure 26, the flow of events in Figure 27, and the corresponding
sequence diagram in Figure 28.
20
Member
Provider
: ChocAn Interface
Class
: Maintain Member
Class
: Get Input
Class
: Member Info
Class
1: Select Modify
Member option
3: Supply modified
member data
4: Return modified
member data
Data provided
by the member
for the provider
to enter
5: Modify member data

Figure 28.

Get
Input
Class
Provider
Figure 29.
ChocAn
Interface
Class
Maintain
Provider
Class
Class diagram showing the classes that realize the Maintain Provider
use case of the ChocAn information system.
Provider
Info
Class
INF207-E/205
21
: Get
Input
Class
3: Supply new
provider data
1: Select Add
Provider option
Provider
Figure 30.
: ChocAn
Interface
Class
4: Return new
provider data
2: Transfer
selection
5: Add new
provider
: Maintain
Provider
Class
: Provider
Info
Class

12 of the Maintain Provider use case of the ChocAn information
system.
Use case Maintain Provider:

Consider the scenario of Figure 12, the first scenario of the Maintain Provider use case. The collaboration
diagram is shown in Figure 30, the flow of events in Figure 31, and the corresponding sequence diagram in
Figure 32.
The new provider enters data (13). The ChocAn information system is updated accordingly (45).
An acknowledgment is displayed (68).
Figure 31.
The flow of events of the realization of the scenario of Figure 7.75 of the
Maintain Provider use case of the ChocAn information system.
22
Provider
: ChocAn Interface
Class
: Maintain Provider
Class
: Get Input
Class
: Provider Info
Class
1: Select Add
Provider option
3: Supply new
provider data
4: Return new
provider data
5: Add new provider
Figure 32.
A sequence diagram equivalent to the collaboration diagram of Figure 30. The

flow of events is therefore as shown in Figure 31.
: Get
Input
Class
3: Supply modified
provider data
1: Select Modify
Provider option
Provider
Figure 33.
4: Return modified
provider data
2: Transfer
selection
: ChocAn
Interface
Class
5: Modify
provider data
: Maintain
Provider
Class
: Provider
Info
Class

INF207-E/205
23
The provider enters modified data (13). The ChocAn information system is updated accordingly
(45). An acknowledgment is displayed (68).
Figure 34.

Maintain Provider use case of the ChocAn information system.
Now consider the scenario of Figure 13, the second scenario of the Maintain Provider use case. The
collaboration diagram is shown in Figure 33, the flow of events in Figure 34, and the corresponding
sequence diagram in Figure 35.
Provider
: ChocAn Interface
Class
: Maintain Provider
Class
: Get Input
Class
: Provider Info
Class
1: Select Modify
Provider option
3: Supply modified
provider data
4: Return modified
provider data
5: Modify provider data
Figure 35.

24
The member provides

to enter
: Get
Input
Class
3: Request member
number
Member
Provider
Figure 36.
1: Select Verify
Member Status
option
8: Display member
status
: ChocAn
Interface
Class
4: Return member
number
2: Transfer
selection
5: Request
member status
7: Return member
status
: Maintain
Member
Class
6: Return member
status
: Member
Info
Class

12 of the Verify Member Status use case of the ChocAn information
system.
The provider enters the member number, supplied by the member (14). The ChocAn information
system returns the member status (57), which is then displayed (8).
Figure 37.
The flow of events of the realization of the scenario of Figure 14 of the Verify
Member Status use case of the ChocAn information system.
INF207-E/205
25
Use case Verify Member Status:
Consider the scenario of Figure 14 of the Verify Member Status use case. The collaboration diagram is
shown in Figure 36, the flow of events in Figure 37, and the corresponding sequence diagram in Figure 38.
Member
Provider
: ChocAn Interface
Class
: Maintain Member
Class
: Get Input
Class
: Member Info
Class
1: Select Verify Member

Status option
3: Request member
number
4: Return member
number
Data provided
by the member
for the provider
to enter
5: Request member status

6: Return member status
7: Return member status
8: Display member
status
Figure 38.
A sequence diagram equivalent to the collaboration diagram of Figure

36. The flow of events is therefore as shown in Figure 37.
26
The member provides
to enter
Get
Input
Class
Member
Provider
Figure 39.
ChocAn
Interface
Class
Add
Visit
Class
: Maintain
Member
Class
Maintain
Provider
Class
Request
Service
Class
Member
Info
Class
Provider
Info
Class
Service
Info
Class
Class diagram showing the classes that realize the Add Visit use case
of the ChocAn information system.
Visit
Info
Class
INF207-E/205
27
Use case Add Visit:
The member provides

to enter
3: Request member
number
19: Request comments
and date of visit
Member
1: Select Add
Visit option
Provider
4: Return member
number
20: Return comments and
date of visit
2: Transfer
selection
24: Display visit

information
: ChocAn
Interface
Class
8: Transfer
member
information
: Maintain
Member
Class
6: Request
member
information
7: Return
member
information
: Member
Info
Class
21: Record visit

information
23: Transfer visit

information
5: Transfer member
number
Figure 40.
: Get
Input
Class
22: Transfer visit

information
: Add
Visit
Class
9: Transfer
provider
number
: Visit
Info
Class
18: Transfer service

information
12: Transfer
provider
information 13: Request
service
data
: Maintain
Provider
Class
10: Request
11: Return
provider
provider
information
information
: Provider
Info
Class
: Request
Service
Class
14: Request
sevice code
16: Approve
service
name
15: Return
service
name
17: Return
service
information
: Service
Info
Class

Add Visit use case of the ChocAn information system.
28
The provider enters the member provided by the member (14). The ChocAn information system
determines the member's status and other member information (58). Now the provider number
is used to obtain provider information (912). Next, the service code is entered (1314) and the
service name returned, displayed for the provider's approval (15-16), and used to return service
information (1718). The provider provides comments and the date of visit (1920). Visit
information is then recorded and displayed (2124).
Figure 41.
(The box above is the figure - as done by the process in the textbook (see
p.117).) The flow of events of the realization of the scenario of Figure 15 of
the Add Visit use case of the ChocAn information system.
Consider the scenario of Figure 15, a scenario of the Add Visit use case. The collaboration diagram is
INF207-E/205
29
Member
: ChocAn Interface
Class
1: Select Add
Visit option
Provider
: Add Visit
Class
: Get Input
Class
: Maintain Member
Class
: Member Info
Class
3: Request member
number
4: Return member
number
Data provided
by the member
for the provider
to enter
5: Transfer member number

6: Request member
information
7: Return member
information
8: Transfer member information
9: Transfer provider number
13: Request service data
19: Request comment

and date of visit
20: Return comments
and date of visit
21: Record visit information
23: Transfer visit

information
23: Display visit
information
Figure 42.

flow of events is therefore as shown in Figure 41 (Part 1 of 2).
30
: Maintain Provider
Class
: Provider Info
Class
: Request Service
Class
: Service Info
Class
: Visit Info
Class
10: Request provider

information
11: Return provider
information
12: Transfer provider
information
14: Request service

code
15: Return service
name
16: Approve service
name
17: Return service
information
18: Transfer service information
22: Transfer visit information
Figure 42.

flow of events is therefore as shown in Figure 41 (Part 2 of 2).
INF207-E/205
31
Member
Info
Class
ChocAn
Interface
Class
Figure 43.
Create
Report
Class
Member
Report
Class
Class diagram showing the classes that realize the Print Member Report use
: Member
Info
Class
3: Request member
information
1: Select Print
Reports option
Provider
Figure 44.
4: Return member
information
2: Select Print
Member Report
: ChocAn
Interface
Class
5: Print member
report
: Create
Report
Class
: Member
Report
Class

Print Member Report use case of the ChocAn information system.
32
Use case Print Member Report:
Consider the scenario of Figure 16 of the Print Member Report use case. The collaboration diagram is
The provider requests that a report be printed (1) and that it be the member report (2).
Information regarding the member is obtained (34), the report printed (5), and an
acknowledgment is displayed (68).
Figure 45.
The flow of events of the realization of the scenario of Figure 44 of the Print
Member Report use case of the ChocAn information system.
: Create
: ChocAn Interface
Class
Report Class
1: Select Print
Reports option
2: Select Print
Member Report
Provider
: Member Info
Class
: Member Report
Class
3: Request member
information
4: Return member
information
5: Print member report
Figure 46.

INF207-E/205
33
: Provider
Information
Class
Provider
: ChocAn
Interface
Class
: Create
Report
Class
: Provider
Report
Class
: Service
Information
Class
Figure 47.
Class diagram showing the classes that realize the Print Provider Report use
Use case Print Provider Report:

Consider the scenario of Figure 17 of the Print Provider Report use case. The collaboration diagram is
34
: Provider
Information
Class
3: Request
provider
information
1: Select Print
Reports option
Provider
4: Return
provider
information
2: Select Provider
Report
: ChocAn
Interface
Class
7: Print provider
report
: Create
Report
Class
6: Return
service
information
: Provider
Report
Class
5: Request
service
information
: Service
Information
Class
Figure 48.

Print Provider Report use case of the ChocAn information system.
The provider requests that a report be printed (1) and that it be the provider report (2).
Information regarding each provider (34) and the services provided by that provider (56) is
obtained and incorporated in the provider report. The provider report is printed (7), and an
Figure 49.
The flow of events of the realizations of the scenario of Figure 48 of the Print
Provider Report use case of the ChocAn information system.
INF207-E/205
35
: ChocAn Interface
: Create Report
Class
Class
1: Select Print
Reports option
2: Select Print
Provider
Report
Provider
: Provider Info
Class
: Service Info
Class
: Provider Report
Class
3: Request provider
information
4: Return provider
information
5: Request service information
6: Return service information
7: Print provider report
10: Display
acknowledgment
Figure 50.
9: Send
acknowledgment
8;: Send acknowledgment

Use case Print EFT Report:

Consider the scenario of Figure 18 of the Print EFT Report. The collaboration diagram is shown in Figure
52, the flow of events in Figure 53, and the corresponding sequence diagram in Figure 54.
36
: Provider
Information
Class
Provider
: ChocAn
Interface
Class
: Create
Report
Class
: EFT
Report
Class
: Service
Information
Class
Figure 51.
Class diagram showing the classes that realize the Print EFT Report use case
of the ChocAn information system.
INF207-E/205
37
: Provider
Information
Class
4: Return
provider
information
3: Request
provider
information
1: Select Print
Reports option
Provider
2: Select EFT
Report
: ChocAn
Interface
Class
7: Print EFT
report
: Create
Report
Class
6: Return
service
information
: EFT
Report
Class
5: Request
service
information
: Service
Information
Class
Figure 52.

Print EFT Report use cases of the ChocAn information system.
The provider requests that a report be printed (1) and that it be the EFT report (2).
Information regarding each provider (34) and the services provided by that provider (56) is
obtained and incorporated in the EFT report.
The EFT report is printed (7), and an

Figure 53.
The flow of events of the realizations of the scenario of Figure 52 of the Print
EFT Report use cases of the ChocAn information system.
38
: ChocAn Interface
: Create Report
Class
Class
1: Select Print
Reports option
2: Select Print
Provider
report
Provider
: Provider Info
Class
: Service Info
Class
: EFT Report
Class
3: Request provider
information
4: Return provider
information
7: Print provider report
10: Display
acknowledgment
Figure 54.
9: Send
acknowledgment

INF207-E/205
39
: Provider
Information
Class
Provider
: ChocAn
Interface
Class
: Create
Report
Class
: Manager
Report
Class
: Service
Information
Class
Figure 55.
Class diagram showing the classes that realize the Print Manager Report use
Use case Print Manager Report:

Consider the scenario of Figure 19 of the Print Manager Report use case. The collaboration diagram is
40
: Provider
Information
Class
3: Request
provider
information
1: Select Print
Reports option
Provider
4: Return
provider
information
2: Select Print
Manager Report
: ChocAn
Interface
Class
7: Print manager
report
: Create
Report
Class
6: Return
service
information
: Manager
Report
Class
5: Request
service
information
: Service
Information
Class
Figure 56.

19 of the Print Manager Report use case of the ChocAn information
system.
The provider requests that a report be printed (1) and that it be the print manager report (2).
Information regarding each provider (34) and the services provided by that provider (56) are
obtained and incorporated in the print manager report.
The report is printed, and an

Figure 57.

Print Manager Report use case of the ChocAn information system.
INF207-E/205
41
: ChocAn Interface
: Create Report
Class
Class
1: Select Print
Reports option
2: Select Print
Manager
Report
Provider
: Provider Info
Class
: Service Info
Class
: Manager Report
Class
3: Request provider
information
4: Return provider
information
7: Print manager report
10: Display
acknowledgment
Figure 58.
9: Send
acknowledgment

UNISA 2006

Aseproj

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Aseproj

Hochgeladen von

Copyright:

Verfügbare Formate

INF207-E/205/2006

TUTORIAL LETTER 205 FOR INF207-E

Tutorial matter that you should have received to date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

NOTA AAN AFRIKAANSSPREKENDE STUDENTE

Tutorial matter that you should have received to date

General information, study programme, exam admission & assignments

Discussion of Assignment 5 (This tutorial letter)

I have lost / did not receive certain study material!

How do I download study material or access the discussion forum?

Turn to Appendix A in the prescribed book, the Chocoholics Anonymous project.

2) Perform the analysis workflow of the Chocoholics Anonymous project.

Money ChocAn is obligated to pay to providers for services they

A food prepared from ground roasted cacao beans that is truly

An organization dedicated to helping people addicted to

An automated process by which funds are transferred from one

A number that identifies a member who is inactive or a number

A 9-digit number that uniquely identifies each member of

Active, Inactive, Suspended.

A data storage medium where the EFT data are kept.

An individual who provides services to paying members of

A directory that holds the service codes, descriptions of the

A 9-digit number that uniquely identifies each ChocAn provider.

Internist, Dietitian, Exercise Specialist.

A 6-digit number that uniquely identifies a service provided to a

(For example, 598470 denotes a session with a

The process of checking that the members number is correct

An occasion on which a consultation, exercise session, or other

Initial ChocAn glossary

Figure 1. Use-case diagram for ChocAn.

The provider enters or updates data given by the member:

Figure 2. Description of the Maintain Member use case for ChocAn.

The provider enters or updates provider information including:

Figure 3. Description of the Maintain Provider use case for ChocAn.

The provider enters the member number that is to be validated.

The provider enters the member number.

provider enters his or her provider number.

Then information is written by the ChocAn information system to a file, including:

Figure 5. Description of the Add Visit use case for ChocAn.

current week, including:

The ChocAn information system prints the EFT report including:

The ChocAn information system prints a report including:

The provider enters new member information:

A provider wishes to modify current member information.

The provider edits the member information:

A provider wishes to add a new provider.

The provider enters new provider information:

A provider wishes to modify current provider information.

The provider edits the provider information:

A provider enters a member number to verify member status

The provider enters the member number to verify member status.

The system determines that the member is active.

The provider enters his or her provider number.

The system determines that the provider is active.

The provider enters the date of the visit.

The provider enters the service number for that visit.

The system displays the corresponding service.

The provider verifies that the service selected is correct.

10. The provider enters optional comments.

The system stores the visit information:

A ChocAn manager wishes to print a member report.

current week, including:

A ChocAn manager wishes to print a provider report.

the current week, including: