System Development Methodology: Difference between revisions

Revision as of 08:51, 16 March 2006

Revision as of 18:41, 18 March 2006

Line 1:

'''System Development Methodology''' (SDM) is primarily being used for the development of IT-projects. SDM is a [[waterfall_modelwaterfall model|waterfall method]]. This means that a phase only starts when a previous phase has been closed. This counts for all phases, except the first one.

SDM is a [[top down]] model. Starting from the system as a whole, its description becomes more detailed as the design progresses.

==History==

SDM was developed in [[1970]] by a company known as [[PANDATA]], now part of [[Cap Gemini]], by order of three Dutch companies: [[AKZO]], [[Nationale Nederlanden]] and [[PTT]]. It was revised in [[1987]]. This version is commonly known as [[SDM2]].

==The method==

As stated before, SDM is a method based on phases. Before every phase an agreeement needs to be reached detailing the activities for that phase. These documents are known as [[Milestone_Milestone (Project_ManagementProject Management)|milestone]] documents. Several uses for these documents exist:

As stated before, SDM is a method based on phases. Before every phase an agreeement needs to be reached detailing the activities for that phase. These documents are known as [[Milestone_(Project_Management)|milestone]] documents. Several uses for these documents exist:

* Traceability. Through applying deadlines to milestone documents, clients can keep track on whether a project is on schedule

Line 16 ⟶ 14:

==Phases==

The method uses 7 phases which successively are being executed. The phases are:

Line 30 ⟶ 27:

===Problem definition===

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 expectations clash, causing problems later during development or during use of the system.

===Definition study===

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 be considered to determine feasibility are:

Line 45 ⟶ 40:

===Design===

In this phase the design for the product will be 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 documments: The [[Functional_DesignFunctional Design|functional design]], explaining what each part of the system does, and the [[technical design]], explaining how each part of the system is going to work.

In this phase the design for the product will be 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 documments: The [[Functional_Design|functional design]], explaining what each part of the system does, and the [[technical design]], explaining how each part of the system is going to work.

SDM2 split this step in two parts.

Line 54 ⟶ 48:

===Building the system===

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 a smaller chance for errors in this phase. 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 as well without a propgrammer to look for such problems.

===Testing===

The testing consists of two steps: A system test and an acceptance test.

Line 66 ⟶ 58:

===Implementation===

During this phase the final version of the system is implemented by the organization: The hardware is set up and the software is installed, end users are trained to use the program, existing data is entered into the system and documentionat is delivered to the proper people.

===Operation and Support===

Once the system has been implemented it is used within the organization. During its lifetime it needs to be kept running and possibly enhanced.

==External links==

* [http://www.hyperthot.com/pm_sdm.htm Software Development Methodology]

* [http://www.zbc.nu/main.asp?ChapterID=420 Checklist SDM Activiteiten] (In Dutch)

[[Category:Software development]]

[[nl:System_Development_Methodology]]