1.
Submitted To: Md. Mijanur Rahman
Submitted By: Group Creativity

2.
Group Name:- Creativity
• Talha Ahmed: 152-35-1138
• Khalid Hasan: 152-35-1169
• Himel Mahmud: 152-35-1214
• Zarrin Tasnim: 152-35-1234
• Mayen Uddin: 152-35-1282

3.
DOMAIN AREA: Ready Made Garments

4.
SYSTEM NAME
Garments Account System

5.
Ready-Made Garments
Ready-Made Garments (RMG) industry has been Bangladesh’s key export
industry and a main source of foreign exchange for the last 25 years. The
sector contributes significantly to the GDP providing employment to around
4.2 million Bangladeshis, mainly women.
USA is the largest importer of Bangladeshi RMG products, followed by
Germany, UK, France and other E.U. countries.

6.
Company Name: Onupom Fashion Wears Ltd.
 Mostly manufacture Pants and Jackets.
 Do not use any software.
 Company take orders from mostly international companies.

7.
Scenario
 This system is based on account management system of a garments
factory.
 Employees should be registered along with accountants and admin.
 Accountants will handle the salaries of employees, expenditures and
profits.
 Admin will supervise the overall system.

8.
Existing System

9.
Business Process

10.
Elicitation Technique: Interviewing
 Since with this system different departments are involved, we have to talk to everyone about
what they need.
 All the requirements must collaborate with each other that is why it has to be structured
interview.
SDLC: Prototyping
Reasons:
• Since the company never used any software before, so they could not give all the
requirements.
• A prototype will help them understand the theme of the software.
It will help them to understand what else should be added that would to help them.

11.
Raw Requirements
 It will be an account management system.
 System will be offline.
 Must have multiple users.
 Every user account must be according to their job position.
 Employees will be registered by Admin.
 Employees can edit their personal information.
 Database will keep record of all the information.
 Salaries will be handled by the Accountant.
 Database will keep track of employees’ attendance and overtime.
 Admin will handle production order information.
 Data will keep record of order history and details, expense and profits.

12.
Sequence Diagram

13.
Use-Case Diagram

14.
System Requirement Specification (SRS)

15.
Functional:
 User id
 Password
 Data entry
 Salary
Information
 Bill email
 Salary check
Non functional:
•Email attachments
•Salary amount
•Number of system users
•Type of information entered in the database
•Way of bill payment
Process:
•C++
•Linux
•Offline

16.
Stakeholder
Internal
 Admin
 Employees
 Accountant
 Manager
 Chairman
External
• Software Developer
• Security Staff
• Buyers
• BGMEA
• Import/Export Agencies
• Bank
• Product Suppliers

17.
Proposed System
Manager account system (Offline version)
Features:
 Information can be entered in database.
 Can be used be multiple users
 Each user has unique accounts that allows them to do specific works
 System specially made of accounts department
 Can be associated with bank
 Provides emails of bills

18.
Graphical User Interface

19.
Experience:
Bad:
 It was hard to make them feel comfortable to discuss with us about their system.
 Since they did not think about using software before, it was hard to figure out their
requirements.
Good:
 Learned how in real life to apply our work.
 Learned how to communicate with customers.
 Learned how to bring out requirements when the customer does not know what they
want.
 Learned how the field of ready made garments works.