Comprehensive Guide to Systems Development and Database
Design
Introduction
This document provides an in-depth exploration of the core concepts in
systems development and database design. It includes detailed
explanations of methodologies like Waterfall and Agile, as well as tools
such as Entity Relationship Diagrams (ERDs) and Use Case Diagrams
(UCDs). The goal is to provide a resource that not only introduces these
concepts but also explains their real-world applications in software
development and database management.
1. Systems Development Life Cycle (SDLC)
Definition: The SDLC is a structured framework used to plan, develop,
test, and deploy software systems. It provides a clear process that ensures
quality and reduces risks throughout a project.
Stages of SDLC
1. Feasibility Study:
o This stage evaluates whether the project is achievable and
worthwhile.
o Key considerations: technical feasibility (can the technology
support this?), financial feasibility (is the budget sufficient?),
and operational feasibility (does this solve the problem?).
2. System Analysis:
o Focuses on gathering requirements from users and
stakeholders.
o Methods include interviews, observations, and surveys.
o Output: A clear list of functional and non-functional
requirements.
3. System Design:
o Divided into two parts:
Logical Design: Specifies what the system must do
without detailing how it will be implemented.
Physical Design: Defines the hardware, software, and
network architecture to implement the logical design.
, 4. Implementation:
o The coding phase, where developers build the system using
programming languages, frameworks, and tools.
o Includes unit testing to verify that individual components work
correctly.
5. System and Acceptance Testing:
o System Testing: Ensures the complete system works as
intended.
o Acceptance Testing: Confirms that the system meets user
requirements and can be deployed.
6. Operation and Maintenance:
o Involves deploying the system for real-world use and providing
updates and fixes as needed.
o Ensures the system continues to meet evolving requirements.
Challenges with Waterfall SDLC
Assumes that requirements are fully understood upfront, which is
not always realistic.
Limited flexibility to accommodate changes during development.
Testing occurs late, increasing the cost of fixing errors.
Alternatives to Waterfall: Agile Methodologies
Agile addresses Waterfall’s limitations by emphasising flexibility,
collaboration, and iterative development.
Core Agile Principles:
Prioritise customer collaboration and satisfaction through continuous
delivery of small, functional increments.
Adapt to changes even late in the development process.
Agile Frameworks:
1. SCRUM:
o Roles: Product Owner (sets priorities), SCRUM Master
(facilitates the process), and Development Team.
o Key features: Sprints (short work cycles) and ceremonies like
Daily Standups and Sprint Retrospectives.
Design
Introduction
This document provides an in-depth exploration of the core concepts in
systems development and database design. It includes detailed
explanations of methodologies like Waterfall and Agile, as well as tools
such as Entity Relationship Diagrams (ERDs) and Use Case Diagrams
(UCDs). The goal is to provide a resource that not only introduces these
concepts but also explains their real-world applications in software
development and database management.
1. Systems Development Life Cycle (SDLC)
Definition: The SDLC is a structured framework used to plan, develop,
test, and deploy software systems. It provides a clear process that ensures
quality and reduces risks throughout a project.
Stages of SDLC
1. Feasibility Study:
o This stage evaluates whether the project is achievable and
worthwhile.
o Key considerations: technical feasibility (can the technology
support this?), financial feasibility (is the budget sufficient?),
and operational feasibility (does this solve the problem?).
2. System Analysis:
o Focuses on gathering requirements from users and
stakeholders.
o Methods include interviews, observations, and surveys.
o Output: A clear list of functional and non-functional
requirements.
3. System Design:
o Divided into two parts:
Logical Design: Specifies what the system must do
without detailing how it will be implemented.
Physical Design: Defines the hardware, software, and
network architecture to implement the logical design.
, 4. Implementation:
o The coding phase, where developers build the system using
programming languages, frameworks, and tools.
o Includes unit testing to verify that individual components work
correctly.
5. System and Acceptance Testing:
o System Testing: Ensures the complete system works as
intended.
o Acceptance Testing: Confirms that the system meets user
requirements and can be deployed.
6. Operation and Maintenance:
o Involves deploying the system for real-world use and providing
updates and fixes as needed.
o Ensures the system continues to meet evolving requirements.
Challenges with Waterfall SDLC
Assumes that requirements are fully understood upfront, which is
not always realistic.
Limited flexibility to accommodate changes during development.
Testing occurs late, increasing the cost of fixing errors.
Alternatives to Waterfall: Agile Methodologies
Agile addresses Waterfall’s limitations by emphasising flexibility,
collaboration, and iterative development.
Core Agile Principles:
Prioritise customer collaboration and satisfaction through continuous
delivery of small, functional increments.
Adapt to changes even late in the development process.
Agile Frameworks:
1. SCRUM:
o Roles: Product Owner (sets priorities), SCRUM Master
(facilitates the process), and Development Team.
o Key features: Sprints (short work cycles) and ceremonies like
Daily Standups and Sprint Retrospectives.
