Programming Methods Assignment

Only available on StudyMode
  • Topic: Flowchart, Unified Modeling Language, UML diagrams
  • Pages : 7 (1203 words )
  • Download(s) : 177
  • Published : January 29, 2013
Open Document
Text Preview
Table of Contents
Task 13
Report 14
Logical Data Structure4
Preliminary Program Structure5
Program Specification6
Report 29
Logical Data Structure9
Preliminary Program Structure10
Program Specification10
Task 214
Pseudo code for Report 115
Pseudo code for report 216
Flowcharts for Report 118
Flowchart for Report 219
Task 321
Pseudo codes for a procedure that checks whether a member is paid-up member.22 Pseudo code for main menu23
Flowchart for Main menu24
Test Plan25
Desk checking25
Dry Run26
Task 428
Unified Modeling Language29
High level class diagram30
Top level use case diagram31
Activity diagram32
State diagram33
Task 534
Review of the assignment34

Task 1
The club secretary would like the following reports on a regular basis: Report 1A list of all the paid-up member names and contact telephone numbers Report 2A list of the renewals due within the next month, with total payment due if all members renew their membership Using JSP techniques and methodology analyse the requirements for both reports. Produce diagrams for both reports showing the step-wise progression. Diagrams should include. •Logical data structure diagrams(DSDs)

Preliminary program structures(PSDs)
The detailed program specification for each report.

Report 1
Logical Data Structure

Figure 1.1.1 Logical Data Structure Diagram

The logical data structure diagram reflects that no processing is required for the non-renewed members. So the diagram reflects only the records for the paid-up members. The paid-up members are more specified by their details, member number, name, and contact number.

Preliminary Program Structure

Figure 1.1.2 Preliminary program structure
The preliminary program structure represents the data components, which are structured for more detailed analysis. This structure will then form the basis of the program construction. Each data component is related to only one program component, which further relates to one input and/or one output component.  

Program Specification
At the top level, the program is separated into the components’ initialisation tasks, processing tasks and closing tasks:
Figure 1.1.3 Top level of top-down development – stepwise refinement Step 1
At the top level the outline requirements for each main component are: •Initializing: open files
Processing: process each record to find payment status
Closing: close all files.

Figure 1.1.4 Step 1 of top-down development – stepwise refinement

Step 2
Taking each component in turn, they can be further divided to give each of the following refinements: •Initializing refinement: open files for reading and writing. •Processing refinement: set up loop to read in and process each record. •Closing refinement: close files, output closing message.

Figure 1.1.5 Step 2 of top-down development – stepwise refinement Step 3
No further refinements are needed for the initialization or termination routines. However a further analysis of the processing tasks is needed. Processing the records - processes are needed to:
establish paid-up members details
write results to file
count the number of records

Figure 1.1.5 Step 3 of top-down development – stepwise refinement Step 4
A small refinement is required to establish paid-up member details. Establish paid-up member details:
Compare date of due paid with today date (today date refers to the date, the Club Secretary checks the membership list). •Write results to paid-up_Member variable
Write results to file:
Write paid-up member number + member name + contact phone number to record fields in new file Accumulate number of paid members:
Add 1 to number_of_records variable

Figure 1.1.6Step 4 of top-down development – stepwise refinement Report 2
Logical Data Structure

Figure 1.2.1 Logical Data Structure Diagram

tracking img