Q1. State TRUE or FALSE for each of the following statementbased on Figure Q1.highanalysis modelabstraction dimensionclass diagramsanalysis packagesCRC modelscollaboration diagramsdata flow diagramscontrol-flow diagramsprocessing narrativeslowdesign class realizationssubsystemscollaboration diagramsdesign moderefinements to:design class realizations.subsystemscollaboration diagramsarchitectureelementsuse-cases - textuse-case diagramsactivity diagramsswim lane diagramscollaboration diagramsstate diagramssequence diagramstechnical interfacedesignNavigation designGUI designinterfaceelementsclass diagramsanalysis packagesCRC modelscollaboration diagramsdata flow diagramscontrol-flow diagramsprocessing narratives.state diagramssequence diagramscomponent diagramsdesign classesactivity diagramssequence diagramsrefinements to:component diagramsdesign classesactivity diagramssequence diagramscomponent-levelelementsprocess dimensionFigure Q1 (Pressman, 2009)Requirements:constraintsinteroperabilitytargets andconfiguration(ii) Both data flow diagram and use case diagram are analysis models.design class realizations.subsystemscollaboration diagramscomponent diagramsdesign classesactivity diagramssequence diagramsdeployment diagramsdeployment-levelelements(i) A sequence diagram can describe the architecture elements of a software application.(iii) An activity diagram can describe the elements in a software's component in more detail.(iv) The higher the abstraction level, the more detailed the diagram will be.(v) Use case diagrams are not suitable for describing a software's interface elements.

Answered: Image /qna-images/answer/f582afeb-f08c-46a9-9e2b-c31ada818161.jpg

(i) A sequence diagram can describe the architecture elements of a software application. (ii) Both data flow diagram and use case diagram are analysis models. (iii) An activity diagram can describe the elements in a software's component in more detail. (iv) The higher the abstraction level, the more detailed the diagram will be. (v) Use case diagrams are not suitable for describing a software's interface elements.

(i) A sequence diagram can describe the architecture elements of a software application. (ii) Both data flow diagram and use case diagram are analysis models. (iii) An activity diagram can describe the elements in a software's component in more detail. (iv) The higher the abstraction level, the more detailed the diagram will be. (v) Use case diagrams are not suitable for describing a software's interface elements.

Database System Concepts

7th Edition

ISBN:9780078022159

Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Publisher:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Chapter1: Introduction

Section: Chapter Questions

Problem 1PE

See similar textbooks

Similar questions

Describe the significance of modeling the context of a system while it is being constructed. A software developer may commit two errors if they are unaware of the context of the system.
What objectives do formal methods seek to achieve, and how do they do so?At least four parameters must be supplied in order to enable the use of specifications in software development.What objectives do formal methods seek to achieve, and how do they do so? At least four parameters must be supplied in order to enable the use of specifications in software development.
What perspectives should be considered while modeling software systems?
Explain the following concepts relating them to software development and design with UML diagrams: Forward engineering and reverse engineering.
In the process of building models for software system architecture, which perspectives have to be taken into consideration?
In software development, how closely are cohesion and coupling related?
What are the benefits of using object-oriented analysis and design in system analysis and design?
Software development and modelling methodologies are distinct. Each individual's participation in the development process must be described in depth. You may mention a UML diagram in your text, correct?
Question 1: Below diagram shows various levels of software design as were discussed in the class. For a Library Management System you have to produce the following: Draw standard diagram to divide system into subsystems/ packages. Draw UML class diagram to divide the subsystems/ packages into classes. Draw an ERD of the system based on the class diagram Divide the classes into routines. Give the internal routine design.