SD Prelim Flashcards
such as meeting deadlines, managing resources effectively, handling changing requirements, ensuring quality, and addressing communication gaps.
Software Development Challenges
defines the boundaries and functionalities of a software project.
- identifying what the software will do & don’t
-crucial to prevent scope creep, which can lead to project delays and increased costs.
Software Scope
is a systematic and disciplined approach to the development, operation, and maintenance of software
Software Engineering Discipline:
systematic approaches to software development that prescribe the structure and interaction of the development process.
Software methodologies
recognizes the importance of people, communication, and teamwork in software development.
The Human Side of Software Development
an iterative and incremental approach to software development that prioritizes flexibility and responsiveness to change
Agile
Linear and sequential model where each phase must be completed before moving to the next
- Phases: Requirements, Design, Implementation, Testing, Deployment, Maintenance.
Waterfall Model
extension of the waterfall model where each development stage corresponds to a testing phase.
- Phases: R, D, I, T, D, M.
V-Model (Verification and Validation)
Breaks down the system into a number of small builds or increments.
- Phases: Planning, Design, Implementation, Testing, Deployment.
Phased (or Incremental) Model
Develops the system incrementally, with each increment adding functionality.
- Phases: Prototyping, Incremental Development, Operational Deployment.
Evolutionary Model
Integrates elements of both the waterfall model and evolutionary model.
- Phases: risk analysis, engineering, prototyping, and testing.
Spiral Model
Focuses on the assembly of pre-built software components to create larger systems.
- Phases: Component Acquisition, System Design, Construction, Integration, and Testing.
Component-Based Software Engineering (CBSE):
An iterative and incremental approach.
Phases: Inception, Elaboration, Construction, Transition.
Emphasizes iterative development, flexibility, and adaptability.
Unified Process (UP)
Emphasizes quick development and iteration.
Phases: Planning, User Design, Construction, Cutover.
Prototyping and user feedback are integral.
Rapid Application Development (RAD)
Involves end-users in the design and development process.
Emphasizes collaborative workshops and rapid prototyping.
Joint Application Development (JAD)
Focuses on individual and team performance improvement.
Phases: Planning, High-Level Design, Detailed Design, Code, Compile, Test.
Personal Software Process (PSP) / Team Software Process (TSP)
creating a partial or initial version of the system to gather feedback.
Phases: Requirements Specification, Quick Design, Build Prototype, User Evaluation.
Prototyping
Emphasizes customer satisfaction and flexibility.
Extreme Programming (XP)
umbrella term for various iterative and incremental software development
approaches.
Agile Software Development
collaboration between development and operations teams to enhance the entire software delivery process.
- Aims to automate the software delivery pipeline, e
DevOps
discipline that incorporates aspects of software engineering and applies them to infrastructure and operations problems.
Site Reliability Engineering (SRE)
Represents the customer, defines features, and prioritizes the product backlog.
Product Owner:
Facilitates the Scrum process, removes impediments, and ensures adherence to AGILE principles.
Scrum Master:
Cross-functional group responsible for delivering the product incrementally.
Development Team
Individuals or groups with an interest in the project’s outcome.
Stakeholders:
- Establishes a framework for software life cycle processes.
- Defines processes, activities, and tasks involved in software development and maintenance.
International Organization for Standardization (ISO) 12207:
essential part of the software development process, as it lays the foundation for the implementation of a software system.
Software design
subject to intellectual property laws, which are designed to protect the rights of the creators of original works, including software designs
Software design
needs, expectations, and desires of the end-users of a software system.
- serve as the foundation for the design and development of a software system
- define what the software should do and how it should perform.
User requirements
a critical phase in the software development life cycle (SDLC)
- involves studying and understanding the existing system, identifying problems or opportunities for improvement, and specifying the requirements for a new or enhanced system.
System analysis
Adopts the ISO 12207 standard for software life cycle processes.
IEEE 12207
Specifies the format for documenting software requirements.
IEEE 830
Describes the process for validating software products.
IEEE 1012
Defines the process for developing and acquiring software user documentation.
IEEE 1063:
Provides a framework for describing the architecture of a software-intensive system.
IEEE 1471:
form of intellectual property protection that applies to inventions
Patents
protects the expression of an idea, rather than the idea itself.
Copyright
confidential information that provides a competitive advantage to a business.
Trade secrets
