CampusLearn
← CSC 411 Final Year Computer Science Project

Project Conception, Problem Formulation, and Requirements Engineering

Notes

Introduction to Project Conception The undergraduate final year computer science project represents the culmination of academic training, requiring students to solve a non-trivial, authentic problem using sound software engineering principles. Success begins with identifying an impactful problem domain rather than selecting a trending technology. Projects should address real societal, commercial, or industrial gaps, particularly within the local ecosystem. Formulating the Problem Statement A weak project often stems from an ambiguous problem statement. A well-formulated problem statement must establish the context, explicitly identify the deficiency in current manual or legacy digital solutions, state the consequences of that deficiency, and propose a measurable computational intervention. Students must avoid broad declarations such as building an agricultural app, focusing instead on quantifiable metrics such as reducing post-harvest supply chain delays for perishable commodities. Requirements Engineering Once the problem is established, requirements must be elicited, analyzed, and specified. Functional requirements delineate the core features the system must execute, including data capture, business logic, role-based access control, and reporting. Non-functional requirements govern system qualities such as response time, concurrent user capacity, data security, regulatory compliance, and availability. Under Kenya's Data Protection Act of 2019, any application handling personally identifiable information must incorporate privacy by design as a critical non-functional requirement. Feasibility Analysis Before committing to development, students must assess technical feasibility, operational feasibility, and schedule feasibility. Technical feasibility evaluates whether the necessary tools, hardware, and APIs are accessible. Operational feasibility examines whether intended end-users possess the digital literacy and infrastructure to adopt the platform. Schedule feasibility ensures the scope is achievable within the two academic semesters allotted for CSC 411. Practical example Consider a final year project conceived for a matatu savings and credit cooperative society, known locally as a SACCO, operating along the Nairobi-Thika superhighway. The problem identified is significant revenue leakage caused by untracked cash collections and lack of verifiable passenger manifests as required by the National Transport and Safety Authority, NTSA. The functional requirements specify that the driver or conductor must generate digitized stage-to-stage tickets, the system must log vehicle location checkpoints, and SACCO stage marshals must validate trips via mobile devices. The non-functional requirements dictate that offline ticket issuance must execute within two seconds on low-cost Android smartphones, with automated data synchronization once mobile data connectivity resumes in network dead zones. The student conducts a feasibility study verifying that local drivers can use USSD or simple touchscreen interfaces, while adhering to the Data Protection Act by masking passenger phone numbers captured during payment processing.

Quiz

1. Which of the following represents an essential non-functional requirement for a student project handling citizen data under Kenyan law?

2. In schedule feasibility for a standard two-semester capstone, which approach is most appropriate?

3. What is a common pitfall when formulating a computer science final year project problem statement?

Sign in to submit and securely grade your quiz.