Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

3RD YEAR - SECOND SEM > Software Engineering 4 > Flashcards

Software Engineering 4 Flashcards

1
Q
  • Boehm’s spiral model,
  • the spiral development model,
  • the risk-driven model,
  • the cyclic model, and the incremental,
  • iterative model — is a cyclic, iterative model for software development that involves a risk-driven approach to developing products.
A

spiral model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q
  • combination of Waterfall Model and Iterative Model
  • allows refinement throughout each stage of the model. This means that one stage can be skipped for testing and returned to at a later point
A

spiral model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

best suited for complex embedded product development where the requirements are changing from the customer’s side.

A

spiral model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

HISTORY OF SPIRAL MODEL

A
  • Defined by Barry Boehm in his 1988 article.
  • This model was not the first model to discuss iterative development, but it was the first model to explain why the iteration matters.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

The product manager focuses on defining the spiral’s objectives, identifying the requirements needed to achieve the objective, and, lastly, defining the scope of the spiral

A

Planning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

In this phase of the cycle, the product manager identifies all of the potential risks associated with the spiral’s objectives and requirements. Risks can be * technical, financial, market-related, operational, and/or environmental.*

A

Risk

Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

engineers take what was documented in the requirements and translate it into a functional product. The product manager in this phase validates and ensures that what was built meets the requirements and objectives of the spira

A

Engineering & Development

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

evaluate the success of the output of the spiral using the defined metrics in the spiral objectives

A

Evaluation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Four Phases of Spiral Model

A
  1. Planning
  2. Risk Analysis
  3. Engineering and Development
  4. Evaluation
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Advantages of Spiral Model

A
  1. best suited for large projects
  2. supports risk handling
  3. flexibility in requirements
  4. customer satisfaction
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Disadvantages of Spiral Model

A
  1. difficulty in time management
  2. more complex than other SDLC model
  3. not suitable for small projects
  4. depend too much on risk analysis
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

WHEN TO USE SPIRAL MODEL?

A
  1. medium to high risk projects
  2. users are unsure of their needs
  3. risk and cost evaluation are important
  4. complex requirements
  5. significant changes are expected
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

four fold procedure

A
  1. evaluate first prototype
  2. define requirements of second prototype
  3. pland and design second protoytpe
  4. construct and test second prototype
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

early sample, model or release of a product built to test a concept or process or to act as a thing to be replicated or learned from

A

prototype

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q
  • sequential SDLC model where each development phase has a corresponding testing phase.
  • This ensures verification and validation throughout the process
A

V-Model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

originating in late 1980s Germany, is a software development framework, advancing over the waterfall model by incorporating early testing phases to promptly identify and resolve issues. It gained notable adoption, especially in industries like automotive manufacturing.

A

V - MODEL

15
Q

the 2 phases of v - model

A
  1. verification phase
  2. validation phase
16
Q

verification phase

A
  1. requirement analysis
  2. system design
  3. architectureal design
  4. module design
  5. coding
17
Q

Validation Phase

A
  1. unit testing
  2. integration testing
  3. system testing
  4. user acceptance testing
18
Q

initial phase involves understanding product requirements from the customer’s perspective through detailed communication.

A

Requirement analysis

19
Q

Once clear and detailed product requirements are obtained, the system design phase begins. This involves detailing the hardware and communication setup for the product. The system test plan is then based on this design.

A

System design

20
Q

Architectural specifications are designed with multiple technical approaches, considering technical and financial feasibility

A

Architectural design

21
Q

phase breaks down the system into modules, defining data transfer and communication. Integration tests are designed based on this for documentation

A

High Level Design (HLD

22
Q

In this phase, detailed internal designs for system modules, known as Low Level Design (LLD), are specified

A

module design

23
Q

system modules are developed using chosen programming languages and guidelines

A

CODING

24
Q

Unit Test Plans (UTPs) are created during module design to eliminate errors at the code level.

A

unit

testing

25
Q

conducted during the architectural design phase. This testing verifies the coexistence and communication of internal modules within the system

A

Integration testing

26
Q
  • is linked to the system design phase. It ensures the entire system’s functionality and communication with external systems.
  • This phase often uncovers software and hardware compatibility issues.
A

System testing

27
Q

examples of v - model

A
  1. Medical Device Software
  2. Automotive Embedded Systems
  3. Telecommunication Software
28
Q

ADVAnTAGES of V-Model

A
  1. for smaller projects
  2. early verification
  3. highly disciplined
  4. accurate process tracking
29
Q

DISADVAnTAGES of V-Model

A
  1. high risk changes
  2. slows down development process
  3. does not support iteration
  4. requires a lot of documentation
30
Q

WHEN TO USE V - MODEL?

A
  1. short project
  2. focus on early correction and detection of defects
  3. small-medium projects
  4. ample resources available
  5. requirements clearly defined
31
Q

ComparIson of spiral and v models

A

SPIRAL MODEL
* Testing is done in the spiral model at the end of the engineering phase
* Cost of spiral model is expensive
* Flexibility to change in the spiral model is not that difficult.
* The guarantee of success through the Spiral model is low
* It is iterative.

V - MODEL
* In V-model, testing activities start with the first stage.
* Cost of V-model is also expensive.
* Flexibility of V-model little flexible
* Guarantee of success through V-model is high
* It is not iteratve.

3RD YEAR - SECOND SEM (25 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions