se unit ii 2 marks

8/6/2019 SE Unit II 2 Marks

1/8


2/8

Problems

It can be undocumented.

Changes made during the software development proceed may degradethe system structure.

Sometimes organizational quality standard may not be strictly applied.

(Or)

Compare Evolutionary prototyping and Throw away prototyping

Evolutionary prototyping Throw away prototyping

The principle objective of Evolutionary

prototyping model is to deliver the working

system to the end-user.

The principle objective of Throw away

prototyping model is to validate or derive

the system requirements.

The process of development starts with

well understood requirements.

The process of development starts with

poorly understood requirements.

It must be developed for the systems where

the specification cannot be developed inadvance.

The Throw away prototype is developed to

reduce the requirements risks

6. What are the advantages of evolutionary prototyping?

a. Fast delivery of the working system.

b. User is involved while developing the system.

c. More useful system can be delivered.

d. Specification, design and implementation work in co-coordinated manner.

7. What are the various Rapid prototyping techniques?

a. Dynamic high level language development.

b. Database programming.c. Component and application assembly.

8. What is the use of User Interface prototyping?

This prototyping is used to pre-specify the look and feel of user interface

in an effective way.

9. What are the characteristics of SRS?

a. Correct The SRS should be made up to date when appropriaterequirements are identified.

b. Unambiguous When the requirements are correctly understood then only

it is possible to write unambiguous software.c. Complete To make SRS complete, it should be specified what a software

designer wants to create software.

d. Consistent It should be consistent with reference to the functionalities

identified.

e. Specific The requirements should be mentioned specifically.

f. Traceable What is the need for mentioned requirement? This should be

correctly identified.

2


3/8

10. What are the objectives of Analysis modeling?

a. To describe what the customer requires.

b. To establish a basis for the creation of software design.

c. To devise a set of valid requirements after which the software can be built.

11. Compare functional and behavioral modeling

Functional modeling Behavioral modeling

The Functional model depicts all the

essential functionalities of the system.

The Behavioral modeling represents how

system behaves.

The Functional model is represented by

data flow and control flow diagrams.

The Behavioral model is represented by

state chart diagrams.

The Functional diagram gives detailed

scenario of system which has to be

developed.

The Behavioral model gives the abstract

repre

12. What is data modeling?Data modeling is the basic step in the analysis modeling. In data modeling

the data objects are examined independently of processing. The data model

represents how data are related with one another.

13. What is a data object?

Data object is a collection of attributes that act as an aspect, characteristic,

quality, or descriptor of the object.

14. What are attributes?

Attributes are the one, which defines the properties of data object.

15. What is cardinality in data modeling?

Cardinality in data modeling, cardinality specifies how the number of

occurrences of one object is related to the number of occurrences of anotherobject.

16. What does modality in data modeling indicates?

Modality indicates whether or not a particular data object must participate

in the relationship.

17. What is ERD?

Entity Relationship Diagram is the graphical representation of the objectrelationship pair. It is mainly used in database applications.

18. What is DFD?

Data Flow Diagram is a graphical representation that depicts the information flow

and the transforms that are applied on the data as it moves from input to output. Thebasic form of a DFD, also known as a data flow graph or a bubble chart.

3


4/8

19. What does Level0 DFD represent?

Level0 DFD is called as fundamental system model or context

model. In the context model the entire software system is represented by a singlebubble with input and output indicated by incoming and outgoing arrows.

20. What is a state transition diagram?State transition diagram is basically a collection of states and events. The

events cause the system to change its state. It also represents what actions are to be

taken on the occurrence of particular event.

21. Define Data Dictionary.

The data dictionary can be defined as an organized collection of all the

data elements of the system with precise and rigorous definitions so that user andsystem analyst will have a common understanding of inputs, outputs, components

of stores and intermediate calculations.

21. State the four generic activities of requirement engineering?Requirement engineering involves four generic activities such as:

1. Feasibility study2. Requirements Elicitation and Analysis

3. Requirements specification and documentation

4. Requirements validation

22. What are the purposes of building software prototypes?

1. To develop a system for user interface.

2. To develop a system to validate requirements.3. To demonstrate application feasibility.

4. To avoid risk on assumption based building and

5. More clear study on application.

23. What are the different steps that described the requirement engineeringprocess?

The different steps that described the requirement engineering process are,

Requirements Elicitation

Requirements analysis and negotiation

Requirements specification

System modeling

Requirements validation

Requirements management

24. What is Requirements Elicitation?

Requirements Elicitation involves asking the customer, the users, and other whatthe objective for the system or product are, what is to be accomplished, how the

system or product fits into the needs of the business, and finally, how the system or

product is to be used on a day-to-day basis.

4


5/8

25. WhyRequirements Elicitation process is difficult?The following are the reasons,

Problems of scope

Problems of understanding

Problems of volatility

26. What types of models do we create during requirement analysis?

Functional model

Data model

Behavioral model

27. What is usage of models?

To understand the system

Serves as a focal point of review

Foundation for design

28. What does functional model stands for?

Functional model shows the series of transformation that are made on data orinformation on moving through software. It describes how the system functions to

produce the required output for the set of input supplied to it.

Functional model involves Data Flow Diagrams.

29.What does Behavioral model stands for?A model that depicts softwares reaction to some external events is known as

behavioral modeling. The State Transition Diagram (STD) represents the behavior of asystem by depicting its states and events that cause the system to change state.

30. What guidelines should we follow while analyzing the requirements?

Understand before creating a analysis model.

Develop a prototype to understand the system.

Record the reasons for every requirement

Rank the requirements

Eliminate ambiguity

31. What is meant by feasibility study?A feasibility study is a short focused study which reports the recommendation

whether or not it is worth carrying system development process.

Feasibility study that checks, Whether the system contributes to the organizational objectives.

If the system can be engineered using current technology and within

budget.

32. What are the different types of requirements?

User requirements

System requirements

5


6/8

Interface requirements

33. What are the various kinds of requirement documents?

User requirements definition document

System requirements specification document

34. List the classification of software system requirements.(Or)

What are the board categories of system requirements?

Software system requirements are often classified as follows

Functional Requirements

Non- Functional Requirements

Domain Requirements

35. What are Functional Requirements? (Or) Define: Functional Requirements.

Functional Requirements are statements of services the system should provide

how the system should react to particular input and how the system should behavein particular situation.

Functional Requirements:

Describe functionality or system services.

Depend on the type of software, expected users and the type of the system where

the software is used.

36. What are Non-Functional Requirements? (Or) Define: Non-Functional

Requirements.

Non-Functional Requirements are constraints on the services or functions

offered by the system such as timing constraints, constraints on the development

process, standards, etcNon-Functional Requirements:

Define system properties and constraints

eg: reliability, response time and storage requirements

Non-Functional Requirements may be more critical than FunctionalRequirements.

37. Classify Non-Functional Requirements.Non-Functional Requirements can be classified based on how they are derived as:

Product Requirements

Organizational Requirements

External Requirements

38. What are user requirements?

Users Requirements should describe Functional and Non-Functional requirements so that they are understandable by system users who dont have

detailed technical knowledge.

Users Requirements are defined using natural language, tables and diagrams.

6


7/8

39. What are system requirements?System requirements are,

More detailed specification of userrequirements.

Serve as a basis for designing the system.

May be used as part of the system contract.

40. List the advantages ofEvolutionary prototyping

Advantages

Fast delivery of the working system.

User is involved while developing the system.

More useful system can be delivered.

Specification, design and implementation work is co-ordinated manner.

12 MARKS QUESTIONS

1. Explain the Functional and Non-Functional requirements in detail.

2. Explain the concepts of Requirement Engineering process.

3. Draw a detailed data flow diagram (DFD) for the library information system.

4. Describe various prototyping techniques.

(Or)

Describe the prototype development process in detail with neat sketch.

(Or)

Explain the prototyping approaches in detail with their applications.5. Explain the software requirement specification (SRS) for a typical software project

6. Write short notes on data modeling.

7. Explain the various requirement elicitation techniques.

8. Describe analysis model and its elements in detail.

9. Describe behavioral model in detail.

10. Design the behavioral model for micro oven .

11. Illustrate the structure of data dictionary with suitable example.

(Or)Write short notes on data dictionary.

12. Design an state transitions diagram(STD) for an automated washing machine.

13. Create a data dictionary for student profile.

14. Write short notes on FAST.

15. Explain the Entity relationship diagram(ERD) with some suitable example.

7


8/8

16. Describe how software requirements are documented? State the importance of documentation.

17. Draw a level-1 DFD for safe home security system. Explain the flow between the processes.

18. Draw a basic structure of analysis model and explain each entity in detail.

8

se unit ii 2 marks

Documents