Module 10: Building Successful Information Systems
Key Terms
1. Agile methodology - A framework that focuses on an incremental development process and
timely delivery of working software, emphasizing collaboration between programmers and
business experts.
2. Computer-aided systems engineering (CASE) - Tools that automate parts of the application
development process, particularly helpful in large-scale projects.
3. Crowdsourcing - The process of outsourcing tasks traditionally performed by employees or
contractors to a large group of people through an open call.
4. Design phase - Phase where analysts choose the most realistic solution offering the highest
payoff for the organization, outlining details with exact specifications for implementation.
5. Economic feasibility - Assessment of a system's costs and benefits.
6. External users - Non-employees who use the system, including customers, contractors,
suppliers, and other business partners.
7. Extreme programming (XP) - A method for developing software applications where the project is
divided into smaller functions, and developers cannot proceed until the current phase is finished.
8. Feasibility study - Analysis of a proposed solution’s feasibility and how it can be presented to
management.
9. Implementation phase - Phase where the solution is transferred from paper to action,
configuring the system and procuring components.
10. Insourcing - When an organization’s team develops the system internally.
11. Internal users - Employees who use the system regularly, providing feedback on its strengths and
weaknesses.
12. IT project management - Activities required to plan, manage, and control the creation and
delivery of an information system.
13. Joint application design (JAD) - A collective activity involving users, top management, and IT
professionals in structured workshops.
14. Legal feasibility - Assessment of legal issues, including political repercussions and meeting legal
requirements.
15. Low-code - Development platforms requiring minimal coding knowledge.
16. Maintenance phase - Phase where the system operates, enhancements are developed, and
modifications are tested.
17. No-code - Platforms that do not require any previous knowledge of coding; users can drag and
drop application components.
18. Operational feasibility - Measure of how well the proposed solution will work within the
organization.
19. Outsourcing - Hiring an external vendor or consultant specializing in providing development
services.
20. Pair programming - Two programmers participate in one development effort at one workstation.
21. Parallel conversion - Old and new systems run simultaneously for a short time to ensure the new
system works correctly.
22. Phased-in–phased-out conversion - As each module of the new system is converted, the
corresponding part of the old system is retired.
23. Pilot conversion - System introduced in a limited area of the organization.
24. Planning phase - Crucial phase where the problem is defined, and a feasibility study is
conducted.
25. Plunge (direct-cutover) conversion - Old system is stopped, and the new system is
implemented.
26. Proof-of-concept prototype - Shows users that a particular task can be done.
27. Prototyping - Developing a small-scale version of the system to illustrate benefits and allow user
feedback.
28. Rapid application development (RAD) - Focuses on user involvement and interaction between
users and designers, using iterative processes.
29. Request for information (RFI) - Screening document for gathering vendor information.
30. Request for proposal (RFP) - Written document with detailed specifications used to request
bids.
31. Requirements-gathering and analysis phase - Phase where analysts define the problem and
generate alternatives for solving it.
32. Scheduling feasibility - Assesses whether the new system can be completed on time.
33. Self-sourcing - End users develop their own information systems with little formal assistance.
34. Service-oriented architecture (SOA) - Focuses on the development, use, and reuse of small,
self-contained blocks of code.
35. Systems development life cycle (SDLC) - Series of well-defined phases performed in sequence
serving as a framework for developing a system or project.
36. Technical feasibility - Assessment of the technology to be used in the system.
Concepts
1. Systems Development Life Cycle (SDLC):
• Also known as the "waterfall model," it consists of five phases: planning, requirements-
gathering and analysis, design, implementation, and maintenance.
• Each phase's output becomes the input for the next phase.
2. Planning Phase:
• Define the problem, ensuring not to confuse symptoms with the underlying issue.
• Conduct a feasibility study assessing economic, technical, operational, scheduling, and
legal aspects.
• Form a task force comprising representatives from different departments, including IT, to
gather user feedback.
3. Requirements-Gathering and Analysis Phase:
• Identify what users do, how they do it, problems faced, and expected outcomes from the
new system.
• Use techniques like interviews, surveys, observations, and JAD sessions.
• Create system specifications detailing the project scope.
4. Design Phase:
• Choose the most realistic solution offering the highest payoff.
• Output includes detailed specifications for files, databases, forms, reports,
documentation, procedures, hardware, software, networking components, and general
system specifications.
• Utilize CASE tools to automate parts of the design process.
5. Implementation Phase:
• Transfer the solution from paper to action, configuring the system and procuring
necessary components.
• Tasks include acquiring new equipment, hiring/training employees, designing physical
layouts, coding, testing, security measures, and creating disaster recovery plans.
• Conversion methods include parallel, phased-in–phased-out, pilot, and plunge
conversions.
6. Maintenance Phase:
• Operate the system, develop/test enhancements, add/replace hardware/software
components.
• Assess system performance, collect data, and ensure it meets objectives.
• Establish a help desk to support users.
7. New Trends in Systems Analysis and Design:
• Service-Oriented Architecture (SOA): Focuses on reusing small, self-contained code
blocks.
• Rapid Application Development (RAD): Combines planning and analysis phases, uses
prototypes, and emphasizes iterative processes.
• Extreme Programming (XP): Divides projects into smaller functions, emphasizing
simplicity, responsiveness, teamwork, and communication.
• Agile Methodology: Emphasizes incremental development, collaboration, and adapting to
changing needs.
• Low-Code and No-Code Development: Platforms allowing users to create applications
with minimal or no coding knowledge.
Summaries
1. Overview of SDLC:
• The SDLC provides a structured approach to developing information systems, ensuring
integration of people, software, and hardware.
• Each phase builds upon the previous one, culminating in a fully functional and maintained
system.
2. Planning Phase:
• Critical for defining the problem and conducting feasibility studies.
• Involves forming a task force to gather user feedback and assess various dimensions of
feasibility.
3. Requirements-Gathering and Analysis Phase:
• Focuses on understanding user needs, analysing current systems, and generating
solutions.
• Techniques like interviews, surveys, and JAD sessions aid in collecting comprehensive
data.
4. Design Phase:
• Selects the optimal solution and outlines detailed specifications.
• Utilizes tools like CASE to enhance efficiency and accuracy.
5. Implementation Phase:
• Transfers the solution into action, ensuring all components are configured and tested.
• Various conversion methods ensure smooth transitions.
6. Maintenance Phase:
• Ensures the system continues to meet organizational needs through ongoing assessments
and updates.
• Includes establishing support structures like help desks.
7. Emerging Trends:
• New methodologies like SOA, RAD, XP, Agile, and low/no-code aim to enhance flexibility,
speed, and cost-effectiveness in system development.
• These approaches cater to dynamic environments where traditional methods may fall
short.
Mind Map: Building Successful Information Systems
Central Node:
Building Successful Information Systems
Branch 1: Systems Development Life Cycle (SDLC)
• Sub-Branch 1.1: Planning Phase
• Define the problem
• Conduct feasibility studies (economic, technical, operational, scheduling, legal)
• Form task force
• Identify potential systems
• Sub-Branch 1.2: Requirements-Gathering and Analysis Phase
• Gather requirements (interviews, surveys, observations, JAD sessions)
• Analyse current system issues
• Generate alternatives for solving problems
• Sub-Branch 1.3: Design Phase
• Choose the most realistic solution
• Outline detailed specifications
• Use tools like CASE for automation
• Sub-Branch 1.4: Implementation Phase
• Transfer solution into action
• Acquire new equipment, hire/train employees
• Develop security measures, disaster recovery plans
• Conversion methods (parallel, phased-in–phased-out, plunge, pilot)
• Sub-Branch 1.5: Maintenance Phase
• Operate the system
• Develop/test enhancements
• Ensure system meets objectives
Branch 2: Feasibility Studies
• Sub-Branch 2.1: Economic Feasibility
• Assess costs vs. benefits
• Tangible vs. intangible benefits
• Sub-Branch 2.2: Technical Feasibility
• Evaluate available technology
• Assess organizational readiness
• Sub-Branch 2.3: Operational Feasibility
• Measure how well the solution fits the organization
• Consider user acceptance
• Sub-Branch 2.4: Scheduling Feasibility
• Ensure timely completion
• Sub-Branch 2.5: Legal Feasibility
• Address legal and regulatory concerns
Branch 3: New Trends in Systems Analysis and Design
• Sub-Branch 3.1: Service-Oriented Architecture (SOA)
• Focus on reusable code blocks
• Enable integration with third-party services
• Sub-Branch 3.2: Rapid Application Development (RAD)
• Emphasize user involvement
• Iterative development process
• Sub-Branch 3.3: Extreme Programming (XP)
• Incremental development
• Pair programming and continuous feedback
• Sub-Branch 3.4: Agile Methodology
• Collaborative, modular approach
• Timely delivery of working software
• Sub-Branch 3.5: Low-Code/No-Code Development
• Minimize or eliminate coding requirements
• Drag-and-drop interfaces for application creation
Branch 4: Implementation Alternatives
• Sub-Branch 4.1: Insourcing
• Internal team develops the system
• Sub-Branch 4.2: Self-Sourcing
• End users develop their own systems
• Sub-Branch 4.3: Outsourcing
• Hire external vendors
• Types: Onshore, Nearshore, Offshore, Crowdsourcing
Branch 5: Tools and Techniques
• Sub-Branch 5.1: Computer-Aided Systems Engineering (CASE) Tools
• Automate parts of the application development process
• Sub-Branch 5.2: Prototyping
• Develop small-scale versions of the system
• Types: Gathering requirements, determining feasibility, selling prototypes
• Sub-Branch 5.3: Project Management Tools
• PERT, CPM, Gantt Charts
• Software: Wrike, Smartsheet, Clarizen
A framework for developing systems or projects,
What is the Systems Development Life Cycle
consisting of five phases: Planning,
(SDLC)?
Requirements-Gathering and Analysis, Design,
Implementation, and Maintenance.
What is the goal of an information system? To deliver useful information in a timely manner to
the right decision maker.
What are the four W’s in the planning phase? Why, Who, When, What. These helps define the
problem and solution scope.
An assessment of whether a proposed system is
What is a feasibility study? beneficial or practical, focusing on economic,
technical, operational, scheduling, and legal
dimensions.
What is economic feasibility? Evaluating the costs and benefits of implementing
a system to ensure it results in a net gain.
What is technical feasibility? Assessing whether the technology needed for the
system is available or feasible to implement.
Determining if the proposed system will work well
What is operational feasibility?
within the organization and how users will react to
it.
What is scheduling feasibility?
Ensuring the system can be completed on time.
What is legal feasibility? Evaluating any legal issues or conflicts with
regulations that the system might create.
A collaborative approach involving users, top
What is joint application design (JAD)?
management, and IT professionals in structured
workshops to develop applications.
What tools are used in the requirements- Interviews, surveys, observations, JAD sessions,
gathering phase? data flow diagrams (DFDs), and entity relationship
models (ERMs).
What is conceptual design? An overview of the system without specifying
hardware or software choices.
What is logical design? A more detailed version of conceptual design,
specifying particular hardware and software.
Creating specific designs for a chosen platform,
What is physical design?
including hardware, software, and networking
components.
What is prototyping? Developing a small-scale version of the system to
illustrate benefits and allow user feedback.
Define initial requirements, develop the
What are the four steps of prototyping?
prototype, review and evaluate it, revise the
prototype.
Running old and new systems simultaneously for
What is parallel conversion?
a short time to ensure the new system works
correctly.
What is plunge (direct-cutover) conversion? Stopping the old system and immediately
implementing the new one.
A methodology focusing on developing, using,
What is service-oriented architecture (SOA)?
and reusing small, self-contained blocks of code
called services.
A flexible approach emphasizing incremental
What is agile methodology?
development, collaboration, and timely delivery
of working software.
Multiple-Choice Questions (20)
1. What is the main goal of an information system?
a) To automate all business processes
b) To deliver useful information in a timely manner to the right decision maker
c) To reduce costs by eliminating employees
d) To replace outdated hardware
2. Which phase of the SDLC involves gathering user feedback and defining the problem?
a) Planning
b) Requirements-Gathering and Analysis
c) Design
d) Implementation
3. What does a feasibility study assess?
a) The cost-effectiveness of a project
b) Whether the project aligns with organizational goals
c) Both A and B
d) None of the above
4. In which conversion method do the old and new systems run simultaneously for a short time?
a) Parallel conversion
b) Phased-in–phased-out conversion
c) Plunge (direct-cutover) conversion
d) Pilot conversion
5. What is prototyping?
a) A small-scale version of the system to illustrate benefits
b) A detailed documentation of the system's specifications
c) A feasibility study conducted during the planning phase
d) A process to test hardware components
6. Which methodology emphasizes simplicity, teamwork, and immediate feedback from users?
a) Agile methodology
b) Extreme Programming (XP)
c) Rapid Application Development (RAD)
d) Service-Oriented Architecture (SOA)
7. What is the primary purpose of a Request for Proposal (RFP)?
a) To gather vendor information
b) To request bids for equipment, supplies, or services
c) To document internal system requirements
d) To evaluate user satisfaction
8. Which trend allows non-developers to create applications using drag-and-drop interfaces?
a) Low-code/no-code development
b) Crowdsourcing
c) Outsourcing
d) Self-sourcing
9. What is the role of CASE tools in the SDLC?
a) To automate parts of the design and analysis phases
b) To provide legal advice during feasibility studies
c) To implement hardware components
d) To conduct user interviews
10. Which phase focuses on enhancing and modifying the system after it is operational?
a) Planning
b) Design
c) Maintenance
d) Implementation
11. What is the "critical path" in project management?
a) The longest sequence of activities that must be completed on time
b) The shortest sequence of activities
c) A list of all possible tasks
d) A timeline for hiring new employees
12. Which conversion method introduces the system in a limited area before full implementation?
a) Parallel conversion
b) Pilot conversion
c) Phased-in–phased-out conversion
d) Plunge (direct-cutover) conversion
13. What is the advantage of using SOA (Service-Oriented Architecture)?
a) Reduced application development time
b) Increased complexity
c) Higher costs
d) Decreased flexibility
14. Which dimension of feasibility assesses whether the system will comply with legal requirements?
a) Economic feasibility
b) Technical feasibility
c) Legal feasibility
d) Operational feasibility
15. What is the main disadvantage of self-sourcing?
a) Faster development
b) Lack of access to crucial data
c) Improved communication
d) Enhanced security
16. What is the first step in the requirements-gathering phase?
a) Prototyping
b) Interviewing users
c) Creating a Gantt chart
d) Writing an RFP
17. Which tool is used to visualize complex systems with inputs, processes, and outputs?
a) Data Flow Diagram (DFD)
b) Gantt chart
c) Feasibility report
d) Cost-benefit analysis
18. What is the purpose of a JAD session?
a) To train employees on new systems
b) To develop an application collaboratively
c) To conduct feasibility studies
d) To create prototypes
19. Which framework focuses on delivering software in short sprints?
a) Scrum
b) Waterfall
c) RAD
d) SOA
20. What is the primary focus of economic feasibility?
a) Assessing user satisfaction
b) Evaluating costs and benefits
c) Ensuring technical compatibility
d) Meeting legal requirements
True or False Questions (20)
1. The SDLC model is also known as the "waterfall model."
2. The planning phase is the least important phase in the SDLC.
3. A feasibility study is conducted only during the planning phase.
4. Prototyping is a technique used to test the technical feasibility of a system.
5. In parallel conversion, the old system is stopped immediately after the new system is implemented.
6. Outsourcing refers to developing a system internally without external help.
7. Agile methodology emphasizes incremental development and timely delivery.
8. Crowdsourcing involves outsourcing tasks to a large group of people through an open call.
9. CASE tools are primarily used for training employees.
10. The maintenance phase begins after the system is fully operational.
11. Self-sourcing reduces the need for IT professionals.
12. RAD combines the planning and analysis phases into one phase.
13. Pair programming involves two programmers working together at one workstation.
14. No-code platforms require users to have extensive coding knowledge.
15. Legal feasibility ensures the system complies with organizational policies.
16. The implementation phase includes acquiring new equipment and training employees.
17. SOA focuses on reusing small blocks of code called services.
18. Insourcing means hiring an external vendor to develop the system.
19. PERT and CPM techniques are used to identify bottlenecks in project schedules.
20. The output of the design phase is a system specifications document.
Fill in the Missing Word Questions (20)
1. The SDLC consists of five phases: planning, ____________, design, implementation, and maintenance.
2. A ____________ is a written document used to request bids for equipment or services.
3. During the ____________ phase, analysts define the problem and generate alternatives for solving it.
4. ____________ feasibility assesses whether the system will work within the organization's operations.
5. In ____________ conversion, the old system is stopped, and the new system is implemented
immediately.
6. ____________ is a philosophy that focuses on reusing small blocks of code called services.
7. ____________ involves developing a small-scale version of the system to demonstrate its benefits.
8. A ____________ prototype is used to sell the proposed system to users and management.
9. ____________ involves outsourcing tasks to a large group of people through an open call.
10. ____________ tools automate parts of the application development process.
11. The ____________ phase focuses on configuring the system and procuring components.
12. ____________ feasibility assesses whether the system can be completed on time.
13. ____________ is a method that divides projects into smaller functions and develops them step-by-
step.
14. ____________ involves creating private data stores to ensure data integrity.
15. ____________ is the process of controlling the flow of data to prevent inconsistencies.
16. The ____________ phase ensures the system continues to meet its objectives after deployment.
17. ____________ is a collaborative approach involving users, top management, and IT professionals.
18. ____________ focuses on reducing costs and increasing productivity through minimal coding.
19. A ____________ chart lists completion times on the x-axis and activities on the y-axis.
20. ____________ is a major disadvantage of low-code/no-code platforms due to lack of control.
Answers
Multiple-Choice Questions
1. b
2. b
3. c
4. a
5. a
6. b
7. b
8. a
9. a
10. c
11. a
12. b
13. a
14. c
15. b
16. b
17. a
18. b
19. a
20. b
True or False Questions
1. True
2. False
3. False
4. True
5. False
6. False
7. True
8. True
9. False
10. True
11. True
12. True
13. True
14. False
15. False
16. True
17. True
18. False
19. True
20. True
Fill in the Missing Word Questions
1. Requirements-Gathering and Analysis
2. RFP
3. Requirements-Gathering and Analysis
4. Operational
5. Plunge (direct-cutover)
6. Service-Oriented Architecture (SOA)
7. Prototyping
8. Selling
9. Crowdsourcing
10. CASE
11. Implementation
12. Scheduling
13. Extreme Programming (XP)
14. Data Administration
15. Data Control
16. Maintenance
17. Joint Application Design (JAD)
18. Low-Code/No-Code Development
19. Gantt
20. Security Issues
