How To Learn Process Of Software Engineering

Software engineering (SE) is that the application of a constantly, most regimented, quantitative approach of the planning, development, operational, and more maintenance of software package, and for that reason the study of those approaches; that's, the applying of engineering to software package. In layman's terms, it's the act of victimization insights to conceive, model and scale an answer to a tangle. the primary regard to the term is that the 1968 international organization software package Engineering Conference and was meant to impress thought concerning the perceived "software crisis" at the time. Software package development, a way used and a lot of generic term, doesn't essentially subsume the engineering paradigm. The extensively accepted ideas of software package engineering as Associate in Nursing engineering discipline are laid out in the Guide to the software package Engineering Body of information (SWEBOK). The SWEBOK has become Associate in Nursing internationally accepted customary ISO/IEC.

Difference Between Software Engineering And System Engineering

• System engineering is concerned with all aspects of computer-based systems development including hardware, software and process engineering.
• Software engineering is part of this process 

Software Process Model

• A simplified representation of a software process,presented from a specific perspective
• Workflow perspective   represents inputs, outputs and dependencies 
• Data-flow perspective   represents data transformation activities 
• Role/action perspective represents the roles/activities of the  people involved in software process 

Software Process

• Set of activities whose goal is the development or evolution of software
•            Specification - what the system should do and its development constraints
•         Development - production of the software system
•       Validation - checking that the software is what the customer wants
•       Evolution - changing the software in response to changing demand.

Methods Of Software Engineering

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)

CASE (Computer-Aided Software Engineering)

Software systems which are intended to provide automated support for software process activities, such as requirements analysis, system modelling, debugging and testing.

• Upper-CASE      Tools to support the early process activities of requirements and design
• Lower-CASE   Tools to support later activities such as programming, debugging and testing

Attributes Of Good Software

The software should deliver the required functionality and performance to the user and should be maintainable, dependable and usable

• Maintainability Software must evolve to meet changing needs.
• Dependability  Software must be trustworthy
• Efficiency Software should not make wasteful use of system resources
• Usability Software must be usable by the users for which it was designed

Key Challenges Facing Software Engineering

•  Legacy systems Old, valuable systems must be maintained and updated
• Delivery There is increasing pressure for faster delivery of software
• Heterogeneity  Systems are distributed and include a mix of hardware and software.

Professional And Ethical Responsibility

• Software engineering involves wider responsibilities than simply the application of technical skills.
• Software engineers must behave in an honest and ethically responsible way if they are to be respected as professionals
• Ethical behaviour is more than simply upholding the law