Structured systems analysis and design method: Difference between revisions

Content deleted Content added
Line 135:
The product is a complete Physical Design which could tell software engineers how to build the system in specific details of hardware and software and to the appropriate standards.
 
=== Stage 6 Physical design===
==Advantages and disadvantages==
A methodological approach of studying a business (or an area of a business) from a number of different perspectives is more likely to provide a more thorough understanding of the business, its processes and data, than the "ad-hoc" approaches that were used previously. This in turn should (it was hoped) lead to systems that are more complete and correct.
 
This is the final stage where all the logical specifications of the system are converted to descriptions of the system in terms of real hardware and software. This is a very technical stage and a simple ''overview'' is presented here.
However, the SSADM approach of having to complete one phase before beginning the next led some projects into what is referred to as "analysis paralysis". What is meant by this is that because a business and its processes never stays the same for very long, the systems team would continually have to revisit analysis and design products for amendment, causing (sometimes lengthy) delays in getting to the programming and delivery stages of the system. In recognition of this, later versions of the Methodology introduced a more optional/dynamic approach to the process.
 
The logical data structure is converted into a physical architecture in terms of database structures. The exact structure of the functions and how they are implemented is specified. The physical data structure is optimized where necessary to meet size and performance requirements.
There is also a cost in training people to use the techniques. The learning curve can be considerable if the full method is used, as not only are there several modelling techniques to come to terms with, but there are also a lot of standards for the preparation and presentation of documents.
 
The product is a complete Physical Design which could tell software engineers how to build the system in specific details of hardware and software and to the appropriate standards.
In summary, using this methodology involves a significant undertaking which may not be suitable to all projects.
 
==References==