System Development Methodologies

Write an essay that demonstrates an understanding of predominant system development methodologies and develop an organizational action plan to evaluate and choose an appropriate system development methodology. This essay should

(1) clearly define the purpose,
(2) provide an overview of predominant systems development methodologies/managerial approaches,
(3) identify the decision criteria and data sources, and
(4) present a plan for data collection, synthesis, & decision making. Note that you are not necessarily advocating a change to Agile but are laying out the requisite steps and information.

Essentially you are laying out what you need to determine if a company should pursue an Agile methodology.

APA Format with Title Page, (no abstract required), Section headers, running header, labeled figures and tables, citations, and references sections.

Submit via CNVS Upload with a Turn It In originality score < 17%.

Sections:
1.0 Introduction
a clear and direct purpose statement for presenting a plan to choose a system development methodology for an organization.

2.0 System Development Methodologies
Provide a brief overview, definitions, and major components (phases, tools, methodologies) of the SDLC (including the purpose of the SDLC in an organization). I suggest stepping through each phase and giving one concrete example of a tool or method in that phase.
Do the same for the Agile System Development Methodology.
Here is a nice comparison/overview: Introduction to Scrum – 7 Minutes

3.0 Identify the decision criteria and data sources
Now that you have established a baseline understanding of two predominant system development methodologies, begin to identify the requisite data and information needed to support an informed decision to choose a methodology. Consider advantages and disadvantages of each (textbook Chapters 01 & 04), including organizational context & culture, technology and infrastructure, industry & competitive environment.
For example, the decision may be different if a company is primarily consumer-oriented versus in a B2B arrangement. Does organizational size, IT department organization/governance/size, company history play a part?
The output of this section is a comprehensive list (not just two) of sources of information that are needed for this decision.
Include various sources and types of data: internal/external, qualitative/quantitative.

4.0 Present a plan for data collection & synthesis
From the identified data sources, present a detailed plan on how to gather the information from the top two most important data sources. Why are these two most important?
The Requirements Modeling/Fact Finding step of the SDLC Analysis phase outlines some techniques. How are data collected, validated, organized, and synthesized from the data sources?
Interviews, Surveys, Observation, Systems Analysis Models, Systems Documentation, etc.? What technique is needed to collect data from the data source. What data are generated (e.g., interview transcript) and how will it be used?

5.0 Analysis and Presentation to Management
Lastly, how would these data be analyzed and presented to management to support a decision? Select appropriate methodology/technology to aid in synthesis (i.e., to process the data) and the expected outcomes and impact toward the final decision.
How would you go about connecting & combining information from different resources?
Consider a table or visual aid that depicts the logic and flow of this decision: decision criteria, data source, collection, synthesis, analysis, and outcome/decision.

For example:
IT Department Management (criteria),
Organizational Chart, Job Descriptions, & Interviews (data source),
contact HR for org. chart/descriptions, interview with CIO, Director, Team Leaders (collection),
transcribe and store interview transcript, summarize by theme and sentiment toward IT department strengths and weaknesses (synthesis),
a table of strong and weak managerial facets of the IT department, determination of a strong managerial control of the IT department or not and how that influences the overall decision (outcome/decision).

ANSWER

Introduction

System development methodologies contribute significantly to the functions of the system development life cycle. These methodologies offer guidelines relevant to the development of IT systems, and each one functions differently depending on the project size, type, and available resources. The utilization of software development methodologies enhances the probability of delivering quality software within the selected budget and stipulated timelines.

Developers opt to adapt team software development methods that correspond with an organization’s development effort. All these systems constitute a series of procedures that must be executed comprehensively to assert the achievement of tasks and delivery of final products. Software development methodologies regularly undergo shifting specifications that pose negative implications on organization progress since it decreases predictability and inflicts strain on timelines and budgets.

Before selecting the most appropriate system methodology, adequate research is essential to determine the risks and challenges predominantly experienced in organizations and projects involving this art invention. Further, the core values associated with a particular methodology should be upheld by system developers and equipment utilized in the research, planning, and design of these technologies. This paper intends to examine the various system development methodologies utilized in organizations and select the most efficient method.

System Development Methodologies

Software Development Life Cycle (SDLC) is a type of software methodology that provides a framework for planning, designing, and managing developing an information system. It constitutes various phases, including requirement analysis, design, testing, coding, and maintenance. Requirement analysis is the prior phase of SDLC. It focuses on the classification of the necessities of a system. Essentially, this phase is a comprehensive depiction of the software contents being developed. Jama software may be utilized in this stage because it aids in the management of requirements, tests, and risks that are defined during the development of products. The design phase involves problem-solving and planning for software solutions, and it implicates developers to define appropriate system solutions. The Software Design Document (SDD) is the output of this stage.

The coding phase converts the SDD into code by utilizing a programming language that produces a program code. To enable coding, Lucidchart can be used in documentation processes. Testing is undertaken to determine application outcomes. Effective testing ensures quality products, accurate results, and low maintenance costs (Dora & Dubey, 2013). Various tools, including Katlon, may be used for desktop and web software projects. Maintenance constitutes the final stage and involves the distribution of software to suitable end-users. Its methodologies include Iterative, Spiral, and Lean.

Agile methodologies are substitutes for traditional sequent methodologies. They enable teams to break down larger tasks into smaller ones that are more manageable. In essence, the agile methodology is a subset of iterative and developmental procedures based on recurring enhancement processes. These systems underline the significance of continuous and timely delivery of software solutions. Agile methods facilitate a regulated organizational process that encourages consistent monitoring and evaluation, accountability and teamwork, and a business approach that corresponds with company objectives and consumer demands. Agile methods comprise notable elements, namely: quick release, constant testing, collaboration, small teams, and code reviews. This methodology offers an organization with the capability of evolving IS solutions rapidly.

Iteration -1 is the stage whereby a potential project is identified and prioritized. The project’s feasibility is assessed, and if eligible, it is considered. The Iteration 0/Warm Upstage involves the active stakeholder engagement and the retrieval of funds and support. It further involves team-building alongside the development of an appropriate working environment. After the Iteration 0/Warm Upstage is the Release Iteration(s) that includes the release of the software product, final system testing, and training production staff and end-users. The production phase involves the detection of malfunctions within the system.

 The retirement phase involves the complete removal of the system from production and the update of enterprise models. Agile methodologies constitute Scrum and Feature Driven Development (FDD). Scrum is centered on how teams should function and identifies the technical variables likely to shift (Hidalgo, 2019). FDD is appropriate for start-up projects and the upgrading of existing codes. Source control tools such as CVS and Subversion provide more flexibility for teams, while continuous integration tools ensure that the software functions effectively.

Identify the decision criteria and data sources

Since the company is consumer-oriented, its system methodology has to prioritize customers’ demands and preferences. With SDLC, the system is designed as per developers’ needs instead of those of the consumer. Whereas SDLC produces multiple intermediate products that can be analyzed and amended, it fails to meet consumer needs fully. Users are also unable to review intermediate products and assess whether a product aligns with their entrepreneurial prerequisites. Alternatively, customer satisfaction is guaranteed with agile methodologies since these systems ensure efficient and accurate delivery of services, and their simplicity enables all organizational stakeholders to comprehend their functions. These systems ascertain increased attention to consumer requirements since they encourage enhanced collaboration and feedback.

However, large organizations may not be capable of integrating agile methodologies because the systems rely on more flexible and less formal processes, which are more applicable to small organizations. A company’s history will also be significant in the selection of an appropriate system methodology. When the SDLC is used, it advocates for consistent procedures and limits creativity. Therefore, if a company is accustomed to such a culture, the integration of other system methodologies such as agile may become a challenge. An organization’s competitive environment further necessitates agile methodologies due to the need for faster and more accurate services. If a company’s competitors rely on the fast detection of errors and defects, the company will be prompted to employ faster and more accurate systems.

Present a plan for data collection & synthesis

            Data will be collected by the researcher and research assistants. Qualitative data will be collected through interviews that will be conducted by the researcher. The researcher will interview the director and several team leaders to gather their opinions regarding the current system methodology. Permission to obtain internal data from the organization’s database will be sought from upper management. The organization’s charts will also be significant in data collection. Data obtained from the database and organizational charts will be used as baseline data.

Questionnaires will be utilized to collect quantitative data. The questionnaires will seek to determine the importance of the current system methodology, its risks, as well as its challenges Directors and team leaders will be requested to provide their opinions on the flexibility, complexity, and speed of the system methodology in use and their proposals to address the system’s challenges. Data will be submitted to IT department experts for validation and organization. Data will be synthesized through observation and regular research from various sources, such as articles and journals.

The generated data will constitute interview transcripts and survey data, which will be used by the IT board to determine the most suitable methodology it can fund. The generated data will also be used to advance knowledge of related studies and develop programs that endorse system development projects.

Analysis and Presentation to Management

Data will be assessed using SPSS version 25. Pearson correlation will be utilized to determine correlations between variables, the independent and dependent variables. At the same time, regression analysis will be used to assess the impact of the two methodologies on an organization’s performance, customer satisfaction, and service delivery. Agile methodologies will be advocated for due to their improved efficiency in organizational outcomes and their significance in enhancing consumer-centricity.

Information from the various sources will be combined using the modeling tools in Data Builder, including SQL view and Graphical view. The tables from diverse sources will be combined by selecting them and dragging them to the canvas. Local CSV tables will be combined with SAP ABAP sources, while the SAP HANA may be combined with Odata sources. Data will be presented in the form of charts, tables, and graphs. Qualitative data obtained from interviews will be transcribed and coded to form themes.

Better outcomes                                                                    Poor outcomes

Fig 1: Strong and weak managerial facets of the IT department and their influence on decision

IT Department Management (criteria)

Interviews, Organizational Chart and Database (data source)

Interviews with Director and Team Leaders, organization database, organization charts (collection)
Transcribe and store interview records, review the themes and inform the IT department regarding its advantages and disadvantages (synthesis)

References

Hidalgo, E. S. (2019). Adapting the scrum framework for agile project management in science: case study of a distributed research initiative. Heliyon, 5(3), e01447. https://globaljournals.org/GJCST_Volume20/2-A-Comparison-between-Agile.pdf

Dora, S. K., & Dubey, P. (2013). Software Development Life Cycle (SDLC) Analytical comparison and survey on Traditional and agile methodology. Abhinav National Monthly   Refereed Journal of Research in Science & Technology.

To get your original copy of this completed paper, please Order Now