Software Fundamentals and Components

True (A)

Software specification, software development, software validation, software evolution

<p>codes</p> Signup and view all the answers

<p>Application Software = Software designed for end-users to perform tasks System Software = Software that manages and operates computer hardware Development Software = Software used to create other software Utility Software = Software that performs maintenance tasks</p> Signup and view all the answers

<p>Spiral Model (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>Testing at each stage</p> Signup and view all the answers

<p>Prototyping</p> Signup and view all the answers

<p>Waterfall Model = Sequential stages with strict progression Agile = Iterative and collaborative development SCRUM = Development in sprints Kanban = Visual flow management of tasks</p> Signup and view all the answers

<p>Agile (D)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>Agile</p> Signup and view all the answers

<p>Customer satisfaction (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>To provide a small software requirement specification for future sprints.</p> Signup and view all the answers

<p>velocity</p> Signup and view all the answers

<p>Business Requirements = Describes business objectives and goals User Requirements = What users must be able to do with the product Functional Requirements = A list of criteria without additional definitions Quality Attributes = Attributes that emerge from business rules</p> Signup and view all the answers

<p>Software requirement specifications are needed. (C)</p> Signup and view all the answers

<p>Interviews, surveys, or user stories.</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

A collection of codes designed to perform specific tasks and fulfill requirements.

The application of scientific and practical knowledge to create, design, implement, and maintain software.

Manuals, operating procedures, and other written materials that describe how to use software.

Process of designing the software's architecture, layout, and structure; it is a fundamental initial step of software development.

A structured process for creating software, with different models defining stages and procedures.

A simple SDLC model where each stage must be completed before moving to the next.

SDLC model involving creating prototypes, refining them, and then filling them with functionality.

SDLC model for large, expensive projects, with repeated stages of risk analysis and development.

SDLC model connecting development stages to testing, emphasizing parallel verification and validation.

Simplest SDLC model; little planning, many resources thrown at the problem, used for small-scale projects, not recommended for large-scale projects..

Iterative and incremental SDLC model focused on collaboration and adaptability, often used for projects with short timelines and changing requirements.

An Agile framework that uses sprints (short development cycles) for iterative software development.

Visual project management system to track tasks through different stages, primarily used for ongoing production work.

"Extreme Programming" is a software development approach prioritizing customer satisfaction by encouraging developers to embrace and implement customer feedback changes.

Scrum involves customer involvement throughout the development process, allowing for flexible requirements; Waterfall requires initial, comprehensive specifications, limiting changes later on.

Story points estimate the effort needed to implement user stories; velocity tracks the average work completed per sprint; and the sprint backlog provides a short-term view of planned work.

A good requirement has to be unambiguous, complete, verifiable, consistent, achievable, stable, and traceable for successful software development.

Business requirements define organizational objectives; user requirements specify user actions; functional requirements detail software functions; business rules and constraints establish limits; and quality attributes define desired software characteristics.

Methods to gather, understand, and document user needs for software creating a comprehensive software specification.

A comprehensive document describing the intended purpose and environment for software, specifying what and how the software will work.

IDEF models are a set of modeling methods used to create high-level conceptual and logical views of software systems. These models are used to visualize software systems in a structured fashion.