Introduction to Systems, Information Systems, System Components, and the Role of a System Analyst
This tutorial introduces the basic concepts of systems, information systems, system components, and system analysis. Practical examples and a Student Attendance Management System case study are included to connect theory with real-world applications.
Learning Outcomes
After completing this tutorial, students should be able to:
- Define a system and explain its major characteristics.
- Identify the major components of a system.
- Explain input, processing, output, feedback, and control.
- Define an information system and describe its components.
- Differentiate data from information.
- Explain the responsibilities of a system analyst.
- Apply system analysis concepts to a practical case study.
1. What Is a System?
A system is a collection of related components that work together to achieve a common goal. These components may include people, procedures, data, hardware, software, and other resources.
A system receives inputs, performs activities, and produces outputs. Its components interact with one another to achieve the intended objective.
Examples of Systems
| System | Input | Processing | Output |
|---|---|---|---|
| Library System | Book and member details | Book issue and return processing | Issue records and due dates |
| Banking System | Account and transaction details | Transaction validation and balance updates | Transaction confirmation |
| University Examination System | Student registration and marks | Eligibility checks and grade calculation | Results and grade sheets |
| Traffic Control System | Vehicle flow and sensor data | Traffic monitoring and signal control | Traffic signal changes |
Characteristics of a System
- Organization: Components have a defined structure or arrangement.
- Interaction: Components communicate or work with one another.
- Interdependence: One component may depend on another component.
- Integration: Components operate together as a unified whole.
- Objective: A system exists to achieve one or more goals.
- Boundary: The boundary defines what is included within the system.
- Environment: External conditions and organizations may affect the system.
2. Major Components of a System
A common way to understand a system is through its input, processing, and output. Feedback and control help the system evaluate its performance and operate according to defined rules.
Feedback: Information about results or performance.
Control: Rules and actions used to guide or correct system operations.
Figure 1: A simplified input–process–output model.
1. Input
Data, resources, or requests entering the system.
Example: A student's ID and course code.
2. Processing
Activities that transform inputs into useful results.
Example: Checking whether a student is registered for a course.
3. Output
The information, service, or product generated by the system.
Example: An attendance record or report.
4. Feedback
Information used to evaluate performance and identify problems.
Example: A report showing low attendance.
5. Control
Rules and checks that help ensure the system operates correctly.
Example: Only authorized teachers can submit attendance.
6. Boundary and Environment
The boundary defines the system's scope; the environment includes external influences.
Example: University policies and network availability.
Open and Closed Systems
An open system exchanges information, resources, or energy with its environment. A university, for example, interacts with students, employers, families, and regulatory bodies.
A closed system is modeled as having little or no exchange with its environment. Completely closed systems are uncommon in real organizations, so this term is often used as a simplified analytical model.
3. What Is an Information System?
An Information System (IS) is an organized combination of people, procedures, data, and technology used to collect, process, store, and distribute information. Information systems support daily operations, coordination, control, and decision-making.
An information system is not just a computer program. People and procedures are essential because they determine how data is collected, checked, interpreted, protected, and used.
Components of an Information System
| Component | Description | University Example |
|---|---|---|
| People | Users and professionals who interact with the system | Students, teachers, administrators, IT staff |
| Hardware | Physical devices used for input, processing, storage, and output | Computers, servers, scanners |
| Software | Programs that perform tasks and manage information | Attendance application and database software |
| Data | Recorded facts processed into useful information | Student ID, course code, attendance status |
| Procedures | Rules and instructions describing how tasks are performed | Steps for taking attendance and correcting errors |
| Networks and Communication | Connections that allow data to move between users and systems | Campus LAN, Wi-Fi, internet |
Data Versus Information
Data consists of recorded facts. Information is data organized or processed so that it becomes meaningful for a particular purpose.
| Raw Data | Information | Possible Decision |
|---|---|---|
| Present, Present, Absent, Present, Absent | Attended 3 of 5 classes; attendance is 60% | Review the attendance policy and follow up if necessary |
| Individual sales transactions | Monthly sales summary | Restock products with high demand |
| Individual examination marks | Course result sheet and grade distribution | Identify learning gaps and support students |
Types of Information Systems
| Type | Purpose | Example |
|---|---|---|
| Transaction Processing System (TPS) | Records routine daily transactions | Course registration or fee payment |
| Management Information System (MIS) | Produces regular summaries and reports | Monthly attendance report |
| Decision Support System (DSS) | Supports analysis of alternatives and decisions | Comparing alternative class schedules |
| Executive Information/Support System (EIS/ESS) | Provides high-level information for strategic oversight | University performance dashboard |
| Office Automation System | Supports communication and office activities | Email and shared calendars |
| Knowledge Management System | Captures and shares organizational knowledge | Teaching-resource portal |
These categories can overlap. A modern university platform may provide several information-system functions within one integrated service.
4. System Analysis and System Design
System analysis is the process of studying a problem, understanding the current system, identifying user needs, and specifying what a proposed system should do.
System design translates the requirements into a plan for how the proposed solution will be structured and implemented.
| System Analysis | System Design |
|---|---|
| What problem needs to be solved? | How will the solution work? |
| Who are the users and stakeholders? | What interfaces and screens are needed? |
| What information is required? | How will data be stored and related? |
| What rules and constraints apply? | What architecture and technologies should be used? |
| What must the system accomplish? | How will the components be organized? |
5. The Role of a System Analyst
A system analyst studies an organization's needs and helps define an appropriate information-system solution. The analyst connects organizational stakeholders with the technical team.
The role is not limited to programming. It includes asking questions, studying workflows, identifying problems, documenting requirements, evaluating alternatives, and supporting implementation.
Main Responsibilities of a System Analyst
- Understand the problem: Identify current difficulties, goals, constraints, and reasons for change.
- Identify stakeholders: Determine who uses, manages, supports, or is affected by the system.
- Gather requirements: Use interviews, surveys, observation, workshops, and document analysis.
- Analyze current processes: Identify bottlenecks, repeated work, risks, and data-flow problems.
- Define requirements: Document the functions and quality standards the system must satisfy.
- Evaluate feasibility: Consider technical, economic, operational, schedule, and legal constraints.
- Model the solution: Use appropriate diagrams and models to represent processes, data, and system behavior.
- Communicate with stakeholders: Confirm that requirements are accurate and understandable.
- Support testing and implementation: Help ensure that the delivered solution meets agreed requirements.
- Support improvement: Review feedback and identify opportunities for future enhancements.
Functional and Non-Functional Requirements
| Type | Meaning | Attendance System Example |
|---|---|---|
| Functional | A service or behavior the system must provide | A teacher can record attendance for a class. |
| Functional | A required operation or rule | The system calculates attendance percentages. |
| Non-functional: Security | A quality or constraint related to protection | Only authorized users can change attendance records. |
| Non-functional: Performance | Expected responsiveness or capacity | An attendance list loads within an agreed time. |
| Non-functional: Usability | Ease of use and accessibility | The interface works on common mobile and desktop browsers. |
| Non-functional: Reliability | Consistent and dependable operation | Saved records remain available after a system restart. |
Important Skills for a System Analyst
- Communication: Explain technical and non-technical ideas clearly.
- Analytical thinking: Break complex problems into manageable parts.
- Requirements elicitation: Ask relevant questions and confirm users' actual needs.
- Modeling and documentation: Represent processes, data, and rules accurately.
- Technical knowledge: Understand databases, software, networks, and security.
- Problem-solving: Compare alternatives and help resolve conflicting requirements.
- Ethics and privacy awareness: Protect sensitive information and consider access controls.
System Analyst Versus Programmer
| System Analyst | Programmer / Developer |
|---|---|
| Focuses on understanding needs and defining requirements. | Focuses on implementing software functionality. |
| Works closely with users, managers, and technical teams. | Works closely with analysts, designers, testers, and developers. |
| Produces requirement documents, models, and recommendations. | Produces source code, tests, and software components. |
| May contribute to design, testing, and implementation. | May help clarify requirements and design decisions. |
In practice, these responsibilities may overlap, especially in small development teams.
6. Case Study: Student Attendance Management System
Imagine that a university department records attendance on paper. Teachers submit attendance sheets to the office, staff calculate percentages manually, and students may find it difficult to check their records.
The department wants a digital system that makes attendance recording, review, and reporting more efficient.
Problem Statement
The existing process may take considerable time and create risks of missing, inconsistent, or incorrectly calculated records. A digital solution should help authorized users record, review, and report attendance accurately.
Stakeholders
- Students: Need to review their attendance records.
- Teachers: Need to record attendance and make authorized corrections.
- Department administrators: Need course-wise, section-wise, and student-wise reports.
- IT administrators: Need to manage user accounts, backups, and availability.
- Department management: Needs reliable summaries to support academic decisions.
Example Functional Requirements
- The system shall allow authorized users to sign in.
- The system shall allow a teacher to select a course, section, and class date.
- The system shall display registered students for the selected class.
- The system shall allow the teacher to record each student's attendance status.
- The system shall prevent duplicate attendance entries for the same student and class session unless an authorized correction process is used.
- The system shall calculate attendance totals and percentages.
- The system shall generate student-wise, course-wise, and section-wise reports.
- The system shall record important changes when an audit trail is required.
Example Non-Functional Requirements
- Access shall be restricted according to user roles.
- Attendance records shall be protected against unauthorized modification.
- The interface should work on common mobile and desktop browsers.
- Data should be backed up according to an agreed schedule.
- Reports should be generated within an agreed response time under normal usage.
Input–Process–Output Model
Course, date, status
Validate and save
Records and reports
Figure 2: High-level model of the attendance system.
Questions a System Analyst Should Ask
- Who is authorized to record attendance for each course?
- Can attendance be edited after submission? Who approves changes?
- How should late arrivals, excused absences, or makeup classes be represented?
- Should students see attendance immediately or after teacher confirmation?
- What reports are required, and who can access them?
- What happens if the network fails during a class?
- How long must records be retained, and how will they be backed up?
7. Overview of the System Development Life Cycle (SDLC)
The System Development Life Cycle describes common activities involved in developing and maintaining an information system. The stages may be performed sequentially or iteratively, depending on the development approach.
Figure 3: Simplified SDLC. Real projects may revisit earlier stages based on feedback.
| Stage | Main Activity | Typical Deliverable |
|---|---|---|
| Planning and Feasibility | Define the problem, scope, resources, risks, and feasibility | Project plan or feasibility report |
| Analysis | Gather and validate requirements | Requirements specification |
| Design | Plan architecture, interfaces, data, and controls | Database and interface designs |
| Implementation | Build or configure the solution | Working application |
| Testing | Check whether the system meets requirements | Test cases and test results |
| Deployment and Maintenance | Release, support users, fix issues, and improve the system | Released system and updates |
8. Common Mistakes to Avoid
- Assuming that a system is only a computer or software application.
- Confusing raw data with meaningful information.
- Ignoring people, procedures, security, or the organizational environment.
- Designing a solution before understanding the problem.
- Writing vague requirements that cannot be tested.
- Failing to validate requirements with stakeholders.
- Ignoring exceptional situations such as duplicate records or network failure.
9. Quick Revision
- A system is a set of related components working toward a goal.
- Input enters the system, processing transforms input, and output is the result.
- Feedback provides performance information; control helps guide system operations.
- An information system combines people, hardware, software, data, procedures, and communication networks.
- Data are recorded facts; information is data organized or processed to be meaningful.
- System analysis identifies problems and requirements; system design plans the solution.
- A system analyst connects stakeholders and technical teams and helps define system requirements.
- Good requirements should be clear, relevant, testable, and validated with stakeholders.
10. Review Questions
Short Questions
- What is a system?
- List five characteristics of a system.
- What is the difference between input and output?
- Define feedback and control.
- What is an information system?
- Differentiate data and information with an example.
- What is system analysis?
- What is system design?
- Who is a system analyst?
- What is the difference between functional and non-functional requirements?
Analytical and Discussion Questions
- Explain the components of a system using a university as an example.
- Describe the components of an information system and explain how they depend on one another.
- Explain at least six responsibilities of a system analyst.
- For a Student Attendance Management System, identify five stakeholders and write five functional requirements and three non-functional requirements.
- Why should a system analyst investigate existing procedures before recommending new software?
- Explain the major stages of the SDLC with examples.
11. Suggested References
- Kenneth E. Kendall and Julie E. Kendall, Systems Analysis and Design.
- Alan Dennis, Barbara Haley Wixom, and Roberta M. Roth, Systems Analysis and Design.
- Jeffrey A. Hoffer, Joey F. George, and Joseph S. Valacich, Modern Systems Analysis and Design.