Read without ads and support Scribd by becoming a Scribd Premium Reader.
See Premium Plans
 
Software Engineering
Sub-code=BCSE 3402(3-0-0)
PART ONE: THE PRODUCT AND THE PROCESS
Chapter 1 - The Product
Overview
•
Software is designed and built by software engineers.
•
Software is used by virtually everyone in society.
•
Software engineers have a moral obligation to build reliable software thatdoes no harm to other people.
•
Software engineers view computer software, as being made up of theprograms, documents, and data required to design and build the system.
•
Software users are only concerned with whether or not software productsmeet their expectations and make their tasks easier to complete.Software
•
Software is both a product and a vehicle for developing a product.
•
Software is engineered not manufactured.
•
Software does not wear out, but it does deteriorate.
•
Currently, most software is still custom-built. Software Application Types
•
System software
•
Real-time software
•
Business software
•
Engineering and scientific software
•
Embedded software
•
Personal computer software
•
Web-based software
•
Artificial intelligence softwareSoftware Crisis
 
•
Software failures receive a lot more publicity than software engineeringsuccess stories.
•
The software crisis predicted thirty years ago has never materialized andsoftware engineering successes outnumber the failures.
•
The problems that afflict software development are associated more withhow to develop and support software properly, than with simply buildingsoftware that functions correctly.Software Myths
•
Software standards provide software engineers with all the guidance theyneed. The reality is the standards may be outdated and rarely referred to.
•
People with modern computers have all the software development tools.The reality is that CASE tools are more important than hardware toproducing high quality software, yet they are rarely used effectively.
•
Adding people is a good way to catch up when a project is behindschedule. The reality is that adding people only helps the project schedulewhen is it done in a planned, well-coordinated manner.
•
Giving software projects to outside parties to develop solves softwareproject management problems. The reality is people who can
’
t manageinternal software development problems will struggle to manage or controlthe external development of software too.
•
A general statement of objectives from the customer is all that is neededto begin a software project. The reality is without constant communicationbetween the customer and the developers it is impossible to build asoftware product that meets the customer's real needs.
•
Project requirements change continually and change is easy toaccommodate in the software design. The reality is that every change hasfar-reaching and unexpected consequences. Changes to softwarerequirements must be managed very carefully to keep a software projecton time and under budget.
•
Once a program is written, the software engineer's work is finished. Thereality is that maintaining a piece of software is never done, until thesoftware product is retired from service.
•
There is no way to assess the quality of a piece of software until it isactually running on some machine. The reality is that one of the mosteffective quality assurance practices (formal technical reviews) can beapplied to any software design product and can serve as a quality filter very early in the product life cycle.
•
The only deliverable from a successful software project is the workingprogram. The reality is the working program is only one of severaldeliverables that arise from a well-managed software project. Thedocumentation is also important since it provides a basis for softwaresupport after delivery.
 
•
Software engineering is all about the creation of large and unnecessarydocumentation. The reality is that software engineering is concerned withcreating quality. This means doing things right the first time and not havingto create deliverables needed to complete or maintain a software product.This practice usually leads to faster delivery times and shorter development cycles.
Chapter 2 - The Process
Overview
•
The roadmap to building high quality software products is softwareprocess.
•
Software processes are adapted to meet the needs of software engineersand managers as they undertake the development of a software product.
•
A software process provides a framework for managing activities that canvery easily get out of control.
•
Different projects require different software processes.
•
The software engineer's work products (programs, documentation, data)are produced as consequences of the activities defined by the softwareprocess.
•
The best indicators of how well a software process has worked are thequality, timeliness, and long-term viability of the resulting software product. Software Engineering
•
Software engineering encompasses a process, management techniques,technical methods, and the use of tools. Generic Software Engineering Phases
•
Definition phase - focuses on what (information engineering, softwareproject planning, and requirements analysis).
•
Development phase - focuses on how (software design, code generation,software testing).
•
Support phase - focuses on change (corrective maintenance, adaptivemaintenance, perfective maintenance, preventative maintenance). 
Search
Search History:
Searching...
Result 00 of 00
00 results for result for
  • p.
    • Notes
    Load more