ISDS 406 Exam with 90 Questions and
Correct Answers
ways to categorize projects - ANSWER -size
-cost
-purpose
-length
-risk
-scope
-economic value
duties of a project manager - ANSWER -Select best methodology
-Develop a project work plan
-Establish a staffing plan
-Create ways to coordinate and control the project
Waterfall development methodology - ANSWER Assumes a project phase is complete
before moving to the next phase. Doing each phase thoroughly before moving
forward ensures correct and high-quality outcomes
waterfall methodology assessment - ANSWER Strengths: system requirements
identified long before construction begins, requirements are "frozen" as project
proceeds (no moving targets)
Weaknesses: must wait a long time before there is "visible" evidence of the new system,
takes a long time from start to finish
Parallel Development Methodology - ANSWER subdivide the project into
subprojects that can be worked on at the same time, reduces the project length
, parallel development assessment - ANSWER strengths: reduces overall project
time compared to waterfall, reduces the need for rework; with shorter time frame,
less change of requirements changing
Weaknesses: creating subprojects requires careful design decisions, integrating
subprojects at the end can be complex and difficult
V-Model Development Methodology - ANSWER Emphasizes system quality through test
plan development
V-Model Methodology Assessment - ANSWER Strengths: simple and straight forward,
quality improves through the emphasis on testing, includes quality assurance
expertise early in the project
Weaknesses: rigid, difficult to use in a dynamic business environment
Rapid Application Development (RAD) - ANSWER Incorporate special techniques
and tools: CASE tools, JAD sessions, visual programming languages and visual
editors of traditional programming languages
Iterative development methodology - ANSWER RAD: Develop system in series
of versions
Iterative development methodology assessment - ANSWER Strengths: users get a
system to use quickly, users identify additional needs for later versions based on
real experiences with current version
Weaknesses: users faced with using an incomplete system for a time, users must
be patient and wait for fully-functional system
Correct Answers
ways to categorize projects - ANSWER -size
-cost
-purpose
-length
-risk
-scope
-economic value
duties of a project manager - ANSWER -Select best methodology
-Develop a project work plan
-Establish a staffing plan
-Create ways to coordinate and control the project
Waterfall development methodology - ANSWER Assumes a project phase is complete
before moving to the next phase. Doing each phase thoroughly before moving
forward ensures correct and high-quality outcomes
waterfall methodology assessment - ANSWER Strengths: system requirements
identified long before construction begins, requirements are "frozen" as project
proceeds (no moving targets)
Weaknesses: must wait a long time before there is "visible" evidence of the new system,
takes a long time from start to finish
Parallel Development Methodology - ANSWER subdivide the project into
subprojects that can be worked on at the same time, reduces the project length
, parallel development assessment - ANSWER strengths: reduces overall project
time compared to waterfall, reduces the need for rework; with shorter time frame,
less change of requirements changing
Weaknesses: creating subprojects requires careful design decisions, integrating
subprojects at the end can be complex and difficult
V-Model Development Methodology - ANSWER Emphasizes system quality through test
plan development
V-Model Methodology Assessment - ANSWER Strengths: simple and straight forward,
quality improves through the emphasis on testing, includes quality assurance
expertise early in the project
Weaknesses: rigid, difficult to use in a dynamic business environment
Rapid Application Development (RAD) - ANSWER Incorporate special techniques
and tools: CASE tools, JAD sessions, visual programming languages and visual
editors of traditional programming languages
Iterative development methodology - ANSWER RAD: Develop system in series
of versions
Iterative development methodology assessment - ANSWER Strengths: users get a
system to use quickly, users identify additional needs for later versions based on
real experiences with current version
Weaknesses: users faced with using an incomplete system for a time, users must
be patient and wait for fully-functional system
