BCA III SEM SOFTWARE ENGINEERING(Elective) SYLLABUS & NOTES
Software Engineering
University of Mysore SEP BCA III SEM
Course Overview
Subject : Software Engineering (Elective)
This course provides a premium technical study of the processes, models, and paradigms underpinning professional software lifecycle management. It balances formal requirements validation pipelines, comprehensive structural UML modeling configurations, and modern architectural pattern designs required for robust, scalable product development.
Course Specifications
- Semester: III
- Course Code: CAE312 (Elective)
- Course Title: Software Engineering
- Course Credits: 03(3-0-0)
- Hours/Week: 03
- Total Contact Hours: 48 Hours
- Formative Assessment Marks: 20
- Exam Marks: 80
- Exam Duration: 03
Course Content Hours
Unit 1: Process Models & Agile Methods
Overview: Introduction; Software Engineering Ethics; Software Process Models; Process Activities; Coping with Change; Agile Software Development: Agile Methods; Plan- Driven and Agile Development.
Unit Hours: 12 Hours
Unit 2: Requirements Engineering Processes
Requirements Engineering: Functional and Non-Functional Requirements; Software Requirements Document; Requirement’s Specification; Requirements Engineering Processes; Requirement’s Elicitation and Analysis; Requirement’s Validation; Requirements Management.
Unit Hours: 12 Hours
Unit 3: System Modeling & UML Notations
System Modeling: Context Models; Interaction Models- Use Case Modelling, Sequence Diagrams; Structural Models- Class Diagrams, Generalization, Aggregation, Behavioral Models- Data-Driven Modelling, Event-Driven Modelling; Model-Driven Engineering.
Unit Hours: 12 Hours
Unit 4: Architectural Design & Implementation
Architectural Design: Architectural Design Decisions; Architectural Views; Architectural Patterns- Layered Architecture, Repository Architecture, Client–Server Architecture Pipe and Filter Architecture.
Design And Implementation: Object-Oriented Design Using The UML- System Context and Interactions, Architectural Design, Object Class Identification, Design Models, Interface Specification; Design Patterns; Implementation Issues.
Course Outcomes (COs)
- CO1: Explain software engineering concepts, process models, and agile practices.
- CO2: Apply techniques to gather and manage software requirements.
- CO3: Model systems using UML diagrams and system modeling techniques.
- CO4: Design software architecture using patterns and UML notations.
Conclusion
Acquiring a deep grasp of structural software design choices and lifecycle principles equips computing students to manage real-world development environments reliably. Integrate the complete digital cloud documentation repositories provided above to align your studies exactly with University of Mysore academic blueprints.
Engineering Architecture
Figure 1: Analytical structural mapping tracking system design dependencies, documentation verification, and implementation patterns.
Comments
Post a Comment