Application development for the digital firm

Application Development for the Digital Firm

Rapid Application Development (RAD)

• A prototype is created as part of an iterative development process to address specific design challenges. A very brief development cycle is the main focus of this incremental software development process approach. It applies strategies like:
  • Tools for creating GUIs with visual programming
  • Developing a crucial system component iteratively
  • Close collaboration between end users and an IS specialist

Phases in RAD Model

• Requirement Planning
  • Tasks related to requirement planning are completed at this phase. Business demands project scope and system requirements are agreed upon by users, managers, and IT personnel. Get permission to go on.
• Users Description
  • A thorough system area model, a conceptual system design, and an implementation strategy are produced during this phase. The analysis and design tasks related with this stage are carried out by end users taking part in Joint Application Design (JAD) workshops.
• Construction Phase
  • In the building phase, the proposed system's design—which was first presented in the user description phase—is finished, and the application software needed to put it into practice is created and put through testing. Additionally, preparations are made for the system's move to production state.
• Cut Over
  • In the cut over phase, the system created during the construction phase is put into use. Developers are now preparing the new system with old data and coaching users on how to easily utilize the new application. Additionally, they offer assistance in resolving any issues that arise right away after the program is put into use.
• Advantages
  • Shortened process for obtaining customer satisfaction.
  • It boosts the product's productivity.
  • The user's feedback is available at the beginning.
• Disadvantages
  • High level expertise and specialization are needed. The expense of manufacture is high.
  • Extremely frequent technical risk

Trint Application Development (TAD)

As the name suggests, the TAD model of the software design process brings people together (or gathers them) in one specific place. users, developers, analysts, and designer representatives. The primary goal of this model is to create a workable design. This model is used to construct the basic system architecture and speed up the development of information requirements.

• Agile Development
  • It is a collection of software development techniques in which self-organizing, cross-functional teams work together to produce requirements and solutions. By dividing a major project into multiple smaller projects, it emphasizes on producing working software quickly. It encourages teamwork and promotes spoken communication over written documentation, as well as quicker decision-making.
• Component Based Development
  • Construction and deployment of a software system made up of individual components. a collection of items that offer software for related tasks and can be integrated to produce complex commercial applications. The separation of concerns is the focus of this subfield of software engineering (separating of computer program into different section in respect of the wide ranging functionality available throughout given software system). For creating, putting into practice, and combining loosely linked, independent components into systems, it is a reuse technique.

Alternative System Building Methods

• Traditional System Lifecycle
  • Earliest method of information system construction
  • Phased approach, formal step for device development (following the "waterfall" method), and task completion at each stage.
  • Keep the formal level distinction between the end user and the IS specialist.
  • The emphasis is on formal specifications and paper work.
  • Less versatile, time-consuming, and expensive
     
• Prototyping
  • A user and a developer are both involved in the prototyping model. Here, the developer conducts a user interview and designs a preliminary system. The user makes modifications and works with the prototype. Until the user is pleased, this process is repeated. Prototyping is the process of creating such a paper-based model, improving it, and testing it again. It is a prototype of IS that is being used for testing and demonstration. Prototyping is the practice of creating a prototype.
• Steps in Prototyping Model
  • Identify the user's needs
  • Create a first prototype
  • Make a prototype
  • Update and improve the prototype or implementation
• Advantages
  • In the first phase, a partially finished product is built. Users have the opportunity to observe the product early in its lifecycle and can provide the appropriate feedback as a result.
  • Adding new requirements is simple.
  • A more active user participation in system development is possible.
  • Users' expectations make implementation simpler
  • Flexible
• Disadvantages
  • The iterative process of prototype demonstration and revisions might last a long time if improperly handled.
  • The end user may lose interest in the project if they are not satisfied with the initial prototype.

End User Development

uses 4GL to enable system development by end users with little to no assistance from technical experts. As compared to traditional language, 4GL are less procedural. 4GL prioritizes user needs over operational details. Query languages, report generators, graphics languages, and application generators are a few examples of computer software tools.

• Advantages
  • More quick completion of projects
  • High levels of satisfaction and user involvement
• Disadvantages
  • Not intended for applications requiring a lot of processing
  • Insufficient testing, management, control, and documentation
  • A loss of data control

Application Software Packages

• A group of prewritten, precoded application software applications that are commercially accessible for sale or rental make up the strategy for constructing information systems. Application software packages are available for both straightforward tasks and intricate mainframe systems. System design, maintenance, and support costs are decreased by the usage of software packages in conjunction with suppliers, support personnel, and documentation. Some software package providers include features for customisation, enabling a package to be changed to fulfill particular needs without compromising the software's integrity.
• Function, flexibility, user-friendliness, software resources, hardware resources, database needs, installation and maintenance effort, documentation, cost, etc. are the important factors to consider while assessing application software packages.
• The Request for Proposal (RFP), a comprehensive list of inquiries sent to providers of package software, serves as the foundation for the evaluation process for packages.

Outsourcing

Utilizing an outside party to create or run a company's information system is known as outsourcing. Either a software package or a custom-built system may be used.

Types of Outsourcing

• Cloud and Saas Provider
  • Companies that subscribe employ hardware and software that vendors provide.
• External Vendor
  • Hired to design and develop software
• Domestic Outsourcing
  • Driven by the company's requirement for increased resources and capabilities.
• Off-Shore Outsourcing
  • Driven by a desire to save money
• Advantages
  • Be flexible with the organization's IT requirements.
• Disadvantages
  • Identifying and choosing vendors at a hidden cost
  • Excessive reliance on outside providers

Reference

Laudon, Laudon, "Management Information Systems Managing the Digital Firm", twelfth edition