Case Study: CD Store
Case Study: CD Store
Case Study: CD Store
CASE STUDY
Of
Software Engineering
Topic:
CD Store
Management
z
26 Anand
Gawade
27 Pranjal Gharat
28 Dipesh Gobji
29 Vishal Gorule
30 Ashish Gupta
z
Problem description:
Problem Analysis:
The CD store offers many CDs.
The manager offers customer to take CD/DVD on rent as well as
customer can buy the CD/DVD.
CDs are arranged in particular pattern.
Manager takes the details of customer who wants the CD on rent
and entries are done in the register.
Now CD store wants to automate this system.
So that there are two things involved –
1. Understanding the problem
2. Producing requirement document[SRS]
Customer comes to the CD store and asks for the required CD.
Manager checks his register and provide information that whether
that CD is available or not.
Manager registers his name and address and take deposit from
customer.
He gives the receipt with submission date, which is normally of
maximum two days.
If customer wants to buy the CD he can buy the CD by paying
desired amount.
Manager enters the CD details in his register, where he can found
which CD is taken away and which CD is in store.
Every CD can be used only for five times after that CD is send to
scratch, so manager is checks the CD details to find out which CD
is used for how many times.
z
DD
Supplies file=[date+[ CD_name + quantity+cost]*]*
Order files: [cost+[CD_name*CD_type* CD_number]*]*
Status=Avalibale |Not availbale
Receipt= [due_date+issue_date+cost]*
CD register= [ issue_date+[CD_name*CD_type*CD*number]+
[quantity]+[counte]*]*
SRS
z
Introduction:
Purpose:
The purpose of document is to describe the external
requirements for a CD store management system.
Scope:
It describes the requirements of the system. It is meant for
use by the developer and will be the basis for validating the final
delivered system, any change made to the requirements in the
future will have to go through a formal change approval proven.
The developer is responsible for asking for classifications. Where
necessary and will not make any attentions without permission of
the clients.
General Description
z
Specific requirements
z
I/P1:
Manager enters the CD’s Characteristics like Move name,
type of CD, CD number if available etc.
I/P2:
Manager enters customer’s details like name, address,
contact no etc.
I/P3:
Manager enters CD details and current date when CD is
taken by customer.
O/P1:
CD name, rack no, number indicating how much time CD is
used.
Or
Error message
CD is not available order now
O/P2:
Receipt with purchase date, returning date, amount.
O/P3:
z
Functional Requirements:
z
Design Constraints:
Software constraints– Only for Windows OS
Hardware constraints- 36 MB RAM
Acceptance criteria:
Before accepting, developer must demonstrate that the
system works on the data for last month.
The developer will have to show through test cases that all
conditions are satisfied.
• Automate updating.
Supplier file
CDs register File
check
Check
Process counter
supplies Supplies
CDs
scratch
supplies
check
order
supplier
supplies Manager
CDs
Order file
receipt
Customer
to CD register
file
z
Supplier file=[date+[CD_no*CD_name+cost]*]*
CD register file=[issue date+[CD_no*CD_name*CD_type]
+cost+counter]*
Order file=[CD_name*CD_type*CD_no+cost]