Lesson Plan |
||
Name of the Faculty : GAURAV GARG | ||
Discipline : B.TECH | ||
Semester : VI Sem | ||
Subject : Principles of Software engineering | ||
Paper Code : CSE-302-F | ||
Lesson plan duration:From Jan 2018 to April 2018 | ||
work load lecture per week(in hours):3 lectures | ||
Week | Theory | |
Lecture Day | Topic | |
1st | 1 | The process, software products, emergence of software engineering |
2 | Evolving role of software, software life cycle models, | |
3 | Software Characteristics, Applications, Software crisis. | |
2nd | 1 | Project management concepts, software process and project metrics Project planning |
2 | Project size estimation metrics, project estimation Techniques | |
3 | Empirical estimation techniques | |
3rd | 1 | COCOMO- A Heuristic estimation techniques |
2 | Staffing level estimation, team structures, staffing, | |
3 | Risk analysis and management, project scheduling and tracking | |
4th | 1 | Requirements engineering, system modeling and simulation Analysis principles modeling, |
2 | Requirements engineering, system modeling and simulation Analysis principles modeling, | |
3 | Specification principles, Representation, the software requirements specification and reviews Analysis Modeling: | |
5th | 1 | Data Modeling, Functional modeling and information flow: Data flow diagrams, Behavioral Modeling; |
2 | The mechanics of structured analysis: Creating entity/ relationship diagram, data flow model, control flow model, the control and process specification; | |
3 | The data dictionary; Other classical analysis methods. | |
6th | 1 | Design concepts and principles: the design process: |
2 | Design and software quality, design principles | |
3 | Design concepts: Abstraction, refinement, modularity, |
|
7th | 1 | Software architecture, control hierarchy, structural partitioning, data structure, software procedure, |
2 | Information hiding; Effective modular design | |
3 | Functional independence, Cohesion, Coupling | |
8th | 1 | Design Heuristics for effective modularity; |
2 | The design model; Design documentation. | |
3 | Software architecture, Data Design: Data modeling, | |
9th | 1 | data structures, databases and the data warehouse, |
2 | Analyzing alternative Architectural Designs ,architectural complexity | |
3 | Mapping requirements into a software architecture; Transform flow, | |
10th | 1 | Transaction flow; Transform mapping: Refining the architectural design. |
2 | Software Testing Techniques, | |
3 | Software testing fundamentals: objectives, principles, testability; | |
11th | 1 | Test case design, white box testing, |
2 | Basis path testing: Control structure testing: Black box testing | |
3 | Testing for specialized environments, architectures and applications. | |
12th | 1 | Software Testing Strategies: Verification and validation, Unit testing, Integration testing,; Validation testing, alpha and beta testing; |
2 | System testing: Recovery testing, security testing, stress testing, performance testing; The art of debugging, the debugging process debugging approaches. | |
3 | Software re-engineering , reverse engineering ,restructuring, forward engineering. |
|
13th | 1 | Quality concepts, Software quality assurance , SQA activities |
2 | Software reviews: cost impact of software defects, defect amplification and removal; | |
3 | Formal technical reviews: The review meeting, review reporting and record keeping, review guidelines; Formal approaches to SQA; |
|
14th | 1 | Statistical software quality assurance; software reliability: Measures of reliability and availability , |
2 | The ISO 9000 Quality standards: The ISO approach to quality assurance systems, The ISO 9001 standard, Software Configuration Management. | |
3 | CASE, building blocks, integrated case environments and architecture, repository. |