CSS Computer Science Software Engineering & Compiler Construction Syllabus

Software Engineering & Compiler Construction syllabus — full chapter and topic list

Expand any chapter to see its topics and sub-topics. This is the whole examinable outline for Software Engineering & Compiler Construction in CSS Computer Science, not a summary of it.

1. 1

   Software Processes

   3 topics

   • Process Models
   • Requirements Engineering
   • Analysis Modeling
2. 2

   Design & Construction

   4 topics

   • Design Concepts & Principles
   • Architectural Design
   • Implementation & Coding
   • Software Testing
3. 3

   Quality, Maintenance & Management

   4 topics

   • Software Quality Assurance
   • Formal Specifications & Correctness
   • Maintenance & Evolution
   • Project Management & Process Improvement
4. 4

   Compiler Phases & Lexical Analysis

   2 topics

   • Translators & Compiler Phases
   • Lexical Analysis
5. 5

   Syntax & Semantic Analysis

   4 topics

   • Context-Free Grammars
   • Parsing Techniques
   • Syntax-Directed Translation
   • Semantic Analysis & Type Checking
6. 6

   Code Generation & Optimization

   3 topics

   • Intermediate Code Generation
   • Target Code Generation
   • Code Optimization Techniques

Software Engineering & Compiler Construction flashcards for CSS Computer Science

24 of 68 cards from the Software Engineering & Compiler Construction deck — real questions with worked answers.

1. In software engineering, what is a process model (software process model)?

   An abstract representation of the software process: it describes the sequence of activities, the order in which they occur, and the deliverables/work products produced, providing a framework for managing development.

2. Describe the Waterfall (classic life cycle) model and its main weakness.

   A linear, sequential model where phases (requirements, design, implementation, testing, maintenance) flow downward, each completed before the next. Weakness: rigid, no overlap, requirements must be fixed early, and working software appears very late.

3. What is the key idea and main use of the Prototyping model?

   Build a quick, throwaway or evolutionary prototype to clarify vague requirements and get user feedback early. Used when requirements are unclear; risk is that hacked-together prototypes get mistaken for the final product.

4. What characterizes the Incremental process model?

   Software is delivered in increments; the first increment is often a core product, and each later increment adds functionality. Combines elements of the waterfall applied iteratively, delivering usable software early.

5. Describe Boehm's Spiral model and its defining feature.

   An evolutionary, risk-driven model that combines iterative prototyping with systematic waterfall aspects. Each loop (spiral) has four quadrants: objective setting, risk analysis/evaluation, development & testing, and planning the next iteration. Defining feature: explicit risk analysis each cycle.

6. What is the RAD (Rapid Application Development) model?

   A high-speed incremental model emphasizing a very short development cycle (often 60-90 days) using component reuse and automated tools. Requires modular systems and adequate resources/teams; unsuitable for high technical-risk or non-modularizable systems.

7. List the core values of the Agile Manifesto.

   (1) Individuals and interactions over processes and tools; (2) Working software over comprehensive documentation; (3) Customer collaboration over contract negotiation; (4) Responding to change over following a plan.

8. In Scrum, what are the three roles, and what is a sprint?

   Roles: Product Owner, Scrum Master, and the Development Team. A sprint is a fixed-length time-box (typically 2-4 weeks) during which a potentially shippable product increment is produced.

9. What is the V-model in software development?

   An extension of the waterfall where each development phase has a corresponding testing phase: requirements↔acceptance testing, system design↔system testing, architecture↔integration testing, module design↔unit testing, forming a V shape with coding at the bottom.

10. What is requirements engineering, and what are its main activities?

    The process of establishing the services a customer requires and the constraints on the system. Main activities: elicitation (gathering), analysis/negotiation, specification (documentation), validation, and requirements management.

11. Distinguish functional from non-functional requirements.

    Functional requirements describe what the system should do (specific services/behaviors). Non-functional requirements are constraints on services/behavior such as performance, reliability, security, usability, and standards compliance.

12. What is requirements elicitation and name three techniques for it.

    The activity of discovering requirements from stakeholders. Techniques: interviews, questionnaires/surveys, brainstorming, observation/ethnography, use cases/scenarios, prototyping, and JAD (Joint Application Development) workshops.

13. What is an SRS (Software Requirements Specification)?

    A document that completely describes the external behavior of the software: functional and non-functional requirements, interfaces, and constraints. It serves as the agreed contract between customers and developers (IEEE 830 is a standard format).

14. What is requirements validation, and name one technique used for it.

    Checking that the documented requirements define the system the customer really wants — checking validity, consistency, completeness, realism, and verifiability. Techniques: requirements reviews, prototyping, and test-case generation.

15. What is analysis modeling in software engineering?

    The activity that builds models representing customer requirements from three domains: information (data), functional (processing), and behavioral (states/events) — bridging requirements and design.

16. What does a Data Flow Diagram (DFD) represent, and what are its four elements?

    A DFD models the flow of data through a system (function-oriented). Four elements: processes (transformations), data flows (arrows), data stores, and external entities (sources/sinks).

17. What is a context diagram (Level 0 DFD)?

    The highest-level DFD that represents the entire system as a single process, showing its interactions (data flows) with external entities, but no internal detail.

18. What is an Entity-Relationship Diagram (ERD) used for?

    To model the data/information domain: it depicts entities (objects/things), their attributes, and the relationships (with cardinality) between entities. It is the basis for database design.

19. What is a State Transition Diagram (STD) in analysis modeling?

    A behavioral model showing the states a system can be in, the events that cause transitions between states, and the actions taken as a result of those transitions.

20. What is a data dictionary in structured analysis?

    An organized repository that defines all data objects, data flows, and data stores used in the system — describing their composition, types, and meaning to ensure consistency.

21. Define the design concepts: abstraction and refinement.

    Abstraction is suppressing detail to focus on essential features (procedural and data abstraction). Refinement (stepwise refinement) is the complementary top-down process of elaborating an abstraction into increasing detail.

22. Define modularity and explain its benefit.

    Modularity is dividing software into separately named and addressable components (modules) that are integrated to satisfy requirements. Benefit: it makes complexity manageable (divide and conquer), easing development, testing, and maintenance.

23. Define cohesion and coupling, and state the design goal.

    Cohesion measures how strongly related the responsibilities within a single module are; coupling measures the degree of interdependence between modules. Design goal: high (strong) cohesion and low (loose) coupling.

24. List the levels of cohesion from worst to best.

    Coincidental, logical, temporal, procedural, communicational, sequential, and functional (best).

See more Software Engineering & Compiler Construction flashcards →

Planning Software Engineering & Compiler Construction for CSS Computer Science

Software Engineering & Compiler Construction (CSS Computer Science) FAQ