[go: up one dir, main page]
Scribd
Upload
44 views2 pages

Software Engineering Unit-Ii Two Marks Questions: 1. Define Requirements Analysis

Uploaded by

Jyo Reddy

Requirements analysis is the process of determining user expectations for a new or modified product, known as requirements. Requirements elicitation collects requirements from users and stakeholders. Software requirements should be clear, correct, consistent, coherent, comprehensible, modifiable, verifiable, prioritized, unambiguous, traceable, and from a credible source. Software metrics provide measures for aspects of the software process and product, while process metrics measure methods, tools, standards, and performance in SDLC phases. Actors represent roles in a system, use cases represent functions, and verification and validation check that a system meets specifications and fulfills its purpose.

Copyright:

© All Rights Reserved
Download as DOCX, PDF, TXT or read online from Scribd
Download as docx, pdf, or txt

Software Engineering Unit-Ii Two Marks Questions: 1. Define Requirements Analysis

Uploaded by

Jyo Reddy
44 views2 pages
Requirements analysis is the process of determining user expectations for a new or modified product, known as requirements. Requirements elicitation collects requirements from users and stakeholders. Software requirements should be clear, correct, consistent, coherent, comprehensible, modifiable, verifiable, prioritized, unambiguous, traceable, and from a credible source. Software metrics provide measures for aspects of the software process and product, while process metrics measure methods, tools, standards, and performance in SDLC phases. Actors represent roles in a system, use cases represent functions, and verification and validation check that a system meets specifications and fulfills its purpose.

Original Title

8.2 SE__2_MARKS_UNIT_II

Copyright

© © All Rights Reserved

Available Formats

DOCX, PDF, TXT or read online from Scribd

Did you find this document useful?

Is this content inappropriate?

Requirements analysis is the process of determining user expectations for a new or modified product, known as requirements. Requirements elicitation collects requirements from users and stakeholders. Software requirements should be clear, correct, consistent, coherent, comprehensible, modifiable, verifiable, prioritized, unambiguous, traceable, and from a credible source. Software metrics provide measures for aspects of the software process and product, while process metrics measure methods, tools, standards, and performance in SDLC phases. Actors represent roles in a system, use cases represent functions, and verification and validation check that a system meets specifications and fulfills its purpose.

Copyright:

© All Rights Reserved
Download as DOCX, PDF, TXT or read online from Scribd
Download as docx, pdf, or txt
44 views2 pages

Software Engineering Unit-Ii Two Marks Questions: 1. Define Requirements Analysis

Uploaded by

Jyo Reddy
Requirements analysis is the process of determining user expectations for a new or modified product, known as requirements. Requirements elicitation collects requirements from users and stakeholders. Software requirements should be clear, correct, consistent, coherent, comprehensible, modifiable, verifiable, prioritized, unambiguous, traceable, and from a credible source. Software metrics provide measures for aspects of the software process and product, while process metrics measure methods, tools, standards, and performance in SDLC phases. Actors represent roles in a system, use cases represent functions, and verification and validation check that a system meets specifications and fulfills its purpose.

Copyright:

© All Rights Reserved
Download as DOCX, PDF, TXT or read online from Scribd
Download as docx, pdf, or txt
You are on page 1/ 2

SOFTWARE ENGINEERING UNIT-II TWO MARKS QUESTIONS

1. Define Requirements analysis.
Ans:-Requirements analysis, also called requirements engineering, is the process of determining user
expectations for a new or modified product. These features, called requirements, must be quantifiable,
relevant and detailed. In software engineering, such requirements are often called functional
specifications.

2. What is requirements elicitation?
Ans:-requirements elicitation is the practice of collecting the requirements of a system from users,
customers and other stakeholders. The practice is also sometimes referred to as "requirement gathering".

3. List Software Requirements Characteristics.


o Clear
o Correct
o Consistent
o Coherent
o Comprehensible
o Modifiable
o Verifiable
o Prioritized
o Unambiguous
o Traceable
o Credible source
4. Define software metrics.
Ans: Software Metrics provide measures for various aspects of software process and software product.

5. Define process metrics.


Ans: Process Metrics - In various phases of SDLC, the methods and tools used, the company standards
and the performance of development are software process metrics.

6. Define Actor.
Ans: Actor in a use case diagram is any entity that performs a role in one given system. This could be a
person, organization or an external system and usually drawn like skeleton .

7. Define UseCase.
Ans: A use case represents a function or an action within the system. Its drawn as an oval and named
with the function.

8. Why verification and validation  is used?


Ans: Verification and validation  is the process of checking that a software system meets specifications
and that it fulfills its intended purpose.

9. What is data modeling?


Ans: Data modeling in software engineering is the process of creating a data model for an information
system by applying formal data modeling techniques.
10. What is class diagram?
Ans: class diagram is basically a graphical representation of the static view of the system and represents
different aspects of the application. So a collection of class diagrams represent the whole system.
11. What are software requirements?
Ans: Software requirements are functional description of proposed software system. Requirements are
assumed to be the description of target system, its functionalities and features. Requirements convey the
expectations of users from the system.

12. What are functional requirements?


Ans: Functional requirements are functional features and specifications expected by users from the
proposed software product.

13. What are non-functional requirements?


Ans: Non-functional requirements are implicit and are related to security, performance, look and feel of
user interface, interoperability, cost etc.

14. What is the difference between function oriented and object oriented design?
Ans: Function-oriented design is comprised of many smaller sub-systems known as functions. Each
function is capable of performing significant task in the system. Object oriented design works around the
real world objects (entities), their classes (categories) and methods operating on objects (functions).

15. Briefly define top-down and bottom-up design model.


Ans: Top-down model starts with generalized view of system and decomposes it to more specific ones;
whereas bottom-up model starts with most specific and basic components first and keeps composing the
components to get higher level of abstraction.

You might also like