How to collect a requirements! if you want to know about this matter, you will be read this slide.

1. Requirement Engineering
practical knowledge
gathering
BY
RAJU AHMED RONY

2. Domain Area
Garments

3. System Name
Embroidery Management System

4. Description of Domain Area
 Garment is a place where fabric is being converted into cloth.
 Most important sector for Bangladesh
 Working place for most poor people
 Profitable sector
 A sector which helps us to earn foreign currency

5. Scenario of the System
Clients provide a fixed design of a product.
Then the designer design the product through
ES WILCOM software what the clients
provide and translate to machine executable
code. After that, the designer load the final
design into the embroidery machine. Also
stabilize the fabric and place it in the
machine. At last the embroidery machine
embroidery the design on the fabric.

6. Elicitation Technique & SDLC
 Elicitation Technique: Questionaries & Interview
 SDLC Model: Scrum
Reason to use Scrum:
 Don’t completely understand the values, requirements
 Upgradeable & deliver a quality product
 It’s complicated project

7. Elicitation Technique Process
Questionaries:
1. We prepared some questions.
2. We asked the stakeholders some scripted questions.
Interviewing:
1. We asked some scripted and open-ended questions.
2. We also asked about their existing system and daily operation

8. Raw Requirements
 It will be data-based embroidery management system.
 Designer will be registered handled by admin.
 Operator will be registered handled by admin.
 Description of the design given by client will be handled by designer.

9. Existing System
 Get or create a digitized embroidery design file preferably
in some kind of editable format.
 Designer edit the design or combine with other designs
 Translate to machine executable code
 Load the final design file into the embroidery machine
 Stabilize the fabric and place it in the machine
 Start and monitor the embroidery machine

10. Stakeholders
Internal Stakeholders:
1. Developer
2. Owner
3. Admin
External stakeholders:
1. Clients
2. Workers
3. Bank
4. Operator
End User:
1. Operator
2. Admin of the system

11. Business
Process
Merchandiser receives
Primary order from
The client
Merchandiser gives necessary
instruction to the designer to
make a demo
If the client gives okay signal
then it goes to cutting section
Cutting section cut
the fabrics as it
necessary
The it goes to
embroidery section
Sewing section do
the work of sewing
Merchandiser and the
representatives check whether the
product quality is up to the mark or
not
After the clearance , the product is
ready for shipment to be handed
over to the client

12. Proposed System
 Log in system
Advantage:
 This should secure this system.
 No one forced to use the same provider.

13. Requirements
Functional Requirements Nonfunctional Requirement
1. Style Unlimited
2. Edit As Desired
3. Insert Max 3 materials at a time
4. Crop As Desired
5. Stitch Limited
Process requirement:
1. Environment: Windows 8.1, Linux
2. Language: Python, Java
3. Elicitation: Questionaries, Interview
4. SDLC: Scrum

14. Software Requirement Specification
SRS – ID SRS Name SRS
Description
SRS Type Priority
R - 001 Data based
embroidery
management system
This is a data based
embroidery
management system
of a garment
Functional
Requirement
High
R - 002 Designer registration
Designer registration
will handle by
admin.
Functional
Requirement
Medium
R - 003 Operator registration
The operator
registration will
handle by admin.
Functional
Requirement
Medium
R - 004 Design description
Design description
will handle and lead
by designer.
Functional
Requirement
Medium
R - 005
Embroidery on
Fabric
Loading the final
design machine
embroidery the design
Functional
Requirement
Medium

15. Use Case Diagram
Give Design
description
Draw design
Give
feedback
Confirmation
design
send design to
the machine
Operate the
machine
Confirm
registration
Communicate
with client
Shipment
Client
Operator
Designer
Admin

16. Admin Designer OperatorClient
<------------------------------
<------------------------------------
<----------------------------------
<-----------------------------
<-----------------------------------
1. Give design description
2. Give instructions
3. Demo design
4. Feedback design
5. Confirm design
6. Final design 7. Send design
8. Printed product
9. Send product
10. Shipment
Sequence Diagram

17. GUI (Graphical User interface)
User name
Password
LOG IN
ES-WILCOM

18. Experience
1. Acquired practical knowledge
2. Knew about software's (ES WILCOME, )
3. Saw the working process of the garment
4. Also knew about how professionals do their job.

19. Thanks to Everyone