HFOSS To Do
From Foss2Serve
(Difference between revisions)
Heidi.ellis (Talk | contribs) (→Finding Requirements and other project artifacts) |
|||
| Line 8: | Line 8: | ||
==== Finding Requirements and other project artifacts ==== | ==== Finding Requirements and other project artifacts ==== | ||
Instructors need examples of software development artifacts. What can we do to assemble a list of good (and not so good) examples of software project work? Things like: requirements and design specs; documentation standards; coding standards; agile processes; online/recorded stand up meetings; etc. | Instructors need examples of software development artifacts. What can we do to assemble a list of good (and not so good) examples of software project work? Things like: requirements and design specs; documentation standards; coding standards; agile processes; online/recorded stand up meetings; etc. | ||
| + | |||
| + | [[Category: Reference]] | ||
Latest revision as of 15:17, 28 May 2015
This is a collection of projects or things that need doing to support the HFOSS community and help it further develop. Some of these might be projects for students.
Finding Data Structures
HFOSS code contains lots of examples of data structures, and faculty need examples for teaching. It would be a useful resource to document use of various data structures in HFOSS code and make that list available. A student at NCC has done some preliminary work in this area:
Finding Requirements and other project artifacts
Instructors need examples of software development artifacts. What can we do to assemble a list of good (and not so good) examples of software project work? Things like: requirements and design specs; documentation standards; coding standards; agile processes; online/recorded stand up meetings; etc.
