Software Development Lifecycle Models Flashcards Preview

CMSC 128 - Introduction to Software Engineering > Software Development Lifecycle Models > Flashcards

Flashcards in Software Development Lifecycle Models Deck (20):
1

A series of actions / someting that leads to a result

Process

2

Difference of a model and a process

A model is an abstraction of processes while a process is the implementation

3

It defines the framework under which a software product is going to be developed

Software development life cycle

4

Phases the product under development go through in a life cycle model

High level

5

Activities involved in each of the model phases and their respective deliverable

Lower level

6

Phases of SDLC

Analysis
Design
Implementation
Testing & integration
Installation / deployment & maintenance

7

Phase - identify requirements and define specs

Analysis

8

Phase - high-level database, architectural and interface

Creating ERD/Class Diagram, network design, use case, activity, mockup design, prototypes

Design

9

Phase - design into executable code

Implementation

10

Phase - modules are tested. If passed, it is integrated

Testing and integration

11

Phase - deployment of product to client’s environment

May have to be supported for periodic updates / fix bugs

Installation / deployment and maintenance

12

Stop the use of the product

No support for updates and fixes

End of life

13

Software development model presented by WINSTON ROYCE whrein each phase must be finished first before moving to the next phase

Waterfall method

14

Software development model wherein it allows visualization of requirements and find out the errors earlier

Prototyped waterfall model

15

Software development model wherein it has
1. Analysis / identification of problem domain
2. Design / solution domain classes and interrelationships, interface, entity
3. Implementation - use Java, C++, Csharp
Use UML

Object Oriented Model

16

Prioritize requirements

Identify requirements for different releases

Use a model to develop each release

Incremental and iterative model

17

Software development model introduced by barry boehm wherein this model addresssed the weakness of waterfall model in respect to the treatment of software development risks

Embeds risk management ctivities within development activities

Spiral model

18

Phases of a spiral model

1. Identification of objectives, alternatives and contraints relevant

2. Evaluation and assessment of the alternatives with respects to constrains and identifies ootential risks

3. Develop phase deliverable by erforming its activities followed by a review of these deliverables

4. Preparation and planning for the following phase

19

Main reason for software project failure

Software risks and the lack of a clear and continuous risk management strategy

20

6 Lightweight software development methods

Agile
Scrum
Rapid Applications Development
Extreme programming
Adaptive software development
Dynamic systems development