Register now to access 7 million high quality study materials (What's Course Hero?) Course Hero is the premier provider of high quality online educational resources. With millions of study documents, online tutors, digital flashcards and free courseware, Course Hero is helping students learn more efficiently and effectively. Whether you're interested in exploring new subjects or mastering key topics for your next exam, Course Hero has the tools you need to achieve your goals.
12 Pages
EWW_LCO_F04a_T04
Course: CSCI 577, Fall 2009School: USC
Rating:
Word Count: 1999
Document Preview
Sushil Premjani David Cabezas Usha Guduri Nishant Kaushik Kajal Bhargava Abhyuday Chakravarthi Contents 1. Identify Success-Critical Stakeholders 2. Review and Expand Negotiation Topics 3. Classify Win Conditions By Priority 4. Negotiate Agreements 5. Check Completeness 6. Glossary 1. Identify Success-Critical Stakeholders NAME Dr. Gary Seaman Sushil Premjani David Cabezas Nishant Kaushik Kajal Bhargava Usha...
Unformatted Document Excerpt
Coursehero >> California >> USC >> CSCI 577Course Hero has millions of student submitted documents similar to the one
below including study guides, practice problems, reference materials, practice exams, textbook help and tutor support.
Course Hero has millions of student submitted documents similar to the one
below including study guides, practice problems, reference materials, practice exams, textbook help and tutor support.
Sushil Premjani David Cabezas Usha Guduri Nishant Kaushik Kajal Bhargava Abhyuday Chakravarthi Contents 1. Identify Success-Critical Stakeholders 2. Review and Expand Negotiation Topics 3. Classify Win Conditions By Priority 4. Negotiate Agreements 5. Check Completeness 6. Glossary 1. Identify Success-Critical Stakeholders NAME Dr. Gary Seaman Sushil Premjani David Cabezas Nishant Kaushik Kajal Bhargava Usha Guduri ROLE Client System Architecture OCD Lifecycle Plan Feasibility Rationale EMAIL ADDRESS seaman@usc.edu dcabezas@usc.edu nkaushik@usc.edu kbhargav@usc.edu guduri@usc.edu abhyudac@usc.edu Project Manager , Prototype premjani@usc.edu Abhyuday Chakravarthi Requirements Analysis 2. Review and Expand Negotiation Topics Tool Name: Outline of Ways to Win 1. Project requirements 1. Budget/Schedule 2. Development Requirements 2.1. Tools Requirements 2.2. Language Requirements 2.3. Hardware Requirements 2.4. Communication Requirements 2.5. Standards Compliance requirements 3. Deployment Requirements 4. Transition requirements 5. Support Environment Requirements 2. Capabilities 1. Nominal Requirements 2. Off-nominal Requirements 3. System Interface 1. <a href="/keyword/user-interface-standards-requirements/" ><a href="/keyword/user-interface-standards/" >user interface standards</a> requirements</a> 1.1. Graphical <a href="/keyword/user-interface-standards/" >user interface standards</a> 2. Communications Interface requirements 3. Other Software Requirements Interface 4. Level of Service 1. Dependability 2. Usability 3. Performance 4. Security 5. Evolution 1. Capability Evolution Requirements 2. Interface Evolution Requirements 3. Level of Service Evolution requirements 4. Workload and Environment Evolution Requirements 3. Classify Win Conditions by Priority 1. Project requirements 1. Minimal budget for hardware and licenses - $500 [LHF, Agreed, Budget and Schedule] 2. Server will run on Mac OS G4 [IWH, Hardware Requirements] 3. Even though project done last year, no legacy system requirements - A completely new deployment which need not cater to existing ones [LHF, Agreed, Dependability, Transition requirements, Deployment Requirements] 4. Input format will be in any text format that preserves formatting [LHF, Agreed, Transition requirements] 5. We have 24 weeks in all : 12 for planning and architecture and the next 12 for actual deployment [LHF, Agreed, Budget and Schedule] 6. Freedom of choice for programming and annotating languages [LHF, Agreed, Language Requirements, Performance, Tools Requirements] 7. Freedom of choice for any Database [LHF, Agreed, Tools Requirements, Support Environment Requirements, Performance] 2. Capabilities 1. Search by four criteria: ethnonym (tribal names), geographic area, author, coding category. [LHF, Nominal Requirements, <a href="/keyword/user-interface-standards-requirements/" ><a href="/keyword/user-interface-standards/" >user interface standards</a> requirements</a> ] 2. Browse by four criteria: ethnonym (tribal names), geographic area, author, coding category. [LHF, Nominal Requirements, <a href="/keyword/user-interface-standards-requirements/" ><a href="/keyword/user-interface-standards/" >user interface standards</a> requirements</a> ] 3. Search for texts and annotated image/graphics [LHF, <a href="/keyword/user-interface-standards-requirements/" ><a href="/keyword/user-interface-standards/" >user interface standards</a> requirements</a> ] 4. Two modes: administrator, user [LHF, Agreed, Deployment Requirements] 5. User shall be able to view full texts and summaries of texts [LHF, Agreed, Nominal Requirements] 6. Error messages for invalid keyword choice [LHF, Agreed, Off-nominal Requirements] 3. System Interface 1. Google look and feel to the interface (simplicity is desired) [Agreed, <a href="/keyword/user-interface-standards-requirements/" ><a href="/keyword/user-interface-standards/" >user interface standards</a> requirements</a> , Graphical <a href="/keyword/user-interface-standards/" >user interface standards</a> , LHF] 2. Mechanism for selecting search categories and coding [LHF, Agreed, <a href="/keyword/user-interface-standards-requirements/" ><a href="/keyword/user-interface-standards/" >user interface standards</a> requirements</a> , Deployment Requirements] 3. Ability to click on maps from the globe, scaling down to village settlements [Agreed, Graphical <a href="/keyword/user-interface-standards/" >user interface standards</a> , IWH] 4. Browse and Search option [LHF, Agreed, and Nominal Requirements] 5. Browse by coding, author, ethnonymns, geographical locations. [LHF, Nominal Requirements, Graphical <a href="/keyword/user-interface-standards/" >user interface standards</a> ] 6. Web interface [LHF, Agreed, Graphical <a href="/keyword/user-interface-standards/" >user interface standards</a> ] 7. A single interface between the client web interface and the search engine - HTTP [LHF, Agreed, Communications Interface requirements] 4. Level of Service 1. Password protection for all users (including administrations). [LHF, Agreed, Security] 2. 90% relevant search results [LHF, Performance] 3. Interface (search engine) is always available. If database is offline, informative message is issued. [LHF, Dependability] 4. Response time will be approx. 15 sec. [LHF, Agreed, and Performance] 5. Evolution 1. Currently, 242 coding categories. Must support addition of thousands of new categories in the future. [IWH, Agreed, Capability Evolution Requirements] 2. 32 hunter-gather societies are currently coded. Storage must support additional 130 societies. [LHF, Agreed, Capability Evolution Requirements] 3. Data set will be updated by admin-level user. [LHF, Agreed, Workload and Environment Evolution Requirements] 4. Software will be maintained by hired help (e.g. part-time undergraduate student). [LHF, Agreed, Level of Service Evolution requirements, Performance, Support Environment Requirements] Tool Name: Evaluation Graph 4. Negotiate Agreements Tool Name: WinWin_Tree 1. Project requirements 1. Minimal budget for hardware and licenses - $500 [LHF, Agreed, Budget and Schedule] 2. Server will run on Mac OS G4 [IWH, Hardware Requirements] 1. MOST OF US NOT FAMILIAR WITH THE MAC OS. [Support Environment Requirements, Hardware Requirements] 1. Client will provide the team with a MAC Powered Laptop to get accustomed to the OS. [Agreed, Hardware Requirements] 3. Even though project done last year, no legacy system requirements - A completely new deployment which need not cater to existing ones [LHF, Agreed, Dependability, Transition requirements, Deployment Requirements] 4. Input format will be in any text format that preserves formatting [LHF, Agreed, Transition requirements] 5. We have 24 weeks in all : 12 for planning and architecture and the next 12 for actual deployment [LHF, Agreed, Budget and Schedule] 6. Freedom of choice for programming and annotating languages [LHF, Agreed, Language Requirements, Performance, Tools Requirements] 7. Freedom of choice for any Database [LHF, Agreed, Tools Requirements, Support Environment Requirements, Performance] 2. Capabilities 1. Search by four criteria: ethnonym (tribal names), geographic area, author, coding category. [LHF, Nominal Requirements, <a href="/keyword/user-interface-standards-requirements/" ><a href="/keyword/user-interface-standards/" >user interface standards</a> requirements</a> ] 1. Flexibility for adding future search criteria [Capability Evolution Requirements] 1. Architected to support additional categories. [Agreed, Interface Evolution Requirements, Capability Evolution Requirements, Level of Service Evolution requirements] 2. Browse by four criteria: ethnonym (tribal names), geographic area, author, coding category. [LHF, Nominal Requirements, <a href="/keyword/user-interface-standards-requirements/" ><a href="/keyword/user-interface-standards/" >user interface standards</a> requirements</a> ] 1. Flexibility for adding future browsing criteria [Capability Evolution Requirements] 1. Architected to support additional categories. [Agreed, Capability Evolution Requirements, Interface Evolution Requirements, Level of Service Evolution requirements] 3. Search for texts and annotated image/graphics [LHF, <a href="/keyword/user-interface-standards-requirements/" ><a href="/keyword/user-interface-standards/" >user interface standards</a> requirements</a> ] 1. Evolve to support audio/video formats. [Capability Evolution Requirements] 1. Evolvability issue. Architecture shall take into consideration scalability for audio/video, but support is not required if not feasible. [Agreed, Capability Evolution Requirements] 4. Two modes: administrator, user [LHF, Agreed, Deployment Requirements] 5. User shall be able to view full texts and summaries of texts [LHF, Agreed, and Nominal Requirements] 6. Error messages for invalid keyword choice [LHF, Agreed, Off-nominal Requirements] 3. System Interface 1. Google look and feel to the interface (simplicity is desired) [Agreed, <a href="/keyword/user-interface-standards-requirements/" ><a href="/keyword/user-interface-standards/" >user interface standards</a> requirements</a> , Graphical <a href="/keyword/user-interface-standards/" >user interface standards</a> , LHF] 2. Mechanism for selecting search categories and coding [LHF, Agreed, <a href="/keyword/user-interface-standards-requirements/" ><a href="/keyword/user-interface-standards/" >user interface standards</a> requirements</a> , Deployment Requirements] 3. Ability to click on maps from the globe, scaling down to village settlements [Agreed, Graphical <a href="/keyword/user-interface-standards/" >user interface standards</a> , IWH] 4. Browse and Search option [LHF, Agreed, and Nominal Requirements] 5. Browse by coding, author, ethnonymns, geographical locations. [LHF, Nominal Requirements, Graphical <a href="/keyword/user-interface-standards/" >user interface standards</a> ] 1. Evolve to support additional browsing categories/criteria. [Capability Evolution Requirements] 1. Interface designed to support addition of additional browsing criteria [Agreed, Interface Evolution Requirements, and Capability Evolution Requirements] 6. Web interface [LHF, Agreed, Graphical <a href="/keyword/user-interface-standards/" >user interface standards</a> ] 7. A single interface between the client web interface and the search engine - HTTP [LHF, Agreed, Communications Interface requirements] 4. Level of Service 1. Password protection for all users (including administration). [LHF, Agreed, Security] 2. 90% relevant search results [LHF, Performance] 1. Client has no specific requirements for accuracy. [Performance] 1. Will confer with client to reach a measurable method for relevancy/accuracy needs. [Agreed, Performance, Usability] 3. Interface (search engine) is always available. If database is offline, informative message is issued. [LHF, Dependability] 1. Interface Availability subject to server. Client only requires availability during working hours. [Dependability] 1. Interface only needs to be available during working hours (8am - 5pm). [Agreed, Dependability] 4. Response time will be approx. 15 sec. [LHF, Agreed, and Performance] 5. Evolution 1. Currently, 242 coding categories. Must support addition of thousands of new categories in the future. [IWH, Agreed, Capability Evolution Requirements] 2. 32 hunter-gather societies are currently coded. Storage must support additional 130 societies. [LHF, Agreed, Capability Evolution Requirements] 3. Data set will be updated by admin-level user. [LHF, Agreed, Workload and Environment Evolution Requirements] 4. Software will be maintained by hired help (e.g. part-time undergraduate student). [LHF, Agreed, Level of Service Evolution requirements, Performance, Support Environment Requirements] 5. Check Completeness Tool Name: Taggertool 1 1.1 1.2 1.2.1 1.2.1.1 1.3 1.4 1.5 1.6 1.7 2 2.1 2.1.1 2.1.1.1 2.2 2.2.1 2.2.1.1 2.3 2.3.1 2.3.1.1 2.4 2.5 2.6 3 3.1 Item Project requirements Minimal budget for hardware and licenses - $500 [LHF, Agreed, Budget and Schedule] Server will run on Mac OS G4 [IWH, Hardware Requirements] MOST OF US NOT FAMILIAR WITH THE MAC OS. [Support Environment Requirements, Hardware Requirements] Client will provide the team with a MAC Powered Laptop to get accustomed to the OS. [Agreed, Hardware Requirements] Even though project done last year, no legacy system requirements - A completely new deployment which need not cater to existing ones [LHF, Agreed, Dependability, Transition requirements, Deployment Requirements] Input format will be in any text format that preserves formatting [LHF, Agreed, Transition requirements] We have 24 weeks in all : 12 for planning and architecture and the next 12 for actual deployment [LHF, Agreed, Budget and Schedule] Freedom of choice for programming and annotating languages [LHF, Agreed, Language Requirements, Performance, Tools Requirements] Freedom of choice for any Database [LHF, Agreed, Tools Requirements, Support Environment Requirements, Performance] Capabilities Search by four criteria: ethnonym (tribal names), geographic area, author, coding category. [LHF, Nominal Requirements, <a href="/keyword/user-interface-standards-requirements/" ><a href="/keyword/user-interface-standards/" >user interface standards</a> requirements</a> ] Flexibility for adding future search criteria [Capability Evolution Requirements] Architected to support additional categories. [Agreed, Interface Evolution Requirements, Capability Evolution Requirements, Level of Service Evolution requirements] Browse by four criteria: ethnonym (tribal names), geographic area, author, coding category. [LHF, Nominal Requirements, <a href="/keyword/user-interface-standards-requirements/" ><a href="/keyword/user-interface-standards/" >user interface standards</a> requirements</a> ] Flexibility for adding future browsing criteria [Capability Evolution Requirements] Architected to support additional categories. [Agreed, Capability Evolution Requirements, Interface Evolution Requirements, Level of Service Evolution requirements] Search for texts and annotated image/graphics [LHF, <a href="/keyword/user-interface-standards-requirements/" ><a href="/keyword/user-interface-standards/" >user interface standards</a> requirements</a> ] Evolve to support audio/video formats. [Capability Evolution Requirements] Evolvability issue. Architecture shall take into consideration scalability for audio/video, but support is not required if not feasible. [Agreed, Capability Evolution Requirements] Two modes: administrator, user [LHF, Agreed, Deployment Requirements] User shall be able to view full texts and summaries of texts [LHF, Agreed, Nominal Requirements] Error messages for invalid keyword choice [LHF, Agreed, Off-nominal Requirements] System Interface Google look and feel to the interface (simplicity is desired) [Agreed, <a href="/keyword/user-interface-standards-require...
Find millions of documents on Course Hero - Study Guides, Lecture Notes, Reference Materials, Practice Exams and more.
Course Hero has millions of course specific materials providing students with the best way to expand
their education.
Below is a small sample set of documents:
Below is a small sample set of documents:
USC - CSCI - 577
Client Meeting Notes Team#21 Project Title: CSE Website Enhancement Using Extreme Programming Week No.: 6 Week Period: 10/17-10/23 Date:10/22/04 Meeting Time: 3.30-5.00 pm Location: SAL 319 Duration:1 hr 30 min Attendance Team Members 1. Michael Chu
USC - CSCI - 577
Executive SummaryVersion 1.0Executive Summary of PATS EvaluationPrasad Hatalkar Chaitali Daftary Himani Tidke Nilesh Dherange Rajrupa Ghosh Nazim Pethani Tiffany Kim(Manager) (Tester and Test Reviewer) (Requirements Analyst) (Test Designer) (
USC - CSCI - 577
CSCI577A EASYWINWIN REPORTTeam 7: Data Mining of Digital Library Usage DataChi, Hui-Hsien FRD Chan, Shing-Cheung OCD Krivokon, Maxim SSRD Huang, Hsiao-Han SSAD Muliawan, Fenny LCP/Prototype Li, Pei-Han - UML1. Statkeholders Role Product Cus
USC - CSCI - 577
System and Software Architecture Description (SSAD)Online Bibliographies of Chinese Religions in Western LanguagesTeam 3 Stephan Pak: Project Manager Atul Vij: Requirements Rukmani khajuria: Operational Concept Puneet khurania: Prototypes Nantana
USC - CSCI - 577
Team Number: Week: Program Size (SLOC) Base Added Deleted Modified Reused # of COTS Total New SLOC Effort (Hours) Project Mgmt. Requirements COTS Assessment Design Life Cycle Planning Configuration Mgmt. Feasibility Analysis Wiki WinWin Maintenance A
USC - CSCI - 577
AARSummary_LCOCore_F07a_T05-3 - Areas of Concern LogProject Name: Artifact: Module: MBASE Phase/level: Activity: Exit Criteria:Crystal Stairs DashboardLco Core Inception PhaseReview # Review Date: Review Time:110/15/2007 8:00 AM3Date S
USC - CSCI - 577
Respond_AARSummary_LCP_LCODraft_F07a_T05.xls - Problem List CoverProject Name: Artifact: Module:Crystal Stairs Dashboard Protype : LCP_LCO_F07a_T05_V1.0.docReview #: Date: Activity: MBASE Phase/level:1-010/29/2007Type of review: Indep
USC - CSCI - 577
Team 20 Hunter-Gatherer DatabaseClient Meeting Report #1Date: Venue: Start time:9/18/2007 Grace Ford Salvatori Hall (Face to Face Interaction of the Client and the team) 1:00 pmAttendee: Mr. Christopher Boehm Mr. Munish Luthra Miss. Sumit Aila
USC - CSCI - 577
577A Team#3: Thai CDC Project Roles(1) Individual Team Member Role, Job Description and Responsibilities: Team Member Name: Laksmi Kodali Mallikarjun Team Member Role: Feasibility Rational Analyst and Project Manager Team Member Responsibilities: P
USC - CSCI - 577
577b Risk AssessmentBID Review SystemTeam No 11Aswani Priyanka Seernam Divyanka Amit Ashutosh Mithila Rao Velishala Yuwei Jiang Julie Payne William Yeoh Keith CullingProject Manager Asst. Project Manager / Asst. Shaper QA Software Architect /
USC - CSCI - 577
Plan SummaryTeam Number: Week: Program Size (SLOC) Base Added Deleted Modified Reused # of COTS Total New SLOC Effort (Hours) Project Mgmt. Requirements COTS Assessment Design Life Cycle Planning Configuration Mgmt. Feasibility Analysis Code COTS Ta
USC - CSCI - 577
Initial PrototypeVersion No: 1.2Initial PrototypeProject Name: EEO Section Database Team number: Team 13Team members and roles:Team Member Kshama Thacker Siddhi Mehta Anuneet Kumar Gaurav Vasa Anuj Gupta Rishi Popat Akshay Garg Art Irigoyen C
Loyola Chicago - GILBERT - 603
USC - CSCI - 577
TEAM#16-CLIENT MEETING NOTESDATE: 09/11/2008 VENUE: SAL 328 START TIME: 13:30 PST ATTENDEES: Ms. Julie Sanchez(Client) Mr. Jae Young Bang(Program Manager) Mr. Ka Ho Au(Prototyper) Mr. Shi Heng Guan(Planning and Control Engineer/ Asst. Shaper) Mr You
USC - CSCI - 577
SUPPORTINGINFORMATION DOCUMENT(SID) ProyectoPastoralatDoloresMission 135N.MissionRoad,LosAngeles,CA90033 [Phone:3238810018,Fax:3232687228] [info@proyectopastoral.org] RevampingProyectoPastoral[Fall2008]The purpose of the Supporting Informat
USC - CSCI - 577
Respond_AARSummary_LCP_FCCore_F08a_T03 - Areas of Concern LogProject Name: Artifact: Module: MBASE Phase/level: Activity:Team 3: Revamping Proyecto PastoralLCP N/A Valuation Lifecycle PlanningReview # Review Date: Review Time:LCP10/13/2008
USC - CSCI - 485
CSCI 485, Midterm IIDecember 2, Fall 2004 Prof. Shahram Ghandeharizadeh Warm-up (15 points) 1. (5 points) Write your name and student-id on your blue book. 2. (10 points) What does it mean for a program to be a transaction? (Definition of the term t
USC - AME - 101
AME 101 Fall 2008 Problem Set #1 Assigned: 9/5/2008 Due: 9/12/2008, 4:30 pm, in drop-off box in OHE 430 Problem #1 (15 points) The friction factor (f) for flow of a fluid with density , velocity U, in a pipe of length L, diameter d, resulting in a pr
Youngstown - CC - 58176940
Text Environments in LYXG. Jay Kerns August 26, 2008Contents1 Lists of Information (this is a Section)1.1 1.2 Bulleted and Numbered Lists (Subsection) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other Types of Lists (Subsection) 1.
Youngstown - CC - 5895
S1-S3 univariate skewness, r1-r3 univariate kurtosisDiscriminant Analysis Example: Fisher's Iris Data STAT 5895: Summer 2007 Run #2TYPE=Iris-setosa Obs S1 S2 S3 R1 R2 R31 0.30861 0.20748 0.55788 0.24973 1.32093 -0.39765 TYPE=Iris-versic Obs S1 S
Arizona - GEO - 412
A Brief Introduction to Benthic Marine InvertebratesWhy study marine invertebrates?For a gentlemen should know something of invertebrate zoology, call it culture or what you will, just as he ought to know something about painting and music and the
UMKC - ECON - 502
UMKC - ECON - 502
UMKC - ECON - 602
Arizona - ECOL - 437
Lecture 25, 14 Nov 2006 Vertebrate Physiology ECOL 437 (MCB/VetSci 437) Univ. of Arizona, Fall 2006 Kevin Bonine & Kevin OhHousekeeping, 14 Nov 2006- Dont forget to do seminar write-up! (due 10 November) - Turn in peer edits.Upcoming Readings to
Arizona - ECOL - 406
Lecture 25, 13 Nov 2007 Restoration etc. Conservation Biology ECOL 406R/506R University of Arizona Fall 2007 Kevin Bonine Cathy HulshofUpcoming Readings today: Ch 11 and weblinks (Restoration, Reconciliation) Thurs 15 Nov: Ch 12, and web-links (Eco
Arizona - ECOL - 437
Lecture 23, 07 Nov 2006 Vertebrate Physiology ECOL 437 (MCB/VetSci 437) Univ. of Arizona, Fall 2006 Kevin Bonine & Kevin OhHousekeeping, 07 Nov 2006Kidney/Urine Lab on 08 November, Term Paper drafts (2 with codenames) Dont forget to do seminar wri
Reed - ART - 395
Dalai Lama Shows Support for Olympics, and Protests - New York Times3/1/09 12:09 PMApril 11, 2008Dalai Lama Shows Support for Olympics, and ProtestsBy MARTIN FACKLERTOKYO The Dalai Lama said Thursday that he supported Beijings hosting of th
Reed - ART - 395
Arizona - GEOS - 212
Geos 212 Introduction to Oceanography NAME _ Practice Exam 3: Fall 2008 Put your name on every page of this exam pages have been lost before. No books, notes, calculators, conversations, or anything but your own brain.Section 1: Multiple Choice (
Alabama - CS - 357
Outline and Reading CS 357 Data StructuresLecture 9 Fall 2004 Department of Computer Science University of Alabama Trees PriorityQueue ADT (7.1) Total order relation (7.1.1) Comparator ADT (7.1.4) Sorting with a priority queue (7.1.2) Selection-sort
Alabama - CS - 357
Active Learning CS 357 Data StructuresLecture 1 Fall 2004 Department of Computer Science University of Alabama Active Participation in ClassroomQuestioning Preparation Working in Pairs ReportingPair Up: What data structures do you already know?
Alabama - CS - 325
Lecture 16 Tuesday, December 6thTodayBasics of Java appletsAnnouncementsBonus project available, due 9:30am on Dec. 8th Thursday surveys Determine format of final Q&A regarding finalFinal Exam Wednesday, December 14th, 8:00am 10:30amQui
Alabama - CS - 325
Lecture 6 Today More Unix A small bit more with Iterators Homework Project 1 due Friday night at 9:00 pm Announcements Quiz today Homework assignment on inheritance by tomorrowSummer 2002 CS 325 Class Notes Page 1Moving files to/from Uni
Alabama - CS - 325
CS 325 - Class 16 Today Start MFC introductionMicrosoft Windows Reading Visual C+ manuals are onlinehttp:/msdn.microsoft.com/library Announcements Exam 1: This Friday 6/27 Find them, read an article or two AssignmentsGet familiar with
Alabama - CS - 325
Lecture 9 Thursday, February 15TodayCommand-line arguments in Java Input with Java, console and graphicalAnnouncementsProject is due Monday i ht t 9pm P j t 3 i d M d night at 9Command line args in Javapublic class CmdArgs { public static voi
Alabama - CS - 325
Lecture 06 Thursday, September 15thTodayClient/server computing the details The necessary data structures Writing a client Writing a serverAssignmentsProject Two is due next Tuesday at 9:30amOverview of the basicsClient must knowServer n
Alabama - CS - 325
CS 325Exam OneSpring 2007Short Answer Questions (30 points, 2 points each) 1. What is your favorite Unix editor?Will accept any Unix editor as the answer2. What does the following Unix command do? cp ~cordes/hello* .Copies all files in ~co
Alabama - CS - 325
Lecture 13 Tuesday, November 15thTodayFew more details with inheritance & exceptions Material from today is NOT on the examProject Six status reportsAnnouncementsExam Three is Thursday (open book, open note) Inheritance and ExceptionsProje
Alabama - CS - 603
Formal SemanticsThe syntax of a programming language is formally defined by a grammar. How can its semantics be formally defined? The semantics definition should capture the "meaning" of each syntactic construct.1Kinds of Formal Semantics Operat
Alabama - CS - 357
Announcements Next time, finish chapter 8. Project 3 is out and due this Saturday, March 23, by 11:59p. Project 4 will be out on Friday.CS 357: Data StructuresClass 23 March 18, 2001Spring 2002 CS 357 Class NotesPage 2More Practice Gener
Arizona - MGE - 415
Rock ExcavationDrilling with a Student Centered Focus. Modules 2.1 2.2 Spring 2004 Assignment #21. Consider you have to drill a Humboldt iron silicate with a 2 inch diameter drill. Assume the work rate for the drill is 195,000 in-lb/min and the en
Arizona - MGE - 415
Alabama - PH - 105
PH105-001Quiz 6cOct. 13, 2006A 1200-kg car traveling at 25 m/s rear-ends a 2400-kg truck initially at rest. The car gets entangled with the truck so they move together with a common velocity after the collision. (a) What is speed of the car and
Alabama - PH - 101
Name _ PH101-001 Exam 2a-key March 12, 20081. A soldier wants to knock down a door by firing a round of bullets from a machine gun into the door. He can use either lead bullets which become embedded in the door or rubber bullets that bounce off the
Contra Costa College - CHEM - 325
Stereoisomers I- enantiomers: non-superposable mirror images - diastereomers: non-superposable, but not mirror images A. Centre of chirality - asymmetric central atom - for carbon, indicated C* Notations:CHO H OH CH3CHO H 3C OH HH3C OH CHO HSum
Alabama - EC - 110
Name: _ Class: _ Date: _ID: AExam 2 Study GuideMultiple Choice Identify the choice that best completes the statement or answers the question. _ 1. The presence of price controls in a market usually is an indication that a. an insufficient quanti
Arizona - AST - 541
Astronomy 541 Extragalactic Astronomy and CosmologyUniversity of Arizona, Spring 2009 MW 1:15-2:30 pm Replacement lectures Friday at the same time Course Summary This course will study extragalactic astrophysics, beginning with the fundamentals of
Arizona - AST - 541
Assignment 5Astronomy 541 Assignment: Due Wednesday, February 25, in classProblem 1 (4 pts): For m = 1 and cs = 0, show that the gravitational potential of a growing-mode perturbation is time independent (as usual, ignore the homogeneous term in t
Arizona - AST - 541
Assignment 4Astronomy 541Assignment: Due Wednesday, February 18, in classProblem 0 (not to be turned in): Verify the statements in lecture that: a) the ratio of the number density of photons to that of nucleons is about 1.8 10 9 for 2 b h2 = 0.0
Arizona - AST - 541
Assignment 2Astronomy 541To remind you, there will not be lectures on Monday February 9 and Wednesday February 11; instead there will be lectures on Fridays February 6 and 13. First, some ungraded back-of-the-envelope calculations to try: 1) How ma
Arizona - PHYS - 205
Computational Physics Syllabus.page 1Physics 205: Computational PhysicsFall 2007 Section 2: Room 204/208 Steward ObservatoryTelephone: Email: Office: Hours: Prof. Daniel Eisenstein 621-5904 deisenstein@as.arizona.edu Steward room 322 Tuesday 9:15
Arizona - AST - 400
Assignment 9Astronomy 400BRemember that the second midterm is in class on Tuesday, April 22.Assignment: Due Tuesday, April 8, in classProblem 1 (5 pts): The age of a universe with m = 1 and zero is 2/3H0 . We believe that the universe is at le
Alabama - OM - 300
Inventory ManagementChapter 10 IntroductionInventory Management Part 1What is Inventory?A stock of items kept by an organization to meet internal or external customer demand.1Inventory Management Part 1 Department of IS, Stat, MS, 2001 Dep
Alabama - OM - 300
ST 250 Bivariate DataObjective: Estimate the mean weight for all males that have: Height Waist Age70 70 70 62 76 76 30 36 36 28 28 40 21 yrs 21 45 21 21 211TRUE Model:Y = B0 + B1X1 + B2X2 + + BkXk + Y = the variable whose mean will be esti
Arizona - BIOC - 462
BIOC 462b Dr. Tischler NUTRIENTS IN BIOCHEMISTRY Text: pages 519-520; 549-550; 633-635; 657-659; 677; 691-692; 891; 895 Recommended Problems to Solve: 14-16; 23-7 Objectives: 1. Describe an unhealthy macronutrient diet that would lead to an increase
USC - ECON - 480
Topic 3 - Monopoly power and price discrimination If the rm knows only the demand function D(p), the optimal strategy is to choose a price per unit p. Sometimes, the rm has some information on consumers preferences. In that case, it is optimal to pr
USC - ECON - 681
ECON 681 Contract TheoryWeekly readings All students must read the paper they are instructed to read. If you do not read the paper in advance, you will not be able to understand the course material. Reading consists at least in (i) the abstract and
USC - ECON - 480
Topic 6 - Barriers to entryThere are two types of barriers to entry: (i) structural, that is given by a firm's inherent situation and (ii) strategic, that is created by firms' choices. Structural barriers: firms' costs (economies of scale, technol
USC - ECON - 480
Elements of Game Theory Basic Game Theory Terms. Game: Description of the situation, includes the rules of the game; Players: decision makers in the game; Payos: expected rewards enjoyed at the end of the game Actions: possible choices made by the p
USC - ECON - 537