1.2.3 Software Development Flashcards

You may prefer our related Brainscape-certified flashcards:
1
Q

Identify the different stages of the Software Development Lifecycle (SDLC)

A
  • Feasibility
  • Requirements
  • Analysis and design
  • Implementation
  • Testing
  • Evaluation
  • Maintenance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Feasibility

A
  • Establishes whether or not the project can be done
    Considers factors of the project e.g. technical, economic, legal and political
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is a requirement?

A
  • A specific feature of the new system and recorded in a document called requirement specification
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What key sections can requirements be broken down into?

A
  • Interface: how the user interact with it
  • Functional: what the system will do
  • Performance: how well/fast will the system respond
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

SDLC: Analysis and Design

A
  • The process of taking the requirements of a new system and deciding what the system will look like, how will it store data
  • Design can only go ahead once the requirements specification has been completed
  • Each requirement needs to be incorporated into the design
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Waterfall lifecycle

A
  • Derives its name from cascading effect from one phase to another
  • Each phase has a well-defined start and end point with identifiable deliverables
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Advantages of the waterfall lifecycle

A
  • Simplicity makes it easy to manage
  • Everyone on the project is very clear on the responsibilities at each stage
  • Clear deliverables
  • Easy to see if a project is running to schedule
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Disadvantages of the waterfall lifecycle

A
  • Carries a lot of risk
  • The user doesn’t get to see the product for the first time until the project is near its end
  • Misunderstanding requirements can lead to a project that is not easy to fix
  • Requirements must be very well understood so this model is not suitable for complex projects
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Spiral model

A
  • Risk-driven development methodology
  • More of a guide for development teams, allowing them to adopt element of one or more other methodologies
  • Better thought of as a process model generator, where decisions on the software development methodology are made based on the risk identified
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Advantages of the spiral model

A
  • Risk management is at the heart of this model
  • Excellent for projects that contain a high level of risk
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Disadvantages of the spiral model

A
  • Complex nature of risk analysis increases costs - risk management is a highly specialised skill
  • If risk analysis is done badly, the project suffers
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Rapid Application Development (RAD)

A
  • Involves producing successive prototypes of the software until a final version is produced and approved
How well did you know this?
1
Not at all
2
3
4
5
Perfectly