stud
bud
Sign up
Log in
Home
Library
Explore
SAT
More
QAA BCS Systems Development Essentials - 4 Development Practices Flashcards | StudBud
Explore
/
QAA BCS Systems Development Essentials - 4 Development Practices
QAA BCS Systems Development Essentials - 4 Development Practices
10 terms
·
StudBud Administration
·
81 plays
A quiz on Development Practices
Flashcards
10 cards
F
Practice quiz
P
Host live
L
Questions
10
Answers
1
Which is NOT a typical need for bespoke development?
Software that supports exact business requirements
Software that supports routine business processes
Software that supports business value creation
Software that supports unique business processes
2
A typical Enterprise Resource Planning (ERP) system will NOT support?
Human Resource Management
Supply Chain Management
Unique requirements of a specific business sector
Customer Relationship Management
3
Which is NOT true of a component?
Can be combined to build applications
Reusable program building block
External specification independent of internal working
Must be created by bespoke internal development
4
What does COTS stands for?
Computer off the Shelf
Commercial off the Shelf
Customer off the Shelf
Cloud off the shelf
5
Which is NOT an example of a prototype?
Demonstration software
Design document
Sample screen / report
Working software
6
An advantage of a Software Package Solution is?
Competitive advantage
Cost, time and quality
100% fit to requirements
Financial stability of vendor
7
Which is a disadvantage of bespoke development?
Designed and built to meet exact business requirements
Only paying for features that are required
Can provide a competitive advantage
More expensive to build
8
With Evolutionary delivery how often can an iteration be deployed?
Daily
As agreed with the business
Weekly
Monthly
9
Which is an advantage of Agile?
Easier to manage
Control of scope creep
Suitable for projects with a strict contract
Earlier delivery of working software
10
Which value of the Agile Manifesto is correct?
Individuals and interactions over processes and tools
Comprehensive documentation over working software
Contract negotiation over customer collaboration
Following a plan over responding to change