158:
187:
of functionality and construction, as well as their relations, are documented. This is how the idea of iterative development got started; a functional design is by nature influenced by the technology platform chosen for implementation, and some basic design decisions will need to be revisited when early assumptions prove later to be wrong or costly to implement. This became the forerunner of the Rapid
Application Development method, which caused these two phases to become cyclical and work in tandem.
133:. The company was founded in order to develop the method and create training materials to propagate the method. It was successful, but was revised in 1987 to standardize and separate the method theory from the more technical aspects used to implement the method. Those aspects were bundled into the process modelling tool called "Software Development Workbench", that was later sold in 2000 to BWise, another Dutch company. This revised version of the method without the tool is commonly known as
146:
174:
and process flows in the BD were making decisions that the technical crew later needed to code, although their technical knowledge was not detailed enough to make those decisions. This obviously led to problems in collaboration between project teams during both the BD and DD phases. Because of the waterfall method of Go/No Go decisions at the end of each phase, the technical crew would have to make a formal
27:
344:
During the system test the development team—or a separate testing team—tests the system. Most of this will be focused on the technical aspects: does the system work as it should, or are there bugs still present? Bugs that are found in this phase will be fixed. At the ending of this phase, the program
332:
In this phase, the design is converted to a working system. The actual way this is done will depend on the system used. Where in older systems programmers often had to write all of the code, newer systems allow the programmers to convert the design into code directly, leaving less work to be done and
266:
In this phase, a more in-depth study of the project is made. The organization is analysed to determine their needs and determine the impact of the system on the organization. The requirements for the system are discussed and decided upon. The feasibility of the project is determined. Aspects that can
186:
In SDM2, the term "Basic Design" was replaced by the term "Global Design" to indicate that this document was continuously updated and subject to change during both the BD and DD phases. Thus the "Basic design" is both global and detailed at the end of the project. In the global design, the principles
83:
In the early to mid-1970s, the various generic work steps of system development methodologies were replaced with work steps based on various structured analysis or structured design techniques. SDM, SDM2, SDM/70, and
Spectrum evolved into system development methodologies that were based on the works
248:
Upon completion of a phase, it is decided whether to go on to the next phase or not; the terms 'Go' and 'No-Go' are used for this. The next phase will not start until a 'Go' is given, while if there is a 'No-Go', the project either stays in the current phase to be improved or is canceled completely.
190:
SDM2 only partially solved the problem of meeting customer requirements; modern software development methods go several steps further by insisting for example on incremental deliveries, or that the customer appoint key users of the delivered system to play a role in the project from start to finish.
348:
During the acceptance test, the end-users will test the system. They will test to see if the program does what they want it to do. They will not test every possible scenario, but they will test to see if the program does what they want and expect it to do and that it works in an easy way. Bugs that
173:
During the SDM functional design phase called BD (Basic Design), design aspects were documented (out of phase) in detail for the later technical design DD (Detailed Design). This caused a gray zone of responsibility to occur between the two phases; the functional crew responsible for the data flows
58:
group in the 1980s, and the last version of SDM to be published in
English was SDM2 (6th edition) in 1991 by Cap Gemini Publishing BV. The method was regularly taught and distributed among Capgemini consultants and customers, until the waterfall method slowly went out of fashion in the wake of more
304:
explaining what each part of the system does, and the high-level technical design, explaining how each part of the system is going to work. This phase combines the functional and technical design and only gives a broad design for the whole system. Often, the architecture of the system is described
257:
In this phase, the problems that have to be solved by the project are defined. The current and desired situations are analysed, and goals for the project are decided upon. In this phase, it is important to consider the needs of all parties, such as future users and their management. Often, their
316:
In this phase, the design for the product is described technically in the jargon needed for software developers (and later, the team responsible for support of the system in the O&S phase). After the basic design has been signed off, the technical detailed design determines how this will be
169:
SDM2 was a revised version of SDM that attempted to solve a basic problem that occurred often in SDM projects; the delivered system failed to meet the customer requirements. Though any number of specific reasons for this could arise, the basic waterfall method used in SDM was a recipe for this
108:
model. Starting from the system as a whole, its description becomes more detailed as the design progresses. The method was marketed as a proprietary method that all company developers were required to use to ensure quality in customer projects. This method shows several similarities with the
333:
a smaller chance for errors. At the same type, the system becomes more reliant on the design—if the design has been properly tested, the proper code will be generated, but if the design is not fully correct, the code will be incorrect without a programmer to look for such problems.
352:
During this phase, the final version of the system is implemented by the organization: the hardware is set up, the software is installed, end user documentation is created and, end users trained to use the program, existing data is entered into the system.
170:
problem due to the relatively large amount of time spent by development teams between the
Definition Study and the Implementation phases. It was during the design phases that the project often became out of sync with customer requirements.
178:
in order to make corrections in the detailed sections of the Basic Design. Such changes were often confusing for the customer, because these originated from the project team rather than directly from the customer requirements,
183:. Usually the customer was only allowed to produce requirements up to and including the functional design in the BD phase. After that, the customer had to wait patiently until acceptance testing in the Implementation phase.
53:
divided in seven phases that have a clear start and end. Each phase delivers subproducts, called milestones. It was used extensively in the
Netherlands for ICT projects in the 1980s and 1990s. Pandata was purchased by the
295:
In this phase, the design for the product is made. After the definition study has determined what the system needs to do, the design determines how this will be done. This often results in two documents: The
324:
In SDM2, this phase elaborates on the Global Design by creating more detailed designs, or further refining existing detailed designs, to the point where they can be used to build the system itself.
109:
proprietary methods of CAP Gemini's most important competitors in 1990. A similar waterfall method that was later used against the company itself in court proceedings in 2002 was CMG:Commander.
199:
SDM is a method based on phases. Before every phase, an agreement needs to be reached detailing the activities for that phase. These documents are known as
210:
Consolidation — By approving a milestone document, it gains a certain status. The client can not change any of the specifications later during development.
361:
Once the system has been implemented, it is used within the organization. During its lifetime, it needs to be kept running and possibly enhanced.
321:
per function, and the technical design per function, explaining how each part of the system is going to work, and how they relate to each other.
130:
393:
97:
308:
SDM2 split this step in two parts, one for the BD phase, and one for the DD phase, in order to create a Global Design document.
377:
439:
207:
Traceability — Through applying deadlines to milestone documents, clients can keep track on whether a project is on schedule
424:
20:
414:
200:
64:
72:
222:
The method uses 7 phases which are successively executed, like the waterfall model. The phases are:
68:
349:
are found in this phase will be reported to the development team so that they can fix these bugs.
341:
The implementation, or testing phase consists of two steps: a system test and an acceptance test.
161:
The "Plan-Do-Check-Act" cycle of Rapid application software development, showing the start of a
213:
If necessary, the project can be aborted. This mostly happens during the start of development.
384:'s own method CMG:Commander method was used to prove company responsibility for employee work
301:
126:
280:
Economics — Are the costs of developing the system lower than the profit made from using it?
258:
expectations clash, causing problems later during development or during use of the system.
42:
271:
Advisable — Are the resources (both time and knowledge) available to complete the project.
8:
157:
60:
277:
Technique — Can the available equipment handle the requirements the system places on it?
444:
317:
developed with software. This often results in a library of source documentation: The
318:
297:
85:
153:, which since the 1980s forms the basis of any software project management process.
100:
and others, as well as data modeling techniques developed by Thomas
Bachmann and
50:
46:
175:
420:
433:
381:
150:
105:
241:
Implementation: Installation, data conversion, and cut-over to production
121:, which itself was created as a joint venture by three Dutch companies:
118:
101:
93:
409:
122:
117:
SDM was developed in 1970 by a company known as PANDATA, now part of
55:
145:
283:
Organization — Will the organization be able to use the new system?
89:
274:
Significance — Does the current system need to be replaced?
134:
232:
Basic Design: High level technical design and revised plan
244:
Operation and
Support: Delivery to ICT support department
226:
Information planning: Problem definition and initial plan
286:
Legal — Does the new system conflict with existing laws?
229:
Definition study: Requirements analysis and revised plan
235:
Detailed Design: Building the system (and revised plan)
140:
26:
396:
on the sale of
Software Development Workbench to BWise
238:
Realization: Testing and acceptance (and revised plan)
45:
method developed by the software company
Pandata in
19:For development methods in software projects, see
78:
431:
131:Posterijen, Telegrafie en Telefonie (Nederland)
267:be considered to determine feasibility are:
181:even after a change freeze was put in place
380:in Computable magazine how the competitor
203:. Several uses for these documents exist:
356:
156:
144:
25:
252:
432:
41:(System Development Methodology) is a
141:Main difference between SDM and SDM2
425:Association for Computing Machinery
261:
13:
311:
14:
456:
403:
336:
194:
410:Software Development Methodology
21:Software development methodology
290:
387:
371:
327:
79:The Cap Gemini SDM Methodology
1:
364:
84:of Steven Ward, Tom Demarco,
65:Rapid application development
440:Software development process
7:
16:Software development method
10:
461:
415:Checklist SDM Activiteiten
112:
73:Agile software development
18:
217:
49:in 1970. The method is a
394:Dutch Computable article
69:Rational Unified Process
345:should work properly.
166:
154:
31:
357:Operation and Support
302:User interface design
160:
148:
127:Nationale Nederlanden
29:
253:Information planning
43:software development
421:Record for SDM book
201:milestone documents
61:extreme programming
167:
155:
98:Michael A. Jackson
32:
319:functional design
298:functional design
86:Larry Constantine
452:
397:
391:
385:
375:
262:Definition study
63:methods such as
460:
459:
455:
454:
453:
451:
450:
449:
430:
429:
406:
401:
400:
392:
388:
376:
372:
367:
359:
339:
330:
314:
312:Detailed Design
293:
264:
255:
220:
197:
143:
115:
81:
51:waterfall model
47:the Netherlands
24:
17:
12:
11:
5:
458:
448:
447:
442:
428:
427:
418:
412:
405:
404:External links
402:
399:
398:
386:
369:
368:
366:
363:
358:
355:
338:
337:Implementation
335:
329:
326:
313:
310:
292:
289:
288:
287:
284:
281:
278:
275:
272:
263:
260:
254:
251:
246:
245:
242:
239:
236:
233:
230:
227:
219:
216:
215:
214:
211:
208:
196:
195:The SDM method
193:
176:Change request
142:
139:
114:
111:
80:
77:
35:Cap Gemini SDM
15:
9:
6:
4:
3:
2:
457:
446:
443:
441:
438:
437:
435:
426:
422:
419:
416:
413:
411:
408:
407:
395:
390:
383:
379:
378:Dutch article
374:
370:
362:
354:
350:
346:
342:
334:
325:
322:
320:
309:
306:
303:
299:
285:
282:
279:
276:
273:
270:
269:
268:
259:
250:
243:
240:
237:
234:
231:
228:
225:
224:
223:
212:
209:
206:
205:
204:
202:
192:
188:
184:
182:
177:
171:
164:
159:
152:
151:Deming circle
147:
138:
136:
132:
128:
124:
120:
110:
107:
103:
99:
95:
91:
87:
76:
74:
70:
66:
62:
57:
52:
48:
44:
40:
36:
28:
22:
389:
373:
360:
351:
347:
343:
340:
331:
323:
315:
307:
294:
291:Basic Design
265:
256:
247:
221:
198:
189:
185:
180:
172:
168:
162:
116:
104:. SDM is a
82:
38:
34:
33:
30:SDM2 method.
328:Realization
434:Categories
417:(In Dutch)
365:References
163:spiralling
119:Cap Gemini
102:Peter Chen
94:Ed Yourdon
59:iterative
445:Capgemini
56:Capgemini
106:top-down
165:method.
113:History
90:Ken Orr
305:here.
218:Phases
300:, or
37:, or
149:The
135:SDM2
129:and
123:AKZO
71:and
39:SDM2
423:on
382:CMG
436::
137:.
125:,
96:,
92:,
88:,
75:.
67:,
23:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
