System design is a critical phase in the development of library management systems, shaping how software solutions meet the specific needs of Kenyan libraries and information centres. It translates user requirements into a blueprint that guides developers and stakeholders through the implementation process. This chapter explores how software specification requirements inform system design and examines essential components such as quality, timeliness, and cost-effectiveness, which ensure that library systems are both functional and sustainable in Kenya’s diverse information environments.
The Software Specification Requirements (SRS) document serves as the foundational agreement between stakeholders and the development team, detailing what the library management system must achieve. In Kenyan libraries, this document ensures that system developers understand the unique workflows and user expectations, from cataloguing to circulation and digital resource access. Designing with a well-constructed SRS prevents costly revisions and aligns system functionality with institutional goals.
The SRS document provides a clear and detailed description of system functionalities, constraints, and interfaces, acting as a contract for developers and users. In Kenyan university libraries, for example, the SRS articulates requirements such as integration with existing databases, user authentication protocols, and reporting features that support academic research. It guides designers in creating systems that are both user-friendly and compliant with institutional policies.
The SRS encompasses several components critical to designing library systems that meet user expectations and legal standards. In Kenyan public libraries, components such as data privacy and access control are vital due to the sensitive nature of patron information.
In Kenya’s county libraries, communication between system analysts, developers, and librarians is essential to ensure that the system meets practical needs. The SRS acts as a communication tool that aligns expectations and facilitates validation through reviews and approvals.
Developing an accurate SRS for library systems in Kenya can encounter challenges such as unclear user needs or rapidly changing technology. Addressing these challenges ensures that system design remains relevant and effective.
Mitigation involves thorough stakeholder consultations, iterative reviews, employing clear and precise language, and setting realistic boundaries for system scope.
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 process of performing system design guided by the software specification requirements document, which serves as the foundation for translating user needs into technical solutions. It examined key components of system design including quality, timeliness, and cost-effectiveness, emphasizing the balance necessary to deliver functional and efficient systems. The inputs and outputs of system design were discussed, highlighting how initial requirements and constraints shape the design outputs such as system models and specifications. The stages of system design were detailed from requirement determination through to hardware study and final design, outlining the systematic progression needed to develop a viable system. Different types of system design were presented, including logical, physical, architectural, and detailed designs, each addressing distinct aspects of system structure and implementation. The chapter concluded by introducing data modelling techniques such as conceptual, relational, object oriented, logical models, and dataflow diagrams, which are essential tools for representing and analysing system data and processes. Together, these elements provide a comprehensive framework for effective system design in software development projects.
Type: Individual
| Tools & Equipment | Materials |
|---|---|
| Computer with Microsoft Word installed | System requirement brief for School Management System |
| Internet access | Printing paper A4 size |
| Printer |
| S/N | Item | Quantity |
|---|---|---|
| 1 | Computer with Microsoft Word installed | 1 Pc per Candidate |
| 2 | System requirement brief for School Management System | 1 Set per Candidate |
| 3 | Internet access for research | 1 Pc per Candidate |
| 4 | Printer | 1 Pc per 5 Candidates |
| 5 | Printing paper A4 size | 5 Sheets per Candidate |
| 6 | Dust coat | 1 Pc per Candidate |
| Items to be Evaluated | Marks Available | Marks Obtained | Comments |
|---|---|---|---|
| TASK 1: Preparation and PPE | |||
| Don dust coat before commencing work (Award 1 mark for wearing dust coat correctly) | 1 | ||
| Access and review the system requirement brief (Award 1 mark for reviewing each of the two main requirement sections) | 2 | ||
| Open Microsoft Word and set up document layout (margins, font, spacing) (Award 2 marks for correct document formatting) | 2 | ||
| Research additional relevant requirements or standards online (Award 2 marks for documented research notes or citations) | 2 | ||
| Sub-Total | 7 | ||
| TASK 2: Document Development | |||
| Write Introduction section including purpose, scope, definitions (Award 1 mark each for purpose, scope, definitions) | 3 | ||
| Specify functional requirements with clear descriptions (Award 1 mark each for at least five distinct functional requirements) | 5 | ||
| Specify non-functional requirements including performance, usability (Award 1 mark each for at least three non-functional requirements) | 3 | ||
| Include system interfaces and user characteristics (Award 1 mark each for interfaces and user characteristics) | 2 | ||
| Review and edit document for clarity and completeness (Award 2 marks for thorough review and correction) | 2 | ||
| Save the document with an appropriate file name (Award 1 mark for correct file naming) | 1 | ||
| Sub-Total | 16 | ||
| TASK 3: Printing and Submission | |||
| Print the completed SRS document on A4 paper (Award 2 marks for neat and complete printout) | 2 | ||
| Submit printed document to assessor (Award 1 mark for timely submission) | 1 | ||
| Sub-Total | 3 | ||
| PRODUCT CHECKLIST | |||
| SRS document completeness (Introduction, Functional, Non-functional, Interfaces, User characteristics) (Award 1 mark per complete section) | 5 | ||
| Document formatting and presentation quality (Award 3 marks for professional formatting, consistent style, no spelling errors) | 3 | ||
| Accuracy and relevance of requirements to the given brief (Award 4 marks for correct and relevant requirements reflecting the brief) | 4 | ||
| Sub-Total | 12 | ||
| GRAND TOTAL | 38 | ||
Type: Individual
| Tools & Equipment | Materials |
|---|---|
| Laptop with Microsoft Word installed | System design reference materials (books/manuals) |
| Writing materials (pen, notebook) |
| S/N | Item | Quantity |
|---|---|---|
| 1 | Laptop with Microsoft Word installed | 1 Pc per Candidate |
| 2 | System design reference materials (books/manuals) | 3 Pcs per Candidate |
| 3 | Writing materials (pen, notebook) | 1 Set per Candidate |
| Items to be Evaluated | Marks Available | Marks Obtained | Comments |
|---|---|---|---|
| TASK 1: PPE and Setup | |||
| Candidate uses appropriate PPE (e.g. sanitizing hands, clean workstation) (Award 1 mark for correct PPE and workstation setup or zero) | 1 | ||
| Sub-Total | 1 | ||
| TASK 2: Research and Data Collection | |||
| Candidate consults system design reference materials (Award 1 mark for each relevant material consulted up to 2 marks) | 2 | ||
| Candidate takes notes on components, inputs, and outputs (Award 2 marks for clear and organized note-taking or zero) | 2 | ||
| Sub-Total | 4 | ||
| TASK 3: Report Preparation | |||
| Candidate opens a blank Microsoft Word document (Award 1 mark for opening blank document) | 1 | ||
| Candidate writes clear identification of system design components (Award 1 mark each for naming at least three components correctly) | 3 | ||
| Candidate describes inputs of system design with examples (Award 1 mark each for at least three accurate descriptions) | 3 | ||
| Candidate describes outputs of system design with examples (Award 1 mark each for at least three accurate descriptions) | 3 | ||
| Candidate explains relationship between inputs and outputs (Award 2 marks for a clear, logical explanation or zero) | 2 | ||
| Sub-Total | 12 | ||
| TASK 4: Document Formatting and Submission | |||
| Candidate formats the report with headings and page numbers (Award 2 marks for correct formatting or zero) | 2 | ||
| Candidate saves and submits the report as per instructions (Award 1 mark for correct saving and submission) | 1 | ||
| Sub-Total | 3 | ||
| PRODUCT CHECKLIST | |||
| Report includes identification of at least 5 system design components (Award 1 mark for each correctly identified component) | 5 | ||
| Report includes clear descriptions of at least 3 inputs of system design (Award 1 mark for each accurate input description) | 3 | ||
| Report includes clear descriptions of at least 3 outputs of system design (Award 1 mark for each accurate output description) | 3 | ||
| Report explains the relationship between inputs and outputs clearly (Award up to 4 marks for a coherent explanation) | 4 | ||
| Sub-Total | 15 | ||
| GRAND TOTAL | 35 | ||