Feedback
Think carefully about what the question is asking: it refers to the full process — from design and development to implementation and ongoing maintenance of an Information System. This is not just a one-time cost or a licensing fee.
✅ Correct answer: Lifecycle spending.
Think again about how companies use Information Systems today. Most organizations no longer use IS just for simple tasks or record keeping. Instead, they depend on IT for strategic planning, decision-making, and competitive advantage. That’s why it’s critical for IS to be safe and reliable.
✅ Correct answer: Rely on IT for strategic tasks.
Remember, the role of a systems developer is technical and business-focused. They are involved in understanding business needs, designing secure systems, and supporting implementation and user adoption.
✅ Correct answer: Hosting corporate social events.
It’s important to know the main approaches to system development. The three primary system-building choices are:
Insourcing – using internal IT staff
Selfsourcing – when end-users develop their own systems
Outsourcing – hiring external vendors
✅ Correct answer: Co-sourcing.
Note: End-user development is often used interchangeably with selfsourcing.
Selfsourcing refers to situations where non-IT professionals, such as managers or analysts, create or modify their own systems using tools like spreadsheets, databases, or low-code platforms. It's often called end-user development. While it can speed up development and reduce IT workload, it also poses risks if not properly managed or supported by IT.
✅ Correct answer: End-users developing the system themselves.
The Waterfall model in the Systems Development Life Cycle (SDLC) is a linear, step-by-step approach where each phase (like planning, analysis, design, implementation, and maintenance) must be completed before the next begins. It is not iterative, and once a phase is completed, it's typically not revisited.
✅ Correct answer: Sequential and activity-based.
System Development Life Cycle (SDLC) activities include tasks directly related to planning, analyzing, designing, developing, testing, and maintaining an information system. Activities like:
Budgeting (in the planning phase),
Gathering requirements (in the analysis phase),
Designing models (in the design phase), and
Writing documentation (throughout the process),
are all standard SDLC activities.
However, marketing campaigns are business operations, not part of the SDLC. While an IS may support marketing efforts, the act of running campaigns is not a development activity.
✅ Correct answer: Running marketing campaigns.
A Critical Success Factor (CSF) is a vital element that must go right for an organization or project to succeed. It represents a strategic area where satisfactory results ensure competitive performance or the achievement of mission-critical objectives.
Options like project delays, system bugs, or interface changes are challenges or technical issues—not strategic drivers.
CSFs are used to guide priorities and evaluate performance, helping organizations stay focused on what matters most for success.
Make sure to connect CSFs to high-level goals, not technical or temporary events.
✅ Correct answer: A key goal essential to organizational success.
A project scope document provides a concise summary of what the project will deliver, including its boundaries, objectives, and key deliverables. It is not overly detailed—it focuses on the big picture to ensure everyone understands what is and isn’t included in the project.
It’s not a user manual or a database schema, which are more technical and detailed documents.
It’s also not a lengthy report; clarity and brevity are key in scope definitions to avoid confusion and scope creep.
Always remember: project scope = clear overview of goals and boundaries.
✅ Correct answer: A short paragraph summarizing high-level requirements
Scope creep occurs when new features, tasks, or requirements are added to a project without proper review or approval, often without adjusting the timeline, budget, or resources. It can lead to delays, cost overruns, and project failure.
It is not about writing documentation, hiring staff, or even prioritizing existing requirements.
Avoiding scope creep requires clear scope definition, proper change management, and continuous stakeholder communication.
Always guard against scope creep by sticking to the agreed plan unless formal changes are made.
✅ Correct answer: Adding unplanned features beyond initial scope
Project milestones are critical checkpoints in a project timeline that mark the completion of significant phases or tasks. They help:
Track progress
Ensure deadlines are met
Facilitate communication with stakeholders
They are not vague long-term goals, marketing deadlines, or security checkpoints. Confusing milestones with general goals can lead to poor time management and project delays.
Understanding milestones helps keep the project organized and on schedule.
✅ Correct answer: Dates by which key activities must be completed
Joint Application Development (JAD) sessions are collaborative workshops where users, stakeholders, and developers come together to:
Discuss system requirements
Clarify business needs
Reach agreements early in the development process
JAD sessions are not for training, budgeting, or technical tasks like installing servers. Their main purpose is to ensure that the system reflects what the users truly need, which reduces misunderstandings and improves system success.
✅ Correct answer: Gather and review requirements collectively
Prioritizing requirements involves identifying which system features are most critical and ensuring that stakeholders agree on their importance. User sign-off confirms that requirements have been reviewed and prioritized correctly, serving as official approval to proceed.
Tasks like creating design diagrams, writing test conditions, or implementing databases come later in the system development process and are not directly part of the prioritization phase.
✅ Correct answer: Signing off by users
Fixing errors early in the Systems Development Life Cycle (SDLC)—especially during the planning or requirements phases—is much cheaper because the system is still on paper. At this stage, corrections usually mean revising documentation or diagrams, not rewriting code or redesigning systems.
As the project progresses, errors become more costly to fix due to increased complexity, rework, and potential impact on users and functionality. That’s why early validation and accuracy are essential.
✅ Correct answer: Fixes only involve editing documentation
In the design phase of the SDLC, "technical architecture" refers to the underlying technology infrastructure required to support the system. This includes hardware (servers, devices), software (platforms, tools), and telecommunications equipment (networks, connections). It provides the foundation upon which the system will operate and ensures that performance, scalability, and security requirements can be met.
Other choices, such as marketing strategies or user training, belong to different phases like planning or implementation.
✅ Correct answer: Hardware, software, telecom equipment
In the design phase of the SDLC, modeling is the process of creating visual representations of how the system will function. This includes screen layouts (user interfaces), report formats, database schemas, and process flows. These models help developers and stakeholders understand and agree on the system’s structure before actual development begins.
If you chose a different option, remember: modeling is about planning and visualization, not coding, testing, or budgeting.
✅ Correct answer: Graphically representing screens, reports, databases
during the development phase, IT specialists primarily focus on building the system itself, which includes designing the architecture and writing the code. Tasks like training end-users or budget approvals happen in other phases. Keep reviewing the different phases of the software development life cycle, and you'll get it!
✅ Correct answer: Building architecture and writing code
Test conditions are all about detailed steps that guide the testing process, including what you expect to happen at each step. They are more specific than high-level goals and focus on verifying that the system works correctly. Keep practicing how different project documents fit into the development cycle.
✅ Correct answer: Detailed steps with expected results
The test type that checks whether independent modules work together is called integration testing. Unit testing focuses on individual components, while system testing looks at the complete system, and UAT involves the end-users. Keep reviewing the testing types.
✅ Correct answer: Integration testing
User Acceptance Testing (UAT) is all about making sure that real users can perform their required tasks with the system. It focuses on usability and practical functionality rather than just technical specs or hardware setup. Keep going—you’re building a strong understanding of testing phases!
✅ Correct answer: Users can perform required tasks
Parallel implementation means running the old and new systems at the same time to ensure a smooth transition and catch any issues before fully switching over. It’s different from immediately turning off the old system or testing with a small group. Keep up the great work—you’re learning important concepts!
✅ Correct answer: Using both old and new systems simultaneously
During the maintenance phase, a help-desk mainly responds to user questions and supports them in using the system effectively. While fixing bugs may be part of the broader maintenance process, the help-desk focuses more on direct user assistance. Keep reviewing the roles in each phase.
✅ Correct answer: Responds to user questions
The correct answer is that classic SDLC often mandates writing everything from scratch, which can prevent the reuse of existing code. This traditional approach tends to follow rigid steps and doesn’t always encourage reusing pre-built components or libraries. Don’t worry—understanding the limitations of SDLC is a great step toward mastering modern development practices!
✅ Correct answer: It mandates writing everything from scratch
The correct answer is that SDLC's one-time coding approach can lead to duplicate development of UI screens and components, especially if changes are needed later. Since the classic SDLC doesn't loop back easily, updates often require rewriting instead of modifying existing parts. Keep it up—understanding these limitations will help you compare different development models more effectively!
✅ Correct answer: Duplicate development of UI screens repeatedly
Component-Based Development (CBD) focuses on creating small, reusable pieces of code—called components—that can be combined to build larger systems. This approach improves efficiency and maintainability compared to building everything from scratch. Great job staying engaged.
✅ Correct answer: Creating reusable small code blocks
The main goal of Component-Based Development (CBD) is to develop reusable components that can be used across multiple applications. This saves time, reduces errors, and promotes consistency. Keep going—understanding this concept will help you see how modern software development improves efficiency!
✅ Correct answer: Develop reusable components for multiple apps.
Rapid Application Development (RAD) speeds up development mainly by creating quick prototypes and getting early user feedback. This helps catch issues and refine the system faster than traditional methods. You're on the right track—keep exploring how different methodologies work!
✅ Correct answer: Emphasizing rapid prototype creation with user feedback
After the planning and analysis stage in Rapid Application Development (RAD), the next step is to create and test prototypes. This allows developers and users to collaborate closely and make improvements early. You're doing great—just keep connecting each step with its purpose in the process!
✅ Correct answer: Creating and testing prototypes
One of the strengths of RAD is that it involves end-users actively and early, which helps gather requirements more quickly and accurately. Their direct input speeds up development and ensures the final product meets real needs. You're on the right path—keep learning how user involvement shapes different development methods!
✅ Correct answer: Accelerated requirements gathering
Reusing existing components in RAD helps to speed up prototyping, which is one of the key goals of this approach. Instead of building everything from scratch, developers can assemble working systems faster using proven, reusable parts. Great effort—keep going, you're strengthening your understanding of RAD!
✅ Correct answer: Speed up prototyping
The final stage in RAD is ongoing support and maintenance. Even though RAD emphasizes speed and prototyping, like any development approach, the system still needs updates, bug fixes, and user support after deployment. You're doing well—understanding the full cycle helps you see the big picture of software development!
Extreme Programming (XP) is known for breaking projects into small, manageable, and iterative phases. This allows for continuous feedback, frequent testing, and quick adjustments. Unlike traditional models, XP is flexible and centered around collaboration and improvement. Keep going—you’re grasping key ideas from modern development methodologies!
In Extreme Programming (XP), developers cannot move forward until the current iteration is complete. This ensures that each piece of functionality is fully tested and working before the next one begins. It's all about building quality step by step. Keep up the great work—you're making solid progress in understanding agile methods!
Both Extreme Programming (XP) and Component-Based Development (CBD) share the idea of reusing components from a library to save time and improve code quality. This promotes efficiency and consistency across projects. You're doing great—identifying shared principles helps you connect different development approaches more easily!
One of the key reasons Extreme Programming (XP) is successful is its strong emphasis on customer satisfaction. By involving the customer closely and delivering small, functional pieces of the system frequently, XP ensures that the final product truly meets user needs. Keep it up—understanding the customer’s role is crucial in agile development!
The main difference is that Agile methods tend to limit project scope more strictly than XP, often working in shorter cycles with clearly defined deliverables. While XP is a type of Agile, it tends to focus more on engineering practices like pair programming and test-driven development. You're making solid progress—understanding these nuances helps you choose the right method for different projects!
Agile projects focus on turning a minimum set of requirements into working deliverables quickly and then iterating based on feedback. This helps teams adapt to changes and deliver value faster. Keep going—you’re getting a great grasp of Agile principles!
According to the Agile Manifesto, long detailed requirement documents are actually discouraged. Agile values working software and collaboration over extensive paperwork, encouraging flexibility and quick adaptation. You're on the right track—keep learning how Agile focuses on simplicity and responsiveness!
Agile projects are known for being fast, flexible, and focused on delivering fewer—but more valuable—features quickly. This nimbleness helps teams respond to change and deliver what users really need. Keep up the great work—you’re sharpening your understanding of Agile principles!
A key strength of Extreme Programming (XP) is that it empowers developers to handle changes even late in the software development lifecycle. This flexibility helps the team respond to evolving customer needs without derailing the entire project. Great job—understanding this adaptability is essential to grasping XP’s value!
Tissues - Practice Quiz
Test your knowledge about the 5 seeing habits discussed in the text 'UPS 5 seeing habits'.