Systems Development Life Cycle

erocespinel
Mind Map by , created almost 6 years ago

IS201 Mind Map on Systems Development Life Cycle, created by erocespinel on 11/05/2013.

34
1
0
Tags
erocespinel
Created by erocespinel almost 6 years ago
HARDWARE/NETWORKING
erocespinel
OPTIMIZATION MODELING WITH SOLVER
erocespinel
IS Security and Privacy
erocespinel
GCSE Physics Revision notes
Megan McDonald
Function and Structure of DNA
Elena Cade
4.3 Security Across the Technology Life Cycle
DJ Perrone
Valuing and Storing Information, Intro to ER Diagrams
erocespinel
USING EXCEL TO MEASURE THE SUCCESS OF STRATEGIC INITIATIVES
erocespinel
Untitled
erocespinel
Paradigms
erocespinel
Systems Development Life Cycle
1 Key Terms:
2 Concepts
2.1 a. Identify/Understand Consequences of Software (Systems) Success or Failure
2.1.1 1. Increase or Decrease Revenues, 2.Repair or damage brand reputation, 3.Prevent or incur liabilities, 4. Increase or decrease productivity
2.2 b. Know the phases of the SDLC
2.2.1 SDLC Software Systems Development Life Cycle

Annotations:

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

Annotations:

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

Annotations:

  • 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. 
2.2.1.1.1.1.1 e. Agile principles
2.2.1.1.1.2 Agile Methodology

Annotations:

  • 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. 
2.2.1.1.1.2.1 FORMS OF THIS METHODOLOGY
2.2.1.1.1.2.1.1 Rapid Application Development (RAD) Methodology

Annotations:

  • 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.2.1.1.1.2.1.2 Extreme Programming Methodology (XP)

Annotations:

  • 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
2.2.1.1.1.2.1.3 SCRUM Methodology

Annotations:

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

Annotations:

  • 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-
2.2.1.3 3. Design Phase

Annotations:

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

Annotations:

  • 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
2.2.1.5 5. Testing Phase

Annotations:

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

Annotations:

  • IMPLEMENT IT
2.2.1.6.1 Direct Conversion
2.2.1.6.2 Parallel Conversion
2.2.1.6.3 Phased Conversion
2.2.1.6.4 Pilot Conversion
2.2.1.7 7. Maintenance

Annotations:

  • Maintain so that it continues to meet business goals Continues for life
2.3 Understand benchmarks for systems success
2.4 f. Project Management Applied to SDLC

Annotations:

  • 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
2.4.1 i. Project Management Issues
2.4.1.1 i. Choose strategic projects
2.4.1.2 ii. Set the project scope
2.4.1.3 iii. Manage resources and maintain the project plan
2.4.1.4 iv. Change Management
2.4.1.5 v. Risk Assessment, Risk Management, Risk Mitigation
2.5 Understand the various types of feasibility
2.5.1 Technical Feasibility
2.5.2 Economic Feasibility
2.5.3 Legal Feasibility
2.5.4 Operational Feasibility
2.5.5 Scheduling Feasibility
2.6 Understand the key Implementation tasks and strategies
2.6.1 i. Train users
2.6.2 ii. Convert
2.6.3 iii. Benefits and Risks of conversion of different strategies
2.6.4 iv. Acceptance testing

Media attachments