Functional vs. Non-Functional Requirements in IEEE
How does the IEEE standard define functional and non-functional requirements, and why is this distinction important?Business Activity Modeling
How does Business Activity Modeling assist in system analysis, and provide an example.Logical Data Structure
What is a Logical Data Structure (LDS), and how is it used in system analysis?Business System Options
How are Business System Options (BSOs) developed and selected during system analysis?Logical vs. Physical Design
Differentiate between logical and physical design in the context of information system development.
Answers and Descriptions
Answer: IEEE defines functional requirements as specific system behaviors (e.g., process orders) and non-functional as quality attributes (e.g., scalability). This distinction ensures clear specification of capabilities and performance expectations.
Description: This question reinforces IEEE standards’ role in requirement clarity, enhancing analytical precision.Answer: Business Activity Modeling maps organizational processes to identify inefficiencies and requirements (e.g., modeling a retail checkout process to identify bottlenecks). It ensures system alignment with business goals.
Description: This question clarifies modeling’s role in aligning systems with business needs.Answer: An LDS represents data entities and relationships (e.g., customer-order relationship) without physical implementation details, used to define data requirements and ensure design consistency.
Description: This question deepens data modeling knowledge, critical for database design. The referenced image (LDS example) visually illustrates entity relationships.Answer: BSOs are developed by proposing alternative solutions based on requirements (e.g., in-house vs. cloud system). Selection considers cost, feasibility, and alignment with goals, using stakeholder consensus.
Description: This question encourages strategic thinking in evaluating options, a key analysis skill.Answer: Logical design defines system processes and data structures abstractly (e.g., DFDs). Physical design specifies hardware, software, and database implementation details (e.g., table structures).
Description: This question clarifies design phases, aiding in understanding the transition from abstract to concrete specifications.