Template-05 - Project Report (Part-1) 123
Template-05 - Project Report (Part-1) 123
Project Team
Student Name Student ID Program Contact Number Email Address
M Faisal MitM-s19-012 MIT 03244368810 Mitm-s19-12@superior.edu.pk
Muhammad Akram MitM-s19-004 MIT 03484226503 Mitm-s19-12@superior.edu.pk
Muhammad Waqas MitM-s19-003 MIT 03350488672 Mitm-s19-12@superior.edu.pk
Project Report
[Store Management System]
Change Record
Author(s) Version Date Notes Supervisor’s Signature
1.0 <Original Draft>
<Changes Based on
Feedback from
Supervisor>
<Changes Based on
Feedback From Faculty>
<Added Project Plan>
<Changes Based on
Feedback from
Supervisor>
APPROVAL
PROJECT SUPERVISOR
Comments: ___________________________________________________________________
_____________________________________________________________________________
Name:______________________________
Date:_______________________________ Signature:__________________________
PROJECT MANAGER
Comments: ___________________________________________________________________
_____________________________________________________________________________
Date:_______________________________ Signature:__________________________
Date:_______________________________ Signature:__________________________
Dedication
Acknowledgements
I am really thankful to my supervisor who has fully supported me in my all work and delivered me all
content already that support to understand work.
Executive Summary
Table of Contents
Faculty of CS&IT, Superior University Lahore, Pakistan 6
< Store Management System >
Dedication.......................................................................................................................................iv
Acknowledgements..........................................................................................................................v
Executive Summary.........................................................................................................................vi
Table of Contents...........................................................................................................................vii
List of Figures..................................................................................................................................ix
List of Tables.....................................................................................................................................x
Chapter 1.........................................................................................................................................1
Introduction.....................................................................................................................................1
1.1. Background.......................................................................................................................2
1.2. Motivations and Challenges..............................................................................................2
1.3. Goals and Objectives.........................................................................................................3
1.4. Literature Review/Existing Solutions.................................................................................3
1.5. Gap Analysis......................................................................................................................3
1.6. Proposed Solution.............................................................................................................5
1.7. Project Plan.......................................................................................................................5
1.7.1. Work Breakdown Structure...........................................................................................5
1.7.2. Roles & Responsibility Matrix........................................................................................6
1.7.3. Gantt Chart....................................................................................................................6
1.8. Report Outline...................................................................................................................7
Chapter 2.........................................................................................................................................8
Software Requirement Specifications..............................................................................................9
2.1. Introduction......................................................................................................................9
2.1.1. Purpose..........................................................................................................................9
2.1.2. Document Conventions.................................................................................................9
2.1.3. Intended Audience and Reading Suggestions...............................................................9
2.1.4. Product Scope..............................................................................................................10
2.1.5. References...................................................................................................................10
2.2. Overall Description..........................................................................................................10
2.2.1. Product Perspective.....................................................................................................10
2.2.2. Product Functions........................................................................................................11
2.2.3. User Classes and Characteristics.................................................................................12
2.2.4. Operating Environment...............................................................................................12
2.2.5. Design and Implementation Constraints.....................................................................13
2.2.6. User Documentation.....................................................................................................7
2.2.7. Assumptions and Dependencies...................................................................................7
2.3. External Interface Requirements......................................................................................8
2.3.1. User Interfaces...............................................................................................................8
2.3.2. Hardware Interfaces......................................................................................................8
2.3.3. Software Interfaces........................................................................................................8
2.3.4. Communications Interfaces...........................................................................................9
2.4. System Features................................................................................................................9
2.4.1. System Feature 1...........................................................................................................9
2.4.1.1. Description and Priority.............................................................................................9
Faculty of CS&IT, Superior University Lahore, Pakistan 7
< Store Management System >
2.4.1.2. Stimulus/Response Sequences..................................................................................9
2.4.1.3. Functional Requirements...........................................................................................9
2.4.2. System Feature 2.........................................................................................................10
2.4.2.1. Description and Priority...........................................................................................10
2.4.2.2. Stimulus/Response Sequences................................................................................10
2.4.2.3. Functional Requirements.........................................................................................10
2.4.3. System Feature 3 (and so on)......................................................................................11
2.5. Other Nonfunctional Requirements...............................................................................11
2.5.1. Performance Requirements........................................................................................11
2.5.2. Safety Requirements...................................................................................................11
2.5.3. Security Requirements................................................................................................12
2.5.4. Software Quality Attributes.........................................................................................12
2.5.5. Business Rules.............................................................................................................12
2.6. Other Requirements........................................................................................................12
Chapter 3.......................................................................................................................................13
Use Case Analysis...........................................................................................................................13
3.1. Use Case Model...............................................................................................................14
3.2. Fully Dressed Use Cases..................................................................................................14
Chapter 4.......................................................................................................................................15
System Design................................................................................................................................15
4.1. Architecture Diagram......................................................................................................16
4.2. Domain Model................................................................................................................16
4.3. Entity Relationship Diagram with data dictionary..........................................................16
4.4. Class Diagram..................................................................................................................17
4.5. Sequence / Collaboration Diagram.................................................................................17
4.6. Operation contracts........................................................................................................17
4.7. Activity Diagram..............................................................................................................18
4.8. State Transition Diagram.................................................................................................18
4.9. Component Diagram.......................................................................................................18
4.10. Deployment Diagram..................................................................................................19
4.11. Data Flow diagram [only if structured approach is used - Level 0 and 1]...................19
Chapter 5.......................................................................................................................................20
Implementation.............................................................................................................................20
5.1. Important Flow Control/Pseudo codes...........................................................................21
5.2. Components, Libraries, Web Services and stubs............................................................21
5.3. Deployment Environment...............................................................................................21
5.4. Tools and Techniques......................................................................................................22
5.5. Best Practices / Coding Standards...................................................................................22
5.6. Version Control................................................................................................................22
Appendices....................................................................................................................................23
Appendix A: Information / Promotional Material.........................................................................24
Reference and Bibliography...........................................................................................................27
Index..............................................................................................................................................29
Faculty of CS&IT, Superior University Lahore, Pakistan 8
< Store Management System >
List of Figures
List of Tables
1.5.2 Gap analysis process 4
1.7.1 work break down structure 6
Faculty of CS&IT, Superior University Lahore, Pakistan 9
< Store Management System >
1.7.3.1 Table Gantt chart 7
Chapter 1: Introduction
Stores Management System is a web based manufacturing system that enables a
manufacturing industry to schedule its manufacturing operations based on the daily update of
sales from its dealers. Once the sales figures of items for the past week are entered by the
dealers over the internet along with the orders for the next delivery, the schedule for the next
week’s production will be drawn up. A report of the required raw materials or parts will be
drawn up with the product requirements over the internet & asked to quote their rates.
1.1. Background
This system normally put all the incoming and outgoing product in store all the record will insert
on computer .users can shop from store and computerized bill issued by the computer for the
user all record will remain save in system as a record shopkeeper can checked all the detail of
his store on the computer in past it was a huge task many problem faced by manually work.
Communication.
Time Management.
Inventory Accuracy/Tracking.
Customer Expectations.
Redundant Processes.
Product Diversification.
Chapter 2
Software Requirement
Specifications
2.1 Introduction
A Software Requirements Specification (SRS) is a document that describes the nature of a
project, software or application. In simple words, SRS document is a manual of a project
provided it is prepared before you kick-start a project/application. This document is also known
by the names SRS report, software document
2.1.1 Purpose
The purpose of the document is to collect and analyze all assorted ideas that have come up
to define the system, its requirements with respect to consumers. Also, we shall predict and
sort out how we hope this product will be used in order to gain a better understanding of the
project, outline concepts that may be developed later, and document ideas that are being
considered, but may be discarded as the product develops.
2.1.5 References
The references are:
This subsection contains the requirements for the e-store. These requirements are
organized by the features discussed in the vision document. Features from vision
documents are then refined into use case diagrams and to sequence diagram to best
capture the functional requirements of the system. All these functional requirements can
be traced usingtractability matrix.
The user interface for the software shall be compatible to any browser such as Internet
Explorer, Mozilla or Netscape Navigator by which user can access to the system.
The user interface shall be implemented using any tool or software package like Java
Applet, MS Front Page, EJB etc.
Since the application must run over the internet, all the hardware shall require to connect
internet will be hardware interface for the system. As for e.g. Modem, WAN – LAN,
Ethernet Cross-Cable.
The store shall communicate with the content manager to get the product
specifications, offerings and promotions.
The store system shall communicate with billPay system to identify available
payment methods , validate the payments and process payment.
The store system shall communicate to credit management system for handling
financing options.
The store system shall communicate with CRM system to provide support.
REQ-SF1-3:
Bar code functions may be provided by the WMS vendor, but the inventory app needs to support
the use.
<Provide a short description of the feature and indicate whether it is of High, Medium, or
Low priority. You could also include specific priority component ratings, such as benefit,
penalty, cost, and risk (each rated on a relative scale from a low of 1 to a high of 9).>
2.4.2.2 Stimulus/Response Sequences
<List the sequences of user actions and system responses that stimulate the behavior
defined for this feature. These will correspond to the dialog elements associated with use
cases.>
2.4.2.3 Functional Requirements
<Itemize the detailed functional requirements associated with this feature. These are the
software capabilities that must be present in order for the user to carry out the services
provided by the feature, or to execute the use case. Include how the product should
respond to anticipated error conditions or invalid inputs. Requirements should be
concise, complete, unambiguous, verifiable, and necessary. Use “TBD” as a placeholder
to indicate when necessary information is not yet available.>
REQ-SF2-1:
REQ-SF2-2:
REQ-SF2-3:
Chapter 3
Use Case Analysis
3,2,1 figure
Chapter 4
System Design
4.3.2 figure
4.4.4 Figure
Product object
4.5.1:login sequence diagram
Where admin user will be able to login their account after login user can manage all operation
on stock ,discount ,payment sale all page such as sale purchase product stock will be secure and
user can access after login
.
4.5.2 figure
4.7.2 Figure
4.7.3 login activity diagram
4.7.4 figure
purpose of these UML diagrams is to represent states of a system. States plays a vital role
in state transition diagrams
4.9.3 Figure
4.11. Data Flow diagram [only if structured approach is used - Level 0 and 1]
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
Chapter 5
Implementation
Chapter 5: Implementation
Implementation is the part of the process where software engineers actually program
the code for the project. Software testing is an integral and important phase of
the software development process. This part of the process ensures that defects are
recognized as soon as possible
Technology Used
NET Framework Structure
Compilation to Manage Code
JIT compilation
JIT compilation Data Provider
The Connection object
The command Object
The Data Reader object
Appendices
A.1. Broacher
A.2. Flyer
A.3. Standee
A.4. Banner
A.5. First Level heading [16 pt, Calibri, Bold, Left aligned]
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
A.5.1. Second level heading [14 pt, Calibri, Bold, Left aligned]
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
A.1.1.1. Third level heading [12 pt, Calibri, Bold, Left aligned]
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
A.1. First Level heading [16 pt, Calibri, Bold, Left aligned]
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
A.1.1. Second level heading [14 pt, Calibri, Bold, Left aligned]
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
A.1.1.2. Third level heading [12 pt, Calibri, Bold, Left aligned]
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
Reference and
Bibliography
[1] M. Sher, M. Rehman, “Title of the Paper” Conference name/Journal Name, Edition,
Volume, Issue, ISBN/ISSN, PP, Publisher/City-Country, Year.
[2] ……
Index
Index
[A]
[B]
[C]