42 Pages

lecture3

Course: NR 143, Fall 2009
School: Hudson VCC
Rating:
 
 
 
 
 

Word Count: 1917

Document Preview

to Introduction GIS Lecture 3: Part 1. Understanding Spatial Data Structures Part 2. An introduction to the Vector data model Lecture by Austin Troy, University of Vermont Introduction to GIS Part 1. Understanding Spatial Data Structures Introduction to GIS Perception, Semantics, and Space How do we deal with representing semantic constructions of spatial objects, like "mountain,"...

Register Now

Unformatted Document Excerpt

Coursehero >> New York >> Hudson VCC >> NR 143

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.

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.
to Introduction GIS Lecture 3: Part 1. Understanding Spatial Data Structures Part 2. An introduction to the Vector data model Lecture by Austin Troy, University of Vermont Introduction to GIS Part 1. Understanding Spatial Data Structures Introduction to GIS Perception, Semantics, and Space How do we deal with representing semantic constructions of spatial objects, like "mountain," "river," "street," "city," How about representing more conceptual semantic constructions like "temperature," "migration pattern," "traditional homeland," "habitat," "geographic range," etc? Answer: we have various data models which use different abstractions of reality Entities and Fields There are two general approaches for representing things in space: Entities/ Objects: precise location and dimensions and discrete boundaries (remember, points are abstractions). Fields, or phenomena: a Cartesian coordinate system where values vary continuously and smoothly; these values exist everywhere but change over space Introduction to GIS Entities and Boundaries There are two general types of boundaries, bona fide and fiat (D. Mark, B. Smith, A. Varzi) Pure bona fide boundaries represent real discontinuities in the world, like roads, faults, coastlines, power lines, rivers, islands, etc. Pure Fiat boundaries are a human cognitive or legal construction, based on a categorization, such as administrative unit, nation state, hemisphere Some have elements of both, like soil type areas Introduction to GIS Two major data models Entity approach roughly corresponds with the vector model Field approach roughly corresponds with raster model Any geographic phenomenon can be represented with both, but one approach is usually better for a particular circumstance Introduction to GIS Raster Spatial features modeled with grids, or pixels Cartesian grid whose cell size is constant Grids identified by row and column number Grid cells are usually square in shape Area of each cell defines the resolution Raster files store only one attribute, in the form of a "z" value, or grid code. Consider the contrary.... Introduction to GIS Vector Vector layers either represent: Points (no dimensions) Lines, or "arcs" (1 dimension) or Areas, or "polygons" (2 or 3 dimensions) Points are used to define lines and lines are used to scribe polygons Each point line or polygon is a "feature," with its own record and its own attributes Introduction to GIS Raster and Vector representations of the same terrain Raster: great for surfaces Vector: limited with surfaces Introduction to GIS Raster and Vector representations of the same land use Introduction to GIS Raster and Vector representations of the same land use: closer in Introduction to GIS Vector vs. Raster: bounding Raster: bad with bounding Vector: boundary precision Introduction to GIS Vector vs. Raster: Sample points Cancer rates across space Introduction to GIS In Arc View and Arc GIS, we can covert vector layers to grids, based on an attribute, or grids to vector layers Moving between vector and raster The disadvantage of vector to raster is that boundaries can be imprecise because of cell shape Each time you convert, you introduce more error too Introduction to GIS WHEN TO USE RASTER OR VECTOR??? Introduction to GIS Raster data analysis is better for representing phenomena: where boundaries are not precise that occur everywhere within a frame and can be expressed as continuous numeric values where change is gradual across space where the attribute of a cell is a function of the attributes of surrounding cells Introduction to GIS Raster technical advantages : Simple file structure Simple overlay operations Small, uniform unit of analysis Raster technical disadvantages : Big file size, especially for fine-grained data Difficult and error-prone reprojections Square pixels are unrealistic Introduction to GIS Vector analysis is better : Where there are definable regions Where the relative position of objects is important Where precise boundary definition is needed Where multiple attributes are being analyzed for a given spatial object For modeling of routes and networks For modeling regions where multiple overlapping attributes are involved EG: units with man-made boundaries (cities, zip codes, blocks), roads, rivers Introduction to GIS Vector technical advantages : Smaller file size (in general) More graphically interpretable Allows for topology (see further on) Vector technical disadvantages : Complicated file structure Minimum mapping units are inconsistent between overlapping layers Introduction to GIS Specific Vector Usages All legal and administrative boundaries (zip codes, states, property lines, land ownership) Building footprints and 3-D models Roads Bedrock geology Pipelines, power lines, sewer lines Flight paths and transportation routes Coastlines Introduction to GIS Specific Raster Usages Terrain modeling where micro-locational variability is present and matters Groundwater modeling, where surface flow outside of channels is important Representation of slope and aspect Representations of distance and proximity to features Spatial representation of probabilities (logit) Modeling phenomena in nature with continuous spatial variability and numeric attributes, like soil moisture, depth to bedrock, percent canopy cover, vegetative greenness index, species richness index Introduction to GIS Tossups In many cases, though, the choice between raster and vector may not be so clear. Often it depends on the application The following are some examples where you could go either way: Introduction to GIS Soil Soil type: Vector Soil types are meant to represent discrete and homogeneous areas and are qualitative. There is no "slight gradation" between soil types like with pH Soil pH: raster pH is numeric, not categorical, and that number may vary slightly within a single soil type polygon If pH were turned into categories, like High, Medium and Low, vector might be better Introduction to GIS Rivers Most people think of a river as a discretely bounded entity, hence vector What about where the river size fluctuates seasonally, e.g. desert rivers? Or where the location of the river bed changes slowly and gradually the over years Or where the river becomes delta, and the distinction between "river" and "swamp" becomes fuzzy? Or where the river has a certain probability of flowing or being dry at any given location and time Introduction to GIS Rivers Depends on the type of analysis being done With vector can do network modeling of stream and river system, but only in the arcs Vector stream model can take advantage of topologically enabled analysis tools With raster, can do surface flow modeling More realistic, because when it rains water flows everywhere, not just in channels, shows accumulation Think of every piece of land as mini stream channel Introduction to GIS Vegetation Mapping Vector works well for modeling vegetation stand type where categories are broad, e.g. mixed conifer, deciduous hardwood Raster works better where there is micro-locational heterogeneity in species distribution Raster also works better for representing ecotones, or edges between two stands The more specific and variable the classification, the more likely the raster approach will be needed Introduction to GIS Part 2. Brief Intro to the Vector Data Model Introduction to GIS Intro to Vector Recall that there are three basic "feature" or "object" types in the vector data type: Point Arc Polyons In general a given layer holds a given feature type (e.g. "roads" is a line layer, "counties" is a polygon layer, "weather stations" is point) Introduction to GIS Intro to Vector A point layer only consists of a bunch of (x,y) coordiantes In a line (arc) layer, points define lines In a polygon layer, lines define areas Hence each level of vector features builds on the last Introduction to GIS Intro to Vector Each point has a unique location 2 points define a line segment One or several line segments define an arc The endpoints of an arc are "nodes The angle points are "vertices" (sing. Vertex) The feature is the arc, not the line Two arcs meet at the nodes Introduction to GIS Intro to Vector Several arcs can scribe a polygon Polygons are closed regions whose boundaries are made up of line segments connected at many angles. Polygons generally define an area of homogenous phenomena (e.g. forest stand, building, zip code, lake) These phenomena can be described by one or more stored attributes Introduction to GIS Vector Representation:lines Ring: this is a series of line segments (a string) that close upon each other It is NOT a polygon!! The computer does not know that the area inside "belongs" to that object Introduction to GIS Vector Representation:lines A polygon is encoded differently, because the computer "knows" that the areas within those arcs "belongs" to that polygon, while it does not with a ring Introduction to GIS Vector: Topology Topology: spatial relationships between objects are encoded; the spatial location of each point, line and polygon is defined in relation to every other point, line and polygon Topology allows for behaviors of objects in relation to other objects to be defined Topology allows for powerful analysis tools and can significantly reduce error and increase quality Vector files in ARC INFO are topologically encoded. Arc GIS 8.3 geodatabases will be as well. Currently geodatabases are partially topological Introduction to GIS Vector Topology: purpose One of the most important functions of topology is ensuring data quality and "logical consistency" When you bring in line and polygon data from external sources, you will often find errors such as lines (arcs) that dangle or overshoot, polygons that don't close, adjacent polygons that show up as not sharing a border (we'll return to this later in the semester) Introduction to GIS Vector ...

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:

Allan Hancock College - DESC - 3679
DESC9180 Designing Virtual WorldsWeek 3 Session 6pm 9pm Tuesday, August 08, 2006 Ning Gu and Figen GulDESC9180 Designing Virtual WorldsUniversity of Sydney, August 2006Session Overview1. 2. 3. 4.Lecture and discussion: A sense of place a
Allan Hancock College - LGUL - 3679
DESC9180 Designing Virtual WorldsWeek 3 Session 6pm 9pm Tuesday, August 08, 2006 Ning Gu and Figen GulDESC9180 Designing Virtual WorldsUniversity of Sydney, August 2006Session Overview1. 2. 3. 4.Lecture and discussion: A sense of place a
USC - CSCI - 577
Iteration Plan (IP)UNO Web Tool Team no. # 4JingQiao Fu Dushyant Sharma Poorak Kashyap Nishant Sehgal Sachdev Singh Ankit Shah Lin, Xu Chu Amit KhullarProject Manager Requirement Engineer Prototyper Software Architect/ ON-Campus Shaper Life Cycl
USC - CSCI - 577
Life Cycle Plan (LCP)Version 1.0Life Cycle Plan (LCP)EZBay Team 7Prachi Pagey Ian Elston Snehal Vanjari Nupul Kukreja Alok Gurav Gabriel Alcocer Sagar Naware Kevin StigertsPlan and Control engineer Prototyper Requirements Engineer Software A
USC - CSCI - 577
System and Software Architecture Description (SSAD)Version 1.3System and Software Architecture DescriptionTheater Script Online Database Team #16Jae Young Bang Gary Lam Young Chan Noh Ka Ho Au Shi Heng Guan Sandeep Mikkilineni Nory Kealii Nis
USC - CSCI - 577
Life Cycle Plan (LCP)Theater Script Online DatabaseTeam No 16Jae Young Bang Sandeep Mikkilineni Gary Lam Shi Heng Guan Young Chan Noh Ka Ho Au Nory Kealii Nishimura John Christopher Reynolds Julie SanchezProject Manager Operational Concept Eng
USC - CSCI - 577
Operational Concept Description (OCD)Theatre Script Online Database Team# 16Team Members:1) Jae Young Bang 2) Ka Ho Au 3) Shi Heng Guan 4) Young Chan Noh 5) Gary Lam 6) Nory Nishimura 7) John Reynolds 8) Sandeep MikkilineniRoles:Project Manag
USC - CSCI - 577
System and Software Architecture Description (SSAD)Version 6.0System and Software Architecture DescriptionTheater Script Online Database Team #16Jae Young Bang Gary Lam Young Chan Noh Ka Ho Au Shi Heng Guan Sandeep Mikkilineni Nory Kealii Nis
USC - CSCI - 577
Life Cycle Plan (LCP)IGM On-line Art GalleryTeam #:6Team MembersRolesJay Shah Godfrey DukeProject Manager IIV&V/Shaper(Off-campus)/ Requirements Engineer(Off-Campus) Life Cycle Planner System Architect Operational Concept Engineer/Shaper(
USC - CSCI - 577
Operational Concept Designer (OCD)Version 1.3.OPERATIONAL CONCEPT DESCRIPTION (OCD) THE IGM ONLINE ART GALLERY TEAM #6TEAM MEMBERS:1) Jay Shah 2) Ramandeep Singh 3) Amogh Paradkar 4) Shreyas Nangalia 5) Anveshak Akula6) Godfrey DukeProjec
USC - CSCI - 577
Feasibility Evidence Description (FED)Team # 6The IGM on-line Art GalleryTeam Members Jay Shah Godfrey Duke Ramandeep Singh Amogh Paradkar Shreyas Nangalia Anveshak Akula Shivalika Goyal Vyom CaesarRoles Project Manager IIV&V/Shaper(Off- camp
Cal Poly - CS - 6243
The Design and Implementation of the Log File SystemRosenblum & OusterhoutProblem (due to technological advances): CPU rates increase faster than I/O speeds. Programs tend to become I/O bound Solution: Decouple performance of programs from I/OUse
USC - EDUC - 503
Gabriela Ibarra Grade: 9 Time frame: 40 50 minutesLESSON PLAN 2Direct InstructionStandard: 3.0 Literary Response and AnalysisLiterary Criticism Analyze the way in which a work of literature is related to the themes and issues of its historical
Hudson VCC - HIST - 025
SETTING THE STAGE: EUROPE IN THE HIGH MIDDLE AGESEUROPE IN THE HIGH MIDDLE AGESEUROPE @ 1300 ADEUROPE IN THE HIGH MIDDLE AGESSOCIAL & POLITICAL STRUCTURE FEUDALISM Lords Vassals Clergy Serfs TownspeopleEUROPE IN THE HIGH MIDDLE AGESEC
Hudson VCC - HIST - 138
THE ESTABLISHMENT OF SOVIET POWERLenin proclaims power in the name of the SovietsTHE ESTABLISHMENT OF SOVIET POWER The First Steps "Land, Bread, and Peace" Peace = top priority Treaty of Brest-Litovsk, Feb. 1918THE ESTABLISHMENT OF SOVIET PO
USC - CSCI - 577
Packaged Tools and ProceduresOnline Reading Assessment (ORA)Team 2NameMatthew Rettagliata Randal Romell Carol Tauro Akash Agarwal Tristan Urquico Lorenz Verzosa Jonathan Wright Yi WangRoleSystem & Software Architecture Description System &
Lynchburg College - PUBLIC - 102
Your TitleYour Name Environmental Science 102L Daphnia Lab Report May 18, 2009 IntroductionHypothesisMaterials and MethodsResultsDiscussionLiterature Cited1
Hudson VCC - NR - 254
Community Forestry: At home and Abroad - NR 254/ENVS 196 Spring 2002 Prof. Cecilia Danks Forest bureaucracies - lecture notes 1. Characteristics of a bureaucracy a. Max Weber "father of modern sociology" i. writing in late 1800s-early 1900s - German
USC - CSCI - 577
TEAM 19Period: 10/02/05 10/08/05WEEKLY STATUS REPORTTeam 19 eBay Notification System Week 4 Progress 1. 2. 3. Weekly meetings everyday after class for at least an hour. Our third teleconference with our remote client on Friday, 7th October, 2005
Hudson VCC - DSPACE - 3976
License granted by David Heleba (david.heleba@uvm.edu) on 2005-01-14T21:30:07Z (GMT):NOTE: PLACE YOUR OWN LICENSE HEREThis sample license is provided for informational purposes only.NON-EXCLUSIVE DISTRIBUTION LICENSEBy signing and submitting t
Hudson VCC - DSPACE - 5130
License granted by David Heleba (david.heleba@uvm.edu) on 2005-01-28T20:29:29Z (GMT):NOTE: PLACE YOUR OWN LICENSE HEREThis sample license is provided for informational purposes only.NON-EXCLUSIVE DISTRIBUTION LICENSEBy signing and submitting t
USC - CSCI - 577
System and Software Architecture Description (SSAD)Data Mining PubMed ResultsTeam 5Team Members PROJECT MANAGER: CONCEPT ENGINEER: REQUIREMENTS ANALYST: ARCHITECT: LIFE CYCLE PLANNER: PROTOTYPE DEVELOPER: IV&V: IV&V: Srikanth Ranganamyna Dinesh
USC - CSCI - 577
Response to AAR_FRD_IIVV_LCODraft_F07a Team 18 EZSIM II Team Members Arpit Shah Nirav Shah Chintan Rita Amap Bhat Harita Bhavsar Nitin Gupta Dinesh Iyer Project Manager System Requirement Analyst UML Modeler System Architect Prototype Developer Feasi
USC - CSCI - 577
LCOPackage_Evaluation_LCO_F07a_T18Version 2.0Evaluation of LCO Package for EZSIM II ProjectProject Done by Team 18 Review Done by Chintan Rita, QFP Review Submitted on November 5th 2007Introduction This document contains the independent eva
USC - CSCI - 577
RLCOPackage_Evaluation_QFP_F07a_T18Version 4.0Evaluation of RLCO Package for EZSIM II ProjectProject Done by Team 18 Review Done by Chintan Rita, QFP Review Submitted on December 17th 2007Introduction This document contains the evaluation o
USC - CSCI - 577
Supporting Information DocumentVersion # 1.0USC CSCI577a CourseSupporting Information Document (SID)2007ArpitKumar Shah Nirav Shah Chintan Rita Amap Bhat Harita Bhavsar Nitin GuptaSID_LCO_F07a_T18_v1.0Project Manager Requirement Analyst
USC - CSCI - 577
Evaluation of Initial Prototype for EZSIM II ProjectProject Done by Team Review Done by Dinesh18 12th 2007Somasundaram Iyer, SRE & ShaperReview Submitted on OctoberIntroduction This document contains the independent evaluation of the prototy
USC - CSCI - 577
Supporting Information Document (SID)Conference Room Reservation SystemTeam 14Team members and roles Vishal Gupta Project Manager Rishabh Nanda - Concept Engineer Preeti Powar Business Analyst, Assistant Shaper Deepak Gupta System Architect
USC - CSCI - 577
Team 16November 28th, 2007CSCI 577aSoftware Engineering I University of Southern CaliforniaProject 16 EMentoringTeam Assignment Client Meeting Report# 11November 28 , 2007thSubmitted By:1Team 16November 28th, 2007Team 16Project N
USC - CSCI - 577
System Design and Architecture Team has established a complete system architecture consisting of needed modules, business logic and interface components. All actors or operational stakeholders needed for the system are identified UML use cases and
USC - CSCI - 577
Software And System Architecture Document (SSAD) Software And System Architecture Description (SSAD)Version 1.0NEW Economics for WomenTeam number 11NAME Raghava Aditya Ravula Tejaswi Chadalavada Swarag Segu Adil Fulara Nitin Bandi Veena Movva
USC - CSCI - 577
Supporting Information Document (SID)NEW ECONOMICS FOR WOMENTeam No: 11Team members and roles Name Raghava Aditya Ravula Tejaswi Chadalavada Nitin Bandi Adil Fulara Veena Movva Swarag Segu Role Project Manager & SSRD & Meeting Facilitator OCD P
USC - CSCI - 577
Software And System Architecture Document (SSAD) Software And System Architecture Description (SSAD)Version 1.2NEW Economics for WomenTeam number 11NAME Raghava Aditya Ravula Tejaswi Chadalavada Swarag Segu Adil Fulara Nitin Bandi Vee
USC - CSCI - 577
Quality Management Plan (QMP)ECLIPSE BASED COCOMO IITeam number 12Alexander Mathew Girija Goleria Pawan Chandak Gaurav Badlaney Bankim Bhalaria Tanya Jacob Christopher Higginbotham Michael MedvedProject Manager, Prototype Life Cycle Plan Oper
USC - CSCI - 577
Christopher Higginbotham CSE iCard# F06-15 Team #12 25 Sep 2006Evaluation of WinWin NegotiationWin Cond ition Num ber W88 W73 Proble m(s) Why there is a problem How to fix it Catego rized correctl y Yes Yes If no, correct categor yW73Unclear S
Virginia Tech - CALS - 1126
Community-based Wetland Co-Management in Bangladesh IntroductionIn an attempt to find new solutions to problems resulting from top-down approaches to resource conservation and sustainability, community-based co-management over an entire wetland ecos
Virginia Tech - CS - 5314
ASCL Another Simple Calculator LanguageRyan Blace Spring 2007Outline Review of requirements Quick introduction to ASCL Features and examples Design and implementation details References that were used in development ConclusionReview of Re
USC - CSCI - 577
CS577A LCA Draft Evaluation CS577A LCA Draft Evaluation Team 1 Quality Management Information System IV&V Reviewer: Anuradha Kallury Date: 12/01/04 Part A: Management OverviewAnuradha KalluryThe following is a list of features in the solution th
USC - CSCI - 577
Feasibility Rationale Description (FRD)Conference Room Reservation SystemTeam 14Team Members: Vishal Gupta Project Manager, Feasibility Analysis Rishabh Nanda - Operational Concept Preeti Powar - Analyst, Assistant Shaper Deepak Gupta - System
USC - CSCI - 577
Survey on COTS Integration Issues1. Team Number: 1 2. Is your system largely dependent on COTS products? _ Yes _X_ No 3. How many COTS products does your team utilize (include operating systems)? _X_ 4. List the members of your team, their roles, e
USC - CSCI - 577
PROJECT #1 BOX-OFFICE DATABASE SYSTEM (BODS) CLIENT MEETING REPORT #3DATE VENUE START TIME: 26TH SEPTEMBER, WEDNESDAY : 24TH STREET THEATER : 4:00 PMMEETING ATTENDEES: SHIVANG PATEL : PROJECT MANAGER AND SSAD SIDDHARTHA SHAH : OCD (ASST. Shaper
USC - CSCI - 577
CSCI 577a Team 16 System and software requirement report Version 1.1System and Software Requirements Definition (SSRD)Family and Homeless Well Being ProjectTeam No 6Alexander Sharma - Project Manager/ Life cycle planner Amit Mange Hemali Shah
Cal Poly Pomona - CHEM - 160
TWO-DIMENSIONAL NMR SPECTROSCOPY Goal: The goal of this experiment is the determination of the covalent structure and if the data permit the conformation of an organic compound. NMR methods will be used but the mass spectrum will also be measured as
Hudson VCC - NR - 250
NR 250 Limnology Laboratory 7: Algae Reporting Form A. Algae Viewing Attach a sheet or two of paper with drawings and names if you like. This may be easier if you don't know the divisions right away. Or you can use the space here. 1. A cyanobacterium
USC - CSCI - 577
Iteration Plan (IP)Theater Script Online DatabaseTeam No 16Iteration Plan (IP)Version 9.0Jae Young Bang Gary Lam Young Chan Noh Ka Ho Au Shi Heng Guan Nory Kealii Nishimura Julie SanchezNon-technical Lead Tester/ Technical Lead System Arc
USC - CSCI - 577
TEAM#16-CLIENT MEETING NOTESDATE: 03/ 09 /2009 VENUE: SAL START TIME: 1:00 PM PST ATTENDEES: Ms. Julie Sanchez(Client) Mr. Jae young Bang(Project Manager) Mr. Gary Lam(System Requirement Engineer)Following is the observations made by the team memb
USC - CSCI - 577
TEAM#16-CLIENT MEETING NOTESDATE: 04/ 08 /2009 VENUE: SAL START TIME: 3:00 PM PST ATTENDEES: Ms. Julie Sanchez(Client) Mr. Jae young Bang(Project Manager)Following is the observations made by the team member attended the meeting: Mr. Jae young Ban
USC - CSCI - 577
Team 16: Code Count Report The method employ to count is using Unified Code Count which was download from the course website. The languages we used are: JAVA, JSP, CSS, HTML (embedded), SQL and JAVASCRIPT.Count by modules: Module Search* User Inter
USC - CSCI - 577
Project #8: AAA Petal Pushers Remote R&D Client Meeting Note #1 Date Venue Start time N/AThere is no client meeting for this week (01/28/09 - 02/04/09)N/A N/AAdjourn TimeN/A
USC - CSCI - 577
Supporting Information Document (SID)Theater Script Online Database Team #16Jae Young Bang Gary Lam Young Chan Noh Ka Ho Au Shi Heng Guan Nory Kealii Nishimura Julie SanchezNon-technical Lead Tester/ Technical Lead System Architect/Builder Buil
USC - CSCI - 577
Operational Concept Description (OCD)Theatre Script Online DatabaseTeam# 16Team Members:1) Jae Young Bang 2) Ka Ho Au 3) Shi Heng Guan 4) Young Chan Noh 5) Gary Lam 6) Nory NishimuraRoles:Project Manager / Non-tech Lead / Developer Prototyp
USC - CSCI - 577
Life Cycle Plan (LCP)Theater Script Online DatabaseTeam No 16Jae Young Bang Gary Lam Shi Heng Guan Young Chan Noh Ka Ho Au Nory Kealii Nishimura Julie SanchezNon-technical Lead/Builder Tester/Technical Lead Planning and Control Engineer System
USC - CSCI - 577
Feasibility Evidence Description (FED)Theater Script Online Database Team No 16Jae Young Bang Gary Lam Young Chan Noh Ka Ho Au Shi Heng Guan Nory Nishimura Julie SanchezProject Manager / Non-tech Lead / Developer Requirements Engineer / Tech Lea
USC - CSCI - 577
Quality Management Plan (QMP)Theater Script Online DatabaseTeam No 16Quality Management Plan (QMP)Version 9.0Jae Young Bang Gary Lam Young Chan Noh Ka Ho Au Shi Heng Guan Nory Kealii Nishimura Julie SanchezNon-technical Lead Requirements
USC - CSCI - 577
System and Software Architecture Description (SSAD)Version 9.0System and Software Architecture DescriptionTheater Script Online Database Team #16Jae Young Bang Gary Lam Young Chan Noh Ka Ho Au Shi Heng Guan Nory Kealii Nishimura Julie Sanchez
USC - CSCI - 577
Proposal for Ada to AADL TranslatorFeasibility Rationale Description(FRD)Team# 18Team Members DeWitt Latimer IV Mridu Sethi Nidhi Gulati Sapan Lalani Suprabha Ray Swapnil Patel Vijay KakadiaIndependent Verification & Validation System and Soft
USC - CSCI - 577
Project DetailDue : Monday, December 15, 2008 at 11:59 PM Submission : Post the file under Final Deliverables page in your team website File name : ProjectDetail_20083_Txx.doc (xx is your team no.) -Instruction: Fill in this form. Make sure that the
USC - CSCI - 577
System and Software Requirements Definition (SSRD)Theater Script Online DatabaseTeam No 16Jae Young Bang Gary Lam Young Chan Noh Ka Ho Au Shi Heng Guan Sandeep Mikkilineni Nory Kealii Nishimura John Christopher Reynolds Julie SanchezProject M
USC - MEDIA - 1105
<!DOCTYPE html PUBLIC "-/W3C/DTD XHTML 1.0 Strict/EN" "http:/www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http:/www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head> <title>Changeset 1105 for tools/DotSceneLoaderTemplate/media/
USC - MISC - 2438
<!DOCTYPE html PUBLIC "-/W3C/DTD XHTML 1.0 Strict/EN" "http:/www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http:/www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head> <title>Changeset 2438 for ogre/Tests/OgreMain/misc/ArchiveTes
USC - MISC - 2438
<!DOCTYPE html PUBLIC "-/W3C/DTD XHTML 1.0 Strict/EN" "http:/www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http:/www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head> <title>Changeset 2438 for ogre/Tests/OgreMain/misc/ArchiveTes