NAME: CHARLES ONYEKA NWUNE

MATRICULATION NUMBER: DBS/23/MBA/00565

COURSE CODE: MBA 8312

COURSE NAME: MANAGEMENT INFORMATION

As a newly appointed manager at a leading finance firm. You have been asked with presenting to
the organization board of directors an overview of the system development lifecycle. The board
composed primarily of non-technical members, seek to understand how the system development
lifecycle ensures a successful delivery of high-quality information systems.

A. Define SDLC in a way that is clear and accessible to non-technical stakeholders.

The System Development Lifecycle (SDLC) is a methodical process utilized in the development
and upkeep of any Information Systems (IS). Consider it a checklist that outlines each step
required for developing a software application or system. By following this lifecycle, systems are
developed effectively, aligned with business goals, and completed within the specified timeframe
and budget constraints. It also serves to ensure that the developed system meets the quality
expectations, is operational, and provides value to the organization.

To put it simply or in lame man terms to the non-technical stakeholders, SDLC is like a strategy
when constructing a house; you make blueprints of the house (planning and design), make
purchases for the house (development), and once it’s finished, you test whether everything is in
check before finally moving in (deployment). It is a systematic and well thought out approach to
mitigate potential risks and guarantee that the product is successfully delivered.

B. Explain key phases of the system development lifecycle detailing the purpose and
significance of each phase in the context of system development
1. Planning Phase

This phase is very fundamental as it entails, the reason why an information system is built and
how the team members can come together to build the system would be bult
Purpose: The goal of this phase is to define the scope and purpose of the project, identify
necessary resources, and create a roadmap for execution.
Significance: Planning is critical because it sets the foundation for the entire project. Without
proper planning, the project could face unnecessary delays, budget overruns, or unclear goals.
It's the stage where risks are first identified, and a strategic approach is taken to manage them.
It is important because at this stage, techniques are put in place to help the project team control
and direct the project through the entire SDLC.

2. Analysis
Purpose: In this phase, the project team gathers detailed information about what the system
needs to do, and assesses whether it's feasible in terms of budget, resources, and technical
capacity.
Significance: This is where the business requirements are clarified, ensuring that what the
business needs from the system is understood. It’s crucial to avoid misunderstandings later
in the project that could lead to costly changes or missed expectations. In this phase, the
proposal is presented to the project sponsor and other key individuals who now decide
whether it’s reasonable enough to go on with the project.

3. Design
Purpose: This phase focuses on creating a detailed design of how the system will work,
including the user interface, data flow, and architecture. At this stage it is also discussed
whether system would be developed by the company or outsourced.
Significance: The design phase is the map to development. A well-planned design ensures
the system will function as required and be able to expand and scale in the future. It's also
where we iron out any technical restrictions or boundaries that need to be resolved before
development.
 4. Implementation

This phase entails either the purchase or development and purchase of the system. This is
a very important stage as it involves deconstruction or total elimination of the old system
to enable the installation of a new system.
Purpose: This phase involves rolling out the system to users, migrating any existing data,
and ensuring everything is ready for full operation.
Significance: Deployment is when the system is made live, so careful planning and
execution are critical to avoid disruptions. Proper training for users and support structures
should be in place to ensure a smooth transition. This phase is the most expensive phase
hence rapt attention to detail should be paid here and also a high level of technical expertise
should be leveraged as any slight error might lead to a hike in already approved budget.

5. Maintenance and Support Phase

This phase is basically for monitoring the already concluded four stages to ensure optimization of
developed systems.
Purpose: After the system is deployed, this phase ensures it continues to operate effectively,
addressing any issues that arise and making necessary updates.
Significance: The maintenance phase ensures that the system remains up-to-date and functional.
This stage is also very robust and kind of flexible to cater for issues that may emerge in future and
also the ever-changing needs in business, requiring changes to the system.

C. Discuss the importance of each phase in ensuring the overall success of a system
development. How does these phases contribute to risk management, cost control and
meeting stakeholders’ expectation

1. Planning

The planning phase guarantees the project has definite objectives, realistic timelines, and
the appropriate use of resources. This avoids scope creep (uncontrolled alteration in project
scope) and establishes a solidly planned start to the project, minimizing project failure or
unforeseen circumstances. Risk management is at the center of this since, through it, some
 possible risks are determined early during the project and solutions are established
beforehand. In this phase organizational feasibility should be carried out here as it helps
tackle and the questions regarding the risk of who would use the system and how it can be
successfully incorporated to the organizations already ongoing operations. One way for
this to be assessed is by understanding how well the goals of the project aligns with
business objectives and organizational strategies.

2. Analysis
By gathering detailed and precise requirements, this phase minimizes the chance of
developing a system that doesn't meet business needs, avoiding costly revisions. It also
helps ensure that the project is feasible and can be completed within the available budget
and timeline. Here a schedule feasibility must be undertaken to know the amount of risk
that would be faced if new system cannot be developed within estimated timeframe and
how this could in turn affect the utility if the system. This schedule feasibility includes the
use of Gantt charts, program evaluation review technique and critical path method etc. for
efficiency. This directly impacts cost control and stakeholder satisfaction because the
system will have to meet their expectations from the start.

3. Design:
This phase has to do with the question of if we can build it as a team. A technical feasibility
should be carried out here to measure the risks and the extent to which system can be
successfully designed, developed and implemented later by the project team. A well-
thought-out design lays the groundwork for future development. A strong design ensures
that the system is scalable, maintainable, and flexible, which can save significant costs
down the road. Good design also helps in identifying potential bottlenecks or inefficiencies,
which improves risk management and ensures the system aligns with stakeholder needs.

4. Implementation:
Successful deployment requires careful planning to ensure the system is integrated
seamlessly with existing processes and users are trained to use it effectively. A smooth
implementation minimizes disruption to business operations, ensuring that costs and risks
are kept low during the transition phase.
 5. Maintenance and support
Once deployed, the system must be maintained to remain effective. Maintenance ensures
that the system adapts to changing business needs, keeping it relevant and useful. By
addressing issues quickly, this phase helps to control long-term costs and ensures that the
system continues to meet stakeholder expectations over time.

D. Propose strategies for effectively communicating the progress and outcome of each
SDLC phase to the Board, ensuring transparency and alignment with the organizational
goals.

1. Executive Dashboards:

Use visual dashboards to present key measures, such as timeline progress, budget adherence, and
status of risk management. Dashboards present challenging data in a format viewable at a glance
and are well suited for decision-making at the highest level.

2. Regular Updates:

Have concise and regular updates at milestones. Keep it on progress, risk, and delays or issues.
Use graphs, charts, and simple language so that non-technical members can understand the
information.

3. Quarterly/Monthly Status Reports:

Create standard reports that outline high-level achievements, problems faced, and how they are
being addressed. Ensure reports relate to the organization's overall objectives and expectations.

4. Stakeholder Engagement:

Have regular meetings with stakeholders, such as the board, to communicate progress, challenges,
and change. This makes everyone transparent and aligned with the objectives of the project.
E. Reflect on potential challenges that may arise during the SDLC process and suggest
strategies to address the challenges.

Communication Breakdowns:

Poor communication between technical and non-technical teams can lead to confusion which could
negatively affect the SDLC process.

Strategy to mitigate/prevent challenge: Encourage regular cross-functional meetings and mandate

Budget Overruns:

This is simply running over budgeted expenses due to unexpected issues or inefficiencies.

Strategy to mitigate/ prevent challenge: Develop an intensive budget estimate during the planning
stage, and monitor expenditures closely. Provide contingency provisions in the budget to cover
unexpected expenses.

Quality Assurance Shortfalls

This is likely to occur when bugs or performance issues may not be caught until the system is live.

Strategy to mitigate/prevent challenge: Have a rigorous testing process that includes functional
and performance testing. Include user feedback in the test phase and ensure tests are conducted for
every possible scenario.

Qualified Qa personnel should be available at any given time during the system development
lifecycle

Delays

This is due to unforeseen obstacles by members of the team which makes them unable to complete
tasks within the given timeframe thereby prompting delays, which may affect overall project
timelines.
Strategy to mitigate/prevent challenge: Add buffer time to the project timeline and check on
progress from time to time. Make adjustments accordingly, and warn stakeholders in advance in
case of delays.

Scope Creep

These are unexpected changes or alterations to the project which encroaches into already
established scope that have the potential to delay timelines and lead to cost overruns.

Strategy to mitigate/ prevent challenge: Ensure there is a proper change control process in place
where every change is documented, analyzed for its impact, and approved prior to being
implemented.