Reference no: EM131114869

Question:

Prototyping, joint application design (JAD), and rapid application development (RAD) are among the different approaches to streamline the systems analysis and design process. While these are considered methodologies, their function is to provide a framework for shorter development time.

Prototyping

Prototyping is sometimes used to help validate a design and is especially useful when the desired system is complex or has undefined or unclear requirements. A prototype application is often built to highlight one aspect of the new system, in order to give the decision-maker enough of a view to determine whether the design meets requirements. A website design prototype, for example, might show a few sample pages with different color combinations and just enough hyperlinks to help the end user decide other elements of the design such as the flow from one function to the next. Prototyping, while helpful, can be very expensive if too much functionality is built that must later change. There is also the risk that the external view will be taken to literally by end users who may reject the final product.

Simulation

Simulation is often used to validate a design, by projecting the transformation of information as it flows through a system. Simulation might be used, for example, in an accounting system, to understand how a customer's account will be handled as it ages from current to 60 days past due. Such processes will be automatically triggered at 30 days (i.e. monthly statement), 60 days (reminder notice), transmit to the collection agency (> 90 days past due). Test cases identified during simulation will likely be used during the testing phase after the system has been constructed. Simulation, while valuable, can lead to over emphasis on a few scenarios while neglecting the design of other functions of the new system.

Rapid Application Development (RAD)

RAD is an object-oriented approach to systems development and includes a method of development as well as software tools. There are three phases to RAD: requirements planning, design workshop, and implementation phase. Once requirements are gathered, the design workshop phase begins, which is very intensive in user participation with IT developers. During this phase, users respond to a system prototype, and analysts refine and design modules using software tools such as CASE tools for development. RAD must have experienced analysts and developers since development is accelerated. Usually RAD development lasts 60-days, and it can be done in conjunction with prototypes. By the time the RAD workshop takes place, the users have established ownership and acceptance of the new system.

Joint Application Development (JAD)

JAD was developed by IBM to cut the time required by personal interviews and to improve the quality of requirements gathering. Through a participative process, the users and IT can create a closer collaboration to develop the new system. Although JAD can be substituted for personal interviews, it has been employed to accomplish requirements analysis and to design the user interface jointly in a group setting. JAD requires specialized skills on the part of the analyst and a commitment on part of the organization to undertake this approach. JAD can be very effective if the appropriate user and IT team are invited to the sessions. One of the keys to a successful JAD workshop is laying the groundwork through planning. If all possible, it is recommended to hold offsite sessions away from the organization in comfortable surroundings. JAD sessions must be scheduled when all participants are committed to attend. There are some drawbacks such as holding sessions for long periods of time, lack of reports and documentation, and lack of skills and company culture. The drawbacks should be weighted when making the decision to use traditional one-to-one interviews or use JAD.

Selecting the Appropriate Development Methodology is an important decision after a project has been approved. Since there are many methodologies, the first challenge faced by analysts is to select which methodology to use. Choosing a methodology is not simple, because no one methodology is always best (if it were, we'd simply use it everywhere!). Many organizations have standards and policies to guide the choice of methodology. You will find that organizations range from having one "approved" methodology, to having several methodology options, to having no formal policies at all.

The PPT below summarizes some important methodology selection criteria. One important item not discussed in this figure is the degree of experience of the analyst team. Many of the RAD-based methodologies require the use of "new" tools and techniques that have a significant learning curve. Often these tools and techniques increase the complexity of the project and require extra time for learning; however, once they are adopted and the team becomes experienced, the tools and techniques can significantly increase the speed in which the methodology can deliver a final system.

Required Reading

Dennis, A., Wixom, B., & Tegarden, D. (2005). Introduction to Systems Analysis and Design. [PPT file].

Retrieved from https://www.cs.fsu.edu/~baker/swe2/restricted/notes/dennis/ch02.ppt

Valacich, J., George, J, & Hoffer, J. (2012). Modern Systems Analysis and Design. Chapter Flashcard sets. Chapter 2. [Audio file]. Retrieved from https://quizlet.com/15166289/systems-analysis-and-design-chapter-2-flash-cards/

Suppose you are an analyst for the RTech Software Consulting Company (RSCC), a large consulting firm with offices around the world. The company wants to build a knowledge management system that can identify and track the expertise of individual consultants anywhere in the world based on their education and the various consulting projects on which they have worked. Assume that this is a new idea that has never before been attempted in RSCC or elsewhere. RSCC has an international network, but the offices in each country may use somewhat different hardware and software. RSCC management wants the system up and running within a year.

What type of methodology would you recommend RSCC use? Why? Write this assignment in 2-3 pages.

References and proper citing per apa format a must