Mastering Scope Planning and Requirements Analysis in Project Management Quiz

Non-functional specifications are related to how a system performs rather than what it does. The correct answer, 'Must use cat 6 ethernet cables,' falls under this category as it specifies a requirement related to the network's performance capabilities. The incorrect answers provided are all functional specifications related to the hardware components of the system, making them invalid choices for non-functional specifications. Non-functional specifications focus on aspects such as reliability, scalability, performance, and security.

A non-functional specification focuses on how the system operates, rather than what the system does. Examples include performance requirements, security measures, or technology constraints.

Clients often have specific environmental requirements for the products or services they seek. In this case, a 'dust free environment' is a common requirement to ensure the proper functioning and longevity of the product. The incorrect answers of 'noisy environment', 'humid environment', and 'crowded environment' do not align with typical environmental requirements and can negatively impact the product performance.

The correct stages in identifying technical requirements involve understanding the system requirements, confirming constraints, and documenting the technical requirements. The incorrect answers do not align with the systematic approach to identifying technical requirements.

The technical requirements play a significant role in determining the design of a system or product, as the design must meet these technical needs in order to function properly.

Data flow diagrams (DFD) and entity relationship diagrams (ERD) are commonly used modelling techniques for database systems. Table creation diagrams (TCD), query optimization diagrams (QOD), and basic design diagrams (BDD) are not standard modelling techniques for databases.

A computer-based prototype is a simplified version of the proposed system that helps in visualizing and testing ideas before fully implementing them. System simulation involves modeling real-world systems digitally. The waterfall model is a sequential design process in which progress is seen as flowing steadily downwards. Agile development is an iterative approach where requirements and solutions evolve through collaboration between cross-functional teams.

RAD (rapid application development) typically involves collaborative and iterative development with short cycles, minimal planning, and a focus on user feedback. This approach is in contrast to developers working individually, long development cycles, and extensive documentation commonly found in traditional software development methodologies.

Data Flow Diagrams (DFDs) are primarily used for process modeling and visualizing the flow of data within a system, helping to understand how data is input, processed, and output.

A Level 0 DFD is the highest level in a DFD, showing the system as a whole with its main processes and interactions. Level 1 DFDs break down the system into more detailed subprocesses, Level 2 DFDs provide even more detail, and a Context Diagram shows the system interactions with external entities.

A Data Dictionary is a comprehensive text document that provides detailed definitions of data flows, processes, and data stores within an organization. It serves as a reference guide for understanding and managing the organization's data assets.

In addition to a 'problem statement', an 'opportunity statement' is another type of statement that can help identify the business issue in the requirements report. A risk statement focuses on potential hazards, a challenge statement highlights difficulties to overcome, and a goal statement outlines objectives to achieve.

The identified business needs should be in line with the overarching vision and strategic mission of the business in order to ensure synergy and direction in operations.

When documenting technical requirements, it is important to identify key stakeholders within the business who will be impacted by the requirements, as well as stakeholders external to the business who may have valuable input or requirements.

There is no single standard template for writing a requirements report as different industries and organizations may have their own preferred formats and structures.

Interface requirements deal with how different components/systems communicate with each other, while process requirements outline the specific actions or steps necessary for a system to achieve its intended functionality.

Once technical requirements are identified, the next step is to develop a solution that meets those requirements.

Automation of repetitive stable tasks is indeed a growing focus in the IT industry as organizations seek to improve efficiency and reduce human error through the use of technology.

Contractual and service level agreements are crucial components of managing the relationships and performance of suppliers and partners in the supply chain, making supply chain management the correct answer.

Interfacing standards like EDI (Electronic Data Interchange) and XML (eXtensible Markup Language) are commonly used in various industries for exchanging information between different systems. ASCII and UTF-8 are character encoding standards, HTTP and FTP are protocols for transferring files over the internet, and SQL and HTML are languages used for querying databases and creating web pages respectively, but they are not primarily used for interfacing standards.

Electronic Data Interchange (EDI) is a system for exchanging business documents electronically in a standard format between trading partners. The correct answer provided indicates a lack of information on an example of EDI usage, while the incorrect answers do not relate to the concept of EDI.

B2C stands for Business to Consumer, not Business to Commerce. Therefore, the statement is true as getting credit card information from a bank involves a business (bank) providing services directly to consumers.

The correct answer focuses on security measures, access control, and user roles which are key considerations for designing user interfaces for internal users. The incorrect answers are not directly related to user interface design considerations for internal users.

The correct answer options all relate to interfaces designed for internal users within an organization, while the incorrect answers do not specifically target internal user functions.