Systems Development and Implementation

Authors Avatar

Systems Development and Implementation

By Group C8:

Amit Anand (PG040012)

Gautam Waingankar (PG040055)

Mithun Banerjee (PG040095)

Sidharth Bhargava (PG040184)

Suraj Jadhav (PG040205)

Vineet Agrawal (PG040043)



Systems Development and Implementation

  1. Executive Summary

The report examines systems development and implementation with focus on the software value chain. It analyses the impact of marketplace issues on software design and the ways and means to create value for the customers. It takes a look at object oriented software development, a modular software development technique that has been widely adopted. It views the future trends in software development and the pros and cons of making, buying or renting software. Finally, it examines the two ways of implementing systems and their relative merits and demerits.

  1. Sources of value for the user

The primary purpose of software is to serve the needs of its end users. Some of the generic value factors from the perspective of the user are as follows

  • Productivity and impact – The tangible impact an application has on the organization such as improving productivity, reducing time to accomplish tasks, better management of knowledge assets etc.
  • Network effects – The increase in value of the application with the increase in number of users that use the application.
  • Usage – Higher the usage (more number of users and more use per user), higher the value.
  • Quality and performance – Defects observed in the system, the volume that the system can handle and its response time are some of the factors.
  • Usability – Users’ perception of how easy it is to use the application
  • Flexibility and extensibility – Flexibility in meeting changing requirements is valued, especially in business applications.
  • Composability - A single closed software solution offers less value than one that can be combined with other solutions to achieve greater functionality. This is called the composability of complementary software solutions.
  1. The software value chain

  1. Applications and infrastructure

The most fundamental architectural concept in software is the decomposition into application and infrastructure. With some notable exceptions, firms in the industry generally specialize in one or the other. The core competencies for providing applications and providing infrastructure are different. Applications focus the value proposition on end users, and infrastructure provides value primarily to application developers and to operators. Applications are valued most of all for functionality and usability; their performance and technical characteristics are more dependent on infrastructure. It is advantageous to move as much technical capability to the infrastructure as possible, so application developers can focus on user needs. Considering the separation of application from infrastructure, there are two supplier value chains as shown in the figure below.

  1. Industry organization

Since companies tend to form around individual units of value that enhance internal synergies and exploit common expertise, industrial organization can be thought of as a partitioning of the value chain into distinct companies. In these terms, there are natural businesses formed by partitioning of the value chain as shown in the figure below

The application software supplier typically bundles the analysis and development functions, working closely with the end-user organization to define requirements.

Join now!

The infrastructure software supplier must be cognizant of the requirements imposed by a wide range of applications. The system integrator specializes in provisioning. This role takes responsibility for acquiring software from both application and infrastructure suppliers (usually more than one), does whatever is necessary to make it work together, and installs and tests the software. Some programming is typically involved as well.

Another role in provisioning is the consultant, who helps the end-user organization rework the organization and business processes around the software, and often helps configure the software to the needs of the particular end-user. Operation is the ...

This is a preview of the whole essay