CS1004: Block 4 - Business Analysis
Q
What is the Waterfall model?
A
A sequential, one-way, progressive flow of activity and
information.
--
2
Q
Advantages of the waterfall model?
A
Practical and easy to use
Simple structured approached agreed content and structure
Emphasis on analysis and design documentation
--
3
Q
Disadvantages of the waterfall model?
A
Requirements, processes and data structure evolve over time
Technology changes very rapidly
The market changes very rapidly
--
4
Q
When is the waterfall model appropriate?
A
Systems not expected to change over time
Safety-critical systems
computerizing existing manual systems without major changes
--
5
Q
What is RAD(Rapid application development)
A
RAD based on prototyping and incremental and or evolutionary delivery
--
6
Q
Principles of RAD
A
Requirement cannot always be specified in advance,
Requirements are never complete
80/20 rule:80% of the system can be built in 20% of the time
Most important requirements build first
--
7
Q
What is DSDM
A
Evolved from RAD for the purpose of meeting tight schedules, budgets and quality standards.
Focusing on quality assurance
Structure to RAD and increase the likelihood of success
More formalized procedures
--
8
Q
What is Extreme programming?
A
A continuous process of development, testing, integration and very frequent small releases.
Intends to improve;
Software quality
Productivity
Responsiveness to changing requirements
--
9
Q
Some characteristics of XP?
A
Customer directly prioritises work
Pair programming
Test-driven development
Delay programming of features until they are needed
--
10
Q
Criticisms of Agile methods?
A
Lack of design and documentation
Finding the balance with enough design and documentation but not too much.
Need for above-average programmers
Above-average programmers always create above average code.
Just an excuse for “cowboy coding”, e.g. in
terms of face-to-face communication and relatively
sparse use of documentation.
--
11
Q
Differences: traditional vs. agile methods
A
Compared to traditional methods, agile ones
emphasise:
Continuous customer participation in development decisions and interaction with developers.
Timeboxing: fixed resources and deadline instead of fixed requirements.
Iterative development and more frequent release of software versions.
Small teams in close collaboration.
--
12
Q
Who is involved in system development?
A
The user/ stakeholders
The developer or programmer: turning requirements into programs
The analyst developers and users do not “speak” the same language
--
13
Q
Who is the analyst?
A
The person who communicates user requirements and translates them into computer programmes.
Bridges the gap between developer and user
--
14
Q
What is a methodology?
A
Collection of procedures, techniques, tools, notations, and documentation
Aids developers efforts to implement Information Systems
Guiding choice of techniques for carrying out the tasks
--
15
Q
Levels of user engagement; Waterfall model
A
User agrees requirements
Developers do design and implement it
The user performs acceptance trials
--
16
Q
Levels of user engagement; RAD
A
The user is involved in all critical decisions
Users “buy into” the design decisions
--
17
Q
RAD Vs Waterfall;
Cost
Time
Requirements
A
Waterfall;
Cost-flexible
Time-flexible
Requirements-fixed
RAD;
Cost-fixed
Time-fixed
Requirements-flexible
--
18
Q
Four phases of RAD
A
Requirements planning phase
User design phase
Construction phase
Cutover phase
--
19
Q
Stages in System development life cycle
A
Scope and objection
Feasibility study
System Analysis
System Design
Implementation
System in use
Evaluation and maintenenace--
20
Q
What is the cost of correction
A
Cost of correction is multiplied by 10
--
21
Q
Principles of DSDM
A
The project team must be empowered to make decisions.
User involvement is the key to an efficient and effective project.
All changes are reversible.
--
22
Q
One characteristic of cowboy coding?
A
Uncertain design requirements