Brainscape's Knowledge GenomeTM

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


See full index

Software Design 2016 > Question 5- SDLC \ Business system analysis > Flashcards

Question 5- SDLC \ Business system analysis Flashcards

1
Q

SDLC

(Software development life cycle)

A

Series of steps/ phases which provide a model for the development and life cycle management of a piece of software

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

4 Phases of SDLC

A

1-Planning
2-Analysis
3-Design
4-Implantation

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

Definition of phases

A

Each phase is a set of steps with the aim of delivering specific document files, which creates an understanding about the poject. Phases are executed sequentially incrementally, iteratively or in some other pattern

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

Planning

(PROJECT INITIATION / MANAGEMENT)

A

1-Identify and select system to develop
2-Assess feasibility
3-Develop project plan

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

Analysis

(WHO, WHAT, WHERE, WHY)

A

1-Gather business requirements
2-Create process diagrams
3-Buy vs build analysis

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

Design

(HOW)

A

1-Design IT infrastructure

2-Design system models (GUI, ERD’S)

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

Implementation

(BUILD)

A

1- Write detailed user documentation
2-Determine implementation method
3-Provide testning for system users

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

What is a methodology

A

*It is a formalised approach to implementing SDLC.
*It is a recommended series of steps and procedures to be followed in the course of developing an information system. e.g
Structured-Waterfall
RAD-Phased/prototyping
Agile-Extreme programming/SCRUM

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

Waterfall

A
  • Planning, Analysis, Design, Implementation, System
  • Development is sequential- moving from one phase to the next.
  • A large document is delivered and approved before continuing to the next
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Advantages Of Waterfall

A
  • Simple and easy to understand
  • Easy to manage
  • Phases processed/managed one at a time
  • Works well for small projects
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Disadvantages Of Waterfall

A
  • No working software product until late
  • High risk and uncertainty
  • Not suitable for products likely to change
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

When to use Waterfall

A
  • When requirements are well known
  • Product definition is stable
  • Technology is understood
  • Project is short
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

RAD- Rapid Application Development

A

Aim is to deliver some part of the system quickly, and deliver a working system to the user
examples- Prototyping

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

Prototyping

A

Prototyping preforms analysis, design, implementation phases concurrently. All phases are preformed and repeated in cycle until the system is complete

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

Agile Development

A
  1. Indivduals and interactions over processes and tools
  2. Workibng software over comprehensive documentation
  3. Customer collaboration over contract negotiation
  4. Responding to change over following a plan
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

eXtreme Programming (XP)

A
  • The best-known and most widely used agile method.
  • XP takes an ‘extreme’ approach to iterative development.
  • New versions are built several times per day.
  • Increments are delivered to customers every 2 weeks.
  • All tests must be run for every build and the build is only accepted if tests run successfully.
  • Continuous testing,
  • Simple coding
  • Close interaction with the end users to build systems very quickly
17
Q

Scrum

A
  • Teams are self-organized and self directed.
  • No designated team leader.
  • Teams organize themselves in a symbiotic manner and set their own goals for each sprint (iteration).
  • Once a sprint has begun, teams do not consider any additional requirements. Any new requirements that are uncovered are placed on a backlog of requirements
  • At the beginning of every workday, a Scrum meeting takes place.
  • At the end of each sprint, the team demonstrates the software to the client. Based on the results of the sprint, a new plan is begun for the next sprint.
    *Questionable whether Scrum can scale up to develop very large, mission-critical systems. A typical Scrum team
    size is no more than 7 memebers
18
Q

Factors for selecting Methodology

A
  • Clarity of user requirements
  • Familiarly with technology
  • System complexity
  • System Reliability
  • Short time schedules
  • Schedule visibility
19
Q

How RUP is structured

A
  • Inception – specifying the project vision
  • Elaboration – planning the necessary activities and required resources; specifying the features and designing the architecture
  • Construction – building the product
  • Transition – supplying the product the user community
20
Q

Advantages of RUP

A
  • Develop Software Iteratively – structure of RUP involves a series of iterations –mini-projects
  • Manage requirements – all development is driven by use-cases
  • Visually model software – UML provides us with the appropriate product deliverables for each activity, e.g.
  • Control changes to software
21
Q

Disadvantages of RUP

A
  • Heavy process – documentation heavy/ bureaucratic/ complex
  • Time consuming
  • Needs to be tailored – structured process
  • Needs training – requires skills
  • Expensive
  • Well managed
22
Q

3 Elements of the RUP

A

1- The RUP is use-case driven -Use-case driven means that the development process follows through the various
disciplines i.e. analysis, design, implementation, test that derive from the construction of the use-cases. The use-cases mature as the software process continues
2- The RUP is Architecture-Centric -The various views offered by UML allow developers, users and stakeholders to view the complete systems from a number of perspectives. Every product has both function (use-cases) and form (architecture) and they evolve simultaneously
3- The RUP is iterative and incremental- Mini projects are iterations that result in an increment. Iterations refer to steps in the workflows and increments evolve the product. They must be planned, organized around use-cases or/and risk areas.

23
Q

Incremental Development

A
  • Incremental/phased development breaks the system into a series of versions.
  • The product is designed, implemented and tested incrementally- with a little more added each time
  • It involves both development and maintenance.

Software Design 2016 (1 decks)

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