EWW_LCO_F04a_T04
12 Pages

EWW_LCO_F04a_T04

Course Number: CSCI 577, Fall 2009

College/University: USC

Word Count: 1999

Rating:

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 577

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.

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...
MOST POPULAR MATERIALS FROM CSCI 577
MOST POPULAR MATERIALS FROM CSCI
MOST POPULAR MATERIALS FROM USC