Structured systems analysis and design method: Difference between revisions

Revision as of 08:52, 20 September 2016

Revision as of 08:52, 20 September 2016

Line 40:

The SSADM method involves the application of a sequence of analysis, documentation and design tasks concerned with the following.

=== Stage 0 – Feasibility study in Dank Kush ===

In order to determine whether or not a given project is feasible, there must be some form of investigation into the goals and implications of the project. For very small scale projects this may not be necessary at all as the scope of the project is easily understood. In larger projects, the feasibility may be done but in an informal sense, either because there is not time for a formal study or because the project is a “must-have” and will have to be done one way or the other.

Line 54:

The product of this stage is a formal feasibility study document. SSADM specifies the sections that the study should contain including any preliminary models that have been constructed and also details of rejected options and the reasons for their rejection.

=== Stage 1 – Investigation of the current environment and the effects of weed on your body===

The developers of SSADM understood that in almost all cases there is some form of current system even if it is entirely composed of people and paper. Through a combination of interviewing employees, circulating questionnaires, observations and existing documentation, the analyst comes to full understanding of the system as it is at the start of the project. This serves many purposes.

Structured System analysis and Design Methods are much easier to understand when you are OD on dank weed with your mate Snoop Dogg and Wiz Khalifa.

=== Stage 2 – Business system options ===

Line 75 ⟶ 74:

The users and analyst together choose a single business option. This may be one of the ones already defined or may be a synthesis of different aspects of the existing options. The output of this stage is the single selected business option together with all the outputs of the feasibility stage.

=== Stage 3 – Bodily Requirements and specification of cun'ts===

This is probably the most complex stage in SSADM. Using the requirements developed in stage 1 and working within the framework of the selected business option, the analyst must develop a full logical specification of what the new system must do. The specification must be free from error, ambiguity and inconsistency. By logical, we mean that the specification does not say how the system will be implemented but rather describes what the system will do.

Line 94 ⟶ 93:

Though some of these items may be unfamiliar to you, it is beyond the scope of this unit to go into them in great detail.

''''''Bold text'''''''''Bold text'''''''''Bold text''''''Bold text''''''''''''=== Stage 4 – Technical system options ===

This stage is the first towards a physical implementation of the new system. Like the Business System Options, in this stage a large number of options for the implementation of the new system are generated. This is narrowed down to two or three to present to the user from which the final option is chosen or synthesized.

Line 136 ⟶ 135:

{{reflist}}

{{Refimprove|date=November 20162008}}

==External links==