Gregg Jolley & Lorna Hooper
•Als PPT, PDF herunterladen•
0 gefällt mir•325 views
![AKMG MISSION ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Andere mochten auch
Andere mochten auch (13)
Ähnlich wie Gregg Jolley & Lorna Hooper
Ähnlich wie Gregg Jolley & Lorna Hooper (20)
Mehr von Ark Group Australia Pty Ltd
Mehr von Ark Group Australia Pty Ltd (20)
Gregg Jolley & Lorna Hooper
- 1. ARMY KNOWLEDGE SEARCH IN SHAREPOINT Major Gregg Jolley and Mrs Lorna Hooper ARMY KNOWLEDGE MANAGEMENT GROUP 2011
- 3. What’s the Problem? Information Overload Retention of Corporate Knowledge Management of Corporate Information Uncontrolled Information Inability to Find Documents Disparate Information, Users, Needs Requirement for Systematic Approach Integrate/amalgamate Lessons/Doctrine/Output Formats (ALPC)
- 4. Poor Knowledge/Content Management Collaboration Efficiencies Aligning with AKD purpose with SP No “Lingua Franca” write once/output many format Integration of Repository: AKMG = Integrate/amalgamate Lessons/Doctrine/Output Formats (ALPC) Disparate Information, Users, Needs Inadequate Search /Inability to Find Documents / Poor Knowledge/Content Management Poor Knowledge/Content Management Management of Corporate Information Common Purpose – Taxonomy/Metadata Retention of Corporate Knowledge/Requirement for Systematic Approach SOLUTION PROBLEM
- 5. SHAREPOINT & THE AKD KNOWLEDGE MANAGEMENT Integrating the Knowledge Management Structure of Sharepoint with the Knowledge Management Process of Army Knowledge Management Group
- 7. METADATA ENVIRONMENT Optional – Tailored Repository Level Mandatory - Army Knowledge Domain Inclusion Requirement Mandatory - Essential 6 Elements AGLS Compliance
- 10. METADATA SCHEMA 1 ST LEVEL The 6 Mandatory elements (the primary elements required by Australian Government Locator Service (AGLS) 2 ND LEVEL The AKD Mandatory Metadata Schema elements 3 RD LEVEL The tailored Metadata Schema elements of the original repository
- 13. METADATA SCHEMA 3 rd Level The tailored Metadata Schema elements of the original repository
- 14. AUTHORITY CONTROL TOOL Authority Taxonomy & Additional Sources of information
- 15. CLASSIFICATION & META TAGGING: Internal Governance
- 16. CLASSIFICATION & META TAGGING: External Governance
- 17. Original AGLS elements Creator* Title* Date* Subject or function* Identifier or availability* Publisher Audience Contributor Coverage Description Format Language Mandate Relation Rights Source Type * = mandatory
- 18. CLASSIFICATION & META TAGGING: FRAMEWORK
- 19. SEARCH OPTIMISATION ENVIRONMENT Folksonomy/Tag Cloud Army Knowledge Domain Authority Control Tool Australian Defence Force Glossary
- 20. AKMG/SHAREPOINT INFORMATION ORGANISATION Army Knowledge Domain SHARE POINT SHARE POINT Share Point & the AKD are LINKED
- 23. AKMG’s Hierarchy of Published Knowledge Authority
- 24. Share Point & the AKD together can facilitate the rapid integration of lessons learned into formal knowledge
- 25. Share Point & the AKD together can create a Knowledge Sharing Organisation
- 27. Questions
Hinweis der Redaktion
- The Army Knowledge Management Group’s mission is to make the Australian Army’s “Formal Knowledge” sources visible, accessible and available to the Australian Defence Organisation, to our Allies and Industry Partners in the wider environment. The Army’s formal knowledge sources in 2010 encompass the extant Land Warfare Doctrine, the content of the Army Learning Organsation’s “Knowledge Source” databases and the Technology Based Training packages produced by the Army Learning Production Centre.Allies and
- Including TAGS & Defence Records Management as References
- • • •
- Fifth International IEEE Conference on Commercial-off-the-Shelf (COTS)-Based Software Systems (ICCBSS'06) The COTS Software Obsolescence Threat Orlando, Florida February 13-February 16 ISBN: 0-7695-2515-6ASCII Textx Leigh Merola, "The COTS Software Obsolescence Threat,"Commercial-off-the-Shelf (COTS)-Based Software Systems, InternationalConference on, pp. 127-133, Fifth International IEEE Conference onCommercial-off-the-Shelf (COTS)-Based Software Systems (ICCBSS'06),2006. BibTexx @article{ 10.1109/ICCBSS.2006.29,author = {LeighMerola},title = {The COTS Software Obsolescence Threat},journal={Commercial-off-the-Shelf (COTS)-Based Software Systems, InternationalConference on},volume = {0},year = {2006},isbn ={0-7695-2515-6},pages = {127-133},doi ={http://doi.ieeecomputersociety.org/10.1109/ICCBSS.2006.29},publisher ={IEEE Computer Society},address = {Los Alamitos, CA, USA},} RefWorksProcite/RefMan/Endnotex TY - CONFJO - Commercial-off-the-Shelf(COTS)-Based Software Systems, International Conference onTI - The COTSSoftware Obsolescence ThreatSN - 0-7695-2515-6SP127EP133A1 -Leigh Merola,PY - 2006KW - nullVL - 0JA -Commercial-off-the-Shelf (COTS)-Based Software Systems, International ConferenceonER - Leigh Merola, Raytheon, Integrated Defense Systems DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/ICCBSS.2006.29 Software is the primary focus of integration efforts for development of Open Architected, scalable, adaptable solutions in today?s Defense Systems of Systems. Unfortunately, successful software vendors obsolete their own product versions to maintain the pace with the market, without regard for the military need for continued support or expandability. Recognized by many professionals as being of equal gravity as the hardware obsolescence issue, software obsolescence has to-date not enjoyed the same level of visibility. This paper reveals the obsolescence problem in development, integration, test, production, and program management environments; a different perspective compared to the typical focus on obsolescence risk management and mitigation in the end-user, operational environment. Despite the portfolio of methods implemented for the effective management of COTS hardware obsolescence on a growing number of military programs, the software obsolescence problem is not being managed or mitigated. Could software obsolescence become more overwhelming than the hardware obsolescence dilemma?