Objectives and Stages of Structured System Analysis and Design - Term Paper Example

[Structured System Analysis & Design Type the document sub Here [04/03 [In this work, we have discussed SSADM Techniques, SSADM Objectives and Stages, SSADM Steps, SSADM Techniques, SSADM Benefits and drawbacks and in the end Conclusion.] Contents 1 Introduction 3 2 SSADM Techniques 4 3 SSADM Objectives and Stages 5 4 SSADM Stages 6 5 SSADM Steps 6 6 SSADM Techniques 7 7 SSADM Benefits and Drawbacks 7 8 Conclusion 9 9 References 11 Full Paper Title Name University 1 Introduction In the UK, SSADM (Structure System Analysis & Design Method) is a most commonly used computer application for development purpose. Moreover, this application is mostly utilized for the government computing projects in UK. In Europe, it is widely being adopted by most public sectors than government organizations. The SSADM is in the public sector and is previously specified in British Standards as BS7738. (Structured systems analysis and design method.2007) The name “Structured Systems Analysis and Design Method” (SSADM) is a system advance to the investigation and design pertaining to information systems. SSADM was created for the CCTA, a UK government office is associated with the usability of SSADM technology in government sectors since 1980 and onwards. The names, “Structured Systems Analysis and Design Method” and “SSADM” are now Registered Trade Marks of the Office of Government Commerce (OGC), which is in the United Kingdom’s Treasury. SSADM is based on waterfall model to facilitate information system design reach the destination; SSADM can be derived to symbolize a base or foundation for precise and through documented approach for designing a system, and compare with up to date Rapid Application Development methods, one of the examples are DSDM. The SSADM is chasing the waterfall life cycle model that is staring from the likelihood to study physical design stage during development. One of the core features of the SSADM is that it includes intense involvement in the requirements analysis stage. The clients are made to sign off from every stage that is completed ensuring the requirements are fulfilled. Moreover, the users are offered simple and easy to understand data that includes a number of diagrammatic representations regarding the system. The SSADM will divide the development projects into several stages, modules, steps and tasks. Furthermore, the initial and primary model that is developed in SSADM is the data model. It is considered as a part of requirement gathering and incorporates thoroughly designed stages with detailed steps and processes. 2 SSADM Techniques In fact, the techniques that are used in SSADM are logical data modeling, data flow modeling and entity behavior modeling. Logical Data Modeling: This technique is involved in the process of identification, modulation and documentation of data, as it is the process of requirement gathering of the system. Likewise, data is supplementary divided in to associations and entities. Data Flow Modeling: This technique incorporates trailing the data flow in a machine hosting information. Likewise, procedures are examined evidently along with data stores, exterior entities and data progress. Entity Behavior Modeling: This technique incorporates identification and documentation of the events persuading every entity along with the series incorporating the activity of these events. The significant characteristics of SSADM are (Shelly & Rosenblatt, 2011): Separating a project into undersized modules that with well-defined aim and objectives. Constructive necessary specifications and system designs are used. Representation in terms of diagrams and other useful modeling procedures are adopted. Simple and essay methodology that is understood by customers and developers. Performing activities are in a proper series. 3 SSADM Objectives and Stages SSADM provides a framework to identify and define projects that are appropriate for SSADM project management. In actual, SSADM segregates projects associated with project development into small components, project stages along with different steps and processes. SSADM’s objectives are listed below: Improve project management and associated organization. Makes good and valuable use of knowledgeable and non-knowledgeable development employees. Ensures improved and valuable systems. Projects are flexible related to the loss of employees. Projects that are facilitated by computerized tools, for instance, integrated application engineering systems. For better communications among participants of project, a framework is created that covers all the facets of software development life-cycle, starting from the software feasibility stage to the production stage of an application physical design. In general, it is utilized with integrating other structured analysis methods. For example, PRINCE is an approach that is used for addressing extensive attributes of project management. Comprehensively, SSADM portrays a view similar to waterfall model for system development, where steps are defined in sequence i.e. one after another linked with each other to reach the next level. SSADM stages are mentioned below (Shelly & Rosenblatt, 2011): Feasibility Investigation of the current environment Business systems options Definition of requirements Technical system options Logical design Physical design 4 SSADM Stages SSADM defines an extensive use of processes, techniques, procedures and principles in every stage of the life cycle for saving and communicating the information into figures and diagrams. Likewise, SSADM is known to be the most ample model, as the distinctiveness associated with the projects is up to the task i.e. appropriateness is closely linked with project requirements. Moreover, CASE tools are also used for maintaining SSADM 5 SSADM Steps SSADM incorporates five steps, as they can be precisely broken down further into the following steps (Longworth, Nicholls, & National Computing, 1986): Feasibility study: To decide whether it is cost effective to go further on with the system and whether it is actually promising. Requirements Analysis: Identifying of the requirements and needs related to the system And modeling these requests in terms of the procedures carried out. Requirements Specification: The functional and non-functional necessities are determined in detail. Logical System Specification: Technical systems options are produced and the logical design of the system is created. This consist the design of update and enquiry processing. Physical Design: The logical system measurement and technical system specification is utilized to design a physical database and set of program specifications. For the above mentioned stages, SSADM demonstrates methods, processes and techniques for saving the collaborative information. Information includes both illustrative figures and representations via diagrams. 6 SSADM Techniques The 3 most significant techniques that are been utilized by SSADM are (Cutts, 1991): Logical Data Modeling. This defines the process of identification, modulation and documentation of data or information necessities of the system that is designed. The data is alienated into two segments i.e. entities and relationships. Data Flow Modeling. This is the process of distinguishing, modulation and documentation of data transfer and data movement in an information system. Data Flow Modeling observes these processes or activities that convert data from one type to another along with data stores, external entities and data flows. Entity Behavior Modeling. This is the process of identification, modulation and documentation associated with the events that portrays impact on each entity along with the sequence via occurrence of these events. 7 SSADM Benefits and Drawbacks The benefit of SSADM is that it utilizes three techniques in order to determine the information system viability. One of the major benefits of SSADM is the incorporation of three techniques that will determine viability of information systems. Likewise, the entity identification and their relationship in the system are verified by logical data modeling. Furthermore, data flow modeling technique demonstrates data modification from one state to another form, occupying space for data and entities that transmit it in the systems along with the routes that is responsible for data flows. In addition, event modeling credentials demonstrates the impact of these entities within the business and their information systems. Therefore, these three procedures and perspectives are offer the more complete and precise model. By examining and analyzing a thorough review of the system, the probability of minimizing information readiness at the initial stages of the project. Likewise, the occurrence in the system occurs due to poor design. Moreover, SSADM is regularly used in the United Kingdom; team members associated with the project are familiar with the processes and procedures. SSADM methodology is a structured approach that develops and deploys controls on all procedures pertaining to data creation. Likewise, this is the core objective of SSADM, as it gives slight room for mistakes and it is also the main reason of its adoption and popularity within the UK. However, the error free structure is linked to some constraints. One can predict that the necessities of the system may change at each stage during the software development process. As SSADM is constructed on the basis of data analysis, if any changes are identified after the analysis stage, system suggested by the data can be defective (Satzinger, Jackson, & Burd, 2008). Moreover, for supporting business, SSADM is closely aligned with critical business functions of an organization. Some of the attributes for SSADM supporting business functions includes enhanced quality by reviewing every stage of the software development process and meeting the customer requirements precisely by reviewing requirement analysis stage. After completing the given criteria, the time and volume must be adequate at disposal for the completion of every stage of the development process. Moreover, the radically changing situation in business because SSADM do not modifies the changes available in the specification after the completion of the review stage. For considering long term benefits of SSADM, overall quality of information services within the organization is enhanced. Likewise, SSADM use is also adopted by government organizations and initially it was developed to focus on three kinds of organizations and government projects, as these projects have adequate time and resources to align with the nature of SSADM methodology. The major drawback related to the SSADM system is that it takes more time as compared to other system. It is difficult for a business organization to generate the information system by a due date because SSADM takes too much time to analyze the projects. There is a huge suspension among the initiation of the project and the deployment of the system. If the staff members of any organization are not fully qualified in the SSADM techniques, the business will need to spend more period and currency on training their employees (Satzinger, Jackson, & Burd, 2008). 8 Conclusion SSADM provides numerous benefits as well as drawbacks in terms of delivering the projects on time. In order to develop a system for a medium-sized business organization, a comparatively small information system must be created. There are better solutions for the development of information system. On the contrary, there are limited resources available in a medium-sized business organization therefore; it should be considered utilizing an off-the-shelf product that is low cost and time consuming. Moreover, stages, objectives, steps, techniques, benefits and drawbacks are also discussed in detail. 9 References Cutts, G. (1991). Structured systems analysis and design methodology Blackwell Scientific Publications. Longworth, G., Nicholls, D., & National Computing, C. L. (1986). Structured systems analysis and design method (SSADM) manual NCC. Structured systems analysis and design method. (2007). Network Dictionary, , 465-465. Satzinger, J. W., Jackson, R. B., & Burd, S. D. (2008). Systems analysis and design in a changing world Course Technology/Cengage Learning. Shelly, G. B., & Rosenblatt, H. J. (2011). Systems analysis and design Course Technology Ptr. Read More