Wk 2 - Apply: Signature Assignment: Project Plans [due Mon]

profileNowresaliraqi2
WK1_SDLCComparison2.pptx

SDLC Comparison

University of Phoenix

CMGT555

1

Phases of Waterfall and Agile SDLCs

Waterfall SDLC

Requirements: understanding what is to be designed, functions, and purposes

System design: Preparing system design after studying requirements specifications.

Implementation: writing of the sources as per the requirements

Testing: Testing team checks the code for any potential problems.

Deployment: the project is released into the markets.

Maintenance: this happens after installation. Modifications are made on the system if need be.

Agile SDLC

Concept: project scope determined by the owner.

Inception: the project team is created who also create a mock-up of the user interface and architecture.

Iteration: constructions occur here, and the bare functionality of the product

is built.

Release: Quality assurances team performance test on the product, which is

then released

Maintenance: software is now fully deployed and made avoidable to end-users.

Retirement: replacement of the project if it becomes obsolete.

2

Waterfall and agile Documentation Differences

Waterfall documentation adopts a sequential methodology where tasks are handled in a liners process.

The tasks are handle in a simple process, one after the other till the end.

Agile documentation adopts an iterative methodology that incorporates a collaborative and cyclic process.

It provides room for the process to move through a series of cycles throughout its lifetime.

Each method can be used depending on the preferences and nature of the project

some projects are more iterative while others are sequential.

3

Stakeholder’s expectations

The SDLC method to adopt varies depending on the stakeholder's expectations.

The project team:

Expects to have all the time, support, and tools needed to complete the project

Management and executive;

Expects the project to be completed successfully

Expects the project to save on company finances

Clients:

Expects all the requirements o be executed and followed.

The trick to making sure the project runs smoothly is managing all stakeholders' expectations by putting them in balance.

4

Pros and Cons

Waterfall SDLC Pros Cons
No financial Surprises Longer delivery time
The outcome is crystal clear. Needs can be difficult to define
Time scales are kept.  
Testing is made easy. Lacks flexibility
Agile SDLC Highly flexible Documentation gets left behind
Allows room for better communication Hard to predict
The product gets to market faster.
  One can get immediate feedback. Hardtop measure progress
  Faster to detect and fix issues.  

5

Graphic summary

6

WeLoveVideo attributes

WeloveVideo loves a better, faster, and cheaper approach to quickly meeting customers' demands and increasing team productivity.

The company has high regard for transparency to offer clients a chance to be involved throughout their project.

The company utilizes very complicated technology with a very skillful team.

The company also handles projects with aggressive deadlines, a high degree f novelty, and a higher degree of complexity.

Most of the time company's projects are new and designed according to customers' specifications.

7

References

Olorunshola, O. E., & Ogwueleka, F. N. (2021). Review of System Development Life Cycle (SDLC) Models for Effective Application Delivery. In Information and Communication Technology for Competitive Strategies (ICTCS 2020) (pp. 281-289). Springer, Singapore.

Shaikh, S., & Abro, S. (2019). Comparison of traditional & agile software development methodology: A short survey. International Journal of Software Engineering and Computer Systems, 5(2), 1-14.