DOC PREVIEW
UMD CMSC 131 - Lecture Set 1: Introduction

This preview shows page 1-2-3-4-5 out of 14 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 14 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 14 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 14 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 14 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 14 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 14 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

1CMSC 131 Spring 2007Bonnie Dorr (adapted from Rance Cleaveland)Lecture Set 1: IntroductionToday’s topics:1.Course information2.Tools needed for this course3.Computer terminology basics1CMSC 131 Fall 2007Jan Plane (adapted from Bonnie Dorr)CMSC 131Name: “Object-Oriented Programming I”Instructor: Jan PlaneClass meetingsLecture: 03xx Lecture MWF 2-2:50 in CSIC 211704xx Lecture MWF 3-3:50 in CSIC 2117Lab sections (CSIC 2118)0301: MW 10:00 -10:50 in CSIC 21200302: MW 11:00 - 11:50 in CSIC 21200401: MW 11:00 – 11:50 in CSIC 21070402: MW 12:00 – 12:50 in CSIC 21072CMSC 131 Fall 2007Jan Plane (adapted from Bonnie Dorr)Coordination of SectionsFive sections total of CMSC 131two lectures taught by me three lectures taught by Fawzi EmadTen TAs in total for the 5 sectionsAll sections will be closely coordinated:Same lecture material on same daySame projectsSame labsCoordinated examsLab/Discussion/Recitation Sectionsexercises – laptopsquizzesnew material occasionally23CMSC 131 Fall 2007Jan Plane (adapted from Bonnie Dorr)What Is This Course?A fast-paced introduction to techniques for writing computer programs! Skill Development in ProgrammingConceptual Understanding of ProgrammingNot really “computer science”There will be quite a bit of work but assumes you are starting at level 0.Keys to successAttend all classes and lab sectionsStart assignments early – and continue until you truly understandGet help early if you are having trouble – 2 instructors & 10 TAsStudy every dayit doesn’t work to cram for these examsask questions as soon as you realize you are confusedCheck announcements on course web-page every day4CMSC 131 Fall 2007Jan Plane (adapted from Bonnie Dorr)BookJava™ Software Solutions: Foundations of Program Design (5thedition), by Lewis & LoftusLectures do not follow book closelyBook is very useful as a reference5CMSC 131 Fall 2007Jan Plane (adapted from Bonnie Dorr)Course Web-Pagewww.cs.umd.edu/class/fall2007/cmsc131/Check daily!Review:AnnouncementsSyllabusContactScheduleLecture slides - outlines36CMSC 131 Fall 2007Jan Plane (adapted from Bonnie Dorr)Study QuestionsAvailable on web-pageLogin: studyPassword: dailyLook at them on evenings before class; they will help you keep up7CMSC 131 Fall 2007Jan Plane (adapted from Bonnie Dorr)Course SoftwareEclipseAn IDE (integrated development environment)You will use it for writing Java™ programsAccess to Eclipse (it’s free!)You can install it on your own machine: http://www.cs.umd.edu/eclipseAlso accessible in Workstations at Maryland (WAM) labs around campus: http://www.wam.umd.edu/CVS (Concurrent Versions System)A version-management systemYou will use it for submitting your projectsWe will talk more about this later8CMSC 131 Fall 2007Jan Plane (adapted from Bonnie Dorr)Tools for Writing ProgramsThe bad old daysText editor: used to create files of source codeCompiler: generate executables from sourceDebugger: trace programs to locate errorsToday: IDEs (= “integrated development environment”)Text editor / compiler / debugger rolled in oneExamples: Eclipse, Visual Studio, etc.49CMSC 131 Fall 2007Jan Plane (adapted from Bonnie Dorr)Basics of Eclipsewww.cs.umd.edu/eclipse/EclipseTutorial/Eclipse is used to:CreateEditCompileRunDebugprograms (for this class, Java programs).10CMSC 131 Fall 2007Jan Plane (adapted from Bonnie Dorr)Basics of Eclipse-speakProject: collection of related source filesTo create a program in Eclipse:Create a new projectCreate files in the projectPerspective: framework for viewing and/or manipulating programsImportant perspectives in this class:Java: for creating, running programsDebug: for tracing, removing errors in programsCVS repository: for interacting with assignment-submission system11CMSC 131 Fall 2007Jan Plane (adapted from Bonnie Dorr)Eclipse Demo512CMSC 131 Fall 2007Jan Plane (adapted from Bonnie Dorr)Class Projects with CVSYou will use Eclipse for Java programming in this courseHow will you:obtain (check-out) files that are supplied to yousave (commit) the files for later workturn in (submit) when you are finishedclass projects?CVS (= Concurrent Versions System)Tool for project-file managementMaintains versions, etc.Allows different sites to work on same project13CMSC 131 Fall 2007Jan Plane (adapted from Bonnie Dorr)CVS WorldviewFiles =“repository”ServerFiles(local copies)Client 1Files(local copies)Client 2“checkout”“checkout”“commit”“commit”14CMSC 131 Fall 2007Jan Plane (adapted from Bonnie Dorr)CVS in More DetailCVS server maintains current versions of files in project (= “repository”)To access files from another machine (“client”), repository files must be “checked out”Changes to files on client may be “committed” to server, with changed files becoming new version(Once a repository is checked out by a client, subsequent versions may be accessed via “update”)615CMSC 131 Fall 2007Jan Plane (adapted from Bonnie Dorr)What’s Needed for CVS?Server machineFor CMSC 131, CS linuxlab machinesUser authenticationFor CMSC 131, student linuxlab accounts16CMSC 131 Fall 2007Jan Plane (adapted from Bonnie Dorr)How CMSC Project Submission WorksRepository created for each student linuxlabaccountYou check out repository to start work on projectWhen you “save” changes in Eclipse, “commit”automatically invoked by plug-insYou “submit” when finished using Eclipse (UMD plug-in handles relevant CVS commands)17CMSC 131 Fall 2007Jan Plane (adapted from Bonnie Dorr)To Checkout a Project1.Set repository locationChange to “CVS Repository Exploring”perspective in Eclipse (“Window -> Open Perspective” …)Right-click in “CVS Repositories” panel and select “New -> Repository Location…”718CMSC 131 Fall 2007Jan Plane (adapted from Bonnie Dorr)Adding a CVS RepositoryCommon to everyoneYour linuxlab usernameYour linuxlab passwordDon’t forget to set this!19CMSC 131 Fall 2007Jan Plane (adapted from Bonnie Dorr)To Checkout a Project (cont.)1.Open repository name, then “Head”2.Right-click on project name to save20CMSC 131 Fall 2007Jan Plane (adapted from Bonnie Dorr)821CMSC 131 Fall 2007Jan Plane (adapted from Bonnie


View Full Document

UMD CMSC 131 - Lecture Set 1: Introduction

Documents in this Course
Set #3

Set #3

7 pages

Exam #1

Exam #1

6 pages

Exam #1

Exam #1

6 pages

Notes

Notes

124 pages

Notes

Notes

124 pages

Load more
Download Lecture Set 1: Introduction
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Lecture Set 1: Introduction and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Lecture Set 1: Introduction 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?