Methodologies

Waterfall life cycle

The method that we could use is the waterfall model life cycle. It is defined as a sequence of phases and each stage is validated before moving on to the next stage. System life cycle includes requirements, problem investigation, feasibility, analysis, design, maintenance and evaluation.

220px-SDLC_-_Software_Development_Life_Cycle

The waterfall life cycle involves the following procedures:

  • Requirements

In this page, the requirements are meeting with the customer and company to find out what their requirements are. There is a lot of pressure on getting this correct because if there are errors this could lead to a misunderstanding when it comes to designing the product. These requirements must be accurate and detailed so there are no issues further down the line and so the product meets the clients specification. You could have an interview with the customer to find out what they want, or use a questionnaire to obtain further information. Another way to obtain the information is to observe them using their current system to advice.

  • Feasibility

In this stage the designer checks to see if the item is worth making or if it is possible to do, also to consider the software currently being used or whether it has to be made from scratch. The software should only be created if it’s worth it because otherwise the company that designs the item may lose money and resources.

  • Design

When designing, the clients’ requirements are broken down into sections for implementation. Certain items like software and hardware are identified for each section so then the sections are designed accordingly. Diagrams are also designed to aid the design, which could be important. Pseudo Code is broken English language to show how you want the program to work. Your role will be to design the programming language by using JavaScript, C++ or VB.

  • Implementation

This is an actual software process where coding takes place, coding is written as part of the diagrams which are designed in the previous phase. Code is written for each section, which is then tested.

  • Testing

In this phase the program is tested to make sure that the program is fully working. The testing methods include Beta testing in which the designer releases a demo version of the program; it also asks a third-party to test the   whole program to ensure it meets their requirements. Alpha testing is using the users within the organization to test. Doing this enables the designers to see if there are any bugs and errors in the program, which if found can be quickly fixed. The code and design is then altered for the correct output and retests it again, it also may return to the Implementation phase to rewrite the codes. To record the result you could use a questionnaire or a test plan to test all of the functions. Another way is to observe the program being used to see if the program works.

  • Verification

In this stage, the item is validated before being sent to the client; also, the information that is in the item needs to be valid and truthful because the customer might end up declining and many lose trust in the company. Verification also checks to see if the item is fully completed.

  • Delivery

In this stage the final item when finished is sent it to the client after testing the faults, to see if the client likes the item or what they want to change. This is to make sure if the program has any problems you may need to go back to the design interface to repair the program.

  • Maintenance

In this stage, the development teams are constantly visiting the clients’ site to keep up with maintenance of the item. This is done to reduce the change of hacks and breaks in the item over time. The client secures a contract for so many years, which allows the development team to maintain the system. If the client wants the system updated then the development team starts from the first phase.

  • Evaluation

In this stage, the final item is checked for Pros and Cons, after these further improvements are made to the item where appropriate. These changes can be easily applied for the client when routine maintenance is due. This could happen at any time but mostly at the start just when the item has been finished.

References:  

http://en.wikipedia.org/wiki/Systems_development_life_cycle (Review 5th November 2014 – Water System life cycle)

http://en.wikipedia.org/wiki/Waterfall_model (Review 5th November 2014 – Water System life cycle)

http://www.computerworld.com/article/2576450/app-development/system-development-life-cycle.html (Review 5th November 2014 – Water System life cycle)

http://www.tutorialspoint.com/sdlc/sdlc_waterfall_model.htm (Review 5th November 2014 – Water System life cycle)

http://www.merttol.com/articles/web/web-site-development-life-cycle.html (Review 5th November 2014 – Water System life cycle)

Images:

http://upload.wikimedia.org/wikipedia/commons/thumb/1/19/SDLC_-_Software_Development_Life_Cycle.jpg/220px-SDLC_-_Software_Development_Life_Cycle.jpg (Review 5th November 2014 – System life cycle)

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s