<- previous index next ->
Each team will have a laptop or use the instructors laptop
to connect to the projector. Teams go in the order of their
team number.
Introduce your team:
Company name
Product name
Team members
Bring up your UID, point out some parts.
Your choice, what you like, what you think is good, etc.
About 5 minutes, maximum of 10 minutes.
Next, fill in the Code Inspection Report, cir, Template.
It is getting a little harder to work as a team.
In some development processes, this would be called
a "Test Plan" with some reporting of actual testing
included.
Section 1.3 Include a "style guide" consisting of appropriate
coding and commenting conventions for your choice of language
and design. Everyone on the team will be reading the code
and checking against what you write. Including me and
probably your customer. Be reasonable.
Section 1.4 "possible defects" are a list of everything that
you will be testing for. Look for any limits or size
restrictions from your SRS, SDD, and UI. You are basically
listing all the items you will be testing.
e.g. User name can not be more than 31 characters.
(use your applications limits)
One item is "Check that code follows the coding and
commenting conventions."
You may use lists and tables.
Looking ahead to the "Test Report" you may want to
number the items in the list. Yes, there is some
redundancy, yet, testing is an important part of
product development.
Then, the application must be written and your inspection
results recorded in section 3.
Now the Code Inspection Report, CIR is assigned.
CS345 Project
<- previous index next ->