Systems Development Life Cycle and Methodologies

Glossary of Key Terms

●​ Systems Analysis: The process of understanding and specifying what a new system
should accomplish, focusing on identifying the needs and defining the functional and
non-functional requirements.
●​ Systems Design: The process of describing in detail how a system will solve a business
need, focusing on specifying the components, architecture, and interactions of the
solution.
●​ Systems Development Life Cycle (SDLC): A structured, multi-stage process used to
develop information systems, typically including planning, analysis, design,
implementation, and maintenance phases.
●​ Subsystem: An identifiable and partitioned part of an overall system that performs a
specific set of functions.
●​ Stakeholder: Any person or group who has an interest in the successful implementation
of a system, including users, managers, clients, and technical staff.
●​ Functional Requirements: Requirements that define the specific actions or services that
a system must perform.
●​ Nonfunctional Requirements: Requirements that describe the qualities or constraints of a
system, such as performance, usability, reliability, and security.
●​ Agile Development: An iterative and incremental approach to software development that
emphasizes collaboration, flexibility, and rapid adaptation to changing requirements.
●​ Iteration: A short cycle of development in an iterative methodology, resulting in a working
version of a part of the system.
●​ Model: A representation of some aspect of a system, used to understand, document,
and communicate requirements and design. Models can be textual, graphical, or
mathematical.
●​ Use Case: A description of a sequence of interactions between a user and a system to
achieve a particular goal.
●​ Class: In object-oriented programming, a template or blueprint for creating objects,
defining their attributes (data) and behaviors (methods).
●​ Object: An instance of a class, representing a real-world entity with specific data and the
ability to perform certain actions.
●​ Encapsulation: The bundling of data (attributes) and methods (processes) that operate
on the data within a single unit, such as a class, and controlling access to that unit.
●​ Information Hiding: A principle in object-oriented design that suggests that the internal
workings of a module (like an object) should be hidden from its users, exposing only the
necessary interface.
●​ Unified Modeling Language (UML): A standardized graphical modeling language used to
visualize, specify, construct, and document the artifacts of a software-intensive system.
 ●​ Activity Diagram: A graphical representation of workflows and activities, showing the
sequence of actions and decisions within a process.
●​ Project: A planned undertaking with a beginning and an end, producing a definite result,
such as the development of a new system.
●​ System Vision Document: A document that outlines the overall business need and
objectives of a new system, serving as a starting point for project discussions.
●​ Work Breakdown Structure (WBS): A hierarchical decomposition of the total scope of
work to be carried out by the project team to accomplish the project objectives and
create the required deliverables.
●​ Feasibility Analysis: An evaluation of the practicality and viability of a proposed project,
typically considering technical, economic, and organizational factors.

Core concepts and methodologies related to systems

development.

1. Systems Development Life Cycle (SDLC)

●​ The SDLC is the fundamental process of understanding how an information system can
support business needs by designing, building, and delivering it to users [1-3].
●​ It typically involves four main phases: planning, analysis, design, and implementation
[4-9]. Some sources also mention systems security and support as a later stage [10].
●​ The planning phase focuses on understanding why a system should be built and how
the project team will proceed [5, 8, 11]. Key deliverables include a system request and a
feasibility analysis [11, 12].
●​ The analysis phase answers questions about who will use the system, what it will do,
and where and when it will be used [8, 13, 14]. Deliverables include the system proposal
and business analysis models [15, 16]. This phase involves understanding and
specifying what the new system should accomplish, also known as systems analysis [10,
17-20].
●​ The design phase decides how the system will operate in terms of hardware, software,
network infrastructure, user interface, and data storage [8, 16, 21]. Deliverables include
architecture design, interface design, and database specifications [21-23]. This is also
known as systems design, which describes how the system will work [10, 18-20, 24].
●​ The implementation phase involves building (or purchasing) and testing the system,
installing it, training users, and establishing a support plan [9, 23, 25-29].
●​ The SDLC is a process of gradual refinement, where each phase elaborates on the work
done previously [11, 30].
●​ There are six core processes required in the development of any new application: 1.
Identify the problem or need and obtain approval to proceed. 2. Plan and monitor the
project. 3. Discover and understand the details of the problem or the need (systems
analysis). 4. Design the system components that solve the problem or satisfy the need
 (systems design). 5. Build, test, and integrate system components. 6. Complete system
tests and then deploy the solution [31-35].

2. Systems Development Methodologies

●​ A methodology is a formalized approach to implementing the SDLC, providing a list of

steps and deliverables [9, 27, 29].
●​ Several categories of methodologies are discussed:
○​ Structured Design Methodologies follow a formal, step-by-step approach, moving
logically from one phase to the next. Waterfall development is a classic example,
where phases are completed sequentially [9, 36, 37]. It can struggle with unclear
requirements and long delays [37, 38].
○​ Rapid Application Development (RAD) methodologies aim to speed up the
process by using special techniques and tools, often involving iterative
development and user feedback [36, 39]. Examples include parallel development
(subprojects in parallel) [37, 39], phased development (systems developed in
versions sequentially) [40, 41], prototyping (building early versions for feedback)
[41, 42], and throwaway prototyping (prototypes discarded after clarifying
requirements) [41, 43].
○​ Agile Development Methodologies emphasize flexibility and rapid response to
changing requirements through iterative application development with less focus
on extensive documentation [38, 44-47]. Extreme Programming (XP) and Scrum
are examples [43, 48]. Agile methods rely on the agile manifesto and its
principles [45].
●​ The choice of methodology depends on factors like system complexity, user
requirements clarity, familiarity with technology, project schedule, and the analyst team's
experience [43, 49, 50].

3. Core Concepts in Systems Analysis and Design

●​ Systems analysis focuses on understanding and specifying what the new system should
accomplish [10, 17-20, 51]. Key activities include gathering detailed information, defining
requirements (functional and non-functional), prioritizing requirements, developing
user-interface dialogs, and evaluating requirements with users [52-59].
●​ Systems design focuses on defining and describing in detail the system that solves the
need [10, 18-20, 24, 51]. It specifies all the components of the solution system and how
they work together [24].
●​ Requirements are all the activities the new system must perform or support and the
constraints it must meet [51, 60-62].
●​ Functional requirements are the activities the system must perform (the business uses)
[54, 60, 63-66].
●​ Nonfunctional requirements relate to qualities like usability, reliability, performance, and
security. The FURPS+ model categorizes these as Functionality, Usability, Reliability,
 Performance, Security, and other constraints (Design, Implementation, Interface,
Physical, Support) [54, 59, 60, 62-65, 67, 68].
●​ Stakeholders are all the people who have an interest in the successful implementation of
the system and are primary sources of information for requirements [58, 66, 69-71].
Analysts need to identify and involve them [69, 70].
●​ Iterative development is an approach where the system is "grown" piece by piece
through multiple iterations, with each iteration involving all core development processes
[31, 72-76].
●​ Agile Development is characterized by being use-case-driven, architecture-centric,
iterative, and incremental [77, 78].
●​ A system is an independent entity, while a subsystem is a component of a larger system
[79, 80].

4. Modeling in Systems Analysis and Design

●​ Models are representations of some aspect of the system being built and are crucial for
understanding, documenting, and communicating system requirements and design [71,
81-85].
●​ Different types of models include:
○​ Textual models: memos, reports, narratives, lists [83].
○​ Graphical models: diagrams and schematic representations (e.g., use case
diagrams, class diagrams, workflow diagrams) [71, 81, 83].
○​ Mathematical models: describe requirements numerically [83].
●​ The Unified Modeling Language (UML) is a standard set of model constructs and
notations used in object-oriented development [4, 7, 28, 59, 68, 75, 78, 83, 86-89]. UML
includes various diagrams for different purposes, such as use-case diagrams (capture
business requirements) and class diagrams (document information requirements) [6, 28,
68, 72, 76, 86, 88, 90].
○​ Workflow diagrams (activity diagrams) are used to document the steps within a
use case and the interactions between the user and the system [7, 60, 91-94].
○​ Class diagrams are used to understand and document the information
requirements of a system, identifying classes and their relationships [68, 88, 90,
91, 95-99].
○​ Use cases define what the end users need the system to do [68, 72, 86-88, 91,
95, 98, 100, 101]. A use case diagram provides a visual representation of use
cases [90, 95].

5. Role of the Systems Analyst

●​ A systems analyst is a business professional who analyzes business situations,

identifies opportunities for improvement, and designs information systems to implement
them [2, 19, 20, 76, 102-104].
 ●​ They act as a bridge between business needs and IT solutions [102].
●​ They require a wide range of skills, including technical, business, analytical,
interpersonal, management, and ethical skills [81, 103-108].
●​ Various career options are available for information systems graduates, with job titles
ranging from programmer analyst to business consultant [104, 109].

This overview highlights the central themes and concepts related to systems development
covered in the provided study guide and excerpts.

Quiz Questions
1.​ What is the fundamental purpose of systems analysis and design (SA&D)?
a.​ The fundamental purpose of systems analysis and design (SA&D) is to provide
developers with the tools and techniques needed to understand business needs,
capture a vision for a solution, define that solution in detail, communicate it
effectively, build or direct its construction, and ultimately ensure it meets the
original need.​

2.​ Distinguish between systems analysis and systems design in terms of their focus and
the key questions they address.
a.​ Systems analysis focuses on understanding and specifying what a new system
should accomplish by detailing the required functions and features. In contrast,
systems design focuses on describing how the system will work by specifying all
the necessary components and their interactions to deliver the desired solution.​

3.​ Why is documentation particularly important in system development projects with

distributed teams?
a.​ In distributed teams, where members are geographically separated and may only
be responsible for specific parts of the programming, written documents are
crucial for ensuring a shared understanding of the project's vision, details, needs,
and specifications, facilitating effective communication and collaboration.​

4.​ Briefly describe the Systems Development Life Cycle (SDLC) and its significance in
creating a new information system.
a.​ The Systems Development Life Cycle (SDLC) is a project management
framework that outlines the necessary activities to develop a new information
system, including planning, analysis, design, implementation, and maintenance.
It provides a structured approach with a beginning and an end to produce a
defined result.​

5.​ Explain the concept of a subsystem within a larger information system and provide an
example from the RMO case.
a.​ A subsystem is an identifiable and partitioned portion of an overall system,
focusing on a specific set of functionalities. In the RMO case, the Supplier
 Information subsystem, which collects and maintains data about manufacturers
and wholesalers, is an example of a distinct part of the larger system.​

6.​ What is the role of a system analyst in the context of understanding and capturing the
vision for a new system?
a.​ The system analyst acts like an architect for software development by planning,
capturing the vision of the project funders (often the business stakeholders),
understanding the detailed needs, and specifying these requirements before
programming begins. They bridge the gap between the business need and the
technical solution.​

7.​ Differentiate between functional and non-functional requirements, providing one example
of each.
a.​ Functional requirements describe the specific actions or services that the system
must perform, such as "the system must keep track of customer orders."
Non-functional requirements describe the qualities or constraints of the system,
such as "the system must have a response time of under three seconds."​

8.​ Define the term "stakeholder" in the context of systems development and why it is crucial
to identify them.
a.​ A stakeholder is any person or group who has an interest in the successful
implementation of the system. Identifying stakeholders is crucial because they
are the primary source of information for system requirements, each offering a
unique perspective on what the system should do and how it should operate.​

9.​ What is the purpose of an activity diagram in systems analysis?

a.​ The purpose of an activity diagram in systems analysis is to document and
illustrate the workflow of a process or a series of actions, often including decision
points, parallel activities, and the overall sequence of steps. It helps in
understanding and communicating how a business process is currently
performed or how a new system feature will function.​

10.​Briefly explain the core principle behind agile development methodologies.

a.​ Agile development is based on the principle of developing a system in small
chunks or iterations, allowing for frequent feedback and adaptation to changes in
requirements that are expected to occur during the development process. It
emphasizes flexibility and collaboration over rigid, upfront planning.