Made with
ConceptDraw
DIAGRAM 18

SSADM Diagram

SSADM’s full name is “Structured Systems Analysis and Design Method”. This method is known to be a “waterfall” one, which means that it is a non-iterative design process, used in the different development processes of software, having the progress as a flowing steadily downwards, reminding a “waterfall”. These “downwards” go through the phases of initiation, design, analysis, conception, construction, production, testing, maintenance and implementation. SSADM is used in the design and analysis of different information systems, representing a pinnacle of the rigorous document-led approach, contrasting with more contemporary so-called “agile” methods (for example, “Scrum” one or “DSDM”). This method is basically a particular implementation and it helps build the work of different schools of the analysis, development methods, design and so on.

"Structured Systems Analysis and Design Method" or "SSADM" has its principles in use, which stages of the development started in 1980, when the “Central Computer and Telecommunications Agency” evaluated the analysis and the design methods in order to end up using exactly this one. In 1981 the consultants from “Learmonth and Burchett Management Systems” developed the first version of SSADM, followed by the second in 1984 and the third in 1986. Already in 1990 the fourth one was launched, followed by 4+ and 4.2 in 1995. Thus, SSADM got more and more popular, being renamed in 2000 as simply the "Business System Development" method. The leading techniques, which make this method so special, include the process of identifying, modelling and documenting data moving all around an information system. This process was called “Data Flow Modelling”, examining the processes as well as the external entities, and also the data flows. The second feature of using the Structured Systems Analysis and Design Method is that it involves the process of identifying, modelling as well as documenting the data requirements of the system, which is being designed. The result of such manipulation is a data model, which contains the entities, attributes (which can be facts about the mentioned entities) and relationships between different entities.

There is another process, involved in a Structured Systems Analysis and Design Method, known as a “two-stranded” one. This process includes the “Entity Behaviour Modelling”, which is identifying, modelling and documenting the events, which affect each of the existing entities as well as the sequence. It also involves the “Event Modelling”. In general, the “SSADM” method is known to be involving the application of a sequence of analysis, design tasks and documentation appearing. All of the stages go one by one, including the determination of whether or not a given project is feasible, answering the questions of if the project is technically possible, can the business afford to carry out such project, is there any impact on the new system, being socially acceptable and will the new system be compatible with the existing practices. Thus, “SSADM” specifies the sections that the study should contain, including any preliminary models, being constructed as well as the details of the rejected options.

On the second stage of conducting the SSADM we should understand that in almost all of the cases there is some form of the current system existing, even if it is composed of only paper and people. Thus, in a way of combining the circulating questionnaires, the interviewing employees, the existing documentation as well as the observations, we can understand the system much better. After investigating the current system, we have to decide which design of the new system we want to have. Once we do, we should develop a set of business system options, in which the new system could be produced. The answers to the questions, which we have to ask ourselves, have to include the needed degree of automation, the distribution of the system, the cost and so the benefit, the impact of the new system and many more.

Next stage provides developing a full logical specification of what the new system must do and the way it should be implemented. Such specification should not include any ambiguity or inconsistency, although there is also no need to mention in detail the way the system will be implemented but to describe what this system is meant to be doing. To make such analysis, it is better to build the required logical models for both the DFDs, which are “data flow diagrams” and the LDM, which is a “Logical data Model”. Going through this stage, you will end up having the updated data catalogue as well as the requirements one, the processing specification, the user function matrix as well as the function definitions, the entity life-histories, the logical data model and the effect correspondence diagrams.

Getting to the next stage, you should be prepared to conducting a physical implementation of the new system, as lots of options for the implementation of the new system should be generated by now. The outputs of the next stage are known to be an “implementation-independent” as well as concentrate on the requirements for the human computer interface. It ends with getting the product of the logical design, made up of data catalogue, the required logical data structure, the logical process model, etc. On the final stage all of the logical specifications of the system should be already converted to descriptions of the system, taking into consideration the real hardware and software. This stage is known to be a very technical as a total simple overview should be presented here.

Going through the stages in order to get the needed result, you can make a diagram, mentioning all of the needed data while conducting your Structured Systems Analysis and Design Method. With the help of ConceptDraw DIAGRAM it is much simpler to create any needed diagram, including the SSADM one. Having the vector stencils library “SSADM” from the solution named as the “Systems engineering”, which contains the specific symbols for making the “SSADM diagram” looking simply amazing, which includes it to be looking smart and professional, you can achieve the needed result. The ConceptDraw DIAGRAM software will be there for you providing all of the needed tools, including the “Systems engineering solution”, which can be found in the “Software Development area” of ConceptDraw Solution Park on this site or in ConceptDraw STORE.

Use the Systems engineering solution to draw SSADM diagrams for your business documents, presentations and websites.

SSADM Diagram

Example 1. SSADM Diagram — Systems Development Lifecycle

The example above illustrates the waterfall model used in SSADM. This model involves 5 stages of developing a product such as requirements specification and its' analysis, design, coding and testing.

ConceptDraw DIAGRAM is a perfect tool for:






TEN RELATED HOW TO's:
If your company is in chaos in clutter and no one understands their rights and responsibilities, maybe it's time to change that. One of the ways to put the company in order is to draw an organization chart that would reflect the structure and show the relationships among departments and positions. This is a very useful and easy to understand scheme. This is example of the one of the most typical kind of organizational chart. It depicts an organizational structure of the hierarchical type. Its construction is similarv to pyramid. The single main position on the top - in this case, the mayor's position followed by sub-levels of authority in his command. Each position in the pyramid reports only to his supervisor, and takes only a report of direct subordinates. Such scheme limits the number of communications. This organizational structure is effectively used in public organizations. Also it is suitable for any organization with the need for multiple levels of middle managers. The ability to create organizational charts of different types is supplied with ConceptDraw Ogrcharts solutions.How to Draw an Organization Chart *
Picture: How to Draw an Organizational Chart
Related Solution:
Diagrams are a very important part of modern life. With the help of flow diagram software, a lot of companies can promote their ideas at the market. Its usefulness is totally doubtless. This is a flow chart of the invoice payment flow. This flowchart details decrypts all stages of the process of obtaining and paying bills. It is a description of the universal process - such steps performs accounting departments of almost any organization. Since every business no matter what it does is a consumer of some goods or services. The given flow chart was made using ConceptDraw DIAGRAM software and the Diagrams solution for making flowcharts of any kind.Flow Diagram Software *
Picture: Flow Diagram Software
Related Solution:
When you are a beginner in software development, you make a lot of mistakes. Developing logical models, or data flow diagrams is a way to see the the whole project and all the processes clearly. And some novices, unfortunately for them, miss modeling stage at the beginning of project life cycle, and get into troubles as the project grows. This image represents the data flow diagram applying symbols of Yourdon and Coad notation. This DFD depicts the data flow inside an organization department deals with receivables. The icons of standard Yourdon and Coad notation provides possibility to draw professional looking and well- readable DFD for business documentation. This data flow diagram was designed with the help of ConceptDraw DIAGRAM and its Data Flow Diagrams solution. The solution delivers three vector graphic libraries including elements of Yourdon and Coad and Gane-Sarson notations.Data Flow Diagram Process *
Picture: Data Flow Diagram Process
Related Solution:
How to describe the necessity of using network security devices and visually illustrate this information? Now, it's very easy thanks to the ConceptDraw DIAGRAM diagramming and vector drawing software extended with Network Security Diagrams Solution from the Computer and Networks Area of ConceptDraw Solution Park.Network Security Devices *
Picture: Network Security Devices
Related Solution:
UML Collaboration Diagram Example Illustration. This sample was created in ConceptDraw DIAGRAM diagramming and vector drawing software using the UML Collaboration Diagram library of the Rapid UML Solution from the Software Development area of ConceptDraw Solution Park. This sample shows the creation process of the contact list and can be used at the staff training and staff working, at the attraction process the new clients.UML Collaboration Diagram Example Illustration *
Picture: UML Collaboration Diagram Example Illustration
Related Solution:
ConceptDraw DIAGRAM diagramming and vector drawing software extended with unique SCRUM Workflow solution from the Project Management area of ConceptDraw Solution Park allows fast and easy design professional-looking Scrum Workflow Diagrams and Scrum workflow scheme for projects required when working on projects and managing them, when developing software with cutting-edge Agile methodologies.Scrum workflow *
Picture: Scrum workflow
Related Solution:
The vector stencils library Crow's Foot Notation from the solution Entity-Relationship Diagrams (ERD) contains specific symbols of the Crow's foot notation such as relationship symbols and entity symbols for ConceptDraw DIAGRAM software.Martin ERD Diagram
Picture: Martin ERD Diagrams
Related Solution:
This sample shows the Strategic Plan of the Broadband Lifecycle that was developed by Strategic Networks Group. The Broadband Lifecycle represents the advance of the broadband investments.Successful Strategic Plan *
Picture: Successful Strategic Plan
No need for any special drawing skills to create professional looking diagrams outside of your knowledge base. ConceptDraw DIAGRAM takes care of the technical details, allowing you to focus on your job, not the drawing. ConceptDraw DIAGRAM delivers full-functioned alternative to MS Visio. ConceptDraw DIAGRAM supports import of Visio files. ConceptDraw DIAGRAM supports flowcharting, swimlane, orgchart, project chart, mind map, decision tree, cause and effect, charts and graphs, and many other diagram types.MS Visio Look a Like Diagrams *
Picture: MS Visio Look a Like Diagrams
A flowchart is a powerful tool for examining processes. It helps improving processes a lot, as it becomes much easier to communicate between involved people, to identify potential problems and to optimize workflow. There are flowcharts of different shapes, sizes and types of flowchart vary from quite basic process flowcharts to complex program flowcharts. Nevertheless, all these diagrams use the same set of special symbols like arrows to connect blocks, parallelogram to show data receiving or rectangles for showing process steps. Basic flowcharts are used to represent a simple process algorithm. A basic flowchart notation consists of rectangles (business processes), arrows (the flow of information, documents, etc.). The same notation is used in items such as the "decision", which allow you to do the branching. To indicate the start of the entire business process and its termination can be used the "Terminator" element. The advantages of Basic Flowchart are simplicity and clarity. With it you can quickly describe the business process steps. Creating of Basic Flowchart does not require any special knowledge, as easily understand by employees with different levels of education and IQ.Types of Flowchart — Overview
Picture: Types of Flowchart: Comprehensive Overview
Related Solution:
ConceptDraw
DIAGRAM 18