Software Engineering principles and practices

Software Engineering

1. Department of Collegiate and Technical Education
Software Engineering Principles and Practices(IV Semester)
Computer Science and Engineering
WEEK 1- Overview
Session - 3

2. Topics of the session :
•Components of process
•Process activities
•Project ,product,process
•Process assessment and improvement
•Software engineering Ethics

3. 1.3.1 Components of process:
1.Program : A computer
program is a list of instructions
that tell a computer what to
do.
 
2.Documentation : Consists of
different types of manuals.
Examples of documentation
manuals are: Data Flow
Diagram, Flow Charts, ER
diagrams, etc.
Documentation

4. •3. Operating Procedures: 
Operating Procedures consist of
instructions to set up and use the
software system and instructions
on how to react to the system
failure.
Example of operating system
procedures manuals is: installation
guide, Beginner's guide, reference
guide, system administration guide,
etc

5. 1.3.2 Process Activities :
1.Software specifications:  It describes what the software
will do and how it will be expected to perform. It defines
the requirements needed to perform a project. It also
describes the functionality the product needs to fulfill all
stakeholders (business, users) needs. The functionality
of the software and constraints on its operation must be
defined.
2.Software development: Software development is the
process of conceiving, specifying, designing,
programming, documenting, testing, and bug fixing
involved in creating and maintaining applications. The
software to meet the requirement must be produced.

6. 3.Software validation:  is the process of checking that a software system
meets specifications and requirements so that it fulfills its intended purpose. The
software must be validated to ensure that it does what the customer wants. It may
also be referred to as software quality control.
 
4.Software Evaluation :is the process of measuring the performance and
utility of software assets in businesses' inventories. The purpose of software
evaluation is to detect dysfunctional and unused software. Companies can
optimize their costs by discarding software with low IT value. So, with these
savings, they can make more efficient IT investments.

7. 1.3.3 Project :
is a development project in which a software process is used.
an individual or collaborative enterprise that is carefully planned to
achieve a particular aim.
is defined as
 a sequence of tasks that must be completed to attain a certain
outcome.
It refers to any temporary endeavor with a definite beginning and end.
executing the activities for some specific user needs.
Depending on its complexity, it can be managed by a single person or more.
EX: Students management system , Online shopping system, library management
system ,Enterprise resource management system ,Hospital management system ,
nowadays ..latest need as Android Task Monitoring, analysis for product rating ,
Finger print based ATM system etc..

8. 1.3.4 Product: 
Software products are the outcomes of a software project.
Product includes any software manufactured based on the customer’s request.
This can be a problem solving software or computer based system.
this is the result of a project.
 
Ex: i)Students management systems are : Veracross,
 
FACTS Student Information System,
 
Salesforce.org Educ ation Cloud,
 
PowerSchool eSchoolPLUS,
 
Infinite Campus etc
ii) Best ERP Software for SMEs in India : Tally ERP , Sage ERP , Marg ERP , Strategic ERP etc
iii) best shopping cart in India : Shopify, Zepo , Build-a-Bazaar ,BigCommerce, KartRocket etc

9. 1.3.5Process: 
•Process specifies a method of development software.
• It is a set of sequence steps that have to be followed to create a project.
•The main purpose of a process is to improve the quality of the project.
•The process serves as a template that can be used through the creation of its
examples and is used to direct the project.
 
•The main difference between a process and a product is that the process is a set of
steps that guide the project to achieve a convenient product. while on the other hand,
the product is the result of a project that is manufactured by a wide variety of
people.
 

10. S.NOProduct Process
1. Product is the final production of the project.
While the process is a set of sequence
steps that have to be followed to
create a project.
2. A product focuses on the final result.
 
Whereas the process is focused on
completing each step being
developed.
3.
 
In the case of products, the firm guidelines are
followed.
 
In contrast, the process consistently
follows guidelines.
4. A product tends to be short-term.
Whereas the process tends to be long-
term.
5.
The main goal of the product is to complete
the work successfully.
While the purpose of the process is to
make the quality of the project better.
 
 
  

11. 1.3.6 Process Assessment and improvement:
The process assessment leads to process
capability determination and process
improvement.
Process capability determination is an organized
assessment, which analyzes the software
processes in an organization. Assessment
includes five phases initiating, diagnosing,
establishing, acting and learning.

12. •SPICE (Software Process Improvement and Capability Determination)
is a standard used for both process improvement and process capability
determination.
•SPICE provides a framework for assessing the software process and is
used by the organizations involved in planning, monitoring,
developing, managing, and improving acquisitions.
• It is carried out in accordance with the International Organization
for Standardization (ISO) and International Electro-technical
Committee (IEC), which are used together and known as ISO/IEC
15504.

13. Software Process Improvement (SPI) Cycle includes:
Process measurement : Software is measured to Create the quality of the
current product or process. Anticipate future qualities of the product or
process. Enhance the quality of a product or process. It is quantifying of
products, processes, and resources to make decisions to meet project
goals.
Process analysis: You need to document the current processes, or the
needed core processes of a project that are going to be handled with
software.
Process change: the transition from an existing state of the software
product to another improved state of the product. It controls, supports,
and manages changes to artifacts, such as code changes, process changes,
or documentation changes.

14. 1.3.7 Software Engineering Ethics:
“Ethics”, addresses any intentional action that impacts negatively or positively
the lives and values of others.
Software engineering ethics can describe the activity of software engineers
making practical choices that affect other people in significant ways.
Software engineering ethics is clearly both an activity and a body of principles.
Second, it can be used to describe a collection of principles, guidelines, or ethical
imperatives that guide or legislative action,

..continued

15. Billion people depend on software systems to effectively conduct their
daily lives has led many in computing to give more attention to the
nontechnical aspects and to wrestle (hard struggle) with the ethical
impact of their daily decisions and the values.
The technical decisions should be consciously guided by values.
Professions describe these values in Codes of Ethics, Codes of Conduct
and Codes of Practice.
Example for ethical decisions: Intellectual property rights, privacy
policies, and online etiquette, or "netiquette"
( Note : Netiquette thus describes
 the rules of conduct for respectful and appropriate communication
on the internet. )

16. Software engineers shall adhere to the following Eight Principles:
•PUBLIC - Software engineers shall act consistently with the public interest.
•CLIENT AND EMPLOYER - Software engineers shall act in a manner that is in the best interests of their client or
employer and that is consistent with the public interest.
•PRODUCT - Software engineers shall ensure that their products and related modifications meet the highest professional
standards possible.
•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.
•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 promote an
ethical approach to the practice of the profession.

17. Computer Science and Engineering – 20CS44P
Chairperson: Smt. Usha D 142- Govt,Women’s Polytechnic,Ramanagar
Moderator :
  
Smt. Sunandadevi V K
109- Government Polytechnic, Kalaburagi
Subject Reviewer
 
Smt. Suvarna Mahadev V M
136- Government Polytechnic, Bagepalli
Content Developers
1. A V Radhika
149- GPT ,Chitradurga
2.Lohith S Y 173-GPT, Harapanahalli
3. Raghavendra M 131- School of Mines ,KGF
4.Poornima Kebbepura R C 112- GPT, Tumkur
4. O K Manjunath 156-GPT, Mulabagal
6. Jyothi B.K 177-GPT ,Siddapura.
7. Pallavi H S 169-GPT KGF.

18. THANK YOU