GUI For Computer Architecture May01-05 Team Members: Neil HansenCprE Ben JonesCprE Jon MathewsCprE Sergey SannikovCprE Clients/Advisors: Manimaran Govindarasu Arun Somani April 25, 2001

Presentation Outline Problem Statement Problem Statement Design Objectives Design Objectives End Product Description End Product Description Assumptions and Limitations Assumptions and Limitations Project Risks and Concerns Project Risks and Concerns Technical Approach Technical Approach Recommendations for Further Work Recommendations for Further Work Evaluation of Project Success Evaluation of Project Success Human and Financial Budgets Human and Financial Budgets Lessons Learned Lessons Learned Closing Summary Closing Summary Questions Questions

Problem Statement Verilog and SimpleScalar are tools that aid in the study of computer architecture, but they lack a flexible graphical user interface (GUI). Verilog and SimpleScalar are tools that aid in the study of computer architecture, but they lack a flexible graphical user interface (GUI). Professors in computer engineering at Iowa State would like to enhance the visualization of the computer architecture that the students are studying. Professors in computer engineering at Iowa State would like to enhance the visualization of the computer architecture that the students are studying.

Design Objectives Develop a GUI for a computer architecture simulator that: Allows students to see the process of instruction execution. Is simple to use and understand. Layers are used to show and hide information and to improve clarity.

End Product Description The product is a GUI educational tool for students studying micro-architecture. It animates the execution of MIPS assembly programs cycle by cycle. The animation is based on data generated by a Verilog simulation of the computer architecture. Instructors can simulate new programs with the provided tools for distribution to the students.

Program Screenshot

Assumptions and Limitations The micro-architecture is limited to a simplified version of MIPS architecture as described in CprE 305. Users are expected to be familiar with the MIPS instruction set. Animations consist of less than 60 cycles. The simulator must be capable of producing text output. Screen size limits the effective display of information.

Project Risks and Concerns Possible Risks: Not finishing on time. Not finishing on time. Losing a team member. Losing a team member. Pitfalls of learning a new language. Pitfalls of learning a new language. Risks Encountered: Complexity of the architecture. Complexity of the architecture. Preferred version of Verilog hard to find. Preferred version of Verilog hard to find. Security issues with Java. Security issues with Java. Source management. Source management.

Technical Approach Micro-architecture simulator (Verilog) Translator (Perl) GUI software (Java) SimulatorTranslatorGUI

Technical Approach (cont.) Micro-architecture Simulation and Tools Assembly Source Code Verilog Model Verilog Instruction Memories Verilog Output Assembler

Technical Approach (cont.) The Translator Verilog Output Translator Assembly Program Traces

Technical Approach (cont.) GUI Program Traces

Recommendations for Further Work Support advanced architecture features. Support advanced architecture features. A server version of the software would allow students to submit their own code for animation. A server version of the software would allow students to submit their own code for animation. Enhance the quality of the animation with multimedia. Enhance the quality of the animation with multimedia.

Evaluation of Project Success Milestones: Assembler to create Verilog programs. Verilog model of architecture. Translator from Verilog to GUI. GUI software. User and Instructor Manuals Code documentation.

Project Success (cont.) Testing Approaches   System test   Evaluation test by graduate students and faculty:   Provides feedback on the effectiveness of the tool   Determines the suitability as a presentation tool   User test by students currently taking CprE 305 to provide feedback on the usability of the tool.

Human and Financial Budgets

Human and Financial (cont.)

Lessons Learned Start early on all deliverables. Start early on all deliverables. Software can disappear from the labs. Software can disappear from the labs. Contingency plans are helpful. Contingency plans are helpful. Goals and milestones keep the project on track. Goals and milestones keep the project on track. Communication and teamwork make for smooth sailing. Communication and teamwork make for smooth sailing.

Closing Summary This software allows students to better visualize the internal processes of a micro-architecture. This software allows students to better visualize the internal processes of a micro-architecture. Instructors are able to present course material in more flexible format. Instructors are able to present course material in more flexible format.

Questions? Comments…? Concerns…?