UML Diagrams and Project Management Quiz

Requirements engineering is the process of defining, documenting, and maintaining requirements in the engineering design process.

Requirements describe the features and functionalities of the system, conveying the users' expectations from the software product.

The steps include Inception, Elicitation, Elaboration, and Negotiation.

<p>A prototype can give end-users a concrete impression of the system's capabilities.</p> Signup and view all the answers

<p>The Rational Unified Process is a generic process model that separates activities from phases.</p> Signup and view all the answers

<p>Requirements engineering is essential as it helps in defining, documenting, and maintaining the necessary features and functionalities of the system.</p> Signup and view all the answers

<p>Software Engineering is important because it provides a systematic approach to developing high-quality software that meets user requirements and is maintainable and scalable.</p> Signup and view all the answers

<p>Software myths refer to the common misconceptions or false beliefs about software development that can lead to unrealistic expectations or poor decision-making.</p> Signup and view all the answers

<p>A software process is a set of activities, tools, and techniques used to develop software products. It is important because it provides a structured approach to software development, ensuring consistency, quality, and predictability.</p> Signup and view all the answers

<p>Software perspective refers to the different viewpoints or approaches to software development, such as the process perspective, the product perspective, and the quality perspective. Specialized process models are tailored software development processes designed for specific domains or project types, such as the Agile model or the Spiral model.</p> Signup and view all the answers

<p>Software Engineering Practice refers to the application of software engineering principles, methods, and tools in real-world software development projects. It is significant because it ensures the delivery of high-quality software products that meet user requirements and industry standards.</p> Signup and view all the answers

<p>Software process models provide a structured framework for organizing and managing software development activities. They define the phases, tasks, and workflows involved in the software development life cycle, helping to ensure consistency, quality, and predictability in the software development process.</p> Signup and view all the answers

<p>Formal technical reviews can be effectively used during each phase of development to uncover certain errors.</p> Signup and view all the answers

<p>The main activities involved are communication, planning, modeling, construction, and deployment.</p> Signup and view all the answers

<p>A software process model is an abstract representation or description of a software engineering process from a particular perspective.</p> Signup and view all the answers

<p>A software engineering process defines the approach or framework for activities involved in building software, while software engineering also encompasses the technologies, technical methods, and automated tools used to populate the process.</p> Signup and view all the answers

<p>Examples of umbrella activities are project tracking and control, risk management, quality assurance, configuration management, and technical reviews.</p> Signup and view all the answers

<p>The five framework activities are communication, planning, modeling, construction, and deployment.</p> Signup and view all the answers

<p>Functional requirements depend on the system, the software, and the users, can be expressed at different levels of detail (user/system requirements), and it is desirable to have a complete and consistent set of functional requirements for a system.</p> Signup and view all the answers

<p>Non-functional requirements apply to the system as a whole, are more critical than individual functional requirements, and are more difficult to verify compared to functional requirements.</p> Signup and view all the answers

<p>The three main types of non-functional requirements mentioned are product requirements, organizational requirements, and external requirements.</p> Signup and view all the answers

<p>Metrics can be used to quantitatively specify and verify non-functional requirements, which are more difficult to verify compared to functional requirements.</p> Signup and view all the answers

<p>A complete set of functional requirements defines all the required system facilities, and a consistent set of functional requirements has no contradictions.</p> Signup and view all the answers

<p>Non-functional requirements apply to the system as a whole, while functional requirements are specific to individual system components or features.</p> Signup and view all the answers

<p>Not all standards tend to decrease the delivery time of software while maintaining its quality.</p> Signup and view all the answers

<p>Adding more manpower to a behind-schedule project further delays the project.</p> Signup and view all the answers

<p>The organization invariably suffers when it outsources the software project because it is incompetent in managing and controlling the project internally.</p> Signup and view all the answers

<p>Starting development with incomplete and ambiguous requirements often leads to software failure.</p> Signup and view all the answers

<p>Adding requirements at a later stage often requires repeating the entire development process.</p> Signup and view all the answers

<p>Software is flexible; hence software requirement changes can be added during any phase of the development process.</p> Signup and view all the answers