ITEC 306 Applications Development and Requirements Engineering

These flashcards cover key concepts in applications development and requirements engineering essential for understanding the course material.

Applications Development

The process of creating software to solve problems through systematic steps: Planning, Designing, Coding, Testing and Deployment, and Maintaining.

System Software

Software that manages hardware and provides a platform, such as Windows and Linux.

Application Software

Software that performs user tasks, such as Facebook and Microsoft Excel.

Middleware

Software that connects different applications or systems, like database middleware and web servers.

Embedded Software

Software built into devices to control specific functions, such as in ATMs and washing machines.

Generic Products

Ready-made software sold to many users, like Microsoft Office and Adobe Photoshop.

Customized Products

Software built for a specific client's needs, like company systems or school portals.

Software Development Life Cycle (SDLC)

A process consisting of Planning, Analysis, Design, Development, Testing & Evaluation, Deployment, and Maintenance.

Waterfall Model

A software development model that is linear and sequential, ideal for well-defined projects.

Agile Model

A software development model that is iterative and flexible, often used in startups and SaaS.

Requirements Engineering

The process of defining, managing, and testing requirements to ensure the system meets user needs.

High-Level Requirement

A broad description of the system without detailed specifics.

Detailed Requirement

A specific description of how the system functions, including steps and inputs.

Functional Requirements

Requirements that define what the system should do, including services and reactions.

Non-Functional Requirements

Requirements that define constraints such as performance, timing, and standards.

Validation in Requirements Engineering

The process of checking that requirements accurately reflect what the customer wants.

Stakeholders in Systems

Anyone affected by the system with a legitimate interest, including end users, system managers, and owners.

Metrics for Non-Functional Requirements

Criteria such as speed, size, ease of use, reliability, robustness, and portability used to specify requirements.

Elicitation

The process of gathering requirements from stakeholders.

Quality Function Deployment (QFD)

A technique that translates customer needs into technical software requirements.

Design Concepts in Software Development

Frameworks guiding software design, including abstraction, refinement, modularity, and data structures.

Design Quality Attributes (FURPS)

Attributes used to evaluate design quality: Functionality, Usability, Reliability, Performance, and Supportability.