Mobile provisions supervision

Title of the Project: Mobile provisions supervision

Project Architecture: N-Tire/MVC Architecture
SDLC Methodologies: Waterfall/Spiral Model
Course:
Roll No:
Name of the Student:
Technology And Language: MS.Net 3.5 With Visual C#
Internal Guide:
E-Mail ID:
Mobile No (Student):

Abstract of the Project:

Introduction:
Mobile provisions supervision is the web application providing services to the users who are the
purchasing the mobiles in online. The main aim of the Mobile provisions supervision is any customer
they can access the system through website at any time without going to the company. As a new
customer also he can collect all information like as a Category Type details. This projects deals mainly
buying the mobiles in online through the transactional process.

Functional Requirements:
The Mobile provisions supervision proposed to implement the services for two types of users like Administrators
and Customers and normal users.

• Admin manages all the information and the transactional standards that get executed upon the
system.
• This is highly integrated and associated for the operational standards upon the system. Admin
takes the overall authority standards upon the system.

• Administrator maintains all Customers Details, Bill Details and Districts and Locations details are
maintained.
• Admin gives the flexibility to all the normal users who visit the website.
• This is a public user profile and is generalized to provide such information, and choose the
different mobiles.
• This is just a simple viewable profile and does not help the users in executing any transactional
standards.
• User can login, view the mobiles, give the orders and pay the bill through the transactional
process.
Non-Functional Requirements:
• Secure access of confidential data (user’s details). SSL (Secure Sockets Layer) can be used.
• 24 X 7 availability
• Better component design to get better performance at peak time
• Flexible service based architecture will be highly desirable for future extension

Existing System:
The existing system is manual and the manual system works in the following way:
• Whenever the users want to purchase mobiles, they need to go nearest mobile shop and user
has to view all the details about mobiles.
 • After purchasing the mobile user may get the problem with that, again user need to go concern
sales holders. In this process user may feel some kind of difficulty.

• If any mobile details related to the user have been changed then the details has to be submitted
again. This process is to be taken manually.
Till now most companies has adopted the above manual system that produces lot of problems and at
the same time the following disadvantages are there with the above system.

The increasing complexity, producing the reports as desired is not possible, and protracted time-scales
of modern systems design and development have made working to a standardized Mobile Provisions
Supervision system both essential and mandatory.

Proposed Systems:
To overcome all the difficulties of the existing system the management has proposed automated the
whole system and the development of the new automated system contains the following activities,
which try to automate the entire process keeping in view of the database integration approach.

• It provides complete activity as automated system.

• It is not limited to a single system because it is aimed to develop for web based
environment.
• User friendliness (Graphical User Interface) is provided in the application.
• Provide Interactive interface through which a user can interact with different areas of
application easily.
• The system makes the overall task much easier and flexible.
• It can be accessed over the Internet/Intranet.
• There is no risk of data mismanagement at any level while the project development is under
process.
• It provides high level of security using session technique.
• It provides role based authentication to the different users like Administrator, Customers and
Normal users.
• Deploy the application on a single system and make is available on all the systems within the
network, thereby reducing the maintenance cost of software.

Modules:
After looking at the functional requirements it is identified that we can divide the system into mainly
following modules:
• Admin Module
• Customer Module
• Reports Module
• Authentication Module

Administrative module:

This module manages all the information and the transactional standards that get executed upon the
system. This module is highly integrated and associated for the operational standards upon the system.
This module takes the overall authority standards upon the system.

Customer module:

This module gives the flexibility to all the customers and normal users who visit the website. This is a
public user profile and is generalized to provide such information and choose different mobiles. The
 module is just a simple viewable profile and does not help the users in executing any transactional
standards.

Reports Module:
In this Module both Administrator and Customer generates the reports. Administrator maintain the
mobile details and accessory details, the customer view the mobile details and order details

Authentication Module:
The Authentication module is the security module provides Credentials i.e. valid username, password
to the persons who are logging in this project.

Users of the System:

This system should be designed to support the following users:
• Administrator
• Customers
• Normal users

Environment:
• Servers:

• Operating System Server: - Microsoft Windows XP/2000 or Higher

• Data Base Server: Microsoft SQL Server 2005/2008

• Clients: Microsoft Internet Explorer (Client Browser)

• Development Tools: Microsoft Visual Studio .Net 2008/2010

• Documentation Tools: MS Office 2007/2010

• Drawing Tools: IBM Rational Rose Enterprise, MS Office Visio 2007

• User Interface: ASP.NET With AJAX

• Code Behind: VC#.NET

Requirements:
• Hardware Requirements:

Number Description
1 PC With Minimum 20 GB Hard-Disk And 1GB RAM

• Software Requirements:

Number Description
1 Windows XP/2000 Or Higher With MS-Office 2007/2010
2. MS-SQL Server 2005/2008
3. Ms-Visual Studio .Net 2008/2010
4. MS-Internet Explorer
Milestones:
No. Milestone Milestone Description
Name
1 Requirements Complete specification of the
Specification system including defining
hierarchies constitutes this
milestone. A document detailing
the same should be written and
a presentation on that be made.
2 Technology Understanding of the technology
Familiarization needed to implement the project.
3 Database A database of at least 10 entries
Creation of users with at least 1 should
application admin.
4 High-level and Listing down all possible
Detailed scenarios and then coming up
Design with flow-charts or pseudo code
to handle the scenario.
5 Development Implementation of the main
of Front End screen giving the login, screen
Functionalities. that follows the login giving
various options, screens for each
of the options
6 Integrating the The front-end developed in the
Front-end with earlier milestone will now be able
the Database to update the database. Other
features should be functional at
this stage. In short, the system
should be ready for integration
testing.
7 Integration The system should be thoroughly
Testing tested by running all the test
cases written for the system
(from milestone 5).
8 Final Review Issues found during the previous
milestone are fixed and the
system is ready for the final
review.
The following steps will be helpful to start of the project:
• Study and be comfortable with technologies such as: ASP.Net with C#, and SQL Server.
• Gather some knowledge of product hierarchies and maintenance before starting the design.
• Create a user database with different access levels.
Remarks
Attempt should be made to add
some more relevant functionality
other than those that are listed in
this document.
The presentation should be from
the point of view of being able to
apply it to the project, rather than
from a theoretical perspective.
It is important to finalize on the
database at this stage itself so that
development and testing can
proceed with the actual database
itself.
The scenarios should map to the
requirement specification.
During this milestone period, it
would be a good idea for the team
to start working on a test-plan for
the entire system. This test-plan
can be updated as and when new
scenarios come to mind.
Another 2 weeks should be there
to handle any issues found during
testing of the system. After that,
the final demo can be arranged.
During the final review of the
project, it should be checked that
all the requirements specified
during milestone number 1 are
fulfilled
• Start with creating the login screen.
• Create menus for navigation and group the functionalities as sub menus.
• Create the help-pages of the application in the form of FAQ. This will helps user.