Reference no: EM131542822

Assignment: Systems Development Life Cycle (SDLC)

Need a 200 words minimum with reference, need by Saturday.

Ever ask yourself how is it possible to manage very large software projects? Just like building a skyscraper, a bridge, a house or even renovating your kitchen, a software project can quickly be delayed or go over budget by mismanagement, lack of control, by misdirected resources or activity. Project managers depend on standardized tools and techniques to help make sure everything is proceeding, as it should.

History

Originally, software project managers relied on the traditional tools used in designing and building large engineering projects such as skyscrapers, roads and bridges. e.g. PERT & GANT

The complicated demands of software development led to a better understanding of managing complex projects by breaking down the work into small easily managed parts.

These methods rely and on a cyclical model where each development cycle includes the following components: identify the need, evaluate the available options, develop the component, verify what was built, and plan for the next time around, and starts and ends with something that works. These newer models and techniques are now being applied to all types of projects. The design-build method now used in engineering projects is based on the cyclical model. Can you think of a construction project that used this model?

Today the construction industry has adopted the this model from the software industry. It is often referred to as design as you go or design/build. This shortens the delivery time and cost since the project starts construction sooner by not needing to wait for the final details from design.

A cyclical development process allows for greater flexibility in managing any project. By splitting projects into modular tasks and using a cyclical process, it is no longer necessary to wait for all previous steps to be complete before starting on a task. The cyclical processes used in software development support developing each module independently. As a bonus, once a module is ready, it can be used over and over whenever and wherever it's needed.

Think of how many apps your smartphone has. Each of these can be used on its own, but the best ones rely on one another. Your phone app needs a phonebook; your messaging app needs a phonebook, your email app needs a phonebook, and so on. Instead of having a separate phonebook for each, your smartphone relies on a single contacts app that is shared by many other apps. The designer of each of the separate apps only needs to know how to talk to the contacts app.

i.e. Once the overall design is ready and the interface of the module is defined, work can start on that module even if the detailed design of every component module is not yet ready.

Can you think of ways you can apply this to your personal life or projects?

Reference:
Chebib, L.F. (2016). SDLC vs. STLC.