Development Approaches Flashcards
1
Q
Characteristics of
Structured Development Approach
A
- Large scale
- Long, complex projects
- Formal stages
- Large team
- Start at the top and work progressively to the bottom
- Especially useful when all the requirements of the product are, or can be, defined and understood before any planning and design commences.
2
Q
Characteristics of
Agile Development Approach
A
- Close collaboration
- Requirements evolve, timescale is fixed
- Working version delivered after each iteration
- Interactive approach with selective refinement
- Constant testing
- Frequent updates
- Good for software that can be constantly improved
- Adapts to user feedback
3
Q
Characteristics of
Prototyping Development Approach
A
- Tests new design features which are incorporated in final product
- Progressively refined into working solution
- Relatively fast
- Models larger project allowing easier modification and visualisation of end product
- Frequent testing
- Many versions
- Medium sized projects
- Constant communication between users and devs
- Lack of absolute reliability, esp. early on.
4
Q
Characteristics of
RAD Development Approach
A
- Lack of formal stages
- Use of existing code routines where possible
- uses CASE (computer aided software engineering) tools
- Developer and client work together as a team
- Short time for completion
- Smaller projects
- Low budgets
- Compiling a variety of resources to create your product - don’t create it entirely from scratch
5
Q
Characteristics of
End User Development Approach
A
- Customise to unique requirements of user
- Cost effective in terms of development
- Completely modifiable when change in business dictate
- Bound by constraints of the functionality of the product
- Potentially open for errors due to lack of programming knowledge
- User customisation of readily available software applications to suit their needs
- No prior/limited expertise is needed
- Uses RAD and/or prototypes
- not a developer approach - built by the end user
- Quick, simplistic, small documents, limited documentation, don’t really plan ahead for problems, fix issues as they are encountered
6
Q
Use cases for
Structured Development Approach
A
- Driver software
- Operating software
- Large-scale systems
7
Q
Use cases for
Agile Development Approach
A
- Changing or Unknown requirements
- Need to get the software done quickly
- Web-based software
- Some mobile apps
- Software like Word and Excel that can be continually fine-tuned
- Operating systems
8
Q
Use cases for
Prototyping Development Approach
A
- Indie games
- Websites
- Social Media
9
Q
Use cases for
RAD Development Approach
A
- Mobile games
- Simple passion projects
- Sections of larger programs
10
Q
Use cases for
End User Development Approach
A
- Stock control (Microsoft Access or Excel)
- Small business – customer data base (Access)
11
Q
Stages
Structured Development Approach
A
- defining and understanding
- planning and designing
- implementing
- testing and evaluating
- maintaining
12
Q
Stages
Agile Development Approach
A
- Defining and understanding the initial problem
- Plan, design and implement
- Test and evaluate current solution
- Release working version to users
- Define and understand new requirements
- Repeat 2-5 as needed
13
Q
Stages
Prototyping Development Approach
A
- Defining and understanding the initial problem
- Plan and design the prototype
- Implement the prototype
- Test and evaluate the prototype
- Redefine the problem
- Repeat 2-5 as needed
- Implement operational solution
- Testing and evaluating
