Identifying a Real-World System: Components, Users, and Boundaries
After studying this tutorial, students should be able to:
- Identify a real-world system and explain its purpose.
- Identify the components and resources of a system.
- Distinguish between system users and other stakeholders.
- Define a system's boundaries and external environment.
- Identify system inputs, processes, outputs, and feedback.
- Apply these concepts to a software project proposal.
1. What Is a System?
A system is a collection of interconnected components that work together to achieve a common objective. A system receives inputs, processes information or materials, produces outputs, and may use feedback to improve its operation.
A system can be physical, organizational, biological, or computerized.
Examples include:
- A university examination system.
- A hospital patient management system.
- A banking transaction system.
- An online shopping system.
- A student attendance management system.
Example: A University Attendance System
A university needs to record whether students attend scheduled classes. Teachers collect attendance information, the university maintains student and course records, and authorized users review attendance reports.
A Student Attendance Management System organizes these activities in one software application.
2. Identify the Real-World System
The first task in system analysis is to select a real-world activity or problem that needs to be understood or improved.
Sample Project: Student Attendance Management System (SAMS)
System type: Web-based information system.
Primary purpose: To record, store, retrieve, and report student attendance for university courses and class sessions.
Problem being addressed: Manual attendance procedures can require considerable time for record keeping, percentage calculations, and report preparation. Paper records can also be difficult to retrieve or verify.
Proposed solution: Develop a centralized application that allows authorized teachers to record attendance and generate attendance reports.
2.1 Define the System's Objectives
The proposed system should:
- Maintain student, teacher, course, and section information.
- Allow authorized teachers to record attendance for class sessions.
- Store attendance records in a database.
- Calculate attendance summaries and percentages.
- Allow authorized users to retrieve reports.
- Protect attendance information from unauthorized access.
3. Identify the System Components
System components are the parts that work together to achieve the system's objectives. For a computerized information system, these commonly include hardware, software, data, procedures, people, and communication networks.
| Component | Meaning | Example in SAMS |
|---|---|---|
| Hardware | Physical equipment used to operate the system. | Teacher's computer, server, and network equipment. |
| Software | Programs that implement system functions. | JSP pages, Java application logic, and database software. |
| Data | Information collected, stored, and processed. | Student IDs, course IDs, class dates, and attendance statuses. |
| People | Individuals who operate, manage, or use the system. | Teachers, authorized administrators, and students who view permitted information. |
| Procedures | Rules that define how activities are performed. | Attendance entry, correction approval, and report-generation procedures. |
| Network | Communication infrastructure connecting system users and services. | Campus LAN or internet connection used to access the application. |
3.1 Functional Components of SAMS
The software can also be divided into functional modules.
| Module | Responsibility |
|---|---|
| Authentication | Verifies users and applies access permissions. |
| Student Management | Maintains student profiles and identifiers. |
| Course Management | Maintains course offerings, sections, and teacher assignments. |
| Attendance Management | Records and retrieves attendance for individual class sessions. |
| Reporting | Calculates attendance summaries and produces reports. |
| Database Management | Stores and maintains consistent system records. |
4. Identify the System Users and Stakeholders
A system user is someone who directly interacts with the system. A stakeholder is anyone who affects the system, is affected by it, or has an interest in its outcomes. Some stakeholders are direct users, while others may not log in to the application at all.
| User or Stakeholder | Role | Possible Responsibilities |
|---|---|---|
| System Administrator | Manages system configuration and access. | Create authorized accounts, assign roles, and maintain settings. |
| Teacher | Records and reviews attendance. | Select a course, record attendance, and correct permitted errors. |
| Student | Views permitted personal attendance information. | Check attendance summaries and report possible discrepancies. |
| Department or Academic Administrator | Reviews attendance information for academic administration. | Review reports and monitor attendance according to policy. |
| University Management | Uses summarized information for decisions. | Review institutional attendance trends and policy compliance. |
| IT Support Staff | Supports the technical environment. | Resolve server, network, backup, and deployment issues. |
5. Identify the System Boundaries
A system boundary defines what is included in the system being analyzed and what remains outside it. It helps the analyst control project scope and clarify responsibilities.
For SAMS, the boundary separates the attendance application and its managed functions from external systems, people, and institutional processes.
5.1 Functions Inside the Boundary
- Authentication and role-based access.
- Student, course, section, and teacher records maintained by the application.
- Attendance-session creation and attendance entry.
- Attendance storage, retrieval, and correction under approved permissions.
- Attendance percentage calculations and reports.
- Application-level validation and audit records, where implemented.
5.2 Functions Outside the Boundary
- The university's official policy-making process.
- Physical classroom teaching and student participation.
- Official enrollment and registration processes, if handled by another system.
- The university's payroll and financial management systems.
- Campus internet infrastructure and third-party services not managed by SAMS.
Some outside systems may exchange information with SAMS in a future version. Integration does not automatically mean that the external system becomes part of the attendance application's boundary.
5.3 System Boundary Diagram
Teachers, Students, Administrators
Login and Access Control
Student and Course Management
Attendance Recording
Attendance Calculation
Report Generation
Student, Course, Session, Attendance Records
Conceptual diagram: users interact with the application, which reads and writes authorized records in the database and produces outputs.
6. Identify Inputs, Processes, Outputs, and Feedback
A system can be analyzed through its input-process-output model. Feedback and control mechanisms help ensure that the system operates according to requirements.
| Element | Explanation | SAMS Example |
|---|---|---|
| Input | Data or requests entering the system. | Student ID, course, class date, attendance status, and login credentials. |
| Process | Operations performed on the inputs. | Validate user permissions, save attendance, and calculate percentages. |
| Output | Information produced by the system. | Attendance register, student percentage, and course attendance report. |
| Feedback | Information used to identify and correct problems. | A teacher reports an incorrect record, and an authorized correction is processed. |
| Control | Rules and checks that keep operations within approved limits. | Role permissions, validation rules, and duplicate-record prevention. |
Example Calculation
Suppose a student attends 18 out of 24 eligible class sessions.
Attendance percentage = (Sessions Attended ÷ Eligible Sessions) × 100
Attendance percentage = (18 ÷ 24) × 100 = 75%
The system can display the result in a student attendance report. The denominator and treatment of excused absences must follow the institution's attendance policy.
7. Define the Project Scope
The system boundary describes what belongs to the system; the project scope specifies the features and work that will be delivered in the current project.
| Included in the Initial Project | Excluded from the Initial Project |
|---|---|
| User login and role management. | University-wide ERP replacement. |
| Student, course, and section records. | Financial accounting and tuition collection. |
| Manual attendance entry by authorized teachers. | Biometric or facial-recognition attendance hardware. |
| Attendance percentage calculations. | Automated examination eligibility decisions unless specifically approved and implemented. |
| Student-wise and course-wise reports. | Payroll, learning management, and unrelated academic modules. |
Defining the scope prevents unnecessary features from expanding a small academic project beyond its available time and resources.
8. Real-World Scenario
Scenario: Recording Attendance for a Programming Class
A teacher conducts a programming class for a section of 40 students. The teacher opens SAMS, signs in, selects the course and section, and opens an attendance session for the class date.
- The system verifies the teacher's access permissions.
- The system retrieves the enrolled students for the selected section.
- The teacher marks each student's attendance.
- The system validates the entries and saves the records.
- The system generates an attendance summary.
- An authorized user later reviews the student's attendance percentage.
System input: Course, section, class date, and attendance statuses.
System process: Validation, database storage, and calculation.
System output: Saved attendance records and summary reports.
Boundary example: The teacher's actual classroom teaching is outside the software system, while recording attendance through the application is inside it.
9. Student Exercise
Choose one real-world system and identify its components, users, and boundaries.
Suggested systems:
- Library Management System
- Hospital Appointment System
- Online Shopping System
- University Examination Management System
- Banking Transaction System
Prepare your work using the following structure:
| Task | What You Should Identify |
|---|---|
| 1. System Name | Name the real-world system and explain its purpose. |
| 2. Problem | Describe the problem the system addresses. |
| 3. Components | Identify hardware, software, data, people, procedures, and networks where applicable. |
| 4. Users and Stakeholders | List direct users and other stakeholders, with their roles. |
| 5. System Boundary | Explain which functions are inside and outside the system. |
| 6. Input-Process-Output | Give at least two examples of inputs, processes, and outputs. |
| 7. Scope | List the features included in the proposed project and the features excluded. |
10. Knowledge Check
Question 1: Which of the following is a system component?
- Data
- Software
- People
- All of the above
Show answer
Answer: d) All of the above. Data, software, and people can all be components of an information system.
Question 2: What does a system boundary define?
- The system's color scheme
- What is inside and outside the system being analyzed
- The number of users only
- The programming language only
Show answer
Answer: b). The boundary distinguishes the system under analysis from its external environment.
Question 3: In SAMS, who normally records class attendance?
- Authorized teachers
- Unrelated external customers
- Payroll staff in every case
- Internet service providers
Show answer
Answer: a) Authorized teachers. The final permissions should be defined by the university's approved workflow.
11. Conclusion
Identifying a real-world system requires more than naming a software application. A system analyst must understand the system's purpose, components, users, inputs, processes, outputs, feedback mechanisms, and boundaries.
In the Student Attendance Management System example, teachers and administrators interact with the application, attendance data is processed and stored in a database, and reports are produced for authorized users. Defining the boundary and scope makes the project easier to plan, design, and implement.
Key takeaway: A clear understanding of the system and its environment should come before detailed database design and programming.
Course: System Analysis and Design
কোন মন্তব্য নেই:
একটি মন্তব্য পোস্ট করুন