33 Pages

session15KR

Course: CSCI 561, Summer 2008
School: USC
Rating:
 
 
 
 
 

Word Count: 1742

Document Preview

Representation Knowledge Knowledge engineering: principles and pitfalls Ontologies Examples CS 561, Sessions 14-15 1 Knowledge Engineer Populates KB with facts and relations Must study and understand domain to pick important objects and relationships Main steps: Decide what to talk about Decide on vocabulary of predicates, functions & constants Encode general knowledge about domain Encode...

Register Now

Unformatted Document Excerpt

Coursehero >> California >> USC >> CSCI 561

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.
Representation Knowledge Knowledge engineering: principles and pitfalls Ontologies Examples CS 561, Sessions 14-15 1 Knowledge Engineer Populates KB with facts and relations Must study and understand domain to pick important objects and relationships Main steps: Decide what to talk about Decide on vocabulary of predicates, functions & constants Encode general knowledge about domain Encode description of specific problem instance Pose queries to inference procedure and get answers CS 561, Sessions 14-15 2 Knowledge EngineerRunway Safety/Runway Incursion Decide what to talk about Airport, planes, risks, mitigations Decide on vocabulary of predicates, functions & constants Encode general knowledge about domain Circles and Arrows Taxonomy in PowerLoom Rules describe the inferential knowledge "If the pilot is much more senior than the copilot, there is a risk that the copilot will be intimidated." "If the plane is fully loaded with fuel, its takeoff distance is increased." Modeling the Tenerife Disaster Encode description of specific problem instance Pose queries to inference procedure and get answers "Real time" play of events to get: {(risk1 (mit11..mit1n)) (risk2 (mit21..mit2m))...} How do you sort the risks and sort the mitigations with the risk????? CS 561, Sessions 14-15 3 Knowledge engineering vs. programming 1. 2. 3. 4. Knowledge Engineering Choosing a logic Building knowledge base Implementing proof theory Inferring new facts Programming Choosing programming language Writing program Choosing/writing compiler Running program Why knowledge engineering rather than programming? Less (Different?) work: just specify objects and relationships known to be true, but leave it to the inference engine to figure out how to solve a problem using the known facts. [Capture the Domain] CS 561, Sessions 14-15 4 Properties of good knowledge bases Expressive What can you say? Concise How hard is it to say something? Contextinsensitive Can you represent many domains? Unambiguous Effective Clear Correct ... Tradeoffs: e.g., sacrifice some correctness if it enhances brevity. PowerLoom, Prolog, Owl, RDF all offer different features (Mostly speed v. completeness v. expressivity) CS 561, Sessions 14-15 5 Efficiency Ideally: Not the knowledge engineer's problem To me efficiency is the wrong question. Can you make anything work at all? Can you capture all the "knowledge" in a domain so that you can compute with it? Can the solution be easily maintained? Can the solution be used in planning as well as diagnosis? CS 561, Sessions 14-15 6 Pitfall: design KB for human readers KB should be designed primarily for inference procedure! e.g.,VeryLongName predicates: BearOfVerySmallBrain(Pooh) does not allow inference procedure to infer that Pooh is a bear, an animal, or that he has a very small brain, ... Rather, use: In other words: BearOfVerySmallBrain(pooh) = x(pooh) Bear(Pooh) b, Bear(b) Animal(b) a, Animal(a) PhysicalThing(a) ... [See AIMA ch. 10 for many examples] CS 561, Sessions 14-15 7 Debugging In principle, easier than debugging a program, because we can look at each logic sentence in isolation and tell whether it is correct. [Beware of subtle interactions, but code has this problem as well.] Example: x, Animal(x) b, BrainOf(x) = b means "there is some object that is the value of the BrainOf function applied to an animal" and can be corrected to mean "every animal has a brain" without looking at other sentences. CS 561, Sessions 14-15 8 Ontology Collection of concepts and interrelationships Widely used in the database community to "translate" queries and concepts from one database to another, so that multiple databases can be used conjointly (database federation) CS 561, Sessions 14-15 9 Ontology Example Khan & McLeod, 2000 CS 561, Sessions 14-15 10 A Government Ontology State hasP hasB People Sovereign State Nation State Anarchy hasRules for Boundary Sovereignty via hasS hasS Political Sovereignty via Economic Sovereignty via System Religious System No Rules People Political System hasRules of by for Economic System Free Market implements Socialism implements Marxism Oligarchy Democracy of by for Monarchy for of by Royal Family of by Small Group Capitalism (Adam Smith) Hybrid Economy Theocracy of by for People Constitutional Democracy hasRules "Good" Communism for Religious Leaders People Totalitarian People "Bad" Communism Oligarchy for of by of by Law Family of by for Dictatorship of by for Political Leaders of by for Parents Family Members Dictator Communist Party For details about the United States instances, see last page. Russia Under Lenin was a Nation State whose Political and Economic Sovereignty was via Good Communism Russia Under Stalin was a Nation State whose Political and Economic Sovereignty was via Bad Communism CS 561, Sessions 14-15 11 Towards a general ontology Develop good representations for: categories measures composite objects time, space and change events and processes physical objects substances mental objects and beliefs ... CS 561, Sessions 14-15 12 Representing Categories (or Concepts) We interact with individual objects, but... much of reasoning takes place at the level of categories. Representing categories in FOL: use unary predicates in a table form (small set of objects) e.g., Tomato(x) based on its properties reification: turn a predicate or function into an object e.g., use constant symbol Tomatoes to refer to set of all tomatoes "x is a tomato" expressed as "xTomatoes" Strong property of reification: can make assertions about reified category itself rather than its members e.g., Population(Humans) = 5e9 Allows us to easily reason about categories. CS 561, Sessions 14-15 13 Categories: Allow inheritance to organize and simplify knowledge base e.g., if all members of category Food are edible and Fruits is a subclass of Food and Apples is a subclass of Fruits then we know (through inheritance) that apples are edible. Taxonomy: hierarchy of subclasses Because categories are sets, we handle them as such. e.g., two categories are disjoint if they have no member in common a disjoint exhaustive decomposition is called a partition etc... CS 561, Sessions 14-15 14 Example: Taxonomy of hand/arm movements Hand/arm movement Gestures Manipulative Acts Mimetic Deictic Communicative Symbols Referential Modalizing Unintentional Movements Quek,1994, 1995. CS 561, Sessions 14-15 15 Classification In FOL all facts and rules are simply thrown into the mix. No organization. In taxonomic hierarchies there is obviously some organization. Classification, a type of inference, is possible. Watch the classification movie. http://www.isi.edu/isd/LOOM/loomclassifier.mov CS 561, Sessions 14-15 16 Measures Can be represented using units functions e.g., Length(L1) = Inches(1.5) = Centimeters(3.81) Measures can be used to describe objects e.g., Mass(Tomato12) = Kilograms(0.16) Caution: be careful to distinguish between measures and objects e.g., b, bDollarBills CashValue(b) = $(1.00) CS 561, Sessions 14-15 17 Composite Objects One object can be part of another. PartOf relation is transitive and reflexive: e.g., PartOf(Bucharest, Romania) PartOf(Romania, EasternEurope) PartOf(EasternEurope, Europe) Then we can infer Part Of(Bucharest, Europe) [An example of a backward chaining rule] Composite object: any object that has parts CS 561, Sessions 14-15 18 Composite Objects (cont.) Categories of composite objects often characterized by their structure, i.e., what the parts are and how they relate. e.g., a Biped(a) ll, lr, b Leg(ll) Leg(lr) Body(b) PartOf(ll, a) PartOf(lr, a) PartOf(b, a) Attached(ll, b) Attached(lr, b) ll lr x Leg(x) PartOf(x, a) (x = ll x = lr) [Problems: How about a onelegged biped? Such description can be used to describe any objects, including events. We then talk about schemas and scripts. CS 561, Sessions 14-15 19 Events Chunks of spatiotemporal universe (space and time) [see. p. 336] e.g., consider the event WorldWarII. It took place in some "place" during some "time" it has parts or subevents: SubEvent(BattleOfBritain, WorldWarII) it can be a subevent: SubEvent(WorldWarII, TwentiethCentury) Intervals: events that include as subevents all events occurring in a given time period (thus they are temporal sections of the entire spatial universe). Cf. situation calculus: fact true in particular situation event calculus: event occurs during particular interval CS 561, Sessions 14-15 20 Events (cont.) Places: spatial sections of the spatiotemporal universe that extend through time Use the predicate In(x) to denote subevent relation that holds when one event's spatial projection is part of another's: e.g. In(NewYork, USA) Location function: maps an object to the smallest place that contains it: x,l Location(x) = l At(x, l) ll At(x, ll) In(l, ll) CS 561, Sessions 14-15 21 Times, Intervals and Actions Time intervals can be partitioned between moments (=zero duration) and extended intervals: Absolute times can then be derived from defining a time scale (e.g., seconds since midnight GMT on Jan 1, 1900) and associating points on that scale with events. The functions Start and End then pick the earliest and lates...

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:

USC - CSCI - 588
Mobile Business Finder (MBF) CS588 - Team 18 CampusShaozheng jia (ID 7064) Chung-hua Chang (ID 0664 ) Shing-cheng Chen (ID 7525) 1Project DescriptionPurpose:The Mobile Business Finder (MBF) is a tool for mobile phone users. With the M
USC - CSCI - 588
N.G.G.C A gaming console which can be used as a generic multimedia device It has different built in modes such as the COMPUTER MODE, THE SET-TOP BOX MODE etc in which it can be used The basic concept here being that we can have a single device con
USC - PHAR - 432
MANAGED CARE AND PBM SALES AND MARKETINGMARCH 19, 1998 USC PHARMACY SCHOOLDISCUSSION TOPICSManaged Care/ PBM Background Marketing and Sales- is there a difference? Market Drivers- Opportunity Analysis Market Players PBM Market Segments Deter
USC - PHAR - 319
From jmccombs@hsc.usc.edu Fri Sep 11 08:21:35 1998Subject: Re: Quiz 1>Dear Professor McCombs,>>My name is Monica Malhotra and I am in your Pharmacy Literature Review and>Statistical Analysis. I have gone through the articles and have been>tr
USC - CS - 377
IntroductionqqGetting started with software engineering Objectives To introduce software engineering and to explain its importance To set out the answers to key questions about software engineeringSommerville 2000, Medvidovic 2006Introduct
USC - CS - 589
Adaptive dependability Authors: P. Narasimhan ,T.A.Dumitras, A.M. Paulos, S.M. Pertet, C.F. Reverte, J. G. Slember and D. Srivastava Presented by Tarun Nainani Middleware for Embedded MEAD Overview Introductio
USC - CS - 577
Project NameRegression Test PackageVersion: 1.0Developers Team xx Team MembersRegression Test PackageVersion1.0[This page has been intentionally left blank]2Regression Test PackageVersion1.0Table of Contents1 INTRODUCTION..5 1.1
USC - CS - 577
Benefits of using development toolsPresented by Jonathan Ng 577b Spring 2005What is development tools? A program or application that software developers use to create, debug, or maintain other programs and application Different forms
USC - CS - 577
CS577B Spring 2005 IV&V Homework TRR Package EvaluationDue May 4, 2005, 5:00pm 30 pointsContact Person Keun Lee (keunlee@sunset.usc.edu) for questions concerning the checklists or the ARR process Contact Alex Lam (alexankl@usc.edu) for all other q
USC - CS - 577
Team Assignment "OCD Early Sections(20)"Due Sep. 24, 2003This assignment is a companion to the first Quality Report, "QR1(10)". You can't correctly complete this assignment without doing BOTH. This assignment requires additional quality reporting
USC - CS - 577
USCUniversity of Southern CaliforniaC S ECenter for Software EngineeringCS577a3 Software Engineering I Special AnnouncementsA Winsor Brown Ashish Soni Sept. 22, 2003Sep. 22, 2003 v1USC-CSE1USCUniversity of Southern CaliforniaC S E
USC - CS - 577
X-Apparently-To: wishih@yahoo.com via web20201.mail.yahoo.com; 05 Dec 2001 14:10:40 -0800 (PST) X-RocketRCL: 7407;1;1673738157 X-Track: 1: 40 Date: Wed, 05 Dec 2001 16:13:08 -0600 From: Scott Henninger <scotth@cse.unl.edu> X-Mailer: Mozilla 4.7
USC - CS - 577
Meeting Agenda & Minutes (02/07/02 6:00 PM - 8:00 PM)-From Last Meeting:ALL: Homework for next Wednesday. Please send me a copy on Thursday of next week. - N/APallavi: Continue work on SSAD. Get most updates completed ASAP.Antonia: Finis
USC - CS - 577
From: mklug [mklug@usc.edu]Sent: Wednesday, March 20, 2002 11:15 AMTo: Paul SitkoCc: csci-577b-trw@yahoogroups.comSubject: RE: [CSCI-577b-TRW] CORRECTION! CCD Time and Place.Paul,The system has not been tested for multiple project support yet
USC - CS - 577
Meeting Agenda & Minutes (04/07/02 5:00 PM - 6:30 PM)-From Last Meeting:ALL: All transition drafts need to be ready for release on 04/07/02.Lucy: Complete development related to IV&Ver defects by 04/07/02. - Done.Pallavi: Complete develop
USC - CS - 577
Wilson Dental Library New Book ListTransition PlanApril 18, 2002 Milestone: IOC Working Set n (n=2) Version: 1.2ClientFrank Mason John GlueckertDevelopers CS 577bJesal Bhuta Suim Hurr Wenkuang Chang Bezu Arega Team Leader, Configuration Manage
USC - CS - 577
/team7b/RLCA/Plans/Transition_Plans_S02b_T7b.doc. Transition Plan Transition_Plans_S02b_T7b.pdf. Transition Plan Support_Plans_S02b_T7b.doc. Support PlanSupport_Plans_S02b_T7b.pdf. Support Planare not available as they were not written yet duri
USC - CS - 577
/team7b/SupportSet/PRR/There is no presentation slides for PRR.
USC - CS - 577
Client MeetingDate: 01/25/2002Location: Leavey 122Participants: Professor Boehm, Candy, Steve, Team 8&11Notes:1. Testing : Blackboard, iPlanet, journyx2. How to decrease the coupling between two teams: project management, collaborative serv
USC - CS - 577
To: Scott Henninger <scotth@cse.unl.edu>Subject: BORE 4.x.x Client - Defect (Save function in Case Editor not working)Cc: Vivian Nguyen <minhhan@hotmail.com> Scott,One of my users (Vivian) was working on the BORE system and was modifying a c
USC - CS - 577
Date: Thu, 14 Mar 2002 09:02:02 -0600 From: Scott Henninger <scotth@cse.unl.edu> X-Mailer: Mozilla 4.73 [en]C-{C-UDP; EBM-SONY1} (Windows NT 5.0; U) X-Accept-Language: en To: Katherine Cheung <kkc@usc.edu>, Jason Lesh <jlesh@usc.edu>, B
USC - EDUC - 205
1CTSE 205 Child Development and Learning (3) Rossier School of Education University of Southern California Spring Semester 2006 Class Meetings: TU & TH. 12:30-2:00 WPH 107 Jennifer Welsh, Instructor jwelsh@usc.edu Monica Miller, Teaching Assistant
USC - CSCI - 577
USCC S EUniversity of Southern CaliforniaCenter for Software EngineeringSSRD & (Intro to) OOADEd Colbert CS577a Fall 2005September 21, 2005USCC S EUniversity of Southern CaliforniaCenter for Software EngineeringPre-Class Reading
USC - CSCI - 577
USCC S EUniversity of Southern CaliforniaCenter for Software EngineeringValue-Based Review- Independent Verification & Validation (IV&V)9/16/2005 Keun Lee USC CSE(keunlee@sunset.usc.edu)USCC S EUniversity of Southern CaliforniaCen
USC - CSCI - 577
USCC S EUniversity of Southern CaliforniaCenter for Software EngineeringIncremental Commitment Model (ICM)* for SoftwareA Winsor Brown and Barry Boehm, USC CS 577a Lecture Fall 2008 * NOTE: Check the handouts page for this lecture and 8/27/0
USC - CSCI - 577
University of Southern CaliforniaCenter for Systems and Software EngineeringThe Future of Software ProcessesCS 577a November 3, 2008 Barry Boehm11/03/081University of Southern CaliforniaCenter for Systems and Software EngineeringOutlin
USC - CSCI - 577
University of Southern CaliforniaCenter for Systems and Software EngineeringUSC e-Services Software Engineering ProjectsBarry Boehm, Winsor Brown, Sue Koolmanojwong ,Di Wu, Pongtip Aroonvatanaporn, Itti Charoenthongtrakul, Raed ShomaliUSC Cent
USC - CSCI - 577
Software Engineering and TRIZ Application of TRIZ to Software Design PatternsIndividual Research Presentation Unnati Sethi Wednesday April 11th, 2007Agenda What is TRIZ? Software Engineering reviewed with TRIZ Feedback from s/w engg to T
USC - CSCI - 577
Requirements Engineering in Public SafetyPatrick StevensRequirements for Public Safety Systems What is Requirements Engineering? Specific to Public Safety Public as a Stakeholder Availability Response time Accuracy ConsistencyAvailabilit
USC - CSCI - 577
Requirement Analysis- Alexander Prince MathewWhat are requirements ? Clients visualization of the product Best depicts the purpose of the product Set of features which can be bundled Ensure forward/backward compatibility Features which define
USC - CSCI - 577
CVS InstructionsBelow are instructions for using CVS. You can access CVS using WinCVS, Eclipse, or by logging into greenbay. There are more ways to access CVS, but this document doesn't cover them. Note: Your team repository will be on the greenbay
USC - CSCI - 577
Product Delivery & Client Acceptance 20 Points Due May 3, 2007 - Identify all files, documents delivered to client with version number - Identify what acceptance tests were run and their results (by reference) - List all open problems/issues - Fill o
USC - CSCI - 577
EasyWinWin Negotiation ScheduleLast Updated @ Sep 16th, 2005 12:37amSAL 322Wed 9/14 9:00am - 11:20am 11:30am -1:50pm 2:00pm - 3:30pm 3:30pm - 5:50pm 9:00am - 11:20am 11:30am - 1:50pm 2:00pm - 3:30pm 3:30pm - 5:50pm CLASS Mon 9/19 Team 23 - First T
USC - CSCI - 577
CSCI 577a, Fall 2009 Reviewing IV&V Evaluations for LCO Draft Due Date: October 28, 2005 2:05pm 10 points Contact csci577@usc.edu with your questionsAssignment Instructions: You should have received a concern log from your IV&Vers documenting the c
USC - CSCI - 577
CSCI 577a, Fall 2009 LCA Draft on the WebDue: 11/21/2005 2:00pm 20 pointsAssignment Instructions: For this assignment, the following documents must be posted on-line at the team website following the structure defined in the Archiving guidelines.
USC - CSCI - 577
LCA ARB PresentationTeam 19: eBay Notification SystemTeam Members Rahul Vaid FRD Rosalia Jose OCD Di Wu SSRD Joseph Hsu SSAD Brad Woodward SSAD / LCP Amer Malik Prototyping Arpitha Hegde - LCPOperational Concept DescriptionPresented By :Ro
USC - CSCI - 577
System and Software Architecture Description (SSAD)eBay Notification SystemTeam 19Rahul Vaid Project Manager / FRD Rosalia Jose OCD Wu Di SSRD Joseph Hsu SSAD Brad Woodward UML Modeling Amer Malik Prototype Arpitha Hegde Software Develop
USC - CSCI - 577
TEAM 19Period: 10/16/05 10/22/05WEEKLY STATUS REPORTTeam 19 eBay Notification System Week 6 Progress 1. 2. We completed our LCO Package. One of our team members, Brad Woodward had a one on one conversation with our client, Dave to discuss the 2n
USC - CSCI - 577
System and Software Architecture Description (SSAD)eBay Notification SystemTeam 19Rahul Vaid Project Manager Rosalia Jose Tester and Prototype Wu Di Requirements Analyst Joseph Hsu Software Architect Brad Woodward Life Cycle Planner Amer M
USC - CSCI - 577
Client Meeting Notes #7 6th Telephone Conversation with DaveConversation Minutes10/28/2005Dave wanted all of us to be present, but because of a few problems only the following people were present for the TELECON. Rahul Vaid Di Wu Amer Malik Jose
USC - CSCI - 577
EasyWinWin Report Team 1Rusha Mistri Amit Parikh Premal Shah Yauvan Suba Gaurav Dalal Jitin Khurana1. Identifying Stakeholders:The key stakeholders who participated in the EasyWinWin negotiations were: 1. Erin Shaw - Customer 2. Rusha Mistri - P
USC - CSCI - 577
System and Software Requirements Definition (SSRD)Intelligent CodeCount SuperstructureTeam 16Lead - Robert F. Huber Operation Concept - Sunil C. Raga System Architect - Thomas Ackenhausen Proto-typist - David Naumann UML Modeler - Kevin Sigmund
USC - CSCI - 577
Life Cycle Plan (LCP)Intelligent CodeCount SuperstructureTeam 16Lead - Robert F. Huber Operation Concept - Sunil C. Raga System Architect - Thomas Ackenhausen Proto-typist - David Naumann UML Modeler - Kevin Sigmund IV&V - Joe Vahabzad IV&V - Br
USC - CSCI - 577
Meeting # 1Day Time Number of people who attended the meeting Place of meeting Client Team Member who attended this meeting 9/16/05 11:30AM - 1:30PM 7 RTH Ms. Julie Kwan Srikanth Ranganamyna Dinesh Siddhareddy Eric Johnson Kris Wiseley Christina Kha
USC - CSCI - 577
Operational Concept Description (OCD)PubMed Data AnalyzerTEAM 5TEAM MEMBERS PROJECT MANAGER: CONCEPT ENGINEER: REQUIREMENTS ANALYST: ARCHITECT: LIFE CYCLE PLANNER: PROTOTYPE DEVELOPER: IV & V: IV & V: Srikanth Ranganamyna Dinesh Siddhareddy Eri
USC - CSCI - 577
System and Software Requirements Definition (SSRD)Data Mining PubMed ResultsTeam 5Team Members PROJECT MANAGER: CONCEPT: REQUIREMENT: ARCHITECT: PLAN: PROTOTYPE: IV&V: IV&V: Srikanth Ranganamyna Dinesh Siddhareddy Eric Johnson Kris Wiseley Chris
USC - CSCI - 577
Life Cycle Plan (LCP)Data Mining PubMed Results Team 5TEAM MEMBERS PROJECT MANAGER: CONCEPT: REQUIREMENT: ARCHITECT: PLAN: PROTOTYPE: IV & V: IV & V: Srikanth Ranganamyna Dinesh Siddhareddy Eric Johnson Kris Wiseley Christina Khachatryan Sri Ram
USC - CSCI - 577
CS 577b Student PresentationTestingPresented by: Randal RomellCommon TerminologiesAgile Manifesto - "eXtreme ." - "Pair ."- "eXtreme Testing" a.k.a - "Pair testing"How eXtreme is eXtreme testing?Is it much more stressful that stress testi
USC - CSCI - 577
Software Architectures in RoboticsVannak Touch Objective Cool robotic video and pictures Common software architectures for robotic Selection criteria for architectures Conclusion Robotic Software Architectures Deliberati
USC - CSCI - 577
Quality Focal Point DefinitionQuality Focal Point (QFP) Definition(s).I from LCP 3.2 Development ResponsibilitiesQuality Focal Point: Preparing and running independent testing (plans, cases); takes responsibility for the quality of the product an
USC - CSCI - 577
USCC S EUniversity of Southern CaliforniaCenter for Software EngineeringValue-Based Software EngineeringCS 577b Ray Madachy March 20, 2006USCC S EUniversity of Southern CaliforniaCenter for Software EngineeringOutline VBSE Refresh
USC - CSCI - 577
University of Southern CaliforniaCenter for Systems and Software EngineeringFeasibility Rationale Description (FRD)Dr. Barry Boehm CS577 Fall 200710/08/2007(c) USC-CSSE1University of Southern CaliforniaCenter for Systems and Software
USC - CSCI - 577
File Name: Weekxx_MSProejct_F07a_Txx.doc Due every Wednesday by 2:05pm 1. Weekly update of your project plan using MS Project 2. Post your file in the team website, do not submit to csci577@usc.edu 3. Make sure you indicate the percentage complete fo
USC - CSCI - 577
Life Cycle Plan (LCP)BTI Appraisal Projects Team 7Team Role Project Manager Developer Developer IIV&VTeam Member Aqeel Al Sadah Sudhir Malhan Divya Marlapalle Phillip GomezFebruary 27, 2008LCP_RLCA_S08b_T07_V5.1i Version Date: 2/27/08L
USC - CSCI - 577
Life Cycle Plan (LCP)BTI Appraisal Projects Team 7Team Role Project Manager Developer Developer IIV&VTeam Member Aqeel Al Sadah Sudhir Malhan Divya Marlapalle Phillip GomezApril 7, 2008LCP_IOC1_S08b_T07_V5.2i Version Date: 4/7/08Life C
USC - CSCI - 577
Transition Readiness ReviewLos Angeles Music and Art School (LAMAS) Team-805/01/09 TRR 1OUTLINE Operational concept overview Project Demo (IOC) Support plan Data archiving Summary of transition plan Q&A05/01/09TRR2Operational Concep
USC - CSCI - 577
Iteration PlanIteration Plan (IP)Los Angeles Music and Art School (LAMAS) Team-8Member Sahil Narang Anupam Vats Meghna Seth Manish Tewatia Tushar Patel Aviral SharmaRole Project Manager, Requirement Analyst Operational Concept Engineer Protot
USC - CSCI - 577
Operational Concept Description (OCD)LAMAS Customer Service ApplicationTEAM NUMBER-8Member Sahil Narang Anupam Vats Meghna Seth Manish Tewatia Tushar Patel Aviral SharmaRole Project Manager, Requirement Analyst Operational Concept Engineer Pr
USC - CSCI - 577
Transition Plan (TP)Bid Review SystemTeam 11TP_IOC_S08b_T11_V1.1Page i of 10Version Date: 02/16/08Transition Plan Version no x.xxYuwei Jiang Divyanka Aswani Priyanka Seernam Mithila Rao Velishala Kalyani Soniminde Julie Payne Keith Cull
USC - CSCI - 577
2008PEER REVIEW PLAN (PRP)COINCOMO 2.0CSCI 577b Team 4 University of Southern California 04/28/2008PEER REVIEW PLAN(PRP) Version 0.13Development Team Roles Project Manager System Architect/System Analyst System Architect/System Analyst I
USC - CSCI - 577
Transition Plan (TP)E-Mentoring SystemTeam #16Chen Zhao Tan Liu Philip Wong Chen Wei Ma Carlos Rosario Bruno Samuel Carlene Davis Dawn Bautiste Allen Lew Anthony DunbarProject Manager / Feasibility Rationale Requirements Analyst System Archit