Professional Documents
Culture Documents
ch1 Introduction
ch1 Introduction
• Introduction
• Critical systems
• Software processes
• Project management
• Software requirements
• Requirements engineering
processes
• System models
• Critical systems specification
• Architectural design
• Object-oriented design
Assessment
• Prerequisite :Design and Analysis of Algorithms
• Weighing of assessment
Final term examination 50
Oral exam 10
Practical examination 10
Semester work+midterm 30
--------------------------------------------------
Total 100
To path you must get at least 50% i.e. 50 grads
and 30% from final written exam i.e. 15 grads
An Introduction to Software
Engineering
introduce software engineering and
explain its importance
What is software?
What is software engineering?
What is the difference between software
engineering and computer science?
What is the difference between software
engineering and system engineering?
What is a software process?
What is a software process model?
FAQs about software engineering
Most software process models are based on one of three general models or
paradigms of software development:
Waterfall
Iterative development
Component-based software engineering.
What are the costs of software
engineering?
Roughly 60% of costs are development costs, 40% are testing costs.
Costs vary depending on the type of system being developed and the
requirements of system attributes such as performance and system reliability.
changing needs;
Delivery
Developing techniques that lead to faster delivery
of software;
Trust
Developing techniques that demonstrate that
software can be trusted by its users.
What are software engineering
methods?
Structured approaches to software development which include system models, notations,
rules, design advice and process guidance.
Model descriptions
Descriptions of graphical models which should be produced;
Rules
Constraints applied to system models;
Recommendations
Advice on good design practice;
Process guidance
What activities to follow.
Professional and ethical responsibility
Preamble
The short version of the code summarizes aspirations at a high level of the
abstraction; the clauses that are included in the full version give examples
and details of how these aspirations change the way we act as software
engineering professionals. Without the aspirations, the details can become
legalistic and tedious; without the details, the aspirations can become high
sounding but empty; together, the aspirations and the details form a
cohesive code.
PUBLIC
Software engineers shall act consistently with the public interest.
PRODUCT
Software engineers shall ensure that their products and related
modifications meet the highest professional standards possible.
Code of ethics - principles
JUDGMENT
Software engineers shall maintain integrity and independence in their professional
judgment.
MANAGEMENT
Software engineering managers and leaders shall subscribe to and promote an
ethical approach to the management of software development and maintenance.
PROFESSION
Software engineers shall advance the integrity and reputation of the profession
consistent with the public interest.
Code of ethics - principles
COLLEAGUES
Software engineers shall be fair to and supportive of
their colleagues.
SELF
Software engineers shall participate in lifelong
learning regarding the practice of their profession
and shall promote an ethical approach to the
practice of the profession.
Ethical dilemmas