The document discusses key aspects of software engineering from an industry perspective. It states that unclear requirements are the most common reason for project failure, with a 68% failure rate. It emphasizes the importance of proper requirement analysis to avoid budget overruns, missed deadlines, and incomplete or delayed software delivery. It also covers topics like requirement management tools, software development activities, version control, and testing environments and tools.

1. © TechKnowXpress
SOFTWARE ENGINEERING
(INDUSTRY PERSPECTIVE)

2. © TechKnowXpress
MOST IMP REASON FOR PROJECT FAILURE
CLARITY OF REQUIREMENTS
(68% PROJECT FAILURE RATE)

3. © TechKnowXpress
REQUIREMENT ANALYSIS
 Impacts of inadequate requirement analysis
 Project budget overrun
 Project deadlines missed
 Incomplete delivery
 S/w developed after prolonged time when the corporate need is over

4. © TechKnowXpress
SCENARIO
 At the education level, science is more important
 But at the industry level, technology is more
important
 Technology is the implementation of science
 Industry needs tools and technology to get benefit
of science, which is embedded into it.

5. © TechKnowXpress
REQUIREMENT MANAGEMENT TOOLS
 Requirement management tools
Caliber
codeBeamer Requirement Management
Enterprise Architect

6. © TechKnowXpress
SOFTWARE DEVELOPMENT ACTIVITIES
 Development
 Test Bed Generation
 Environment for testing
 Test Data Preparation
 Test Automation Script Preparation
 Project Management

7. © TechKnowXpress
VERSION CONTROL
 Version management tools
 Important capabilities of Version control tools
 Version number pattern
 Role of configuration manager
 Version migration

8. © TechKnowXpress
DEVELOPMENT
 Multiple team members and teams - project
 Source Code control – challenging
 Phases of software features – new versions
 Compatibility and portability
 Therefore, industry uses tools like
SVN
CVS

9. © TechKnowXpress
IMPORTANT CAPABILITIES OF VERSION
CONTROL TOOLS
 IDE(Integrated Development Environment) –
integration – version control tools(eg: SVN)
 SVN – client software – native integration
capability
 Configuration Manager – Version number Pattern

10. © TechKnowXpress
WHAT IS VERSION NUMBER PATTERN?
 Example: xx.yy.zz
 xx - version number
 yy subversion number
 zz sub-subversion number

11. © TechKnowXpress
RULES
 Version number – increment – new features (v. 2.0.0)

12. © TechKnowXpress
RULES(conti…)
 Sub-subversion and sub-version number
increment:
 Development to QA team (v. 1.0.0)
 QA bug identification is addressed (v. 1.0.1)
 Client finds bug (v. 1.0.2)
 Acceptance by client (v. 1.1.0)

13. © TechKnowXpress
Version Control
 SVN – multiple source code – same product
(v. 1.1.0) (v. 2.0.0) (v. …)
Development bugs solved in 1.1.0
will be from
source 1.1.0 1.1.1
fixes bug
QA
release to client

14. © TechKnowXpress
EXAMPLE –
 Client upgrades OS
 Eg.: windows 8.1 to windows 10

15. © TechKnowXpress
VERSION MIGRATION
 Change log – maintenance – version
 Eg: 1.1.0 -> 1.1.1 – changes
 Patch for version upgradation.
 Example

16. © TechKnowXpress
PATCH
 A patch is a software update comprised code inserted
(or patched) into the code of an executable program.
 A patch is installed into an existing software program.
 Patches are often temporary fixes between full
releases of a software package.

17. © TechKnowXpress
PATCH(conti…)
 Fix a software bug
 Install new drivers
 Address new security vulnerabilities
 Address software stability issues
 Upgrade the software

18. © TechKnowXpress
KEY NOTES
Stable version for each product is declared
Different versions – stable – different environment

19. © TechKnowXpress
SOFTWARE DEPARTMENT
DIRECTOR
PROJECT
MANAGER
DEVELOPMENT
HEAD
QA HEAD CONFIGURATION
MANAGER
DEVELOPMENT
LEAD 1
DEVELOPMENT
LEAD 2
MANUAL
TEST
LEAD
AUTOMATIC
TEST
LEAD
MODULE
LEAD 1
MODULE
LEAD 2

20. © TechKnowXpress
PROJECT MANAGER
UAT
MANAGER
DEVELOPMENT
MANAGER
PROJECT
MANAGER
CRM
MANAGER
QA
MANAGER
CONFIGURATION
MANAGER

21. © TechKnowXpress

22. © TechKnowXpress
TESTING
 Test Data
Test Scenarios
Test Case
Test Data Expected Result
Success Failure

23. © TechKnowXpress
TESTING ENVIRONMENT
 OS Name
 Version
 Country specific
 Language
 Service Pack
 Browser
 Name
 Version

24. © TechKnowXpress
TESTING ENVIRONMENT(conti...)
 RDBMS Tools
 Server side name
 Client side name

25. © TechKnowXpress
TESTING ENVIRONMENT(conti...)
 Pre – installed software / Environment on OS
 Players
 Flash version
 Win media version
 Framework
 Eg: Dotnet
 Version
 Partial/full

26. © TechKnowXpress
TESTING ENVIRONMENT(conti...)
 IDES
 Netbeans
 Eclipse
 Application server
 Name
 Version
 Independent / Embedded

27. © TechKnowXpress
SOFTWARE TESTING TOOLS
 QC (Quality Control)
 QTP(Quick Test Professional)
– future scenarios
- Data at one single place
- Testing process Automation

28. © TechKnowXpress
IMPORTANCE OF AUTOMATION TESTING
USING AN EXAMPLE
 Eg: Income Tax Calculation

29. © TechKnowXpress
-techknowxpress@gmail.com