• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Sdlc
 
  • 1,994 views

 

Statistics

Views

Total Views
1,994
Views on SlideShare
1,002
Embed Views
992

Actions

Likes
0
Downloads
54
Comments
0

4 Embeds 992

https://pic.fsu.edu 915
http://pic.fsu.edu 45
http://www.shortcourses.ca 17
http://shortcourses.ca 15

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Sdlc Sdlc Presentation Transcript

    • System & Software Development
    • Managing Information
      • A Computer-based Information System (CBIS) uses these components to manage and distribute information.
    • Participants in Systems Dev. Systems Analyst: professional who specializes in analyzing and designing systems. Stakeholders: those that stand to benefit from a new system.
    • Systems Development Life Cycle Systems development is the activity of creating new or modifying existing information systems.
    • System to Software Development Program Specification Program Development Life Cycle
    • Program Development Many Variations…
    • Program Development Many Variations…
    • Program Development Many Variations…
    • Program Development Many Variations…
    • Analysis
      • The most important task in creating a software product is extracting the requirements or requirements analysis. Customers typically have an abstract idea of what they want as an end result, but not what software should do. Incomplete, ambiguous, or even contradictory requirements are recognized by skilled and experienced software engineers.
      From http://en.wikipedia.org/wiki/Software_development_process
    • Design
      • Specification is the task of precisely describing the software to be written, possibly in a rigorous way.
      • A use case is a description of a system’s behavior as it responds to a request that originates from outside of that system.
      • Flowcharts and psuedo-code are typically used.
    •  
    • Implementation
      • Implementation is the part of the process where software engineers actually program the code for the project.
    • Testing
      • Alpha testing – in-house
      • Beta testing – select users
      • Syntax errors – incorrect use of language, causes system crashes
      • Logic (semantic) errors – system works, but gives the wrong result, incorrect software design
    • Maintenance
      • Maintenance and enhancing software to cope with newly discovered problems or new requirements can take far more time than the initial development of the software.
    • Program Design Models
      • Waterfall Model : Analysis, Design, Implementation, Testing, Maintanance, months or years before product is presented
      • Agile Software Development/Extreme Programming (XP) : Iterative,small steps, automated testing, pair programming, dependence on frequent user feedback
      • Cowboy coding : anything goes
    • http://webstyleguide.com