Inventory Management System for Ariser Pharma

Software Requirements
Specification
for
Inventory System for

Ariser Pharma
Version 1.0
Prepared by
Zofishan Khalid FA12-BSE-001
Anoosha Zafar FA12-BSE-028
Khadija Nawab FA12-BSE-002
Kaleem Ullah FA12-BSE-008
Shakeel Ahmed FA12-BSE-029
Supervised by
Sir Atique Zafar
Department of Computer Science,
CIIT, Islamabad.
19th May, 2014

SoftwareRequirementsSpecificationfor<Project> Pageii
TableofContents
1. Introduction..............................................................................................................................1
1.1 Purpose.......................................................................................................................................1
1.2 Scope..........................................................................................................................................1
1.3 Definitions,AcronymsandAbbreviations.................................................................................2
1.4 References..................................................................................................................................2
1.5 Overview....................................................................................................................................2
2. OverallDescription..................................................................................................................2
3. UseCase(s)................................................................................................................................3
3.1 UseCaseList..............................................................................................................................3
3.2 UseCaseDiagram......................................................................................................................4
3.3 UseCaseDescription.................................................................................................................4
3.3.1Login.......................................................................................................................................4
3.3.2Logout.....................................................................................................................................5
3.3.3RegisterEmployee..................................................................................................................6
3.3.4RegisterProduct......................................................................................................................6
3.3.5SearchRecord.........................................................................................................................7
3.3.6ManageRecord.......................................................................................................................8
3.3.7GenerateReport......................................................................................................................9
3.3.8RegisterTransaction...............................................................................................................9
3.3.9InvoiceReciept...................................................................................................................10
4. SpecificRequirements...........................................................................................................11
4.1 Functionality.............................................................................................................................11
4.2 Usability...................................................................................................................................20
4.3 Reliability.................................................................................................................................20
4.4 Performance.............................................................................................................................20
4.5 Supportability...........................................................................................................................20
4.6 Security....................................................................................................................................21
4.7 DesignConstraints...................................................................................................................21
4.8 Interfaces..................................................................................................................................22
4.8.1UserInterface........................................................................................................................22
4.8.2HardwareInterface................................................................................................................23
4.8.3CommunicationInterface......................................................................................................23
SoftwareRequirementsSpecificationfor<Project> Page1
IEEE Software Requirements

Specification Template
1. Introduction
1.1 Purpose
This application has been designed to facilitate the Inventory System for Ariser Pharma to add the
information digitally that provides efficiency in the working of the shop. Moreover, it will provide
easy maintenance, less consumption of time, cost effectiveness and ease of work load for medical
shop employees. The main feature includes invoicing; inventory and stock control will help to track all the
profits, and loss of the shop.
Moreover, our system facilitates the users by following ways:
Improve efficiency, productivity

Cost effective solutions
Graphical User Interface.
Secure access
1.2 Scope
The offline way of billing and invoicing is meant for the conventional medical stores having a
stock too large to handle manually and a larger number of customers per day .The larger the
amount of customers buying the medicines, the larger is the number of bills and invoices created.
Making the hand written bills and saving them by having the carbon copy of them is a very
tedious and physically exhaustive. Also to keep the record of the medicines sold per day and
calculations of bills take too much time and increase mental stress.
Keeping in mind these problems stakeholders wanted to implement all those works digitally. So
we are going to design a desktop application. Our desktop application will enable employees to
digitize the information of their customers. The system will have several functionalities like add,
delete, view, search, update etc. thus lowers the stationery cost. It has certain other benefits such
as it will provide us with the security of customers data, less time will be consumed in accessing
a specific customers information, easy maintenance of the system, enhanced efficiency due to its
simple interface, reliability of data due to the implementation of information security techniques
and the availability of data 24/7.
1.3Definitions,AcronymsandAbbreviations
Abbreviations Meaning
CEO ChiefExecutiveOffice
NIC NationalIdentityCard
IEEE Institute of Electrical and Electronics Engineers
GUI Graphical User Interface
HDD Hard Disk Drive
TB Tera Byte
RAM Random-Access Memory
LAN Local Area Network
Visual C# Visual C sharp Language
SQL Structured Query Language
1.4 References
Sommerville. Software Engineering (6th Edition). Addison Wesley, 2000.

Software Requirements Specification Inventory Management and Work Order System,
December 23, 2002, Transcore.
www.abbreviations.com
www.docstoc.com
http://ciscoforall.com/detailednotesoncomputernetworksandtheirtypes/
1.5 Overview
An inventory management system is an automated system that keeps track of inventory on a regular
basis. The system ensures that items marked for inventory and distribution are accounted for and that
stock levels, quantities and costs are reasonable when requisitions for inventory are placed through
the system by manual re-ordering.
The SRS contains the overall description of the project including overall system functionalities, use
cases, functional and non functional requirements of the system ,different system constraints,
dependencies and the user interface.
2. OverallDescription
There are many types of inventory system but our system is very simple inventory system which
automate a shop and will have store all information in database and some specific functions all used
to make it efficient and reliable which are given below:
Login:
This function is to provide security and different privileges to different user (administrator or
employee)
Transaction:
All the transaction will be data will be entered through this function to store information as record.
Generate report:
This function will enable the user to generate reports (daily, weekly, monthly) which will contain all
information about transaction and will have portion for profit and lose
Register employee:
This function can only be used by administrator to add employee and his/her all information including
his/her id and password
Register product:
This function is to add product information in the system including its company name, and all related
information.
Manage record:
This function enable administrator to change some information if he/she wants to change about
employee, product.
3. UseCase(s)
3.1. Use Case List

UseCase PrimaryActor UseCases
ID
A1 Administrator, Login
Employee
A2 Administrator, Logout
Employee
A3 Administrator Register Employee
A4 Administrator Register Product
A5 Administrator, Search Records
Employee
A6 Administrator Manage Records
A7 Administrator Generate Report
A8 Administrator, Register Transaction
Employee
A9 Administrator, Invoice - Receipt
Employee
3.2.UseCaseDiagram
3.3. UseCase
Description
3.3.1Login
UseCaseID: A1
UseCase Login
Name:
Actors: Employee , administrator
Description: The user should provide user name and password to authenticate himself
so the system should recognize either it is an administrator or an
employee
Trigger: The user clicks on the application icon
Preconditions: 1. The role is not defined
2. The user is not logged into the system.
Postconditions: 1. The user is logged in to the system

2. The system menu is displayed
NormalFlow: 1. User clicks the icon to start the application.
2. User types user name and password.
3. User confirms his entry is valid.
4. System validates if customer is registered.
5. System checks the status of the user.
6. System confirms login
AlternativeFlows: 2a. At step 2, If the employee forgets the password for login
1. User will request the administrator for a password.
2. The administrator will give the default password for each
employee respectively.
Exceptions: 4a. At step 4 of the normal flow, if the user enters invalid username and
password
1. The system displays error message invalid username and
password.
2. The flow returns to step 2.
Includes: ---
FrequencyofUse: When the application starts.
SpecialRequirements: This function will provide secure access to the system
Assumptions: Either the user is an administrator or employee
NotesandIssues: The password should not contain more than 8 alphanumeric characters.
3.3.2Logout
UseCaseID: A2
UseCase Logout
Name:
Actors: Employee , administrator
Description: The user should log out before closing the system to make the data
protected
Trigger: The user clicks the logout button.
Preconditions: The user is logged into the system and menu is displayed.
Postconditions: The user Successfully logged out from the system.

NormalFlow: 1. The user clicks the Log Out button.
2. The user will be logged out.
AlternativeFlows: ---
Exceptions: 1a. At step 1 of the normal flow, if the user by mistake clicks the log out
button when the activity is in process.
1. The system will ask for confirmation for logout
1.1. If the user enters Yes, use case resumes to step 2
1.2. If user enters No, system remains on current position.
Includes: Login
FrequencyofUse: On demand of user.
SpecialRequirements: If the system is cut off by electricity the user will be logged out
automatically to provide data security.
Assumptions: User was logged in.
NotesandIssues: After log out the data will not be accessible to any other user.
3.3.3.RegisterEmployee
UseCaseID: A3
UseCase Register Employee
Name:
Actors: Administrator
Description: In this function the administrator will have the privilege to register a
new employee
Trigger: The user clicks the Register Employee button
Preconditions: 1. User is logged into the system
2. The menu is displayed.
Postconditions: The database has been updated.

NormalFlow: 1. User clicks the Register Employee button.
2. User enters the required information of the employee.
3. User clicks the submit button.
4. System displays the message that employees record has been saved.
AlternativeFlows: ----
Exceptions: 3a. At step 3, if the user presses the submit button before entering all
information
1. Alert message Please fill all the fields will be displayed.
2. Use case resumes on step 2
Includes: Login
FrequencyofUse: On demand
SpecialRequirements:
Assumptions: The user is an administrator.
NotesandIssues: The user can edit the record after entering the information
3.3.4.RegisterProduct
UseCaseID: A4
UseCase Register Product
Name:
Description: In this function the administrator can register a new product by entering
the information about the company, date etc.
Trigger: The user clicks the Register Product button
Preconditions: 1. The product is not yet in the stock
2. The user is logged in to the system
3. The system menu is displayed
Postconditions: The product is in the stock.

NormalFlow: 1. User clicks the Register Product button.
2. User enters the necessary information about the product.
3. User clicks the submit button.
4. System displays the message that employees record has been
saved.
Exceptions: 3a. At step 3, if the user presses the submit button before entering all
information
1. Alert message Please fill all the fields will be displayed.
2. Use case resumes on step 2.
Includes: Login
SpecialRequirements: ---
Assumptions: The user is an administrator.
NotesandIssues: The user can edit the record after entering the information
3.3.5.SearchRecords
UseCaseID: A5
UseCase Search Records
Name:
Actors: Administrator, Employee
Description: The user will have privilege to view and search all records.
Trigger: When the user clicks the Search Record button.
Preconditions: 1. The user is logged in.
2. The records must be there in the database to be searched.
Postconditions: The desired record has been searched.

NormalFlow: 1. The user selects the search record button.
2. Option for different categories of records will be displayed
(employee / product/Transaction).
3. The user chooses the desired category to search.
4. The system searches for the desired record asked by the user
5. The system displays the record.
Exceptions: 4a. At step 4 of the normal flow, if the record doesnt exist
1. System will display error message No record found
2. Use case return to step 3 of the normal flow.
Includes: Login
SpecialRequirements: This system will restrict the employee that he cannot search the
employee records.
Assumptions: The user is an administrator
NotesandIssues: ---
3.3.6. ManageRecords
UseCaseID: A6
UseCase Manage Records
Name:
Description: In this function the administrator will have privilege to manage (update /
modify) all/any records if he/she wanted to.
Trigger: When user clicks Manage Record button.
Preconditions: 1. The administrator is logged in to the system.
2. System contains outdated or missing data.
Postconditions: The system will be updated with the desired changes to the record.
NormalFlow: 1. The user clicks the Manage Records button.
2. Categories of different records will be displayed (employee /
product/Transaction).
3. User chooses the desired category to be managed.
4. The user manage the desired records
5. User select the submit button.
6. System displays confirmation message that the records are now
updated.
AlternativeFlows: ----
Exceptions: 2a. At step 2, if user enters incorrect date for sale and purchase. For
example. Product sale date is before the date of purchase.
1. System will display error message Invalid Date. Try again.
2. Use case resumes at step 4 of the normal flow.
Includes: Login
SpecialRequirements: Backup system must be maintained for about a month to retrieve any
valuable information.
Assumptions: The records must be there in the database to be managed
(update/delete).
NotesandIssues: 1. The user can edit the record after entering the information.4
2. Care must be taken while managing records as important records
can be deleted.
3.3.7. GenerateReport
UseCaseID: A7
UseCase Generate Report
Name:
Description: This function will provide access to the user to generate the daily,
weekly or monthly reports for "Budgeting and Forecasting".
Trigger: User clicks Generate Report button.
Preconditions: User is logged in to the system.

Postconditions: The report is successfully generated.
NormalFlow: 1. User clicks the Generate Report button.
2. User specifies the type of report (daily, weekly, and monthly).
3. User clicks the Submit button.
4. System generates the report.
Exceptions: 3a. At step 3, If the user does not select the option for the type of report
the system
1. System will generate the daily report by default.
2. Use case resumes at step 4
Includes: Login
SpecialRequirements: ---
Assumptions: 1. The printer is present.
2. Records were present for report generation.
NotesandIssues: The system generates a default daily report if the user doesnt specify
the type of report.
3.3.8. RegisterTransaction
UseCaseID: A8
UseCase Register transaction
Name:
Actors: Administrator, Employee
Description: When the customer wants to buy a product .The employee adds
transaction record into the system. He enters the name of the product,
price, date and time of purchase.
Trigger: When the user clicks the Register Transaction button.
Preconditions: 1. User is logged into the system.
2. Product is in stock.
Post conditions: 1. The sales is registered

2. Inventory is updated.
Normal Flow: 1. Customer asks for a product
2. User looks for the product in the system.
3. User enters transaction information.
4. System is updated.
Alternative Flows: ---
Exceptions: 2a. At step 2 of the normal flow if the product is not in the stock.
1. System will display error message No record found.
2. Use case will terminate.
Includes: Login
Frequency of Use: On demand
Special Requirements: ---
Assumptions: ---
Notes and Issues: The administrator can monitor the registry at all times.
3.3.9. InvoiceReceipt
UseCaseID: A9.1
UseCase Invoice Receipt
Name:
Actors: Employee
Description: After the purchase, the customer will be able to receive the invoice
receipt
Trigger: When the system is updated after transaction.
Preconditions: 1. The user is logged into the system.
2. Transaction has been made
Postconditions: 1. The sale is registered
2. The inventory is updated
3. The user gets the receipt
NormalFlow: 1. System updates the inventory.
2. The system calculate the total of the invoice (product * quantity)
3. The system generates the invoice receipt
Exceptions:
Includes: Login
SpecialRequirements: The system must be available 24/7 for efficient transactions.
Assumptions: Transaction has been made.
NotesandIssues: The administrator can monitor the invoices at all times.
4. SpecificRequirements
4.1 Functionality
LOGIN
4.1.1<FunctionalRequirementOne>
Identifier A1.1
Title UsernameandPassword
Requirement Theusershallbeabletologinbyenteringhisusername(firstname)
andpassword(8alphanumericcharacters).
Source CEO(Chiefexecutiveofficer)
Rationale Tosecureconfidentialdata.
RestrictionsandRisk Theusershouldentercorrectusernameandpassword
Dependencies A1,A2,A3,A4,A5,A6,A7,A8,A9(Allrequirements)
Priority High
4.1.2<FunctionalRequirementTwo>
Identifier A1.2
Title Confirmlogin
Requirement Theusershallconfirmloginbyclickingtheloginicon.
Rationale Toconfirmthatthedatatheuserenteredisfinal,correctandvalid.
RestrictionsandRisk
Priority High
4.1.3<FunctionalRequirementThree>
Identifier A1.3
Title Accountverification
Requirement Thesystemshallverifythatusersprovidedaccountexistsinthedatabase
forlogintothesystem.
Rationale Tomakesurethattheuserisregisteredinthesystemandispartofthe
company.
RestrictionsandRisk
Priority High
4.1.4<FunctionalRequirementFour>
Identifier A1.4
Title Statusverification
Requirement Thesystemshallverifythestatusoftheuserasbeinganadministratoror
anemployeetoproviderespectiveaccesstothesystem.
Rationale Todifferentiatebetweenanemployeeandanadministratortolimittheir
accessaccordingly.
RestrictionsandRisk
Priority High
4.1.5<FunctionalRequirementFive>
Identifier A1.5
Title LoginSuccessful
Requirement Thesystemshalldisplayaconfirmationmessagetogivefeedbackthat
LoginSuccessful.
Rationale Toinformuserthatthesystemisreadytoaccess.
RestrictionsandRisk
Priority Low
4.1.6<FunctionalRequirementSix>
Identifier A1.6
Title LoginFailed
Requirement The system shall display a warning message invalid username and
password with an option reenter username or password if the user
enterswronginformation.
Rationale Wewanttoauthenticateeitheruserexistsornot
RestrictionsandRisk Theusershallgivetherightinformationrequiredbysystemtologin
Dependencies A1.3,A1.4,A1.5
Priority High
LOGOUT
4.1.7<FunctionalRequirementSeven>
Identifier A2.1
Title Logout
Requirement Theusershallbeabletologoutbyclickingthelogoutbuttononlyonce.
Rationale Wewanttoleavethesystemsafely
RestrictionsandRisk
Dependencies A2.2
Priority High
4.1.8<FunctionalRequirementEight>
Identifier A2.2
Title ConfirmationMessage
Requirement ThesystemshalldisplayamessageAreyousuretoexit?withanoption
YesorNoifanyactivityisinprocess.
Rationale Wewanttoaskfromuserthathewanttoleaveornot
RestrictionsandRisk Theusershalldoublecheckeverythingbeforeloggingoutsothatthereis
noriskoflossofdata.
Dependencies A2.3
Priority High
4.1.9<FunctionalRequirementNine>
Identifier A2.3
Title SuccessfulLogout
LogoutSuccessful.
Rationale Toinformuseraboutlogoutconfirmation
RestrictionsandRisk
Dependencies
Priority Low
REGISTEREMPLOYEE
4.1.10<FunctionalRequirementTen>
Identifier A3.1
Title RegisterEmployee
Requirement Theuser(administrator)shallbeabletoregisteranemployeebyclicking
theRegisterEmployeebuttononce.
Rationale Wewanttoregisteremployee
RestrictionsandRisk
Dependencies A3.2
Priority High
4.1.11<FunctionalRequirementEleven>
Identifier A3.2
Requirement The user (administrator) shall be able to fill the information, Name,
EmployeeId,NIC,Address,Contactinformation,Qualification,Dateof
Hire, Salary, of a new employee in the form that will appear after
clickingtheRegisterEmployeebutton.
Rationale Wewanttosaveallinformationabouttheemployee
RestrictionsandRisk Theusershallenteralltherequireddatainrespectivefieldrecommended
Dependencies A3.3
Priority High
4.1.12<FunctionalRequirementTwelve>
Identifier A3.3
Requirement Theuser(administrator)shallconfirmhisentrybyclickingthesubmit
buttonintheformonthescreen.
Rationale Toletthesystemknowthattheenteredinformationisfinal
RestrictionsandRisk Theusershallsavetheinformationaldatainmaindatabasebypressing
therightbutton(submit)once.
Dependencies A3.5
Priority High
4.1.13<FunctionalRequirementThirteen>
Identifier A3.4
Requirement ThesystemshallbeabletodisplayanalertmessageFillallrequired
fieldsiftheuserclicksthesubmitbuttonifanyfieldremainsempty
Rationale Wewanttoinformuserthathedidnotenterdatainallfields
RestrictionsandRisk
Dependencies A3.2
Priority High
4.1.14<FunctionalRequirementFourteen>
Identifier A3.5
RegistrationSuccessfulafterupdatingthesystem.
Rationale Toinformuserthattheemployeeinformationissuccessfullyregisteredin
thedatabase.
RestrictionsandRisk Theusershallfillalltherespectivefieldsbyenteringrightinformationso
thatdataissavedsuccessfullyinmaindatabase
Dependencies
Priority Low
REGISTERPRODUCT
4.1.15<FunctionalRequirementFifteen>
Identifier A4.1
Title RegisterNewProduct
Requirement Theuser(administrator)shallbeabletoregisteranewproductbyclicking
theProductRegistrationbuttononce
Rationale Wewanttoinformtheuserthathehasaddedproductdatasuccessfully
RestrictionsandRisk
Dependencies A4.2
Priority High
4.1.16<FunctionalRequirementSixteen>
Identifier A4.2
Title ProvideProductInformation
Requirement The user (administrator) shall be able to fill the information, Name,
Batchnumber,Company,Quantity,PurchaseDate,ExpireDateofanew
product in the form that will appear after clicking the Product
Registrationbutton.
Rationale Wewanttosaveallrelativeinformationaboutproduct
RestrictionsandRisk Nofieldshouldremainempty
Dependencies A4.3
Priority High
4.1.17<FunctionalRequirementSeventeen>
Identifier A4.3
Title ConfirmationofProduct
Requirement Theuser(administrator)shallbeabletoconfirmhisentrybyclickingthe
submitbuttonintheformonthescreen.
Rationale Wewanttoverifyandsavethegivendatabyuser
RestrictionsandRisk
Dependencies A4.6
Priority High
4.1.18<FunctionalRequirementEighteen>
Identifier A4.4
Title DisplayAlertMessage
Requirement ThesystemshallbeabletodisplayanalertmessageFillallrequired
fieldsiftheuserclicksthesubmitbuttonifanyfieldremainsempty.
Rationale Wewanttohaveallrespectiveinformationaboutproductanddontwant
tomissanyofall.
RestrictionsandRisk
Dependencies A4.2
Priority High
4.1.19<FunctionalRequirementNineteen>
Identifier A4.5
Title DisplayWarningMessage
Requirement ThesystemshalldisplayawarningmessageProductalreadyinstock
with an option update information if the user enters an already
registeredproduct.
Rationale Wedonotwantanyduplicationinourdatabase
RestrictionsandRisk
Dependencies
Priority High
4.1.20<FunctionalRequirementTwenty>
Identifier A4.6
Title DisplayconformationMessage
ProductRegistrationSuccessfulafterupdatingthesystem.
Rationale Wewanttoinformtheuserthatproductissuccessfullyregistered
RestrictionsandRisk
Dependencies
Priority Medium
SEARCHRECORD
4.1.21<FunctionalRequirementTwentyone>
Identifier A5.1
Title SearchRecords
Requirement TheusershallbeabletosearcharecordbyclickingtheSearchRecord
icon.
Rationale Tofindtherecord
RestrictionsandRisk
Dependencies A5.2
Priority High
4.1.22<FunctionalRequirementTwentytwo>
Identifier A5.2
Title Selecttypeoftherecords
Requirement Thesystemshallbeabletodisplaythemenu(C:/MenuForm)form
allowingtheusertochoosefromproduct,employeeortransactionrecord
byclickingthesubmitbuttononlyonce.
Rationale Tospecifytherecordtype
RestrictionsandRisk Theemployeeisrestrictedthathecannotaccesssomeofthefieldfrom
thedatabase
Dependencies
Priority High
4.1.23<FunctionalRequirementTwentythree>
Identifier A5.3
Title Privileges
Requirement Thesystemshallrestricttheuser(employee)tosearchtheemployee
recordbydisplayingthemessageRestrictedRecord.
Rationale Tospecifytheuser.
RestrictionsandRisk
Dependencies A5.2
Priority High
MANAGERECORD
4.1.24<FunctionalRequirementTwentyfour>
Identifier A6.1
Title Manage record
Requirement The user (administrator) shall be able to Manage (delete/update) a record
by clicking the Manage Record icon.
Source CEO(Chief executive officer)
Rationale When the user wants to change information about any record
Restrictions and Risk ---
Dependencies A6.2
Priority High
4.1.25<FunctionalRequirementTwentyfive>
Identifier A6.2
Title Selectthefieldtomanage
Requirement Thesystemshallbeabletodisplaythemenu(C:/MenuForm)form
allowingtheusertochoosewhichrecord(employee,productor
transaction)tobemanagedbyclickingtheManagerecordicon.
Rationale Tokeepthedatauptodateinthemaindatabase
RestrictionsandRisk Theemployeeisrestrictedthathecannotaccesssomeofthefieldfrom
thedatabase
Dependencies A6.3
Priority High
4.1.26<FunctionalRequirementTwentysix>
Identifier A6.3
Title Confirmthechanges
Requirement Thesystemshallallowtheusertoconfirmthechangesmadebyclicking
theConfirmModificationiconaftermakingchangesinthedatabase.
Rationale Tosavetherecentchangesindatabase
RestrictionsandRisk
Dependencies A6.4
Priority High
4.1.27<FunctionalRequirementTwentyseven>
Identifier A6.4
Title Confirmationmessage
SystemUpdatedaftermanagingtherecords.
Rationale Toinformtheuserthatyouhavesuccessfullyupdatedtheinformation
RestrictionsandRisk
Dependencies ...
Priority High
4.1.28<FunctionalRequirementTwentyeight>
Identifier A6.5
Title Alert message for confirmation
Requirement The system shall display a warning message Want to save changes? with
options to Save, Dont Save or Cancel if the user forgets to save the
changes made the record.
Source CEO
Rationale To make sure that data is not lost.
Restrictions and Risk
Dependencies A6.2
Priority High
GENERATEREPORT
4.1.29<FunctionalRequirementTwentynine>
Identifier A7.1
Title Generate Report
Requirement The user (administrator) shall be able to generate report by clicking the
Generate Report button.
Source CEO (Chief executive officer)
Rationale To let system know we want to generate a report.

Dependencies A7.2
Priority High
4.1.30<FunctionalRequirementThirty>
Identifier A7.2
Title Select Type
Requirement The user (administrator) shall be able to choose report the menu (daily,
weekly, monthly) displayed by the system.
Rationale Specify the report to be generated.
Restrictions and Risk
Dependencies A7.3
Priority High
4.1.31<FunctionalRequirementThirtyone>
Identifier A7.3
Title Default
Requirement The system shall be able to generate a default daily report if the user
doesnt specify the type of report.
Rationale To specify the system to generate at least a daily report.
Dependencies ---
Priority High
REGISTERTRANSACTION
4.1.32<FunctionalRequirementThirtytwo>
Identifier A8.1
Title Transaction Registration
Requirement The user (administrator) shall be able to Enter Transaction record by
clicking the Enter Transaction button.
Rationale To be able to enter transaction information
Dependencies A8.2
Priority High
4.1.33<FunctionalRequirementThirtythree>
Identifier A8.2
Title Provide Information
Requirement The system shall able to display a form (C:/Transaction.form) to enter
information of Product Name, Quantity, Price, Date and Time of purchase.
Rationale To keep a record of the sales in the company
Restrictions and Risk The user should enter all information in respective field
Dependencies A8.3
Priority High
4.1.34<FunctionalRequirementThirtyFour>
Identifier A8.3
Title Product availability
Requirement The system shall be able verify the product record and prompt the user by
displaying the message Product not in stock if the product quantity is
less than 0 in the database.

Rationale To check for availability of the product in the inventory
Restrictions and Risk The user should be restricted to not take order which can exceed the stock
Dependencies A9.1
Priority High
INVOICERECEIPT
4.1.35<FunctionalRequirementThirtyFive>
Identifier A9.1
Title Invoice
Requirement The system shall be able to produce invoice (receipt) containing
information of Product Name, Quantity, Price, Date and Time of purchase
transaction is performed
Rationale To give the proof to the customer of his/her purchase.
Dependencies ---
Priority Medium
4.2 Usability
4.2.1 <UsabilityRequirementOne>
TheSystemshallbeuserfriendlybyhavinganinterfacewithproperheadings,buttons,images,and
errororalertmessages.
4.2.2<UsabilityRequirementTwo>
The employee shall be able to use 99% features without error after a 1 hour training session.
4.3 Reliability
4.3.1 <ReliabilityRequirementOne>
The system shall be unavailable for 2 minutes in 24 hrs.
4.3.2 <ReliabilityRequirementTwo>
The system shall have a mean time between failures of minimum 7 days.
4.3.3 <ReliabilityRequirementThree>
The system shall have a Maximum Bugs or Defect Rate of 1 bug/function-point.
4.3.4 <ReliabilityRequirementThree>
The system shall be able to repair within 5 seconds
4.4 Performance
4.4.1 <PerformanceRequirementOne>
Thesystemshallhavearesponsetimeofaverage0.2seconds/transactionandamaximum
0.5seconds/transaction.
4.4.2 <PerformanceRequirementTwo>
The system shall process a minimum of 5 transactions per second.
4.4.3 <PerformanceRequirementThree>
The system shall be able to accommodate a maximum of 15 new users.
4.5 Supportability
4.5.1 <SupportabilityRequirementOne>
Thesystemshallbeabletooperatewithinthemaximummaintenancebudgetforaminimumof4
years
4.5.2 <SupportabilityRequirementTwo>
ThesystemshallsupportIEEECodingStandards.
4.6 Security
4.6.1<SecurityRequirementOne>
The system shall be able to provide security by user login with their 8 digit alpha numeric password.
4.7 DesignConstraints
Since the application is designated for users who do not have a background of using computers, user
interface which is both effective and easy to use by the users will pose a difficult challenge. Inventory
System for Ariser Pharma will contain the following constraints:
4.7.1 <DesignConstraintOne>
The system shall be a desktop application.
4.7.2 <DesignConstraintTwo>
The system shall be implemented on a 32-bit Windows platform having:
Minimum 1 TB HDD
Intel dual core
processor, 2.3 MHz
Minimum 2 GB RAM
4.7.3 <DesignConstraint
Three>
The user interface shall be
designed in Visual C#.
4.7.4 <DesignConstraint Four>

The application shall be coded in C# and SQL language.
4.7.5 <DesignConstraint Five>

The database shall be maintained in Microsoft Access.
4.7.6 <DesignConstraintSix>
The application shall support shared networking facility
using LAN (Local Area Network).
4.8 Interfaces
4.8.1 UserInterfaces
4.8.2 Hardware Interfaces
This
will
be a
desktop application, and as such will

be designed to interface with the
hardware present on most of the 32-bit desktops.
As this system uses shared networking, it will be using the LAN network to connect to the administrator
computer and other shared computers, which will allow it to communicate with the database. This means
that it will be using the infrastructure of LAN and physical lines of the network in order to perform
properly.
4.8.3 CommunicationsInterfaces
ThissystemrequiresaLANadaptorforconnectingthecomputerswhicharetobeshared.

Inventory Management System for Ariser Pharma

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Inventory Management System for Ariser Pharma

Încărcat de

Drepturi de autor:

Formate disponibile

Software Requirements

Inventory System for

19th May, 2014

IEEE Software Requirements

Moreover, our system facilitates the users by following ways:

Improve efficiency, productivity

Sommerville. Software Engineering (6th Edition). Addison Wesley, 2000.

3.1. Use Case List

Postconditions: 1. The user is logged in to the system

Postconditions: The user Successfully logged out from the system.

Postconditions: The database has been updated.

Postconditions: The product is in the stock.

Postconditions: The desired record has been searched.

Preconditions: User is logged in to the system.

Post conditions: 1. The sales is registered

Restrictions and Risk ---

Source CEO (Chief executive officer)

4.7.4 <DesignConstraint Four>

4.7.5 <DesignConstraint Five>

4.8.2 Hardware Interfaces

desktop application, and as such will

S-ar putea să vă placă și