There Are Two Main Different Forms of Communication, Written and Oral.

To communicate effectively, you must know the five questions of communication. These questions are why, who, what, when, and how. This essentially means that you must know why you are communicating and what point you want to get across in the first place. You must also understand who you are communicating with to determine proper etiquette when speaking. You must know what exactly you’re speaking about and how much detail to go into. You also must know when the proper time for you is to speak, and lastly, how to approach the communication.

There are two main different forms of communication, written and oral. It is crucial to not make written mistakes in communication as these cannot be easily alleviated as oral speaking can and can easily be unprofessional. With electronic communication easily becoming the main form of communication, proper etiquette must be maintained across various forms of communication, i.e. instant messaging, email, etc.

I personally learned a lot in this lesson when pertaining to essentially all the “rules” of communication. There are a lot of tips that, while can be instinct for others, can have a learning curve for a lot of people. An easy example is how many times I’ve seen people write emails to professors and employers in the way that they would text friends, with abbreviations and slang.

The SDLC, systems development life cycle, by definition, is the series of phases used by structured analysis. The phases are systems planning, systems analysis, systems design, systems implementation, and systems security and support. This process is key towards a successful rollout of a new design or feature.

The planning phase is the initial step and starts with a request towards the developer or department of a change wanted in a system. Once the developer sees the issue requested, the systems analysis phase starts, which begins modelling of the new solution. Questionnaires and other observation means are used to help accelerate the modelling of the solution, and a system requirements document is then made. The next step is the systems design phase, in which the solution will start to be physically modelled on the road to be implemented. All the features will start to show and be tested, and the system design specification will be developed. Next is the systems implementation phase, in which the solution will reach its finishing stages and eventually be marked as final. Eventually, it will be rolled out to purchasers or others, and will include an evaluation for help with the last step. The last step is the systems support and security phase, while using evaluation from the systems implementation to help accelerate it, is basically maintenance to help correct errors in the original implementation as well as enhancing the overall experience.

Object-oriented analysis comes in when a combination is needed for all the data and processes of a system. When these processes and data are combined, they are called objects. The elements of object-oriented analysis, commonly abbreviated OOA or O-O, are the objects, the classes, and the properties.

As mentioned previously, objects are the combination of the data and processes. Next are the classes, which are groups that contain similar objects paired into a single class. Next are the properties, which are characteristics that objects themselves have, or are granted to by their respective classes. An example of all of this put together can essentially be looked at by two different types of hamburgers. The “Hamburger” class can include two hamburger buns and a beef patty. If we extend the Hamburger class to include two other objects, i.e. a Whopper and a Big Mac, they will inherit the properties of the hamburger class, the two buns and patty, however they will also have their own properties with their own respective toppings and condiments not seen on the other class.

A systems analyst is the person who overall assesses a company’s systems. They evaluate the condition of their maintained systems by consistently investigating the integrity of it and interacting with the users around it. The primary role of a system’s analyst is to help develop systems for businesses. They do this by understanding the problems offered by businesses and then offering their findings to programmers in a way they can understand.

The goal of the analyst is to prevent disasters from ever happening, and if they do, to quickly fix any problem that arises. This needs constant communication between the business and the analyst, as well as constant monitoring of systems. This means that the analyst needs skills far beyond just technical knowledge, they also need the proper communication etiquette necessary to get their job done.

Everything in everyday life has a process, whether it is a simple or a complicated task. Not every process is defined by a transaction that takes place at a store or grading a student’s assignment. Even something as simple as picking up a sheet of paper can have a process that starts in someone having to get