Free Computer Online Taleem
Online Admission System for
(Software Requirements Specification)
Coordinator:
Sajid
Document
Submitted by:
XXXXX
Program:
XXXXX
Table of Contents
1.
Scope (of the project)
2.
Functional and non-Functional Requiremens
3.
Use Case Diagram
4.
Usage Scenarios
5.
Adopted Methodology
Scope of Project:
This project’s aim is to
automate the system, pre-checking the inclusion of all
required material and automatically ranking each
student’s application based on a number of criteria. These criteria include the ranking of their school, their grade
at said school. The data used by the system is stored in a database that will
be the center of all information held about students and the base for the
remainder of the process after the initial application has been made. This
enables things to be simplified and considerably quickened, making the jobs of
the people involved easier. It supports the current process but centralizes it
and makes it possible for decisions to be made earlier and easier way.
1. Functional requirements:
This section provides the over view of the product.
The project will require the ASP.NET MVC as a front end and at the
back end the database MYSQL will be running.
Various functional modules that can be implemented by the product
will be:
i. Customers will be able to
login/register into the website.
ii. Customers will be able to
create an account after submitting their email id, name, address, etc on the
website.
iii. Customers will also be
able to easily search for products by using different keywords like
name, category wise etc and will be able to refine their results by using
filters such as price, product type etc. on the website.
iv. Customers will be able to
view the products in detail such as images, zoom in option etc. on the website.
v. Customers will have the ability
to pick and choose their products by submitting the information on the
website.
vi. Customers can view the
events posted by the admin on the website.
vii. Customers can submit their
reviews on the products listed on the website.
viii. Customers will be able to
place orders on the website.
ix. Customers will be able to
check their order status on the website.
x. Customers will be able to
use the facility of shopping cart on the website.
xi. Admin will be able to
manage the customers, products, orders etc on the website from the backend.
xii. Provide the basic pages
(i.e., about us, Contact Us, FAQ, help) for company information
2. Software Requirements:
i.
Operating System: Microsoft Windows XP or above
ii.
Front End tools: HTML, ASP.NET for website
iii.
Xamarin Forms for Mobile App development
iv.
Back End tools: MySql
3. Hardware Requirements:
i.
CPU: Pentium VI processor
ii.
RAM: 512 MB
iii.
HDD: 40 GB
iv.
Keyboard, Monitor, Mouse, Printer
2.
Non Functional Requirements
Some Performance requirements identified is listed below:
Ø The database shall be able
to accommodate a minimum of 10,000 records of students.
Ø The software shall support
use of multiple users at a time.
Restrict communications between some areas of the program. Check
data integrity for critical variables
Some
of the attributes of software that relate to the ease of porting the software
to other host machines and operating systems.
The user will be able to reset all options and all stored user
variables to default settings.
Some of the attributes identified for the reliability is listed
below:
Ø All data storage for user
variables will be committed to the database at the time of entry.
Ø Data corruption is
prevented by applying the possible backup procedures and techniques.
USE
CASE DIAGRAM:
Online
Shop from user perspective use case
Description:
This
use case provides the viewpoint for the whole process from user perspective.
Customer
sees only the necessary functions that the system must define.
Actors:
Online Customer
Preconditions:
Customer must have a bank account.
Base
Case:
1.
Customer must log in and authenticate
2.
Customer must choose the type of purchase to perform
3.
Customer can view and select products
4.
Customer can perform a purchase
5. Customer
can cancel a purchase
6. He
can view additional information regarding the purchase
Alternative
Flows
None
Post
conditions: Customer performs transactions based on defined accounts.
Additional
Info/Issues: None
View
Products Use Case
Description:
View
products use case describes the whole operations a user can perform on a
product currently on the store. It also describes an exceptional case when a
product is not available on the quantity required.
Preconditions:
Customer must login and authenticate firstly
Base
Case:
1.
Customer can view the products
2. He
can select the products
3. He
can add the products to cart
4. He
can define quantities on ordered products
5.
System checks whether the quantity is satisfied or not
6.
System responds to client with approving the purchase
7.
System generates an automatic order to products supplier
Alternative
Flows
None
Post
conditions: Customer performs transactions based on defined accounts.
Additional
Info/Issues: None
Make
Purchase Use Case
Description:
This
use case defines the cycle when customer makes a purchase. When deciding to
perform a purchase the customer proceeds to the checkout operation and then to
the payment method and according verifications.
Preconditions:
Customer must confirm the final form of the cart and products already in.
Base
Case:
1.
Customer must complete with the cart
2. He
is taken to the checkout step
3. He
is forwarded to a payment method based on the purchase type that he decided
beforehand.
Alternative
Flows:
The
customer may cancel the purchase when it is in “Not Available yet” status.
Post
conditions: Customer performs transactions based on defined account.
0 comments:
Post a Comment