ITSS 4330 exam 1 | UPDATED Questions with 100%
Verified Answers
Q1: SDLC Phases
A: planning,
analysis,
design
implementation
Q2: Planning
A: Why should we build this system?
What value does it provide?
How long will it take to build?
Project management
IS dept makes the request
Feasibility analysis
Q3: Analysis
A: requirements/ determination what does the system do’
Model current system
Formulate a new system
Requirements (business model that reps the business data/processes)
System proposal
Q4: Design
A: erd, mapping things out
how are we doing that
Develop a design strategy
Design architecture and interfaces
Develop databases and file specifications
Hardware, software
Ui design
Develop the program design to specify
What programs to write
What each program will do
Q5: Implementation
A: Construct the system
Build it (write the programming code)
Test it
Install system
Train the users
Q6: structured design
, A: waterfall and parallel development
Q7: Waterfall
A: Sequential phases, heavy documentation, few changes allowed; pros—early
requirements clarity, stability; cons—slow, rigid, costly changes.
Q8: parallel development
A: Break into subprojects developed concurrently; faster delivery, but integration can be
complex
Q9: RAD
A: Rapid Application Development
Accelerates SDLC with tools (CASE, JAD, visual languages, code generators). Risk—
managing user expectations.
Q10: Types of RAD
A: Phased Development
Prototyping
Throwaway Prototyping
Q11: Phased Development
A: versions released sequentially; quick value but incomplete systems at first. Produce
operational software out first *each phase is a functional system
Q12: Prototyping
A: iterative cycles of analysis/design/implementation with evolving prototypes; fast
feedback but weak analysis may cause design flaws.
Cyclical system: keep working on until completed
Quickly makes a system that users can evaluate
Con: fast paced, cant analyze as effectively
Q13: Throwaway Prototyping
A: Early mockups/test models used to resolve issues, then discarded; slower than
prototyping but yields more reliable systems.
Longer than prototyping
More assurance for testin
Q14: OOSAD
A: Object-Oriented Systems Analysis and Design
Combines data + process focus via objects, often RAD■based. Must be
Use■Case Driven (simple, process■specific models). ~ one at time
Architecture■Centric (functional, static, dynamic views).
Iterative/Incremental (continuous refinement).
Verified Answers
Q1: SDLC Phases
A: planning,
analysis,
design
implementation
Q2: Planning
A: Why should we build this system?
What value does it provide?
How long will it take to build?
Project management
IS dept makes the request
Feasibility analysis
Q3: Analysis
A: requirements/ determination what does the system do’
Model current system
Formulate a new system
Requirements (business model that reps the business data/processes)
System proposal
Q4: Design
A: erd, mapping things out
how are we doing that
Develop a design strategy
Design architecture and interfaces
Develop databases and file specifications
Hardware, software
Ui design
Develop the program design to specify
What programs to write
What each program will do
Q5: Implementation
A: Construct the system
Build it (write the programming code)
Test it
Install system
Train the users
Q6: structured design
, A: waterfall and parallel development
Q7: Waterfall
A: Sequential phases, heavy documentation, few changes allowed; pros—early
requirements clarity, stability; cons—slow, rigid, costly changes.
Q8: parallel development
A: Break into subprojects developed concurrently; faster delivery, but integration can be
complex
Q9: RAD
A: Rapid Application Development
Accelerates SDLC with tools (CASE, JAD, visual languages, code generators). Risk—
managing user expectations.
Q10: Types of RAD
A: Phased Development
Prototyping
Throwaway Prototyping
Q11: Phased Development
A: versions released sequentially; quick value but incomplete systems at first. Produce
operational software out first *each phase is a functional system
Q12: Prototyping
A: iterative cycles of analysis/design/implementation with evolving prototypes; fast
feedback but weak analysis may cause design flaws.
Cyclical system: keep working on until completed
Quickly makes a system that users can evaluate
Con: fast paced, cant analyze as effectively
Q13: Throwaway Prototyping
A: Early mockups/test models used to resolve issues, then discarded; slower than
prototyping but yields more reliable systems.
Longer than prototyping
More assurance for testin
Q14: OOSAD
A: Object-Oriented Systems Analysis and Design
Combines data + process focus via objects, often RAD■based. Must be
Use■Case Driven (simple, process■specific models). ~ one at time
Architecture■Centric (functional, static, dynamic views).
Iterative/Incremental (continuous refinement).
