Wednesday, April 1, 2009

Glossary, Checklists, Templates, Process Model, Tiny Tools

Glossary, Checklists, Templates, Process Model, Tiny Tools

Software Engineering Glossary (abbreviated)

Software Engineering Checklists

Software Engineering Documents

Software Engineering Periodicals

Software Engineering "Tiny Tools" that provide web-based solutions to software engineering problems

Managing Software Projects

Managing Software Projects

Project Management Concepts

Estimation for Software Project

Software Project Scheduling

Risk Management

Software Project Scheduling

Maintenance and Reengineering

Quality Management

Quality Management

Software Testing Strategies

Software Quality Assurance

Software Configuration Management

Formal Methods

Cleanroom Software Engineering

Software Engineering Practice

Software Engineering Practice


A Generic View
System Engineering
Requirements Engineering

Analysis Modeling

Design Engineering
Architectural Design
Component-Level Design
User Interface Design

Pattern-Based Design

The Software Process

The Product (Software)
Generic Models
Prescriptive Process Models
Agile Process Models

Metrics - Process and Project

Metrics - Technical

Software Engineering Resources

Advanced Topics in Software Engineering

Advanced Topics in Software Engineering

Software Process Improvement

Component-Based Software Engineering

Computer Aided Software Engineering (Software Tools)

Future Directions

Web Engineering

Web Engineering


Web Engineering Process

Formulation and Planning

Analysis Modeling for Web Applications

Design Modeling for Web Applications

Testing of Web Applications

History

When the modern digital computer first appeared in 1941, the instructions to make it operate were wired into the machine. Practitioners quickly realized that this design was not flexible and came up with the "stored program architecture" or von Neumann architecture. Thus the first division between "hardware" and "software" began with abstraction being used to deal with the complexity of computing.

Programming languages started to appear in the 1950s and this was also another major step in abstraction. Major languages such as Fortran, Algol, and Cobol were released in the late 1950s to deal with scientific, algorithmic, and business problems respectively. E. W. Dijsktra wrote his seminal paper, "Go To Statement Considered Harmful", [4] in 1968 and David Parnas introduced the key concept of modularity and information hiding in 1972[5] to help programmers deal with the ever increasing complexity of software systems. A software system for managing the hardware called an operating system was also introduced, most notably by Unix in 1969. In 1967, the Simula language introduced the object-oriented programming paradigm.

These advances in software were met with more advances in computer hardware. In the mid 1970s, the microcomputer was introduced, making it economical for hobbyists to obtain a computer and write software for it. This in turn lead to the now famous Personal Computer or PC and Microsoft Windows. The Software Development Life Cycle or SDLC was also starting to appear as a consensus for centralized construction of software in the mid 1980s. The late 1970s and early 1980s saw the introduction of several new Simula-inspired object-oriented programming languages, including C++, Smalltalk, and Objective C.

Open-source software started to appear in the early 90s in the form of Linux and other software introducing the "bazaar" or decentralized style of constructing software [6]. Then the Internet and World Wide Web hit in the mid 90s changing the engineering of software once again. Distributed Systems gained sway as a way to design systems and the Java programming language was introduced as another step in abstraction having its own virtual machine. Programmers collaborated and wrote the Agile Manifesto that favored more light weight processes to create cheaper and more timely software.

Software engineering

Software engineering is the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software, and the study of these approaches; that is, the application of engineering to software.[1]

The term software engineering first appeared in the 1968 NATO Software Engineering Conference and was meant to provoke thought regarding the current "software crisis" at the time.[2] Since then, it has continued as a profession and field of study dedicated to creating software that is of higher quality, cheaper, maintainable, and quicker to build. Since the field is still relatively young compared to its sister fields of engineering, there is still much work and debate around what software engineering actually is, and if it deserves the title engineering. It has grown organically out of the limitations of viewing software as just programming. Software development is a term sometimes preferred by practitioners in the industry who view software engineering as too heavy-handed and constrictive to the malleable process of creating software.