In today’s society, software companies are constantly pressured to deliver quality software projects at a strict deadline that must be met. As a result, companies must always renovate themselves and software developers must keep up with the latest technologies. However, software companies often resort to the premature release of software projects in order to meet deadlines. These projects are aesthetically complete and free of errors. Incomplete projects often fail their customers when they are challenged. A recent example of such software project is the affordable care act website. The website, when challenged (multiple users attempting to register at the same time), instantly crashed and caused much frustration among users. Among other reasons,
…show more content…
A software developer should also be familiar with the different methodologies that software development teams use to organize and implement the software project. In the Sentinel project, a waterfall methodology was first used to implement the project before switching to an agile methodology. A waterfall methodology roughly consists of heavy documentation at first, followed by design, then implementation, testing and integration. This methodology is a traditional way of developing software that still has use for some projects, but fails to keep up with the constant changes of a current software project. An agile methodology consists of having small iterations in which a software project gets slight increments during each iteration; tests are made at the beginning of each iteration, and then the implementation for that iteration is done. Meetings with the client occur often to address what the customer really wants versus what he or she described. An agile methodology has more detail than what was described. As a result, this newer methodology only works if it’s performed correctly. For example, HealthCare.gov attempted to use an agile methodology (4), yet failed to deliver a complete quality project when the deadline approach. A software engineering has the responsibility to know these methodologies, correctly apply these methodologies, and recognize which methodology to use depending on the project
A software developer should also be familiar with the different methodologies that software development teams use to organize and implement the software project. In the Sentinel project, a waterfall methodology was first used to implement the project before switching to an agile methodology. A waterfall methodology roughly consists of heavy documentation at first, followed by design, then implementation, testing and integration. This methodology is a traditional way of developing software that still has use for some projects, but fails to keep up with the constant changes of a current software project. An agile methodology consists of having small iterations in which a software project gets slight increments during each iteration; tests are made at the beginning of each iteration, and then the implementation for that iteration is done. Meetings with the client occur often to address what the customer really wants versus what he or she described. An agile methodology has more detail than what was described. As a result, this newer methodology only works if it’s performed correctly. For example, HealthCare.gov attempted to use an agile methodology (4), yet failed to deliver a complete quality project when the deadline approach. A software engineering has the responsibility to know these methodologies, correctly apply these methodologies, and recognize which methodology to use depending on the project