Karteikarten
SLR 6 - Software Development
Karten in diesem Stapel (33)
- 1Steps of the Development Life CycleFeasibility
Requirements
Analysis and Design
Implementation
Testing
Evaluating
Maintenance - 2FeasibilityDetermine if the problem can be solved with a program
Should we proceed with development? - 3RequirementsDetermine what the program needs to do to solve the problem
Make a list of requirements which the client wants from the program - 4Analysis and DesignHow should the program work?
Define the structure of the program - 5ImplementationProgramming the actual program
- 6TestingTest to see if the program works as intended
Trying to find any bugs - 7EvaluatingEvaluating if the program is complete
Is it ready to release? - 8MaintenanceOnce the program is released
Updating and managing the program to make sure it carries on working after release - 9Models of DevelopmentWaterfall model
Rapid application development (RAD)
Spiral model
Extreme programming
Paired programming - 10Waterfall ModelEach phase has a clear start and end, connected like a chain. Can go backwards
Client input only at beginning so the software may need to be redone - 11Advantages of WaterfallSimple
Easy to manage
Defined start and end of stages
Easy to work out time scale
Easy to know next steps - 12Disadvantages of WaterfallNot flexible
High risk factor
Misunderstandings lead to big errors
Client is removed from development
Poor choice for unsure requirements - 13Rapid Application Development (RAD)Prototypes are made until a finished product is reached
Each prototype is created then evaluated
Each prototype takes a few weeks to be created - 14Advantages of RADClient is involved
Final program likely to meet client's requirements due to amount of testing
Every prototype is evaluated by the client
Prototypes make testing easier where different ideas can be tested - 15Disadvantages of RADNeeds regular contact with client
Does not scale well with larger projects
Not suitable if efficiency is a priority
Each cycle can take a few weeks - 16Spiral ModelRisk driven approach to development
4 stages - identifying objectives and purpose of each stage, designing, development and testing, plan the next iteration
Starts with core foundations and repeats through the stages - 17Advantages of SpiralFocuses on dealing with risks
Each rotation focuses on the next part of the program
Eliminates risks during development
Works well for large scale projects with lots of risk and uncertainty
Each part is evaluated before progression - 18Disadvantages of SpiralRisk management is a specialised skill and is costly
Going through each cycle takes time
It takes longer than other methods - 19Extreme ProgrammingFocuses on the idea that requirements shift during development
Prototypes are developed very quickly - 20Advantages of Extreme ProgrammingTakes into account that requirements may shift as the program is developed
Prototypes are developed quickly so there is a lot of client feedback - 21Disadvantages of Extreme ProgrammingA client is needed to be embedded into the team to provide instant feedback
- 22Paired ProgrammingTwo programmers sit at one computer, one codes and the other gives feedback
- 23Advantages of Paired ProgrammingQuality of code often very high
Code is seen with fresh eyes so errors are usually spotted
Code will be efficient
Low amount of bugs - 24Disadvantages of Paired ProgrammingHaving two developers work on one part means higher cost and time
Lots of collaboration is needed
Takes longer as less people are coding - 25AlgorithmsAn algorithm is the logical steps needed to solve a problem
Can be represented as a flow chart or pseudocode - 26Testing StrategiesBlack box testing
White box testing
Alpha testing
Beta testing - 27Black Box TestingOnly tests inputs and outputs of the program
If the output is expected then it passes
Tests if the overall code works as intended - 28White Box TestingTests every possible route the program can take
Tests how efficient each part of the code is - 29Alpha TestingHappens quickly
Tested internally
Very early version - 30Beta TestingHappens after development
Tested externally through sign-up programs
Almost finished product
Used to test things like load bearing and user input - 31Valid DataValid data/normal data is data that is expected by the program. Tests if the program can identify and use correct data
- 32Borderline DataBorderline/boundary Data is on the boundaries of valid and invalid data. Tests what the program considers correct data
- 33Invalid DataInvalid/Extreme Data is data that usually should not be inputted. Tests how the program handles invalid inputs
Informationen
- Beschreibung
- Karteikarten am SLR 6 - Software Development, erstellt von Jordan Larter am 13/01/2020.
- Erstellt von
- Jordan Larter
- Aufrufe
- 5
- Bewertung