System development

       What others call project management, programmers call system development. The focus partly is the same: who does what when? But in sys. dev. there's more focus on the programming. One of the results of system development is documentation, resulting in some people using the two words as if they meant the same.
       Some of the challenges for a programmer are to make sure, that the right program is written, and that it's ready on time. Through validation and verification you can solve some of the problem. Verification is to make sure, that the plan was followed - did we remember to make a function, so you can jump into a chatroom? Validation is to make sure, that the program works - would real players ever consider going to a chatroom while they play? The programmer also has to ascertain quality - that the program maintains a certain standard, and is as good as it can be within the timeframe.
       In almost every kind of system development, there are some phases - analysis, design, programming and maintenance. But different methods see these phases differently. Some think they should come nicely one after the other, others think they should be mixed, others again think some of the phases should be very small etc. Some methods can be mixed - e.g. you can take the phases of OOAD and mix them as prototyping dictates.

Concept last updated: 11/07 2003.

Relations
is a kind of
is part of
can be part of
is a kind of
is a kind of
is a kind of
is a kind of

Other sources

Struktureret analyse System development Systemdefinition

Libellus