Maryam Doc-1

Final Year Project Report
Laptop Sales System

A report submitted in partial fulfillment of the degree of
Department of Computer Science &Information Technology
Revision History
Descriptio Author Comments

n
14- Version 1.0 Initial Draft
01-
17
Laptop Sales System
28- Version 2.0 Final Document

07-
17
Document Approval
The following Software Requirements Specification has been accepted and

approved by the following:
Signature Printed Name Title Date

Laptop Sales 05-03-18
System
Project Document Page 2 of 39

05/03/2018
Laptop Sales System
Table of Contents
Chapter 1 Introduction 6
1 Introduction 6
1.1.1 Purpose 6
1.1.2 Scope 6
1.1.3 Definitions, Acronyms and Abbreviations. 7
1.1.4 References: 7
1.1.5 Overview: 8
1.2 Overall Description: 8
1.2.1 Product Perspective: 8

1.2.1 Interfaces 8
1.2.2 Product Functions: 8
1.2.3 System Interface: 9
1.3 User Characteristics: 9
1.4 General Constrains: 9
1.5 Assumption and Dependencies: 9
Customer gives the details about the Laptop that she/he wants to purchase...........................9
1.5.1 Communications Interfaces 10
1.5.2 Memory Constraints 10
1.5.3 Operations 10
1.5.4 Site Adaptation Requirements 10
1.6 Product Functions 11
1.7 Constraints 11
1.8 Apportioning of Requirements 11
Chapter 2 Software Requirements Specification 12
2 .Specific Requirements: 12
2.1. External Interface Requirements: 13

2.1.1. User Interface: 13
2.1.2. Hardware interface: 13
2.1.3. Software Interface: 14
2.1.4. Communication Interface: 14
2.2 External Interfaces: 14

05/03/2018
Laptop Sales System
2.3 Functions 15
2.4 Performance Requirements 15
2.5 Logical Database Requirements 16
2.6 Design Constraints 16
2.6.1 Standards Compliance 16
2.7 Software System Attributes 16
2.7.1 Reliability 17
2.7.2 Availability: 17
2.7.3 Security: 17
2.7.4 Maintainability: 17
2.7.5 Portability: 18
2.8 Organizing the Specific Requirements: 19
2.8.1 System Mode: 19
2.8.2 User Class: 19
2.8.3 Objects: 19
2.8.4 Feature: 19
2.8.5 Stimulus: 19
2.8.6 Response: 19
2.8.7 Functional Hierarchy 19
2.9. Functional Requirements: 20
2.9.1 Login: 20
2.9.2 Registration: 21
2.9.3 Order: 21
2.9.4 Add Laptop: 21
2.9.5 Delete Laptop: 21
2.9.6 Search Laptop: 21
2.9.7 Update Laptop: 21
2.9.8 Report of sailing laptops: 22
Inputs: Report will be generated. 22
2.9.9 Use Case diagram: 22
2.11. Non Functional Requirement: 22
2.12. Design Constraint: 23
2.13. Logical database design: 23
Chapter 3 System Design and Architecture 24
3. SYSTEM OVERVIEW 24
3.1 Architectural Design 24

3.2 Decomposition Description 24
3.2.1. Data flow Diagram (DFD): 25
3.2.2 State Transition Diagram 25

05/03/2018
Laptop Sales System
3.2.3 Data Description 26

3.2.3.1 ER Diagram 27
3.4 Data Dictionary 27
3.4.1 Sign Up 28
3.4.2 Information Table 28
3.4.3 Sales information 29
3.4.4 Laptop Type: 30
3.4.5 Information Laptop: 30
3.4.6 Table: 31
3.4.7 Company: 32
3.6 Component Design 33
Chapter 4 Implementation and Testing 34
4.1 Overview of User Interface 34

4.2 Test Cases 34
4.2.1 Unit testing 34
4.2.2 Integration testing 34
4.2.3 System testing 35
4.3 Database Connectivity 35
4.4 Screen Images 35
4.4.1 Main Page 35
4.4.2 Login Page 36
4.4.3 Sales Page 36
4.4.3 Shop Information Page 37
4.4.4 Company Information Page 37
4.4.4 Report Page 38

05/03/2018
Laptop Sales System
Chapter 1
Introduction
1 Introduction
Laptop shop management system which is used to keep the record of whatever the sale
from shop. It is also used keep track of the remaining balance. It is the project of sailing
and purchasing the laptop .By using this software the shop manager can easily manage
their whole system. It provide the facility of data update, data recovery, data manipulation,
data modification and data integration. It also provide data security from unauthorized
access, It means only authorized user can access the data and manipulate it.
Laptop management system also saves times like in traditional system data was kept in
files there may be chances of lots of necessary data and information so that this system is
perfectly fruitful for management of laptop.
It provides a plate form to gather data, modify it, manipulate it or then keep it in secure
place. Data recovery and backup is also a major benefit of this system in case of any lots
of data. This SRS is going to define the different functions, interfaces and performance of
the system. This document is a Desktop-based that is used for the ease of Laptop
management admin
1.1.1 Purpose
Main purpose of Laptop management system is to better the performance of system so
that every person can easily interact and perform their actions. Information about the
Laptops and their records are safely kept in this system, actually this system is only made
for to facilitate Laptop Shop management owner and manager. Time saving and data
correctness is the main benefit of this system. All records are permanently stored. We can
access all information whenever we want to use.
1.1.2 Scope
This project is basically made to have a proper management of hostel .As we all know
hostels are the main factors because it provide opportunity for many of students .In the
whole world where ever the hostel is build there must be need of its management because
without managing hostel it may create many huge problems .So that now hostel admin
have no need to worry to manage their system because this system provides the complete
and perfect platform to manage their work .It is very important for hostel admin that there
should be completeness , perfectness in their managing .It may be a tough job for those
who don’t give much attention to this system . In the whole world this system is required
for management because it is fruitful for every person.

05/03/2018
Laptop Sales System
1.1.3 Definitions, Acronyms and Abbreviations.
WWW Set of large interlinked document on

internet.
Database Collection of all information that is
under control of this system.
HTML Hyper Text markup language that is
basically used to create the static
website.
Protocol A standard that enable the connection
for the communication and data
transfer.
Pause To stop something.
Resume To restart something.
Stakeholder Any person that is not a developer

but has interest in the system.
UML Unified modeling language. Standard
to write the software designs.
XML Extensive Markup Language that is

used for the transfer of data.
HTTP Hypertext transfer protocol.it is
client server protocol between server
and web browser.
HTTPS Secure hypertext transfer over
secure socket layer
1.1.4 References:
 http://seminarprojects.com/Thread-simple-download-manager#ixzz42qwn9TYs
 Wikipedia - www.wikipedia.com
 Database Management Systems.
1.1.5 Overview:

05/03/2018
Laptop Sales System
The rest of document will explain the specification of Laptop management system in
detail. SECTION 2 will explain the general factors that affect the software and its
requirements such as project constrains and user characteristics etc. SECTION 3 will
explain the detailed functional specific system and other related requirements of the
system.
1.2 Overall Description:
1.2.1 Product Perspective:

List each system interface and identify the functionality of the software to accomplish the
system requirement and the interface description to match the system. These are external
systems that you have to interact with. For instance, if you are building a business
application that interfaces with the existing employee payroll system, what is the API to
that system that designer’s will need to use.
1.2.1 Interfaces
Specify:
(1) The logical characteristics of each interface between the software product and its users.
(2) All the aspects of optimizing the interface with the person who must use the system
This is a description of how the system will interact with its users. Is there a GUI, a
command line or some other type of interface. Are there special interface requirements. If
you are designing for the general student population for instance, what is the impact of
ADA (American with Disabilities Act) on your interface.
1.2.2 Product Functions:

The software product will perform the following functionality:
 Customer gives information to shop manager.
 Customer pays all the bills.
 Shop manager gets customer requirements.
 Manager manipulate all gathered information.
 Manager displays Laptop bills.
 Manager stores all information of customer.
 DB manager update all of laptop and customer details.
The web browsing functionality of this software will allow the user to get information and
other type of material from anywhere using internet. User can save or have the
information. On any topic using this search engine. This software will also provide the
features of bookmark

05/03/2018
Laptop Sales System
1.2.3 System Interface:

The system interface of this software is designed using C sharp Visual Studio.
1.3 User Characteristics:

The user of this document should have basic knowledge of searching over the web
browser should have the knowledge that how to view history, how to book mark web
pages, how to use different tabs, how to download the material. User should also have
knowledge of word editing so that he could use these feature in detail. So we can
distribute the use in two levels:
 Education Level: The user should be at least educated to understand the

language of browser and editor(English).
 Technical Level: the user should be comfortable using general purpose

application on the personal computer.
1.4 General Constrains:
Software has the following constrains that should be kept in mind by developer while
developing the software:
 Ratio and size of monitor color or black and white monitor makes
it virtually.
 Font Color and sizes need to be changeable to meet the requirement
of sight damaged viewers.
 The Situation Become more complex when collaborative resizing of
windows and frames, printing or communication condition.
 Internet speed is major issue in the ensuring the good quality of
web browsing and downloading.
1.5 Assumption and Dependencies:

Some Web pages display wrong with some browsers.
 Browser Specific codes are
used in Programming of web masters.
 Processing power of CPU
Also effect the performance of system.
 The user must know English
language.
Customer gives the details about the Laptop that she/he wants to purchase.
1.5.1 Communications Interfaces

05/03/2018
Laptop Sales System
Specify the various interfaces to communications such as local network protocols, etc.
These are protocols you will need to directly interact with. If you happen to use web
services transparently to your application then do not list it here. If you are using a
custom protocol to communicate between systems, then document that protocol here so
designers know what to design. If it is a standard protocol, you can reference an existing
document or RFC.
1.5.2 Memory Constraints
Specify any applicable characteristics and limits on primary and secondary memory. Don’t
just make up something here. If all the customer’s machines have only 128K of RAM,
then your target design has got to come in under 128K so there is an actual requirement.
You could also cite market research here for shrink-wrap type applications “Focus groups
have determined that our target market has between 256-512M of RAM, therefore the
design footprint should not exceed 256M.” If there are no memory constraints, so state.
1.5.3 Operations
Specify the normal and special operations required by the user such as:
(1) The various modes of operations in the user organization
(2) Periods of interactive operations and periods of unattended operations
(3) Data processing support functions
(4) Backup and recovery operations
1.5.4 Site Adaptation Requirements
In this section:
(1) Define the requirements for any data or initialization sequences that are specific to a given
site, mission, or operational mode
(2) Specify the site or mission-related features that should be modified to adapt the software
to a particular installation
If any modifications to the customer’s work area would be required by your system, then
document that here. For instance, “A 100Kw backup generator and 10000 BTU air
conditioning system must be installed at the user site prior to software installation”.
This could also be software-specific like, “New data tables created for this system must be
installed on the company’s existing DB server and populated prior to system activation.”
Any equipment the customer would need to buy or any software setup that needs to be
done so that your system will install and operate correctly should be documented here.
1.6 Product Functions

05/03/2018
Laptop Sales System
Provide a summary of the major functions that the software will perform. Sometimes the
function summary that is necessary for this part can be taken directly from the section of
the higher-level specification (if one exists) that allocates particular functions to the
software product.
This describes the functionality of the system in the language of the customer. What
specifically does the system that will be designed have to do. Drawings are good, but
remember this is a description of what the system needs to do, not how you are going to
build it.
1.7 Constraints
Provide a general description of any other items that will limit the developer's options.
These can include:
(1) Regulatory policies

(2) Hardware limitations (for example, signal timing requirements)
(3) Interface to other applications
(4) Parallel operation
(5) Audit functions
(6) Control functions
(7) Higher-order language requirements
(8) Signal handshake protocols (for example, XON-XOFF, ACK-NACK)
(9) Reliability requirements
(10) Criticality of the application
(11) Safety and security considerations
1.8 Apportioning of Requirements

Identify requirements that may be delayed until future versions of the system. After you
look at the project plan and hours available, you may realize that you just cannot get
everything done. This section divides the requirements into different sections for
development and delivery. Remember to check with the customer – they should prioritize
the requirements and decide what does and does not get done. This can also be useful if
you are using an iterative life cycle model to specify which requirements will map to which
interation.

05/03/2018
Laptop Sales System
Chapter 2
Software Requirements Specification
2 .Specific Requirements:
This section contains all the software requirements at a level of detail sufficient to enable
designers to design a system to satisfy those requirements, and testers to test that the
system satisfies those requirements. Throughout this section, every stated requirement
should be externally perceivable by users, operators, or other external systems. These
requirements should include at a minimum a description of every input (stimulus) into the
system, every output (response) from the system and all functions performed by the
system in response to an input or in support of an output. The following principles apply:
(1) Specific requirements should be stated with all the characteristics of a good SRS
 correct
 unambiguous
 complete
 consistent
 ranked for importance and/or stability
 verifiable
 modifiable
 traceable
(2) Specific requirements should be cross-referenced to earlier documents that relate
(3) All requirements should be uniquely identifiable
(4) Careful attention should be given to organizing the requirements to maximize readability
(Several alternative organizations are given at end of document)
Before examining specific ways of organizing the requirements it is helpful to understand

the various items that comprise requirements as described in the following subclasses.
This section reiterates section 2, but is for developers not the customer. The customer
buys in with section 2, the designers use section 3 to design and build the actual
application.

05/03/2018
Laptop Sales System
Remember this is not design. Do not require specific software packages, etc unless the
customer specifically requires them. Avoid over-constraining your design. Use proper
terminology:
The system shall… A required, must have feature
The system should… A desired feature, but may be deferred til later
The system may… An optional, nice-to-have feature that may never make it to
implementation.
Each requirement should also be testable. Avoid imprecise statements like, “The system
shall be easy to use” Well no kidding, what does that mean? Avoid “motherhood and
apple pie” type statements, “The system shall be developed using good software
engineering practice”
Avoid examples, This is a specification, a designer should be able to read this spec and
build the system without bothering the customer again. Don’t say things like, “The system
shall accept configuration information such as name and address.” The designer doesn’t
know if that is the only two data elements or if there are 200. List every piece of
information that is required so the designers can build the right UI and data tables.
2.1. External Interface Requirements:

2.1.1. User Interface:
This software will have the user friendly and menu based interface. Following are the
things that are included in this interface.
 Getting information.
 Managing information.
 Updating data.
 Store data.
 Backup of data.
 Recovery of data.
 Sailed laptop detail.
 Present and new laptop
details.
 Laptop bill Calculation.
 All reports of laptop sales and
purchase.
 All remaining products
information.
 All products detail.
 All customers detailed that
are login.

05/03/2018
Laptop Sales System
2.1.2. Hardware interface:
 A system must contain 1 GB

RAM is required
 2.16Ghz processor is required
 233 MB Hard Disk Drive will
be used
2.1.3. Software Interface:
 Any window based Operating

System will be used like Vista Window 8, Window 7 and window
 d C sharp
 Back En10 etc.
 Front En d Operating System
File System
 Visual studio
2.1.4. Communication Interface:
 The Software when used as Sale person side must be connected to the internet
to submit the request to the customer requirement .
 The Software when used as admin side must be connected to the internet to
view the requests of the customer and can send the result to manager to
manage and update all information .
 The Protocol that is used for Communication will be HTTP .it provide
communication interface between client server.
2.2 External Interfaces:

This contains a detailed description of all inputs into and outputs from the software
system. It complements the interface descriptions in section 2 but does not repeat
information there. Remember section 2 presents information oriented to the customer/user
while section 3 is oriented to the developer.
It contains both content and format as follows:
 Name of item
 Description of purpose
 Source of input or destination of output
 Valid range, accuracy and/or tolerance
 Units of measure

05/03/2018
Laptop Sales System
 Timing
 Relationships to other inputs/outputs
 Screen formats/organization
 Window formats/organization
 Data formats
 Command formats
 End messages
2.3 Functions
Functional requirements define the fundamental actions that must take place in the
software in accepting and processing the inputs and in processing and generating the
outputs. These are generally listed as “shall” statements starting with "The system shall…
These include:
 Validity checks on the inputs

 Exact sequence of operations
 Responses to abnormal situation, including
 Overflow
 Communication facilities
 Error handling and recovery
 Effect of parameters
 Relationship of outputs to inputs, including
 Input/Output sequences
 Formulas for input to output conversion
It may be appropriate to partition the functional requirements into sub-functions or sub-

processes. This does not imply that the software design will also be partitioned that way.
2.4 Performance Requirements

This subsection specifies both the static and the dynamic numerical requirements placed on
the software or on human interaction with the software, as a whole. Static numerical
requirements may include:
(a) The number of terminals to be supported
(b) The number of simultaneous users to be supported
(c) Amount and type of information to be handled
Static numerical requirements are sometimes identified under a separate section entitled
capacity.

05/03/2018
Laptop Sales System
Dynamic numerical requirements may include, for example, the numbers of transactions
and tasks and the amount of data to be processed within certain time periods for both
normal and peak workload conditions.
All of these requirements should be stated in measurable terms.
For example,
95% of the transactions shall be processed in less than 1 second
rather than,
An operator shall not have to wait for the transaction to complete.
2.5 Logical Database Requirements

This section specifies the logical requirements for any information that is to be placed into
a database. This may include:
 Types of information used by various functions

 Frequency of use
 Accessing capabilities
 Data entities and their relationships
 Integrity constraints
 Data retention requirements
If the customer provided you with data models, those can be presented here. ER diagrams
(or static class diagrams) can be useful here to show complex data relationships.
Remember a diagram is worth a thousand words of confusing text.
2.6 Design Constraints

Specify design constraints that can be imposed by other standards, hardware limitations,
etc.
2.6.1 Standards Compliance
Specify the requirements derived from existing standards or regulations. They might
include:
(1) Report format
(2) Data naming
(3) Accounting procedures
(4) Audit Tracing

05/03/2018
Laptop Sales System
For example, this could specify the requirement for software to trace processing activity.
Such traces are needed for some applications to meet minimum regulatory or financial
standards. An audit trace requirement may, for example, state that all changes to a payroll
database must be recorded in a trace file with before and after values.
2.7 Software System Attributes

There are a number of attributes of software that can serve as requirements. It is
important that required attributes by specified so that their achievement can be objectively
verified. The following items provide a partial list of examples. These are also known as
non-functional requirements or quality attributes.
These are characteristics the system must possess, but that pervade (or cross-cut) the
design. These requirements have to be testable just like the functional requirements. Its
easy to start philosophizing here, but keep it specific.
2.7.1 Reliability
Specify the factors required to establish the required reliability of the software system at
time of delivery. If you have MTBF requirements, express them here. This doesn’t refer
to just having a program that does not crash. This has a specific engineering meaning.
2.7.2 Availability:
Specify the factors required to guarantee a defined availability level for the entire system
such as checkpoint, recovery, and restart. This is somewhat related to reliability. Some
systems run only infrequently on-demand (like MS Word). Some systems have to run 24/7
(like an e-commerce web site). The required availability will greatly impact the design.
What are the requirements for system recovery from a failure? “The system shall allow
users to restart the application after failure with the loss of at most 12 characters of input”.
2.7.3 Security:
Specify the factors that would protect the software from accidental or malicious access,
use, modification, destruction, or disclosure. Specific requirements in this area could
include the need to:
 Utilize certain cryptographic techniques
 Keep specific log or history data sets
 Assign certain functions to different modules
 Restrict communications between some areas of the program
 Check data integrity for critical variables
2.7.4 Maintainability:

05/03/2018
Laptop Sales System
Specify attributes of software that relate to the ease of maintenance of the software itself.
There may be some requirement for certain modularity, interfaces, complexity, etc.
Requirements should not be placed here just because they are thought to be good design
practices. If someone else will maintain the system
2.7.5 Portability:
Specify attributes of software that relate to the ease of porting the software to other host
machines and/or operating systems. This may include:
 Percentage of components with host-dependent code
 Percentage of code that is host dependent
 Use of a proven portable language
 Use of a particular compiler or language subset
 Use of a particular operating system
Once the relevant characteristics are selected, a subsection should be written for each,
explaining the rationale for including this characteristic and how it will be tested and
measured. A chart like this might be used to identify the key characteristics (rating them
High or Medium), then identifying which are preferred when trading off design or
implementation decisions (with the ID of the preferred one indicated in the chart to the
right). The chart below is optional (it can be confusing) and is for demonstrating tradeoff
analysis between different non-functional requirements. H/M/L is the relative priority of
that non-functional requirement.
 Correctness.
 Efficiency.
 Flexibility.
 Integrity.
 Ineroperabilty.
 Maintainability.
 Reliability.
 Security.
 Reusability.
Definitions of the quality characteristics not defined in the paragraphs above follow.
• Correctness - extent to which program satisfies specifications, fulfills user’s mission

objectives.
• Efficiency - amount of computing resources and code required to perform function.
• Flexibility - effort needed to modify operational program.
• Interoperability - effort needed to couple one system with another.
• Reliability - extent to which program performs with required precision.
• Reusability - extent to which it can be reused in another application.

05/03/2018
Laptop Sales System
• Testability - effort needed to test to ensure performs as intended.

• Usability - effort required to learn, operate, prepare input, and interpret output.
• Security-Provides security by giving user-name and password .
2.8 Organizing the Specific Requirements:

For anything but trivial systems the detailed requirements tend to be extensive. For this
reason, it is recommended that careful consideration be given to organizing these in a
manner optimal for understanding. There is no one optimal organization for all systems.
Different classes of systems lend themselves to different organizations of requirements in
section 3. Some of these organizations are described in the following sub classes.
2.8.1 System Mode:
Some systems behave quite differently depending on the mode of operation. When
organizing by mode there are two possible outlines. The choice depends on whether
interfaces and performance are dependent on mode.
2.8.2 User Class:
Some systems provide different sets of functions to different classes of users.
2.8.3 Objects:
Objects are real-world entities that have a counterpart within the system. Associated with
each object is a set of attributes and functions. These functions are also called services,
methods, or processes. Note that sets of objects may share attributes and services. These
are grouped together as classes.
2.8.4 Feature:
A feature is an externally desired service by the system that may require a sequence of
inputs to effect the desired result. Each feature is generally described in as sequence eof
stimulus-response pairs.
2.8.5 Stimulus:
Some systems can be best organized by describing their functions in terms of stimuli.
2.8.6 Response:
Some systems can be best organized by describing their functions in support of the
generation of a response.

05/03/2018
Laptop Sales System
2.8.7 Functional Hierarchy
When none of he above organizational schemes prove helpful, the overall functionality can
be organized into a hierarchy of functions organized by either common inputs, common
outputs, or common internal data access. Data flow diagrams and data dictionaries can be
use dot show the relationships between and among the functions and data.
2.9. Functional Requirements:

According to Laptop shop admin need and requirements the Laptop management system
could perform the following functionalities:
 Administrator aspect:
o Taking backup of database.
o Creating/editing/deleting the database.
o Add or delete users.
o Changing the super passwords
 User Aspect:
o Requesting registration
o Login to system
o Edit personal information
o View item
o Add item to cart
o Update cart
o Check item in cart
o Order items
o View orders
o View reports of sailing laptops and remaining laptops.
.
 Analysis:
o The user is already register or not.
o Authorizing user based on login and password.
2.9.1 Login:
Input: Enter user name and password.

Process: Matches the user and password from database.
Output: Successful login.
Error: Invalid user name or password.

05/03/2018
Laptop Sales System
2.9.2 Registration:
Input: Enter user name, password and other information.

Process: Checks the user is already registered or not.
Output: Successfully Registered.
Error: User is already registered.
2.9.3 Order:
Input: Click order button to order selected item.

Process: User is login or not.
Output: Order created.
Error: User is not login.
2.9.4 Add Laptop:
Inputs: Admin or staff should be logged in. All detail will be entered.
Processing: All detail will be stored in database.
Output: New Laptop will be stored in database.
Error: Any wrong detail entered.
2.9.5 Delete Laptop:
Inputs: Admin or staff should be logged in. Delete the Laptop detail.
Processing: All detail will be selected from database and delete.
Output: Record will be deleted.
Error: Any wrong detail entered which is not present in database.
2.9.6 Search Laptop:
Inputs: Admin or staff should be logged in. Staff/Admin enter the Laptop for
searching
Processing: Record will be selected from all stored records in database.
Output: If the Laptop exist then show record to the user.
2.9.7 Update Laptop:

05/03/2018
Laptop Sales System
Inputs: Admin or staff should be logged in. Staff/Admin should update the Laptop.
Processing: All records are updated.
Output: Laptop records will be updated.
2.9.8 Report of sailing laptops:
Inputs: Report will be generated.

Processing: Report will be made.
Output: Report will be shown.
2.9.9 Use Case diagram:
Figure 2.1: Use case Diagram
2.11. Non Functional Requirement:

 Performance Requirements:
 HTML should be fully supported.
 There should be no limitation of number of user any number of

05/03/2018
Laptop Sales System
user should be supported here.

 The number of task and transaction done in any period of time
like in peak workload and normal conditions usually depend
upon the internet connection and user speed
 Safety Requirements:
It is highly recommended that internet security software must be installed in user pc to
protect their PC’s from any malware, viruses and malicious software that will harm their
PC’s during using the ZedMix software.
 Security Requirements:
All the users should be authenticated properly before using the software. And this
authentication is provided by Email Address and password. All the activities that will take
placed must be logged.
2.12. Design Constraint:

 The software should be design using Waterfall approach because we know the
requirements in advance and it will be easy for us to develop the software by using
this approach.
 The hardware should provide complete support like 2.16 GHz processor is
required to run the software
 Coding should be Effective that it should take less memory and give more quick
result.
 64MB RAM WILL be required by browsing feature of software to run and
almost 512 MB RAM is required to run Downloading Feature of software
 Testing should be done by using Proper testing modules
2.13. Logical database design:
Figure 2.2: Logical Database Design of Laptop Management System

05/03/2018
Laptop Sales System
Chapter 3
System Design and Architecture
3. SYSTEM OVERVIEW
The purpose of the system is to manage the whole Laptop system. This system is
beneficial for managing records of the customer in Laptop Management system. The
system is to use for security purpose using app all information can be secured from
unauthorized users. Customer or Laptop information can be accessed easily at any time.
In the case of any mishap or if data is lost it can be recovered. Manipulation is done easily.
In the system customer gives all the information to the administrator. Admin gets all
information from the customer and then convert it into record according to details and
give it to the DB Manager.
DB Manager updates all of Laptop details and generates report.
3.1 Architectural Design

The laptop management system is a system which includes laptop detail like inserts,
update laptop details. The customer information includes the customer detail like update
customer personal information, select information, delete information\record. Customer
gives input to the system and system act like to these input and function are performed
according to these input information. The admin performs any activity like insert, delete,
update view or search the customer or laptop record.
3.2 Decomposition Description
Provide a decomposition of the subsystems in the architectural design. Supplement with text as
needed. You may choose to give a functional description or an object oriented description.
For a functional description, put top level data flow diagram (DFD) and structural decomposition
diagrams. For an OO description, put subsystem model, object diagrams, generalization hierarchy
diagram(s) (if any), aggregation hierarchy diagram(s) (if any), interface specifications, and
sequence diagrams here.

05/03/2018
Laptop Sales System
3.2.1. Data flow Diagram (DFD):
Figure 3.1: Data Flow Diagram of Laptop Management System
3.2.2 State Transition Diagram

05/03/2018
Laptop Sales System
Figure 3.2: State Transition Diagram
3.2.3 Data Description
Explain how the information domain of your system is transformed into data structures.

05/03/2018
Laptop Sales System
Describe how the major data or system entities are stored, processed and organized. List any
databases or data storage items.
3.2.3.1 ER Diagram
Figure 3.3: ER diagram
3.4 Data Dictionary

05/03/2018
Laptop Sales System
Alphabetically list the system entities or major data along with their types and descriptions. If you
provided a functional describes list all the functions and function parameters. If you provided an
OO description, list the objects and its attributes, methods and method parameters.
3.4.1 Sign Up
Table Name: sign up

Description: This table store information about sign up.
Primary Key: Nill
Description:
ID: It is store sign up id. The data type is integer.
User-type: It is store user type. The data type is nvarchar.
User-name: It is store user name. The data type is nvarchar.
email: It is store user email. The data type is nvarchar
Contact: It stores user contact. The data type is nvarchar.
Password: It stores password. The data type is nvarchar.
3.4.2 Information Table
Table Name: hotelinfo

Description: This table store information about sales information.
Primary Key: Nill

05/03/2018
Laptop Sales System
Description:
Hotel-Name: It is store company Name. The data type is nvarchar..
address: It is store address. The data type is nvarchar..
Contact: It is store information about contact. The data type is nvarchar.
email: It stores email info. The data type is nvarchar.
3.4.3 Sales information
Table Name: sales laptop

Description: This table store information about purchase laptop.
Primary Key: ID
Description:
ID: It is store purchase laptop ID. The data type is integer.

05/03/2018
Laptop Sales System
Type: It is store company Name. The data type is nvarchar..

Price: It is store the model of laptop. The data type is nvarchar..
Size: It is store price of laptop. The data type is nvarchar.
Des: It stores laptop desktop info. The data type is nvarchar.
Laptop Model: It is store the LCD of laptop. The data type is nvarchar..
Processor: It stores processor of laptop. The data type is nvarchar..
RAM: It stores the RAM value of laptop. The data type is nvarchar.
Hard Disk: It stores the quantity of laptop. The data type is nvarchar.
3.4.4 Laptop Type:
Table Name: laptop type

Description: This table store information about laptop type.
Primary Key: id
Description:

05/03/2018
Laptop Sales System
3.4.5 Information Laptop:
Table Name: table

Description: This table store information about table.
Primary Key: ID
Description:

3.4.6 Table:
Table Name: tbl

Description: This table store information about tables.
Primary Key: ID

05/03/2018
Laptop Sales System
Description:

3.4.7 Company:
Table Name: company

Description: This table store information about company information.
Primary Key: Nill

05/03/2018
Laptop Sales System
Name: It stores the company name of laptop. The data type is nvarchar.
Description: It stores the description of company of laptops. The data type is nvarchar.
3.6 Component Design
In this section, we take a closer look at what each component does in a more systematic way. If
Software Design Document you gave a functional description then it provides a summary of your
algorithm for each function describes in procedural description language (PDL) or pseudo code.
OO description, summarize each object member function for all the objects in PDL or pseudo
code. Describe any local data when necessary.

05/03/2018
Laptop Sales System
Chapter 4
Implementation and Testing
4.1 Overview of User Interface

4.1.1 User of the Admin
 Manager
 MD
4.1.1.1 Manager
Manager will be the main administrator of whole LSS(Laptop Sales system). He

will control all records of employees. He will use his login id and password to
access the system. Manager will add, delete or view employee records such as
attendance, overtime or salary report. He will check status if any employee can
have approval of leave or not according his designation.
4.1.1.2 Managing Director
MD is the owner of the industry. He will have the authority to login form a specific
id and password and then view records of all employees and manager too he could
also generate report anytime.
4.2 Test Cases

The test cases involves the testing of the developed system using variouskinds of
data. An elaborated testing of data is prepared and a system is tested using the test
data. While testing errors are noted and corrections remade, the corrections are
also noted for future use.
4.2.1 Unit testing

During the implementation of the system each module of the system was tested
separately to un-cover errors within its boundaries. User interface was used as a
guide in the process.
4.2.2 Integration testing

Integration testing is a systematic technique for constructing the program
structure while conducting tests to uncover errors associated with interfacing. The
objective is to take unit-tested module and build a program structure that has been
dictated by design.

05/03/2018
Laptop Sales System
4.2.3 System testing

Testing is a set of activities that can be planned in advance and conducted
systematically. The proposed system is tested in parallel with the software that
consists of its own phases of analysis, implementation, testing and maintenance.
4.3 Database Connectivity
4.4 Screen Images
Display screen-shots showing the interface from the user’s perspective. These can be hand drawn
or you can use an automated drawing tool. Just make them as accurate as possible.
4.4.1 Main Page

05/03/2018
Laptop Sales System
4.4.2 Login Page
4.4.3 Sales Page

05/03/2018
Laptop Sales System
4.4.3 Shop Information Page
4.4.4 Company Information Page

05/03/2018
Laptop Sales System
4.4.4 Report Page

05/03/2018
Laptop Sales System

05/03/2018

Maryam Doc-1

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Maryam Doc-1

Загружено:

Авторское право:

Доступные форматы

Final Year Project Report

Laptop Sales System

Department of Computer Science &Information Technology

Descriptio Author Comments

28- Version 2.0 Final Document

The following Software Requirements Specification has been accepted and

Signature Printed Name Title Date

Project Document Page 2 of 39

1.2 Overall Description: 8

1.2.1 Product Perspective: 8

Chapter 2 Software Requirements Specification 12

2.1. External Interface Requirements: 13

Project Document Page 3 of 39

Chapter 3 System Design and Architecture 24

3.1 Architectural Design 24

Project Document Page 4 of 39

3.2.3 Data Description 26

Chapter 4 Implementation and Testing 34

4.1 Overview of User Interface 34

Project Document Page 5 of 39

Project Document Page 6 of 39

1.1.3 Definitions, Acronyms and Abbreviations.

WWW Set of large interlinked document on

Resume To restart something.

Stakeholder Any person that is not a developer

XML Extensive Markup Language that is

Project Document Page 7 of 39

1.2 Overall Description:

1.2.1 Product Perspective:

1.2.2 Product Functions:

Project Document Page 8 of 39

1.2.3 System Interface:

1.3 User Characteristics:

 Education Level: The user should be at least educated to understand the

 Technical Level: the user should be comfortable using general purpose

1.4 General Constrains:

1.5 Assumption and Dependencies:

1.5.1 Communications Interfaces

Project Document Page 9 of 39

1.5.2 Memory Constraints

1.5.4 Site Adaptation Requirements

1.6 Product Functions

Project Document Page 10 of 39

(1) Regulatory policies

1.8 Apportioning of Requirements

Project Document Page 11 of 39

Before examining specific ways of organizing the requirements it is helpful to understand

Project Document Page 12 of 39

2.1. External Interface Requirements:

Project Document Page 13 of 39

2.1.2. Hardware interface:

 A system must contain 1 GB

2.1.3. Software Interface:

 Any window based Operating

2.1.4. Communication Interface:

2.2 External Interfaces:

It contains both content and format as follows:

Project Document Page 14 of 39

 Validity checks on the inputs

It may be appropriate to partition the functional requirements into sub-functions or sub-

2.4 Performance Requirements

Project Document Page 15 of 39

All of these requirements should be stated in measurable terms.