MODULE 2-3 Flashcards
It is the process of breaking a complex topic or substance into
smaller parts in order to gain a better understanding of it.
Analysis
It is a systematic process that includes phases such
as planning, analysis, design, deployment, and maintenance
Systems Development
It is a process of collecting and interpreting facts, identifying the problems, and
decomposition of a system into its components.
Systems Analyst
It is a process of planning a new business system or replacing an existing system
by defining its components or modules to satisfy the specific requirements.
System Design
A process for experimentation that is used to
explore observations and answer questions.
Scientific Method
It is a common methodology for
systems development in many organizations; it features several phases that
mark the progress of the systems analysis and design effort.
System Development Life Cycle
In this phase, the system analyst
identifies the need for a new or enhanced system. In a larger organization, this
recognition may be part of a corporate and systems planning process.
Information needs of the organization as a whole are examined, and projects to
meet these needs are proactively identified.
Planning
During this phase, the analyst
thoroughly studies the organization’s current procedures and the information
systems used to perform organizational tasks.
Analysis
In this subphase, analysts work with
users to determine what the users want from a proposed system. This process usually involves a careful study of any
current systems, manual and computerized, that might be replaced or enhanced
as part of the project.
Requirements Determination
The second part of the analysis
The analysts study the
requirements and structure them according to their interrelationships and
eliminate any redundancies
During this phase, analysts convert
the description of the recommended alternative solution into logical and then
physical system specifications
Design
The physical system
specifications, whether in the form of a detailed model or as detailed written
specifications, are turned over to programmers as the first part of this phase. During this phase, analysts turn system
specifications into a working system that is tested and then put into use.
It includes coding, testing, and installation.
Implementation
When a system
(including its training, documentation, and support) is operating in an
organization, users sometimes find problems with how it works and often think
of better ways to perform its functions. Also, the organization’s needs with
respect to the system change over time. In this phase, programmers make the
changes that users ask for and modify the system to reflect evolving business
conditions. These changes are necessary to keep the system running and useful.
Maintenance
It is the classic SDLC methodology that has been used for many
years. Being linear and sequential, it emphasizes the need for a logical
progression of the phases involved. One phase must be carried out to completion
then its output is used as the input for the next.
Waterfall
Similar to the waterfall method, it is linear and
sequential though different.It is also called the
verification and validation model because every phase has a validation test
attached to it. The left side of the ‘V’ has the verification phases while the right
side has the validation phases. At the bottom is the coding phase.
V-Shaped
It is an agile project management
strategy popular in software development. The key benefit of this approach is
fast project turnaround, making it an attractive choice for developers working in
a fast-paced environment like software development. This rapid pace is made
possible by this SDLC methodology focus on minimizing the planning stage and maximizing
prototype development.
Rapid Application Development (RAD)
This model is mainly focused on providing an approximation of the final
system at the initial stages. It is widely used when fixed requirements are not
available. A prototype is built to show how the final product will look and work.
Prototyping
This model uses a sequential approach while working as a prototype. This
way, it delivers a system that is not complete but is under constant review. The
biggest differentiating aspect though is that it is focused on risk analysis. It is
best suited for projects where risk management is critical
Spiral
This model begins development by building only a part of the
software. Full specifications of requirements are usually not known. The small
part of the system developed is reviewed to identify further requirements. Every
successful iteration produces a software build upon which more features are
implemented. This continues until the final system is achieved.
Iterative
The model focuses on building the whole system in small portions. It works
quite similarly to the iterative model but the difference is that this approach
starts with the full knowledge of requirements. This determines the number of
smaller portions of the system to be built.
Incremental
This method is used to counter the limitations of those which cannot cater
to a fast-changing environment. Projects which use the agile approach always
have their requirements changing quickly. This approach is based on iterative
and incremental processes. It guarantees customer satisfaction through quick
deliverable parts of the whole system. The cycles through which the system is
delivered are called sprints. Technically speaking, the agile model is more of a
framework or guideline than a distinct model.
Agile
