Scribd
Upload
59 views6 pages

SE Notes

1. The document introduces concepts in software engineering including the software process, process framework, and umbrella activities. 2. A process framework establishes the foundation for a complete software engineering process through identifying framework activities and umbrella activities applicable across the entire process. 3. The document also discusses principles of software development including keeping solutions simple, maintaining a clear vision, planning for reuse, and being open to the future. It introduces various process models in software engineering.

Uploaded by

jack
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
59 views6 pages

SE Notes

1. The document introduces concepts in software engineering including the software process, process framework, and umbrella activities. 2. A process framework establishes the foundation for a complete software engineering process through identifying framework activities and umbrella activities applicable across the entire process. 3. The document also discusses principles of software development including keeping solutions simple, maintaining a clear vision, planning for reuse, and being open to the future. It introduces various process models in software engineering.

Uploaded by

jack
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

UNIT - I

INTRODUCTION TO SOFTWARE ENGINEERING:

The nature of software,

changing nature of software,

The software process,


A process is a collection of activities, actions, and tasks that are performed when some work
product is to be created.
An activity strives to achieve a broad objective and is applied regardless of the application
domain, size of the project, complexity of the domain, size of the effort, of degree of rigor with
which software engineering is to be applied.
An action encompasses a set of tasks that produce a major work product.
A task focusses on a small, but well-defined objective that produces a tangible outcome.

The Process Framework,


A process framework establishes the foundation for a complete software engineering process by
identifying a small number of framework activities that are applicable to all software projects, regardless
of their size or complexity.

In addition, the process framework encompasses a set of umbrella activities that are applicable across
the entire software process.

A generic process framework for software engineering encompasses five activities:

Communication

Planning

Modelling

Construction
Deployment

Umbrella Activities,
Software project tracking and control –
Risk management –
Software quality assurance –
Technical reviews –
Measurement –
Software configuration management –
Reusability management –
Work product preparation and production –

Process Adaptation,
• Overall flow of activities, actions, and tasks and the interdependencies
among them.
• Degree to which actions and tasks are defined within each framework
activity.
• Degree to which work products are identified and required.
• Manner in which quality assurance activities are applied.
• Manner in which project tracking and control activities are applied.
• Overall degree of detail and rigor with which the process is described.
• Degree to which the customer and other stakeholders are involved with
the project.
• Level of autonomy given to the software team.
• Degree to which team organization and roles are prescribed.
Software Engineering Practice,

The Essence of Practice,


The essence of practice
1. Understand the problem (communication and analysis).
2. Plan a solution (modeling and software design).
3. Carry out the plan (code generation).
4. Examine the result for accuracy (testing and quality assurance).

General Principles software development myths.


The First Principle: The Reason It All Exists

A software system exists for one reason: to provide value to its users. All decisions should be made with
this in mind.

The Second Principle: KISS (Keep It Simple, Stupid!)

Software design is not a haphazard process. There are many factors to consider in any design effort. All
design should be as simple as possible, but no simpler. This facilitates having a more easily understood
and easily maintained system

The Third Principle: Maintain the Vision


A clear vision is essential to the success of a software project.

The Fourth Principle: What You Produce, Others Will Consume

So, always specify, design, and implement knowing someone else will have to understand what you are
doing

The Fifth Principle: Be Open to the Future

The Sixth Principle: Plan Ahead for Reuse lan Ahead for Reuse

SOFTWARE PROCESS STRUCTURE:

A Generic Process Model,


defining a Framework Activity,

Identifying a Task Set,

Process Patterns,

Process Assessment and Improvement.

PROCESS MODELS:

Prescriptive Process Models:

The Waterfall Model,

Incremental Process Models,

Evolutionary Process Models,


Concurrent Models,

Specialized Process Models:

Component-Based Development,

The Formal Methods Model,

Aspect-Oriented Software Development,

The Unified Process:

A Brief History,

Phases of the Unified Process,

Personal and Team Process Models:


Personal Software Process,

Team Software Process.

You might also like