Case Study: System Development

System development is a procedure in which programmers with organization contribution compose codes to fix an issue that deal with the organization system or automate a procedure. There are 3 significant systems development techniques that been used to solve systems' problems. The system advancement strategies are SDLC (Systems Development Life Process), JAD (Joint Application Development), and RAD (Quick Application Development). SDLC provides tools for managing details within large development tasks that resolve structured issues. JAD enables the recognition, definition, and execution of information infrastructures.

RAD supports the iteration and versatility required for developing robust service process assistance(Osborn, 1995). In this case study, the supervisor been asked to create, develop, and set up a Client Management Details System for a medical center in which 3 physicians practice basic medication.

This system has to be operational in 6 months. There is one person in the center personnel who is fairly well informed about info innovation. Thus, the supervisor needs to identify which system advancement methods will utilize to fix this issue.

Get quality help now

KarrieWrites

Verified writer

Proficient in: Business

5 (339)

“ KarrieWrites did such a phenomenal job on this assignment! He completed it prior to its deadline and was thorough and informative. ”

+84 relevant experts are online

Hire writer

To choose the proper development system, the supervisor need to use a process which consists of s (1) defining requirements, (2) designing an information system to fit those requirements, (3) constructing the code to provide that system, and (4) screening to see whether the code works and the system gets the job done it was meant to do(Osborn, 1995). The requirement for this case study is to create and develop and set up a Management Details System for a medical clinic that has three physicians within 6 months.

Based on that, this process will take longer if we use the SDLC which is the traditional method that need narrative descriptions, data definitions, and sample screens.

Moreover, producing a thorough, often multi-volume description of system requirements can become such a time-consuming task that it begins to extend the expected life of a development project. On the other hand, JAD tends to rely on data models to provide requirements definition and prototypes to capture final design details. The data modeling can produce thorough system specifications more quickly than SDLC narratives, especially through the use of computer-aided software engineering (CASE) tools.

The RAD relies on a series of iterative prototypes to specify and document requirements. The technique reverses the scheduling emphasis normally found in SDLC projects by setting a rolling series of release dates and dynamically adjusting system features to fit. Iterating prototypes gives requirements the opportunity to evolve and the flexibility to change if needed(Osborn, 1995). Since the project is for small clinic, which mean that the budget is limited. SDLC to the use of expensive mainframes to understand transactions, JAD to the need for managing data distribution following the advent of minicomputers, and RAD to the development of business process support based on networked client/server workstations. SDLC provides tools for controlling details within large development projects that solve structured problems.

JAD enables the identification, definition, and implementation of information infrastructures. RAD supports the iteration and flexibility necessary to building robust business process support. Thus, based on the information that discussed earlier, I recommend using the RAD method because the clinic is small one which needs inexpensive system and the system will need support especially that there is only one person who informed about using information technology. In addition, the time limits that clinic has will fit also the RAD method. Literature showed that RAD proves most useful for systems support of unstructured business processes. This not means that this system will limit the business because when the business grows up the system can move for more structure system(Osborn, 1995).

References
Glandon, G., Smaltz, D. & Slovensky, D. (2012). Information Systems for Healthcare Management. Chicago, IL: Health Administration Press. Osborn, C. (1995). SDLC, JAD, and RAD: Finding the Right Hammer. Center for Information Management Studies, Working Paper 95-07.