FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W783614878> ?p ?o ?g. }

• W783614878 abstract "Abstract NOTE: The first page of text has been automatically extracted and included below in lieu of an abstract Preliminary Experience of Using a Learning and Knowledge Management System for an SE-1 Course Abstract Students and instructors struggle to provide an integrated view of learning content that is spread over personal and shared file systems, course management systems, team project repositories, wikis, blogs, and other content storage and retrieval systems. Further, they struggle to organize this content when each system provides a different organizational mechanism and strategy. Course management systems fragment content by semester, course, and class session. File systems fragment content into hierarchically organized folders and files with only folder and file names to describe the content. Project repositories fragment information into versions, artifact types, and subsystems organized as folders. It is especially a challenge for a student who does not yet have the knowledge for how to organize and describe their learning content. We have developed an initial version of a learning and knowledge management system and piloted it for an Introduction to Software Engineering course. To hold the common repository of learning content, we used digital library technology. To organize content, we tagged content using subject headings based on the Software Engineering Body of Knowledge (SWEBOK) subject taxonomy. Instructors and students can contribute content, tag it using SWEBOK and other terms, and search through it using SWEBOK and other terms. The results of our pilot were mixed. A digital library-based repository is insufficient for dynamically changing and evolving content. A significant amount of learning content needs to be provided (more than for just one course), and there needs to be one location of record for accessing content, rather than multiple locations. A positive result was some validation that using SWEBOK to organize, tag, and search for content is helpful in readily accessing information and helping provide students with an understanding of the organization of knowledge of their discipline. Since the main intent of this research project was to gain some operational experience and initial validation of using a domain-specific taxonomy to organize learning content, we consider the project to be a success. Introduction In prior work1 we described the need for and design of a knowledge management system that holds learning content for Software Engineering courses, and provides students, project teams, and instructors with advanced tools to create, share, and annotate both the learning content and an organizational structure for that content. Traditional course management systems, team project repositories, wikis, etc., usually fragment information into silos (that is, into distinct information storage locations which are not integrated). We seek a system to help integrate the fragmented information into a whole across the curriculum and the student’s academic career and to improve student interaction with learning content and with each other in project teams. Further, by organizing the content and presenting it in a way that reflects the structure of knowledge in the software engineering discipline, we expect that the students will more readily" @default.
• W783614878 created "2016-06-24" @default.
• W783614878 creator A5004325126 @default.
• W783614878 creator A5005445758 @default.
• W783614878 creator A5052889739 @default.
• W783614878 creator A5084660131 @default.
• W783614878 date "2020-09-04" @default.
• W783614878 modified "2023-09-27" @default.
• W783614878 title "Preliminary Experience Of Using A Learning And Knowledge Management System For An Se 1 Course" @default.
• W783614878 cites W1548835536 @default.
• W783614878 cites W1559931976 @default.
• W783614878 cites W1887941422 @default.
• W783614878 cites W2135061201 @default.
• W783614878 cites W2187896270 @default.
• W783614878 cites W31559721 @default.
• W783614878 doi "https://doi.org/10.18260/1-2--4022" @default.
• W783614878 hasPublicationYear "2020" @default.
• W783614878 type Work @default.
• W783614878 sameAs 783614878 @default.
• W783614878 citedByCount "0" @default.
• W783614878 crossrefType "proceedings-article" @default.
• W783614878 hasAuthorship W783614878A5004325126 @default.
• W783614878 hasAuthorship W783614878A5005445758 @default.
• W783614878 hasAuthorship W783614878A5052889739 @default.
• W783614878 hasAuthorship W783614878A5084660131 @default.
• W783614878 hasBestOaLocation W7836148781 @default.
• W783614878 hasConcept C136764020 @default.
• W783614878 hasConcept C154945302 @default.
• W783614878 hasConcept C2777212361 @default.
• W783614878 hasConcept C2777855551 @default.
• W783614878 hasConcept C2779010991 @default.
• W783614878 hasConcept C2779114481 @default.
• W783614878 hasConcept C2779182362 @default.
• W783614878 hasConcept C2779344036 @default.
• W783614878 hasConcept C2987181025 @default.
• W783614878 hasConcept C33039251 @default.
• W783614878 hasConcept C41008148 @default.
• W783614878 hasConcept C49774154 @default.
• W783614878 hasConceptScore W783614878C136764020 @default.
• W783614878 hasConceptScore W783614878C154945302 @default.
• W783614878 hasConceptScore W783614878C2777212361 @default.
• W783614878 hasConceptScore W783614878C2777855551 @default.
• W783614878 hasConceptScore W783614878C2779010991 @default.
• W783614878 hasConceptScore W783614878C2779114481 @default.
• W783614878 hasConceptScore W783614878C2779182362 @default.
• W783614878 hasConceptScore W783614878C2779344036 @default.
• W783614878 hasConceptScore W783614878C2987181025 @default.
• W783614878 hasConceptScore W783614878C33039251 @default.
• W783614878 hasConceptScore W783614878C41008148 @default.
• W783614878 hasConceptScore W783614878C49774154 @default.
• W783614878 hasLocation W7836148781 @default.
• W783614878 hasLocation W7836148782 @default.
• W783614878 hasOpenAccess W783614878 @default.
• W783614878 hasPrimaryLocation W7836148781 @default.
• W783614878 hasRelatedWork W1003879637 @default.
• W783614878 hasRelatedWork W2052945752 @default.
• W783614878 hasRelatedWork W2129034233 @default.
• W783614878 hasRelatedWork W2135778746 @default.
• W783614878 hasRelatedWork W2161096329 @default.
• W783614878 hasRelatedWork W2187040207 @default.
• W783614878 hasRelatedWork W2294734560 @default.
• W783614878 hasRelatedWork W2383748991 @default.
• W783614878 hasRelatedWork W4324372432 @default.
• W783614878 hasRelatedWork W783614878 @default.
• W783614878 isParatext "false" @default.
• W783614878 isRetracted "false" @default.
• W783614878 magId "783614878" @default.
• W783614878 workType "article" @default.