Education4U

Software Engineering(SE)

Lec-01 : Introduction

Description

• This tutorial gives you a basic or fundamental understanding of the software products, software design, and the development process, software project management, and design complexities.

• Software engineering is an engineering branch accomplice the development of software products by applying well-defined scientific principles, methods, and also processes.

• The result and outcome of software engineering are efficient and reliable software products.

• Software project management has a full scope of the software engineering process because it includes communication, pre, and post-delivery support, etc.

Topics Covered

• Software process & Models • Software Metrics • Cost estimation • SRA

• Software design • Web Apps • Software Maintenance • Testing

For whom

• For the students pursuing a degree in the software development domain, Software Testing aspirants, and all enthusiastic readers.

• Students who are preparing them for their Engineering Syllabus.

Reference books

1.“Fundamentals of Software Engineering” by Rajib Mall

2.“Software Engineering: A practitioner’s approach” by Roger S Pressman

3.“Software Engineering” by Ian Sommerville

4.“Software Engineering” by Gaurav Gupta and Deepika Gupta

Q & A
Exam Questions

Q1 . Explain the different phases involved in the waterfall life cycle.
Q2 . What are the purposes of Data Flow diagrams, Entity-Relationship diagrams? Give an example diagram of each.
Q3 . What is data modeling? Give examples of data modeling.
Q4 . What is the difference between the SRS document and the design document? What are the contents we should contain in the SRS document and design document?
Q5 . Explain all the phases involved in the implementation phase.
Q6 . What are the prototyping approaches in the software process?
Q7 . What is user acceptance testing? Explain different testing in user acceptance testing. Why is it necessary?
Q8 . What are a class and an object? Give the diagrams and representation of class and object.
Q9 . What are the Drawbacks of the RAD Model?
Q10 . List out the basic principles of software project scheduling?

The E-R diagram is a graphical representation of a highly abstract system data layout. It defines the data elements in the system and their relationships.

It defines set of guidelines for developing software products. It has different stages : requirements collection, analysis, planning, development, testing, implementation, maintenance, and documentation.
The sequence of the stages mentioned in the SDLC may vary, depending on the model chosen for implementation.

To efficiently perform software implementation, many models have been proposed. Some of them include the waterfall model, agile model, spiral model, iterative model, V model, etc.

The project manager is responsible for systematically driving the software project in a way. Some of the key roles and responsibilities of a software project manager include project planning, tracking project progress, risk management, resource management, execution of development activities, and delivering projects under cost, time, and quality constraints.

o Evolutionary prototyping: In this method of system development, the initial prototype is arranged, and it is then precise through the number of phases to the final stage.
o Throw-away prototyping: Using this method, a rough practical implementation of the system is produced. The requirement issues can be identified from this implementation. It is then rejected. The system is then developed using various engineering paradigm.

Project estimation is the process used to calculate development costs (such as the amount of work, time, and resources required to deliver the project).
Project evaluation is based on past project experience or with the help of consulting experts or with the help of standard predefined business formulas.

Function points are used to measure the size of software products. In some businesses, programs play a key role in tracking and estimating project delivery.

The project manager proposes a baseline to track the delivery of the entire project.
A baseline is usually placed to track the overall tasks listed under the phase or phase.
It can help the project manager track and monitor the overall execution of the project.

Software configuration management helps users track the overall changes made in the delivery of software products. Track the updates or changes made to the software based on development and requirements collection.

Change control tracks changes made in the software to ensure consistency and updates meet corporate standards.

Many project management tools are used according to corporate standards, including Gantt chart, PERT chart, milestone list, histogram, MS project, status report, etc.

Requirements play a key role in providing a detailed description of the software product being developed.
Software requirements can help developers and other support teams related to project delivery understand the proposed target system and its expectations.

Functional requirements are used to specify functional characteristics based on business requirements.
For example, add payment options to purchase content from a website. Non-functional requirements can provide insight into security, performance, user interface, interoperability costs, etc.

According to business standards, use metrics to guide the delivery of software products.
Metrics can also be used to measure some functions delivered by software products.
Metrics are divided

Modularization divides software system tasks into multiple modules. These modules are independent of other modules, and the tasks called in each module are executed independently.

This is the advanced software engineering interview question raised in the interview.
Concurrency is the process of executing multiple events or tasks at the same time.
Concurrency can be achieved with the help of modules, events, and tasks related to software project delivery.

Cohesion is used to measure the internal dependence between the various attributes defined in the module.

Coupling is used to measure the interdependence of various elements defined in the module.

Some tools are a data flow diagram (DFD), a structure diagram, a data dictionary, UML (Unified Modeling Language) diagram, ER (Entity Relationship) diagram, etc.

DFD (Data Flow Diagram) level 0 describes the entire data flow and all abstract details in the software information system. It is also called context-level DFD.

• Black box test: Perform a black-box test to verify the output and the given valid input. However, it does not test the implementation part of the program.
• White box testing: Perform white-box testing to verify the input, output, and program implementation involved in the execution process.

Types are corrective, adaptive, perfect, and preventive

CASE (Computer-Aided Software Engineering Tool) is used to implement, support, and accelerate various SDLC activities involved in software projects.

The life cycle of software development includes the following stages:
• Requirement analysis
• Specification
• Software architecture
• Implementation
• Testing
• Documentation
• Training and support

No Reviews. Be the First Student to Review the course...

Review :

0 | 0 Reviews

Course Feature

Category Computer Science
Course Duration 13 Hrs
Language English
Price 99.00
Validity 1 Year
Q & A 24
Exam Questions 10
Full Course PDF View

Wishlist

Add to Cart

Computer Science

Software Engineering(SE)

Lec-01 : Introduction

Course Feature

Share

Data Communication

Distributed Systems

Adhoc & Sensor

Operating Systems(OS)

Useful Links

Download

Computer Science

1.Introduction & Models

2.Software Process & Models

3.Software Metrics

4.Cost estimation

5.Software Requirement Analysis & Specifications

6.Software design

7.Architecture styles & Designs

8.User-Interface

9.Web Apps

10.Software Maintenance

11.Testing

Software Engineering(SE)

Lec-01 : Introduction

1.Introduction & Models

2.Software Process & Models

3.Software Metrics

4.Cost estimation

5.Software Requirement Analysis & Specifications

6.Software design

7.Architecture styles & Designs

8.User-Interface

9.Web Apps

10.Software Maintenance

11.Testing

Q1 . Explain the Entity Relationship Diagram.

Q2 . What is SDLC ( Software Development Life Cycle) ?

Q3 . What are the different types of models available in SDLC?

Q4 . Explain the role of a Software Project Manager?

Q5 . What are the prototyping methods in the software process?

Q6 . What is Software Project Estimation?

Q7 . Explain Functional Points?

Q8 . What is a Baseline?

Q9 . What is Software Configuration Management?

Q10 . What is Change Control?

Q11 . Mention few project management tools?

Q12 . What is a Software requirement?

Q13 . What are functional and non-functional requirements?

Q14 . What are Software Metrics?

Q15 . What is Modularization?

Q16 . Explain Concurrency and how is it achieved during the software product delivery?

Q17 . What is Cohesion?

Q18 . What is coupling?

Q19 . Mention a few software analysis & Design tools?

Q20 . What is DFD Level 0?

Q21 . What is Data Dictionary?

Q22 . What are the various types of software maintenance?

Q23 . Explain CASE tools?

Q24 . Describe the software development process

Course Feature

Share

Related Courses

Data Communication

Distributed Systems

Adhoc & Sensor

Operating Systems(OS)

Useful Links

Download