BCS Written Computer Science

It is a written, descriptive examination. You answer essay-style and structured questions in longhand, often with diagrams and tables. Expect to explain concepts, compare approaches, and solve design problems rather than choose from options. The official body publishes the current paper structure and marking scheme on its website, so confirm the exact format there before you start preparing.

It is generally considered more demanding because you must recall and organise knowledge without prompts. Depth matters: a correct one-line definition earns little. You need to show reasoning, give examples, and discuss trade-offs. Candidates who only memorise facts often struggle; those who practise writing structured answers under time pressure tend to do better.

Retake rules, attempt limits, and any waiting periods are set by BCS and can change between cycles. The official body publishes the current policy on its website and in the application instructions. Check those sources before assuming you can resit freely, and plan your preparation so that a retake is a backup rather than part of your main strategy.

The total duration and number of questions are published by BCS, so confirm them officially. As a working method, divide the available minutes by the number of questions, then reserve the final ten minutes for review. Allocate more time to high-mark questions and never leave a question blank; a structured partial answer usually scores better than an empty page.

Start with fundamentals and architecture, then data structures and algorithms, because later domains assume that vocabulary. Move to programming, databases, networks, and operating systems, which carry the heaviest combined weight. Then cover software engineering, security, emerging technologies, and ICT in governance. Finish with integrated practice that mixes domains, since written papers often combine topics.

Typical failure modes include shallow answers that list points without explanation, poor time allocation that leaves later questions unanswered, ignoring the command word such as compare or justify, missing diagrams where they would clarify, and illegible handwriting. Another common mistake is studying only one or two domains and hoping to specialise; the paper rewards broad coverage.

Write full answers by hand to a timer, then mark them against a checklist: definition, explanation, example, diagram, and trade-off. Get feedback from a mentor or study group on structure and clarity. Build a bank of reusable diagrams and comparison tables. Practise at least one integrated question per week that draws on two or more domains.

Yes, to a point. Clear labelled diagrams, such as a three-tier architecture or a normalisation example, save words and earn marks. Key definitions and standard trade-offs should be recallable. But memorisation alone is not enough; you must be able to adapt the diagram or definition to the specific question asked.

Those administrative details are published by the Bangladesh Computer Society on its official website and in its notices. This page does not state them because they change between cycles and no official source was supplied. Always verify dates, fees, and pass criteria directly with BCS before applying or booking travel.