← CSC 411 Final Year Computer Science Project
System Architecture, Design Methodologies, and Implementation Frameworks
Notes
Architectural Design and Methodologies
A rigorous final year project demands explicit architectural modeling before coding commences. Software engineering methodology selection dictates the development lifecycle. Most capstones employ Agile Scrum over rigid Waterfall models because requirements inevitably evolve following supervisor feedback. Scrum facilitates two-week sprint cycles focusing on progressive increments: database layer, core backend services, external integrations, and client interfaces.
Architectural Patterns
Students must justify their architectural choices using standardized patterns. The Model-View-Controller pattern separates domain data, business logic, and presentation interfaces. For systems handling diverse clients such as web dashboards, mobile applications, and USSD gateways, a decoupled client-server architecture powered by Representational State Transfer, REST, or GraphQL APIs is standard. Microservices may be explored, but students must defend whether operational complexity is warranted over a clean modular monolith for capstone evaluation.
Third-Party API Integration
Modern Kenyan software systems rarely exist in isolation. Robust projects integrate ubiquitous enterprise endpoints. The Safaricom Daraja API provides mobile money capabilities through Customer to Business, C2B, and Business to Customer, B2C, channels. Integration requires implementing secure authentication using OAuth tokens, handling asynchronous webhook callbacks through publicly accessible endpoints, and managing network latency. Telecommunications aggregators like Africa's Talking supply application programming interfaces for two-way Short Message Service, SMS, and Unstructured Supplementary Service Data, USSD, vital for serving feature-phone demographics.
Database and Interface Design
Data layer modeling requires relational integrity through normalized Entity Relationship Diagrams, ERDs, or well-structured document collections for NoSQL datastores. Indexing strategies, foreign key constraints, and transactional ACID properties must be documented to prevent concurrency issues such as double-spending in financial transactions.
Practical example
A student develops a market linkage platform connecting smallholder tea and dairy farmers in Murang'a County directly to urban wholesalers in Nairobi.
The system utilizes a decoupled architecture featuring a Node.js Express backend, a PostgreSQL relational database, and dual user interfaces consisting of a React web dashboard for wholesalers and a USSD menu for rural farmers.
The student designs a normalized schema with tables for users, produce listings, inventory batches, and transactions.
For payment, the student configures the Safaricom Daraja API. When a wholesaler approves a milk delivery, the backend initiates a Business to Customer payment. The application exposes an HTTPS endpoint registered with Safaricom to capture asynchronous callback payloads confirming transaction status.
By leveraging Africa's Talking USSD simulator during local testing, the student demonstrates that farmers can list liters of milk harvested without requiring an internet data plan, proving robust architectural adaptability for varied network access environments.
Quiz
1. Why is an Agile Scrum methodology generally preferred over Waterfall for final year computing capstone projects?
2. When integrating the Safaricom Daraja M-Pesa API, why must an application expose a secure public callback URL?
3. What is the primary role of a normalized Entity Relationship Diagram in capstone design chapters?
Sign in to submit and securely grade your quiz.