You are here: UK Essays » Essays » Information Technology » Diagram Data Structure

Cookie Information

Privacy Information

Diagram Data Structure

Problem statement: The club secretary would like to see the list of paid -up members name and their contact number by their membership level with total on a regular basis-

Data structure diagram Data structure diagram used to analyses how data will organize .The technique can be applied to the of both problem and data. First it used to structure data later used to in the section of problem. DSD shows the a graphical arrangement of data.

Report-1

Data Structure Diagram

Soccer Club

Members *

Member level

Adult º

Junior º

Age>18

Age<18

Due º

Paid Upº

Member Name

Member ID

Address

Contact number

Jackson Structure Diagram

Soccer Club

Member *

Name

Member level

Contact Address

Contact no.

Junior º

Age<18

Adult º

Age>18

Membership status

Others º

Paid up º

Member ID

Report-1

Program Structure Diagram: This diagram used to design a program from a program specification. The program structure is established by determining the input and output data structure and combining them to produce the program structure.

Soccer Club

Member

Paid up

Step-1 Program specification (Report-1)

• Initializing: Open file.

• Process : Process each .

• Closing: Close file

Member

Processing

Initializing

Closing

Step-2 Program specification (Report-1)

Program

Process Each record

Closing

Processing

Initializing

Open Member File

Closing Member File

Until EOF

• Initializing: Open file for reading and writing

• Process: Set up loop read in and process each record .

• Closing: Close file and output closing file.

Step-3 Preliminary Structure Diagram

Program

Process each member Record

Closing

Processing

Initializing

Open Member File

Until EOF

Open Input File

Open Output File

Open Junior File

Open Adult File

Junior º

Age<18

Adult º

Age>18

Paid up º

Due º

Count=count+1

Name

Contact no.

Address

Step-4 Preliminary Structure Diagram-(Report-1)

Program

Process each member Record

Closing

Processing

Initializing

Open Member File

Until EOF

Open Input File

Open Output File

Open Junior File

Open Adult File

Junior º

Age<18

Adult º

Age>18

Due º

Count=count+1

Name

Contact no.

Address

Paid up

Count=count+1

Name

Contact no.

Address

• Search adult and junior members.

• Check for paid up and Due member .

• Count the number of record

Report-2

Jackson Structure Diagram

Soccer Club

Session

Match *

Team *

Player *

Booking of

No. of Match

Goal no *

Sending of

Played match *

Name

Player ID

Address

Contact no.

Report-2

Data Structure Diagram

Soccer Club

Session

Match *

Team *

Player *

1^st Teamº

2^ndTeamº

Juniorº

No. of Match*

No. of Goal º

Booking of º

Send of º

Played Team

Name

Player Id.

Age

Address

(Report -2 )Program Structure Diagram: This diagram used to design a program from a program specification. The program structure is established by determining the input and output data structure and combining them to produce the program structure.

Program specification

Program

Initialization

Processing

Closing

Step-2 (Preliminary Structure Diagram)

Program

Initialization

Processing

Closing

Open Match File

Process Team Record of the season *

Closing Match File

Until EOF

Output Closing Message

Step-3 (Preliminary Structure Diagram)

Program

Initialization

Processing

Closing

Open Match File

Process Team Record of the season *

Closing Match File

Until EOF

Output Closing Message

Open Output File

Open Input

File

Player *

Number of Match

No. of goal

Booking

Sending off

Team no.

Task-2

Problem statement: Draw a flowchart for two report first one show that a list of paid up members, name, address, phone number with details, which is monthly or yearly,

And another is only monthly with member name, address telephone number, email.

Flow Chart

Flow charts are easy-to-understand diagrams showing how steps in a process fit together. This makes them useful tools for communicating how processes work, and for clearly documenting how a particular job is done. Furthermore, the act of mapping a process out in flow chart format helps you clarify your understanding of the process, and helps you think about where the process can be improved.

A flow chart can therefore be used to:

Ø Define and analyze processes;

Ø Build a step-by-step picture of the process for analysis, discussion, or communication; and

Ø Define, standardize or find areas for improvement in a process

Start

Open member File

Read member _info

Member type=paid up ?

junior[junior_count]= member _info

adult[adult_count]= member _info

Junior_count=junior+1

adult_count=adoult+1

i=0

Display “junior member _info”

member age<18 ?

Until EOF

Yes

No

i++

i< Junior_count

End

i=0

Display “adult member _info”

i++

i< adult_count

Yes

No

No

Yes

Flow chare

Report-1

Start

Open member File

Yes

No

Yes

No

Open member File

Read player_info

player_info=

current session ?

Until EOF

End

Flow chare

Report-2

Start

Open Player File

Played team

team=1^st team || team=2^nd || team=junior ?

Player=goal _score|| bookings || sendings_of ?

Display “Goals scored” goal_score.

Display “Booking” booking

Display “Sendings” sendings_of

goal_score= goal_score +1.

booking =booking=+1

sendings_of= sendings_of+1

Played=team

Yes

No

No

No

Yes

Yes

No

Yes

Display player_info in alphabetical order

TASK -3

Task 3(a)

Pseudocode For REPORT 1

RECORD Members HAS FIELD

MemberName: String

MemberIdr: Integer

MemberAddress: String

ContacteNumber: Integer

EmailAddress: String

Member_Type: String //Paid-up or Due

END RECORD

Use Variables: Members_Informations OF TYPE Member

PROCEDURE InputMembers_Informations()

DISPLAY “Enter Member's name: ”

Accept Members_Informations.MemberName

DISPLAY “Enter Member's Id: ”

Accept Members_Informations.MemberId

DISPLAY “Enter Member's Address: ”

Accept Members_Informations.MemberAddress

DISPLAY “Enter Member's Contact Telephone Number: ”

Accept Members_Informations.ContactNumber

DISPLAY “Enter Membership_ Type: ”

Accept Membership_ Type

END PROCEDURE

IF Membership_ Type=Paid up THEN

Display “Display Information” InputMembers_Informations()

END IF

PROCEDURE main()

InputMembers()

END PROCEDURE

Task 3(a)

Procedure Boolean Paid-Up(Member_Id OF TYPE Integer)

Use variable:Paid_Up OF TYPE Boolean

Junior of type string

adult of type string

toltal paid_up OF Type string

adult members_Informations[] of OF TYPE Member

junior members_Informations[] of OF TYPE Member

paid_up members_Informations[] of OF TYPE Member

OPEN Members.doc

WHILE (! EOF)

Members_Informations:=READ RECORD

adult =0

Junior=0

toltal paid_up=0

IF membersInformations.Member_Id=member_Id THEN

IF( members_Informations.Member_Type=adult)THEN

IF

isPaidUp=TRUE

ELSE

isPaidUp=FALSE

END IF

adult members_Informations[]=members_Informations

paid_up members_Informations[]=members_Informations

adoult= adoult+1

ELSE members_Informations.Member_Type=junior THEN

IF isPaidUp=TRUE

ELSE

isPaidUp=FALSE

END IF

junior members_Informations[]=members_Informations

paid_up members_Informations[]=members_Informations

Junior= Junior+1

END IF

END IF

toltal paid_up= toltal paid_up+1

END WHILE

For (1=; toral paid up, i++)

Print ”paid upmember”: paid_up members_Informations[i]

CLOSE Members.dat

End Procedure

Task-3(b)

PROCEDURE members_Information ()

Count OF TYPE Integer

Count:=0

OPEN Members.dat

DISPLAY “THE PAID UP MEMBERSHIPS”

WHILE (! EOF)

READ MembersInformations

IF Members_Informations.Membership_Type= “adult” THEN IF(isPaidUp(MembersInformations.MemberNumber)=TRUE) THEN

Count: =Count+1

DISPLAY MembersInformations.MemberName “\t”

DISPLAY MembersInformations.ContactNumber “\t”

DISPLAY MembersInformations. lAddress “\t”

END IF

END IF

END WHILE

DISPLAY “The Total Number of paid up MEMBERSHIPS are: \n”Count

IF MembersInformations.Membership_Type= “junior” THEN

DISPLAY “THE PAID UP MEMBERSHIPS”

DISPLAY

Count: =0

WHILE (! EOF)

IF(isPaidUp(MembersInformations.MemberNumber)=TRUE) THEN

Count: =Count+1

DISPLAY MembersInformations.MemberName “\t”

DISPLAY MembersInformations.ContactNumber “\t”

DISPLAY MembersInformations. Address “\t”

END IF

END WHILE

END IF

DISPLAY “The Total Number of Paid upMEMBERSHIPS are: \n”Count

CLOSE Members.dat

END PROCEDURE

Pseudocode For REPORT 2

PROCEDURE NOTMonthlyPaidUpMembers_Information ()

Count OF TYPE Integer

Count:=0

OPEN Members.dat

DISPLAY “THE NOT PAID UP MEMBERSHIPS”

WHILE (! EOF)

READ Members_ Informations

IF Members_Informations.Membership_Type= “adult” THEN

IF (isPaidUp(Members_Informations.MemberNumber)=FALSE) THEN

Count: =Count+1

DISPLAY Members_Informations.MemberName “\t”

DISPLAY Members_Informations.ContactNumber “\t” DISPLAY MembersInformations. Address “\t”

END IF

END IF

END WHILE

DISPLAY “The Total Number of NOT PAID UP MEMBERSHIPS are: \n”Count

IF Members_nformations.Membership_Type= “junior” THEN

DISPLAY “THE NOT PAID UP MEMBERSHIPS”

Count: =0

WHILE (! EOF)

IF(isPaidUp(Members_Informations.MemberNumber)=FALSE) THEN

Count: =Count+1

DISPLAY MembersInformations.MemberName “\t”

DISPLAY MembersInformations.ContactTelephoneNumber “\t”

DISPLAY MembersInformations.EmailAddress “\t”

END IF

END WHILE

END IF

DISPLAY “The Total Number of NOT PAID UPMEMBERSHIPS are: \n”Count

CLOSE Members.dat

END PROCEDURE

Task-4

Testing involves the operation of a system under controlled condition and evaluation of the result to make sure the program does what it is support to do. It is not recommended programmers should desk check their own programs, as it is generally accepted that programmers are not very effective in testing their own programmers. It is much more difficult to find errors in one's own code than in someone else's! Fro this reason, desk checking is best performed by a person other than the author of the program.

Dry running a program segment involves the execution of the segment with the programmer acting as a computer. The success of the technique depends upon the ability to simulate a computer ‘s action without making assumption at all.

The testing processes used throughout the software development life cycle can be either:

Static: reading and checking documents on requirements, reading checking code without running software.

Dynamic: running code to check outputs

There also need to consider the verification and validation

Testing Strategy:

Testing should be used to:

• Demonstrate the validity of the software at each stage in the system development lifecycle

• Check the final system meets user needs and requirements, as specified.

• Examine the behavior of software or system by using sample test data.

Testing Plan for Report 1:

Test plan no: 1

Introduction: producer should be check for member validity check.

Test items: To check the integrity of this producer we will carry on black box testing, Desk check and Dry run testing methods.

Features to be tested: To check the integrity of this producer I have to check

• Variable:

some option to be check-

• Variable not declared.

• Wrong data type declaration.

• Spelling mistake.

• Wrong value assigned.

2.Procedure/function-

option to be check-

• spelling mistake/no definition.

• wrong parameter ,type, and sequence.

(In this system no parameter has been used in procedure so there is no chance to mistake) .

3.return type

In this program there is also no need to return any value through procedure so , no chance making mistake with return type .

Approach: To test this procedure we will have to carry on a paper based black box testing, desk check and dry run.

Test Plan for Report 2:

Test plan no. : 2

Introduction: planned to be tested for member validity check.

Test items: To check the integrity of this producer we will carry on black box testing, Desk check and Dry run testing methods. A detail description of Desk Check and Dry Run is given.

Features to be tested: To check the integrity of this producer I have to check

• Variable:

some option to be check-

• Variable not declared.

• Wrong data type declaration.

• Spelling mistake.

• Wrong value assigned.

2.Procedure/function-

option to be check-

• spelling mistake/no definition.

• wrong parameter ,type, and sequence.

(In this system no parameter has been used in procedure so there is no chance to mistake) .

3.return type

In this program there is also no need to return any value through procedure so , no chance making mistake with return type .

Approach: To test this procedure we will have to carry on a paper based desk check and dry run testing.

Black box testing:

Desk Check for Report 1

Desk Check for Report 2

Dry run for Report 1

Dry run for Report 2

Dry run for Report 2

Task-5

High Level Class Diagram (Domain analysis) For Membership:

Junior

Member ID:

Member name:

Member type:

new()

Update()

Delete()

Member

Member -ID

Member -Name

Member Address:

Member contact:

Member level

Member type

new()

Update()

Delete()

Send Shortlist()

Applicant

Applicant-id

Applicant Name:

Applicant Address

Applicant contact

No.

Update ()

Delete()

Shortlist()

Adult

Member ID:

Member name Member type:

new()

Update()

Delete()

Subscription

Member ID:

Member Type:

Last pay Date:

Payment Due:

new()

Update()

Delete()

Information()

Treasurer

Name:

Address:

Phone:

E-mail:

new ()

Update()

Delete()

Create shortlist()

Inform member()

Secretary

Secretary ID:

Secretary Name:

Secretary Address:

Secretary Phone:

Secretary E-mail:

new()

Update()

Delete()

Search list()

Search payment()

Fig: Class Diagram for member ship system

USE CASE

Application

Open Member file

Add new member

Check member detail

Delete member detail

Print Report

Secretary

Member

USE CASE

Fig: Use Case diagram for member ship system

Join the new member to the data base

Application

Open member

information

Retrieve member detail

Save to database

Check Member payment

Status

Check Member level

Member

Treasure

Checking Member Details

Open member

File

Show paid up Member

List

Chick Member

Details

Treasure

Fig: Checking Member Details Use Case

Deleting Member from Database

Open member

File

Get member Id.

Search for member

Details

Delete member detail

Retrieve member detail

Treasure

Fig:-Deleting Member Detail use ease from Database

Printing a Report

Open member

File

Select Member detail

Provide Detail

Move Data to print

Generate Member detail

Treasure

Print Report

Check Member Detail

: Login

: Member

Display

Check member

Retrieve detail

Select (Member)

Input (Id. pass)

Secretary

Fig : Sequence Diagram for checking Member Details

Add member

: Login

: Member

Display

Check member Payment Status

Feedback

Select (Member)

Input (Id. pass)

Validate Member

Save (Member Details)

Feedback

Secretary

Fig : Sequence Diagram for Add new Member

Deleting a member

: Login

: Member

Display

Check member Payment Status

Feedback

Select (Member)

Input (Id. pass)

Validate Member

Delete (Member Details)

Feedback

Fig: sequence Diagram for Delete a Member.

Print Member detail

: Login

: Member

Display

Provide Report

Feedback

Select (Member)

Input (Id. pass)

Validate Member

Print (Member Detail)

Feedback

Fig: Sequence Diagram for Printing a Report

COLLABURATION DIAGRAM

Checking Member Details

: Login

Check Member

Input (ID, Pass)

Retrieve Details

: Member

Fig: Collaboration Diagram for Checking Member Details.

Adding new Member

Retrieve Details

Input (ID, Pass)

: Login

Check Member

Input (ID, Pass)

: Member

: Junior

: Adult

Fig: Collaboration Diagram for Adding Member

Deleting a Member

Input (ID, Pass)

: Login

Delete Member

Feedback

: Member

Fig: Collaboration Diagram for Delete a Member

Printing a Reports

Input (ID, Pass)

: Login

Select Report

Feedback

: Member

Fig: Collaboration Diagram for Printing a Reports.

Task-6

Introduction

In his assignment I describe Some technique to make the system .I Have describe a feasibility plan to evaluate the system. The plan can easily interact with computer collaboration environment. In this assignment I describe six task which are including Report with diagram, flow chart, procedure pseudo code. test pseudo code .UML modeling technique .I reviewing all of my task below:

All Tasks Review

Task 1

This task desire a list of paid up member and none paid up member detail lick name, address, phone number, and member type with total. To complete this task, I used data structure diagram and program structure diagram Jackson structure diagram with program specification. To complete this task my teacher fully help me also take help from some of my class mate.

Task 2

This task containing a flowchart for each of the two reports specified in Task-1. I had to drawn a flowchart for each of the two reports. . Drawn flow chart I help www.mindtools.com this website

Task 3

To complete the system pseudo code will help us because this task help to make plane that who the system will carry out , I produce two pseudo code according to the report described in task-1 with what I have done with my previous task. And lastly create a pseudo code for a reports main menu.

Task 4

This task I have test the pseudo code written in task 3b by producing test plans, desks checks and dry runs. I had this works. To complete this task I take some help from my Teacher.

Task 5

This task initially want to create a high level class diagram for the record system. I have produce a high level class diagram with domain analysis for the system. Secondly carry out a high level use case analysis and produce a set of use case diagrams . I create a high level use case diagram,. Thirdly task want developed a set of use case diagrams for checking applicant details, adding a new employer to the database, deleting an applicant, printing a report. I create a set of use case diagram for this. Finally task want developed a set of Sequence diagrams for each of the scenarios described in 5c, and also a set of Collaboration diagrams. I create this two set of diagrams. For that I take some help from following website

www.agilemodeling.com/artifacts/classDiagram.htm

Bibliography

• www.agilemodeling.com/artifacts/classDiagram.htm

• Structured Programming Methods( Authors: Roy Stepney, Sandra Powell, Geoff Henderson and Ann Jeffery assert, Published: NCC education 2001)

Sign up and be the first to receive our latest offers: