S302 Study Guide

1. SAM domains that address external forces acting on an organization

a. Business Strategy & IT Strategy
2. Which domain of the SAM focuses on development, maintenance, and operations of the
information needed to support the organization?
a. IT Infrastructure & Process
3. Which domain of the SAM is the driver for the technology transformation alignment perspective?
a. Business Strategy
4. Strategy Execution Alignment Perspective
a. Driver: Business strategy
b. Performance criteria: Cost/service center
5. Strategy Execution Alignment Perspective (roles)
a. Role of top management: Strategy formulator
b. Role of IT management: Strategy implementer
6. Technology Transformation Alignment Perspective
a. Driver: Business strategy
b. Performance criteria: Technology leadership
7. Technology Transformation Alignment Perspective (roles)
a. Role of top management: Technology visionary
b. Role of IT management: Technology architect
8. Competitive Potential Alignment Perspective
a. Driver: IT strategy
b. Performance criteria: Business leadership
9. Competitive Potential Alignment Perspective (roles)
a. Role of top management: Business visionary
b. Role of IT management: Catalyst
10. Service Level Alignment Perspective
a. Driver: IT strategy
b. Performance criteria: Customer satisfaction
11. Service Level Alignment Perspective (roles)
a. Role of top management: Set priorities
b. Role of IT management: Executive leadership
12. Enterprise
a. A collection of organizations that share a common set of goals
13. Which element is not included in the Business Function viewpoint?
a. Process
14. Which element is found in the behavioral aspect of Archimate?
a. Function
15. Project Sponsor
a. -champions the project to outside parties to ensure resources are made available
b. -likely does not have any direct involvement with the work being completed
16. Systems analysis establishes the need for an information system and its extent.
a. True
17. The term "database development" is used to describe the process of database design and
implementation.
a. True
18. The primary objective in database design is to create complete, normalized, nonredundant, and
fully integrated conceptual, logical, and physical database models.
a. True
19. The implementation phase of database design includes creating the database storage structure and
loading the database, but does not provide for data management.
a. False
20. The Systems Development Life Cycle (SDLC) traces the history of an information system.
a. True
21. The Systems Development Life Cycle (SDLC) provides the big picture within which the database
design and application development can be mapped out and evaluated.
a. True
22. The Systems Development Life Cycle's (SDLC's) planning phase yields a general overview of the
company and its objectives.
a. False
23. In the Systems Development Life Cycle (SDLC), problems defined during the planning phase are
examined in greater detail during the analysis phase.
a. True
24. The analysis phase of the Systems Development Life Cycle (SDLC) involves a cycle of coding,
testing, and debugging.
a. False
25. The result of analysis phase of the Systems Development Life Cycle (SDLC) should be a better
understanding of the system's functional areas, actual and potential problems, and opportunities.
a. True
26. In the Systems Development Life Cycle(SDLC), the design of the system's processes begins in
the detailed systems design phase.
a. False
27. In the detailed systems design phase of the Systems Development Life Cycle (SDLC), steps are
laid out for the conversion of a database from an old system to a new system.
a. True
28. Training principles and methodologies are planned during the implementation phase of the
Systems Development Life Cycle (SDLC).
a. False
29. The detailed systems design phase of the Systems Development Life Cycle (SDLC) includes all
the necessary technical specifications for the screens, menus, reports, and other devices used to
make the system more efficient.
a. True
30. During the implementation phase of the Systems Development Life Cycle (SDLC), the hardware,
database management system (DBMS) software, and application programs are installed, and the
database design is implemented.
a. True
31. The system is subjected to exhaustive testing during the testing phase of the Systems
Development Life Cycle (SDLC).
a. False
32. In the Systems Development Life Cycle (SDLC), after testing is concluded, end-user training is
not necessary.
a. False
33. The database contents might be loaded interactively or in batch mode using a variety of methods
and devices including customized user programs.
a. True
34. A system is always at some stage of SDLC because every request for structural changes requires
retracing the steps of the Systems Development Life Cycle (SDLC).
a. True
35. A system maintenance activity generated in response to changes in the business environment is
referred to as corrective maintenance.
a. False
36. The Systems Development Life Cycle (SDLC) is a sequential process rather than an iterative
process.
a. False
37. To analyze the company situation, the database designer must discover what the company's
operational components are, how they function, and how they interact.
a. True
38. After the initial declarations in Database Life Cycle (DBLC), the database designer must
carefully probe in order to generate additional information that will help define the problem
within the larger framework of company operations.
a. True
39. The assignment of access rights may restrict operations on predetermined objects such as
databases, tables, views, queries, and reports.
a. True
40. The main purpose of a backup is to guarantee database restoration following a hardware or
software failure.
a. True
41. In most modern relational DBMSs, a new database implementation requires the creation of
special storage-related constructs to house the end-user tables.
a. True
42. Data integrity is enforced by the database management system (DBMS) through the proper use of
primary and foreign key rules.
a. True
43. The testing and evaluation phase of the Database Life Cycle (DBLC) occurs after applications
programming.
a. False
44. Database performance is one of the least important factors in all database implementations.
a. False
45. The overall purpose of the database initial study is to create the conceptual design.
a. False
46. Evaluation of database performance is rendered easier by the fact there are no standards to
measure it.
a. False
47. The database administrator must be prepared to perform routine maintenance activities within the
database.
a. True
48. Physical design becomes simpler when data is distributed at different locations.
a. False
49. Decentralized design is typical of relatively simple, small databases and can be successfully done
by a single person.
a. False
50. The process of creating an information system is known as __________.
a. System Development
51. The traditional Systems Development Life Cycle (SDLC) is divided into __________ phases.
a. Five
52. The initial assessment and the feasibility study are part of the Systems Development Life Cycle's
(SDLC's) __________ phase.
a. Planning
53. Discovery of user requirements, existing system evaluation, and logical system design are part of
the __________ phase of the Systems Development Life Cycle (SDLC).
a. Analysis
54. Coding, testing, and debugging are part of the __________ phase of the Systems Development
Life Cycle (SDLC).
a. Implementation
55. Installation and fine tuning are part of the __________ phase of the Systems Development Life
Cycle (SDLC).
a. Implementation
56. "Should the existing system be replaced?" is a question that is asked during the __________ stage
of the Systems Development Life Cycle (SDLC).
a. Planning
57. "What are the requirements of the current system's end users?" is a question asked during the
__________ phase of the Systems Development Life Cycle (SDLC).
a. Analysis
58. The logical systems design is created during the __________ phase of the Systems Development
Life Cycle (SDLC).
a. Analysis
59. The feasibility study during the planning phase of the Systems Development Life Cycle (SDLC)
must address the:
a. Technical aspects of hardware and software requirements.
60. The design of the system's processes is completed during the __________ phase of the Systems
Development Life Cycle (SDLC).
a. Detailed System Designs
61. The database contents are loaded during the __________ phase of the Systems Development Life
Cycle (SDLC).
a. Implementation
62. ITIL characteristics
a. Nonproprietary, nonprescriptive, provides best practices and good practices, developed
by Office of Government Commerce (independent office of British Treasury), generic
framework not based on any specific operating system, technology, or industry
63. Benefits of Applying ITIL
a. Establishes clear links between TI services and business strategies, improves quality and
speed of IT services and improves customer relations
64. Utility (Fitness for Purpose)
a. refers to the value offered by a service to support customer's performance on a task, OR
remove/reduce the effect of any constraints on the task.
65. Warranty (Fit for Use)
a. Assurance or guarantee that the service will meet its agreed requirements. Deals with four
characteristics describing how the service is delivered to the customers, all of which must
be present. The characteristics are:
b. Service must be available when it is required
c. Service must be provided at the right capacity/level
d. Service must have continuity, by consistently and continuously providing food service to
maintain its reputation
e. Service must provide security, meaning it must not involve risks for the customer, and if
unavoidable, minimize the risk.
66. ITIL Service Lifecycle Stages
a. Service Strategy
b. Service Design
c. Service Transition
d. Service Operation
e. Continual Service Improvement
67. Service Strategy Stage
a. Determining the underlying principles used for developed the policies, objectives,
guidelines, and processes that are required throughout the progression of the lifecycle.
Also involves identifying business opportunists. Lifecycle tends to rotate around this
stage because the decision made here will have impact on the subsequent stages of the
lifecycle
68. Service Design Stage
a. Stage in which IT services are designed and developed. Design encompasses all aspects
of the service, and is based on the principles founded during the Service Strategy stage
69. Service Transition Stage
a. Stage for creating the framework that will ensure that the designed service is effectively
and efficiently implemented in the live environment. This stage will include determining
risks, constraints, and whether the service will meet requirements. This ensures that the
expected performance is closely in line with the actual performance
70. Service Operation Stage
a. Stage in which all the required activities and processes for effectively running designed
services are carried out, so that the framework developed in the Service Transition stage
is effectively implemented
71. Continual Service Improvement Stage
a. Overarching stage in for maintaining the quality of services, done through learning and
improving on the processes involved in each stage of the ITIL Service Lifecycle. Helps to
ensure the effectiveness and efficiency of each stage
72. Enterprise stakeholder needs
a. 1. Maintain high quality information to support business decisions
b. 2. Generate business value from IT
c. 3. Achieve operational excellence through the reliable and efficient application of
technology
d. 4. Maintain an acceptable level of risk
e. 5. Optimize the cost of IT
f. 6. Ensure regulatory compliance
73. COBIT DRIVERS
 a. 1.More stakeholder involvement
b. 2. Increasing dependency of third parties
c. 3. Ever increasing volume of information
d. 4. IT becoming an integral part of the business
e. 5. A need for an end to end management and governance framework
f. 6. Better control over user based IT solutions
g. 7. Alignment with other guidance and integration of ISACA frameworks
74. Benefits of COBIT
a. 1. Starting point of governance and management activities
b. 2. Holistic, integrated and complete view of enterprise governance and management of IT
c. 3. Creates a common language between IT and the business
d. 4. IT consistent with generally accepted corporate governance standards
75. COBIT Initially in three volumes
a. 1. Framework
b. 2. Process reference guide
c. 3. Implementation guide
76. COBIT based on
a. 1. 5 principles
b. 2. 7 enables
77. COBIT Enabler guides
a. 1. Enabling processes
b. 2. Enabling information
c. 3. Other enabler guides
78. COBIT Professional Guides
a. 1. Implementation
b. 2. Information Security
c. 3. Assurance
d. 4. Risk
e. 5. Other Professional Guides
79. COBIT Principles (5)
a. 1. Meet stakeholder needs
b. 2. Cover enterprise end to end
c. 3. Apply a Single integrated framework
d. 4. Enable a holistic approach
e. 5. Separate governance from management
80. COBIT Principle 1
a. 1. Meeting Stakeholder Needs
b. 2. Governance objective - value creation
c. a. Benefit realization
d. b. Risk optimization
e. c. Resource optimization
81. Goals cascade is the mechanism to
a. Translate stakeholder needs into specific, actionable and customized
b. 1. Enterprise goals
c. 2. IT related goals
d. 3. Enabler goals
82. Goals Cascade
 a. 1. Stakeholder drivers (environment, technology evolution) influence
b. 2. Stakeholder needs of benefit realization, resource optimization, risk optimization
c. 3. Which cascades to stakeholder needs and enterprise goals
d. 4. These cased to IT related goals - which consist of enterprise goals mapped to IT related
goals
e. 5. These cascade to enabler goals
83. Stakeholder needs are influenced by a number of drivers
a. 1. Strategy changes
b. 2. Changing business and regulatory environment
c. 3. New technologies
84. Enterprise goals
a. 1. Business or balanced scorecard
b. 2. Consists of bsc dimension, enterprise goal
c. 3. Relation to governance objective
85. Balance (Business) Score Card dimension
a. 1. Financial - enterprise goals
b. 2. Customer - enterprise goals
c. 3. Internal - enterprise goals
d. 4. Learning and growth - enterprise goals
86. Relation to governance objectives (primary, secondary, N/A)
a. 1. Benefit realization
b. 2. Risk optimization
c. 3. Resource optimization
87. IT Related Goals
a. IT BSC Dimension (Financial, customer, Internal, Learning and growth) - related goals
88. Goals Cascade Step 1
a. Stakeholder drivers influence needs which are influenced by a number of drivers
b. a. Strategy changes
c. b. Changing business and regulatory environment
d. c. New technologies
89. Goals Cascade Step 2
a. Stakeholder needs cascade to enterprise goals
b. Stakeholder needs can be translated to a series of generic enterprise goals using the
balanced score card dimensions
90. Goals Cascade Step 3
a. Enterprise goals cascade to IT related goals
b. a. Achievement of enterprise goals requires a number of IT related goals
c. b. Structured along a dimension of an IT balanced scorecard
91. Goals Cascade Step 4
a. IT related goals cascade to enabler goals
b. a. Achieving IT related goals requires the successful application and use of enablers
c. b. Enablers include
d. i. Processes
e. ii. Organization structures
f. iii. Information
g. c. For each enabler a set of specific relevant goals can be defined
92. Governance enablers
 a. Organizational resources for governance
b. a. Frameworks
c. b. Principles
d. c. Structures
e. d. Processes and practices
f. 2. Enterprise resources
g. a. Service capabilities
93. Enterprise enablers - 7 of them
a. Principles, policies and frameworks
b. 2. Processes
c. 3. Organizational structures
d. 4. Culture, ethics and behavior
e. 5. Information
f. 6. Services, infrastructure and applications
94. Principles, policies and frameworks
a. The vehicle to translate desired behavior into practical guidance for day to day
management
95. Processes
a. An organized set of practices and activities to achieve certain objectives
96. Organizational structures
a. The key decision making entities in an enterprise
97. Information
a. All information produced and used by the enterprise
List 3 things that a software development lifecycle identifies
1) The exact activities of developments from initial inception to phasing it out
2) The applied modelling approach
3) The method (methodology) and associated development process
Requirements Elicitation is part of the Application Domain (True or False)
True
Analysis is part of the Application Domain (True or False)
True
System is part of the Solution Domain (True or False)
False
Object Design is part of the Solution Domain (True or False)
True
Program Implementation is part of the Application Domain (True or False)
False
Testing is part of the Application Domain (True or False)
False
Delivery is part of the Solution Domain (True or False)
True
Maintenance is part of the Application Domain (True or False)
False
List the 8 activities of the software development lifecycle
1) Requirements Elicitation
2) Analysis
3) System Design
4) Object Design
5) Program Implementation
6) Testing
7) Delivery
8) Maintenance
What is a Model?
A model is an abstract representation of a system that enables us to answer questions about the system
The Object-Oriented approach for software development evolves around class models
True
What does the software life cycle describe
The software lifecycle describes activities of the software cycle and the order in which those
activities are executed.
List the 7 different software lifecycle models
1) Waterfall model
2) V-Model
3) Incremental and Iterative Model (Phased Model)
4) Prototype Model
5) Spiral Model
6) Extreme Programming Model
7) SCRUM

The Waterfall software lifecycle model follows a structured methology (True or False)
True
The V-Model (software development lifecycle) follows a structured methology (True or False)
True
The Incremental and Iterative software lifecycle model follows a structured methology
False
The Prototype software lifecycle model follows a rapid application development methodology
True
The Spiral software lifecycle model follows an agile software development methology
False
The Extreme Programming software lifecycle model follows an agile software development
methology
True
The SCRUM software lifecycle model follows an agile software development methology
True
The Waterfall model of the SDLC is an exponential-sequential life cycle model
False
What is the Waterfall model of the SDLC?
In a waterfall model, each activity must be completed in its entirety before the next activity can
begin, and activities do not overlap
What are the advantages and disadvantages to the Waterfall model of the SDLC?
Advantages:
- Simple and easy to use
- Easy to manage (each activity has specific deliverables and a review process)
- Activities are processed and completed one at a time
Disadvantages:
- It's difficult to respond to changing customer requirements
- Adjusting scope during the life cycle can kill a project
- No working software is produced until late during the life cycle
- High amounts of risk and uncertainty
What is the V-Model of the SDLC?
- Each activity must be completed before the next begins
- The testing procedures are developed early in the life cycle before any coding begins in the
implementation activity
What are the advantages and disadvantages of the V-Model of the SDLC
Advantages:
- Simple and easy to use
- Each phase has specific deliverables
- Higher chance of success over the waterfall model due to the development of test plans early
during the life cycle
Disadvantages:
- Very rigid
- Little flexibility and adjusting scope is difficult and expensive
- Software is developed during the implementation phase, so no early prototypes of the software
are produced
- Model doesn't provide a clear path for problems found during test phases
The Waterfall model of the SDLC works well for smaller projects where requirements are very well
understood/stable
True
The Waterfall model of the SDLC is a good model for long run projects (True or False)
False
The V-Model of the SDLC works well for larger projects where requirements are easily understood
False

What is the Incremental and Iterative (Phased) Model of the SDLC?

- A working version of software is produced during the first iteration, so you have working
software early on during the software life cycle
 - Subsequent iterations build on the initial software produced during the first iteration
- Iterative methodology allows us to iterate over the activities, moving backwards and forwards,
or round and round.
- Each cycle is an executable release
What are the advantages and disadvantages of the Incremental and Iterative model of the SDLC
Advantages:
- System functionality is available earlier and customer does not have to wait as long
- Early increments act as a prototype to help elicit requirements for later increments
- The highest priority functionalities tend to receive more testing
- More flexible (less costly to change scope and requirements)
- Earlier to test and debug during a smaller iteration
- Each iteration is an easily managed milestone
Disadvantages:
- Each activity of an iteration is rigid and do not overlap each other
- Problems may arise pertaining to system architecture because not all requirements are gathered
up in front for the entire software life cycle

What is the Prototype model of the SDLC?

- In this model, a protoype is build, tested, and then reqorked as necessary until an acceptable
requirements is finally achieved from which the complete system can now be developed
- The prototype is evaluated by the customer/user and used to refine the requirements for the
software to be developed
What are the two kinds of Prototype models?
1) System Prototype
2) Throw-away prototype
What is a System Prototype?
- A prototype that is retained after the requirements elicitation process and used to produce the
final product
- Typically concentrates on well-understood requirements so that the first version of the product
can be delivered quickly
What is a Throw-Away Prototype?
- The prototype is discarded when the requirements elicitation is completed
- Typically concentrates on the least understood requirements
What are the advantages and disadvantages of the Prototype model of the SDLC
Advantages:
- Help understand the requirements for the user interface
- Examining feasibility of a proposed design approach
- Exploring system performance issues
Disadvantages:
- Users treat the prototype as the solution
- A prototype is only a partial specification
What are the 4 phases of the Spiral Model of the SDLC
1) Identification
2) Design
3) Construct or Build
4) Evaluation and Risk Analysis
What are the advantages and disadvantages of the Spiral Model
Advantages:
- The emphasis on alternatives and constraints supports the resuse of existing software
Disadvantages:
- A major strength of spiral model is that it is risk driven, but this can also be a weakness
 - If risk analysis leads to the conclusion that the project should be terminated, an attempt by either
customer or developer to terminate their contract can lead to a breach-of-contract lawsuit
The Spiral model is applicable to large scale software projects (True or False)
True
What does the Agile software development model emphasisze on?
The Agile model emphasizes on simple iterative application development, in which every
iteration is complete software project, including all developing activities
What is the SCRUM model of the SDLC?
- SCRUM is a simple management framework for incremental product development using one or
more cross functional, self-organizing teams of about 7 each
- Scrum teams use fixed length iterations, called sprints, typically 2 weeks or 30 days long
- Scrum teams attempt to build a potential shippable (properly tested) product increment every
iteration
What is the Product Owner in the SCRUM model?
- The single individual responsible for return on investment (ROI) of the product development
- Owns the product vision, re-prioritizes the product backlog, and revises release plan
expectations
- The final arbiter of requirements questions, including which teams are considered "done" at the
Sprint Review Meeting
What is the SCRUM team in the SCRUM model?
- Cross functional group
- Attempts to build a potential shippable product increment every sprint
- Collaborates and is self-organizing
What is the SCRUM Master in the SCRUM model?
- Facilitates the SCRUM process, keeps the SCRUM artifacts visible
- Facilitates Team self-organization
- Shields the team from interference
- Encourage the team to improve their engineering practices
The SCRUM Master does not make business decisions or technical decisions (True or False)
True
The SCRUM Master is the project manager
False
What are functional requirements?
Functional requirements describe the interactions between the system and its environment,
independent from the implementation. It does not focus on any of the implementation details
What are non-functional requirements?
Non-functional requirements describe aspects of the system that are not directly related to
functional behaviour of the system. Non-functional requirements could be quality requirements,
or constraints
List 5 things that should not be in the requirements
- System structure, implementation technology
- Development methodology
- Development environment
- Implementation language
- Reusability
When designing interview questions for the requirements elicitation, the interviewer should ask
close ended questions (True or False)
False