SDLC Lo3

LO3:Undertake a software development lifecycle
Company or team approach to Continuous integration And version

control
Continuous integration is a DevOps software development practice where developers
regularly merge their code changes into a central repository, after which automated
builds and tests are run.
Version control also known as source code are system that allow to track
changes to code and allow you to work in isolation from other
developers.version control allow developers safely work through branching
and merging.
With branching a developer duplicate part of the source code and can make
changes to the code without affecting
Rest of the project. Once the code works properly developer can merge that
code Back into the main source code and make it official.
Object oriented software engineering
• It is a software design technique that is used in software design in object oriented
programming.it includes a requirement, an analysis, a design and a testing
implementation.
• Object – Oriented Analysis : Object Oriented Analysis (OOA) is the first technical
activity performed as part of object oriented software engineering. OOA introduces
new concepts to investigate a problem
• The main difference between object-oriented analysis and other forms of analysis
is that by the object-oriented approach we organize requirements around objects,
which integrate both behaviors (processes) and states (data) modeled after real
world objects that the system interacts with. In other or traditional analysis
methodologies, the two aspects: processes and data are considered separately. For
example, data may be modeled by ER diagrams, and behaviors by flow charts or
structure charts.
An event-driven architecture is designed to detect events as they occur,
and then deal with them using some event-handling procedure.
Identify stakeholder requirements
• Stakeholder requirements are the foundation of successful software
development. They ensure that the final product is aligned with business
goals, meets user needs, complies with regulations, and is delivered within
scope, time, and budget constraints. By actively involving stakeholders and
thoroughly capturing their requirements, software development teams can
deliver high-quality products that provide significant value to the
organization and its users.
• Scope of project: Defining project scope requires input from the project
stakeholders. They work with project managers to establish the key
elements of budget, objectives, quality. To determine scope, project
managers must collect requirements for what the stakeholders need from the
project.
Alternate solution considerations for
stakeholders.
• In the Software Development Life Cycle (SDLC), alternative solutions
for involving stakeholders can help improve project outcomes by
ensuring their needs are met and expectations are managed. Such as
DevOps
• Automated Testing: Provide stakeholders with access to continuous
testing results to ensure quality and gather feedback.
• Visualization Tools: Use tools like Miro to create visual
representations of processes, requirements, and designs for better
stakeholder understanding
Security considerations for stakeholders
• Security considerations for stakeholders in the Software Development Life Cycle (SDLC) are
crucial for ensuring the protection of sensitive data, maintaining compliance with
regulations, and mitigating risks. Here are key security considerations for stakeholders
throughout the SDLC:
• Data Protection Requirements: Identify and document security requirements related to
data protection, including encryption, access controls, and data retention policies.
• Data Flow Diagrams: Create detailed data flow diagrams to understand how data moves
through the system and identify potential security risks.
• Secure Coding Practices:
• Security Testing: Integrate security testing including penetration testing, vulnerability
scanning.
• Third-Party Security: Evaluate and ensure the security of third-party vendors and partners
involved in the SDLC.
Required Quality assurance (QA) and testing
• Quality assurance (QA) and testing are critical for ensuring that the software meets the
expectations and requirements of stakeholders. Effective QA and testing involve several activities
and practices .
• 1. Planning and Requirement Analysis
• 2. Test Design such as automated testing
• 3. Test Execution such as unit ,system, integration, user acceptance testing.
• 4. Defect Management
(Regular Reporting: Provide regular defect reports to stakeholders to keep them
informed about the status and severity of issues.)
5. Continuous Improvement
6. Tools and Techniques like automated tools selenium
• 7. Communication and Collaboration
• Regular Updates: Provide regular updates to stakeholders on testing progress, including test
coverage, defect status, and overall quality metrics.
Constraints activity in software project
that can impact development
• In the Software Development Life Cycle (SDLC), various constraints can impact the development process
and final deliverables. Understanding and managing these constraints is essential for successful project
execution. Here are some common constraints:
• 1. Costs
Budget Limitations: Limited budgets can restrict the scope of project, the resources available, and the
technologies used.
• 2. Organizational Policies
• Compliance and Regulations: Adherence to industry standards, legal requirements, and internal policies
can constrain design choices and development practices.
• Security Policies: Organizational security policies can dictate specific security measures that must be
integrated into the system, impacting design and implementation.
• 3. Legacy Systems
• Integration Challenges: Integrating new systems with existing legacy systems can be complex and time-
consuming.
• Data Migration: Migrating data from legacy systems to new systems can pose significant challenges in
terms of data compatibility, quality, and consistency.

SDLC Lo3

Uploaded by

Copyright:

Available Formats

SDLC Lo3

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SDLC Lo3

Uploaded by

Copyright:

Available Formats

LO3:Undertake a software development lifecycle

Company or team approach to Continuous integration And version

You might also like