Software Engineering and Modeling syllabus

PCC352COM · Third Year Computer Engineering, SPPU 2024 pattern. Every unit, the marks scheme, course outcomes and books, copied from the official syllabus PDF.

PCC352COM2 h/week theoryCCE 30 + End-sem 70
30hours of theory
05.units
02.credits

Unit-wise syllabus

UNIT I

Introduction to Software Engineering

6 hours

Derived reading outline. Source text split at semicolons, line breaks and sentence boundaries, not an official topic hierarchy.

  • Software Engineering: Definition, Importance, Software Crisis, Software Myths & Reality, The Software Process: Software Process Framework, SDLC, Prescriptive Process Models: Waterfall, V- Model, Incremental, Evolutionary Process Models: Prototyping, Spiral, Rapid Application Development (RAD), Agile Development Models: What Is Agility? Agility and the Cost of Change, Extreme Programming, Other Agile Process Models, Overview of Scrum and Kanban.
  • Case Study: Development of an Online Examination System to demonstrate various Software Life Cycle Models and Software Process Structures.
Preserved official unit paragraph

Software Engineering: Definition, Importance, Software Crisis, Software Myths & Reality, The Software Process: Software Process Framework, SDLC, Prescriptive Process Models: Waterfall, V- Model, Incremental, Evolutionary Process Models: Prototyping, Spiral, Rapid Application Development (RAD), Agile Development Models: What Is Agility? Agility and the Cost of Change, Extreme Programming, Other Agile Process Models, Overview of Scrum and Kanban. Case Study: Development of an Online Examination System to demonstrate various Software Life Cycle Models and Software Process Structures.

Unit permalink
UNIT II

Requirements Engineering

6 hours

Derived reading outline. Source text split at semicolons, line breaks and sentence boundaries, not an official topic hierarchy.

  • Requirements Engineering, Establishing the Groundwork: Identifying Stakeholders, Recognizing Multiple Viewpoints, working toward Collaboration, Asking the First Questions, Non-functional Requirements, Traceability Eliciting Requirements: Collaborative Requirements Gathering, Usage Scenarios, Elicitation Work Products, Developing Use Cases, Building the Analysis Model, Elements of the Analysis Model, Negotiating Requirements: Requirement Validation and Management.
  • Software Requirements Specification (SRS) Case Study: Requirements Engineering and SRS development for a College ERP System covering stakeholder identification, requirement elicitation, use case modelling, non-functional requirements, validation and traceability.
Preserved official unit paragraph

Requirements Engineering, Establishing the Groundwork: Identifying Stakeholders, Recognizing Multiple Viewpoints, working toward Collaboration, Asking the First Questions, Non-functional Requirements, Traceability Eliciting Requirements: Collaborative Requirements Gathering, Usage Scenarios, Elicitation Work Products, Developing Use Cases, Building the Analysis Model, Elements of the Analysis Model, Negotiating Requirements: Requirement Validation and Management. Software Requirements Specification (SRS) Case Study: Requirements Engineering and SRS development for a College ERP System covering stakeholder identification, requirement elicitation, use case modelling, non-functional requirements, validation and traceability.

Unit permalink
UNIT III

Software Modelling

6 hours

Derived reading outline. Source text split at semicolons, line breaks and sentence boundaries, not an official topic hierarchy.

  • Introduction to Software Architecture, Architectural design principles and patterns, Types of architectures: Layered, Client-Server, Micro services, MVC, Architectural styles and quality attributes, Architecture documentation (4+1 view model), Object Modelling Using UML Basic Object-Orientation Concepts, Unified Modelling Language (UML), UML Diagrams, Use Case Model, Class Diagrams, Interaction Diagrams, State Chart Diagram, Activity Diagrams, Package Diagrams, Component Diagrams, Deployment Diagram.
  • Case Study: Design and UML modelling of a Library Management System to demonstrate abstraction, modularity, object-oriented design principles, and complete UML modelling including structural and behavioural diagrams.
Preserved official unit paragraph

Introduction to Software Architecture, Architectural design principles and patterns, Types of architectures: Layered, Client-Server, Micro services, MVC, Architectural styles and quality attributes, Architecture documentation (4+1 view model), Object Modelling Using UML Basic Object-Orientation Concepts, Unified Modelling Language (UML), UML Diagrams, Use Case Model, Class Diagrams, Interaction Diagrams, State Chart Diagram, Activity Diagrams, Package Diagrams, Component Diagrams, Deployment Diagram. Case Study: Design and UML modelling of a Library Management System to demonstrate abstraction, modularity, object-oriented design principles, and complete UML modelling including structural and behavioural diagrams.

Unit permalink
UNIT IV

Software Project Management and Testing

6 hours

Derived reading outline. Source text split at semicolons, line breaks and sentence boundaries, not an official topic hierarchy.

  • Software Project Management Complexities, Project Planning, Metrics for Project Size Estimation, Project Estimation Techniques, Empirical Estimation Techniques, COCOMO—A Heuristic Estimation Technique, Scheduling, Organisation and Team Structures, Staffing, Risk Management, Software Configuration Management.
  • Software Testing, A Strategic Approach to Software Testing, Test Strategies for Conventional Software, Test Strategies for Object-Oriented Software, Test Strategies for WebApps, Validation Testing, System Testing, Debugging, Defect Life Cycle, Manual and Automated testing Case Study: Software Project Planning, Estimation, Scheduling, Risk and Configuration Management for an E-Governance Citizen Service Portal using COCOMO and empirical estimation techniques.
  • Case Study: Testing of an Online Shopping Web Application covering manual and automated testing, test planning, strategic testing approaches, object-oriented testing, Web application testing, validation, system testing and debugging techniques.
Preserved official unit paragraph

Software Project Management Complexities, Project Planning, Metrics for Project Size Estimation, Project Estimation Techniques, Empirical Estimation Techniques, COCOMO—A Heuristic Estimation Technique, Scheduling, Organisation and Team Structures, Staffing, Risk Management, Software Configuration Management. Software Testing, A Strategic Approach to Software Testing, Test Strategies for Conventional Software, Test Strategies for Object-Oriented Software, Test Strategies for WebApps, Validation Testing, System Testing, Debugging, Defect Life Cycle, Manual and Automated testing Case Study: Software Project Planning, Estimation, Scheduling, Risk and Configuration Management for an E-Governance Citizen Service Portal using COCOMO and empirical estimation techniques. Case Study: Testing of an Online Shopping Web Application covering manual and automated testing, test planning, strategic testing approaches, object-oriented testing, Web application testing, validation, system testing and debugging techniques.

Unit permalink
UNIT V

Advanced Concepts in Software Engineering

6 hours

Derived reading outline. Source text split at semicolons, line breaks and sentence boundaries, not an official topic hierarchy.

  • Agile and DevOps practices, CI/CD pipelines, DevSecOps and Secure Software Development, Software Architecture Patterns (Event-Driven, Serverless, Reactive Systems), AI in Software Engineering (AIassisted development, automated testing), Low-Code / No-Code Platforms, Software Sustainability and Green Computing.
  • Case Study: Design and implementation of a Smart City Service Portal using Agile practices, DevOps, CI/CD pipelines, Microservices architecture, Cloud-native deployment, and reusable software components.
Preserved official unit paragraph

Agile and DevOps practices, CI/CD pipelines, DevSecOps and Secure Software Development, Software Architecture Patterns (Event-Driven, Serverless, Reactive Systems), AI in Software Engineering (AIassisted development, automated testing), Low-Code / No-Code Platforms, Software Sustainability and Green Computing. Case Study: Design and implementation of a Smart City Service Portal using Agile practices, DevOps, CI/CD pipelines, Microservices architecture, Cloud-native deployment, and reusable software components.

Unit permalink

Marks and credits

HeadMarksCredit
CCE (continuous comprehensive evaluation)302
End-semester exam70

Prerequisite: Programming Fundamentals, Data Structures, Object-Oriented Programming Concepts.

Course outcomes

  1. CO1Explain software engineering principles and software development life cycle models. •
  2. CO2Analyze and document software requirements using standard practices. •
  3. CO3Design software systems using UML-based software modelling techniques. •
  4. CO4Apply project management, testing, and quality assurance techniques. •
  5. CO5Understand and evaluate modern and advanced trends in software engineering.

Books

Text books

Reference books

FAQ

How many units are in Software Engineering and Modeling?

Software Engineering and Modeling (PCC352COM) has 5 units and 30 hours of theory: Unit I Introduction to Software Engineering (6 h); Unit II Requirements Engineering (6 h); Unit III Software Modelling (6 h); Unit IV Software Project Management and Testing (6 h); Unit V Advanced Concepts in Software Engineering (6 h).

What is the marks scheme for Software Engineering and Modeling?

The official Computer Engineering 2024 pattern syllabus lists continuous comprehensive evaluation (CCE) for 30 marks and the end-semester exam for 70 marks, for 2 credits.

What should I know before Software Engineering and Modeling?

Prerequisite listed in the syllabus: Programming Fundamentals, Data Structures, Object-Oriented Programming Concepts.

Add to my plan

Browse all syllabus courses