Untitled

• Software is comprised of instructions/computer programs, data structures, and documentation.
• Software instructions offer features, functions, and performance when executed.
• Data structures facilitate program manipulation of info.
• Documentation details the operation/use of programs.
• SE practices ensure the development of good software to improve living standards.

Failure Curves

• Hardware failure rates decrease initially due to infant mortality, then increase because of wear out over time.
• Software doesn't "wear out" thus the failure rate declines over time, but can increase due to side effects from changes.

Benefits of Studying SE

• It is important to study SE to reap possible benefits

Solving Problems

• Analysis involves breaking down the main problem into subproblems.
• Synthesis involves combining subproblem solutions into a final comprehensive solution.

Legacy Software

• Legacy software requires changes to adapt, enhance, interoperate, and be viable within new environments.

Software Defined

• Software includes computer programs, configuration data, and documentation.
• Configuration data supports setting up the programs.
• System documentation aids understanding of the system structure.
• User documentation explains how to utilize the system.

The Job of Engineers

• Engineers make things work.
• Engineers appropriately apply theories, methodologies, and tools.
• Engineers provide solutions when applicable theories and methods are absent.
• Engineers understand financial and organizational constraints.

Aspects of Software Production

• Technical processes are used to develop software.
• Software production involves activities like the management of projects and teams.
• Tools, theories, and methods are developed to support software production.

Stakeholders

• Participants and stakeholders are essential in software development projects.
• Customers sponsor the system development.
• Users give the system its utility by using.
• Developers build systems to meet user's needs and fulfill contractual obligations.

Development Team Roles

• Requirement analysts work with customers to identify/document requirements.
• Designers generate a system-level description of what the system should do.
• Programmers write code to implement the design.
• Testers catch faults.
• Trainers show users how to use the system.
• Maintenance teams fix later faults.
• Librarians prepare/store software requirement documents.
• Configuration management maintains correspondence among artefacts.

Software Engineering Defined

• It includes paradigms, processes, resources, and skillsets.
• Key phases include requirements analysis, design, coding, testing, deployment, and maintenance.

Software Lifecycle

• Software development includes requirements analysis, system design, and program design.
• Coding/implementation involves writing programs.
• Testing involves unit, integration, and system tests.
• System delivery involves deployment.
• Software maintainence is a phase in SDLC.

Sofware Engineers

• They use a systematic and organized approach to produce high quality software.

Good Software Product

• Good software engineering uses a strategy for producing quality software.
• Product quality has multiple facets.

Stakeholder Judgements

• Users value functionality and fewer failures.
• Designers and maintainers judge internal characteristics like ease of modification.
• Stakeholders have different criteria for quality.
• Quality models are needed.

McCall's Quality Model

• Includes factors like correctness, reliability, efficiency, integrity, usability, maintainability, etc..

Lehman's Laws

• System changes must be consistent, else become less satisfactory over time
• Complexity will increase with time, unless steps are taken to maintain it
• Functional content of systems should continually be inceased to maintain user satisfaction
• Quality will decline if it is not rigourously adapted to operational environment changes.

Software Engineering Challenges

• Acceptable quality, usable, secure & reliable software is an engineering challenge
• Cost-effective concepts that are feasible need more engineering and operational feasibility
• Projects need to respect limited budget and timeframes

Engineering Defined

• Software engineering involves a disciplined and systematic effort.
• The goal is to create and maintain quality software within timeline and budget.

Describing Bugs

• A fault comes from a human error in software activities.
• A failure comes from a deviation from the system's required behaviour.

Elements of Systems

• An activity changes characteristics.
• Objects/entities are elements involved in activities.
• Relationships match entities to activites.
• System boundaries identify inputs and outputs.

Engineering Approach

• Building is like software dev involving requirements, design, programing (building), testing and maintenance.

Process Framework

• Key process framework activities are work products, milestones and deliverables and quality assurance checkpoints.

Communication

• Communication involves reaching out to stakeholders for input.

Framework Activities

• Framework activites include communication, planning, modeling and construction.

Umbrella Activities

• They include tracking, risk management, quality assurance, reviews, config management, reusability, and work product preparation.