Loading...

Messages

Proposals

Stuck in your homework and missing deadline?

Get Urgent Help In Your Essays, Assignments, Homeworks, Dissertation, Thesis Or Coursework Writing

100% Plagiarism Free Writing - Free Turnitin Report - Professional And Experienced Writers - 24/7 Online Support

Abstract of Structured System Analysis and Design Method

Category: Computer Sciences Paper Type: Online Exam | Quiz | Test Reference: MLA Words: 1100

Structured system analysis and design method or also known as SSADM define as a set of principles meant for the analysis and also application design. This type of system typically utilizes a formal methodical technique towards the analysis as well as the design of information systems. This system has been applied by various commercial organizations, specialists, educational businesses, and also some developers (Sajja).

1.      Differentiate between the object-oriented and structured approaches. What are the characteristics of each?

A structured model is a traditional model that still being used in project management. Even though this model has the capability to solve moderately complicated programs, but it is considered to be a less secure one, due to the data cannot be hidden. A structured model is also known to deliver some function that less reusability because of their fixed nature and less flexibility. The main features of this structured model are that they still use traditional programming along with the standard stage procedures of analysis, design, realization, and also testing. On the other hand, an object-oriented design typically uses various different types of the amalgamated modeling language, and also includes some UML diagrams, in order to model any solution. The main feature of an object-oriented model is located on its emphasis and implementation of data structure slightly than technical structure. For this reason, this object-oriented model depends on the UML programming language.

2.      How do the activities of systems analysis and design differ depending on the methodology?

The customary methodology lifecycle is a straightforward model that integrates some characteristics such as phases, requirements, analysis, design application, and finally, testing. In the stage stages of planning and analysis, the scalability and software reusability of the project will be considered by the analysts. Therefore, we can consider that an object-oriented model will be a more appropriate and suitable model rather than a structured model. In addition to this, the functional system within and object-oriented might be either active or static. A methodology is the foundation of the different activities of system analysis and design. In fact, in this object-oriented model, the analysts are freer to modify anything to carry on the project, while a structured model will typically limit them.

3.      How would the role of a systems analyst differ based on the chosen methodology?

A systems analyst would take a look at the company’s computer systems along with their procedures, measures, and also the type of designs with a purpose to make it more effective and efficient. Gathering and analyzing what the requirements intended for a new system are the most fundamental tasks of the system analyst. For this reason, the role of a system analyst would differ and based on the chosen methodology since they are actually the vanguards of the model. In both structured and object-oriented models, the objectives of the analyst will have to meet with the main goals made by the entire stakeholders (Khan, Khalid and Haq).

4.      Do you agree or disagree with the conclusions of the articles' authors in their evaluation of structured and object-oriented system analysis and design methodologies? Why?

According to Irit Hadar (2013), object-oriented is actually refers to a programming pattern that presents as a set of concepts that is sustained by a variety of different languages (Hadar). I agree with the author since an object-oriented model is basically one big program in which each program will represent a different portion of the application, and each of these objects has its own logic and data, also, they interact with one another.

            Another journal that is written by proposed that the Unified Modeling Language or UML has turned out to become the standard modeling language to be used in object-oriented models (Vogel-Heuser, Braun and Kormann). I agree with this conclusion, and I also want to add that this Unified Modeling Language has a number of diagrams, whereas each of them has different functions. For example, a class diagram in UML has its function to present the different objects, their interactions, behaviors, and also activities. Meanwhile, an activity diagram will present the data flow between the processes inside the system.

5.      Why might an organization prefer one approach over the other? What types of circumstances may affect their choice?

Every single system definitely has its own advantages. Some analysts might able to take advantages provided by object-oriented analysis and design by make the use of the Unified Modeling Language or UML which will enable a breakdown of complex designs into a further manageable and convenient design. The analysts who use an object-oriented model also will able to modify the design and also reprocess existing software as well. Thus, it basically depends on the size of the company itself along with the project’s scale to choose the most suitable and appropriate model to be used. However, the more preferred one is an object-oriented model due to it is quite scalable (Cantor).

6.      As a system analyst, which would you prefer? Why?

If I would be trusted as a system analyst for a project, I would prefer to use an object-oriented analysis and design since this model has the techniques to represent the fundamental concepts in the domain issue of the project. In addition to this, an object-oriented model also provides various UML diagrams to model each solution.

7.      Can the two approaches be successfully combined? Explain

The systems’ analysts in these modern days are typically referred merely in an object-oriented model and have only a few interests in using a structured model. At this point, we can see that there is a shift in how the system analysts are applying a model that they think is the most appropriate one for their companies. Thus, it might be impossible to combine these two approaches successfully since the systems analysts will only choose to use one of them. 

References of Structured System Analysis and Design Method

Cantor, Murray. "Object-oriented project management with UML." (2011).

Hadar, Irit. "When intuition and logic clash: The case of the object-oriented paradigm." Science of Computer Programming (2013): 1407-1426.

Khan, Muhammad Naeem Ahmed, Muhammad Khalid and Sami ul Haq. "Review of requirements management issues in software development." International Journal of Modern Education and Computer Science (2013).

Sajja, Priti Srinivas. Essence of Systems Analysis and Design: A Workbook Approach. Springer, 2017.

Vogel-Heuser, Birgit, et al. "Implementation and evaluation of UML as modeling notation in object oriented software engineering for machine and plant automation." IFAC Proceedings Volumes (2011): 9151-9157.

 

 

Our Top Online Essay Writers.

Discuss your homework for free! Start chat

Top Class Engineers

ONLINE

Top Class Engineers

1218 Orders Completed

Quality Assignments

ONLINE

Quality Assignments

0 Orders Completed

Coursework Assignment Help

ONLINE

Coursework Assignment Help

63 Orders Completed