System Development Methods > SDM Important Points > Flashcards

SDM Important Points Flashcards

(100 cards)

Study These Flashcards
1
Q

What is Direct Changeover (Big Bang approach)

A

Switch to new system and completely shut down the old system

No overlap or gradual introduction, change is immediate and irreversible

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Advantages of Direct Changeover (3)

A
  1. This method is the least expensive and fastest to execute.
  2. The benefits of the new system are available to all users immediately.
  3. There is no need to maintain or synchronize two different systems.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Disadvantages of Direct Changeover

A
  1. It is extremely risky because there is no backup system if the new one fails.
  2. The transition can be very stressful and disruptive for users and support staff.
  3. It requires thorough and near-perfect testing before implementation.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is Parallel Changeover (Blue-Green)?

A

Both the old and the new systems run simultaneously for a set period.

Once the new system is proven to be stable and reliable, the old system is decommissioned.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Advantages of Parallel Changeover (3)

A
  1. It is the safest method as the old system provides a reliable backup.
  2. Results from both systems can be compared to verify the accuracy of the new one.
  3. Users have more time to learn and adapt to the new system without pressure.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Disadvantages of Parallel Changeover (3)

A
  1. It is the most expensive method due to the cost and effort of running two systems.
  2. Entering data into both systems can be confusing and labor-intensive for staff.
  3. It can be difficult to get a true comparison if the systems have different functionalities.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is Pilot Changeover?

A

New system is first implemented in a small, controlled part of the organization, such as a single department or location.

If the implementation is successful, the system is then rolled out to the rest of the organization, often using a direct or phased approach.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Advantages of Pilot Changeover? (3)

A
  1. Any failures or problems are contained within the pilot area, minimizing business disruption.
  2. The implementation team can learn from the pilot and make improvements before a full rollout.
  3. The pilot group can provide valuable feedback and support other users during the wider launch.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Disadvantages of Pilot Changeover? (3)

A
  1. The pilot group may not be representative of the entire organization’s needs.
  2. It can be discouraging for the pilot users if they encounter significant problems.
  3. The overall transition process takes longer than a direct changeover.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is Phased Changeover?

A

Gradually introducing the new system one module or component at a time

Continues in stages until the old system is entirely replaced by the new one.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Advantages of Phased Changeover (3)

A
  1. It allows users to adapt to the new system gradually, one part at a time.
  2. The risk is spread out, as technical problems are limited to a single module.
  3. The financial investment for the new system can be spread over a longer period.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Disadvantages of Phased Changeover (3)

A
  1. The full implementation can be a very long and slow process.
  2. It can be complex and costly to create temporary interfaces between new and old modules.
  3. Users must work with a mix of old and new systems, which can be confusing.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

List out 5 advantages of Software Testing

A
  1. Testing improves product quality by identifying and removing defects before the software is released to users.
  2. It is cost-effective because finding bugs during development is significantly cheaper than fixing them after launch.
  3. Specialized testing helps** increase security** by identifying and fixing vulnerabilities that could be exploited.
  4. A well-tested, reliable product leads to higher customer satisfaction and greater trust in the brand.
  5. Testing verifies that the software meets all specified business and technical requirements.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

List out 5 disadvantages of Software Testing

A
  1. The process can be very time-consuming, potentially delaying the product’s final release to the market.
  2. It is an expensive activity, requiring a significant budget for skilled personnel, tools, and infrastructure.
  3. Testing is naturally incomplete, as it’s impossible to test every single scenario, meaning some bugs will always remain.
  4. Passing all planned tests can create a false sense of security, as unexpected issues can still appear in a live environment.
  5. Test plans require constant updates and maintenance every time the software is changed or a new feature is added.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

List out 8 strategies before coding

A
  1. System Architecture to be Used
  2. Choice Programming Language
  3. Programming/ Coding Standards
  4. Types of Testing to be Carried Out
  5. User Involvement
  6. Code Repository (Store, Secure & Share code to other)
  7. Version Control (Backup & restore codes)
  8. SecurityandCopyright
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

List out 5 good programming practices

A
  1. Efficiency CKISS)
  2. Portability (Use good variables and no hard codes)
  3. Security (Code Repository, Encapsulation)
  4. Readable Codes (Meaningful and Informative varible, comments ,formats)
    5.Refactoring
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

List out 6 phases of Waterfall Methodology

A
  1. Requirements Analysis
  2. System Design
  3. Implementation (Development)
  4. Testing (Verification)
  5. Deployment (Installation)
  6. Maintenance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

List out risk management strategies that think that risk may happen

A
  1. Risk Transfers (Transfer to Vendor / Customer)
  2. Risk Avoidance (Alternative path to Avoid - May change original design )
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

List out risk management strategies that think that risk will happen

A
  1. Risk Reduction (Take additional steps - increase cost, delivery time)
  2. Risk Acception (Implement total solution - Time consuming and Costly)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

List out system planning strategies that is before and after Requirements Engineering / Elicitation

A
  1. Feasibility Study
  2. Resource Planning
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

What does SDLC - Planning focus on?

A

Assessing the feasibility and scope of the project. The goal is to determine if the project is viable and to create a high-level plan for its execution

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

What is the Sub-Tasks of Planning?

A

Feasibility study (economic, technical, operational), resource allocation, project scheduling, risk assessment.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Which role are involved in Planning

A

Project Manager, Business Analyst, Stakeholders, Senior Management.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

What document are being output in Planning?

A

Feasibility Study Report

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Which document are being inputted in Planning?
Project Request, Business Case, Market Research.
25
List out 3 popular techniques used in Planning
1. Gantt Charts 2. PERT Charts 3. Feasibility Analysis
26
What is the Focus on SDLC - Analysis
Understand and document the exact requirements of the system from all stakeholders.
27
List out sub tasks involved in Analysis
Elicitation and document functional and non-functional requirements, create use cases, conduct requirement analysis.
28
List out people involved in Analysis
Business Analyst, System Analyst, End-users, Subject Matter Experts (SMEs), Project Manager.
29
List out input documents for Analysis
Feasibility Study Report
30
List out output documents for Analysis
Software Requirements Specification (SRS)
31
List out popular techniques used in Analysis
Interviews, Surveys, JAD (Joint Application Development) sessions, Prototyping.
32
What is the focus on SDLC - Design?
Translates the requirements from the SRS into a detailed blueprint for building the system, covering architecture, data, and user interface.
33
What are the sub tasks for Design?
High-Level Design (architecture), Low-Level Design (modules), database design, UI/UX design.
34
List out people involved in Design
System Architect, UI/UX Designer, Lead Developer, Database Administrator (DBA).
35
List out Input documents for Design
Software Requirement Specification (SRS)
36
List out Output Documents for Design
Design Specification Document (DSD)
37
List out popular techniques used in Design
UML Diagrams (Class, Sequence, Activity), ERDs, Prototyping, Wireframing.
38
What is the focus on SDLC - Development?
Write the actual source code and build the software system
39
List out the sub task in Development
Writing source code, creating databases, performing unit tests.
40
List out people involved in Development
Developers (Front-end, Back-end, Full-stack), DBA.
41
List out input documents for Development
Design Specification Document (DSD).
42
List out output for Development
Fully functional system
43
List out popular techniques for Development
Programming languages (Java, Python, etc.), IDEs (VS Code, IntelliJ), Version Control (Git).
44
List out focus on Implementation
Released to the live production environment, making it available to end-users.
45
List out sub tasks for Implementation
Installing the software on servers, data migration, user training, and formal release.
46
List out people involved in Implementation
DevOps Engineer, System Administrator, IT Support, End-users.
47
List out Input Documents for Implementation
Tested Software Build, User Manuals.
48
List out Output for Implementation
Deployed Working System, Training Materials, Release Notes
49
List out Popular Techniques in Implementation
Big Bang, Phased, or Parallel Deployment; CI/CD Pipelines.
50
List out focus on Maintenance
System is monitored, updated, and enhanced to address issues and new requirements.
51
List out sub task for Maintenance
Bug fixing, system updates, adding feature enhancements, performance monitoring, user support.
52
List out People Involved in Maintenance
Maintenance Team, Developers, IT Support/Help Desk.
53
List out Input for Maintenance
Deployed System, User Feedback, Bug Reports.
54
List out Outputs for Maintenance
Updated Source Code, Patch Documentation, Release Notes.
55
List out Popular Techniques for Maintenance
System Monitoring Tools, Version Control, Ticketing Systems (e.g., Jira).
56
List out 4 phases of Rapid Application Development
1. Analysis & Quick Design 2. Prototype Cycles (Develop, Demonstrate, Refine) 3. Testing 4. Deployment
57
List out 4 techniques for RAD
1. Use expert developers and tools for faster develpment and testing 2. Uses minimal planning, analysis and documentation 3. Users are involved in development and provide feedback through prototype 4. Uses interactive and incremental design approach with prototyping
58
List out 3 advantages of RAD
1. Developed more quicklu with cost savings 2. Cut development time and expense by involving users in every process 3. Allows the dev team to make modifications quickly, as the design evolves
59
List out 3 disadvantages of RAD
1. System might work well in the short term, but organization long-term objective might not met 2. Less time to develop quality, consistency and design standards 3. Does not emphasize the company's strategic business needs
60
Which methodology is closest to standard SDLC?
Waterfall
61
What methodology is used for large database projects?
Structured System Analysis and Design Methodology (SSADM)
62
What methodology is used for web based projects?
Web Information Systems Development Methodology (WIDSM)
63
What methodology is used for projects that have many sections need to be linked after?
Spiral
64
What methodology is used for small and fast projects?
Rapid Application Development (RAD)
65
What methodology is used for advance or heavy coding projects?
Extreme Programming (XP)
66
Which methodology uses most of the Agile Principles?
Extreme Programming (XP)
67
List out the 8 phases of XP
1. Planning 2. Testing 3. Pair Programming 4. Simple Designs 5. Refactoring the Code 6. Continuous Integration 7. On-Site Customer 8. Small Releases
68
List out the 4 phases in SCRUM Methodology
1. Sprint Planning 2. Daily Scrum 3. Sprint Review 4. Sprint Retrospective
69
List out 4 phases of Spiral Methods
1. Planning Phase 2. Risk Analysis 3. Engineering Phase 4. Evaluation Phase
70
Which methodology have a "Risk-Driven" process model
Spiral
71
What does Perfective do to the system?
Add new functionalities to the system
72
What does Preventive do to the system?
Add changes to prevent future errors
73
What does Corrective do to the system?
Repair of faults and errors found in day-to-day system functions
74
What methodology is suitable for long-term projects that frequently change?
Feature Driven Development
75
Which methodology focuses on identifying and eliminating waste, while continuously improving software quality
Lean Software Development
76
List out 3 agile manifesto that are related to Customer Satisfaction
1. Customer Satisfaction by early and **continuous delivery of valuable software** 2. **Welcome changing requirements** , even in late development 3. **Working software is delivered frequently** (weeks rather than months)
77
List out 2 agile manifesto that are related to Fast Development
1. **Close, daily cooperation** between business-people and developers 2. **Working software** is the principle measure of progress
78
List out 2 agile manifesto that are related to Teamwork
1. Projects are built around **motivated individuals** 2. **Face-to-Face conversation** is the best form of communication (co-location)
79
List out 5 agile manifesto that are related to High Product Quality
1. **Sustainable development**, able to maintain a **constant pace** 2. Continuous attention to **technical excellence and good design** 3. **Simplicity** , takes the simplest path consistent with goals and focuses on desired outcome 4. Best architectures, requirements and designs emerge from **self-organizing teams** 5. Regularly, the team **reflects** on how to become **more effective, and adjusts accordingly**
80
List out 5 general advantages of Agile Methodologies
1. Customer satisfaction with frequent delivery of the working product. 2. Gives customers/users ‘power’ to change their minds anytime and send new requirements. 3. Gives more ‘control’ to core developers to make decisions 4. Emphasize the use of the latest design and technologies 5. Encourage close communication and teamwork.
81
List out 5 general disadvantages of Agile Methodologies
1. Customers not available at all times. 2. Difficult for developers to determine final cost and development time as requirements keep changing. 3. Difficult for developers to plan and deliver workable products frequently. 4. Experts' developers and CASE Tools are expensive 5. Often lack comprehensive documentation.
82
What does Product Owner do? ## Footnote Scrum Role
1. Approving product decisions (set task priorities to deliver highest value) 2. Approve the final product of each sprint
83
Who does Product Owner represents?
Customer
84
What does the Scrum master do? ## Footnote Scrum Role
Protect scrum process and prevent distractions
85
What does the Development team do? ## Footnote Srcum Role
Takes and determine how to deliver work in frequent increments
86
What is the purpose of Sprint Review and Retrospective?
1. To close the project / sprint 2. Discuss lessons learned 3. Discuss future improvements 4. Review objectives achieved 5. Address changes to be made
87
What is Static Testing?
Test and find defects without executing code ## Footnote Review documents, static analysis, reviewing, walkthrough, inspection, etc.
88
What is Dynamic testing?
Software code is executed ## Footnote Unit Testing, Integration Testing, System Testing, Automated Testing tools are recommended
89
List out 5 key activities during analysis phase
1. Gather Detailed Information 2. Define Requirements 3. Prioritise Requirements 4. Develop User-Interface Dialogs 5. Evaluate Requirements with Users
90
What is White Box testing?
All INPUT, PROCESS and OUTPUT is seen
91
What is Black Box Testing?
Only INPUT and OUTPUT is seen, PROCESS are hidden
92
What does FURPS+ stands for ?
1. Functions 2. Usability 3. Reliability 4. Performance 5. Security 6. + (Design Constraints, Implementation, Interface, Physical, Support)
93
List out 3 advantages of using Data Analysis tools?
1. Fast and Accurate 2. Present data in various forms for better understanding 3. Help to create better product / service
94
List out 3 disadvantages of using Data Analysis tools?
1. Analysis techniques are many and confusing 2. Need specific format of data for input 3. Some tools are expensive
95
List out 7 benefits of System Analysis
1. Knowledge discovery 2. Problem's source / cause discovery 3. Obtain proof to support a theory 4. Verify assumptions with real facts 5. Filter and keep only important / relevent data 6. See the relationship between facts and figures 7. View data in a different way to obtain ideas
96
List out 8 setbacks of System Analysis
1. Insufficient data collected 2. Unreliable and Invalid data 3. Incorrect analysis methods used 4. Difficult to use analysis tools 5. Lack of scope / Objectives of output 6. Biased Inference - Leads to inaccurate facts 7. Analyst - Lack of analysis skills 8. External Issues
97
Why projects failed? | Related to risk
1. Developer did not identify all risks 2. Developer ignoring risks 3. Developer did not prepare a 'backup plan' for risk 4. Developer did not monitor risk
98
List out 5 steps in Risk Management
1. Develop risk management plan 2. Identify risks 3. Analyze risks 4. Create a backup plan 5. Monitor risk
99
Which methodology is used in complex software projects where requirements are expected to change or are not fully known at start?
Scrum
System Development Methods
flashcards
Decks in class (9)
# Cards
Brainscape helps you reach your goals faster, through stronger study habits.
© 2026 Bold Learning Solutions. Terms and Conditions