LESSON 1
a systematic approach used to understand, plan,
create, and implement effective software systems. It involves a set of methodologies, techniques,
and tools that help organizations and software developers ensure that the software solutions they
create align with user needs, business goals, and quality standards.
System analysis and design
SAD emphasizes understanding user needs and ensuring that the
software serves its intended users effectively. The user's perspective is central to the
entire process.
USER-CENTRIC APPROACH
The process involves identifying problems in existing systems or processes
and finding solutions that can be implemented through software development.
Problem-Solving
SAD follows a structured approach, often adhering to a specific
methodology or framework, to ensure that software development is systematic,
organized, and well-documented.
STRUCTURED PROCESS
SAD typically follows a lifecycle composed of phases, including
requirements gathering, analysis, design, implementation, testing, deployment, and
maintenance.
LIFECYCLE PHASE
By systematically analyzing requirements and designing a solution before
implementation, SAD helps mitigate risks and reduces the likelihood of costly errors or project failures.
RISK MANAGEMENT
SAD involves frequent communication and collaboration among
stakeholders, users, analysts, designers, developers, and other team members.
Communication
The process ensures that the software meets quality standards, aligns
with user expectations, and fulfills business needs.
QUALITY ASSURANCE
SAD considers changes that might occur during development,
ensuring that the software can adapt to evolving requirements and technological
advancements.
CHANGE MANAGEMENT
In this initial phase, the project scope is defined, and the feasibility of the
project is assessed. Key stakeholders are identified, and a project plan is created,
outlining the schedule, budget, and resources required.
PLANNING
During this phase, system analysts work closely with stakeholders to gather and document detailed requirements for the system. The current system is analyzed, and the desired features and functions of the new system are specified.
Requirements Gathering and Analysis
The system design phase involves creating a detailed technical blueprint of the system based on the requirements identified in the previous phase. This blueprint serves as a guide for developers and includes data models, architectural diagrams, and other design specifications
DESIGN
This phase involves coding and programming based on the system
design. Developers build the actual system according to the specifications laid out in the design phase.
IMPLEMENTATION
In the testing phase, the system is rigorously tested to identify and fix any defects or issues. Different types of testing are performed, such as unit testing, integration testing, system testing, and user acceptance testing.
TESTING
Once the system has been thoroughly tested and approved, it is deployed to
the production environment for end-users to access and use.
DEPLOYMENT
After deployment, the system requires ongoing maintenance and support
to address any bugs, make improvements, and adapt to changing needs.
MAINTENANCE
a framework used to guide the process of
developing information systems, software applications, or other products. It provides a structured approach to the development process, ensuring that the system is designed, built, and maintained
in a systematic and methodical manner
SYSTEMS DEVELOPMENT LIFE CYCLE
This phase involves studying the current system (if any), identifying its strengths and weaknesses, gathering user requirements, and defining the objectives of the new system. During this stage, system analysts engage with stakeholders, conduct interviews, use case studies, and analyze data to understand the problem domain and develop a detailed understanding of what the system should accomplish.
SYSTEMS ANALYSIS
In this phase, system analysts and designers use the information gathered
during analysis to create a blueprint for the new system. This blueprint outlines how the system will be structured, what components it will have, how data will be stored and processed, and how various elements will interact with each other
SYSTEMS DESIGN