1.2.3

avatar
Created by
Salima Hassan

Cards (53)

  • agile methodology
    how many stages are there and in order
    there are 3 stages
    -user requirements
    -sprint
    -iteration
  • agile methodology
    stage 1: user requirements
    what happens in this stage
    -they do this to focus on splitting up the project into user stories
    -user stories are descriptions of the different ways the system will be used, what it will look like and what they expect it look like
  • Agile Methodology
    stage 2: sprint
    what happends here
    -a development sprint is a short time frame during which a specific user story is completed
    -this product is a fully working "deliverable" that the client or market can use instantly
  • agile methodology
    stage 3: iteration
    what happens here
    -the deliverable is given to the client
    -the product is evaluated and this information is fedback into the next sprint planning meeting
    -the sprint planning meeting and the sprint are repeated until the full scope of the project is agreed as finished
  • agile methodology
    what is it
    has stges like waterfall lifecycle but some repeat to allow changes in requirements and develop a product over several iterations, called sprints
  • what are 3 drawbacks of agile methodology
    -less predictable on timing and cost as it constantly changes
    -requires a higher time input from the client as they costantly need to give feedback
    -can easily go off track(not initial idea) meaning higher cost and time input
  • what are agile methodology used for

    is best suited to projects where the client can constantly invest their time and have a good idea of what they want
  • what are the 3 merits of agile methodology
    -the client can take a product to the market more quickly
    -clients are able to have updates for the product
    -absolute gurantee that the product is what the client wants
  • algorithmic theory
    is a re-useable set of...
    instruction
  • algorithmic thinking
    what is it
    is a way of solving a problems by producing alogorithms
  • writing down an algorithm
    alogrithms can be written as a set of ...
    numbered steps to follow
  • writing down an algortithm
    in computing, often represent....
    algorithms using psuedcode or flow diagram
  • extreme programming
    2 drawbacks
    -the project is too code focuses and not design focuses, producers little to no documentations
    -if developers are split geographically it can cause issues when it is time for code review
  • extreme programming
    how many stages are there and name them in order
    5 stages
    -extreme planning
    -extreme desgining
    -extreme programming
    -extreme testing
    -acceptance testing
  • extreme programming
    stage 1 :extreme planning
    what happens here
    where the client is in costant communication with the project team to eastablish the requirements
    -the proeject then goes into "planning game" to plan out releases and what will be in each iteration
  • extreme programming
    stage 2 :extreme designing
    what happens here
    where they will build simple designs(of the important functions)
    -during this, it will develope "project metaphor", (this is a way to describe the project and build it up
  • extreme programming
    stage 3 :extreme programming
    what happens here
    where they will develope the agreed items from the planning game
    -during this time, one programmer will code and the other critiquing the code
  • extreme programming
    stage 4 :extreme testing
    what happens here
    this is where code is tested in units
    -integration testing is also completed to ensure it works together and the code is reviewed for efficiency and quality
  • extreme programming
    stage 5 : Acceptance testing
    what happens here
    where the client feeds back on the product in its current stage
  • extreme programming
    what are the 3 merits
    -can produce a product quickly for the client to be able to sell or use
    -the project is constantly refactoring(is the process of restructing code, while not changing its original functionality) in respose to continous client feedback(saves time and money for developing)
    -lower risk of failure because the client has continous feedback in the project
  • extreme programming
    what are they best used for
    best suited to project where the client keeps changing requirements but needs a product quickly to get to market and for the lowest possible price
  • extreme programming
    what is it
    is an agile methodology that is good for rapidly chaning user requirements
  • Rapid Application Development(RAD)
    how many stages are there and name them in order
    3 stages
    -analysis and design
    -Build, demonstrate and refine
    -testing and implementing
  • Rapid Application Development(RAD)
    stage 1: Analysis and design
    what happens here
    -when the project team will look at the user requirement against what they can adapt or use from other places
    -then they will produce a simple design
  • Rapid Application Development(RAD)
    stage 2: Build, demonstrate and refine
    what happens here
    This stage is repeated multiple times where the project team will:
    -develope a product
    -demonstrate it to the client
    -refine the product based on the feedback they have recieved
  • Rapid Application Development(RAD)
    stage 3: Testing and implementing
    what happens here
    -after every semi-stage 2 ther is a testing stage
    -once the client approves, the final stage is implementing the product
  • Rapid Application Development(RAD)
    what are the 2 drawbacks of RAD
    -requires alot of time from the client for feedback
    -the system focuces on producing a product that is good enough not perfect
  • Rapid Application Development(RAD)
    what are the 3 merits of RAD
    -allows a product to be made and put to market extremely quickly
    -the project is relevant to the client and for the market by the time, it is released
    -RAD produces iterative deliverables(means approved versions can be released)
  • Rapid Application Development(RAD)
    what are the best uses for RAD
    best suited for large projects that have short time scales, where it is important to have a timely release to keep market relevance
  • Rapid Application Development(RAD)
    what is it
    is another agile methodology which focuses on getting the product made and quickly
  • Spiral Methodology
    how many stages are there and name them in order
    4 stages
    -identification
    -Design
    -construction
    -Evalution and risk assessment
  • Spiral Methodology
    stage 1: identification
    what happens here
    -the client and the project team collaborate to establish requirements from the user
    -after the first spiral, this stage is also used to review what has been achieved before and what needs to be added
  • Spiral Methodology
    stage 2: design
    what are the spiral of the design stage
    -design stage
    -conceptual design(think)
    -architectural design
    -logical design
    -physical design
  • Spiral Methodology
    stage 2: design
    what happens here
    -during the first spiral they will develop a conceptual design for the project
    -then architectural design in the next spiral, then logical design and finally a physical design in the subsequent spirals
  • Spiral Methodology
    stage 3: construction
    what happens here
    -in this stage they develop the agreed requirements
    -during the first spiral a proof of concept version will be built to get feedback from the client, then functuality will be added in each spiral
  • Spiral Methodology
    stage 4: Evalution and risk assessment
    what happens here
    is used to evaulate the product by the client and assess the risk of what needs to be done
    • This information is then fedback into the next spiral
  • Spiral Methodology
    what is it
    is similar to the waterfall lifecycle but features an iterative agile aspect to it
  • what are 3 drawbacks of Spiral Methodology
    -can easily fall off track and the cost and time scales can increase
    -the client needs to make a large amount of time investment for feedback and evaluation to steer the project
    -produce poor quality documentation compared to waterfall
  • what are spiral methodology uses for (best suited)
    -where the client can invest theri time
    -where the client has a clear idea of what they want
  • what are the 3 merits of Spiral Methodology

    -a product can be developed at each cycle and more added to the system after each spiral(-this meanss the user sees a system very early on)
    -spiral makes use of prototypes(an early version of a product from which future versions are developed)
    -the client can see the product being developed to ensure its what they want