After completing Lab Assignment 1, students should be be able to
| Team 1 | Team 2 | Team 3 | Team 4 | Team 5 |
|---|---|---|---|---|
| Liam | Brock | Samwise | Tom | Paul |
| Gene | Trevor | Gary | Kevin | Ben |
You may wish to review basic pair programming guidelines before you begin.
You should change roles with each iteration
Using pair programming, and changing roles within each iteration, use Visual Studio to author a Document Type Definition (DTD) to validate a club membership list against a list of constraints.
You may wish to refer to W3Schools DTD tutorial for syntax
In one of your two accounts, create a Lab1 web site using Visual Studio 2008.
Working together as driver and navigator
Iteration1.xml and a text file named Iteration1.dtdIteration1.xml used to contain membership information for a clubIteration1.dtd to enforce
Club consists of a MembershipList
Membership list may possibly be empty if the club has no membersMembershipList consists of zero of more MembersMembers will be listed by their Name with id (attribute), FirstName, MiddleInitial (optional), and LastName
FirstName, MiddleInitial (optional), and LastNameIteration1.dtd file against the sample one member club XML data provided below
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE Club SYSTEM "Iteration1.dtd" >
<Club>
<MembershipList>
<Member id="_972134">
<Name>
<FirstName>Scott</FirstName>
<MiddleInitial>T</MiddleInitial>
<LastName>Obert</LastName>
</Name>
</Member>
</MembershipList>
</Club>
Before beginning these functional tests, switch roles between driver and navigator. Test and debug your Iteration1.dtd for validation success and errors with
Iteration1.xml data fileMiddleInitialid valuesFirstName, MiddleInitial, and LastName valuesBegin this iteration with the same roles used with Iteration 1's functional testing. That is, the current driver should have begun Iteration 1 as the navigator, the current navigator should have begun Iteration 1 as the driver.
Iteration2.xml and a text file named Iteration2.dtdIteration2.xml used to contain an expanded membership information for a clubIteration2.dtd to serve as the starting point for the DTD rulesIteration1.xml and Iteration1.dtd in the editor to get them out of the wayAdd the DTD elements and attributes to Iteration2.dtd to require
Club needs a unique clubId attribute followed by its required ClubName.
MembershipList element list should include a club attribute that references the club's idMember will include an optional clubs attribute that references the Club ids that the member belongs to.
Email address is optionalAddress elements: one local or permanent
Street elementsIteration2.dtd file against the sample one member club XML data provided below
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE Club SYSTEM "Iteration2.dtd">
<Club clubId="ACM">
<ClubName>Student Chapter of the ACM</ClubName>
<MembershipList club="ACM">
<Member id="_972134" clubs="ACM">
<Name>
<FirstName>Scott</FirstName>
<MiddleInitial>T</MiddleInitial>
<LastName>Obert</LastName>
</Name>
<Email>ObertS@cwu.edu</Email>
<Address type="local">
<Street>1808 W. Alder Street</Street>
<City>Ellensburg</City>
<State>WA</State>
<ZipCode>98926</ZipCode>
</Address>
<Address type="permanent">
<Street>P.O. Box 1234</Street>
<Street>101 1st Avenue</Street>
<City>Yakima</City>
<State>WA</State>
<ZipCode>98933</ZipCode>
</Address>
</Member>
</MembershipList>
</Club>
Before beginning these functional tests, switch roles between driver and navigator.
Right-click, download and save to your Lab1 folder the following three test files. Test and debug your Iteration2.dtd for validation success and errors.
Lab 1 is an in-class assignment begun on Wednesday and due by the start of class on Friday
U:\Labs\nnLab1 in one of your cs352 accounts where nn is your account numberIteration2.dtd code ()