Tuesday, December 11, 2012

Development Methodologies

What is a Method?
A method is a specific technique defined by a person in a way where a particular process can be carry on (Kinash, 2012). As an example the survey questionnaire. Also this contain model and life cycles. Method chosen depends in part on the Methodology used.


What is a Methodology?

A methodology is used to define how a method apply to conduct research (Kinash, 2012). It has body of knowledge which uses the methods (Kinash, 2012).

Why use a method?
- Define what you need to do
- Define the order in which you do it
- Improve your productivity
- To provide milestones

Other models and life cycles
- spiral model
- waterfall model
- V life cycle
- throwaway prototyping model
- evolutionary prototyping model
- incremental/iterative development
- reusable software model
- automated software synthesis 

17-12-2012
Sequential Methodology

1. Waterfall Project Life Cycle

The waterfall model prescribes a sequential execution of a set of development and management processes, 
with no return to an earlier activity once it is completed. Some variants of the waterfall model allow revisiting the immediately preceding activity if inconsistencies or new problems are encountered during the current activity.
Stages: 


Disadvantages of Waterfall Model
  • Very difficult to go back to any stage after it finished
  • No feedback loop
  • No testing/ quality assurance


Advantages of Waterfall Model
  • Easy to explain to the user
  • Establishes milestones
Concurrency Methodology

2. Evolutionary Project Plan

3. Spiral Life Cycle
Barry Boehm devised the spiral model to address the weaknesses of the waterfall model, especially its lack of resilience in the face of change. The spiral model focuses on addressing risks incrementally by repeating the waterfall model in a series of cycles or rounds:

  • Concept of Operation
  • Software Requirements
  • Software Product Design
  • Detailed Design
  • Code
  • Unit Test
  • Integration and Test
  • Acceptance Test
  • Implementation
Unit Test: Developer has access to code itself and do changes in it
Integration Test: QA don't have access to code only can use execution

RMMM (Risk Monitor, Measurement, Management)
Reactive                                                                     Proactive
When employee leaving the organization hire 


    Kinash, S. (2012) Paradigms, Methodology & Methods . [e-book] http://www.bond.edu.au/prod_ext/groups/public/@pub-tls-gen/documents/genericwebdocument/bd3_012336.pdf [Accessed: 11 December 2012].

    http://www.docstoc.com/docs/112380032/Software-Life-Cycle-Models-%28PowerPoint%29




    No comments:

    Post a Comment