1. Black hole ?

=> DFD ERROR: input but not output. Eg. Creating account in bank

2. Grey hole?
=> DFD ERROR: insuficent input for output.eg. generate employee bank
statement

3. miracle ?
=> DFD ERROR: output without input? Eg. Freeze account number

4. requirements engineering process ?

• eliciation
• specification
• varification and validation
• management

5. Requiremnts eliciation?
. Requirement gathering process using diffents techniques like (survay.
Quationaris, group survary)

6. Requirements specifications?
. systematic documentation of the requirements. A Requirement Specification is a
collection of the set of all requirements that are to be imposed on the design and
verification of the product. The specification also contains other related
information necessary for the design, verification, and maintenance of the product.
DFD, ER diagrams

7. verification ?
. it is process of ensure that we are developed right product or not.
Are we building the product right ?

8. verification ?
. checking developing product is right product.
Are we building right product ?

9. verification techniques?
Inspection
review
walkthrough
10. Validation technique?
Balck box testing
white box testing
unit testing

11. Functional Requirements: These are the requirements that the end user
specifically demands as basic facilities that the system should offer. All these
functionalities need to be necessarily incorporated into the system as a part of the
contract. These are represented or stated in the form of input to be given to the
system, the operation performed and the output expected.
Example: Authentication, user information

12. Non-functional requirements: These are basically the quality constraints that

the system must satisfy according to the project contract. The priority or extent to
which these factors are implemented varies from one project to other. They are also
called non-behavioral requirements.
They basically deal with issues like:
• Portability
• Security
• Maintainability
• Reliability
• Scalability
• Performance
• Reusability
• Flexibility
13. Domain requirements: Domain requirements are the requirements which are
characteristic of a particular category or domain of projects. The basic functions
that a system of a specific domain must necessarily exhibit come under this
category.
Example: we in acconting software we need kowledge of debit credit,
gernalvauchar etc.

14. PDCA?
. plan-do-check-act.
Requirements change control process also called project planning tools .
Steps:
• plan : make plan
• do : perform
• check : monitor
• act : impove, otherwise agin do cycle

15. process modeling?

A techique of graphically representating process that we use to capture, maniulate ,
store and distribute data. Example dfd, er.

16. requirement analysis?

requirements Analysis is the process of defining the expectations of the users for an
application that is to be built or modified. It involves all the tasks that are
conducted to identify the needs of different stakeholders. Therefore requirements
analysis means to analyze, document, validate and manage software or system
requirements.
High-quality requirements are documented, actionable, measurable, testable,
traceable, helps to identify business opportunities, and are defined to a facilitate
system design.

17. UML Diagram

A UML diagram is a diagram based on the UML (Unified Modeling Language) with the
purpose of visually representing a system along with its main actors, roles, actions,
artifacts or classes, in order to better understand, alter, maintain, or document information
about the system.
List of UML diagram
 Structure Diagrams. Class Diagram. Component Diagram. Deployment Diagram.
Object Diagram. Package Diagram. Profile Diagram. Composite Structure
Diagram.
 Behavioral Diagrams. Use Case Diagram. Activity Diagram. State Machine
Diagram. Sequence Diagram. Communication Diagram. Interaction Overview
Diagram.
18. Difference between use case and class diagram: