Rapid Application Development (RAD): Plan as you go

Long ago I came to the conclusion that very few things turn out as expected. That vision of the perfect plan never coming to complete fruition, leaving me frustrated and wondering what happened to change the expected outcome. I finally decided that planning too far ahead could be a waste of time and resources. I'm fairly laid back to begin with, so this "plan as you go" idea really appealed to me. Just relax and take things as they come, leaving my plans open and subject to change. There are advantages and disadvantages to this approach.

With Rapid Application Development, or RAD, having an outline of main requirements without pre-planning can be advantageous to a company. It can save time and money, as well as create an application more applicable to specific company needs. The requirement planning phase is short and results in a main goal, but does not include every step of how to get there. A workable prototype is developed quickly and passed to the user. The user provides feedback to the developer regarding usability and desired functionality. The application is then changed and enhanced, then passed back to the user. This reciprocation continues until the cutover phase, when everything is put in place and implemented. Early RAD systems had two primary disadvantages: reduced Scalability, and reduced features. Reduced scalability occurs because a RAD developed application starts as a prototype and evolves into a finished application (Select Business Solutions, Inc. 2009). Given the disadvantages, I still prefer the RAD development technique for most situations-It fits my thought process, and I have the same approach to my life.

Citations:

-What is Rapid Application Development? (RAD) | Analysis and Design. (n.d.). Retrieved September 26, 2009, from http://www.selectbs.com/adt/analysis-and-design/what-is-rapid-application development

None Listed. www.linearblue.com. Digital image. [agile_circle.jpg]. www.linearblue.com. 27 Sep. 2009

Feeling Insecure? System Design and Security

One of the steps in information system development involves system security. There are many points to consider when planning for the security of a system. One of the things to consider is the type of organization. While it is prudent to give the customers of a company the highest possible security when it comes to their personal information, the truth is that some information doesn't warrant the highest security available. As we look at a business plan, we can determine cost of security implementation vs. the risk. A balance has to be reached between the value of the information to the organization on the one hand and the cost of the personnel, administrative and technological security measures on the other hand. The security measures put in place need to be less expensive than the potential damage caused by the loss of confidentiality, integrity and availability of the information." (EDP Audit Committee International Organisation of Supreme Audit Institutions October 1995.) It's obvious that a small private owned pet store will require less security than a large financial investment brokerage firm.

The information stored on the system will determine how aggressive and how often the system will be attacked. Financial and personal information that can be used to commit fraud is highly sought after by crackers who can sell the information or make use of it for their own gain.

Another consideration is the popularity of the organization. Microsoft is despised by many as being a greedy, corporate giant that destroys competitors in an attempt to create something close to a monopoly. This reputation has caused the cracker community to attack Microsoft systems regularly, exposing the flaws in the software and turning many towards other, safer alternatives. This has cost the organization product sales revenue, as well as large amounts of money invested in security updates and patches developed and released to fix the weaknesses.

When working with a company manager in the analysis and design of an information system, often times it is all about the profit, or the "bottom line". It may be difficult at times to see a return on the investment into security, but the results of inadequate security can be disastrous and cost much more than the initial investment into adequate security.

Creative Design

    There is an art to information system design. There must be a vision of the desired result, and what the purpose is in creating the work. There are multiple tools to choose from for the development of a system, and you utilize the tools that best work for your purpose. When the blank canvas is looked upon, it is best to visualize the steps that must be made to achieve the envisioned outcome. After taking a few steps, it is beneficial to stand back and observe your progress, gauging the effects of your work. If the work is not moving in the desired direction, the steps can be reevaluated and changed according to the need of the business. There are times when the end result does not have the impact of the original vision, and the system is scrapped and a newly stretched canvas is placed upon the easel.

    I see system design as a process that involves creativity as well as technical knowledge. The process of problem solving, including prototyping and finding the best approach for a needed result, requires both sides of the brain. That is why I am interested in system analysis and design…it is a challenge that will bring growth to both my logic and creativity.

Learning Model

The LDSBC learning model consists of steps and principles that enhance and solidify the information we are learning. These principles include: 1)Prepare, 2)Teach One Another, and 3) Ponder and Prove. These three steps ensure an education that will be applicable to the job world which we will be entering in the near future. In D&C section 88 verses 77-80 the Lord speaks of teaching one another and preparation. The principles of the learning model are the same principles we should use when studying the gospel.

We must prepare ourselves to learn. We can pray for increased capacity and understanding, and invite the Spirit. The Holy Ghost will bear witness to truth, and once we experience that witness, the knowledge is ours. In the application of this learning model, we can see that when we share our knowledge with another student, our knowledge is solidified. As we teach each other we help build others weaknesses and have our weaknesses strengthened. It is also important to ponder and prove. As I stated before, the Spirit will hear witness if we take the time to ponder the information we have been given.

My first Blog

Hey.