100 likes | 185 Views
Software Engineering – Introduction. SOFTWARE In 1970 less than 1% of the public could define what “computer software” meant. Today most people feel they understand what it is, but do they?
E N D
Software Engineering – Introduction SOFTWARE In 1970 less than 1% of the public could define what “computer software” meant. Today most people feel they understand what it is, but do they? Textbook definition: Software is instructions (computer programs) that when executed provide desired features, functions and performance. They provide data structures that enable the programs to adequately manipulate information. Additionally, they are documents that describe the operation and use of the programs
Software Engineering – Introduction SOFTWARE - CHARACTERISTICS Software is developed or engineered, it is not manufactured in the classic sense. Except obviously the need to copy the disk or download the program. Software does not wear out. Is this true? The book states, “Software is not susceptible to the environmental maladies the cause hardware to wear out.
Software Engineering – Introduction SOFTWARE - CHARACTERISTICS
Software Engineering – Introduction SOFTWARE - CHARACTERISTICS
Software Engineering – Introduction SOFTWARE - CHARACTERISTICS Although the industry is moving toward component-based construction, most software continues to be custom built.
Software Engineering – Introduction SOFTWARE – CHANGING NATURE MANY TYPES OF SOFTWARE System Software Application Software Engineering/Scientific Software Embedded Software Web Applications Artificial Intelligence Software Open Source
Software Engineering – Introduction SOFTWARE – LEGACY Older programs are often referred to as Legacy Software. Legacy Software has many issues related to quality. It must be: adapted to meet the needs of new computing environments Apple vs. Windows upgrade paths enhanced to implement new business requirements Company adds new distribution methods extended to become interoperable with more modern systems or databases Y2K conversion from COBOL to RDBMS re-architected to make it viable within a network environment Brick and morter vs. Web-based business Is it soly an IT issue, i.e. Pep Boys
Software Engineering – Introduction SOFTWARE – MYTHS Which of these statements are true? We already have a book that’s full of standards and procedures for building software. Won’t that provide my people with everything they need to know? If we get behind schedule, we can add more programmers and catch up. Sometimes called the Mongolian horde concept. We practiced this at IBM. If I decide to outsource the software project to a third party, I can just relax and let that firm build it. ? How do you insure outsourced projects meet non-functional requirements? A general statement of objectives is sufficient to begin writing programs, we can fill I the details later. Project requirements continually change, but change can be easily accommodated, because software is flexible.
Software Engineering – Introduction SOFTWARE – MYTHS Once we write the program and get it to work, our job is done. 60 – 80 % of effort is expended after the initial deployment to customers. Until I get the program running, there is no way to access quality. The only deliverable work product for a successful project is the working program. Software engineering makes us create voluminous and unnecessary documentation and will invariably slow us down.
Software Engineering – Introduction SOFTWARE – HOW IT STARTS Outside of academia, it all starts with a business need. This need is usually expressed informally. Line part at Pep Boys – Ever changing # of fields.