By the end of this chapter, you will be able to:
Mastering these skills will help you design and analyze systems that truly solve real-world problems and meet user expectations in your trade.
System analysis and design is a foundational discipline for ICT technicians tasked with developing effective information systems that meet user needs while operating within defined boundaries. In Kenya, ICT professionals must navigate diverse environments ranging from county government offices to financial institutions, where adherence to system standards and constraints is critical for successful project delivery. This chapter explores how to identify constraints imposed by system standards during the design phase, enabling technicians to develop realistic solutions that comply with legal, technical, and organizational requirements. Understanding these constraints safeguards project viability and ensures alignment with stakeholder expectations.
System standard constraints refer to the limitations and requirements imposed on system analysis and design processes by external and internal standards. These constraints shape the scope, performance, security, and compliance aspects of an information system. For ICT technicians in Kenya, recognizing these constraints early in design phases is essential for delivering systems that are robust, scalable, and legally compliant with Kenyan ICT regulations and organizational policies.
System standards constraints are the mandatory conditions derived from established benchmarks and regulations that govern system development. These constraints influence how system components interact, how data is secured, and how performance expectations are met. They originate from various sources including international standards, national regulatory bodies, industry best practices, and organizational policies.
System standards constraints limit the design options available to the ICT technician but also provide a framework for quality assurance. For example, a hospital information system designed for a county hospital must comply with both the Health Act regulations and the Kenya Health Information System standards, ensuring patient data confidentiality and interoperability with national health databases.
Assessing system standards constraints requires categorizing them according to their nature and impact on system design. ICT technicians must classify constraints to prioritize design decisions and manage trade-offs effectively.
Technical constraints relate to the technological environment in which the system will operate. These include hardware capabilities, software platforms, network bandwidth, and compatibility with existing systems. For instance, a SACCO’s loan management system must function efficiently on the hardware available in rural branches with limited internet connectivity.
Legal constraints arise from compliance requirements imposed by governmental and regulatory agencies. Kenyan ICT technicians must consider laws such as the Computer Misuse and Cybercrimes Act when designing systems to prevent unauthorized access and data breaches. Non-compliance can lead to legal sanctions and reputational damage.
Operational constraints involve limitations related to organizational processes and human factors. These include user skills, training requirements, maintenance capabilities, and existing workflows. For example, a retail business’s point of sale system design must consider the staff’s proficiency with technology and the need for minimal downtime during business hours.
Economic constraints address budgetary limits and cost-effectiveness of the system design. ICT technicians working with county governments often face tight budgets that restrict the choice of software licenses, hardware procurement, and development timeframes. Cost-benefit analysis is critical to balance functionality with affordability.
Environmental constraints encompass physical and infrastructural factors affecting system deployment. In Kenya’s diverse geography, systems deployed in remote areas must consider power reliability, climate conditions, and internet accessibility. For example, an agricultural cooperative’s data collection system must be resilient to power outages and operate on solar-powered devices if necessary.
Create a free account to open more of this chapter.
Free: practical guides, quick cards, workplace scenarios and more.
Create a free accountThis chapter explored the application of system analysis and design concepts starting with the identification of system standard constraints, highlighting the importance of recognizing various types of assessment constraints that affect system design. It then examined the fundamental properties of a system, including organisation, interaction, interdependence, and integration, which define how system components work together. The discussion proceeded to the essential elements of a system such as control, input, process, output, feedback, and environment, emphasizing their roles in system functionality. Different system classifications were covered, distinguishing between open and closed systems, adaptive and non-adaptive systems, as well as deterministic and probabilistic systems. The chapter also reviewed various types of information systems, including management information systems, transaction processing systems, decision support systems, office automation systems, executive support systems, expert systems, knowledge management systems, and human resource systems. It further identified system models by differentiating physical models from logical models, which aid in system representation and design. Finally, the chapter addressed the categories of information at lower, middle, and top levels, culminating in a comprehensive understanding of system analysis and design concepts.
Which of the following is an example of a system input in a hospital patient management system? (2 marks)
a) Patient registration data
b) Treatment protocols
c) Staff schedules
d) Billing reports
Explain the difference between an open system and a closed system with examples relevant to Kenyan organizations. (4 marks)
Type: Individual
| Tools & Equipment | Materials |
|---|---|
| Computer with Windows 10 or above and Microsoft Office 2016 | Printing paper |
| Printer |
| S/N | Item | Quantity |
|---|---|---|
| 1 | Computer with Windows 10 or above and Microsoft Office 2016 | 1 Pc per Candidate |
| 2 | Printer | 1 Pc per 5 Candidates |
| 3 | Printing paper | 50 Sheets per Candidate |
| Items to be Evaluated | Marks Available | Marks Obtained | Comments |
|---|---|---|---|
| TASK 1: Identification of System Standards Constraints | |||
| Created a folder named 'SAD PRACTICAL 2025' on the desktop (Award 2 marks for correct folder creation or zero) | 2 | ||
| Identified at least five system standards constraints relevant to system design (Award 2 marks for each correctly identified constraint, max 8 marks) | 8 | ||
| Explained clearly the impact of each identified constraint on system design (Award 2 marks for each clear explanation, max 10 marks) | 10 | ||
| Saved the report document as 'SYSTEM_CONSTRAINTS' inside the 'SAD PRACTICAL 2025' folder (Award 2 marks for correct saving or zero) | 2 | ||
| Printed the saved report document (Award 1 mark for successful printout or zero) | 1 | ||
| Sub-Total | 23 | ||
| PRODUCT CHECKLIST | |||
| Report contains at least five system standards constraints identified with correct spelling and terminology (Award 1 mark for each correctly identified constraint, max 5 marks) | 5 | ||
| Each constraint explanation is coherent, relevant and demonstrates understanding of impact on system design (Award up to 7 marks based on clarity, relevance and depth of explanation) | 7 | ||
| Report is formatted professionally with headings, paragraphs and saved with correct file name (Award 3 marks for professional formatting and correct file naming) | 3 | ||
| Sub-Total | 15 | ||
| GRAND TOTAL | 38 | ||
Type: Individual
| Tools & Equipment | Materials |
|---|---|
| Computer with Windows 10 and Microsoft Office 2016 | Printing paper A4 size |
| Printer |
| S/N | Item | Quantity |
|---|---|---|
| 1 | Computer with Windows 10 and Microsoft Office 2016 | 1 Pc per Candidate |
| 2 | Printer | 1 Pc per 5 Candidates |
| 3 | Printing paper A4 size | 20 Sheets per Candidate |
| Items to be Evaluated | Marks Available | Marks Obtained | Comments |
|---|---|---|---|
| TASK 1: Identify System Organisation | |||
| Created a folder named SYSTEM_ANALYSIS on the desktop (Award 2 marks or zero) | 2 | ||
| Identified and described at least three components/entities of the system (Award 1.33 marks per correctly identified entity x3 = 4 marks) | 4 | ||
| Explained how the components are organised within the system (Award 4 marks for clear explanation or zero) | 4 | ||
| Sub-Total | 10 | ||
| TASK 2: Explain System Interaction and Interdependence | |||
| Identified at least three interactions between system components (Award 1 mark per interaction x3 = 3 marks) | 3 | ||
| Described interdependence between system components with examples (Award 5 marks for detailed description or zero) | 5 | ||
| Sub-Total | 8 | ||
| TASK 3: Demonstrate System Integration | |||
| Explained how different parts of the system integrate to achieve overall functionality (Award 5 marks for clear explanation or zero) | 5 | ||
| Saved the analysis report as LIBRARY_ANALYSIS.docx in SYSTEM_ANALYSIS folder (Award 2 marks or zero) | 2 | ||
| Printed the saved report (Award 1 mark or zero) | 1 | ||
| Sub-Total | 8 | ||
| PRODUCT CHECKLIST | |||
| Report content covers organisation, interaction, interdependence, and integration properties accurately (Award 8 marks for comprehensive, well-structured report or zero) | 8 | ||
| Report saved and printed with correct file name and folder (Award 3 marks for correct saving and printing or zero) | 3 | ||
| Sub-Total | 11 | ||
| GRAND TOTAL | 37 | ||
At the start of this chapter we promised you would be able to:
Tick each one you can genuinely do.
So, are you there yet?
You're competent when you can confidently do 50% or more of what this chapter promised.
Sign in to record how you're doing.