The Agile movement proposes alternatives to traditional project management. Agile approaches are typically used in software development to help businesses respond to unpredictability which refer to a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. The primary goal of being Agile is empowered the development team the ability to create and respond to change in order to succeed in an uncertain and turbulent environment.
Feedjit
Tuesday
Monday
Rapid Application Development Model
The Rapid Application Development Model was first proposed by IBM in 1980’s. The critical feature of this model is the use of powerful development tools and techniques.
A software project can be implemented using this model if the project can be broken down into small modules wherein each module can be assigned independently to separate teams. These modules can finally be combined to form the final product.
Development of each module involves the various basic steps as in waterfall model i.e analyzing, designing, coding and then testing, etc. as shown in the figure.
Another striking feature of this model is a short time span i.e the time frame for delivery(time-box) is generally 60-90 days.
Software Engineering syllabus
UNIT I Software Development Process: Software crisis and myths, Software process and development: Generic view of process, Software life cycle and models, Analysis and comparison of varies models, an agile view of process.
UNIT II Requirement Engineering: Requirements engineering tasks, Initiating requirement engineering process, Eliciting requirement, developing use-cases, Building the analysis model, Negotiating and validating requirement, Building the analysis model.
UNIT III System Design Overview: Design process and design quality, Design concepts, Design model, Pattern based software design, Architectural design, User interface design. UML: Different methods: Rambaugh / Booch / Jakobsons, Need for standardization. Developing diagrams in UML (Use CASE, Class, Interaction, State diagrams) CASE TOOLS.
UNIT IV Validation and Testing: Strategic approach to Software testing, Strategic issues, Test strategies for conventional software, Validation testing, System testing, Debugging. White box testing and Black box testing.
UNIT V Web Engineering: WebApps engineering layers, Web engineering processes planning for web engineering projects, Project management issue for web engineering. Metrics, Requirement analysis, Analysis models for web engineering design for WebApps, testing for WebApps.
UNIT VI Planning and Management of Project: Project management, Metrics for process and projects, Estimation, Project scheduling, Risk management, Importance of software quality and measurements software engineering techniques for quality assurance, and Change management. ISO 9000 and CMM/PCMM.
Text Books 1. Roger S. Pressman, “Software Engineering”, Tata McGraw-Hill, 6th Edition, 2006. 2. G. Booch, J. Rambaugh, and I. Jacobson, “The Unified Modeling Language User Guide”, Addison Wesley, 2nd Edition, 2005. Reference Books: 1. Shari Pfleeger, “Software Engineering”, Pearson Education, 3rd Edition, 2008. 2. Ian Sommerville, “Software Engineering”, Pearson Higher Education, 10th Edition, 2016. 3. Pankaj Jalote, “An Integrated Approach to Software Engineering”, Springer New York, 2nd Edition, 2013.
Sunday
Query Language
In simple words, a Language which is used to store and retrieve data from database is known as query language. For example – SQL
There are two types of query language:
1.Procedural Query language
2.Non-procedural query language
1. Procedural Query language:
In procedural query language, user instructs the system to perform a series of operations to produce the desired results. Here users tells what data to be retrieved from database and how to retrieve it.
For example – Let’s take a real world example to understand the procedural language, you are asking your younger brother to make a cup of tea, if you are just telling him to make a tea and not telling the process then it is a non-procedural language, however if you are telling the step by step process like switch on the stove, boil the water, add milk etc. then it is a procedural language.
Relational Algebra:
Relational algebra is a conceptual procedural query language used on relational model.
2. Non-procedural query language:
In Non-procedural query language, user instructs the system to produce the desired result without telling the step by step process. Here users tells what data to be retrieved from database but doesn’t tell how to retrieve it.
Relational Calculus:
Relational calculus is a conceptual non-procedural query language used on relational model.
Note: while describing relational algebra and relational calculus, because they are theoretical mathematical system or query language, they are not the practical implementation, SQL is a practical implementation of relational algebra and relational calculus.
Relational Algebra, Calculus, RDBMS & SQL:
Relational algebra and calculus are the theoretical concepts used on relational model.
RDBMS is a practical implementation of relational model.
SQL is a practical implementation of relational algebra and calculus.
Relational Calculus: Tuple Relational Calculus, Domain Relational Calculus
Relational Calculus
- Relational calculus is a non-procedural query language. In the non-procedural query language, the user is concerned with the details of how to obtain the end results.
- The relational calculus tells what to do but never explains how to do.
Types of Relational calculus:
Relational algebra
Relational algebra is a procedural query language, which takes instances of relations as input and yields instances of relations as output. It uses operators to perform queries. An operator can be either unary or binary. They accept relations as their input and yield relations as their output.
Wednesday
Unit 2: Keys
Unit 2: Integrity Constraints
Integrity Constraints
- Integrity constraints are a set of rules. It is used to maintain the quality of information.
- Integrity constraints ensure that the data insertion, updating, and other processes have to be performed in such a way that data integrity is not affected.
- Thus, integrity constraint is used to guard against accidental damage to the database.
Unit 2: Relational Model (Introduction)
Relational Model was proposed by E.F. Codd to model data in the form of relations or tables. After designing the conceptual model of Database using ER diagram, we need to convert the conceptual model in the relational model which can be implemented using any RDMBS languages like Oracle SQL, MySQL etc. So we will see what Relational Model is.
Monday
SE
Unit 1:
Lecture 1: PPT Definition, characteristics, Myths,Crisis
Lecture 3: PPT SDLC, Build and fix, water fall, iterative
Lecture 4: PPT Prototype model
Lecture 5: PPT1 PPT2 Spiral model , V model
Lecture 6: RAD model
Lecture 7: Agile Model Agile Model and Scrum
Unit 2:
Lecture 9: Classification of Software requirements , Functional vs Non-functional Requirements
Lecture 10: Characteristics of Good SRS
Lecture 11: Requirement Engineering 7 Tasks
Lecture 12: Who is System Analyst? Software Metrics
Lecture 13: requirement analysis and Modeling
scenario based modeling
Lecture 14: scenario based modeling 1) use case
Lecture 15: Use case symbols etc 2) activity diagram
Lecture 16: How to draw Activity diagram
Class based modeling
Lecture 17: what is class based modeling 1) Class Diagram 2) Class-Responsibility-Collaborator (CRC) Modeling
Behavioral Modeling
Lecture 18: What is Behavioral Model? state diagram sequence diagram
Flow oriented model
Lecture 19: Flow oriented model
DBMS
Syllabus | |
Text Book | Reference Book |
Introduction: [Basic concepts, Advantages of DBMS over file-processing systems, Data abstraction, Data models and data independence, Components of DBMS and overall structure of DBMS]
Data modeling, entities, attributes, relationships, constraints, Keys, E-R diagrams, and components of the E-R model
Entity-Relationship Model (study Material and PPT)
--------------------------------------------------------------------------------------------------------------
Relational Model: Basic concepts, Attributes and domains, Concept of integrity and referential constraints, Schema diagram, Relational query languages, Relational Algebra and Relational Calculus: Tuple relational and domain relational calculus
Unit 2: Relational Model Overview
Unit 2: Relational Calculus : Tuple Relational calculus, Domain relational calculus
----------------------------------------------------------------------------------------------------------
- Introduction to SQL, characteristics, advantages, data types, and literals
- DDL, creating, modifying, and deleting tables, Views: Creating, Dropping, Updation using views, DML, Operators, SQL DML queries, SELECT query and clauses. Structured Query Language- II: Set operations, Predicates and joins, Set membership, Tuple variables, Set comparison, Ordering of tuples, Aggregate functions, Nested queries, Database modification using SQL Insert, Update and Delete queries, Dynamic and SQL and concept of stored procedures, Queryby-example
1. Introduction to SQL | ||
2. Intermediate SQL | ||
3. Advanced SQL |
-------------------------------------------------------------------------------------------------------
UNIT IV: Relational Database Design and Storage Systems
- Notion of normalized relations
- Functional dependency, decomposition, and properties
- Questions [Explain trivial dependency? 2 marks
- What is meant by the closure of functional dependencies? Illustrate with anexample.
- What is Functional Dependency? Explain types and properties of FD’s.
- ]
- Normalization using functional dependency, multi-valued dependency, and join dependency
- Normalizations ( 1 nf,2nf,3nf,bcnf,4nf,5nf) and examples
- Questions:
- What is normalization? Explain its need.
- Explain insertion, deletion and modification anomalies with suitable examples.
- State BCNF. How does it differ from 3NF?
- State 1NF, 2NF & 3NF and explain with examples.
- Storage systems: secondary storage, RAID,
- 4. RAID
- file organization : Click here
- Indices, static and dynamic hashing
- click here
- Distinguish between: i) Primary and Secondary indexing. ii) Ordered indexing and hashing.
- B-Trees and B+ Trees
UNIT V: Query Processing and Transaction Management
- Measures of query cost
- Selection operation, sorting, and join operation
- Transaction concept, components of transaction management
- Concurrency and recovery system
- Concurrency control protocols (timestamps, locking), validation
- click here
- Multiple granularity, deadlock handling
- click here
- Crash recovery methods (log-based recovery, shadow-paging)
- Buffer management and
- remote backup system
- Click here
- [Question : Write in detail about Remote Backup systems?]
Recent
Weekly
-
Class-Responsibility-Collaborator (CRC) Modeling Class-responsibility-collaborator (CRC) modeling [Wir90] provides a simple means for ident...
-
What is class based modeling Class-based modeling represents the objects that the system will manipulate, the operations (also called meth...
-
Syllabus Text Book Reference Book ---------------------------------------------------------------------------...
-
Characteristics of Good SRS[Software Requirement Specification] Following are the characteristics of a good SRS document: Correctness: U...
-
Syllabus Unit 1: Principles of Testing, Software development life cycle model: Phases of s...
-
ER model stands for an Entity-Relationship model. It is a high-level data model. This model is used to define the data elements and relation...
-
Unit 1: Principles of Testing Software development life cycle model: Phases of software project, Quality, Quality assurance and quality co...
-
QUESTION BANK Unit 1 part1 Explain different Phases of software project. Define Quality assurance and quality cont...
-
Understanding the Course Structure Based on the provided course outline, the course aims to provide a comprehensive overview of entreprene...
-
Question Bank 1: A. Explain the "Pesticide paradox" in software testing and how to avoid it. B. Differentiate between verification...