Planning for System Development

Planning for system development is a critical managerial responsibility that ensures information technology (IT) initiatives are aligned with organizational goals, resources, and long-term strategy. A well-defined IT development plan enables management to approach software and system development projects in a structured, controlled, and cost-effective manner. Without proper planning, system development efforts can lead to cost overruns, delayed delivery, and solutions that fail to meet business needs.

At the outset, management must address several fundamental questions related to system and software development:

• Scope of development: Whether the system will cover selected functional areas or the entire organization.
• Execution approach: Whether development will be carried out by an in-house team or through external consultants.
• Resource commitment: The amount of time, budget, and human resources that can be allocated.
• Development policy: Whether a formal, documented software development model or methodology will be followed.

IT planning provides a structured means of understanding and managing the impact of existing and emerging technologies on an organization. Through systematic planning, relevant technologies are identified, evaluated, and aligned with broader business goals. Based on a comparative assessment of available technologies, management can determine the most appropriate technological direction for the organization.

Business planning has long been recognized as a core responsibility of management. Plans establish a clear direction and framework for action by defining organizational goals, required activities, expected benefits, resource requirements, and timelines. Increasingly, information technology not only supports business strategy but also drives innovation, competitive advantage, and operational transformation. As a result, IT planning has become an integral part of the overall business planning process. If new technological opportunities emerge after a business plan has been finalized, the plan should be revisited and revised to fully leverage these opportunities.

17.1 Phases of IT Planning

Although IT plans vary across organizations, the underlying planning process and activities remain broadly similar. Effective IT planning typically proceeds through the following phases:

Orientation

This initial phase establishes the scope, objectives, methodology, and planning techniques to be applied. It defines the boundaries of the IT plan and clarifies expectations among stakeholders.

Assessment

The assessment phase focuses on understanding both business and technological realities. Key activities include:

• Confirming business direction, objectives, and critical success factors
• Reviewing current and emerging technology trends
• Identifying future information and system requirements
• Inventorying existing information systems and infrastructure
• Assessing gaps between current capabilities and future needs

By the end of this phase, management should have a clear and well-documented understanding of current and future business requirements.

Strategic Plan

This phase focuses on defining the long-term vision for information technology within the organization. It establishes how IT will support or enable business strategy and outlines high-level initiatives required to achieve the desired future state.

Tactical Plan

The tactical plan translates selected strategies into a series of specific projects. These projects are prioritized and scheduled based on resource availability, urgency, and business impact. The planning process concludes with the establishment of monitoring and control mechanisms to track progress and performance.

What Is System Development?

System development refers to the structured process of designing, building, implementing, and maintaining hardware and software systems to achieve effective and efficient information processing. Information systems are developed to meet specific organizational needs and objectives.

System development is typically initiated for one of the following reasons:

• A manual information system needs to be computerized to improve efficiency and accuracy.
• An existing computerized system must be replaced due to performance limitations, changing business needs, or the availability of more advanced and user-friendly technologies.

In both cases, the fundamental phases of system development remain largely the same. However, the depth of system study, analysis, and design may vary depending on whether the existing system is manual or computerized. To manage complexity and risk, organizations rely on formal system development models and methodologies.

17.2 Models Used for System Development

In the early days of computing, software development often involved a single programmer writing code to automate a specific task. Today, enterprise systems are highly complex and require collaboration among system architects, business analysts, developers, testers, and end users. To manage this complexity, various system development models have been introduced.

The most widely recognized of these models is the System Development Life Cycle (SDLC), also known as lifecycle models. These models provide a structured framework for planning, building, and maintaining information systems.

17.3 System Development Life Cycle (SDLC)

The System Development Life Cycle (SDLC) is a comprehensive process for developing information systems through a sequence of well-defined phases, starting from the investigation of initial requirements and continuing through analysis, design, implementation, operation, and maintenance. SDLC is also referred to as application development or information systems development.

SDLC adopts a systems approach to problem solving and provides:

• A clear structure for development activities
• Standardized methods and techniques
• Effective controls to manage quality and risk
• Practical checklists to ensure completeness

Project Life Cycle vs. SDLC

While system development can be viewed as a project, it differs from typical projects in a fundamental way. Most projects have a definite end point, whereas system development includes ongoing maintenance, enhancement, and eventual replacement. SDLC explicitly accounts for this extended lifecycle, making it particularly suitable for managing information systems.

17.4 Types of System Development Life Cycle Models

Several SDLC models have been proposed over time. While they differ in structure and emphasis, all share the same underlying objective: delivering high-quality systems that meet user and business requirements.

Waterfall Model

Also known as the classic or linear sequential model, the waterfall model views development as a series of distinct phases flowing sequentially downward. Each phase must be completed before the next begins, making this model suitable for well-defined and stable requirements.

Incremental Model

In the incremental model, software is constructed in a series of small, manageable builds. Each build delivers a specific set of functional capabilities that are designed, implemented, integrated, and tested as a whole. This approach allows for earlier delivery of value and easier management of complexity.

Iterative Model

Iterative models emphasize continuous user feedback and refinement. Prototypes are often developed and evaluated at each stage, allowing requirements and solutions to evolve based on real-world input.

Need Assessment

Information systems are generally developed in response to identified problems or opportunities. During need assessment, stakeholders attempt to develop a shared understanding of the problem and the desired outcomes. Problems may be structured or unstructured, and this classification influences the approach to system development.

For larger or high-impact systems, formal Terms of Reference (TOR) may be prepared and approved by a steering or project committee. TOR typically covers:

• Investigation of the existing system
• Definition of system requirements
• Specification of performance criteria
• Preliminary cost and budget estimates
• Draft implementation plan

Achieving stakeholder agreement on the problem definition and solution parameters is one of the most critical success factors at this stage.

Entry and Feasibility Study

The purpose of the entry and feasibility study is to secure commitment to change and evaluate whether cost-effective solutions are available. The level of effort required depends on the scale and impact of the proposed system.

In small, localized initiatives, users may be sufficiently motivated to design and implement solutions themselves. In contrast, large-scale systems with organization-wide impact require careful change management, stakeholder engagement, and collaborative evaluation.

A feasibility study team is typically formed and may include:

• Representatives from affected departments
• A system analyst with expertise in systems design
• Individuals with in-depth knowledge of organizational processes and information needs
• External consultants, where specialized expertise is required

Throughout system development planning and documentation, clarity and accuracy of requirements are essential. Tools such as a reliable online word counter can help teams review and standardize requirement documents, ensuring consistency and completeness across planning artifacts.

Effective planning for system development reduces risk, improves alignment between technology and business strategy, and lays a strong foundation for successful information systems implementation.