Enterprise Systems Development Life Cycle Presentation and Analysis

This presentation delves into the Development Life Cycle (DLC) within the context of Enterprise Systems. It begins with an introduction to the DLC, outlining its core processes: planning, creation, testing, and implementation. The presentation emphasizes the importance of problem definition and feasibility studies, which are crucial initial steps. It then explores key stages such as system analysis, program design, and coding, highlighting the significance of robust coding and debugging processes. The presentation also covers documentation and maintenance, recognizing the need for adaptability due to evolving technologies. It contrasts traditional and rapid SDLC approaches, and discusses ERP implementation life cycle, project management roles, and the importance of a Project Management Office (PMO). Finally, the presentation concludes with recommendations and references, offering a comprehensive overview of the DLC and its application in Enterprise Systems.


Development Life
Cycle
A process of software developmnet


Introduction
 Development life cycle is
a process in which various
sub-processes running
behind the main process,
such as planning,
creation, testing, and
implementation.
 The main role of
development life cycle is
analyse actual problem of
the systems (Sage, and
Rouse, 2014).


Problem definition
 It is a basic step of
development life
cycle in which
problem is identified
and project manager
provide solution of
that particular
problem using whole
development life
cycle (Highsmith,
2013).


Feasibility study
 DLC has required
feasibility study about
the system, which is
necessary for the
whole system.
 There are various
types of feasibility of a
systems development
cycle (Kumar,
Zadgaonkar, and
Shukla, 2013).


System analysis
 System analysis is
necessary for all the
processes, such as
designing, coding,
implementation, and
others.
 All the requirements
should clear in front of
project manager and
whole team (Valacich,
George, and Hoffer,
2014).


Program design
 Designing is an
important part of
whole cycle, which is
depend on the analysis
and requirements of
the system.
 Program design part
should cover all the
things in a proper way
to analyse all the
things.


Coding
 Coding part is core
part of a system, as
code provides all the
solutions of the
systems problems.
 Coding must be
strong to make a
system secure and
powerful.


Debugging
 Debugging process
is compulsory
process to manage
various things
properly.
 A program can be
affected from the
viruses or any thing
else, such as cyber-
attacks (Kerzner,
2017).


Documentation
 Documentation is
necessary at every
stage of the whole
life cycle.
 It provides proper
management and
communication in
whole development
cycle (Stark, 2015).


Maintenance
 Maintenance is
necessary because
many faults can be
occur in the system
due to many other
reasons
(Bhuvaneswari, and
Prabaharan, 2013).


 Technologies are changing in every decades.
Therefore, extension and redesign process
should be compulsory in the development life
cycle.
 Future changes will be possible in the present
models
Extension and
redesign


Models of DLC
 Agile model  Waterfall model


System
implementation
 Implementation
process is necessary
step, which depends
on the other steps.
 Because of different
architecture of the
systems, it takes
time more than
expectation.


 Project manager should monitor all the
processes in a proper manner to avoid
mistakes.
 Avoid lack of change management
 Requirements should be clear for the team
members
 analysis part must be completed properly
 Choose proper development model as per the
requirement of the task.
Recommendations


 In conclusion, development life cycle has
various parts, which are analysis, coding,
design, maintenance, and implementation. In
addition, a project manager must control and
monitor all the processes properly to avoid
project failure chances.
Conclusion

 Sage, A.P. and Rouse, W.B., 2014. Handbook of systems engineering and
management. John Wiley & Sons.
 Highsmith, J., 2013. Adaptive software development: a collaborative
approach to managing complex systems. Addison-Wesley.
 Kumar, N., Zadgaonkar, A.S. and Shukla, A., 2013. Evolving a new software
development life cycle model SDLC-2013 with client satisfaction.
International Journal of Soft Computing and Engineering (IJSCE), 3(1),
pp.2231-2307.
 Valacich, J., George, J. and Hoffer, J., 2014. Essentials of systems analysis
and design. Prentice Hall Press.
 Bhuvaneswari, T. and Prabaharan, S., 2013. A survey on software
development life cycle models. International Journal of Computer Science
and Mobile Computing, 2(5), pp.262-267.
 Stark, J., 2015. Product lifecycle management. In Product lifecycle
management (Volume 1) (pp. 1-29). Springer, Cham.
 Kerzner, H., 2017. Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
References


Any Queries ???