Systems Development Life Cycle

1. 1. Increase or Decrease Revenues, 2.Repair or damage brand reputation, 3.Prevent or incur liabilities, 4. Increase or decrease productivity

1. SDLC Software Systems Development Life Cycle

   Nota:

   • A process used by software industry to design, develop and test high quality softwares.
   1. 1. Planning Phase

      Nota:

      • What approach should I take? What are my goals? First and most critical phase
      1. Understand the high-level differences among software development methodologies
         1. Waterfall Methodology

            Nota:

            • In a waterfall model, each phase must be completed before the next phase can begin and there is no overlapping in the phases CONS:  1. Does not allow for much reflection or revision.  -Once an application is in the testing stage, it is very difficult to go back and change something that was not well-documented or thought upon in the concept stage. 
            1. e. Agile principles
         2. Agile Methodology

            Nota:

            • Iterative development: consists of a series of tiny projects Early continuous delivery of useful software components developed by an iterative process with a design point that uses the bare minimum reqs. 
            1. FORMS OF THIS METHODOLOGY
               1. Rapid Application Development (RAD) Methodology

                  Nota:

                  • Fundamentals of RAD: 1. Focus initially on creating a prototype that looks and acts like the desired system -Prototype is an essential part of the analysis phase when using rad 2. Actively involve system users in the analysis, design, and development phases 3. Accelerate collecting the business requirements through an interactive and iterative construction approach
               2. Extreme Programming Methodology (XP)

                  Nota:

                  • Breaks a project into tiny phases and developers cannot continue on to the next phase until the first phase is complete. The faster the feedback the better the results Like a puzzle 4 parts. (1) planning (2) designing-no functionality until it is needed,  (3) Coding (4) Testing-tests are written before the code BENEFIT: -Narrows gap between developers and users ---->Saves time and clarifies needed and unneeded  reqs
               3. SCRUM Methodology

                  Nota:

                  • Small teams to produce small pieces of deliverable software using sprints, 30-day intervals, to achieve an appointed goal Standup meetings
   2. 2. Analysis Phase

      Nota:

      • 1. Analyze end-user  business requirements-requests to be successful  2. Refine project goals into defined functions and operations of the intended system. Essential to getting a good start-So spend as much time, energy, and resources as necessary to perform a detailed, accurate analysis. What must the system do to meet the objectives? -Sign off-
   3. 3. Design Phase

      Nota:

      • 1. Describe the desired features and operation of system
   4. 4. Development (Construction) Phase

      Nota:

      • Takes all the detailed docs of the design phase and transforms them into the actual system. Project has come from preliminary designs to the actual physical implementation
   5. 5. Testing Phase

      Nota:

      • You want to make sure that the system meets all the business reqs from analysis phase And Test in a special testing environment
   6. 6. Implementation Phase

      Nota:

      • IMPLEMENT IT
      1. Direct Conversion
      2. Parallel Conversion
      3. Phased Conversion
      4. Pilot Conversion
   7. 7. Maintenance

      Nota:

      • Maintain so that it continues to meet business goals Continues for life

Nota:

• 1. Unclear or missing business reqs-cost to fix an error grows exponentially the later the error is found in the SDLC 2. Skipping SDLC phases 3. Failure to manage project scope and project plan 4. Changing technology

1. i. Project Management Issues
   1. i. Choose strategic projects
   2. ii. Set the project scope
   3. iii. Manage resources and maintain the project plan
   4. iv. Change Management
   5. v. Risk Assessment, Risk Management, Risk Mitigation

1. Technical Feasibility
2. Economic Feasibility
3. Legal Feasibility
4. Operational Feasibility
5. Scheduling Feasibility

1. i. Train users
2. ii. Convert
3. iii. Benefits and Risks of conversion of different strategies
4. iv. Acceptance testing