Student Lab Activity A. Lab # CIS CIS170A-A1B. Lab.docx

Student Lab Activity
A. Lab # CIS CIS170A-A1
B. Lab 5s of 7: Modularization
C. Lab Overview – Scenario / Summary:
TCOs:
TCO: 7
Given a set of program specifications for a simple business
problem utilizing a modular design, code and test a program
that meets the specifications and employs best programming
practices.
TCO: 8
Given a set of program specifications for a simple business
problem, code and test a program that implements methods with
parameter lists that are passed as supported by the chosen
programming language
This lab will familiarize the student with the process of
modularizing his or her code.
D. Deliverables:
Step
Deliverable
Points
5
Program Listing, Output, and Project Files

45
The Dropbox deliverables include the following.
1. Include a zipped file with all the files from your Visual Basic
project (see directions in Doc Sharing on how to collect and zip
files.)
2. Create a single MS Word document and include the
following.
· For each lab, copy and paste your code directly into the MS
Word file.
· Include screenshot(s) of your test data with test results. Enter
enough data to demonstrate that all your code has been tested.
· Include another screenshot of the Visual Basic build output
messages. Check your build output to make sure you have a
successful build with (0) errors and (0) warnings. NOTE: The
build output messages appear at the bottom of your window
after you click the Build menu and before you click the Start
Without Debugging option. Your build output messages provide
a list of compiler warnings or errors and let you know whether
your program compiled successfully.
· Include the Word document as part of the zipped project file.
3. Upload each part of the lab into its corresponding weekly
Dropbox.
E. Lab Steps:
Preparation:
If you are using the Citrix remote lab, follow the login
instructions located in the iLab tab in Course Home.
Locate the Visual Studio 2010 Icon on the desktop. Click to
open.
Lab:

Step 1: Create a New Project
Create a new project in VB.NET. Name your project
CIS170A_Lab05.
Practically every real-world professional program in existence
today uses some type of modular design—this is just the way
programs are designed and built. As a result, the primary
objective of this lab is for you to understand how modular
programs are designed and how data are passed between
modules as the program is executing. This may be one of the
most important lessons of this course, so it is critical that you
focus on the modular design of the program; if you have any
questions, post them to the Lab Forum threaded discussion.
In this project, we are going to use the Week 4 Hockey Player
Statistics program that you created last week as a starting point
and make a few minor changes in the program requirements.
What you will do is take the existing project and with only
slight modifications to the form design you will modularize the
design of the code and then add a few new requirements. As you
will see when you complete the modular program design you
will be able to add the new requirements to the design algorithm
much more easily.
One very important point is that the logic used in the modules is
virtually identical to the logic used in the Week 4 assignment,
with the only major difference being that the code has been
moved into sub procedures and functions. However, this comes
at a price because the communication of the modules becomes
more complex; however, the gains in efficiency in creating the
original program and then modifying the program when
requirements change (as they always will) outweigh the
negative effects of communication complexity.
Step 2: Program Description

As a reminder here are the requirements of the Week 4 program.
Create a program that will calculate and display the career
statistics for a hockey player. The program will begin by
allowing the user to enter the following information.
· Name of the hockey player - The name must be a nonempty
string.
· Number of seasons played – The number must be at least one
season and no more than 20 seasons.
Only after a valid season value is provided, processing of goals
and assists can begin. The next step is to allow the user to
provide additional information as follows.
· Number of goals - A valid number of goals is between 0 and
60.
· Number of assists - A valid number of assists is between 0 and
60.
The program will keep a running total of the following
statistics.
· Number of goals
· Number of assists
· Total points
A list of the each season’s data will be display after the season
data are provided. Additionally, once all the season data are
collected, the program shall list the summary information for
the player and all the seasons.
NEW REQUIREMENTS
The following are the new requirements that the customer wants

to make.
1. The customer has decided that he or she wants to change the
upper limits for goals, assists, and seasons. He or she wants the
upper limit of the seasons to be 25, the upper limit for the goals
is 70, and the upper limit for assists will be 75.
2. As with most programs that collect names of individuals, the
full name shall be broken into two parts: the first name and the
last name. Both the first and last name must contain nonempty-
string values.
3. The customer wants to keep track of how old the player was
when he or she started playing hockey, so the program shall
provide a field to collect and validate the age of the player
when he or she was a rookie. The starting age shall be at least
18 years old and no more than 30 years old, and the age shall be
displayed as part of the summary output.
4. The user cannot begin to collect season data until after the
first name, last name, seasons, and age are all provided and
validated.
The updated hierarchy chart, which shows the structure and
flow chart of the program, is given below. Notice that most of
the processing details have been encapsulated into separate
modules. As a result, this makes the high-level processing flow
easier to understand and the lower level details of the
processing are isolated into smaller modules. The modules can
be reused as necessary when new requirements are added.
The hierarchy chart shows the events (which are just
“specialized” modules), which illustrates how the higher level
modules control the execution of the lower level modules. The
hierarchy chart also shows the isolation of modules, which is
another key characteristic of modular designs. Also notice from

the hierarchy chart that there are multiple levels of modules in
each tree branch. For example, the Gets Status Button Event
handler branch has three sub-levels of modules. It is not
uncommon for real world, professional programs to have several
levels of modules in each tree branch.
The flow chart for the overall program and each of the modules
listed in the hierarchy chart are provided below. Before you
begin constructing your program, ensure that you review these
diagrams carefully and pay attention to the comments in the
call-out boxes. Also, it is highly recommended that you refer to
these diagrams often while you are building your program.

Step 3: Build the Form
The following is the Object, Property, Setting, Event chart for
the form controls, and each input field will have a label/input
field pair. Also, group the related information in the associated
group box.
The form and form controls will be logically placed on the
form, the controls aligned and sized, and a logical tab order
assigned to each of the form controls.
Object
Property
Setting
frmHockeyStats
Text
Hockey Player Statistics
lblHeading
Text
Name, Course Title, Week Number, Lab Title
grpPlayer
Text
Player Information
lblFirstName
Text
First Name:
txtFirstName
Text
(empty)
lblLastName
Text
Last Name:
txtFirstName
Text

(empty)
lblSeasons
Text
Number of Seasons:
txtSeasons
Text
(empty)
lblAge
Text
Rookie Age
txtAge
Text
(empty)
grpStatistics
Text
Statistic Operations
btnGetStats
Text
Get Player Statistics
grpResults
Text
Season Results
lstSeasons
Items
(empty)
lblTotal
Text
(empty)
grpOperations
Text
Operations
btnClear
Text
Clear
btnExit
Text

Exit
You are free to experiment with colors and form design as you
see fit. However, your application must meet the listed
requirements.
Hint: Use constants for the lower and upper limits for the goals
and assists. This will allow you to easily change the range
limits in one place (see below). For example:
Private Const GOAL_LOWER_LIMIT As Integer = 0
Private Const GOAL_UPPER_LIMIT As Integer = 70
Private Const ASSIST_LOWER_LIMIT As Integer = 0
Private Const ASSIST_UPPER_LIMIT As Integer = 75
Private Const SEASONS_LOWER_LIMIT As Integer = 1
Private Const SEASONS_UPPER_LIMIT As Integer = 25
Private Const PLAYER_MIN_AGE As Integer = 18
Private Const PLAYER_MAX_AGE As Integer = 30
Hint: Declare the seasons, age, total goals, total assists, and
total points variables as “form-level” variables at the top of the
form and outside any module body. This will make these
variables form-level variables and they can be accessed by any
of the modules without having to pass them into the module
through the argument list.
Private totalGoals As Integer = 0
Private totalAssists As Integer = 0
Private totalPoints As Integer = 0
Hint: An event handler can handle events from multiple
controls, which allows you to modularize and reuse event
handler code. For example:
Private Sub txtName_Validating(ByVal sender As Object,

ByVal e As System.ComponentModel.CancelEventArgs)
Handles _
txtFirstName.Validating, _
txtLastName.Validating
Dim txtbox As TextBox = CType(sender, TextBox)
e.Cancel = ValidateStringInput("Name", txtbox.Text)
End Sub
Hint: Use the “sender” argument of each event handler to
inspect the control that fired the event, but you need to convert
the “object” to a textbox first, such as:
Dim txtbox As TextBox = CType(sender, TextBox)
e.Cancel = ValidateStringInput(datadescription, txtbox.Text)
Hint: Use the “IS” operator to see which control fires an event;
for example:
If sender Is txtNumSeasons Then
‘process the number of seasons
ElseIf sender Is txtAge Then
‘process the age
End If
Step 4: Implement the Event Handlers
Use the following as the design for your event handlers,
referring to the flow chart for rules on input validation and
processing. The final calculation SHOULD NOT be completed
until all the input fields are validated.
Control Name
Event
Task

txtFirstName
Validating
Get player first name
Validate player name
txtLastName
Validating
Get player first name
Validate player name
txtSeasons
Validating
Get number of seasons
Validate number of seasons
txtAge
Validating
Get age
Validate age
Enable/disable get statistics command button
btnGetStats
Click
For each season
Get goals
Validate goals
Get assists
Validate assists
Calculate total goals
Calculate total assists
Calculate total points
Output season statistics in list
Next
Output season summary
btnClear
Click
Clear all textboxes and output labels
btnExit

Click
Close program (hint: use “Me.close”)
frmHockeyStats
Load
Clear all textboxes and output label (hint: call the ClearFields
module)
Step 5: Executing the Program
To execute your code, click Start and then start debugging.
Check your output to ensure that you have space(s) where
appropriate. If you need to fix anything, close your execution
window, modify your code as necessary, and rebuild.
Step 6: Deliverables
1. Capture a screen print of your output (do a PRINT SCREEN
and paste into an MS Word document).
2. Copy your code and paste it into the same MS Word
document that contains the screen print of your output.
3. Save the Word document as
CIS170A_Lab05_LastName_FirstInitial.
4. Zip up the Word document along with a complete set of
project files into a single document.
5. Place deliverables in the Dropbox.
END OF LAB
Version 1.0 Page 1 of 9
4/9/2009 Lab Activity MDD WBG310-A1

Begin
Get: First Name
Validate String Input(“First Name”, txtFirstName.Text)
Valid first name?
No
Get: Last Name
Validate String Input(“Last Name”, txtLastName.Text)
Valid last name?
Yes
No
Get: Seasons
Validate Number Input(“Seasons”, txtSeasons.Text,
SEASONS_LOWER_LIMIT, SEASONS_UPPER_LIMIT,
seasons)
Valid Seasons?
No
Yes
Get: Age
Validate Number Input(“Age, txtAge.Text,
AGE_LOWER_LIMIT,
AGE_UPPER_LIMIT, age)
Valid age?
Yes
No
Collect Statistics
Display Summary
Data
Yes
end
For the validate input string function, the description of
the type of information that is being validated and the
actual string input needs to be passed into the validate
string input procedure as read only
For the validate number input function, the description of

the type of information that is being validated, the actual
string input, and both the minimum and maximum values
need to be passed into the procedure by value. The actual
data value parameter will need to be passed in by
reference since it will be changed by the procedure.
Collect statistics and display summary data do
not require any arguments and all data can be
declared as local variables
�
�
Select note and type your message!
Begin
Get: First Name
Get: Last Name
Validate String Input(“Last Name”, txtLastName.Text)
Valid last name?
Yes
No
Valid first name?
Get: Seasons
No
Validate Number Input(“Seasons”, txtSeasons.Text,
SEASONS_LOWER_LIMIT, SEASONS_UPPER_LIMIT,
seasons)

Valid Seasons?
No
Yes
Get: Age
Validate Number Input(“Age, txtAge.Text,
AGE_LOWER_LIMIT, AGE_UPPER_LIMIT, age)
Valid age?
Yes
No
Yes
end
Collect Statistics
Display Summary Data
For the validate input string function, the description of the
type of information that is being validated and the actual string
input needs to be passed into the validate string input procedure
as read only
For the validate number input function, the description of the
type of information that is being validated, the actual string
input, and both the minimum and maximum values need to be
passed into the procedure by value. The actual data value

parameter will need to be passed in by reference since it will be
changed by the procedure.
Validate String Input(“First Name”, txtFirstName.Text)
Collect statistics and display summary data do not require any
arguments and all data can be declared as local variables
count <= seasons?
Count = Count + 1
count = 1
No
goals = GetData(“goals”, GOAL_LOWER_LIMIT,
GOAL_UPPER_LIMIT)
The description of the type of information
that is being collected and the upper and
lower limits of the value need to be passed in
for reading into the GetData function, the
function will then return the validated valueassists =
GetData(“assists”,
ASSIST_LOWER_LIMIT, ASSIST_UPPER_LIMIT)
points = AddToTotals(goals, assists)
The seasons goals and assists are passed in
by value to the AddTotals function, which
then returns the points for that season
DisplayRunningTotals(count, goals, assists,
point)
The season count, goals, assists, and points
are passed in by value and the procedure
then sets the values in the output list
Start
The collect statistics procedure prompts the
user for the goals and assists for each season,
calculates the season points, and then
displays the running totals in the list box.
All data variables can be declared locally, and

there is no need to pass in any data to the
Collect Statistics procedure.
end
Yes
Collect Statistics
�
�
count <= seasons?
goals = GetData(“goals”, GOAL_LOWER_LIMIT,
GOAL_UPPER_LIMIT)
The description of the type of information that is being
collected and the upper and lower limits of the value need to be
passed in for reading into the GetData function, the function
will then return the validated value
assists = GetData(“assists”, ASSIST_LOWER_LIMIT,
ASSIST_UPPER_LIMIT)
points = AddToTotals(goals, assists)
Count = Count + 1
Start
count = 1
The collect statistics procedure prompts the user for the goals
and assists for each season, calculates the season points, and
then displays the running totals in the list box.
All data variables can be declared locally, and there is no need
to pass in any data to the Collect Statistics procedure.

No
The seasons goals and assists are passed in by value to the
AddTotals function, which then returns the points for that
season
DisplayRunningTotals(count, goals, assists, point)
The season count, goals, assists, and points are passed in by
value and the procedure then sets the values in the output list
end
Yes
Collect Statistics
Start
By value dataDescription
By value Min value
By value Max value
The Get Data function prompts the user
for the type of data that is being
collected, and then uses the Validate
Number function to validate the
provided value.
The description of the type of
information that is being collected and
the minimum and maximum values need
to be passed into the procedure by
value. The value will then be returned by
the function
Response = InputBox(“Enter the number of “
& dataDescription & “ between “ & min & “
and & “max”
Validate Number

Input(dataDescription, response,
min, max, value)
The Validate Number Input
function is being re-used, and in
this case you pass in the
arguments of the Get Data
function along with locally
declared response and value
variables into the Validate
Number Input function
min <= value <=
max
Return value
Yes
No
End
Get Data
�
�
�
�
�
Start
By value dataDescription
By value Min value
By value Max value
The Get Data function prompts the user for the type of data that
is being collected, and then uses the Validate Number function
to validate the provided value.
The description of the type of information that is being
collected and the minimum and maximum values need to be
passed into the procedure by value. The value will then be

returned by the function
Response = InputBox(“Enter the number of “ & dataDescription
& “ between “ & min & “ and & “max”
Validate Number Input(dataDescription, response, min, max,
value)
The Validate Number Input function is being re-used, and in
this case you pass in the arguments of the Get Data function
along with locally declared response and value variables into
the Validate Number Input function
min <= value <= max
Return value
Yes
No
End
Get Data
Start
By value season
By value goals
By value assists
By value points
The display running totals procedure
adds the season data to the list box.
The season, goals, assists, and points
need to be passed in by value.
The reason you put this into a separate
module is that if you want to change the

output control then you have localized
the changes to this module
Display Running Totals
Output
Season & Goals & Assists &
Points
End
Overview
Japan is the land of peace and harmony that continues to evolve
in a positive unification of tradition and modernisation. With its
elaborate and colourful history and culture, Japan has formed a
distinct model of hierarchy, honour and etiquette that is still
reflected in many social and business practices today.
If your organisation is planning to conduct business with Japan,
potential success depends upon an understanding of this
culturally influenced protocol. Japanese culture - Key concepts
and values
Wa - The most valued principle still alive in Japanese society
today is the concept of 'wa', or 'harmony'. The preservation of
social harmony dates back to the first constitution in 604 AD
and the teamwork needed when living and working on collective
farms. In business terms, 'wa' is reflected in the avoidance of
self-assertion and individualism and the preservation of good
relationships despite differences in opinion. When doing
business with the Japanese it is also important to remember the
affect of 'wa' on many patterns of Japanese behaviour, in
particular their indirect expression of 'no'.
Kao - One of the fundamental factors of the Japanese social
system is the notion of 'face'. Face is a mark of personal pride
and forms the basis of an individual's reputation and social
status. Preservation of face comes through avoiding
confrontations and direct criticism wherever possible . In Japan,
causing someone to loose face can be disastrous for business
relationships.
Omoiyari - Closely linked to the concepts of 'wa' and 'kao',

'omoiyari' relates to the sense of empathy and loyalty
encouraged in Japanese society and practiced in Japanese
business culture. In literal terms it means "to imagine another's
feelings", therefore building a strong relationship based on trust
and mutual feeling is vital for business success in Japan.
The late 19th and early 20th centuries saw Japan swiftly
embrace the numerous influences of western technology.
Following the country's defeat in WWII, Japan experienced a
remarkable growth in its economy and fast became the world's
most successful export. Since then, Japan's business and
economy has witnessed a wavering of strengths, however today,
Japan is one of the world's leading industrial powers with a
new, stable and exciting business market open to foreign
investment and trade.
Japan business Part 1 - Working in Japan (Pre-departure)
· Working practices in Japan
· Due to the strong contemporary business competition in Asia,
the old concept of the 'unhurried' Japanese negotiation process
is no longer applicable. Decisions are made swiftly and
efficiently.
· When arranging a business appointment, making a personal
call will be more effective than sending a letter and seen as
good manners.
· Punctuality is essential in Japan; lateness is as sign of
disrespect. Arriving 5 minutes prior to an appointment is good
practice.
· Structure and hierarchy in Japanese companies.
· The strong hierarchical structure in Japanese business is
reflected in the negotiation process. They begin at the executive
level and continue at the middle level. However, decisions will
often be made within the group.
· Generally speaking, in business meetings the Japanese will
line up in order of seniority, with the most senior person at the
front and the least senior person closest to the door. In addition
to this rule however, you may find that the most senior person
chooses where to sit.

· It is important to bear in mind that in contemporary Japan,
even a low ranking individual can become a manager if his or
her performance is good.
· Working relationships in Japan
· Due to the influence of Confucianism, it is important to show
greater respect to the eldest members in Japanese business
culture. Age and rank are strongly connected, however a change
in today's business climate means that educational background
and ability are often considered over age.
· Personal space is highly valued in Japan due to the densely
populated areas in which they live. Physical contact, other than
a handshake, is never displayed in public. Japan business Part 2
- Doing business in Japan
· Business practices in Japan
· Business in Japan cannot begin until the exchange of business
cards or 'meishi' has been completed. Use both hands to present
your card, which should be printed in both languages. On
receiving your counterpart's business card make a show of
examining it carefully before placing it on the table. It is
important to deal with another's business card with care.
· A significant part of former Japanese business protocol was
gift giving. In contemporary Japanese business culture, although
not expected, the gesture is still practiced and will be accepted
with gratitude. However, be careful not to take too big a gift as
it may be regarded as a bribe.
· It is good business practice to engage in small talk before
negotiations. Expect your Japanese counterpart to ask questions
regarding your education, family and social life. More private
questions are not acceptable.
· In Japanese business protocol contracts are not necessarily
final agreements or a sign that business in over. In Japan,
looking after partners or clients even after business is very
important. Aftercare and long-term relationships are positively
encouraged.
· Japanese business etiquette (Do's and Don'ts)
· DO use apologies where the intention is serious and express

gratitude frequently as it is considered polite in Japan.
· DO avoid confrontation or showing negative emotions during
business negations. Express opinions openly but evade direct or
aggressive refusals.
· DO greet your counterparts with the proper respect and
politeness. If your counterpart bows make sure you return the
gesture, which is usually performed shortly and shallowly. More
often than not, a handshake is sufficient.
· DON'T give excessive praise or encouragement to a single
Japanese colleague in front of others. Remember that the group
is often more important than the individual.
· DON'T address your Japanese counterpart by their first name
unless invited to do so. Use the titles 'Mr' or 'Mrs' or add 'san'
to their family name; for example, Mr Hiroshima will be
"Hiroshima san"
· DON'T use large hand gestures, unusual facial expressions or
dramatic movements. The Japanese do not talk with their hands.
* Source: CIA The World Factbook 2004

Student Lab Activity A. Lab # CIS CIS170A-A1B. Lab.docx

Recommended

Recommended

More Related Content

Similar to Student Lab Activity A. Lab # CIS CIS170A-A1B. Lab.docx

Similar to Student Lab Activity A. Lab # CIS CIS170A-A1B. Lab.docx (19)

More from emelyvalg9

More from emelyvalg9 (20)

Recently uploaded

Recently uploaded (20)

Student Lab Activity A. Lab # CIS CIS170A-A1B. Lab.docx