1. CSE 560aa08

2. Team Members Kermit Stearns: Project Leader Oscar Flores: Test and Validation Leader Dan Burnett: Documentation Leader Bobby Molique Schmidt: Code Manager Rakaan Kayali: Design Leader

3. Preliminary Schedule (SP1+SP2) Step 1: Instructions/Directives. ASCII Space-separated file for all the instructions. ASCII Space-separated text file for comparison of directives. Methods for instruction and directive conversion Building Error Table (construction of table will start with identifying invalid labels and will progress concurrently with project). Preliminary thoughts on Error table suggest an ASCII text file with error messages written on numbered lines. Messages accessed based on line number which corresponds to error number.

4. Preliminary Schedule (SP1+SP2) Step 2: Building Code Symbol Table: Constructed as a distinct class. Additions made as pass 1 parses the code. Write methods to convert symbols to machine hex. Initiate our Location Counter (LC) and our Next Instruction Counter (NIC).

5. Preliminary Schedule (SP1+SP2) Step 2 Continued… Parse code We make a distinction between five tokens (Instructions, Directives, Comments, White Space and Errors). Store code “Objects” in container as intermediate source code for pass 2. End result is source code for pass 2. Step 3: Produce Object File Convert intermediate source code produced in step 2 into machine hex.

6. Team management and communications plan… Testing and validation Aim is to have a testable version of our project 7 days before the due date. Extensive testing of outlier positions, special cases and normal functionality during last week before submission. Team Standards Checkstyle (Sun Code Convention for Eclipse) format nouns for objects, verbs for methods start objects with lowercase, meaningful names methods and classes are uppercase preference for comments to precede the line of code (javadoc comments)

7. Team management and communications plan… Staying Informed: Calling, Texting, Gmail chat and email. Sharing group files through repository (Google Code). Shared Google Calendar to ease process of meeting scheduling. Resolving Conflict: Majority Vote (voting can be in person or through text or email). In case voting process in unsatisfactory, project leader casts deciding vote with option of consulting with professor. Source Code Management: Subversion (SVN) via Google Code Subclipse plug-in for eclipse

8. Data Flow Diagram Inputs to Pass One: Source Code From User Machine Op-Table Directives Error Table Assembler Pass One Intermediate Version of Source Code Develops Symbol Table Assembler Pass Two Assembler Output Sorted Symbol Table The Source Listing Object file Error Messages where appropriate

9. Questions?