Projecting Software Defects from Analyzing Ada Designs
IEEE Transactions on Software Engineering - Special issue on software measurement principles, techniques, and environments
Component software: beyond object-oriented programming
Component software: beyond object-oriented programming
Technical opinion: reuse: been there, done that
Communications of the ACM
Integrating interactive computer-based learning experiences into established curricula: a case study
Proceedings of the 5th annual SIGCSE/SIGCUE ITiCSEconference on Innovation and technology in computer science education
A component repository for learning objects: a progress report
Proceedings of the 1st ACM/IEEE-CS joint conference on Digital libraries
FIE '00 Proceedings of the 30th Annual Frontiers in Education - Volume 02
Making of an interactive teaching gem
ACM SIGGRAPH 2006 Educators program
No Code Required: Giving Users Tools to Transform the Web
No Code Required: Giving Users Tools to Transform the Web
| Hi-index | 0.02 |
Reuse is vital in the education world because the time and money necessary to create high quality educational software is prohibitive. Estimates for the cost of creating a single well designed, highly graphical and interactive online course in the commercial domain range from several hundred thousand dollars to a million or more. Thus the idea of reusable software components that can be easily shared is tremendously appealing. In fact, "component" has become a buzzword in the educational software community, with millions of dollars from the National Science Foundation and other sponsors funding a wide variety of "component-based" projects. But few, if any, of these projects, have approached the grand vision of creating repositories of easy to reuse components for developers and educators. This paper investigates some of the factors that stand in the way of achieving this goal. We begin by defining the word component and looking at several projects using components, with a focus on our Exploratories project at Brown University. We then discuss challenges in: Searching and Metadata, Quality Assurance, Programming in the University Environment, Platform and System Specificity, Social Issues, Intellectual Property Issues, and Critical Mass. We look at relevant software engineering issues and describe why we believe educational applications have unique factors that should be considered when using components.