Please enable JavaScript.

Coggle requires JavaScript to display documents.

SYSTEM DEVELOPMENT LIFE CYCLE, WATERFALL DIAGRAM - Coggle Diagram

- - - - Inventory Management System Using Waterfall
        
        Scenario: A medium-sized retail company wants to develop a new inventory management system to streamline their operations.*
        
        SDLC Plan* : SDLC Planning: In this scenario, the company opts for a Waterfall approach due to the structured nature of the project
      - Mobile App for a Startup Using Lean Startup Principles
        
        Scenario: A startup is developing a mobile app for a new social networking concept. They have a limited budget and want to quickly validate their idea.
        SDLC Planning: In this scenario, the startup plans to follow Lean Startup principles. The SDLC plan includes building a minimum viable product (MVP) with basic features, launching it to a small group of early users, and collecting feedback
      - Website Redesign Using Agile
        
        Scenario: A small web design agency is tasked with redesigning a client's website. The client wants a more modern look and improved user experience.
        SDLC Planning: In this scenario, the agency plans to use Agile methodology. The SDLC plan includes creating a backlog of design and development tasks, conducting weekly sprints, and holding regular client meetings for feedback.
  - - - Scenario 2 - An international e-commerce giant is launching a new feature-rich mobile shopping app. The development phase involves coding and integrating various functionalities, such as product search, online payments, customer reviews, and personalized recommendations, to create a seamless shopping experience.
      - Scenario 3 - A city's transportation department is undertaking a smart traffic management system project. They aim to develop software that integrates data from traffic cameras, sensors, and GPS devices to optimize traffic flow, reduce congestion, and enhance public safety. The development phase includes coding, integration, and extensive testing of the traffic management software.
      - Scenario 1 - A national healthcare organization is embarking on the development of a comprehensive Electronic Health Records (EHR) system. The goal is to create a secure, interoperable, and user-friendly platform that enables healthcare providers to efficiently manage patient records, track medical history, and improve patient care.
  - - - An approach where different components or modules of a software application are tested as a combined entity.
      - The fuel system may be tested in collabration with an exhaust system, and later, these two module's working tested in collabration with the working of an engine.
      - Mailbox software developers compase different modules, including login page, inbox, default folder and move and flag functions.
    - - Identify interface issues
      - Security testing
      - Verify system integration
  - - - System analyst assesses business processes, identifying software features like expense tracking, invoicing, and tax reporting, and analyzing existing financial documents and workflows to develop a tailored solution.
      - Assessing system development involves evaluating technical, economic, and operational aspects. Technical feasibility determines available technology and resources, while economic feasibility evaluates financial viability and user adoption.
      - Analysts collaborate with stakeholders to gather and document requirements through interviews, surveys, and seminars, guiding the development process and understanding user needs.
  - - - Business Analyst
        It provides the requirements to the design team and reviews the software design and artifacts.
      - Technical-Architect, Tech-Designer, Design Team
        They design the system architecture, software components, etc., along with the design walk-through.
      - Project Manager
        The project managers finalize the data conversion strategy and the test strategy. Plus, they review the software design and artifacts.
  - - - Propose= To support the intended business functions
        
        Scenario=
        
        2) Developers write the source code for various component of the platform :
        
        3)Use programming languages and tools appropriate for the project
        
        1) Installation of hardware
- - - - - An adaptive software development model based on prototyping and quick feedback with less emphasis on specific planning.
      - - The RAD approach prioritizes development and building a prototype, rather than planning.
    - - Cuts down on development time.
      - Facilitates customer feedback and the final product satisfies all stakeholders.
      - Allows for integration from the start.
      - Fast initial reviews occur.
      - Improves the reusability of components.
      - Enhances end-product risk management.
    - - It is dependent on a skilled team of developers/designers.
      - It can only build modularized projects.
      - Cannot be used for cheap projects due to automated and modelling costs.
      - Requires a strong team and individual performances.
      - It works only for projects that require speed.
      - It is hard to manage due to many stakeholders.
  - - - Iterative development means building in small cycles, improving with feedback.
      - Incremental development builds in pieces, adding to what's there. Both methods help manage complex projects, adapt to changes, and deliver useful parts early.
    - - Iterative development
        
        Flexibility: Allows for changes in project requirements during development.
        
        Continuous Improvement: Regular iterations lead to better product refinement.
        
        Early Feedback: Stakeholders see progress early and can provide input.
      - Incremental development
        
        Early Deliveries: Provides functional parts of the product sooner, offering value.
        
        Reduced Risk: Each increment is tested and integrated, lowering overall risk.
        
        Better User Engagement: Early increments allow user feedback and involvement.
    - - Iterative development
        
        Potential for Scope Creep: Frequent changes may expand project scope.
        
        Resource Intensive: Requires ongoing effort and resources for multiple iterations.
        
        Complex Management: Requires effective project management to coordinate iterations.
      - Incremental development
        
        Integration Challenges: Integration of increments can be complex and time-consuming.
        
        Incomplete Early Versions: Initial increments may lack essential features.
        
        Dependency Management: Managing dependencies between increments can be tricky.
  - - - This model is flexible in design.
      - It is easy to detect errors.
      - We can find missing functionality easily.
      - It ensures a greater level of customer satisfaction and comfort.
      - It is ideal for online system.
      - It helps developers and users both understand the system better.
    - - This model is costly.
      - It has poor documentation because of continuously changing customer requirements.
      - There may be too much variation in requirements.
      - There is certainty in determining the number of iterations.
      - There may be incomplete or inadequate problem analysis.
      - There may increase the complexity of the system.
    - - https://1.bp.blogspot.com/-OMvVWj7OUMM/WEe3G9SkNMI/AAAAAAAAAeo/BjrxC40DuLc-5AfO_gR-76uGjFWleJj8gCLcB/s1600/prototype_model_sdlc.png
        
        https://i.pinimg.com/originals/90/de/55/90de55fcac1d999eef366aff25c4c4db.jpg
  - - - a unique approach to software and systems development because it involves clients, customers or end users throughout the product design and development lifecycle. It emphasizes a team-oriented development approach along with a group consensus-based problem-solving model.
    - - JAD allows key users to participate effectively
      - Users more likely to feel a sense of ownership
      - Produces a more acurate statement of system requirements
    - - Can be cumbersome if group is too large
      - It opens up a lot of scope for inter-personal conflict
      - JAD is more expensive that traditional methods