Download sdlc with new brief pass and more Study Guides, Projects, Research Web Design and Development in PDF only on Docsity!
ASSIGNMENT FINAL REPORT
Qualification Pearson BTEC Level 5 Higher National Diploma in Computing
Unit number and title Unit 7: Software Development Life Cycle
Submission date 03/24/2025 Date Received 1st submission
Re-submission Date Date Received 2nd submission
Student Name Nguyen Duc Ngoc Student ID BH
Class HL_LCS_C4 Assessor name Ngo Thi Mai Loan
Plagiarism
Plagiarism is a particular form of cheating. Plagiarism must be avoided at all costs and students who break the rules, however innocently, may be penalised. It is your responsibility to ensure that you understand correct referencing practices. As a university level student, you are expected to use appropriate references throughout and keep carefully detailed notes of all your sources of materials for material you have used in your work, including any material downloaded from the Internet. Please consult the relevant unit lecturer or your course tutor if you need any further advice.
Student Declaration
I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism. I declare that the work submitted for assessment has been carried out without assistance other than that which is acceptable according to the rules of the specification. I certify I have clearly referenced any sources and any artificial intelligence (AI) tools used in the work. I understand that making a false declaration is a form of malpractice.
Student’s signature Ngoc
Grading grid
P1 P2 P3 P4 P5 P6 P7 M1 M2 M3 M4 M5 M6 D1 D2 D3 D
Contents
- Introduction.................................................................................................................................................................................
- Body.............................................................................................................................................................................................
- sequential models................................................................................................................................................................. (P1) Description of predictive and adaptive software development models considering at least two iterative and two
- Waterfall Model (Sequential)..................................................................................................................................................................
- V-Model (Sequential)..................................................................................................................................................................................
- Agile Model (Iterative/Adaptive)..........................................................................................................................................................
- Spiral Model (Iterative/Adaptive)......................................................................................................................................................
- (P2) Explain how risk is managed in software lifecycle models...........................................................................................
- Risk Management in Software Development Life Cycle (SDLC)............................................................................................
- Risk Management Process in Developing a Software Project (Step by Step)..................................................................
- Risk Management in the Spiral Model..............................................................................................................................................
- Waterfall Model Risks..............................................................................................................................................................................
- V-Model Risks..............................................................................................................................................................................................
- Agile Model Risks......................................................................................................................................................................................
- (P3) Discuss the purpose of conducting a feasibility study for the project.........................................................................
- Technical Feasibility.................................................................................................................................................................................
- Economic Feasibility................................................................................................................................................................................
- Organizational Feasibility......................................................................................................................................................................
- Conclusion and Recommendations...................................................................................................................................................
- (P4) Describe how technical solutions can be compared....................................................................................................
- Analysis of Alternatives...............................................................................................................................................................................
- Selection of the Most Suitable Solution................................................................................................................................................
- Recommendation...........................................................................................................................................................................................
- Conclusion.............................................................................................................................................................
- References.................................................................................................................................................................................
Introduction
In today’s digital marketplace, having a robust and user-friendly online sales platform is essential for business
success. TechStyle Solutions has been entrusted with the development of a cutting-edge online sales website that
will provide a seamless shopping experience for customers while ensuring efficiency and scalability for the
business.
Our team is committed to designing a platform that integrates modern e-commerce functionalities, including
intuitive navigation, secure payment processing, real-time inventory management, and personalized user
experiences. By leveraging the latest web technologies and best practices, we aim to deliver a high-performance
solution that meets the client's business objectives and enhances customer engagement.
This project will be executed in a structured manner, following industry-standard development methodologies, to
ensure timely delivery, security, and maintainability. Our focus will be on delivering a scalable, responsive, and
visually appealing online store that aligns with the client's brand and business goals.
Body (P1) Description of predictive and adaptive software development models considering at least two iterative and two sequential models
1. Waterfall Model (Sequential)
Figure 1
2. V-Model (Sequential)
Figure 2
Definition: The V-Model (Verification and Validation Model) is an extension of the Waterfall model, where development and testing phases run in parallel.
Model Characteristics:
● Emphasizes a strong relationship between development and testing phases.
● Each development phase has a corresponding testing phase.
● Provides early validation through rigorous testing.
Phases:
- Requirements Analysis : Understand user requirements.
- System Design : Create the system’s architecture.
- Implementation : Code the system.
- Unit Testing : Perform testing at the component level.
- Integration Testing : Test integrated modules.
- System Testing : Perform complete system tests.
- Acceptance Testing : Validate the system against requirements.
Advantages:
● Early detection of defects due to parallel testing.
● Clear structure similar to Waterfall.
● Suitable for projects with well-defined requirements.
Disadvantages:
● Inflexible to changes after the requirements phase.
● Late feedback from end-users or stakeholders.
● Costly if changes are required in the middle.
- Planning : Outline the scope and requirements for the iteration.
- Design and Development : Design and build software incrementally.
- Testing : Test the software continuously throughout the process.
- Review : Evaluate the iteration’s progress with stakeholders.
- Deployment : Deliver the software incrementally.
- Feedback and Iteration : Incorporate feedback and refine the system.
Advantages:
● Flexibility to handle changing requirements.
● Frequent delivery of working software.
● High customer involvement, ensuring better alignment with needs.
Disadvantages:
● Can be challenging to manage scope.
● Requires a highly skilled and collaborative team.
● May lack detailed documentation, which can be a problem for larger projects.
4. Spiral Model (Iterative/Adaptive)
Figure 4
Definition: The Spiral model combines iterative development with a focus on risk analysis. It allows for incremental releases of the product while focusing on assessing and mitigating risks at each phase.
Model Characteristics:
● Iterative and risk-driven.
● Breaks the project into smaller, manageable parts (spirals).
● Involves continuous risk assessment and refinement.
● Flexible for changes during the project lifecycle.
Phases:
- Planning : Define objectives, alternatives, and constraints.
- Risk Analysis : Assess risks and explore solutions.
- Engineering : Develop and test the system incrementally.
- Evaluation : Evaluate progress and gather feedback.
- Next Spiral : If the project is not complete, repeat the process.
● Monitoring and Control: Risks are continuously monitored throughout the project. If new risks arise or existing risks evolve, the management strategy is adjusted accordingly.
● Documentation and Review: A record of identified risks, actions taken, and their outcomes is maintained for review during and after the project. This can provide valuable insights for future projects.
2. Risk Management Process in Developing a Software Project (Step by Step)
Effective risk management in software development can be broken down into the following steps:
Step 1: Risk Identification
● Objective: Identify potential risks early in the project.
● Activities:
o Brainstorming sessions with stakeholders, team members, and clients.
o Review of past projects for similar risks.
o Using tools like SWOT analysis (Strengths, Weaknesses, Opportunities, Threats) or Failure Modes and Effects Analysis (FMEA).
● Examples of Risks Identified:
o Incomplete or unclear requirements.
o Lack of skilled resources.
o Technological challenges.
o Changes in project scope or schedule.
Step 2: Risk Assessment
● Objective: Prioritize the identified risks based on their likelihood and impact.
● Activities:
o Assign a probability to each risk (e.g., high, medium, low).
o Assess the impact (e.g., critical, moderate, low) if the risk occurs.
o Create a risk matrix to help visualize the severity of each risk.
● Example:
o A risk such as "requirement changes during development" may have a high likelihood and critical impact, making it a high-priority risk.
Step 3: Risk Mitigation Strategy Development
● Objective: Develop strategies to address and mitigate the highest-priority risks.
● Activities:
o Avoidance: Change the project plan to eliminate the risk (e.g., re-scoping the project to avoid high-risk areas).
o Reduction: Implement measures to reduce the likelihood or impact of the risk (e.g., using proven technology, training the team).
o Transfer: Shift the risk to a third party (e.g., outsourcing certain components).
o Acceptance: Accept the risk if the cost of mitigation is higher than the potential impact.
● Example:
o For "changing requirements," use an agile methodology (e.g., iterative cycles and constant feedback) to accommodate changes effectively.
Step 4: Risk Response Planning
● Objective: Plan how to respond to identified risks if they occur.
● Activities:
o For each high-priority risk, define response strategies and actions.
o Prepare contingency plans for critical risks that may disrupt the project.
● Example:
o For a risk of "delayed development due to resource shortages," have a backup plan with additional resources or outsourcing options.
Step 5: Monitoring and Controlling Risks
● Objective: Continuously monitor risks throughout the project lifecycle and adjust strategies as necessary.
● Activities:
o Regularly review and update the risk register.
o Keep track of the status of mitigation actions.
o Adjust project plans or mitigation measures if risks evolve.
● Example:
● Unclear Requirements: In the first spiral, risks related to unclear or changing requirements are identified and addressed. Prototypes can be developed and reviewed by stakeholders to refine requirements iteratively.
● Technological Uncertainty: By developing incremental prototypes, potential technical risks are identified early, allowing the team to switch tools or technologies if necessary.
● Resource Constraints: During each iteration, resource availability is assessed. If resources are constrained, additional team members or external vendors can be brought in to mitigate delays.
The Spiral Model effectively manages risks by integrating risk assessment and mitigation at every stage, making it a suitable model for complex and high-risk projects.
4. Waterfall Model Risks
● Rigid and Sequential Structure : Changes are difficult and costly to implement once a phase is completed.
● High Risk of Misunderstanding Requirements : Early-stage requirement gathering is critical; errors propagate through subsequent phases.
● Delayed Testing : Testing happens only after development, increasing the risk of finding critical issues late in the project.
● Unsuitability for Uncertain Projects : Poor adaptability to changing customer requirements or market conditions.
● Customer Involvement : Limited engagement after initial requirement gathering can lead to misalignment with customer expectations.
5. V-Model Risks
● Inflexibility : Similar to the Waterfall model, it's rigid and less accommodating to changes once development starts.
● High Dependency on Requirements Accuracy : Errors in requirements can lead to issues throughout the validation and verification stages.
● Resource Intensive : Requires parallel testing efforts, increasing costs and resource allocation.
● Limited Iterative Capability : Changes necessitate revisiting earlier stages, causing delays and added complexity.
● Overemphasis on Documentation : Excessive focus on documentation might reduce agility and slow progress.
6. Agile Model Risks
● Scope Creep : Continuous changes and iterations can lead to uncontrolled scope expansion.
● Dependency on Skilled Teams : Requires highly skilled and collaborative teams to deliver quality work in sprints.
● Less Predictability : Planning and timelines are flexible, which can create uncertainty for stakeholders.
● Inconsistent Documentation : Prioritizing working software over documentation might lead to knowledge gaps.
● Customer Availability : Relies on consistent customer feedback, which may not always be feasible.
● Integration Issues : Frequent changes might result in integration challenges if not managed well.
Aspect Waterfall Model V-Model Agile Model Spiral Model Flexibility Low – rigid and sequential; changes are costly once phases are completed.
Low – rigid structure with limited flexibility for changes.
High – iterative and adaptive to change but prone to scope creep.
Medium – iterative with some flexibility but complexity increases.
Risk Management Minimal – risks are identified upfront but often realized late due to delayed testing.
Moderate – risk identification through verification and validation but limited adaptability.
Variable – less structured risk management but relies on frequent feedback to mitigate risks.
High – risk-driven approach with constant assessment and mitigation at every iteration. Testing Timing Late – testing only starts after development is completed.
Concurrent – testing is planned and conducted alongside development.
Continuous – testing happens iteratively in every sprint.
Iterative – testing is performed at the end of each cycle with iterative improvements. Customer Involvement
Low – customer involvement is limited to initial requirements and final delivery.
Low – customer involvement is typically confined to requirement specification stages.
High – active customer involvement throughout the process for feedback and prioritization.
High – requires customer feedback at the end of each iteration for risk evaluation and progress.
Documentation High – comprehensive documentation is essential at every phase.
High – detailed documentation is emphasized for both development and testing.
Medium – documentation takes a backseat to working software.
High – detailed documentation required for risk analysis and iterations. Cost and Time Low for small projects; high if changes occur late.
Moderate to High – requires extensive testing and documentation.
Variable – cost- effective for well- managed teams but can escalate due to scope creep and iterative cycles.
High – costly due to frequent risk assessments and iterative cycles.
2. Economic Feasibility
The economic feasibility assesses whether the project is financially viable, considering the costs and benefits.
Cost Components:
- Initial Costs :
o Development (man-hours, tools, licensing).
o Infrastructure setup (servers, software licenses).
o Training for all ththe staff.
- Operational Costs :
o Maintenance and support.
o Upgrades and scaling over time.
Benefits:
● Efficiency Gains : Streamlined operations reduce manual intervention and increase productivity.
● Error Reduction : Automated processes lead to fewer mistakes, improving accuracy and reliability.
● Cost Savings : Long-term reduction in operational expenses offsets the initial investment.
Break-Even Analysis:
With careful budgeting, the project is expected to reach a break-even point within 2–3 years, driven by increased efficiency and cost savings.
3. Organizational Feasibility
Organizational feasibility ensures the project aligns with company’s strategic goals and operational capacity.
Alignment with company’s Goals:
The new system is designed to support company’s objectives, including:
● Scaling operations to handle growth.
● Streamlining workflows to improve operational efficiency.
● Adopting modern technologies to remain competitive.
Collaboration and Training:
● Partnership with ABC : Close cooperation between ABC’s development team and staff ensures the solution is tailored to specific organizational needs.
● Training Programs : Comprehensive training will be provided to staff to ensure smooth adoption of the new system.
Change Management:
● Strategies to manage resistance to change.
● Phased implementation to allow gradual adaptation.
● Regular feedback loops to address concerns and refine processes.
Additional Considerations
Legal and Regulatory Feasibility:
● Compliance with data protection regulations (e.g., GDPR if applicable).
● Ensuring secure handling of sensitive information.
Scalability and Future-Proofing:
● Designing the system with future growth in mind, allowing for easy upgrades and integration of new features.
Risk Mitigation:
- Technical Risks : Addressed through thorough testing and using proven technologies.
- Financial Risks : Managed through careful budgeting and cost monitoring.
- Organizational Risks : Minimized through stakeholder engagement and effective change management.
4. Conclusion and Recommendations
Based on the analysis, the project is viable across technical, economic, and organizational dimensions. To ensure success:
● Establish clear milestones and regular progress reviews.
● Engage stakeholders throughout the project lifecycle.
● Allocate resources for ongoing training, maintenance, and support.
This comprehensive approach will maximize the likelihood of achieving strategic objectives while delivering a robust, cost-effective, and future-ready solution.
