1. | Welcome | ToC | FAQ | Resources | Courses | Projects | Mail Lists | Members | Misc |
2. | Participation | Source of Ideas | Credit/Ownership | MOST SDP | Teams |
3. | Evolution | Roles | Phases | Documents |

The MOST Programming Project
Suggested Development Process

Programmers hate process. That's the one truth i've learned in my years in the industry. The second thing i learned was that successful programmers deal with their hate and accept a little discipline in their development efforts. Those who have developed applications already have a 'process' that they follow (even if they don't think of it that way). For those who wish to organize their efforts to produce a Mac OS application and do not already have a method selected, we provide the MOST Suggested Development Process (MOST SDP).

The MOST SDP will be better suited to guide the efforts of small, poorly or self-financed independent teams of independents who wish to co-operate to produce a Mac OS application than as a guide for development within a professional software development company. In its first version it is primarily intended for use by "students" as they participate in MOST Development Projects. We expect to evolve the information contained herein based on our experiences and input from other Mac OS developers. Note that we explicitly state in the "evolution" section that, when it comes to development explicitly in the Mac OS environment, the MOST SDP isn't yet *proven* either. We're working on that :-).

Project teams are encouraged to familiarize themselves with the information contained in this section and then decide how much of it to apply to their project. The full level of detail suggested herein is only appropriate for projects with a large number of participants and high degree of complexity. For small scale projects with limited numbers of participants, the overhead introduced by following many of these suggestions would actually be counter-productive. The Project Manager is expected to select an appropriate subset of the suggestions contained herein for use by the project team based on discussions with the team and her/his good judgement. Once selected, the team should follow the agreed upon protocol throughout the life of the project.

• Evolution - Explains the current state of the MOST SDP and our plans to improve it via direct experience in Mac OS development and from outside feedback by bona fide Mac OS developers/technicians/engineers.
• Roles - Defines the roles of the individuals who participate in the project, specifying areas of responsibility and authority for each. Provides suggestions for qualifications needed to fill each role based on project complexity, target audience, etc.
• Phases - Defines the phases through which the project progresses on its way to completion. Defines the tasks performed within each phase and the criteria which should be met before considering a phase cpmpleted.
• Documents - Defines the documents (including the code and the application itself) that will be produced during the life cycle of a project. Identifies the individual, by role, who is responsible for the production of each document and specifies who, by role, should compose the review / acceptance team for each document.

Copyright © 1996, 1997, 1998. Last Update to This Page: 1998/04/29
This Page Maintained by: radar pangaean * * * Original Author: radar pangaean
The MOST web site is built and maintained by the voluntary efforts/donations of our members.