← CSC 215 Systems Analysis and Design
System Architecture, Testing, and Implementation
Notes
System Architecture Design
System architecture translates functional specifications into a concrete technical layout detailing software modules, physical deployment tiers, network configurations, and database schemes. Modern information systems predominantly rely on client-server architectures, ranging from traditional two-tier setups to multi-tier cloud architectures. In a three-tier architecture, the presentation tier handles user interaction through mobile interfaces or web browsers; the business logic tier enforces business rules and validation algorithms; and the data tier manages relational or non-relational database storage. Decoupling these tiers enhances horizontal scalability, improves fault tolerance, and secures proprietary business algorithms from direct exposure on client devices.
Testing Strategies
Quality assurance guarantees that a system satisfies design criteria and operates without fatal runtime exceptions. Testing proceeds in hierarchical phases. Unit testing focuses on validating individual functions, procedures, or software classes in isolation. Integration testing verifies that disparate modules communicate correctly across Application Programming Interfaces and share data without schema mismatch. System testing assesses the integrated platform against end-to-end specifications, including stress, volume, and security penetration checks. Acceptance testing, divided into alpha and beta testing, empowers operational stakeholders to test business workflows and confirm that the software is fit for operational deployment.
System Conversion Strategies
System conversion replaces an obsolete system with the newly built solution. The four classical installation strategies are direct conversion, parallel conversion, phased conversion, and pilot conversion. Direct conversion involves an abrupt cutoff of the legacy platform and immediate activation of the new system, presenting high risk if bugs occur. Parallel conversion operates both the old and new systems simultaneously for a set period, providing the highest safety but doubling operational workload. Phased conversion introduces components of the system in successive stages. Pilot conversion implements the complete system in a single operational unit or branch before broader enterprise rollout.
Practical example
Consider Machakos University migrating its academic record, fee management, and student course registration from an aging desktop local database to a cloud-based Student Information Management System.
The engineering team implements a three-tier web architecture hosted on a regional cloud data center in Nairobi. The presentation tier consists of a responsive mobile web portal, the application tier hosts RESTful microservices for course scheduling and fee auditing, and the data tier uses a replicated PostgreSQL database.
To manage transition risk without overwhelming administrative personnel, the university adopts a phased conversion strategy combined with a pilot conversion. During the pilot stage, only the School of Pure and Applied Sciences registers students via the new web portal during the September semester intake. Simultaneously, integration testing is performed against Safaricom M-Pesa paybill webhooks to confirm instant clearance of tuition payments. After identifying and resolving minor session timeout errors in the pilot, the university phases the deployment across the remaining faculties, successfully mitigating enterprise-wide operational disruption.
Quiz
1. Why is direct cutover conversion regarded as the highest-risk implementation strategy?
2. What is the primary objective of integration testing in a multi-tier application?
3. Which system conversion strategy involves running the legacy system alongside the new system simultaneously to verify output correctness?
Sign in to submit and securely grade your quiz.