1 / 21

SDLC Group 1

SDLC Group 1. Hang Pham Jared Jelacich Hector Arreola. Systems development life cycle. Is a structure step-by-step approach for developing information systems. The activities are determining budget, gather business requirements, designing models, and writing detailed user documentation.

shawn
Download Presentation

SDLC Group 1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SDLCGroup 1 Hang Pham Jared Jelacich Hector Arreola

  2. Systems development life cycle • Is a structure step-by-step approach for developing information systems. • The activities are determining budget, gather business requirements, designing models, and writing detailed user documentation.

  3. SDLC Phase • Planning • Analysis • Design • Development • Testing • Implementation • Maintenance

  4. Different version of SDLC

  5. Waterfall Model • describes a development method that is linear and sequential. • Waterfall development has distinct goals for each phase of development. • The advantage of waterfall development is that it allows for departmentalization and managerial control. • The disadvantage of waterfall development is that it does not allow for much reflection or revision.

  6. Spiral Model • This model of development combines the features of the prototyping model and the waterfall model. • The spiral model is favored for large, expensive, and complicated projects. • Required 9-steps

  7. Prototyping Model • an early approximation of a final system or product is built, tested, and then reworked until an acceptable prototype is finally achieved from which the complete system or product can now be developed. • Works best in scenarios where not all of the project requirements are known in detail ahead of time. • Requires 9-steps

  8. Exploratory Model • used to design and develop a computer system or product • Planning and trying different designs until one of them seems to be the right one to develop. • Works best in situations where few, or none, of the system or product requirements are known in detail ahead of time. • Required 7-steps

  9. Extreme Programming (or XP) • Extreme Programming differs from traditional methodologies primarily in placing a higher value on adaptability than on predictability. • believe that being able to adapt to changing requirements at any point during the project life is a more realistic and better approach than attempting to define all requirements at the beginning of a project and then expending effort to control changes to the requirements.

  10. Agile • anticipates the need for flexibility and applies a level of pragmatism into the delivery of the finished product. • keeping code simple / often tested • delivering functional bits of the application as soon as they're ready. • Goal: is to build upon small client-approved parts as the project progresses, as opposed to delivering one large application at the end of the project.

  11. Joint Application Development • involves the client or end user in the design and development of an application. • Chuck Morris and Tony Crawford, both of IBM, developed JAD in the late 1970s. • in comparison with the more traditional practice, is thought to lead to faster development times and greater client satisfaction, because the client is involved throughout the development process.

  12. Rapid Application Development • Gathering requirements using workshops or focus groups. • Prototyping and early, reiterative user testing of designs. • The re-use of software components. • A rigidly paced schedule that defers design improvements to the next product version.

  13. Is it best for a Company to pick only one or pick the best SDLC that fits for each project? • Some companies prefer having one complete SDLC that everyone gets trained on.

  14. SDLC Advantages • Systematic approach • Standardized series of steps • Formal documents and formal procedures of proceeding from each step to the next • Provide written evidence that can be used to arbitrate disputes between developers and users. • Addresses both business and technical issues • Tried and tested • Very appropriate for transaction processing system (TPS)

  15. SDLC Disadvantages • Requirements analysis may lead to analysis paralysis. • Waterfall nature unrealistic. • Difficulty of documenting requirements in a usable way. • Not knowing well the requirements that concern the particular features. • Budget difficulties.

  16. More Disadvantages • Know little about how long it may take. • Too much unknown for any technique to work well. • User requirements not being met by the application system.

  17. Reason why some business do not use SDLC • It's more of a time issue. • a lot of effort and produces • a lot of documentation.  . • The SLDC is simply not appropriate for all industries.  It's not a guarantee of high quality software

  18. Brighton Group • "There is a direct correlation between the quality of the individuals working on information technology projects and the time it takes to develop and implement a new system. To date, you have provided us with extremely high-quality individuals across the board. Your consultants have proven to possess superior business analysis and technical skills. We appreciate the fine job you and your firm have done for us." -J.N. MIS Director

  19. "You significantly raised the awareness and competency of Project Management in one of our large divisions. On a separate assignment, your consultant revised our Systems Development Life Cycle (SDLC) Training Class to include more small group activities and ensure congruence with the general SPS Project Management approach. Please accept our acknowledgement of the skills and professionalism of your staff." -S.D.Director, Information Technology

  20. Questions??

More Related